Changelog

Builders querying the ZAP can now access a small set of foundational resources (e.g., Practitioner, Organization, etc.) from other Builders outside of the Designated Record Set if they are referenced by Designated Record Set resources for a shared patient. For example, a care team user viewing a patient’s ZAP can see who ordered a MedicationRequest from another Builder, as represented by a reference to a Practitioner resource in the other Builder. However, the user cannot query directly for the Practitioner resource. The Practitioner resource is only accessible as part of a query for the MedicationRequest resource. Learn more here.

📖 Provenance resources now included in Data Marts

In addition to launching our new website 🎉, we've reorganized our documentation to better reflect our focus on the Zus Aggregated Profile, or ZAP, as Zus' core product. Furthermore, we've revised our Quickstart Guide to make it even easier for new users to quickly get up and running creating patients, seeding external data, and accessing that data, all via Zus APIs.

New documentation is up! Learn how Zus thinks about data enrichment and how you can access enriched and normalized terminology for condition and medication activity resources here: https://docs.zushealth.com/docs/data-enrichment

🎉 Builders can now get a comprehensive picture of a patient's health from all data sources on Zus with a single API call to the Zus Aggregated Profile (ZAP) in this alpha release. Data sources include third party partner networks via the Patient History API, other Builders on Zus treating the same patient, and Zus-summarized and de-duplicated (Lens) information. Use this information to power patient onboarding, care coordination, care planning, and other critical workflows. See our documentation to learn more about how to leverage the ZAP. 🎉

Builders can now feed real-time medication events into a patient's Zus Aggregate Profile (ZAP). Once a patient is enrolled in our medication events feed, Zus will automatically capture new prescription activity and create the appropriate FHIR resources within their profile. Important events like missed refills, new medications, and new prescribers will be flagged in an additional 'notification type' field, and builders can optionally configure a webhook to receive a message each time a given FHIR resource is created or updated.

New Resource Summarization tags! The Zus Lens team is in the process of enriching medication activity (MedicationStatement, MedicationAdministration, MedicationDispense, and MedicationRequest) resources as well as condition resources to make sure they are universally coded and categorized where possible.

Zus releases the Active Medication Lens 🔍.

We've introduced a host of new features and enhancements in our FHIRplace application to make browsing FHIR resources in Zus easier than ever. Read on to learn more about what we've been up to this quarter.

📈 Builders can now export their data in Zus's Operational Data Store (ODS) in a transformed, columnar format to a SQL-compliant database for bulk analytic querying. Supported databases include Snowflake and BigQuery. For more information, see: https://docs.zushealth.com/docs/data-marts