Epic is the dominant EHR platform in US healthcare. Many large health systems run on Epic, but an often-overlooked segment of Epic's user base is independent outpatient practices that adopted Epic for its brand recognition, broad specialist connectivity, and care coordination capabilities. For these practices, ambient documentation tools that integrate with Epic via the SMART on FHIR standard represent the most seamless path to deploying ambient AI in their existing workflow.
This article is written for administrators and physicians at Epic-using outpatient practices who are evaluating ambient documentation tools. It covers how the Epic SMART on FHIR integration works, what it enables and what it doesn't, and what to verify before going live.
SMART on FHIR: what it means in practice
SMART on FHIR (Substitutable Medical Applications, Reusable Technologies on Fast Healthcare Interoperability Resources) is an open standard that allows third-party applications to connect to EHRs and read or write patient data. Epic's App Orchard provides a marketplace of third-party applications that have been vetted for SMART on FHIR compatibility with Epic's platform.
For ambient documentation, SMART on FHIR integration means several things: the ambient tool can read patient context from the Epic session (who the patient is, the visit type, relevant problem list information), and the generated note can be written back to Epic in the physician's note editor - appearing as a pre-populated draft rather than arriving in a separate application that requires copy-paste.
This is the critical functional requirement. If an ambient documentation tool at an Epic practice delivers notes into a third-party interface that the physician then transfers to Epic, the workflow is meaningfully worse than a fully integrated one. Physicians tolerate this initially but abandon it over time. Full push-to-Epic note delivery is the baseline for any integration worth deploying.
The authentication workflow
Under SMART on FHIR, the ambient application authenticates through the physician's existing Epic session rather than requiring a separate login. The physician is already logged into Epic; the ambient tool is launched within that session via a link or embedded application frame, inheriting the authentication context.
This matters for physician adoption. Separate login credentials for a documentation tool - a separate username and password that must be entered at the start of each clinic day, or a separate authentication step before each visit - are consistently cited as a friction point that discourages use. Single-sign-on through the existing Epic session removes that friction.
Verify this with any vendor before deploying: does the ambient tool require a separate login, or does it authenticate through the Epic session? The answer should be the latter for any modern SMART on FHIR integration.
Note format and template alignment
Epic uses note templates that practices configure according to their specialty and documentation preferences. A primary care practice might have a standard office visit note template with specific sections and required fields. A behavioral health practice will have different templates. An internal medicine practice doing pre-operative assessments uses different structures than a family medicine practice doing well-child visits.
When an ambient tool pushes a generated note to Epic, the note needs to land in the right template. If the ambient tool generates a generic SOAP note that doesn't align with the Epic template the practice uses, the physician's editing task becomes larger - not just correcting clinical content, but restructuring the note format.
Ask vendors specifically how they handle template alignment for your specialty and note types. The better implementations allow the practice to configure which Epic note template receives generated notes and ensure that the section structure of the generated note matches the template's sections.
Medication list and order capture
One of the more sophisticated capabilities of well-integrated ambient tools is capturing medication changes and new orders that the physician discussed during the visit. When a physician says during a visit "we're going to add lisinopril 10mg daily," an integrated ambient tool can pre-populate a medication order in Epic rather than just documenting the plan in the note text.
This capability varies significantly across vendors and depends on the level of FHIR integration scope the vendor has established with Epic. Not all ambient tools have write access to the medication or order modules - they may have read access to context and write access to notes, but the richer clinical data write capabilities require deeper integration that not every tool has implemented.
If medication capture and order pre-population are important to your practice's workflow, verify specifically what write permissions the vendor's Epic integration includes. Don't assume that "Epic integration" means all capabilities are available - integration scope varies.
Implementation steps for Epic practices
Deploying an ambient documentation tool at an Epic practice follows a reasonably standard sequence, though the specifics depend on whether the practice manages its own Epic instance or accesses Epic through a hosted environment managed by a health system.
For practices on independent Epic instances: the practice's IT contact or Epic administrator needs to install the ambient tool as a SMART on FHIR application through the Epic App Orchard. The vendor should provide an activation code or installation guide for this step. Configuration includes which user roles have access to the application and which visit types it is enabled for.
For practices accessing Epic through a health system instance: the practice typically cannot install third-party applications independently. The health system's Epic team must enable the application at the system level. This adds a procurement and approval step that can take weeks or months. Practices in this situation should involve their health system's IT department early in the vendor evaluation process rather than late.
Either way, the vendor should provide dedicated implementation support for the Epic integration setup - not just documentation but a named contact who can assist with configuration questions. Epic integrations occasionally produce unexpected behavior during setup that requires vendor-side troubleshooting, and having a responsive contact makes a significant difference in time-to-live.
Verification before going live
Before the first physician uses the integration in a live patient visit, run through a test workflow: have the physician start a test encounter, run the ambient tool, generate a draft note, and verify that it appears correctly in the Epic note editor in the right template format. Confirm that the physician can edit and finalize the note in Epic's standard workflow without any additional steps.
Test the authentication flow with the actual EHR login credentials the physician will use in clinic, not an IT administrator account with elevated permissions. Integration errors that don't appear with admin-level access often surface with standard clinician permissions.