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.

Remember that user filters are retained across patient charts, so if a user selects this filter in one patient chart and moves to another the filter will remain.

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

Documents

• Indicate the Title, Author, Date Retrieved, Encounter Type, and Encounter Dates when available
• These appear in the Table of Contents for each CCD

Document Component

• The type of Document is now more obvious - an icon and type is listed in the second column of the table.
• The Encounter Date, Date Retrieved, and Author are now visible within the table
• The type of Document is a new filter - so users can filter by type: CDA, PDF, or Image - JPEG, PNG, TIFF.
• Some TIFF Images may have rendered incorrectly as black boxes - this is now fixed and all Images render correctly.

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.

When using the ZAP in EHRs, users can select more than one condition at a time to add to the chart. Users can also select more than one condition to dismiss.

When the condition is finished syncing with the patient chart or is successfully dismissed, a checkmark appears next to the row. The checkmark to confirm addition to the patient chart will remain green until the user leaves the ZAP to indicate what conditions were added during a given session.

In some circumstances, Zus may not be able to add the condition to the chart. If this occurs, a red error message will appear to alert the user.

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.

Instead, packages will include a boolean value for adtFeeds:true/false and labFeeds: true/false. Please contact support if you have any questions on subscription providers for your patients.

Before:

 "attributes": {
                "meta": {
                    "adtFeeds": true,
                    "labFeeds": true,
                    
                    "subscriptionProviders": [
                        "bamboo",
                        "collective",
                        "connectn",
                        "eden",
                        "floridahie",
                        "ghhconnect",
                        "manifestmedex",
                        "quest",
                        "schio"
                    ]
                },
                "name": "ZAP Pro"

After:

 "attributes": {
                "meta": {
                    "adtFeeds": true,
                    "labFeeds": true
                },
                "name": "ZAP Pro"

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.

This update includes no changes to features or functionality currently in use by Zus customers. Noted changes in unused behavior are available here.

This new capability statement is effective as of today, and our API documentation and Postman workspace have been updated to reflect the new capability statement. Documentation for the new FHIR APIs is accessible from the left side bar of our API Reference, under "FHIR REST APIs".

Please review our updated capability statement to ensure you have the most current information. If you have any questions or require further clarification, please do not hesitate to reach out to our support team.

We appreciate your continued partnership and trust in our services. Thank you for your attention to this update.

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

The Transitions page provides a list of patients that have had recent encounters at hospitals or emergency rooms.

Read more about it here.

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.

Changes to different schemas

A Zus data mart customer today can have up to three different schemas available to them:

• [CUSTOMER_NAME]: The Zus legacy schema, available to select customers - will be retired on October 15, 2024
• [CUSTOMER_NAME]_STAGING: The Zus preview relational schema, available to select customers - will be retired on October 15, 2024
• [CUSTOMER_NAME]_RELATIONAL: The Zus relational schema, generally available to all customers - will continue to be supported through future versioning

For more information on the features on the relational schema and how to access it, please refer to our changelog post introducing the relational schema.

What this means for customers

To ensure a smooth transition, we recommend the following steps during the transition period:

1. Familiarize yourself with the relational schema: Review the updated documentation to understand the enhancements and changes.
2. Test the relational schema: Use your development or testing environments to ensure you have access to the relational schema.
3. Update your systems: Modify any scripts, integrations, or workflows that rely on the legacy schemas to be compatible with the relational schema.

If you encounter any issues or have questions during the transition, our support team is available to assist you. Please reach out to us at [email protected].

Future of versioning of data marts

Zus will update the relational schema to keep up with customer needs and data quality best practices, but will ensure that changes to an existing version of the schema are non-breaking.

If breaking changes are needed, they will be introduced in a new schema version. Each version will be supported for a minimum of 9 months, and customers will be given at least 60 days to transition to a new version once it is made generally available. Zus reserves the right to introduce a breaking change without notice if it impacts an unused feature of the data mart.

Stay tuned for updates and detailed release notes with each new version. We are committed to providing the best experience and ensuring seamless transitions.

❓

What is a breaking change?

A breaking change in a data mart schema disrupts existing functionality or requires users to alter how they interact with the data mart. These changes can impact data querying, processing, or interpretation, necessitating adjustments to reports, dashboards, or applications relying on the schema.

Examples of breaking changes include:

• Schema modifications:
  • Changing the name of an existing column or table
  • Removing an existing table or column
• Data type changes: Altering the data type of an existing column (e.g., from integer to string)
• Constraint changes:
  • Modifying or removing primary keys
  • Modifying or removing foreign key relationships
  • Adding or removing unique constraints

Note: Adding a column or table or reordering existing columns within a table does not constitute a breaking change.

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.

The legacy Pro package contains a recurring refresh for all enrolled patients. Based on feedback from network respondents about the unsustainability of this volume, we are shifting legacy customers to our latest package, which relies exclusively on Intelligent Refresh.

Both the legacy and current ZAP Pro packages use the same Intelligent Refresh logic, described here. We will retain this logic and are committed to building on it over time to give you the freshest patient data at the moment when it is most actionable.

Please reach out to Zus Support if you have any questions or concerns.

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.

Zus Data Mart customers may wish to update any queries filtering where data_source = 'bamboohealth'to where data_source IN ('bamboohealth', 'bamboo-health)in order to include a complete history of Bamboo encounters.