Inspiration

Living in Eastern North Carolina, we witnessed firsthand the healthcare crisis affecting rural communities. With 60+ rural hospitals closing since 2010 and 83% of rural counties facing physician shortages, our neighbors often drive 40+ minutes just to see a doctor. We saw elderly residents struggling to manage appointments across multiple providers, families missing work because they couldn't schedule appointments online, and a complete lack of centralized healthcare information. This inspired us to create Life.com - a unified healthcare portal that brings modern digital healthcare access to underserved rural communities.

What it does

Life.com is a comprehensive healthcare portal that connects patients with providers, pharmacies, and healthcare services in Eastern North Carolina. Users can:

  • Create secure accounts and manage their healthcare journey
  • Search and discover 12 healthcare providers across Eastern NC with detailed information about specializations, services, hours, and contact details
  • Book appointments with providers based on their healthcare needs (preventive care, chronic disease management, specialty care)
  • Manage appointments - view upcoming visits, reschedule, or cancel with just a few clicks
  • Find pharmacies - locate 6 pharmacy locations with addresses and contact information
  • Personalized experience - each user has their own dashboard with their appointments and healthcare information
  • Accessible design - dark/light mode toggle for users with visual impairments, mobile-responsive for access anywhere

The platform is available 24/7, allowing patients to manage their healthcare on their schedule, not just during office hours.

How we built it

We built Life.com using a modern, scalable technology stack:

Backend:

  • Python 3.11 with Flask 3.0.0 web framework for rapid development
  • Gunicorn 21.2.0 as the production WSGI server with 2 workers
  • JSON-based data storage for users and appointments (designed for easy migration to PostgreSQL/DynamoDB)
  • Session-based authentication for secure user management

Frontend:

  • HTML5 with Jinja2 templating for dynamic content
  • Custom CSS3 with flexbox/grid layouts and CSS variables for theming
  • Vanilla JavaScript for interactivity and theme persistence
  • SVG custom favicon with medical cross and stethoscope design
  • Mobile-first responsive design

Testing & Quality:

  • pytest for unit and integration testing
  • pytest-cov for code coverage analysis
  • hypothesis for property-based testing to catch edge cases

Cloud Infrastructure (AWS):

  • Elastic Beanstalk for managed platform orchestration
  • EC2 (t2.micro) instances for compute
  • Elastic Load Balancer for traffic distribution and high availability
  • Auto Scaling Groups for dynamic resource allocation
  • S3 for application package storage
  • CloudWatch for monitoring, logging, and alarms
  • IAM for security and access control

Deployment:

  • Dockerized application for consistency
  • Pushed to AWS ECR (Elastic Container Registry)
  • Deployed via Elastic Beanstalk with Procfile configuration
  • Zero-downtime rolling updates
  • Automated health checks every 5 seconds

Challenges we ran into

. AWS Deployment Complexity: We initially tried App Runner, which had health check failures due to port configuration issues. Then attempted Elastic Beanstalk but hit IAM permission errors requiring instance profiles. We persevered through multiple deployment attempts, learning AWS architecture deeply in the process.

  1. Port Configuration: Discovered that different AWS services expect different ports - App Runner wanted 8080, but Elastic Beanstalk on Amazon Linux 2023 expected 8000. We had to update our Procfile and redeploy.

  2. Session Management: Implementing secure session-based authentication while ensuring user data isolation was tricky. We had to carefully design the session flow to prevent cross-user data access.

  3. Responsive Design: Creating a UI that works seamlessly on both mobile and desktop while maintaining the dark/light mode functionality required careful CSS architecture and testing across devices.

  4. Time Constraints: Building a production-ready application with full AWS deployment in a hackathon timeframe pushed us to prioritize features and work efficiently.

Accomplishments that we're proud of

Production Deployment: We didn't just build a demo - we deployed a fully functional application on AWS with enterprise-grade infrastructure including load balancing, auto-scaling, and monitoring.

Real Healthcare Data: Integrated 12 actual healthcare providers and 6 pharmacies from Eastern North Carolina with accurate information, making this immediately useful for real users.

Complete User Journey: Built end-to-end functionality from registration to appointment booking to management - a complete healthcare experience.

Accessibility First: Implemented dark/light mode and responsive design to ensure the platform is accessible to elderly users and those with visual impairments.

Security & Privacy: Implemented session-based authentication, user data isolation, HTTPS encryption, and followed security best practices.

Scalable Architecture: Built with scalability in mind - our architecture can easily expand from 12 providers to 10,000+ nationwide.

Zero Downtime: Achieved production-ready deployment with health monitoring, auto-recovery, and zero-downtime updates.

What we learned

Technical Skills:

  • Deep dive into AWS services (Elastic Beanstalk, EC2, ELB, S3, CloudWatch, IAM)
  • Production deployment best practices and DevOps workflows
  • Importance of health checks and monitoring in production systems
  • How to debug cloud deployment issues using logs and metrics
  • Docker containerization and its benefits for deployment consistency

Healthcare Domain:

  • The severity of healthcare access issues in rural America
  • How digital solutions can bridge the healthcare gap
  • Importance of user-friendly design for diverse age groups
  • HIPAA compliance requirements for healthcare applications

Product Development:

  • Balancing feature completeness with time constraints
  • Importance of MVP (Minimum Viable Product) approach
  • User experience design for non-technical audiences
  • How to prioritize features that deliver maximum impact

Teamwork:

  • Effective problem-solving under pressure
  • Importance of clear communication during deployment issues
  • How to pivot quickly when facing technical roadblocks
  • Value of persistence when deployments fail multiple times

What's next for Life.com

Make it scalable to all US rural communities.

Share this project:

Updates