Trust you can verify
When you tell a Practitioner the thing you have never said out loud, you are trusting more than a Person. You are trusting a system: where the Note lives, who holds the keys, what the Insurer sees, and what your Employer never will.
A privacy policy matters, but it should not be the only thing an institution can inspect. Heyrafiki publishes its REST API description, SDK source, command line, developer documentation and executable conformance benchmark. An Engineer, Researcher or Regulator can examine the public boundary before deciding how to integrate.
Published rules beat private promises
- For People: The documentation states what each integration may request and keeps private Care outside public developer tooling.
- For Practitioners: Integrators use documented resources and Webhooks rather than depending on a private interface, which keeps a Practice connected to systems it already uses.
- For Researchers and Clinicians: Each public Check names its Instrument, version, scoring method and source. The assurance benchmark publishes versioned fixtures, schemas and a runner another team can reproduce.
- For Developers: The public OpenAPI definition and released JavaScript source give teams a concrete starting point; additional language clients follow the same conformance suite as they are released.
- For the Sector: A Clinic, Insurer or Ministry can evaluate the same documented API and conformance evidence before an integration begins.
Open Infrastructure compounds
The Internet, the Web and modern payments reached across institutions because shared standards let many teams build compatible systems. Public interfaces compound in the same way: each careful implementation makes the surrounding ecosystem easier to connect.
Mental Healthcare needs a shared foundation: one interoperable layer for Care, Conversations, Benefits and Payments that can outlive any single implementation, including ours.
Contribute
Read the API before you trust anything we say about it. Run the benchmark, try an SDK and tell us where the public boundary is incomplete.
The Platform itself stays private, and that is deliberate. A companion post explains which parts, and why keeping them closed is what keeps the open parts safe.
