eClinicalWorks (eCW)

Overview

The Zus eCW integration consists of two main components:

Back-end data connection: Allows Zus to call the eCW FHIR API to retrieve patient demographics and clinical data as well as the eCW Bulk Data API to retrieve large patient groups for bulk loads.

Embedded ZAP UI: Enables viewing the ZAP directly within the eCW chart.

Data Flows

Single Patient Backfill

Patient demographics are retrieved from eCW using their certified FHIR API. This will occur via the Zus EHR backfill process when the ZAP is launched and can be triggered via API. Clinical data is currently being added to this process.

Bulk Data Retrieval

Patients can be synced automatically to Zus nightly using the eCW Registry Module. An eCW user must define a registry, make that available for bulk export, and send the group name to Zus. Once configured on the Zus side updates to these patient groups will be sent to Zus between 9p and 6a each night.

Embedded ZAP via SMART on FHIR

The ZAP will be launched in eCW using their SMART on FHIR app launcher. eCW users will automatically be provisioned in Zus with the Care Team User role and will be able to access the ZAP directly in the eCW patient chart.

Ad-hoc Data Retrieval

Patient demographics will be retrieved from eCW using their certified FHIR API. This will occur via the Zus EHR backfill process when the ZAP is launched and can be triggered via API.

Considerations

  • The eCW Registry Module defines static patient groups that must be updated directly in the Registry Module to reflect new patients.