By Interface Type

IHE Profiles

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.

Epic maintains a set of IHE Integration statements for these profiles. If you are looking to see which technical options in each profile that Epic supports, see Epic’s integration statements.

Incoming Patient Discovery

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 Cross-Community Patient Discovery Profile as a Responding Gateway.

Outgoing Patient Discovery

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 Cross-Community Patient Discovery Profile as an Initiating Gateway.

Implantable Device - Cardiac read the specRead the technical specs

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.

Cross Community Access (XCA)

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...
  • ACS/Xerox
  • Agilex
  • Allscripts
  • Apenimed
  • Athena
  • Caradigm
  • Care Evolution
  • Cerner, Cerner HIE
  • Certify
  • CodoniX
  • Coldwater
  • CONNECT (DoD, VA, SSA)
  • Covisint
  • eClinicalWorks
  • eHealth Data Solutions
  • dbMotion
  • GE
  • Greenway
  • Harris
  • ICA
  • Intersystems
  • Inpriva
  • Magellan
  • MDI Achieve
  • MedFx
  • Medicity
  • MEDITECH
  • Mirth
  • MobileMD
  • NetSmart
  • NextGen
  • No More Clipboard
  • Optum Insight (Axolotl)
  • Orion
  • Qvera

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...
  • DataMotion
  • ehrDocs
  • MaxMD
  • MedAllies
  • Medicity
  • SureScripts

Research Study Management and Enrollment read the specRead the technical specs

To support external Clinical Trial Management Systems, Epic supports two IHE profiles for exchange of research administrative information. 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...
  • Bio-Optronics
  • Click Commerce eResearch Portal
  • Forte Research Systems OnCore
  • MDLogix CRMS
  • National Cancer Institute C3PR
  • UAMS AERS, UAMS Clara
  • Velos eResearch

Outgoing Cancer Reporting

This interface allows organizations using Epic to meet the Meaningful Use 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.

Birth Integration

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.