Platform architecture
How the Curably Platform layers identity, encounter verification, interoperability, and AI intelligence beneath program-specific rails.
Last updated June 2026
Infrastructure layer
The infrastructure layer that makes African healthcare function with intelligence — verifying identity, validating encounters, detecting fraud upstream, enabling data to move across institutions, and giving every care interaction a verified, longitudinal record.
What Curably is not
- A health identity company (too narrow)
- A fraud detection tool (a consequence, not the product)
- A coordination platform (wrong language)
- A B2C product
Institutions integrate at the platform layer. Fraud reduction, coordination, and longitudinal records are outcomes of verified infrastructure — not standalone product SKUs.
Core pillars
Interoperability
Identity, encounters, and clinical events move across HMOs, providers, pharmacies, and regulators through API-first, HL7 FHIR-compatible rails — without re-keying or institutional lock-in.
Continuity of care
Every verified interaction extends a longitudinal record institutions can trust at the next point of service — not a snapshot trapped in one EMR.
Technical implementation: FHIR R4 REST, SMART on FHIR OAuth2, org-scoped records API, consent-gated push targets. See EHR integration and REST API.
AI capabilities
All five capabilities run on platform infrastructure. They are not packaged as separate named products.
| Capability | Function | Primary consumers |
|---|---|---|
| Identity graph resolution | Canonical person records with duplicate and synthetic beneficiary detection across schemes. | Providers, pharmacies, HMOs |
| Encounter authenticity | Check-in, facility, and timestamp evidence tied to each billable care event. | Providers, pharmacies, HMOs |
| Claims pre-check | Verification rail that quarantines invalid submissions before adjudication. | HMOs, TPAs |
| Cross-network anomaly detection | Pattern signals across institutions — not single-claim forensic review. | Providers, pharmacies, HMOs |
| Audit intelligence | Regulator and program-integrity views over verified delivery, not reconstructed billing. | Regulators, program integrity |
Program rails
Vertical programs sit on the platform. Each rail inherits identity, consent, encounter verification, and interoperability without re-implementing them.
| Rail | Focus | Documentation |
|---|---|---|
| CuraLyfe | Chronic disease management | Product overview |
| CuraRx | Prescription and pharmacy verification | Product overview |
| CuraMama | Maternal health pathway coordination | Product overview |
- CuraLyfe — chronic disease pathways, adherence, population signals
- CuraRx — e-prescription verification, dispense evidence, pharmacy API (reference)
- CuraMama — maternal health coordination across facilities and community programs
Data flow
- Identity resolution — beneficiary matched to canonical Curably record at check-in (kiosk, provider portal, or API)
- Consent capture — scoped access granted per interaction; revocations halt outbound sync immediately
- Encounter evidence — visit start/close, facility, timestamp, and actor logged for billing integrity
- Record exchange — FHIR pull/push and records API under consent scopes
- Claims pre-check — invalid or unverified encounters quarantined before payer adjudication
Every step emits audit events. See Audit & compliance.