1. Health systems built around how a facility actually runs
Most facilities already have a way of working: registers, forms and handovers that staff know. The risk with a new system is that it breaks that flow. We start from the patient's path through your facility and build the system around it.
On screen: our design, with invented sample data.
2. One record, from the front desk to the report
The patient's path
- 01
Registration
Find or create the patient once, with the identifiers your facility uses.
- 02
Triage and consultation
Vitals, findings, diagnoses and orders recorded at the point of care.
- 03
Lab and pharmacy
Requests and results, prescriptions and dispensing, where these modules are in scope.
- 04
Billing and discharge
Charges, payments and discharge summaries tied to the same visit.
- 05
Reporting
Service counts and management summaries built from the records, not re-typed.
3. Start with what you need
Configurable modules
A small clinic and a hospital need different things. Modules are scoped per facility.
Patient records
Demographics, visit history and clinical notes.
Outpatient and inpatient
Queues, admissions, ward rounds and transfers.
Laboratory
Test catalogue, requests, results and validation.
Pharmacy and stores
Stock, dispensing, expiry and reorder levels.
Billing
Tariffs, invoices, receipts and insurance schemes where applicable.
Management dashboard
Attendance, services and stock at a glance for managers.
4. Questions facilities ask
Before you commit
What if the internet is unreliable?
Connectivity is part of the design conversation. Depending on the facility, options range from a local server to offline-capable capture that syncs when a connection returns.
Can it report to DHIS2 or eHMIS?
Reporting can be designed to match national formats, and automated exchange can be built where the facility or programme is authorised to connect. We never assume access to national systems.
Who owns the data?
The facility. Hosting, access and backups are agreed at the start and written down.
5. Users, connections and data
Who uses it
- Records and front deskRegistration, queues and appointments
- CliniciansConsultations, orders and clinical notes
- Lab and pharmacyResults, dispensing and stock
- AccountsBilling, payments and reconciliation
- ManagementDashboards and reports, without editing records
Connects to
- DHIS2 / eHMIS reporting formats
- HL7 FHIR where required
- Laboratory equipment exports
- Mobile money and payment references
- Excel and CSV imports
Integrations are scoped per project and built only where the facility is authorised to connect.
Data and security
- Role-based access so each person sees only what their work needs
- An audit trail of who created or changed a record, and when
- Encrypted connections, with hosting and backups agreed in writing
- Demonstrations use synthetic patients, never real records
Talk to us about health systems
Tell us how the work runs today. The first conversation is about understanding it, not selling a package.
Discuss a Health System