<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>https://zushealth.com/ Status - Incident History</title>
    <link>https://status.zusapi.com</link>
    <atom:link rel="self" href="https://status.zusapi.com/history.rss" type="application/rss+xml"/>
    <description>Incident history of Zus Health</description>
    <pubDate>Fri, 25 Sep 2026 19:30:21 +0000</pubDate>
    <item>
      <title>Commonwell data retrieval errors</title>
      <pubDate>Fri, 25 Sep 2026 19:30:21 +0000</pubDate>
      <category domain="event:start">Thu, 24 Sep 2026 20:00:00 +0000</category>
      <category domain="event:end">Thu, 24 Sep 2026 21:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Data Connections, CommonWell Network&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 25, 2026 · 15:24 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We experienced errors in data retrieval from CommonWell between 4pm and 5pm eastern time yesterday for jobs which registered a new patient in CommonWell. Approximately 25% of all CommonWell jobs run during this time entered an error status. All affected jobs had been successfully rerun by 6:30pm eastern time. &lt;/p&gt;
&lt;p&gt;
No customer action is required, and the system has operated normally since.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/400565</link>
      <guid>https://status.zusapi.com/incidents/400565</guid>
    </item>
    <item>
      <title>Elevated errors in FQS</title>
      <pubDate>Mon, 24 Aug 2026 22:22:48 +0000</pubDate>
      <category domain="event:start">Mon, 24 Aug 2026 21:26:09 +0000</category>
      <category domain="event:end">Mon, 24 Aug 2026 22:22:48 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Applications, Zus App, Data APIs, FHIR APIs&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 24, 2026 · 18:21 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have addressed the root cause of the FQS errors, and services are back to normal.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 24, 2026 · 18:13 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The team rolled back a bad deployment and error rates have dropped. We are continuing to monitor.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 24, 2026 · 17:26 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The FQS API is returning elevated rates of 502 errors. This affects the REST and GraphQL APIs, Zus App, and reciprocity requests&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/394438</link>
      <guid>https://status.zusapi.com/incidents/394438</guid>
    </item>
    <item>
      <title>Elevated error rates on Carequality</title>
      <pubDate>Sat, 22 Aug 2026 19:15:38 +0000</pubDate>
      <category domain="event:start">Mon, 17 Aug 2026 21:00:00 +0000</category>
      <category domain="event:end">Sat, 22 Aug 2026 19:15:38 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Data Connections, Carequality Network&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 22, 2026 · 15:15 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All errored jobs have been re-run and completed. The system is functioning normally.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 21, 2026 · 16:34 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All errored jobs have been kicked off for a rerun through the system, and are flowing successfully, we expect completion within the next 12-20 hours, many have completed already.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 21, 2026 · 10:47 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The first batch of error recovery processing has completed successfully.  Zus will be completing the kickoff of all other errored jobs today, with expected completion over the weekend.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 20, 2026 · 09:18 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified and resolved the source of these job errors, and have begun the process of replaying impacted jobs – this process will complete today.&lt;/p&gt;
&lt;p&gt;
If a job you submitted has errored and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 18, 2026 · 18:10 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Zus experienced elevated error rates on our Carequality connector starting at ~5 pm eastern on 8/17/2026. We believe these errors have died down for upcoming jobs, and we will rerun impacted jobs tomorrow. &lt;/p&gt;
&lt;p&gt;
If a job you submitted has errored and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/393306</link>
      <guid>https://status.zusapi.com/incidents/393306</guid>
    </item>
    <item>
      <title>Database maintenance on certain FHIR APIs</title>
      <pubDate>Sun, 16 Aug 2026 11:00:00 +0000</pubDate>
      <category domain="event:start">Sun, 16 Aug 2026 10:00:00 +0000</category>
      <category domain="event:end">Sun, 16 Aug 2026 11:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Applications, Zus App, Data APIs, FHIR APIs&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 13, 2026 · 17:22 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Between 6:00 AM to 7:00 AM EDT on Sunday, August 16, we will be performing routine database maintenance on one part of the FHIR server. This will affect ZAP page loads and search queries on the FHIR API. We expect the disruption to last 10-15 minutes. No data will be affected.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/392158</link>
      <guid>https://status.zusapi.com/incidents/392158</guid>
    </item>
    <item>
      <title>Non-priority jobs operating with delays</title>
      <pubDate>Fri, 21 Aug 2026 15:06:57 +0000</pubDate>
      <category domain="event:start">Wed, 12 Aug 2026 22:49:54 +0000</category>
      <category domain="event:end">Fri, 21 Aug 2026 15:06:57 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Data Connections, CommonWell Network, Carequality Network&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 21, 2026 · 11:05 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are now regularly seeing and processing jobs with a latency of 1 day or less.  Delayed jobs with longer latencies can be attributed to the minor incident of elevated error rates on CareQuality and will be addressed within those recovery efforts.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 20, 2026 · 09:10 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We expect non-priority job latencies to return to normal within a day.&lt;/p&gt;
