Changelog

Users submitting support requests from the ZAP will now be directed to an updated support interface.

Starting today, updates to the Document tab make it easier to find the information you care about in Clinical Document Architecture (CDA) Documents. The tab is also re-organized so users can see the document type, author, and sections more easily.

We’ve updated how DocumentReference (DocRef) resources are generated to improve navigation between related DocRefs and encounters, and to ensure key fields are populated more consistently with meaningful clinical values.

Starting today, users of the Zus web app should find the experience of searching for patients from the patient list faster and more reliable.

Rather than subscribing patients to all ADT networks by default, we now assign patients to the strongest ADT network(s) available in their state, based on known coverage patterns and the active connections configured for your organization. This reduces redundant traffic and aligns subscriptions with the dominant ADT source in each region.

Understanding when something meaningful has happened in a patient’s care is key to delivering timely records. We’ve added two new ways of detecting that:

Continuity of Care Documents include a section called "Participants" that often includes useful information about a patient or other individuals related to the patient in some way.

We’ve enhanced our deduplication logic in the data pipeline for patient and observation resources.

We’ve updated our Intelligent Refresh engine to better support appointments booked on short notice. Previously, appointments created less than 48 hours in advance weren’t automatically prioritized for refresh. Now, they trigger an immediate refresh of EHR data, ensuring clinicians have the most up-to-date information no matter when the appointment was scheduled.

To better prioritize time-sensitive patient data updates such as those triggered by upcoming appointments or recent hospital visits, we’ve made infrastructure improvements that help prevent large bulk jobs from delaying other activity. This change ensures more consistent processing times for critical refreshes, even when high-volume jobs are in flight.