by interface type
See our supported standards
IHE, or Integrating the Healthcare Enterprise, coordinates the use of many different standards by layering on the context of healthcare delivery. You can learn more from IHE.
Incoming Patient Demographics Query
In this scenario, an external system has a patient that it is attempting to match in an Epic system. The external system sends a subset of patient demographics and if the EMR can find a unique high-confidence match, it will return the matching patient. Epic software implements all transactions required in the IHE Technical Framework to support the IHE Patient Demographic Query HL7 V3 Profile as a Patient Demographics Consumer, and the IHE Cross-Community Patient Discovery Profile as a Responding Gateway (see integration statement).
Outgoing Patient Demographics Query
In this scenario, a patient presents to an Epic system, and a user needs to match the patient in an external system. The EMR will send a subset of patient demographics to the external system, which will respond with the patient(s) who match the query. The EMR will confirm the match, usually through the user, and then report back the user's actions. Epic implements all transactions required in the IHE Technical Framework to support the IHE Patient Demographic Query HL7 V3 Profile as a Patient Demographics Supplier, and the IHE Cross-Community Patient Discovery Profile as an Initiating Gateway (see integration statement).
Real-Time Location System (RTLS) Interface read the spec
This bi-directional HL7 v3 interface is used, generically, to track movement of a patient through a certain physical area. In Epic, this interface can be used to track patient movement to automate transfers, surgical case tracking events, and treatment team assignment. Current integrations include...
- Intelligent InSites - Operational Intelligence Platform
- STANLEY Healthcare - AeroScout MobileView
- Versus AdvantagesTM (ED, OR, Bed Management, Enterprise)
Epic's cardiology software implements IHE's Cardiac Catheterization Workflow Profile as an ADT Patient Registration actor, a Department System Scheduler/Order Filler actor (multi-modality procedure update option), an Order Placer, and a Performed Procedure Step Manager.
Epic's cardiology software implements IHE's Echocardiography Workflow Profile as an ADT Patient Registration actor, a Department System Scheduler/Order Filler actor (availability of PPS-referenced instances option), an Order Placer, and a Performed Procedure Step Manager.
Epic's cardiology software implements IHE's Stress Testing Workflow Profile as an ADT Patient Registration actor.
Implantable Device - Cardiac
Epic's cardiology software implements IHE's Implantable Device - Cardiac - Observation Profile as an Implantable Device - Cardiac - Consumer. It supports the OBX - Encapsulated PDF or Ref Pointer option and the PV1 - Patient Visit option.
Patient Information Reconciliation
Epic's cardiology and radiology software implement IHE's Patient Information Reconciliation Profile as an ADT Patient Registration actor, a Department System Scheduler/Order Filler actor, an Order Placer and a Performed Procedure Step Manager.
Epic's radiology software implements IHE's Patient Information Reconciliation Profile as an ADT Patient Registration actor, a Department System Scheduler/Order Filler actor, an Order Placer and a Performed Procedure Step Manager.
Clinical information is primarily exchanged among systems as "documents" - XML files that contain clinical information. Epic's EMR can consume any valid C-CDA or CDA document.
Clinical information is primarily exchanged among systems as "documents" - XML files that contain clinical information. Epic's EMR can create the following documents:
- HL7/ASTM CCD (HITSP C32 Implementation)
- HL7/IHE Consolidated CDA (CCD and Progress Notes Template)
Exchanging Clinical Documents
The process of exchanging clinical documents is handled through a series of messages exchanged via standards-based SOAP Web services. Because organizations that use Epic software are often the size of regional HIEs themselves, interoperability with the Epic EMR requires no centralized infrastructure. Instead, the EMR acts as a document repository itself for point-to-point queries. Specifically, the EMR supports IHE XCA and IHE XDS.b Query-Response. Current integrations include...
- Care Evolution
- Cerner, Cerner HIE
- CONNECT (DoD, VA, SSA)
- eHealth Data Solutions
- MDI Achieve
- No More Clipboard
- Optum Insight (Axolotl)
Sending Clinical Documents (Direct)
Epic's EMR supports document exchange via the Direct protocol. Documents sent from an Epic EMR via Direct follow the XDR/XDM option, in which structured documents are sent in the message with structured metadata. Similarly, Epic receives structured documents to file to the appropriate chart. External provider directories containing Direct addresses can be imported into the Epic EHR using a standard format.While Epic software supports the full SMTP+S/MIME stack, organizations using Epic can alternatively choose to delegate duties to an external HISP. Providers use the EHR to push data using Direct, and patients can use their portal to send structured clinical summaries to any arbitrary Direct endpoint with which the organization has established trust. Current integrations include...
Research Study Management and Enrollment read the spec
To support external Clinical Trial Management Systems, Epic supports two IHE profiles for exchange of research administrative information (see integration statement). The IHE Retrieve Protocol for Execution profile is used to create research studies in the EMR, associate patients to a study, and update the patient's enrollment status in the study. The Clinical Research Process Content profile enables the creation of billing grid definitions and additional study details. Current integrations include...
- Click Commerce eResearch Portal
- Forte Research Systems OnCore
- MDLogix CRMS
- National Cancer Institute C3PR
- UAMS AERS, UAMS Clara
- Velos eResearch
Outgoing Family Health History
This interface (also known as the HL7 Pedigree Interface) transmits family health histories, including diseases and conditions, from Epic’s EMR to another system. This is intended for linking genetic data, risk analysis, and clinical decision support.
Outgoing Cancer Reporting
This interface allows organizations using Epic to meet the optional Meaningful Use Stage 2 Objective to send cancer case information to cancer registries, when using Epic's oncology software. This integration uses the Direct protocol to send the information.
Epic can electronically request birth certificates from a birth registry by exchanging data using the IHE Retrieve Form for Data Capture and Clinical Research Document profiles to facilitate reporting to external registries. Epic can also push birth information to external registries using the Direct protocol.