Patient apps
Native iOS and Android experiences for discovery, booking, payments, appointments, tests, and profile.
- Five-tab patient journey
- Nearest-first provider ordering
- Remote media with caching
- Home
- Platform
Platform overview
Six product surfaces on one shared core
Patient apps, clinical workspaces, front-desk operations, diagnostics, and provider administration all read and write through the same scheduling, payment, notification, and access-control engine.
- API + web + iOS + Android
- Five operational roles
- One booking and payment core
Surface map
Every layer has a different job
Nothing here is a duplicate of the layer above it — each surface owns its own permissions, screens, and responsibilities.
Doctor portal
The clinical workspace: schedules, queue, prescriptions, test requests, printable records, and patient detail.
- Day and week schedule views
- Queue states and walk-ins
- Request ID search
Reception portal
Front-desk coordination with doctor-ready alerts, appointment updates, and bulk actions.
- Doctor-ready alert cycle
- Reschedule and cancel
- Role-safe visibility
Diagnostics network
Lab discovery, testlab role workflows, linked request sync, result uploads, and status propagation.
- Pending, in progress, done
- Result file uploads
- Offered tests and prices
Provider admin
Hospital, doctor, reception, and lab setup with imagery, rosters, counts, and audit visibility.
- Guided setup wizards
- Ordered image galleries
- Activity dashboards
Platform engine
Shared rules for auth, payments, slot generation, notifications, and feature toggles.
- UTC-safe slot logic
- Payment-before-booking guard
- Toggle-based rollout
One core
Decide a rule once, honour it everywhere
When slot duration, cancellation charges, or result status live in the shared engine, the mobile app and the web portal cannot disagree about them.
- Consistent slot resolution Same duration and availability windows on web and mobile.
- Quote-aware money flows Cancel and reschedule charges are quoted before anything mutates.
- Single status vocabulary Assigned, in progress, completed, cancelled — mapped once.
Why it holds up
Substance, not a feature checklist
The platform is built around three properties that are hard to retrofit later: genuine multi-platform reach, real separation between roles, and one place where shared logic lives.
Dual-app reach
Patient journeys ship on both iOS and Android, not one app and a roadmap promise.
Operational separation
Doctors, reception, labs, and admins each get scoped workflows and permissions.
Shared logic
Payment guards, slot rules, result status, and notifications stay consistent across surfaces.
Walk the whole platform in one call
We start from the role you care about most and follow a single patient all the way through to a delivered result.