DeepScribe Inside Epic Haiku: How Deep Is the Integration?

From the vendor's description, three parts. A read path over Epic's interfaces for the schedule, demographics and chart context that DeepScribe uses for pre-charting and to ground the note. A capture path inside Haiku or Canto, so the recording device is the phone or tablet already running Epic. A write path that places the note into your templates, using SmartData elements where configured, and pushes coding suggestions alongside. The vendor's Customization Studio sits on top, letting the organisation define specialty and note type structures that map to existing Epic templates.

Whether the write path is a document level drop or a section level SmartData write matters for clinicians, because it decides whether they edit inside their normal note or paste from a block. DeepScribe's material implies section level mapping through SmartData; confirm it against your own templates during a pilot. Our integration questions guide lists the other things to pin down.

Not published: the interface inventory at a site, the Epic and Haiku version floors, and the encryption and retention specifics beyond a general statement of AES-256 and HIPAA compliance. All of these should be in the technical specification your analyst receives before contract.

Note generation by specialty and note type, mapped to your templates. Chart context pulled forward, including labs and imaging, so the draft can reference them. Coding suggestions synced to the encounter. The vendor cites 2.2 hours saved per clinician per day, a 99.92 percent note approval rating and 89 percent clinician adoption; these are vendor figures from its own customer base and should be treated as a claim to test, not a benchmark. Your own pilot should measure note turnaround, after hours charting and retention at ninety days, as set out on the AI medical scribe use case page.

The coding sync deserves the same scrutiny as it does for any scribe. Suggestions that flow to the encounter change what your billing team sees, and your compliance officer should sample them before they are relied on for claims. Our governance committee playbook covers how to stage that decision, and the ROI calculator turns the time saving claim into a number you can check.

• The vendor programme client in your Epic instance, raised through your integration request process.
• Security review and the business associate agreement, covering audio retention, subprocessors and model training. The HIPAA and AI page sets out what to insist on.
• SmartData element and template mapping for each specialty in scope, done jointly with DeepScribe's Customization Studio.
• Coding workflow design: whether suggestions go to a coder queue or the encounter, and how they are sampled.
• Mobile device management for Haiku and Canto, including microphone permissions on personal devices.
• A test plan with named clinicians, and a change control slot.

DeepScribe historically sold strongly to specialty groups and ambulatory practices. If you are a smaller Epic group on a hosted instance, the first item may sit with your host, and their queue sets the date. We size that queue in an AI readiness audit.

The first is the Toolbox question above. Buyers comparing DeepScribe with Ambience, Nabla and Suki will find those three have announced Epic Toolbox designations for ambient voice recognition and DeepScribe, on its own site, has not. That may be a marketing omission or a real difference in build path; either way, get it in writing.

The second is the reliance on vendor stated metrics. A 99.92 percent approval rate is a measure of clinicians clicking sign, not of edit distance or of errors caught later. Ask for the definition and for the audit method behind it.

The third is pricing, which is on request with nothing published. Our DeepScribe pricing page sets out what buyers report, and the AI medical scribe comparison puts DeepScribe beside the Epic embedded field, including Abridge and Dragon Copilot.

• Is DeepScribe H.E. built on Epic's ambient module under a Toolbox designation, or on a vendor programme client, and what are the Epic, Haiku and Canto version floors?
• Is the note written at section level through SmartData or as a whole document, and can we see it against our own templates before signing?
• Can coding sync be disabled by user class or routed to a coder queue, and what audit trail exists?
• How are the 2.2 hours, 99.92 percent and 89 percent figures measured, and over what population?
• Where is audio processed and stored, for how long, and is any of it used to train shared models? Put it in the BAA.
• What is the per clinician price at our volume, the minimum term, and the exit terms if adoption stalls?

Our vendor HIPAA question list extends the compliance items.

DeepScribe's Epic integration is real and its specialty depth is a genuine strength for orthopaedics, oncology and other groups with long, structured notes. The open questions are about build path and about metrics, and both are the kind of thing a vendor answers differently to an independent reviewer than to a prospect. We confirm the build against your Epic release, test note quality on your encounters, and compare price against the rest of the Epic field. We take no vendor commissions.

Our vendor selection service runs that comparison. Book a call and bring your Epic release and your specialty mix.