Registration & Identity

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


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.

Research Study Management and Enrollment read the specResearch Study Management and Enrollment technical specification

These interfaces integrate with an external Clinical Research Management system to facilitate research workflows. They 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
  • Advarra
  • Baylor Scott and White Health
  • Click Commerce
  • EDGE
  • IBM
  • MDLogix
  • National Cancer Institute
  • Oracle
  • Precision Genetics
  • SAP
  • SignalPath
  • University of Arkansas for Medical Sciences
  • Vanderbilt University
  • Velos