Oct 29, 2025: Document Table Updates
We’ve made several improvements to the Documents table to make it easier to find and understand document types and contents.
We’ve made several improvements to the Documents table to make it easier to find and understand document types and contents.
We’ve made a series of backend optimizations to improve how CDAs are rendered and PDFs are generated, particularly for large documents.
We are updating the logic used to calculate the Readmission (“R”) flag for inpatient encounters to align with the CMS Hospital-wide Readmission (HWR) Measure methodology. This brings our approach in line with the industry standard used across hospitals and quality reporting frameworks.
We’ve refined the patient search experience to make it faster to find the right person. Now, when you enter a name, any exact matches will appear at the top of the results list, separated from similar names below.
Starting October 15, 2025 ZAP users will be able to selectively export only certain sections of a CDA Document. This makes exporting only the relevant information easier, and cuts down on the size of huge CDA exports.
We’ve added source identifiers to the meta.tag element on all new FHIR resources created from Carequality and TEFCA documents.
We’ve introduced a new option for managing patient enrollments in bulk with CSV upload. This provides a straightforward way to create new patients, update demographics, and manage enrollment status without needing to call the API directly.
We’ve made an update to help you better understand the freshness of patient data returned by Zus.
We have refined the timing of our Intelligent Refresh feature for appointments to ensure that care team members have the most up-to-date patient data well in advance of a visit.
We have introduced an optional priority: true attribute in the ZAP Data Subscriptions API that enables an immediate data refresh at the point of patient enrollment. Under normal circumstances, this initial refresh is queued to manage network load. With the priority attribute set to true, the initial refresh will execute immediately. This option is designed for scenarios requiring urgent data retrieval and is throttled at a rate of 10 requests per minute.