Registration & Identity

Establish a shared patient identity to support any patient-specific data exchange. Manage registration functions.

HL7v3

HL7v3 identity interfaces are typically used when two systems both maintain patient identities, and they are trying to establish whether a patient in one system matches a patient in the other. This exchange might occur, for example, between two clinics in the same community, or between two hospitals across the country. Unlike HL7v2 interfaces, HL7v3 interfaces are XML-based and messages are exchanged via Web services.

Outgoing interfaces refer to interfaces in which the EMR sends the message. Incoming interfaces refer to interfaces in which the EMR receives the message.

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 statements).

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 statements).

Research Study Management and Enrollment read the specRead the technical specs

To support external Clinical Trial Management Systems, Epic supports all transactions in the IHE Retrieve Protocol for Execution and Clinical Research Process Content profiles as a ProtocolExecutor and Content Consumer, respectively(see integration statements). These interfaces include the ability for a CTMS to create research study records in the EMR, associate patients to a study, update the patient's enrollment status in the study, and populate billing grid data. Current integrations include...
  • Bio-Optronics
  • Click Commerce eResearch Portal
  • DDOTS (Data Doctors Office Technology Systems) CREDIT
  • Forte Research Systems OnCore
  • heartbase ADT Interface
  • IBM Watson CTM
  • MDLogix CRMS
  • National Cancer Institute C3PR
  • UAMS AERS, UAMS Clara
  • Velos eResearch

Outgoing Death Registry Reporting IHE VRDR Profile

Conforms to the Medical Summary for Vital Records Death Reporting (MS-VRDR) content within the IHE VRDR Profile supplement (Trial Implementation October 27, 2015). The interface content is a Clinical Document (CDA) which contains the basic information for vital records death reporting, including procedures, problems and date/time of death.