VoiceboxMD for EHR Vendors
Your customers want ambient AI documentation. Building it is years of speech and clinical NLP work plus a permanent model bill. Offer them VoiceboxMD instead. It already works inside your product, and a deeper integration is a conversation, not a procurement cycle.
Why EHR Vendors Talk to Us
Documentation burden is the complaint that follows every EHR demo, and it is not a problem the EHR caused or can easily fix. Ambient AI is the answer practices are asking for by name. Very few platform vendors can justify building it, and the ones who try discover that the model bill never stops.
Your users are already asking
Ambient AI documentation is the most requested category in clinical software right now. Practices evaluating a new EHR ask whether it has an AI scribe, and the honest answer for most vendors is a roadmap item. Offering VoiceboxMD answers it today.
You do not have to build it
Speech recognition tuned to 100,000+ medical terms, speaker separation, note structuring and billing code extraction represent years of work and a permanent model bill. Partnering costs you none of that engineering and none of the ongoing inference cost.
It works before you write any code
VoiceboxMD types at the cursor, so it already works inside your product for any customer who installs it. A partnership makes that deeper and official, but nothing is blocked while the conversation happens.
Three Paths, Priced in Engineering Effort
Most integration pages lead with the deepest option, which is also the most expensive, and lose you on the first screen. Here is the honest version, cheapest first. The first row is live right now and asks nothing of your team.
| Path | What happens | Your effort |
|---|---|---|
| Cursor injection | Live today. Works in any EHR, web or desktop, with no cooperation from you. | Nothing |
| Signed webhook | You accept the finished note as JSON at one endpoint you own, with a token you issue. | About a day |
| Direct write to the chart | The note is written into the record over FHIR, attributed to the clinician who dictated it. | A sprint, with us |
Detail on all three is on the EHR integration page. The v1 payload is published on the note format page, the DocumentReference mapping and scope list on SMART on FHIR, and PHI handling on security and HIPAA.
What Your Users Get
A structured note, not a transcript
Notes arrive as sections rather than a wall of text: HPI, review of systems, physical exam, and assessment and plan, in SOAP or H&P shape. That is what makes them mappable into your fields instead of dumped into one free-text box.
Billing codes with the note
Suggested codes are extracted from the encounter alongside the note, and superbill generation is available on the Premium plan. Coding is where practices feel documentation pain in revenue terms, not just in time.
Both workflows, one subscription
Ambient comprehension for long conversational visits and real-time dictation for focused ones. Most clinicians want both, and most ambient-only tools force the practice to buy a second product for the visits where dictating is faster.
Compliance handled
A signed Business Associate Agreement is included on every plan at no extra cost, with AES-256 encryption in transit and at rest. Recordings are not used to train models. Your security review starts from a defensible position.
How This Usually Goes
1. A short technical call
What your customers use, what your API can already do, and which of the three integration paths fits. Usually thirty minutes, and it is often clear inside ten which path is right.
2. A pilot practice
One real practice on your platform, using VoiceboxMD end to end. Real notes, real workflow, before anybody builds anything. This is where integration assumptions get corrected cheaply.
3. Deeper integration, if it earns it
Webhook or direct chart write, scoped against what the pilot showed. We do this with a small number of partners at a time, deliberately, because the first few shape the contract everyone else inherits.
4. Listed and supported
Your platform appears as a supported integration, your users select it at signup, and support paths are agreed so a documentation problem does not arrive at your help desk with no context.
Tell Us What You Are Building
Which platform, roughly how many providers, and what your customers are asking for. A technical evaluator gets a technical reply, not a sales sequence.
EHR Integration, Frequently Asked Questions
Does my EHR need an API for VoiceboxMD to work?
No. VoiceboxMD types at the cursor, exactly as a clinician would, so it works in any EHR that accepts typed input. That covers web-based and installed systems alike, and it requires no API, no integration project and no IT ticket. An API only becomes relevant for the deeper paths, where the note is delivered into the chart programmatically instead of typed.
What does a partnership cost us?
There is no fee to become a supported integration. Your customers subscribe to VoiceboxMD directly, from $49 per provider per month for dictation and $139 for ambient comprehension, with a 7-day free trial and no annual contract. Commercial arrangements including referral and reseller terms are discussed case by case.
Who owns the customer relationship?
By default the practice buys VoiceboxMD from us and we support them directly, which means you carry no billing, no seat management and no first-line support for the documentation product. Where a vendor would rather bundle it into their own subscription, that is a conversation worth having early because it changes the commercial shape.
How is patient data handled?
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. Full detail is available for security review before any technical work starts.
Can we see it working before committing anything?
Yes, and we would rather you did. VoiceboxMD works inside your product today through cursor injection, so a pilot practice can run the full workflow with no engineering on your side. Every partnership we take on starts this way, because a real encounter surfaces integration questions that a specification never does.
How many integrations are you taking on?
A small number at a time. The first partners shape the note contract and the delivery model that later integrations inherit, so they get disproportionate influence over how this works and disproportionate attention while it is built.
Offer your users an AI scribe this quarter.
It already works in your product. The rest is a conversation about how deep to go.
Talk to us