12Healthcare & Clinics · Custom software
Patient records and appointment flow for a private clinic
Patient history, appointments and billing in one record instead of three books.
- Patient registry
- Appointment scheduling
- Visit and consultation notes
- Role-based access control
The problem
Patient files were paper, appointments a diary and billing a separate book. Retrieving a patient's history during a consultation meant fetching a file that was sometimes elsewhere.
What we built
We built a patient record carrying history, visits and billing, with access limited by role so clinical notes are visible only to clinical staff.
Modules delivered
- Patient registry
- Appointment scheduling
- Visit and consultation notes
- Role-based access control
- Billing from visit
- Visit history retrieval
What changed
What the delivered system does differently from the process it replaced.
- History is available during the consultation
- Billing derives from the recorded visit
- Clinical notes are restricted by role
Built with
The stack chosen for this build.
- Next.js
- TypeScript
- PostgreSQL
Why this customer is not named
Most of our customers allow the work to be described but not their name published. Where a customer has given permission, their name and testimonial appear here.
Independent accounts of our work are published by customers themselves on our Facebook reviews page.
Related case studies
Does this look like your problem?
If any of this is familiar, the first step is the same one this project started with: a free requirement study that ends in a written scope and a fixed price.