We have added a new connector-level status to the patient history API. When Zus skips a particular connector due to our intelligent refresh logic or because that data source is otherwise unavailable, that connector will now show a status of skipped in the API and in the Zus App Records Request log.
Outbound ZusHooks messages will now include an "Operation Type" field in order to provide insight on what has changed for a given FHIR resource.
It's now easier than ever to update a patient's ZAP subscription package. The ZAP data subscriptions api will now accept a PATCHrequest to update practitioner or package details.
Starting today a new Vitals component and Vitals card in the overview component are available!
Source documents in the Zus Web Application now open in a new window, allowing users to print these documents or save them as PDFs.
We are excited to announce a new Transition of Care (ToC) Lens designed to cut down on the noise from ADT data and provide a summarized, deduplicated list of emergency and inpatient hospital visits. This Lens provides data as EpisodeOfCare FHIR Resources, and will soon link to additional relevant data about a discharge such as discharge summaries, discharge medications, and more!
Patient history jobs that are managed by Zus's batch process will now run at 3 am UTC on weeknights instead of at midnight UTC. For most customers, this includes the initial Get Up To Speed patient history call that we execute when you first enroll a patient.
Starting today all users will see the Overview Tab[BETA] in the ZAP. The Overview Tab provides a single-page summary of select data types designed to make it easier to get up to speed on the most important information quickly.
Zus conducts Get Up to Speed calls for EHR and medication history when customers first enroll a patient. Going forward, Zus will batch these requests (and other intelligent refreshes where possible) to occur off hours at 12 am UTC / 7 pm eastern. We are taking this step in response to the feedback from the EHR networks about load when customers enroll large cohorts. Batching bulk requests in this manner also ensures that ad-hoc records requests from UI users do not get stuck behind large queues.
Beginning today, ZAP users have access to more source data about patients. In the Sources Tab users will get access to information about what types of organizations have contributed data to the patient's ZAP. This includes Name, Demographics, and Contact data.
