Bring your clinical software into Heidi.
Build one connector and every clinic on your system can use Heidi with their schedule, patients and notes. Build it to the spec, or send us your API docs and Heidi builds it for you.
What clinicians get
- Their day in HeidiToday's appointments from your system, scoped to the signed-in clinician.
- The right patient, first timeSessions start from an appointment with the patient already identified.
- Pre-chartingAllergies, medications, problems and recent notes, before the consult.
- Notes written backThe clinician-approved note lands on the patient's record in your system.
Three ways in
Every route carries the same operations and goes through the same review.
- REST APIPlain HTTPS endpoints in any web framework. The route most vendors take.REST binding
- MCP serverA remote MCP server exposing the Heidi tools. Ideal if you already ship MCP for agents.Specification
- No codeSend us your docsNo build on your side. Heidi writes and hosts the connector against your sandbox.Apply
From application to live
- Step 1ApplyTell us about your product. We reply with sandbox details.
- Step 2BuildBuild to the spec, or let Heidi build from your API docs.
- Step 3ValidateWe check the connector with you against the specification.
- Step 4Go liveHeidi reviews it, then clinics switch it on in Settings.
Connectors are in preview. The transport (REST or MCP) and the submission process may change before general availability. We will give connector authors notice before any breaking change.
Who can build one
Anyone. EMR and PMS vendors, practice groups with an in-house system, or a clinic's one-person IT team. If your system has an API or a database, you can build a connector. Every connector goes through Heidi's review before clinics can switch it on.
Connectors are open in every region, including Australia and New Zealand.
Operations
REST and MCP connectors carry the same operations:
| Tool | Purpose |
|---|---|
heidi_get_connector_info | Identify the connector and the practice behind a key |
heidi_list_practitioners | Let each clinician pick themselves during setup |
heidi_list_appointments | Show a clinician's appointments |
heidi_search_patients / heidi_get_patient | Find and read patients |
heidi_push_note | Write an approved note back to the record |
heidi_get_patient_context (optional) | Pre-chart from history |
heidi_upload_document (optional) | Attach letters and PDFs |
Heidi's agents can also use your connector: "find Margaret Hughes' last visit", "write this letter to her record". Every write waits for the clinician's approval.
How clinics connect
- You issue each clinic a connector key, the same way you issue API access today.
- In Heidi, the clinic opens Settings → Connectors, picks your connector, pastes the key and selects their practitioner.
- Heidi calls your connector with that key over HTTPS.
Get started
- Apply: tell us about your product by email. We work closely with partners to set the connector up.
- Specification: operations, shapes, auth, errors and the REST binding
- Tool connectors: already have an MCP server, e.g. for billing? Offer its tools to Heidi's agent as they are
- Testing: the conformance validator
- Submitting: review and compliance checks
Have API docs but no engineering time? Apply and say "send Heidi our docs": we build and host the connector for you.