Sending and receiving clinical data.
web services and more
We've created other clinical integrations to support the use cases supplied by our organizations.
External Decision Support Functionality
This family of APIs is used to provide external decision support to the clinician at the point of order entry. Possible uses include medical necessity checking or genomic analysis performed in an external system and used to inform better care in the EHR. Technical documentation for these APIs are available through our App Orchard program. Current integrations include...
- ACR Select
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.
Mobile App Integration read the spec
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
In addition to widely used HL7v2 Incoming Results interfaces, this family of APIs is used to integrate an ECG system directly into the outpatient clinical documentation system. Current integrations include...
- Welch Allyn
This is used to integrate a Spirometry system directly into the outpatient clinical documentation system using calls to vendor-specific proprietary APIs. We generally recommend HL7 standards-based exchanges over use of proprietary APIs for new integrations. Current integrations include...
- Welch Allyn
PC-based Vitals Integration
This interface is used to integrate real-time PC-based vitals machines in a clinic with the Epic EMR. Devices are used to record patient vitals and communicated to the device manufacturer's program. Vitals are then offered to the EMR and validated by the user before they are copied into the chart. Current integrations include...
- Midmark IQVitals
- Welch Allyn
This interface allows for tighter integration between Epic's Home Health product and third-party telephony vendors. The EMR exports patient information about scheduled home health visits and tasks that need to be performed as a part of the visit. The caregiver performs the visit and records his or her actions through the telephony system, which then triggers the information back to the Epic EMR for charging and clinical documentation.
External Application Linking
The Epic EMR provides a robust framework for launching external applications - desktop or web - via remote procedure call. The launch, because it is triggered from within the EMR, can provide dynamic contextual information based on the patient, visit, or order that is currently displayed in Epic.You can email us to receive a simple testing harness that will help you validate that your web application can be successfully embedded.