Coming July 18: New Encounter Lens cleans and normalizes encounter data
We are thrilled to announce our latest Lens for Encounter data. This new Encounter Lens ensures that all encounters are cleaned, deduplicated, and normalized.
We are thrilled to announce our latest Lens for Encounter data. This new Encounter Lens ensures that all encounters are cleaned, deduplicated, and normalized.
Users of the Zus Web Application are now able to open CDA documents in a new tab in addition to viewing the document within the ZAP.
Enrolling a patient in a ZAP Data Subscription requires specifying the practitioner with a treatment relationship to the patient. The Data Subscriptions API will now accept a reference to an existing FHIR Practitioner resource in place of the NPI, name, and role fields when creating or updating an enrollment.
After careful consideration, the following tables in the legacy data mart schema will be decommissioned due to their limited usage and value to analytics use cases:
We're excited to introduce a new Intelligent Refresh trigger to improve latency for prescription activity in Zus and enable better tracking of medication adherence. The “Expected Refill” trigger calculates an expected refill date for each medication fill processed in Zus (as whenPickedUp* + days supply) and will automatically schedule a follow up refresh to check for pickup ~5 days after the expected date. As a part of this change, we will be adjusting the 28 day backstop (if no other refresh activity) to 36 days to better align with standard 30 day refill cycles.
Zus will be updating the login session management settings for the Zus Web Application. Beginning June 13, all users will be required to log in daily regardless of activity (in other words, after 24 hours you will be asked to re-enter your login credentials). We are making this change to align with industry security standards.
We have updated the way in which we process patient documents. Previously, when gathering documents for a patient, we would download all of their documents (regardless of the document's age or if we had downloaded it before). We have now implemented an optimized approach (for documents associated with the CareQuality network) where we only download all of a patient's documents once. After that, any further petitions for a patient's documents will limit retrieved documents to only those created in the past year (with specific exceptions for documents with dates prior to 1970). You may see these changes result in fewer duplicates in both the Zus App and overall. If you observe anything trending in an unexpected direction during your normal analysis do not hesitate to get in contact with us.
🥳 A new data mart schema in a familiar relational format is now available!
Starting today any filters or sorting a user applies to the ZAP will be automatically retained. Users no longer have to reset filters after logging out or switching between patients.
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.