Zushook webhook payloads now include a top-level upid field containing the patient's Universal Patient ID (UPID) whenever one is extractable from the resource. This field is present for all authentication types — OAuth, basic, and unauthenticated — and regardless of whether the full FHIR resource is included in the payload.
We’ve added support for identifying delivery type when it appears in free-text clinical documentation and creating a standardized FHIR Procedure resource from it. Supported mappings currently include Cesarean delivery (SNOMED CT 11466000) and Vaginal delivery of fetus (SNOMED CT 700000006).
New tables and columns are now available to customers in Zus data marts as of April 6th, 2026.
We have updated our Clinical Data Contribution Policy to clarify requirements and options for customers in active implementation, and to clarify the expected frequency of ongoing refreshes. Our updated policy is available here: https://docs.zushealth.com/docs/clinical-data-contribution-policy
We’ve completed the rollout of Data Source labels across key surfaces of the ZAP, improving visibility into where patient data originates. This helps clinicians quickly understand whether data is their own (called "first-party"), sourced from the networks (called "third-party"), or from another Zus-connected practice.
We updated CEQ and TEFCA document list behavior to better honor the HomeCommunityId provided in requests.
We’ve added a source organization identifier tag on all new FHIR resources created from CommonWell documents. This identifier can used to determine the original source of a document using the CommonWell custodian OID and can be found in the meta.tag element of the resource.
We fixed a set of issues affecting reciprocity flows for our Healthie EHR Integration focused on CCDA quality, timely availability, and source attribution. The release includes both partnership work with Healthie to improve CCDAs and a set of Zus changes: improved ingestion, stricter attribution, corrupted-data cleanup, parsing improvements, and new monitoring to detect and prevent future failures. Together these changes improve the fidelity of shared clinical records and further strengthen the integration with Healthie's EHR.
We’ve expanded our Chart Build offering with a new, lighter-weight option to help you get up to speed on patient history.
We’ve updated how HCC (Hierarchical Condition Category) codes are represented and displayed to make CMS versioning clearer and reduce ambiguity across data and UI.
