View on GitHubTrust you can Verify
Engineers, Researchers and Regulators can read exactly how Records, Consent and Payments are handled, instead of taking our word for it.
Open Source
The Code that Carries Care, Open to Everyone.
Heyrafiki is Open Source Mental Healthcare Infrastructure. When software carries something this private, the People, Practitioners and Institutions who depend on it should be able to read how it works.
Why the Rails are Open.
Interoperability by Default
Open code built on open healthcare standards means Hospitals, Insurers and Ministries integrate once, without vendor permission and without rebuilding what already works.
Infrastructure that Outlives Us
Rails for a Continent cannot depend on one company's survival. Open code can be run, forked and continued by the Institutions it serves, whatever happens to us.
Digital Public Goods
Built as a Digital Public Good.
Heyrafiki is designed to meet the Digital Public Goods Standard and to advance Good Health and Wellbeing, the third Sustainable Development Goal. Open code is how Infrastructure earns a place inside public health systems instead of beside them.
Open licence
An OSI-approved licence keeps the core inspectable, runnable and extendable.
Open standards
Clinical data on open healthcare standards (FHIR, ICD-10), aggregate reporting designed to align with national systems, DHIS2 included.
Privacy by design
Identity data separated from clinical data, Consent-first sharing and full audit logs, enforced in the architecture.
Do no harm by design
Crisis routes in every Screening flow, validated Instruments only, and drafts that never become records without a Practitioner's approval.
Open where Openness protects you.
Every component faces the same test: does opening this make People safer, or does it make attacking them easier? We publish the answer either way, so you always know which parts are open and why the rest are not.
What is Open
- Client SDKs and integration libraries
- Healthcare-standard adapters and protocol implementations
- The core rails for Records, Consent and Payments
- Assessment scoring, faithful to the published Instruments
What stays Closed, and Why
- Safety and Triage internals. Published thresholds become an evasion manual for the system protecting someone on their worst night.
- Anti-Fraud logic. A fraud model loses its power the day its rules are published, and fraud drains Care from the People it was funded for.
- Verification pipelines. Publishing the checklist would tell an impersonator exactly what to fake.
For Funders of Open Technology
If you back Open Technology for Public Benefit, let us talk.
Support for open rails compounds: every improvement reaches every Person, Program and Health System running on them. We start partnerships small, measure honestly and publish the results.