Care team users can now view lab trends for hemoglobin a1c and glucose for patients with these data available in the Diagnostics component. We are planning to make trends available for additional labs (e.g., cholesterol, triglycerides, GFR) in the near future. This trending feature is currently only available to Builders on an opt-in basis. If you would like the ability to view lab trends, please reach out to our Support team.
Diagnostic reports (i.e., labs, imaging, clinical studies, etc.) can now be viewed in a separate Diagnostics component. The new Diagnostics component allows you to "dismiss" diagnostic reports to hide them from your view and visually distinguishes between viewed vs. not viewed diagnostic reports. The Timeline component still retains diagnostic reports in addition to encounters if you prefer to look at both encounters and diagnostic reports in the same timeline view.
The Medications List and Outside Medications components have now been merged into a single Medications List component in the standalone Zus App. This component contains medications from external providers in addition to medications you have added to your own record. The new component visually distinguishes between your records vs. external medications, as well as viewed vs. not viewed medications.
Zus embeddable components are now powered by the Zus FHIR GraphQL Service, significantly improving page load times and solving several issues which caused data to fail to be surfaced across components.
The Conditions List and Outside Conditions components have now been merged into a single Conditions List component in the standalone Zus App. This component contains conditions from external providers in addition to conditions you have added to your own record. The new component also visually distinguishes between internal vs. external data, as well as viewed vs. not viewed conditions.
The Documents component now includes encounter dates associated with documents (where applicable) and incorporates encounter dates in the Documents list deduplication logic. Clinicians can now prioritize and sort documents to review based on encounter date and there will be more documents available to review as a result of the improvement to the deduplication logic.
The Medications component's Outside Medications tab now shows all summarized medications from outside sources, not just those which Zus determines are active. The Outside Medications tab now also shows medications without medication activity dates to provide a more comprehensive view to clinicians performing medication reconciliation.
We are excited to announce our new /patient-history/jobs API, which comes with improved functionality to schedule a Patient History job and other enhanced features.
On August 8th, the following endpoints will be deprecated:
- Start a job - /patient-history/patient/{patient-id}/refresh
- Check the status of a job - /patient-history/message-status/{message-id}
- Get job messages - /patient-history/messages
To ensure a smooth transition and minimize any disruptions to your projects, we have prepared this guide to help you convert your existing requests to the new API.
Whereas the /refresh endpoint does not have a request body, the new /jobs endpoint does.
{
"data": {
"type": "patient-history/jobs",
"attributes": {
"requestConsent": true,
"practitioner": {
"npi": "1013085661",
"name": "Testfirstname Testlastname",
"role": "309343006"
}
},
"targetDate": "2023-09-01",
"relationships": {
"patient": {
"data": {
"type": "fhir/Patient",
"id": "{patient-id}"
}
}
}
}
}
Please see below for the differences in the response bodies.
{
"data": {
"id": "{job-id}",
"type": "create_patient_history_job",
"attributes": {
"message_status": "done",
"messages": [
{
"services": "commonwell",
"status": "done"
},
{
"services": "surescripts",
"status": "done"
}
]
}
}
}
{
"data": [
{
"type": "patient-history/jobs",
"id": "{job-id}",
"attributes": {
"createdAt": 1681406975,
"jobStatus": "in_progress",
"lastUpdatedAt": 1687809292,
"practitioner": {
"npi": "1013085661",
"name": "Testfirstname Testlastname",
"role": "309343006"
},
"providers": [
{
"service": "commonwell",
"status": "done"
},
{
"service": "surescripts",
"status": "done"
}
]
},
"relationships": {
"patient": {
"data": {
"type": "fhir/Patient",
"id": "{patient-id}"
}
}
}
}
],
"links": {
"self": "<https://api.zusapi.com/patient-history/jobs?page[count]=50&page[offset]=0>"
},
"meta": {
"totalResultCount": 1
}
}
To improve performance, builders can now apply 'last-updated-from' and 'last-updated-to' filters in FHIRplace to decrease the number of resources returned on initial page load. By default, FHIRplace will now apply a filter to only display resources updated within the last 10 days, which can be cleared at any time.
As part of an ongoing effort to enable greater interoperability and care coordination (please see a previous update here), data from the CommonWell and Carequality networks will now be written to the Zus Common Patient Record (CPR). This enables builders to access all available third-party EHR data within the Zus network for patients with whom they have an active treatment relationship.
Zus application and data warehouse users will not need to make any changes to benefit from this update. However, newly created foundational data (Location, Organization, Practitioner) from the CommonWell and Carequality networks will no longer be available in customer data marts.
In FHIRplace, users can view available CPR resources by clicking the filter button next to a given patient. If querying for third-party resources directly via API, builders will need to search for resources by the universal patient identifier of the given patient to access FHIR resources from third-party data sources.