Zus Health news and updates

Zus added a managed role, Builder Data Integration, for App Clients that get access tokens on behalf of users, such as EHR integrations or Zus apps embedded in a customer's interface, through the proxy token endpoint. On 14 October that permission was removed from Builder Admin, so only App Clients with the new role can now retrieve tokens for other users.

Our read

It narrows who can act on behalf of clinicians to reach patient records. Zus moved existing integration clients to the new role itself, so most customers need no action; new integration clients must be assigned it.

Zus refreshed the code sets behind its automatic tagging of specially regulated records against current VSAC value sets. Contraceptive management records now receive the SEX specially regulated label alongside abortion and gender affirming care, the categories covered under California AB 352. Data customers had already written to Zus was retagged under the updated sets.

Our read

First party records that match these codes also receive the Restricted label, which Zus says withholds them from other builders, from Lens summarization, and from CommonWell and Carequality responses. Third party records get the specially regulated label only, so customers should confirm their own downstream systems honor it.