&lt;p&gt;
However, if a job you submitted has not started and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 17, 2026 · 11:39 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Non-priority jobs continue to be delayed, but we are working on clearing the backlog and expect resolution by mid-week.&lt;/p&gt;
&lt;p&gt;
If a job you submitted has not started and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 13, 2026 · 12:41 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Non-priority jobs submitted to the queue are continuing to complete more slowly than normal. Processing times will remain elevated for the next several days, and may climb to 2-3 days.&lt;/p&gt;
&lt;p&gt;
If a job you submitted has not started and the delay is impacting your operations: use the Request Records button in the ZAP to bypass this queue. You will not be charged for the additional job.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 12, 2026 · 18:49 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Due to a buildup of traffic in our non-priority queue, chart builds are operating with delays of approximately 30 hours. Please contact your account contact if this is impacting your operations.&lt;/p&gt;
&lt;p&gt;
Priority chart builds, included requests submitted through the Zus App and refreshes for STAT appointments, are not impacted.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/392044</link>
      <guid>https://status.zusapi.com/incidents/392044</guid>
    </item>
    <item>
      <title>Incident impacting the embedded ZAP in EHRs.</title>
      <pubDate>Thu, 13 Aug 2026 13:45:39 +0000</pubDate>
      <category domain="event:start">Wed, 12 Aug 2026 14:31:10 +0000</category>
      <category domain="event:end">Wed, 12 Aug 2026 17:36:21 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Applications, EHR Integrations, athenahealth, Elation Health, Canvas Medical, Salesforce Health Cloud, Healthie&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 13, 2026 · 09:43 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We can confirm that all data delays that were caused by the incident are now resolved. Any data that was not exchanged during this time has now been replayed and all systems are running as expected.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 12, 2026 · 13:34 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have resolved the underlying issues impacting all EHR integrations.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
The athenahealth integration is now fully functional, and data exchange is restored.  &lt;/li&gt;
  &lt;li&gt;
All data exchange delays are resolved across EHRs, and ongoing data syncing is restored.  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
We will continue to monitor these integrations to ensure smooth function going forward.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 12, 2026 · 11:57 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified the root cause of the issues impacting EHR integrations.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
For athenahealth, the ZAP is not functional. We are working to resolve the root cause, which we are aware of. Data exchange is also currently down.  &lt;/li&gt;
  &lt;li&gt;
Data exchange for all other EHR integrations is currently delayed. We are working to clear these delays.  &lt;/li&gt;
  &lt;li&gt;
We can confirm that the embedded ZAP was not functional in EHRs other than athenahealth from 10:48am-11:40am ET. This is now resolved.  &lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 12, 2026 · 10:31 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating reports of potential issues with EHR Integrations. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more.&lt;/p&gt;
&lt;p&gt;
Additional Context: The embedded ZAP and data synchronization are down for Athena.&lt;/p&gt;
&lt;p&gt;
Edit: the title of this incident was updated at 12:03pm ET&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/391992</link>
      <guid>https://status.zusapi.com/incidents/391992</guid>
    </item>
    <item>
      <title>Potential issue with ZusHooks</title>
      <pubDate>Tue, 4 Aug 2026 21:52:08 +0000</pubDate>
      <category domain="event:start">Tue, 4 Aug 2026 21:16:56 +0000</category>
      <category domain="event:end">Tue, 4 Aug 2026 21:52:08 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - ZusHooks&lt;/p&gt;&lt;p&gt;&lt;small&gt;August  4, 2026 · 17:38 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
ZusHooks deliveries were delayed by up to 2 hours within the last 2 hours. We have resolved the root cause and messages are now delivering normally.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August  4, 2026 · 17:16 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating reports of potential issues with ZusHooks. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more.&lt;/p&gt;
&lt;p&gt;
Additional Context: We are investigating increased Zushooks latency.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/390371</link>
      <guid>https://status.zusapi.com/incidents/390371</guid>
    </item>
    <item>
      <title>Risk Gaps not being calculated as expected</title>
      <pubDate>Wed, 5 Aug 2026 13:45:43 +0000</pubDate>
      <category domain="event:start">Mon, 3 Aug 2026 21:00:00 +0000</category>
      <category domain="event:end">Wed, 5 Aug 2026 13:45:43 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Lenses and Enrichment&lt;/p&gt;&lt;p&gt;&lt;small&gt;August  5, 2026 · 09:45 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This incident has been resolved, and all user updates have been restored.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August  4, 2026 · 16:48 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified an issue in processing data in the Risk product. Risk data was not processed between 5:00pm ET on 8/3/2026 through 12:00pm ET on 8/4/2026. &lt;/p&gt;
