1. Purpose of Integration
The Voice AI system connects to Epic as a SMART-on-FHIR application. It retrieves patient identity and relevant contextual information to enable:
- Verification of patient identity during inbound voice calls
- Lookup of patient demographics to support authentication questions
- Access to encounter context for routing, triage, or workflow automation
- Retrieval of care-team and proxy relationships for authorization checks
2. How Authentication Works
2.1 OAuth2 + SMART on FHIR
Sage Voice AI uses Epic's SMART-on-FHIR authorization model to securely request patient data. The system performs the following steps:
- Redirects or programmatically authenticates using OAuth 2.0
- Obtains access and refresh tokens
- Validates JSON Web Tokens (JWT) using Epic's published JWK sets
- Uses tokens to call the allowed FHIR endpoints
2.2 Patient Identity Matching
To confirm the identity of a caller, Voice AI uses Epic-supported patient identity APIs such as:
Patient.$match– Used to match demographics data (name, DOB, phone)Patient.Read– Used after match confirmation to retrieve official patient chart identity
These APIs allow the system to verify provided caller information against authoritative medical-record data.
3. FHIR APIs Used by Voice AI
The Voice AI platform uses the following FHIR R4 and legacy APIs (STU3/DSTU2 supported where needed):
3.1 Patient Identity & Demographics
Patient.$match– demographic matching for authenticationPatient.Read– core identity and demographic dataPatient.Search– used when the caller provides partial identifying infoPatient.$summary– used when Voice AI must access high-level patient summary context
3.2 Clinical & Visit Context
Encounter.Read– retrieves visit information used to route calls or assist with schedulingEncounter.Search– used to find the most recent visit context
3.3 Care Team & Provider Information
Practitioner.ReadPractitioner.SearchPractitionerRole.ReadPractitionerRole.Search
These allow Voice AI to answer questions such as "Who is my doctor?" or "Which clinic should I call?"
3.4 Related Persons & Authorization
RelatedPerson.Read– emergency contacts & proxiesRelatedPerson.Search– used for authorization validation
3.5 Coverage Information
Coverage.Read– insurance details used for eligibility questionsCoverage.Search– search-based lookup for multiple plans
4. Voice AI Authentication Flow
The Voice AI system builds patient authentication around Epic's demographic and identity endpoints.
Step-by-Step
- Caller provides identity information (name, DOB, phone number).
- Voice AI sends demographic data to
Patient.$match. - Epic returns candidate matches with confidence scores.
- Voice AI verifies key fields using
Patient.Read. - Optional: Proxy validation using
RelatedPerson.Readfor caregivers calling on behalf of patients. - Once authenticated, Voice AI may access encounters, providers, or coverage information to support the caller's need.
The system never stores authentication credentials or PHI outside the permitted session scope.
5. Security & Compliance
- SMART-on-FHIR v2 scopes
- OAuth 2.0 authorization code flow and backend-service flow where applicable
- JWT verification and token refresh handling
- Use of Epic-provided JWK Sets for signature validation
- No long-term PHI storage; all data ephemeral and request-scoped
6. Environments & Testing Process
The Voice AI platform follows Epic's required validation pipeline:
- Sandbox – early development and endpoint integration
- Non-Production – verification using test or synthetic data
- Production – deployment after Epic approval
7. Intended Functional Use Cases in Voice AI
- Identity verification during inbound calls
- Routing based on recent encounters or scheduled visits
- Provider identification ("Which doctor am I seeing?")
- Insurance lookup for benefits questions
- Proxy validation for caregivers calling on behalf of patients
- Access to patient-entered questionnaires for pre-visit automation
This document provides an overview of how Sage Voice AI integrates with Epic FHIR APIs for patient identity verification and clinical context access.
For technical questions or implementation support, please contact the Sage Care integration team.
Epic is a registered trademark of Epic Systems Corporation.