Is Zus Health down?

The following tables in the relational data marts have been failing to refresh since 2pm Eastern Time on Thursday, May 14: condition and child tables document_reference and child tables encounter and child tables The data in these tables reflects data as of 2pm yesterday. We are working to bring these tables back up to date to meet our documented 3-hour target freshness.

The condition and encounter tables have been rectified. We are continuing to work on refreshing the docuemnt_reference tables.

document_reference tables have now been refreshed as well. We are continuing to monitor the situation.

We have resolved the underlying problem that was preventing tables from automatically refreshing. All relational tables should now be following the targeted freshness published in the documentation.

New Generated Patient Summary requests are failing for users. The root cause has been identified and the fix is rolling out. We will post an update when the issue is fully resolved.

Generated Patient Summaries are now restored and will generate as expected.

We are aware of and investigating degraded performance with Zus APIs and in the Zus Application. We will post an update with more information when we’ve identified the root cause.

We identified the root cause of performance degradation and stopped the process from continuing. We’ll continue to monitor closely to ensure there is no further performance impact.

From 3:48pm ET - 4:45pm ET some patients were not accessible in the Zus Web Application. Navigating to the patient ZAP would have resulted in a message that the patient was “inactive” when they were in fact “active.” We identified the root cause and are deploying additional protections to ensure this will not happen again.

We are investigating an increased number of Carequality errors affecting a subset of requests primarily for California-based patients. We have identified a pattern related to certain zip code based patient lookups and are coordinating with our network partner, Kno2, on root cause analysis. Some customers may see delayed or incomplete results while this is ongoing.

We have identified the likely root cause of the increased number of Carequality errors affecting a subset of requests, primarily for California-based patients. Our investigation with Kno2 found that some data published to the Carequality directory by one implementer is not formatted according to Carequality policy, which appears to be driving the pattern related to certain zip code based patient lookups. This issue appears to be affecting ~6% of Zus jobs for patients with a California address. The affected implementer is actively working on a correction. Some customers may continue to see delayed or incomplete results until that correction is made and the directory sync completes.

We are continuing to work with Kno2 on having the affected implementer correct their impacted Carequality directory listings. This issue continues to affect ~6% of Zus jobs for patients with a California address.

We have worked with Kno2 to prevent job errors when encountering misconfigured Carequality directory listings. We are no longer seeing errors for this issue and we have successfully re-run affected jobs.