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.
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.
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.
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.
On September 1, 2024, we will be transitioning customers that signed order forms for a subscription package before December 15, 2023, from the legacy Pro package onto our latest ZAP Pro Intelligent Refresh package. There is no action required from customers.
To better align with our standard naming convention for third party data sources, resources generated from Bamboo Health ADTs created after July 1st, 2024 list a data source of bamboo-health. Resources created prior to 7/1 will continue to list the previous bamboohealth source value.