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.
Clinical Reference Material
Epic's Active Guidelines activity allows providers to search clinical reference websites for information relevant to their patients. Searches are triggered from within the provider's workflow and are specific to the context of the medication, procedure, diagnosis, allergy, lab result, or symptom. Reference material can be further refined based on user, patient, or language. This is Epic's implementation of the InfoButton standard.
External Application Linking
The Epic EMR provides a robust framework for launching external applications via OASIS SAML 2.0’s Identity Provider-initiated use case with HTTP Post binding as well as the HL7 SMART on FHIR profile of the OAuth 2.0 authorization code grant type. The launch, because it is triggered from within the EMR, can provide simple contextual information based that is currently displayed in Epic. You can download a testing harness that will help you validate that your web application can be successfully embedded.
Outgoing Dialysis Updates to CMS
Sends Dialysis data to CMS from the Dialysis Module. Requires Nephrology license. This interface uses the XML message format.
Incoming Patient Care Device Alerts read the spec
Stores technical and physiological alert data from patient care devices such as physiological monitors and infusion pumps. This data is typically used for administrator-level reporting.
Incoming WCTP Push Notifications read the spec
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.