Does Sunoh.ai Work With Epic?

On Epic's open FHIR APIs, per Sunoh's announcement; beyond that, Sunoh publishes little. The standard pattern for an Epic on FHIR scribe is: SMART on FHIR authorisation against the health system's Epic instance, reads of patient demographics, appointments and possibly problems and medications for context, and then one of several routes for the note itself. Those routes range from a FHIR DocumentReference write, which Epic supports for some app types, to an HL7 v2 interface built by the Epic team, to the clinician copying the reviewed note into the encounter. Sunoh does not say which it uses on Epic. Not published. Checked September 2026.

That gap is the whole diligence question. Ask Sunoh, in writing: does the note arrive in the Epic encounter automatically, and as what, a document, a note type, text in a section; does anything write discretely; and is there a SMART launch from within Hyperdrive or Haiku, or does the clinician open the Sunoh app separately. The answers determine whether your Epic team is enabling an app or building an interface, and those are different projects with different owners and timelines. Our EHR integration questions post covers the list.

Sunoh also offers a free browser extension, EHR Sync, that pushes notes into any browser based EHR. Epic's Hyperdrive is a browser based client, so it is worth asking whether any Epic deployment is actually running on the extension rather than the FHIR app. That would be a workaround, not the integration announced in 2024, and you should know which you are buying.

The scribe itself works as it does on eClinicalWorks: record the visit on the Sunoh mobile or web app, receive a transcript, a dialogue flow and a draft SOAP note, review and edit, and send the note to the EHR. Sunoh states that its draft captures labs, imaging, procedures, medication orders and follow up details. On eClinicalWorks those become pre filled orders; whether any of that is structured on Epic is not published, and the default assumption should be that orders are text in the note for the clinician to enter in Epic.

Compared with the embedded Epic scribes, the differences a clinician will notice are: a separate app to open, the patient selected in Sunoh rather than the note starting from the open Epic encounter, and the note arriving as a document or text rather than populating Epic's note template and problem list. Compared with Sunoh's price, those are the trade offs a smaller Epic organisation may be happy to make.

Measure it. Sunoh's published outcomes come from eClinicalWorks and athenahealth customers, not Epic ones. Time the full loop from end of visit to signed note in Epic for twenty encounters, and put that into the ROI calculator against your baseline. The ambient scribe use case page explains how to structure a pilot on Epic.

• App enablement. Your Epic team must review and enable the Sunoh app from fhir.epic.com, including the scopes it requests. Ask Sunoh for the exact list of FHIR resources and scopes.
• Write back path. If the note arrives by anything other than a FHIR write, your Epic team builds and owns the interface. Name the owner and get it on the interface team's queue early.
• Business associate agreement with Sunoh, covering audio and transcript storage on Azure, retention, model training and subprocessors. Sunoh lists the BAA as included in its price.
• Device policy. Capture is on a phone or web browser; mobile device management and lost device procedures cover recorded encounters.
• Epic governance. Most Epic organisations route third party apps through a technology or AI governance committee. The governance committee playbook sets out what that review should cover.
• Consent and state law. A recording notice consistent with your states; the healthcare AI law checker lists them.

The HIPAA and AI compliance page has the vendor questions in order.

Write back is the first, covered above, and it is the one to resolve before any pilot starts.

Evidence is the second. Sunoh's Epic integration is a 2024 announcement and a fhir.epic.com listing; we found no named Epic customer in Sunoh's public material as of September 2026. Ask for two Epic organisations live on the FHIR app for more than six months, and ask them how the note arrives.

Tier is the third. Sunoh is not a Showroom vendor and does not have the Epic partnership that the embedded scribes have. That affects roadmap, support escalation and how quickly a change on Epic's side is accommodated. For a health system it is a reason to compare Sunoh against the Showroom vendors on total cost rather than list price; the scribe comparison sets out who has which Epic tier.

Pricing is the fourth, and here Sunoh is unusually clear: 149 US dollars per user per month against a listed 199, month to month, BAA included, as listed in September 2026. Confirm whether an Epic deployment carries any implementation charge on top. Sunoh pricing covers the details.

• How does the note get into the Epic encounter: FHIR write, HL7 interface or clinician copy, and as what note type?
• Is there a SMART launch from Hyperdrive or Haiku, or does the clinician open Sunoh separately?
• Which FHIR resources and scopes does the app request?
• Is any Epic deployment running on the EHR Sync browser extension rather than the FHIR app?
• Which two Epic organisations can we call, and how long have they been live?
• Is there an implementation charge for Epic beyond the per user price, and is the 149 rate locked?
• Where are audio and transcripts stored, for how long, and do they train shared models?

Put the same list to the Showroom vendors you are comparing against; the HIPAA questions for AI vendors post covers the privacy half.

Sunoh on Epic is a price led option with an open platform integration whose write back path is not public. For a smaller Epic organisation, particularly one on a Community Connect arrangement where the host system controls the app list, it may be the most accessible scribe available, or it may be blocked entirely by the host's governance. For a health system, it is one of several and the embedded vendors have a structural advantage. Which case you are in decides the question.

Our vendor selection engagement establishes the write back path and Epic tier facts in writing, compares Sunoh against the embedded scribes on your encounters and your total cost, and takes the result through your governance committee. If the question is whether your Epic team has the capacity for any third party app right now, the AI readiness audit answers that first. No commissions from Sunoh, Epic or anyone else. Book a call.