Reference Architecture

Built for scale and interoperability

OPES Health OS is built on a layered architecture combining security, global interoperability, and local data sovereignty — engineered for African health facilities.

Layered model

OPES Health OS

Presentation Layer
Web portals · Mobile app · Analytics dashboards · Third-party integrations
Business Services Layer
Patient record · Hospital HIS · Laboratory · Pharmacy · Radiology · Maternity
Interoperability Layer
HL7 FHIR R4 · SNOMED CT · ICD-10/11 · DICOM · CDA · Open REST/JSON API
Health Identity Layer
OPESCare Health ID · Master Patient Index · CRVS · Cross-facility record matching
Data & Intelligence Layer
Clinical data warehouse · HMIS analytics · AI clinical decision support · MoH reporting
Infrastructure Layer
On-premise · Private cloud · Hybrid deployment · Cameroon data centres
Interoperability

Connected to global standards

OPES Health OS implements international health interoperability standards, enabling secure data exchange between facilities, partners, and government systems.

HL7 FHIR R4
Native FHIR API for clinical resource exchange — patients, observations, prescriptions, and reports.
ICD-10 / ICD-11
WHO-compliant diagnostic coding with automated ICD-11 transition pathways built in.
DICOM
Medical imaging management (radiology, ultrasound, CT) with integrated PACS-compatible storage.
Open REST API
Documented API (OpenAPI 3.0) for connecting third-party systems, government portals, and telemedicine apps.
SNOMED CT
Standardised clinical terminology for diagnoses, procedures, and observations.
HMIS / DHIS2
DHIS2-compatible exports for reporting to the Ministry of Health and development partners.
Health identity

One universal patient identifier across Africa

The OPESCare layer assigns every patient a unique digital identifier at their first point of contact with the health system. This identifier persists across consultations, inter-facility transfers, and years — eliminating duplicate records and identification errors.

Master Patient Index (MPI)
Cross-facility record matching
CRVS-compliant
Offline ID & degraded mode
Security

Security designed from the foundation

Every component of OPES Health OS is designed on Security by Design principles — end-to-end encryption, granular access control, and full audit trails.

AES-256 Encryption
Data at rest and in transit encrypted with AES-256 and TLS 1.3.
RBAC Access Control
Granular role-based permissions: clinician, admin, nurse, technician, auditor.
Full Audit Trail
Immutable logging of every action — who accessed what and when.
HIPAA/GDPR-aligned
Architecture aligned with HIPAA, GDPR, and Cameroonian health data law.
Deployment options

Deploy where your data must stay

On-Premise
Hosted on your own servers, within your facility or data centre. Full data control — ideal for general hospitals and public health networks.
Private Cloud Cameroon
Managed hosting in our Cameroon data centres. Data remains in-country, compliant with Ministry of Health requirements.
Hybrid
Combination of on-premise and cloud for multi-site networks — sensitive data stays local, analytics aggregated in the cloud.

Need a detailed technical overview?

Our solutions architects can walk you through the full OPES Health OS architecture and answer your technical questions.

Talk to an architect Security & compliance