Epic voice‑agent playbook

A new playbook making the rounds in digital health lays out a five-day plan for wiring voice agents into hospital record systems through standard application programming interfaces and Fast Healthcare Interoperability Resources, the data format used to move clinical information between apps. (open.epic.com, fhir.hl7.org) The basic plumbing already exists. Epic publishes public Fast Healthcare Interoperability Resources specifications through Epic on FHIR, and Oracle Health’s Millennium platform publishes Fast Healthcare Interoperability Resources Release 4 application programming interfaces for authorized users. (fhir.epic.com, docs.oracle.com) In practice, a voice agent is usually a software assistant that listens, turns speech into text, and then reads or writes only the fields it is allowed to touch inside the electronic health record. Epic says its public interfaces are a subset of its broader interoperability tools, and Oracle says its Fast Healthcare Interoperability Resources application programming interfaces return JavaScript Object Notation over encrypted web connections. (open.epic.com, fhir.epic.com, docs.oracle.com) That is why guides like this focus less on speech models than on launch rules, permissions, and workflow design. Epic’s developer materials point builders to SMART on FHIR-style app launch and endpoint discovery, which determine which clinician, patient, and encounter context an app can see. (fhir.epic.com, open.epic.com, engineering.cerner.com) The timing is not accidental. Hospitals are trying to cut documentation work at the same time large record vendors and cloud companies are pushing ambient documentation products directly into clinician workflows. (epic.com, healthcareitnews.com, oracle.com) Microsoft’s Nuance unit said in January 2024 that Dragon Ambient eXperience Copilot was generally available inside Epic, and Oracle said on March 4, 2025 that its Clinical AI Agent was available across more than 30 specialty areas and had reduced physician documentation time by 30%. (healthcareitnews.com, oracle.com) The burden these tools target is well documented. A 2024 systematic review in the *Journal of General Internal Medicine* said documentation burden is frequently cited as a contributor to clinician burnout, and the federal Agency for Healthcare Research and Quality said physician literature most often links that burden to stress, burnout, and electronic health record workload. (pmc.ncbi.nlm.nih.gov, effectivehealthcare.ahrq.gov) The catch is that “integration” often means more than getting data in and out. Epic says its public materials cover only part of what customers can use, and Oracle’s documentation stresses that access is limited to data a registered user is authorized to see, which turns governance and role-based access into product decisions, not just engineering tasks. (fhir.epic.com, docs.oracle.com) Federal rules are also tightening around artificial intelligence in health information technology. The Office of the National Coordinator’s Health Data, Technology, and Interoperability 1 final rule took effect on February 8, 2024 and added algorithm transparency requirements for predictive decision support in certified health information technology. (healthit.gov, federalregister.gov) So the appeal of a five-day playbook is not that hospitals can deploy a clinical voice agent in one workweek. It is that the shortest path still runs through standards, permissions, testing sandboxes, and a narrow first use case, because that is how these systems were built to connect. (fhir.epic.com, open.epic.com, docs.oracle.com)