Enrolling & Refreshing
To obtain data from Zus data partners, customers can enroll patients in a Zus subscription, or alternatively trigger one-time queries of the networks.
Zus subscriptions
By enrolling patients in subscriptions, customers can ensure that the ZAP is kept up-to-date via a combination of Zus's intelligent refresh and notification-based partners.
Our subscriptions may include the following data types:
| Data type | Availability |
|---|---|
| EHR networks | Traditionally EHR networks are query-based, however Zus intelligent refresh will use event-based triggers to proactively refresh the ZAP. |
| Pharmacy-sourced medication data | Pharmacy data is primarily query-based, however Zus intelligent refresh use event-based triggers to proactively refresh the ZAP. We also refresh medication history on a regular basis to ensure it is up-to-date. |
| Admission notifications (ADT) | By definition, admission notifications are proactive in nature and "pushed" to the ZAP. |
| Lab notifications | Upon enrollment in a subscription, the patient's 2-year lab history is pulled. Any new results are then "pushed" to the ZAP. |
Enrolling via API
The zap-data-subscriptions API, available in the Zus Postman collection, can be used to manage enrollment for your patient population.
Available actions include:
- List available packages
- Enroll a patient in a package
- View current enrollments
- Un-enroll a patient
- Update a patient's enrollment
Note: A patient may be enrolled in 1 package at a time. Creating an enrolled patient a second time will result in an error. To change a patient's package, unenroll the patient and then enroll them in a new package.
Enrolling via Integration
Zus can automatically enroll patients into packages for clients who are leveraging integrations with our EHR partners. Read more about those automated enrollments here.
ℹ️ Optimized queries
Zus optimizes its targeting and lookback logic on the EHR networks by package and use case, for both subscriptions and one-time queries. We may:
- Apply logic to cap the number of documents we retrieve from any single responding organization
- Target intelligent refresh queries to specific organizations depending on the refresh reason
These limits help us avoid overwhelming organizations with repetitive queries and downloads, while also limiting the number of redundant or duplicative documents end users need to sift through.
Updated 7 days ago