Clinic operations platform
MediCare
A patient and clinic-management system covering patient administration, appointments, clinical records, billing, staff permissions and an embeddable scheduling service.
Product work and architecture overview by Savi Saluwadana.
What it does
- Who it serves
- Clinic staff, doctors, billing operators, administrators and patients.
- Product purpose
- Patient administration, appointments, clinical records and billing.
- Patient profiles and conflict-aware appointment scheduling.
- Clinical records with SOAP notes, vitals and prescriptions.
- Billing records, payment tracking and operational dashboards.
- Staff management and a separate embeddable scheduling API.
How it works
- Clinic staff register a patient or arrange an appointment.
- The Go API validates identity, role permissions and domain requests.
- PostgreSQL stores patient, appointment, clinical and billing state.
- A separate scheduling service supports website embeds within its intended scheduling boundary.
Architecture
Next.js → Go API + scheduling service → PostgreSQL
| Component | Responsibility |
|---|---|
| Next.js | Patient, appointment, clinical, billing and admin interfaces. |
| Go domain API | JWT sessions, role checks and clinic workflows. |
| Scheduling API | Separate service boundary for embeddable appointments. |
| PostgreSQL | Patient and operational records persisted by the backend. |
Current scope
The main clinic API and embeddable scheduling API use separate service boundaries. Server-enforced roles separate clinical, billing and administrative access.
Architecture summary reviewed . The repository is private; this page provides a public product summary.