LifePass

Inspiration

LifePass was inspired by a real emergency.

72 hours ago, I experienced a extermly painful gallstone attack while alone in my college dorm room. I had been in extreme pain for over eight hours, unable to stand upright or think clearly. Eventually, I had no choice but to Uber myself to the emergency room.

When I arrived, instead of receiving immediate medical attention, I was handed paperwork. I was asked to write down my full name, address, insurance information, emergency contacts, medications, allergies, and medical history, all while I could barely hold a pencil. Then the staff had to take my illegible handwriting and transfer it onto their computers.

This process took approximately 15–20 minutes before I was even checked in. In an emergency setting, every second matters. Yet the system prioritizes paperwork over patient care right now.

LifePass was created to solve this problem.

What it does

LifePass is a secure medical identity platform that allows patients to create a digital emergency profile and access it instantly through a QR code.

Instead of manually filling out forms, patients can simply present their QR code when they arrive at an emergency room. Healthcare providers scan the code and immediately retrieve the patient's intake information, including:

Name and date of birth
Insurance information
Emergency contacts
Allergies
Medications
Medical conditions

This reduces intake time from 15–20 minutes to just a few seconds. LifePass allows medical staff to focus on what matters most: providing care.

How we built it

LifePass was built using modern full-stack web technologies designed for speed, security, and scalability.

Frontend:

Next.js (React framework) — for fast, responsive user interfaces
TailwindCSS — for clean, professional styling

Backend:

Supabase — used for:
Secure database storage
Authentication
User management

Core functionality:

Patient profile creation and storage
Secure QR code generation
QR scanning interface for healthcare providers
Real-time retrieval of patient data from the database

The QR code does not contain sensitive medical information. Instead, it contains a unique identifier that securely retrieves data from Supabase when scanned.

This ensures both speed and privacy.

Challenges we ran into

One of the biggest challenges was designing a system that balanced speed, usability, and security.

We had to ensure that:

Sensitive medical data was never exposed directly in QR codes
Patient information could be retrieved instantly
The system was easy to use under stress

We also encountered challenges integrating Supabase with Next.js, particularly with type safety, authentication, and environment configuration.

Another challenge was designing a user interface that felt intuitive and trustworthy, especially for healthcare scenarios where clarity and reliability are critical.

What we learned

We learned how technology can directly impact people's lives.

Healthcare systems are often burdened by inefficiencies that increase stress for both patients and providers. LifePass showed us how thoughtful software design can improve critical experiences.

This project transformed a painful personal experience into a solution that could help millions of people.

What's next for LifePass

LifePass is currently focused on emergency room intake, but our long-term vision is to expand beyond ER use cases and support the entire healthcare system.

One major improvement is enabling profile reuse across different types of medical visits, such as primary care, urgent care, specialists, and clinics.

Today, patients are repeatedly asked to fill out nearly identical intake forms at every new provider. LifePass will allow patients to:

Reuse their existing medical profile across providers
Automatically pre-fill common information like name, insurance, medications, and allergies
Only answer new or provider-specific questions

This eliminates redundant paperwork and reduces patient friction across all healthcare interactions.

For example, instead of filling out 30 questions again, a patient might only need to answer 2–3 new ones specific to that provider.

Additional future improvements we want to do: