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 support@zushealth.com.

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.

Starting today, ZAP users can copy relevant data to the clipboard to be easily pasted in other applications.

Users can hover over data in the Demographics, Conditions, Medications, Diagnostics, Allergies, and Immunizations sections to copy individual pieces of data to the clipboard that can then be pasted elsewhere.

We now maintain a list of 'priority' medications for refill adherence that will be refreshed within 7 days of their expected refill date.

The priority list includes any medication associated with a 2024 CMS eCQM or HEDIS quality measure, including for example Anticoagulants, Antidepressants, Antihistamines & Antiemetics, Antipsychotics, Antispasmodics, Benzodiazepines, Bisphosphonates & SERMs, Bronchodilators, Cholinesterase Inhibitors, Corticosteroids, Estrogens & Progestins, Insulin & Oral Hypoglycemics, Immunosuppressants, Opioids, Retinoids, Statins, and Stimulants. Please reach out to view the full list of priority medications or suggest additional medications.

Medications not on the priority list will continue to be refreshed through other triggers, such as upcoming appointments or the 36-day recurring refresh.

Current List of Medication History Refresh Triggers:

• Initial enrollment
• Before the appointments you share with Zus
• After any 3rd party appointments we pull in from other providers on Carequality and Commonwell
• After an ADT discharge
• At most 7 days from the expected refill date for priority adherence medications
• Any time more than 36 days have elapsed between medication refreshes

To better support customers conducting common population health analyses on Zus data marts, we have published a query library. This query library contains links to a public GitHub repo populated with SQL code compatible with the current data mart relational schema.

The query library is broken into 6 sections:

1. Understanding Zus data
2. Analyzing patient demographics
3. Evaluating population health
4. Identifying high risk patients
5. Supporting risk capture
6. Identifying care gaps

This query library is an experimental resource that the Zus team is evaluating supporting long term. As we evaluate further building out the library, please feel free to share suggested additions and other feedback using this feedback form. We look forward to hearing from you!

Beginning November 5, an updated view of Patient Contact Information will be available in the ZAP. Here are some highlights to look forward to:

• Contact information is now separated from Sources so users can get access to the information they need more quickly.
• Phone numbers, email addresses, and physical addresses are listed from most common to least common, including information about what sources noted each individual data point.
• A checkmark indicates if the value is one already known to your organization and is "synced with record" as it does for clinical information in the ZAP
• Users can copy a phone number, email, or address to the clipboard to be pasted into another application such as your CRM tool.
• The "Sources" tab now moves alongside "Contact Info" and both sections are housed under "Demographics" in the ZAP. In the Web Application, this also includes a demographics section with additional patient information.

Read more detailed information in our Clinical Guide.

Note: this will be released to users gradually between November 5 and November 8.

Users can now filter to view only Conditions that are associated with a Hierarchical Condition Category (HCC) Code in the ZAP. By selecting this filter, the list of conditions shows only those with an associated HCC, as indicated by the blue icon in each condition row.

Remember that user filters are retained across patient charts, so if a user selects this filter in one patient chart and moves to another the filter will remain.