Versions Compared

Old Version 4

changes.mady.by.user Aryn Wiebe

Saved on

compared with

New Version 5

changes.mady.by.user Aryn Wiebe

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
title2) Obtain the appropriate eCW implementation guide

This information 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 OAuth2.0 JWT Assertionthe OAuth2.0 authentication.

Expand
title3) Install IguanaX

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

Expand
title4) Use components to build your integration workflow with eCW

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.