EHR Integrations

All Zus EHR integrations have 2 main components (see Embedding the ZAP for details on how this is implemented):

The Zus Aggregated Profile (ZAP) user interface is embedded within the patient chart.
The Zus platform is able to connect to the EHR API and pull at least patient demographics.

Embedded ZAP in the Patient Chart

EHRs such as Athena and eClinicalWorks are able to use the SMART on FHIR app launcher to embed the ZAP in the patient chart. Other EHRs may have proprietary integrations that are implemented following the guidelines here. All of these integrations launch the ZAP with both patient and user context. The user context is used to authenticate the user and, if necessary, provision a Care Team User account in Zus. The patient context is used to trigger an ad-hoc backfill of patient data from the EHR to the Zus platform.

Backend Data Connection

All Zus EHR partners offer API access to patient demographics and various clinical data. The scope and frequency of data pulled varies by EHR, but the bare minimum to access the ZAP is patient demographics which are necessary to match up the patient records in the EHR with those in Zus. The Zus API has a BackfillRequest endpoint that can be used to trigger an ad-hoc backfill, or synchronization, of patient data from the EHR into the Zus platform. This endpoint is invoked when the ZAP is launched and may be automated further depending on the EHR. Automated data synchronization, and access to further clinical data, varies by EHR and may use methods such as webhooks, data polling, etc.