"The Version 3 Normative Edition represents a new approach to clinical information exchange based on a model driven methodology that produces messages and electronic documents expressed in XML syntax. The V3 specification is built around subject domains that provide storyboard descriptions, trigger events, interaction designs, domain object models derived from the RIM, hierarchical message descriptors (HMDs) and a prose description of each element." - HL7.org
Real-Time Location System (RTLS) Interface
read the spec
This bi-directional HL7 v3 interface is leveraged to integrate Epic with Real-Time Locating Systems (RTLS) for tracking location of patients, staff, and medical devices within your facility. We leverage this data to automate and enhance many workflows, such as automatically documenting operating room wheels in and out times, and facilitating medical device association.
Current integrations include...
- Infinite Leap
- Intelligent InSites - Operational Intelligence Platform
- STANLEY Healthcare - AeroScout MobileView
- Midmark RTLS (fka Versus Technology),
Clinical information is primarily exchanged among systems as "documents" - XML files that contain clinical information. Epic's EMR can consume any valid C-CDA or CDA document.
Clinical information is primarily exchanged among systems as "documents" - XML files that contain clinical information. Epic's EMR can create the following documents:
- HL7/ASTM CCD (HITSP C32 Implementation)
- HL7/IHE Consolidated CDA (CCD and Progress Notes Template)
Outgoing Family Health History
This interface follows the HL7 Pedigree standard to transmit 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.
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).
Outgoing BSN Verification Query
read the spec
BSN or Burgerservicenummer verification is required in the Netherlands. There are two types of BSN queries: BSN request, and BSN verification. Using provided demographic data, a BSN request will retrieve and store the BSN for a patient, whereas the BSN verification serves to validate that the BSN a user has stored to the patient record is correct.
Data Exchange with DBC Onderhoud Grouper
Sends Diagnosis Behandeling Combinatie (DBC) and charge information from Epic to the VECOZO Declaratie Grouper. The Grouper retrieves a billable product and billing code (DBC-zorgproduct).
Outgoing eRx Services Request and Response
Kanta stores the active and historical medication list for every patient receiving care in Finland. This HL7 V3 interface communicates with the prescription center any time a user makes changes to a patient’s prescriptions, as well as when a user needs to reconcile a patient’s existing prescriptions into Epic.
Outgoing Child Protection Information Sharing NHS Query
This interface sends queries to the SPINE for the NHS Digital's Child Protection - Information Sharing project. The SPINE responds whether a child is in Child Protection, a child who is a Looked After Child, or an expectant mother of an unborn child who will be under Child Protection.