EHR Integrations General Concepts

All Zus EHR integrations consist of two core components:

An embedded UI that allows users to view the ZAP directly within the patient chart.
A data synchronization process that transfers data between the EHR and Zus.

Embedded UI Components

Many EHRs support a SMART on FHIR app launcher, which can be used to launch the ZAP directly from the patient chart. Developers can follow our embedding guide to build their own embedded ZAP. Several EHRs already offer native support for this integration.

All Zus EHR integrations assume a direct mapping between the EHR user and a Zus user. This ensures that all data access is both scoped and attributed to a specific end-user, preserving auditability and accountability. Many integrations support automatic provisioning of Zus users based on EHR user credentials, enabling a seamless experience for clinicians. However, in some cases, manual user provisioning in Zus may be required depending on the capabilities of the EHR.

Data Synchronization

Single Patient Backfill

All EHR integrations support a single patient backfill, which at a minimum loads patient demographics into Zus. Additional supported data types vary by EHR but often include a range of clinical data, as well as CCDA documents from which Zus extracts a wide array of discrete information.

Single patient backfills are rate-limited to once every 7 days and can be triggered when:

A patient is first loaded into Zus
The patient is enrolled in a Zus package
The ZAP is launched
Any time via API call

Automated Sync

Zus supports automated synchronization of various data types at different intervals, depending on the EHR. This may involve webhooks, polling, asynchronous nightly jobs, or other mechanisms.

Automated Enrollment

Zus supports automatic enrollment of patients into Zus packages across all EHRs. This feature is configured by the Zus team and enables patients to be enrolled as they are added to the EHR. It also allows for automatic unenrollment when patients are marked as inactive in the EHR.