The concept defines the outcome
One identity, continuity of information and connected care centred on the person.
The CHS platform
The digital system behind the CHS concept.
The CHS platform is the software, data model and operational workflow layer designed to make the CHS health-system concept work in practice.
The platform provides the machinery
Registration, records, clinical workflows, permissions, audit, offline operation and controlled connections to coverage programmes.
What the platform provides
A shared operational foundation.
The platform records information once and makes it available only where the next authorised step requires it.
One health identity
The same person across connected facilities, with duplicate detection and a physical card as the offline fallback.
Longitudinal record
Conditions, allergies, medicines, encounters, results, referrals and admissions in one continuous history.
Care workflows
Consultation, nursing, laboratory, pharmacy and hospital care write directly to the shared record.
Coverage engine
A clear answer for this person, this service, this facility and this date, including any contribution or authorisation.
Claims and settlement
Claims are derived from recorded care, with every decision, adjustment and outstanding payment traceable.
Open connections
FHIR, laboratory messaging and DHIS2 integration keep working systems connected rather than replaced.
Care delivery
See how registration, consultation, laboratory, pharmacy, referrals and admissions contribute to one longitudinal record.
Coverage operations
Coverage attaches to an established person through separate eligibility, enrolment, status and verification stages. It never defines the person's identity or clinical record.
Designed for the conditions
Resilient by design. Accountable by default.
Offline
Offline capture is not a degraded mode, and offline status never turns uncertainty into ineligibility: necessary care proceeds.
Privacy
Every screen is built permission-first. A registration clerk sees no clinical content; a doctor sees no claims and no settlement.
Security
One database and one instance per customer. Isolation sits at the database boundary, not the query boundary.
Auditability
Every read of patient data and every change writes an append-only record: who, what, when, under which permission.
Next
Follow one person through the platform.
The journey page shows where identity, administrative coverage information and clinical care meet without becoming the same thing.