Risk Adjustment scoring (CMS HCC-RAF for v24 and v28) and recapture identification is now available via Data Marts under Public Preview for existing Data Mart customers! This feature will be rolled out to Data Mart customers beginning April 2, 2025. We expect rollout to be completed by April 15, 2025.
Note that this feature is still under development, and therefore is subject to change, deprecation, or packaging adjustments with limited advanced notice. Please contact Zus Customer Support with feedback or questions.
Beginning April 25th 2025, the Patient History Jobs List endpoint will only return patient history jobs run in the last 1 year by default. Complete request logs can be requested as needed for by contacting Support.
Additionally, we will no longer support job status as a search parameter to list patient history jobs. We do not expect this to impact any current integrations with the Patient History API, but please reach out should you have any questions or encounter any unexpected behavior.
Starting March 17th, the Zus GraphQL API will only support sorting by last_updated for all FHIR resources. The Zus GraphQL API reference has been updated to reflect this new behavior.
Users of the ZAP integration in the athena EMR can now reconcile lab data into the athena chart. Easily select a single lab or several labs to add into the athena. Add these data right into the Lab Results section of the athena chart with a single click!
More reconciliation workflows are on the way as we continue to deepen the interactions available in the embedded ZAP. Up next will be vitals reconciliation and a new user experience allowing for reconciling more data at once, simplifying the workflow of adding data to the chart.
We’ve reimagined the Zus Aggregated Profile (ZAP) to make it even easier to navigate and focus on what matters most — your data. This UI refresh streamlines interactions and optimizes space, making key information clearer and more accessible across both our native app and embedded EHR experiences.
Starting Monday March 17, 2025, users will see the updated ZAP. The rollout will continue through Wednesday gradually enabling the updated experience over the three day period.
This update is driven by your feedback and lays the foundation for even more powerful features to come. To learn more about how to effectively use the ZAP, check out our Clinical Guide.
We recently identified and resolved an issue where some Athena clinical data may not have been fully backfilled into the Zus platform. This issue did not affect real-time data ingestion, and no data was lost. The impact is that some data synced from Athena would not display the "synced with record" checkmark in the application.
The root cause has been resolved and the data will be backfilled gradually over time. No action is required on your part.
If you have any questions or concerns, please contact us at [email protected].
We’ve improved the way medications are displayed in the Medication Component and Medication Overview Card. Medications are now deduplicated by active ingredient, reducing unnecessary entries for variations in strength or form. This update simplifies the medication list, making it easier to review and reducing cognitive load for users.
Key Improvements with Examples:
Cleaner medication lists: Duplicate entries for the same active ingredient are consolidated. For example, if a patient is prescribed two dosages of atorvastatin (10 mg and 20 mg), they will now appear under a single entry for atorvastatin with relevant dosage details included. If a medication has more than one active ingredient, medications are only deduplicated when all code values match.
Better context in history views: Aggregated data for deduplicated medications is presented in a unified timeline. For instance, if a patient switches from one formulation of metformin to another, the timeline will show a continuous history of metformin use without redundant entries.
Enhanced clarity: Medication details are displayed with clear, concise labels and in a single view. The side panel will now show the combined timeline view of all of the deduplicated medications, including the associated brand names if applicable.
This enhancement ensures a smoother experience by decluttering the interface and helping you focus on the information that matters most.
We have received feedback regarding slow load times in the Diagnostics component and have implemented updates to enhance performance.
Key Updates:
Streamlined Trend Data Display:
Diagnostic results with trends available are no longer indicated by an icon in the diagnostics list. Trends are still accessible in the side panel by clicking into a specific result or report from the primary list.
This adjustment significantly improves data load times while still providing access to the most relevant trend information for each result.
Improved "SEE NOTE" Handling:
For test results displaying a value of "SEE NOTE," we now load the note's content directly into the side panel in many cases.
This change allows users to review important details more efficiently.
We remain committed to improving load times across the Diagnostics component and other areas of ZAP. Thank you for your feedback as we continue to enhance your experience.
Starting this week, notes and documents in the ZAP load separately from encounters.
In the Encounters & Notes tab, encounters now load first, giving users faster access to data. Documents and notes load separately, with a visible loading spinner displayed during the process. Once the documents finish loading, a note icon will appear in rows where documents or notes are available.
Starting January 6, 2025, we will apply the following changes to the Patient History API:
Patient History API requests that do not supply a priority attribute will by default run through our bulk queue. This queue manages our load on Carequality and CommonWell and ensures that our request volumes do not adversely impact other responders. It prioritizes jobs on a FIFO basis and smooths the rate at which they are submitted to the networks to ensure we don’t create large bursts of requests. Depending on how large the queue is when you submit a job, it may take as long as or longer than 36 hours to run; however, most jobs will run within 24 hours.
Patient History API requests that use “priority”: true will be throttled at a rate of 10 requests per minute per customer to prevent inadvertent traffic spikes on the EHR network.
We recommend that customers who expose the Patient History API to human users through a UI update their requests to use “priority”: true and account for throttling at a rate of 10 requests per minute. This will ensure that those users’ requests are honored immediately.
Customers that are submitting requests in bulk or through an asynchronous process don’t need to take any action – your requests will default to the bulk queue starting January 6th.
Customers that use our subscription-based packages and or submit requests through the Zus App need to take no action.
