HL7v3 clinical information interfaces are typically used between two clinical systems looking to exchange patient-specific information. 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.
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 statements
). 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.
The Active Guidelines (AGL) activity in the Epic EMR uses the HL7 InfoButton standard to allow clinicians to retrieve targeted information provided by third parties, specific to the context of the patient or clinical workflow. Rather than searching third party knowledge base, searches are performed automatically based off elements of the patient's chart like diagnoses or orders. The third party can also provide actionable links that queue up specific orders within the Epic EMR.
Current integrations include...
- Facts & Comparisons
- Pub Med
Users can create QRDA I documents from data in their Epic EMR. Each QRDA I document is specific to one patient and contains data pertinent to quality measure reporting. QRDA I documents are typically used by hospitals for quality measure submissions, and the format can also be used by individual providers. Many regulatory programs, including Meaningful Use, Core Measures, PQRS, Inpatient Quality Reporting, and ORYX Performance Measurement Reporting, accept QRDA I documents to satisfy their quality reporting requirements.
Users can create QRDA III documents from data in their Epic EMR. Each QRDA III document includes aggregated quality measurement data for a provider or group of providers, including the quality measures they are reporting on and their performance rate. QRDA III documents are typically used by providers for quality measure submission. Many regulatory programs, including Meaningful Use and PQRS, accept QRDA III documents to satisfy their quality reporting requirements.
Outgoing Clinical Trials Forms Submission
Continuity of Care form Data Capture Interface for Research Enrollment.
Incoming QRDA Documents Interface
Imports QRDA document information used to report on quality measures for regulatory programs. This interface supports ONC 2015 Edition Certification (for Meaningful Use).