Overview

The Epic EHR data store for Gemini Enterprise lets clinicians ask questions about patients in your organization's Epic EHR using natural language. When a question needs Epic data, Gemini Enterprise calls Epic's FHIR R4 APIs as the signed-in user and answers from the data that Epic returns.

The connector is read-only. Gemini Enterprise reads data from Epic when a question needs it, and the data store doesn't index or copy Epic data. Each user authorizes the connector with their own Epic account through SMART on FHIR, and Epic applies that user's access rights.

Supported actions

When the Epic EHR data store is enabled, end users can use natural language commands in Gemini Enterprise to perform the following actions. All actions read Epic EHR data and are enabled by default.

Action Description
Search Patients Finds patients by MRN, Epic patient ID, or family name and birth date.
Get Patient Returns one patient's demographic record, including contact details.
Search Observations Returns a patient's lab results, vital signs, social history, and other observations.
Search Conditions Returns a patient's problem list, encounter diagnoses, medical history, and health concerns.
Search Immunizations Returns a patient's immunization history.
Search Procedures Returns a patient's completed procedures and surgical history.
Search Medication Requests Returns a patient's medication orders and prescriptions.
Search Allergies Returns a patient's drug, food, and environmental allergies, with criticality and reactions.
Search Diagnostic Reports Returns a patient's lab panels and pathology, cardiology, and radiology reports.
Get Report Text Returns the result text of a diagnostic report.
Search Clinical Notes Returns a patient's progress notes, discharge summaries, history and physical notes, consult notes, and operative reports.
Get Note Text Returns the full text of a clinical note.
Search Encounters Returns a patient's hospital admissions, emergency department visits, and outpatient visits.
Search Service Requests Returns a patient's orders, referrals, consults, and scheduled procedures.
Search Coverage Returns a patient's insurance policies, coverage status, and payer.
Describe Epic Capabilities Returns the resources and search parameters that your Epic FHIR server supports.

Actions run with the permissions of the user who authorized the connector. A user can only read the records that they can already read in Epic.

Required permissions

When a user authorizes the connector, Gemini Enterprise requests the following SMART on FHIR scopes:

Scope Purpose
openid Identifies the signed-in user.
fhirUser Identifies the FHIR resource that represents the signed-in user.
offline_access Lets Gemini Enterprise refresh access without asking the user to sign in again.
user/Patient.read Reads patient records.
user/Observation.read Reads lab results, vital signs, and other observations.
user/Condition.read Reads problems and diagnoses.
user/MedicationRequest.read Reads medication orders.
user/AllergyIntolerance.read Reads allergies.
user/Encounter.read Reads encounters.
user/ServiceRequest.read Reads orders and referrals.
user/Coverage.read Reads insurance coverage.
user/DiagnosticReport.read Reads diagnostic reports.
user/DocumentReference.read Reads clinical notes.
user/Binary.read Reads the text of notes and reports.

For information about the Epic APIs that grant these scopes, see Enable the Epic APIs.

Limitations

The Epic EHR data store for Gemini Enterprise has the following limitations:

  • When creating a new app or adding a data store to an existing one, it's recommended to associate only one data store with actions belonging to a single connector type.
  • Enforcing a VPC Service Controls perimeter on existing Epic EHR data stores is not supported. To enforce VPC Service Controls, you must delete and recreate the data stores. For more information on VPC Service Controls and how to use actions after enabling VPC Service Controls, see Secure your app with VPC Service Controls.
  • The Epic EHR data store is supported only in the global, us, and eu locations.
  • Patient searches need an MRN, an Epic patient ID, or a family name and birth date. Epic returns no results for a name alone or a birth date alone.
  • Each search is for one patient. The connector can't list or browse patients or answer questions across patients.
  • Each search returns at most 50 records per page, and Epic doesn't report a total count. Answers that depend on many records might be incomplete.
  • The connector can't read PDF documents. Note and report text longer than about 20,000 characters is truncated.
  • The connector doesn't read devices and implants, care plans, goals, scheduled appointments, care teams, family history, medication administration, consents, patient flags, or imaging studies.
  • Epic doesn't return records that it withholds from the signed-in user.

What's next