Sage Care Logo
bg-wrapper-mobile

Sage Voice AI – Epic FHIR Integration Overview

This document describes how Sage Voice AI interacts with Epic's FHIR and SMART-on-FHIR APIs to authenticate patients, retrieve identity information, and access clinical context necessary for automated patient-facing workflows. All sensitive credentials and environment-specific identifiers have been intentionally omitted.

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:

  1. Redirects or programmatically authenticates using OAuth 2.0
  2. Obtains access and refresh tokens
  3. Validates JSON Web Tokens (JWT) using Epic's published JWK sets
  4. 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 authentication
  • Patient.Read – core identity and demographic data
  • Patient.Search – used when the caller provides partial identifying info
  • Patient.$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 scheduling
  • Encounter.Search – used to find the most recent visit context

3.3 Care Team & Provider Information

  • Practitioner.Read
  • Practitioner.Search
  • PractitionerRole.Read
  • PractitionerRole.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 & proxies
  • RelatedPerson.Search – used for authorization validation

3.5 Coverage Information

  • Coverage.Read – insurance details used for eligibility questions
  • Coverage.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

  1. Caller provides identity information (name, DOB, phone number).
  2. Voice AI sends demographic data to Patient.$match.
  3. Epic returns candidate matches with confidence scores.
  4. Voice AI verifies key fields using Patient.Read.
  5. Optional: Proxy validation using RelatedPerson.Read for caregivers calling on behalf of patients.
  6. 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:

  1. Sandbox – early development and endpoint integration
  2. Non-Production – verification using test or synthetic data
  3. 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.