eClinicalWorks Integration

• If you are provider, who is a direct eCW customer you can reach out to your eCW contact

• If you are a vendor, you may want to first identify a provider partner using eCW who can sponsor the integration request. This is the most straightforward approach. You can also contact eCW about developer programs which may not require active customers.

Once in contact with eCW, you’ll often be required to sign a Business Associate Agreement (BAA) and provide an overview of your workflow to eCW, including:

• The main objectives and type of data you are looking to read or write (eg. demographics, order/results, scheduling and appointments, etc.)

• The direction of data flow between your system and eCW (eg. uni- or bi-directional data flow).

• Estimates of the volume and frequency of the data exchange (eg. real-time or daily batch processing).

The workflow information provided will help eCW guide you on the appropriate type of interface (eg. HL7v2 vs FHIR) they can support and provide the necessary implementation guides for development.

The implementation guide will contain information on:

• The data format and structure, often containing sample messages which can be used when developing in the Translator.

• The transport protocol used to exchange data and any authentication requirements.

  • HL7v2 is often exchanged using LLP or FTP.

  • FHIR API backend service integrations use the OAuth2.0 authentication.

If you haven’t already installed IguanaX, follow our Installation Procedures to get IguanaX setup in your environment.

Before you start, review the Getting Started to introduce yourself to IguanaX and building integrations. IguanaX includes many iNTERFACEWARE Collections with template components and libraries to help you get started with building different types of integrations and common interfacing tasks.

If you are building a HL7 interface exchanging data via LLP, get started with the:

• HL7 Server component to receive HL7 messages from eCW via LLP.

• HL7 Client component to send HL7 messages to eCW via LLP.

If you are building a FHIR interface with eCW, get started with the:

• Epic FHIR Adapter component to review the framework for building a FHIR integration.

• OAUTH Library can be leveraged to authenticate with the eCW Authorization Server.