Inpatient and day-case
Wards, beds and bed states, admissions and discharges, transfers between wards, and a bed board that reflects what is actually happening rather than what was entered this morning.
Features
Six pillars, one patient record
Every module writes to the same schema and the same audit trail. That is the whole reason the pharmacy screen can see the allergy list and the biller can see what actually happened in the room.
The pillars
What each part of the product is for
Listed in full rather than summarised, because a features page that hides the detail is a features page that has something to hide.
Scheduling and slot recovery
An empty chair costs the same as a full one. The scheduler's job is to make sure there are fewer of them.
- Provider schedules with break rules, session templates, holidays and per-facility hours
- Slot holds during checkout, so two patients cannot book the same 09:15 from two devices
- No-show risk score on every booking, with an escalating reminder ladder for the risky ones
- Waitlist that automatically offers a cancelled slot to the best-matched waiting patient
- Timezone-correct throughout: a clinic in Lagos sees Lagos times from a laptop set to UTC
- Public booking page per clinic, on your own domain if you want it
EMR with decision support
A chart that helps at the point of the decision, not a form that has to be completed afterwards.
- Problem list, allergies, medications, immunisations and vitals with growth-appropriate ranges
- Drug–drug and drug–allergy interaction checking at the moment of prescribing
- Structured notes with specialty templates, amendments that preserve the original, and real signatures
- Lab and imaging orders with reference ranges, critical-value flagging and acknowledgement tracking
- Every chart access written to the audit trail with the patient it concerned
- Break-glass access that works in an emergency and generates an alert that a human reviews
Revenue cycle with denial prediction
Getting paid is a workflow, not an afterthought. Most of the money is lost before the claim is ever sent.
- Real-time eligibility checks at booking, so the patient learns their liability before they arrive
- Coding suggestions drawn from the signed note, with the supporting text quoted for the coder
- Claim scrubbing against payer edits before submission
- Denial prediction that ranks the queue, so the riskiest claim gets the human attention
- Partial payments, deposits, refunds and multi-currency, all in exact decimal arithmetic
- Invoices, receipts and statements that print correctly, because they are the legal copy of record
Pharmacy and laboratory
Stock that reconciles and results that reach the ordering clinician.
- Batch-level inventory with expiry control and FEFO dispensing
- Purchase orders, goods receipt, supplier ledger and stock movement history
- Dispensing checked against the patient's allergy list and current medications
- In-house and reference laboratory workflows, with LOINC-coded tests
- Sex- and age-specific reference ranges, and critical values that page someone
- Result acknowledgement tracking, because an unread critical result is the classic malpractice case
Patient engagement
The patient portal is the cheapest member of staff you will ever hire.
- Portal for appointments, results, prescriptions, documents and balances
- Secure messaging between patient and care team, with a real audit trail
- Reminders by SMS, email, WhatsApp and push, in the patient's language
- Intake forms and consent captured before the visit, not on a clipboard during it
- Recall campaigns for chronic-care follow-up and preventive screening
- Reviews requested only from patients who actually attended
AI that stays on a leash
Every AI feature is off by default, metered per call, and produces a draft a human signs.
- Ambient scribe that drafts the note and never files it without a clinician signature
- Symptom triage that routes urgency and always errs toward escalation
- Coding and denial-risk suggestions with the evidence quoted, not a bare answer
- Per-tenant opt-in: nothing is sent to a model provider until the tenant enables it
- Metered per call against a credit allowance, with soft caps that warn and hard caps that stop
- Zero data retention on the model provider side, and the provider named in our subprocessor register
Operational depth
The things that decide whether a clinic can actually run on it
Rarely asked about on the first call. Always asked about on the third.
Laboratory with critical values
In-house and reference workflows, LOINC-coded tests, sex- and age-specific reference ranges, and critical results that generate an alert and track whether a human acknowledged it.
Inventory that reconciles
Batch-level stock with expiry dates, FEFO dispensing, goods receipt against purchase orders, and a movement ledger that explains every discrepancy rather than absorbing it.
Roles that fit a real clinic
Owner, administrator, doctor, nurse, receptionist, pharmacist, lab technician, biller, and patient — each with per-permission grants and denials, and optional restriction to specific facilities.
Queue and walk-in management
Token-based queues per facility, walk-ins interleaved with the booked schedule, and wait-time reporting that tells you which session is quietly running forty minutes late every Tuesday.
Analytics that answer questions
Utilisation by provider and room, no-show cohorts, ageing receivables, denial reasons by payer, chart-closure time by clinician, and revenue by service line. All from the live record, not a nightly export.
Telehealth built in
Video visits attached to the appointment and the encounter, with the same charting, prescribing and billing path as an in-person visit. No separate system, no copy-paste afterwards.
Localisation that goes beyond translation
Per-tenant currency, decimal places and symbol placement, per-facility timezone and working hours, patient-preferred language for reminders, and date formats that do not require guessing.
Documents that print correctly
Prescriptions, invoices, lab reports and discharge summaries are frequently the legal copy of record. They print as black-on-white A4, severity survives greyscale, and single-use links are never expanded onto paper.
Break-glass with consequences
A clinician who needs a record they do not normally have access to can take it, with a reason. The access is granted immediately and generates an alert that a named person reviews — which is what makes the control real rather than theatrical.
FHIR R4 interoperability
Your data leaves as easily as it arrives
Coded at capture with the terminologies the receiving system expects, exposed over a standards-compliant API, and exportable in bulk without anyone writing a query.
US Core-aligned resources
Patient, Practitioner, Organization, Location, Encounter, Condition, AllergyIntolerance, MedicationRequest, Observation, DiagnosticReport, ServiceRequest, Immunization, Coverage and DocumentReference.
Read and write
RESTful search with the standard parameters, `$everything` for a full patient record, and transaction bundles for writes. Growth and Enterprise plans include write access; Professional is read-only.
SMART on FHIR launch
EHR-launch and standalone-launch flows so a third-party clinical app can open in context with scoped, time-limited access — and appear in the audit trail as itself, not as the clinician.
Bulk export
Asynchronous group-level export in NDJSON for population health, research extracts and payer reporting, without anyone writing a database query.
Terminology that travels
LOINC on laboratory tests, SNOMED CT on problems, RxNorm on medications, ICD-10 and CPT on billing. Coded once at capture, so the export is not a text-matching exercise.
Regional programmes
ABDM in India, Malaffi and NABIDH in the UAE, NPHIES in Saudi Arabia. These are licensing-bound integrations, so scope is confirmed per facility rather than assumed.
FHIR conformance is published as a machine-readable CapabilityStatement at the API root, so you can check exactly which resources and search parameters are supported rather than taking this page’s word for it. Regional programme integrations depend on facility licensing and are scoped per site.
See it against your own workflow
Bring a real week of your schedule to the demo. Generic demos prove nothing — we would rather find out on the call whether this fits how you actually work.
30 minutes, an engineer on the call, no slide deck.