Today, users of the preview FHIR RESTful APIs available at https://fqs.zusapi.com/rest can now supply a header "X-New-Pagination" to receive the full URL schema in next and previous links, which conforms to FHIR's RESTful API's standards. This will allow users to update their integrations to take into account the correct URL in links.
We've updated our Intelligent Refresh behavior to help provide more-timely updates on hospitalized patients throughout their admission. In addition to refreshing EHR Documents and Medication Fills within 72 hours of an ADT discharge event, Zus will now refresh available documents within 2 hours of receiving any ADT message, including Admits and Transfers.
We'll be updating the FHIRplace application on June 14, 2024, to begin utilizing our FQS API for greatly improved performance when browsing FHIR resources for your patients. You may notice a few changes in the interface to browse by patient UPID or resource ID, which are outlined below:
Beginning today, source documents (Continuity of Care Documents or CCDs) have an updated design. This new design makes documents easier to use; including a table of contents, collapsible sections, and easier-to-read notes.
FHIR Device resources extracted from CDAs are now available to customers through data marts, in FHIRplace, and via the Zus APIs. These resources typically contain information on device types (implant, instrument, etc), how the device is associated with a specific patient, and the device’s operational status (active, inactive, etc). For example, a Device resource may describe that patient John Doe (with an ID: 12345) has an active cardiac pacemaker, with a SNOMED CT code of 14106009.
Improvements have been made to the organization of conditions in the Conditions Component to help clinical users more easily make sense of a patient’s condition history. These changes will begin rolling out today!
Starting today, the Transition of Care Lens will include a nested extension to help understand the most relevant discharge summary for a given Episode of Care.
Starting today, users will no longer see red dot icons in the ZAP to indicate the presence of data in each component.
3rd party data networks like Carequality and Commonwell require a Type 1, individual NPI number for a treating practitioner in order to submit a request for records. To ensure that all patients meet the minimum requirements to access records from all services in their subscription package, the ZAP data subscriptions API will now perform an additional validation check on enrollment requests and return the following message for Organization NPIs:
Zus is implementing an adjustment in our utilization of Surescripts medication history services in order to improve coverage of ongoing prescription activity for ZAP Pro patients.
