Clinical Information

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.

Outgoing Procedure Log Data read the specOutgoing Procedure Log Data technical specification

Sends data for configured case tracking events from a Cupid procedure log case to external ancillary systems mainly for reporting purposes. The messages contain data on the case including panels, staff, timeouts, implants, equipment, radiation, verifications, flowsheets, events, medications, and labs.
Current integrations include
  • General Data
  • LUMEDX
  • Philips
  • TSG Integrations

Outgoing Dialysis Updates to CMS read the specOutgoing Dialysis Updates to CMS technical specification

Sends Dialysis data to CMS from the Dialysis Module. Requires Nephrology license.
Current integrations include
  • CMS
  • South Dakota Department of Health

Incoming WCTP Push Notifications and Patient Care Device Alerts read the specIncoming WCTP Push Notifications and Patient Care Device Alerts technical specification

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.
Current integrations include
  • Ascom
  • Capsule Technologies
  • GlobeStar
  • Masimo
  • Philips
  • Spok
  • Vocera

Mobile App Integration read the specMobile App Integration technical specification

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.
Current integrations include
  • Sectra Liteview PACS
  • Voalte

Clinical Context Manager Integration read the specClinical Context Manager Integration technical specification

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.
Other systems can provide SSO integration into Epic applications like EpicWeb, EpicCare Link, Tapestry Link, or OutReach by passing user and optionally patient context.

CDS Hooks read the specCDS Hooks technical specification

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.

SAML 2.0 Reauthentication for Haiku and Canto EPCS read the specSAML 2.0 Reauthentication for Haiku and Canto EPCS technical specification

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.