Elderly

Inspiration: Our inspiration came from the gaps we see in today’s healthcare systems: patients struggle to manage records across providers, doctors need streamlined tools to coordinate care, and insurance companies require reliable, structured data to process claims efficiently. We wanted to build a single platform where patients and doctors can interact seamlessly—booking appointments, storing health records, and managing care—while also giving insurers a trustworthy source of medical data. By leveraging Serverpod, we could rapidly prototype a secure, role‑based system that reduces friction for all three stakeholders and demonstrates how technology can simplify healthcare and insurance workflows.

What it does: Our app is a medical platform that enables seamless patient‑doctor interaction. Patients can book appointments, store and access health records, and manage their care through a dedicated dashboard. Doctors get their own dashboard to view patient histories, update records, and handle consultations. All of this is backed by Serverpod’s secure authentication, session management, and role‑based navigation. While our current implementation focuses on patients and doctors, our target audience is insurance companies — the app is designed to evolve into a trusted source of structured medical data that can simplify claim verification and reduce administrative overhead.

How we built it: We built the app using Serverpod as the backend, which provides authentication, session management, and role persistence. The flow begins with role selection (patient or doctor), stored in the profile schema, and continues with secure login and session handling. Based on the role, users are routed to their respective dashboards: patients can book appointments and manage health records, while doctors can view histories and update records. On the frontend, we used Flutter to deliver a clean, modular UI, and integrated Postgres for structured health record storage. To enable real‑time consultations, we added a streaming video call feature, allowing patients and doctors to connect directly within the app. This combination gave us a robust, end‑to‑end medical platform, while keeping the architecture simple and extensible for future insurance integration.

Challenges we ran into:

1. Since we were new to Serverpod, understanding the prerequisites—such as project structure, backend setup, and required tooling—was initially challenging.
2. Initially, understanding Serverpod’s architecture and workflow was challenging, especially how endpoints, data models, and client–server communication are structured.
3. Managing database schema changes and migrations was another challenge, especially understanding how Serverpod handles versioning and applying updates safely.
4. We also faced some friction with operational commands, such as Docker Compose setup, running migrations, and managing development vs production configurations.

Accomplishments that we're proud of: We’re proud that in just two weeks, and with Serverpod being completely new to us, we were able to design and implement a protocol‑level medical app that establishes the foundation for patient‑doctor dashboards, appointment booking, health record storage, and even real‑time video consultations. Getting role‑based authentication, session management, and structured data storage working smoothly with Serverpod was a big milestone. While the app is still early stage and there’s plenty of room to enhance features and polish workflows, we’re proud of how quickly we learned new tools, stitched together multiple components, and delivered a working prototype that demonstrates clear potential for scaling toward insurance integration.

What we learned

1. We gained hands-on experience building a full-stack application using Serverpod, with both frontend and backend in Dart.
2. We learned how auto-generated APIs and strongly typed models can significantly reduce development time and runtime errors.
3. Working with database migrations helped us understand schema evolution and data consistency within Serverpod.
4. We also learned how Docker and Docker Compose are used in Serverpod to manage services like the database and server runtime, including running containers, applying migrations, and maintaining consistent development environments.

What’s next for Elderly

1. Deepen our implementation of security, including proper SSL/TLS setup and robust token-based authentication.
2. Add more elderly-focused features, such as reminders, emergency alerts, and simplified UI improvements.
3. Improve scalability and performance as the user base grows beyond a hackathon prototype.
4. Conduct real user testing with elderly users and caregivers to refine usability and accessibility.

Built With

• dart
• docker
• flutter
• postgresql
• serverpod