Occasionally, CommonWell and Carequality participants respond to patient history requests with CDA documents respondents that have other binaries (e.g., PDFs, text, images) embedded within them. As of last week, we are extracting these embedded binaries and storing them to ODS.

Patient history API calls will now validate the patient's address, including their postal code, before accepting a refresh request. Postal codes must be formatted as 5 digits (e.g., 02138) or 5+4 digits separated by a hyphen (e.g., 02138-1000).

We are pleased to announce an update to our Patient History service that will improve the performance and stability of our medication history search.

We have released a search parameter that allows API users to find FHIR resources created by their Builder organization, thereby excluding third-party and Zus-created Lens resources 🥳. To use the first-party search parameter and benefit from the improved performance 💨, add firstparty=true to the URL.

Message statuses on the patient history API will no longer include the list of FHIR resources created by the underlying connectors. Payloads for this API were consistently too large to support a responsive synchronous experience.

The patient-history/messages endpoint allows Builders to search across previously initiated Patient History jobs. We now order these results by most-recently-created first and support start-date and end-date as parameters to narrow results based on when the job was initiated.

In order to ensure compliance with various clinical information networks, Zus builders are required to specify the name, NPI number, and role of a treating provider when making a /refresh/ request to the Patient History API.

New query examples are up! Learn how you can fulfill your analytic needs with Data Marts. For more information, see: https://docs.zushealth.com/docs/data-marts.

We're pleased to release the next generation of our Patient History service that will enable us with greater speed, stability, and scale in bringing you the clinical data that powers your Zus Aggregated Profile (ZAP).

Calls to the Zus Operational Data Store, which includes our FHIR APIs, are now rate limited at 20 requests per second per IP. The FHIR APIs will return HTTP 429 responses to requests exceeding this limit.