&lt;p&gt;
All Risk gaps impacted during this period are being reprocessed.&lt;/p&gt;
&lt;p&gt;
There was some loss of data during this time, which we are in the process of identifying and restoring.&lt;/p&gt;
&lt;p&gt;
We will close the incident when reprocessing is complete and provide an update on data restoration.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August  4, 2026 · 15:09 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating reports of potential issues with Lenses and Enrichment. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more.&lt;/p&gt;
&lt;p&gt;
Edit: The title of this incident was updated on August 4 at 4:50pm ET.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/390366</link>
      <guid>https://status.zusapi.com/incidents/390366</guid>
    </item>
    <item>
      <title>Issue with reciprocity on Carequality and Commonwell Networks</title>
      <pubDate>Thu, 30 Jul 2026 21:16:16 +0000</pubDate>
      <category domain="event:start">Wed, 29 Jul 2026 19:00:55 +0000</category>
      <category domain="event:end">Thu, 30 Jul 2026 21:16:16 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Data Connections, CommonWell Network, Carequality Network&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 30, 2026 · 17:14 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
With further research and monitoring, we’ve identified and upgraded the system configuration to improve it’s performance and mitigate the likelihood of further recurrences of the 5xx and latency behavior.&lt;/p&gt;
&lt;p&gt;
This issue is resolved.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 30, 2026 · 09:48 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The situation of higher than acceptable 5xx messages and longer latency has resolved, but the team continues to research and monitor.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 29, 2026 · 15:00 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We can confirm incident conditions on reciprocity on the CareQuality and Commonwell networks.  We are seeing elevated 5xx error rates in our responses to the networks and also latency has increased.  The impact is seen on the patient discovery and document list endpoints, document retrieval appears to be unaffected.&lt;/p&gt;
&lt;p&gt;
The team is continuing to investigate cause and potential solutions.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/389395</link>
      <guid>https://status.zusapi.com/incidents/389395</guid>
    </item>
    <item>
      <title>Some clients may not be able to access the ZAP in athena</title>
      <pubDate>Mon, 27 Jul 2026 16:58:19 +0000</pubDate>
      <category domain="event:start">Mon, 27 Jul 2026 15:25:04 +0000</category>
      <category domain="event:end">Mon, 27 Jul 2026 16:58:19 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Applications, EHR Integrations, athenahealth&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 27, 2026 · 12:57 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We can confirm that users of the ZAP in athenahealth are now able to open the ZAP as expected. There was no data loss during this incident. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 27, 2026 · 12:03 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue impacting users’ ability to open the ZAP in athena appears to have resolved. We are continuing to actively monitor this situation.&lt;/p&gt;
&lt;p&gt;
We are also continuing to track athena’s own &lt;a target=&quot;_blank&quot; href=&quot;https://status.athenahealth.com/incident/412942&quot;&gt;published incident&lt;/a&gt;, and will update this incident once we can confirm full resolution of the source issues.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 27, 2026 · 11:25 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating reports of potential issues with Zus App. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Edit July 27 11:40am ET:&lt;/strong&gt; We have confirmed that this issue only impacts users of the ZAP embedded in athenahealth. We have updated the title and impacted services of this incident as such.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/388811</link>
      <guid>https://status.zusapi.com/incidents/388811</guid>
    </item>
    <item>
      <title>Delays processing Surescripts medication history requests</title>
      <pubDate>Thu, 16 Jul 2026 13:42:55 +0000</pubDate>
      <category domain="event:start">Wed, 15 Jul 2026 16:41:04 +0000</category>
      <category domain="event:end">Thu, 16 Jul 2026 13:42:55 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Data Connections, Surescripts Service&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 16, 2026 · 09:10 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue is resolved and all delayed data has now been processed. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 15, 2026 · 12:41 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We’re aware of an issue affecting the processing of some Surescripts medication history requests created on July 10, which may delay or leave incomplete the return of medication history data for the affected requests. This is a partial delay rather than a complete outage, and new requests continue to be processed normally. We’re actively working with Surescripts to resolve the issue and will provide an update as soon as the affected data is fully processed.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/386147</link>
      <guid>https://status.zusapi.com/incidents/386147</guid>
    </item>
    <item>
      <title>Potential issue with Carequality Network</title>
      <pubDate>Fri, 24 Jul 2026 15:48:15 +0000</pubDate>
      <category domain="event:start">Wed, 1 Jul 2026 18:33:00 +0000</category>
      <category domain="event:end">Fri, 24 Jul 2026 15:47:56 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Data Connections, Carequality Network&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 24, 2026 · 11:35 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This incident is now resolved. Based on our continued monitoring, record location is performing as expected. We will continue to support customers with reruns as needed.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 22, 2026 · 18:02 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified an issue that was resulting in slightly degraded patient matching results on the Carequality network since 7/1. The original behavior has been restored as of 7/22. If you have any concerns about a potential data gap, please feel free to rerun a new job or reach out to your account contact.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 21, 2026 · 14:33 EDT&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating reports of potential issues with Carequality Network. At this time we have not confirmed an incident - our team is actively looking into the situation and will share an update as soon as we know more.&lt;/p&gt;
</description>
      <link>https://status.zusapi.com/incidents/387567</link>
      <guid>https://status.zusapi.com/incidents/387567</guid>
    </item>
  </channel>
</rss>