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.
Zus is now live with a direct connection to Carequality! This direct connection will result in higher match rates across your patient population and more historical medical records matched per patient. You do no need to take any action to benefit from the direct Carequality connection.
Care teams can now view encounters and diagnostic reports (i.e., labs, imaging, clinical studies, etc.) from their organization and outside provider records in the new Timeline embeddable component. Learn more about the Timeline and the overall Zus component library.
Care teams can now view clinical documents from their organization and outside provider records in the new Documents embeddable component. These documents contain information that Zus has not yet incorporated into other embeddable UI components. Learn more about the Documents component and the overall Zus component library.
Over the next several weeks, we will be making some changes to how third-party data is stored in order to enable greater interoperability and care coordination. As of today, medication history results from the Surescripts network will be written to the Zus Common Patient Record (CPR), enabling builders to access all available third party medication 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 in order to benefit from this update. 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 identifier of the given patient in order to access results from third party sources.
https://api.zusapi.com/fhir/MedicationDispense?patient.identifier=https://zusapi.com/fhir/identifier/universal-id|{{universal ID}}
The Patient History API will now allow a maximum of one patient-history refresh requests per patient per 13 day period. Multiple requests inside of this window will receive an HTTP 429 error (too many requests), with a Retry-After value included in the response header. Real-time medication, lab, and ADT alerts will not be impacted by this change, and will continue to provide real-time insight into the health of patients.
Builder developer users can now try the Zus GraphQL API, which offers efficient queries to retrieve FHIR resources for one patient to integrate with the Zus Aggregated Profile (ZAP). For more information, see: https://docs.zushealth.com/docs/graphql-fhir-query-service
Care Teams can now view patient allergies from their organization and outside provider records in the new Allergies embeddable component. Learn more about the Allergies component and the overall Zus component library.
📆 Appointments and five other FHIR resource types now included in Data Marts.
Builders can now analyze Appointment, Consent, Device, DeviceUseStatement, FamilyMemberHistory, and Goal FHIR resource types. Please see the linked FHIR specification to understand what the resource types represent.
For example, suppose you want to identify which patients have had the most appointments in the last year. The query below will retrieve an ordered result set.
select
universal_patient_identifier,
count(distinct id)
from appointment
where status != 'cancelled'
and end >= dateadd(year, -1, current_date())
group by 1
order by 2 desc;