by interface type

See our supported standards


Microsoft's Component Object Model is used to drive tighter workflow integration between Microsoft-based software applications. You can learn more from Microsoft.


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...
  • Midmark
  • Mortara
  • Schiller
  • Spaulding
  • 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...
  • Midmark
  • Welch Allyn

Document Image Attachments

In this scenario, the user scans a document into an external document management system. The document is for an AP claim or CRM record. The DMS launches into the claim creation or CRM creation workflow in the EMR, as appropriate, and the scanned document is associated with the newly created record. For other types of scans, the DMS can launch Epic's Document Linker activity, which presents the user with the ability to link the scan to a patient, a referral, a benefit plan, an employer group, etc. Current integrations include...
  • Hyland OnBase
  • SunGard MACESS

Clinical Guidelines

This bidirectional interface is used for referral criteria review. It’s used by Epic customers that do utilization management on referrals as well as by Epic's case management software. Current integrations include...
  • MCG CareWeb QI
  • McKesson Care Enhance Review Manager featuring Interqual Guidelines