Operations

Exchange information to help with the business of running a healthcare delivery organization.

Other Systems

These interfaces are used to keep the data stored in the EMR in sync with other operational software used in the healthcare delivery organization or to provide additional functionality for system users.

In outgoing interfaces, the referral information is being sent to an external system.

Interface Engines

Although Epic software can be interfaced point-to-point with external systems, interface engines can reduce implementation time and help avoid message customization costs. Interface engines also lower the number of interfaces that are required to support the healthcare delivery ecosystem. Current integrations include...
  • BizTalk (Microsoft)
  • Camel
  • Cloverleaf (Infor Global Solutions)
  • Corepoint Integration Engine
  • DataExchange (TIBCO)
  • Datagate (Sun)
  • e-Biz Impact (Sybase)
  • eGate Integrator (Sun)
  • eLink (Eclipsys)
  • Ensemble (InterSystems)
  • HL7Connect
  • Iatrics Engine
  • IGUANA
  • iWay
  • Instrument Manager (Data Innovations)
  • JBoss Fuse
  • JCAPS (Sun)
  • MD Link
  • MITS (Interlink)
  • MQSI (IBM)
  • Mirth (WebReach)
  • OPENLink (Siemens)
  • Rhapsody (Orion Health)
  • Summit Express Connect
  • Viaduct
  • WebSphere Message Broker (IBM)

Release of Information Copy Vendor Integration read the specRead the technical specs

Some organizations use a copy vendor’s system to complete some portion of their Release of Information workflow. Your organizations can use existing Epic functionality to integrate Epic and the copy vendor system and reduce duplicate work. Depending on your organization’s workflows and your copy vendor, you can utilize a text file and file transfer workflow or a web service workflow to expedite this process for your staff and patients. Current integrations include...
  • CIOX & Prism (fka HealthPort and IOD)
  • MRO

Web Service Engines

Although Epic software comes with its own web service library and engine, Interconnect, an additional integration layer on top of these web services can be useful for orchestration, performance, and interpretation. Current integrations include...
  • MuleSoft

Incoming Location and Department Information read the specRead the technical specs

This HL7v2 interface is used to automate synchronization of the logical facility structure within the EMR with an external system for facility management. Specifically, this interface updates records and contact information for hospital and clinic locations and departments. To this point, this integration has been completed only with custom in-house systems previously developed by our organizations.

Tissue Tracking

The Food and Drug Administration (FDA) and The Joint Commission have extensive requirements in place surrounding the documentation of tissue implants. Health care organizations that use tissue implants need to track every movement of the implant within the organization. Epic's tissue integration solution was designed to eliminate double documentation of tissue placement in the operating room. Current integrations include...
  • Cardinal Health Inventory Management Solutions (formerly Wavemark)
  • Champion Healthcare Technologies: UDITracker, GraftTracker
  • LPIT Solutions Tissue TrackCore

Incoming Deficiency Tracking read the specRead the technical specs

An HIM deficiency represents incomplete work by a provider. This interface will make an organization's deficiency tracking more robust by integrating information captured by external systems. Deficiencies can be created directly in the EMR for tracking, or they can be configured to run through native functionality to determine aging and delinquency statuses. Current integrations include...
  • Cerner
  • ImageNow
  • M*Modal
  • McKesson Horizon Patient Folder
  • Nuance EXText (Dictaphone), Nuance EXVoice (Dictaphone)

Computer-Telephony Integration explore the specExplore the technical specs

This functionality is used to integrate Epic with an organization's phone system. When your system receives an incoming communication about a patient, this service can open and populate an appropriate activity in Epic's desktop software for the user who receives the call. Epic can also interface with your web dialer to begin and log outgoing calls, based on your custom schema. Technical support for customization on this integration is available through our App Orchard program. Current integrations include...
  • Cisco (outgoing calls)

Environmental Services explore the specExplore the technical specs

This family of web services is used to integrate Epic's environmental services with an exteral call system. Current integrations include...
  • Vocera

System Health

This family of web services returns information about database server health. Callers can retrieve more information about the types of resources and logs available, as well as any current alerts. We'll provide you with the specs for this interface at the time we've identified a mutual customer.

Incoming Asynchronous Error Management read the specRead the technical specs

Receives asynchronous application acknowledgements in response to any outgoing HL7v2 message sent from Bridges.

Fax Integration

This functionality is used to integrate Epic with an organization’s faxing solution. Epic software can currently be set up for integrated faxing with the following vendors in addition to any fax solutions that use Common Alerting Protocol (CAP) standard XML. Example documents for our CAP XML integration can be provided upon request. For solutions not using CAP XML, integration with individual vendors is developed by Epic at the request of Epic customers. Current integrations include...
  • Biscom
  • Concord Fax
  • Faxination
  • FaxPress
  • Genifax
  • GFI FaxMaker
  • InterFAX
  • Passport
  • RightFax
  • Streem
  • XMediusFAX

Output Management Integration

All Epic community members use the Epic Print Service (EPS) to print documents generated from their instance of Epic. The output management web service can be used to integrate third-party products with EPS, allowing the third-party product to collect jobs exiting EPS that are bound for physical printer devices. Current integrations include...
  • LRS

Print Job Status Updates

This web service can be used to update the status that appears for a print job in Epic. Current integrations include...
  • LRS