Inside the Epic Integration Behind MedTalk AI's Canberra Health Services Deployment
Most AI scribes integrate with an EHR by exporting a note for someone to copy and paste in. That works for a solo GP clinic. It doesn't work inside a hospital running Epic, where clinical documentation has to land in the record through a certified, auditable path, or it introduces exactly the kind of risk a health system can't accept. Here's what that integration actually involves, based on how MedTalk AI was built into Canberra Health Services' Digital Health Record.
Why export-and-paste doesn’t clear the bar
ACT Health's evaluation of MedTalk AI wasn't primarily about transcription quality. It was about whether a platform existed that met the governance, security, and integration bar to run inside a government Epic based health system without introducing new clinical risk. A copy-paste workflow fails that test immediately: there's no reliable audit trail, no structural guarantee the note lands in the right place in the chart, and no way to certify the integration against Epic's own standards.
What the integration is built on
Epic FHIR R5 and SMART on FHIR
MedTalk AI integrates natively using Epic’s current FHIR standard and the SMART on FHIR framework, rather than a custom or proprietary connector that only works for one deployment.
Epic Vendor Partner status
MedTalk AI holds Epic Vendor Partner status, meaning the integration has been through Epic’s own certification path rather than being a self-declared or workaround integration.
HL7 standards based integration
Phase 1 of the Canberra Health Services deployment was built to HL7 standards, embedding MedTalk as part of the clinical record process rather than as a bolt-on tool sitting outside it.
Full audit trail by design
Consent prompts, transcription destruction after the report is generated, AI timestamp logging, and mandatory clinician sign-off are built into the architecture, not added after the fact.
Australian data sovereignty
100% of data residency runs across AWS and Azure Sydney/Melbourne regions, with ACSC Essential Eight aligned security controls (Cyber Safe standard) underneath the integration.
What it looks like in practice
Phase 1 of the deployment reached around 60 clinicians across multiple hospital based specialties in Canberra Health Services, moving beyond GP-style consults into acute and specialist care, where documentation is more complex and multi speaker sessions (like multi disciplinary team meetings) are common. The pilot was evaluated against efficiency and after-hours workload benchmarks, and clinicians saved an average of two hours of documentation time per day.
For a health system evaluating any AI vendor against an Epic environment, the questions worth asking are specific: is the integration FHIR native or a workaround, does the vendor hold certified partner status with your EHR, and is the audit trail (consent, data handling, sign-off) architected in from day one. Those answers are what separate a pilot that scales from one that stalls in procurement.