Does Suki AI Work With Epic?

Suki Assistant reads the schedule and patient context from Epic through the vendor programme's interfaces, records the encounter in the Suki app, and writes the generated note into the Epic encounter, where the clinician reviews and signs it in Hyperspace. Pre-charting, which summarises the chart before the visit, uses the same read path. Suki Inside removes the separate app: the clinician starts recording from the encounter in Haiku, and the note appears in Epic for review on the desktop.

What is not published is the interface inventory at a site, meaning which FHIR resources, which Epic security points, and whether any HL7 v2 feed is involved for the schedule. These are the things your Epic analyst needs before they can size the work, and Suki provides them during scoping. Ask for the technical specification before the contract. Our integration questions guide lists the rest.

Suki also publishes a platform for other vendors to build on, and some Epic sites encounter Suki inside a partner product rather than directly. If that is your route, the Epic integration is still Suki's, but the contract and support line are the partner's. Check who you call when it breaks.

As listed on the vendor's site in September 2026: ambient note generation, pre-charting, and sign-off inside Haiku and Hyperspace; ICD-10 coding suggestions as part of the assistant; and the ability to switch between Suki Inside and Suki Assistant depending on the setting. Order entry and AI dictation within Epic are marked as coming soon. If either of those is why you are buying, get a dated commitment in the contract rather than a roadmap slide.

The documentation loop is the low risk feature and the one to measure first: note turnaround, after hours charting, and how many clinicians are still using the tool at ninety days. Our AI medical scribe use case page sets out the metrics, and the ROI calculator turns them into a number. Coding suggestions should go through the same compliance sampling you would apply to any coding aid.

• The vendor programme client for Suki in your Epic instance, which is an integration request through your own change process.
• Security review and the business associate agreement, with audio retention, subprocessors and model training settled in writing. See the HIPAA and AI page.
• For Suki Inside, Epic's ambient security points and the Haiku version floor.
• Note template mapping, including which sections receive generated text.
• Mobile device management for the Suki app or for Haiku, and microphone permissions on personal phones.
• A test plan with named clinicians in each setting you are deploying to.

The time it takes is set by your queue, not Suki's. Ask how many integration requests are ahead of this one before you promise clinicians a date. We size that queue in an AI readiness audit.

The first gap is the two product problem. Clinicians who like the embedded Suki Inside experience for clinic may still need Suki Assistant for inpatient rounds, which means two workflows to train and support. Ask whether the Toolbox build will cover inpatient, and when.

The second is the coming soon list. Dictation and order entry inside Epic are core to Suki's original identity, and their absence from the Epic build in September 2026 is worth noting if your clinicians expect them.

The third is pricing. Suki sells a per clinician subscription with pricing on request; nothing is published. Our Suki pricing page sets out what buyers report and the scribe pricing comparison puts it beside Abridge, Dragon Copilot, Ambience and Nabla, all of which are also embedded in Epic.

• Which product are we buying for which setting, Suki Inside or Suki Assistant, and what are the Epic and Haiku version floors for each?
• Exactly what is written back, into which note sections, and what happens to the pre-charting summary after the visit?
• When will dictation and order entry be available inside Epic, and is that date in the contract?
• 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?
• Which reference customers run our Epic release, and can we speak to them without the vendor present?

Our vendor HIPAA question list covers the compliance items in more depth.

Suki is a reasonable choice on Epic, especially for groups that want one vendor across several EHRs, since it is also native on athenahealth, Oracle Health and MEDITECH. The risk is buying on the strength of the embedded demo and discovering that half your clinicians live in the other workflow. An independent review tests both products on your encounters, confirms the version floors against your actual Epic release, and prices the result against the embedded alternatives. We take no vendor commissions.

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