Assistant API (MCP server)
A standards-based Model Context Protocol server lets assistants and partner apps work with a patient's record through one interface. OAuth 2.1 sign-in; every call runs as the patient and only ever touches their own data.
For developers & health ecosystem partners
One documented integration surface for practices, pharmacies, payers and digital-health builders. Every method below is live today — and every one is gated by the patient's explicit consent.
A standards-based Model Context Protocol server lets assistants and partner apps work with a patient's record through one interface. OAuth 2.1 sign-in; every call runs as the patient and only ever touches their own data.
A practice's records system pushes conditions, allergies, immunizations or lab results straight to the patient for review. Scoped per-practitioner, per-patient tokens; nothing changes the patient's profile until they accept it.
Receive a patient's check-in at your front desk, resolve SMART Health Links, and verify SMART Health Cards — standards-based, QR-friendly, and testable end to end with fictional patients.
Patients mint purpose-scoped, expiring links to their FHIR bundle or International Patient Summary. US Core 6.1.0 / 7.0.0 profiles; our IPS export passes the ONC Inferno IPS single-bundle test.
There is no organisation-wide key that reads everybody. Patients approve each connection, can see exactly what was shared and with whom, and can revoke access at any time. Partner access is scoped, expiring and audited — consent is the integration contract.
Tell us about your organisation and what you want to build. We will help you pick the right integration method and set up a sandbox test with fictional patients.
Tell us about your organization and workflow. Please don’t include patient names, records or health information.
Your health profile. Wherever life takes you.