By accepting, you will receive these cookies from open.epic.
Decline if you wish to use open.epic without these cookies.
Sending and receiving clinical data.
Web Services and Other Integrations
We've created other clinical integrations to support the use cases supplied by our organizations.
Sends Dialysis Data to CMS (by way of a Renal Healthcare HIE) from the Dialysis Module, per HIE specifications. Requires Nephrology license. Specifications are found https://qnetconfluence.cms.gov/display/ELDF/Documentation+Repository
Sends data for configured case tracking events from a Cupid procedure log case for the purpose of submitting data to external registries. Submissions to the NCDR CathPCI & NCDR ICD registries can be sent directly from Cupid, Epic's CVIS. The messages contain data on the case including panels, staff, timeouts, implants, equipment, radiation, verifications, flowsheets, events, medications, and labs.
Incoming WCTP Push Notifications and Patient Care Device Alerts
read the spec
This collection of interfaces receives alert messages to send push notifications to end users. Upon receiving, reading, or responding to an alert, response messages are sent back to the alert manager. They can also store technical and physiological alert data from patient care devices such as physiological monitors and infusion pumps.
Epic's mobile applications - Haiku, Canto, and Rover - can communicate with specialized clinical review applications like document or image viewers. This framework allows our applications to launch your app with context, making for a a smooth and seamless clinical experience for the user.
CCOW (formerly known as Clinical Context Object Workgroup) is a vendor-independent HL7 standard protocol designed to allow disparate clinical applications to synchronize data in real-time at the point of care. Epic can integrate as a participant with a third-party clinical context manager.
CDS Hooks is an HL7 standard for in-workflow, real-time, provider-facing decision support integration between Electronic Health Record systems and external Decision Support Services. A summary understanding of the specification is necessary for the discussion of state of Epic support for CDS Hooks, so check out the HL7 published specification and current draft specification. Epic recommends against using this feature for other purposes; if you need only a notification, we instead recommend using an event based interface.
Haiku and Canto, Epic's mobile apps for physicians on iOS and Android devices, support launching a web portal during e-prescribing controlled substances (EPCS) to verify the physician's identity with an EPCS-qualified identity provider (IdP). The IdP returns a valid SAML assertion to Haiku or Canto, which allows the physician to continue placing orders. This process follows the SP-initiated Web Browser SSO profile defined in the OASIS SAML 2.0 specification. The workflow is also supported in Rover, Epic's mobile app for nurses, on iOS devices only.
Epic software gives users the ability to export electronic health information in multiple formats depending on the use case. The following computable formats are available:
EHI Tables for complete electronic health information, in a tab-separated value (TSV) file format native to Epic. Refer to the EHI Tables technical specification for detailed information about what’s included in this export by default. A copy of the specification might also be included in the Full EHI Export package you receive. The TSV files might also come packaged with non-computable files that are referenced in a patient record, such as media files and rich text format notes.