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 Epic system sends the message. Incoming interfaces refer to interfaces in which the Epic system receives the message.

Outgoing Death Registry Reporting IHE VRDR Profile read the specRead the technical specs

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.

Research Study Management and Enrollment read the specRead the technical specs

These interfaces integrate with an external Clinical Research Management system to facilitate research workflows. Current functionality can create or update research study records, associate patients to a study, update the patient's enrollment status in the study, and receive study billing grid information. These interfaces follow the IHE - Retrieve Protocol for Execution (RPE) implementation, IHE - Clinical Research Process Content Profile (CRPC), HL7 Study Participation, and HL7 Study Design.
Current integrations include...
  • Bio-Optronics
  • Click Commerce
  • DDOTS
  • Forte Research Systems
  • IBM
  • MDLogix
  • National Cancer Institute
  • Oracle
  • Precision Genetics
  • SignalPath
  • UAMS
  • Vanderbilt University
  • Velos