EHR Integration
How a finished VoiceboxMD note reaches a chart, in three paths, cheapest first. The first one is live today and asks nothing of your engineering team. The other two are measured in days and sprints, not quarters.
Start From What Already Works
Before discussing any integration it is worth being clear that VoiceboxMD works inside your product right now, for any customer who installs it, with no cooperation from you at all. That is not a limitation to apologise for. It is why a pilot can start before a contract does.
It types where the clinician is typing
VoiceboxMD places text at the cursor, the same way a keyboard does. If the field accepts typing, it accepts a VoiceboxMD note. That covers browser-based charts, installed Windows clients and remote desktop sessions alike.
No API, no IT ticket, no project
Because nothing is integrated, nothing has to be approved. A practice on your platform can be dictating the same afternoon they subscribe, which is why this path is the default and why it stays available even after a deeper integration ships.
The limits are real
Typed text lands in whichever field has focus, so it cannot target discrete fields, cannot attach structured data, and cannot confirm the write succeeded. Those three gaps are exactly what the deeper paths close.
Going Deeper, When It Earns It
The reason to integrate properly is the three gaps above: discrete fields, structured data, and knowing the note actually landed. Here is what closing them costs, honestly.
Signed webhook, about a day of work
You expose one endpoint and issue us a token. When a clinician finalizes a note, we POST it as JSON, signed, with retries. No OAuth server, no FHIR server, no marketplace review. For most small and mid-size platforms this is the whole integration, and it is the path we would suggest starting with.
Direct write to the chart, a sprint with us
For platforms with a FHIR API, the note is written into the record as a document attributed to the clinician who dictated it, so your audit log stays truthful and the note is signed where it should be. This is built with partners rather than self-serve, because the mapping between our sections and your fields is the part that actually takes the time.
Linking a user, either way
Both paths need to know that a VoiceboxMD clinician is a specific user on your platform. That is a one-time link the clinician performs once, and then it is invisible. We will walk through the options against whatever your platform already supports.
What Arrives at Your End
The same note travels every path. It is the durable part of this, and it is structured on purpose: a wall of transcript text is not something you can map into a chart.
| Field | What it carries |
|---|---|
| Sections | HPI, review of systems, physical exam, assessment and plan, as discrete fields |
| Format | SOAP or H&P shape, or a custom template the practice defines |
| Codes | Suggested billing codes extracted from the encounter, with the note |
| Provenance | Recording mode, duration, and draft or finalized state |
| Attribution | The clinician who dictated it, so your audit trail stays truthful |
The full structure and the v1 wire format are on the note format page, the DocumentReference mapping and scope list are on SMART on FHIR, and how the encounter audio is handled is on security and HIPAA.
The fastest way to size this is a thirty minute technical call. Bring what your API already does and we will tell you which path fits.
Talk to usStart the Conversation
Which platform, what your API can already do, and what your customers are asking for. A technical evaluator gets a technical reply.
Integration Questions, Answered
How does VoiceboxMD work with an EHR that has no API?
It types at the cursor. VoiceboxMD runs alongside the chart and places the finished text into whichever field the clinician has focused, exactly as a keyboard would. No API is involved, which is why it works in every EHR including installed and remote-desktop systems, and why a practice can start the same day without their vendor being involved.
What does the note look like when you send it to us?
Structured, not a transcript. The note arrives as discrete sections covering HPI, review of systems, physical exam, and assessment and plan, in SOAP or H&P shape or against a template the practice defines, together with suggested billing codes and provenance describing how it was captured. Sections are what make a note mappable into your fields rather than dumped into one free-text box.
What is the smallest possible integration?
One HTTP endpoint. You accept a signed JSON POST containing the finished note and a token you issued, and you decide what to do with it. Most teams scope that at about a day. Everything beyond it, including direct chart write over FHIR, is optional and can come later without changing what you built first.
Do you support SMART on FHIR?
Direct chart write is delivered as a partner engagement rather than a self-serve public API, and the delivery mechanism is agreed against what your platform already exposes. If you have a FHIR API and an authorization server, that is the shortest version of this conversation. Tell us what you have and we will tell you plainly what the work looks like.
Who is the note attributed to?
The clinician who dictated it. That matters more than it sounds: a note written into a chart by a generic service account is a medico-legal problem, not an integration detail. Where the platform supports per-user authorization, the write is performed with the clinician’s own delegated permission so your audit log reflects reality.
How is PHI handled in transit?
VoiceboxMD operates under a signed Business Associate Agreement, included on every plan at no additional cost. Audio and transcripts are encrypted with AES-256 in transit and at rest, and recordings are not used to train models. Detail sufficient for a security review is available before any technical work begins.
Can we test without exposing real patients?
Yes. Nothing in an evaluation requires production PHI, and we would not ask for it. Early conversations run against synthetic encounters, and the pilot step uses a real practice only once both sides are satisfied the workflow holds.
One endpoint is a real integration.
Start with what works today, go deeper when it earns it.
Talk to us