To better support customers conducting common population health analyses on Zus data marts, we have published a query library. This query library contains links to a public GitHub repo populated with SQL code compatible with the current data mart relational schema.

Beginning November 5, an updated view of Patient Contact Information will be available in the ZAP. Here are some highlights to look forward to:

Users can now filter to view only Conditions that are associated with a Hierarchical Condition Category (HCC) Code in the ZAP. By selecting this filter, the list of conditions shows only those with an associated HCC, as indicated by the blue icon in each condition row.

Starting today, there are several new improvements to viewing and interacting with Documents in the ZAP.

As a part of our ongoing efforts to reduce duplicate alerts for hospitalizations, patients already receiving ADT messages through an HIE within the PointClickCare network will no longer be connected to the Collective Medical ADT feed by default. We do not anticipate any reduction in facility coverage for these alerts, but if you have any questions or concerns with this change, please don’t hesitate to reach out.

Starting today, ZAP users can select more than one condition to add to the patient chart.

The individual ADT/Lab providers a given patient will be subscribed to can vary based on factors like geographic location and additional contracting requirements. To avoid any confusion moving forward, the response to GET https://api.zusapi.com/zap-data-subscriptions/packages will no longer include asubscriptionProvidersarray for each package.

As part of an initiative to optimize performance of the Zus platform to better support customers leveraging the Zus Aggregated Profile, we are updating our FHIR platform capability statement.

Starting today, the previously titled "Hospitalizations Page" in the Zus Web Application is called "Transitions."

To improve and streamline our services, Zus will retire non-relational data mart schemas on October 15, 2024. This change will transition all customers to the new, more usable and performant relational schema.