Curably Platform documentation
Technical references for HMOs, hospitals, pharmacies, NGOs, regulators, and integration partners deploying verified identity, encounter validation, and cross-institution data on the Curably Platform.
What Curably is
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.
Platform, not a point product
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.
Core pillars: Interoperability and Continuity of care. AI capabilities: Identity graph resolution, Encounter authenticity, Claims pre-check, Cross-network anomaly detection, Audit intelligence.
Read the full architecture breakdown in Platform architecture.
Documentation map
Getting started
Integrations
EHR integration
FHIR R4 and SMART on FHIR connectivity.
HMS / HIS integration
External hospital systems: OpenAPI, OAuth, claims, webhooks.
NHIA-style adapter
Scheme eligibility and claims/settlement exports for government partners.
Provider portal
Clinical workflows, intake, charting, and admin center.
Pharmacy integration
CuraRx dispensing, verification, and POS workflows.
Kiosk fleet
Check-in devices, offline queue, and fleet management.
Billing & payers
Encounter verification, claims prep, and HMO rails.
API reference
Security & governance
Environments
Production API base URL is issued after onboarding. Sandbox credentials are provisioned for pilot integrations (typically 60–90 days). All environments require TLS 1.2+ and organization-scoped credentials.
Getting started
Support
Integration support: support@letscura.com. Security and compliance questions: Security overview and contact form.