<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.canvasmedical.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.canvasmedical.com/history.atom"/>
  <title>Canvas Medical Status - Incident history</title>
  <updated>2025-12-23T16:34:58.692+00:00</updated>
  <author>
    <name>Canvas Medical</name>
  </author>
  
<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmjit2onh00dyxahe94rvvmu5</id>
  <published>2025-12-23T16:34:58.692+00:00</published>
  <updated>2025-12-23T19:06:03.172+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmjit2onh00dyxahe94rvvmu5"/>
  <title>Coverage eligibility failing due to missing gender</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Faxing, Claims &amp; Eligibility</p>
    <p><small>Dec <var data-var='date'> 23</var>, <var data-var='time'>19:06:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Eligibility checks will now function correctly without the `This payer requires a Gender if Date of Birth is sent` error..</p>
<p><small>Dec <var data-var='date'> 23</var>, <var data-var='time'>16:34:58</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue with eligibility checks. Some checks are erroring with the message `This payer requires a Gender if Date of Birth is sent.` We will continue to update..</p>
<p><small>Dec <var data-var='date'> 23</var>, <var data-var='time'>19:06:02</var> GMT+0</small><br /><strong>Identified</strong> -
  We are in the process of testing a fix for this issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmi58v9fu02caq59w98bd8z2g</id>
  <published>2025-11-19T00:08:38.118+00:00</published>
  <updated>2025-11-19T00:08:38.118+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmi58v9fu02caq59w98bd8z2g"/>
  <title>Login Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>00:08:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’ve identified a login issue to Canvas Settings/Admin affecting users with Multi-Factor Authentication (MFA) after our most recent release. We&#039;re currently implementing a fix. Users without MFA are unaffected..</p>
<p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>00:20:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have also identified an issue with logging in (regardless of MFA settings), if on a previous release.

We have identified a fix for both login issues and are in the process of deploying these fixes. .</p>
<p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>02:29:01</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>03:46:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmgoco1lw02qd319l7pkun6n9</id>
  <published>2025-10-12T23:43:11.424+00:00</published>
  <updated>2025-10-12T23:43:11.424+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmgoco1lw02qd319l7pkun6n9"/>
  <title>Background Jobs and Scheduled Tasks System Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 35 minutes</p>
    
    <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>23:43:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’re currently investigating an issue affecting background jobs (e.g., plugin cron tasks, appointment reminders, faxing updated, automated invoicing, lab polling, etc). Our team is monitoring system health while we work toward a fix..</p>
<p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>01:10:08</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our background queue database reached a critical memory threshold, we scaled up its resources appropriately and are monitoring the backlog of background jobs now.</p>
<p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>02:18:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  All pending background tasks have been processed successfully. The service is now operating at normal capacity with no remaining backlog. We will continue to monitor system health closely..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmeveaed40016dt3byodzo5ij</id>
  <published>2025-08-28T12:43:31.744+00:00</published>
  <updated>2025-08-28T12:43:31.744+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmeveaed40016dt3byodzo5ij"/>
  <title>Canvas Access Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>12:43:31</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of users experiencing frequent 403 errors when accessing Canvas - we are currently working to resolve the issue. .</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>13:58:08</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and a fix is underway.   
  
The issue may occur if users have an idle Canvas tab open when they sign in for the day. To prevent errors, users should restart their browser before navigating to Canvas.</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>14:31:38</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>12:19:20</var> GMT+0</small><br /><strong>Resolved</strong> -
  **Resolved:** A recent update caused some users’ requests to be mistakenly flagged as suspicious, briefly blocking access; we’ve fixed the issue and improved our safeguards to prevent it happening again. If you would like additional detail - please reach out to Canvas Support. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmbtsp4by00ayosxvgys3doyg</id>
  <published>2025-06-12T19:52:14.440+00:00</published>
  <updated>2025-06-12T19:52:14.440+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmbtsp4by00ayosxvgys3doyg"/>
  <title>Google Cloud Platform Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> Faxing</p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>19:52:14</var> GMT+0</small><br /><strong>Identified</strong> -
  Google Cloud Platform (GCP) is currently experiencing interrupted service impacting a variety of services. Canvas users have reported an interruption in Faxing and Google Calendar functionality. Google has identified the issue and are working to resolve. You can additionally review status updates directly from Google [here](https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW#2c2sBHWU84yPDJ8y1ar4). .</p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>14:16:29</var> GMT+0</small><br /><strong>Resolved</strong> -
  Google has reported that all services are fully restored as of approximately 6/12/25 930pm ET .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmbi4air40005e737os2wcusx</id>
  <published>2025-06-04T15:43:35.617+00:00</published>
  <updated>2025-06-04T16:00:28.816+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmbi4air40005e737os2wcusx"/>
  <title>Instances Unavailable Across Multiple Customers</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> API, Web Application</p>
    <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>16:00:28</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our infrastructure provider detected an issue with one of their database servers and had to restart. As part of that process, several systems were briefly restarted, which caused temporary unavailability across some instance. Services are now back online, and we’re closely monitoring to ensure everything remains stable..</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>15:43:35</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing a critical issue where multiple instances are unavailable. Our team is urgently investigating and escalating to our infrastructure provider. Updates will be shared as we learn more..</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>18:10:52</var> GMT+0</small><br /><strong>Resolved</strong> -
  All systems are back to normal and stable. Thanks for your patience while we monitored recovery. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmbf71xxj000ltft990pm1pkd</id>
  <published>2025-06-02T14:37:36.130+00:00</published>
  <updated>2025-06-02T14:37:36.130+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmbf71xxj000ltft990pm1pkd"/>
  <title>Users cannot send electronic prescriptions - receive error message</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> API, Prescribing</p>
    <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>14:37:36</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have reports across our customer base of failed prescriptions which display an error message. We are investigating now and will provide updates as soon as possible. .</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>15:09:43</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We’ve identified that this issue was caused by a release deployed earlier this morning. That release has since been reverted. We sincerely apologize for the interruption.

If you’re still experiencing any issues, please contact Canvas Support: &lt;https://portal.usepylon.com/canvas-medical/forms/standard&gt;.</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>15:28:28</var> GMT+0</small><br /><strong>Identified</strong> -
  We are receiving reports that all customers are experiencing authentication errors across all FHIR endpoints. This appears to be related to the earlier resolution deployed for prescription issues.

Our team is actively investigating and working toward a resolution with the highest priority. We will share updates as soon as more information becomes available..</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>15:54:48</var> GMT+0</small><br /><strong>Identified</strong> -
  For customers using both FHIR API and have providers who send prescriptions - we have the ability to resolve the API endpoint issues OR the ability to prescribe. If you would like to prioritize restoring the API, please reach out to Canvas Support if you do not currently have an open conversation..</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>16:43:45</var> GMT+0</small><br /><strong>Identified</strong> -
  We have a fix to resolve both the FHIR API and Prescribing issues. Please watch for further updates when the fix has been deployed. .</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>17:47:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The authentication errors affecting FHIR endpoints and the earlier prescription issues have both been resolved. Our team is actively monitoring the logs to ensure stability.

We appreciate your patience and partnership. If you experience any continued issues, please reach out to Canvas Support: &lt;https://portal.usepylon.com/canvas-medical/forms/standard&gt;.</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>20:51:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  The earlier issues affecting FHIR authentication and prescription functionality have been fully resolved. Systems remain stable, and we have not observed any further errors during monitoring.

This incident is now closed. If you experience any ongoing issues, please contact Canvas Support: &lt;https://portal.usepylon.com/canvas-medical/forms/standard&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cmacisqyo00ffg42t9k48t8tg</id>
  <published>2025-05-06T13:03:20.546+00:00</published>
  <updated>2025-05-06T13:03:20.546+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cmacisqyo00ffg42t9k48t8tg"/>
  <title>FHIR API Search Endpoint Errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13:03:20</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13:42:23</var> GMT+0</small><br /><strong>Monitoring</strong> -
  FHIR API Search endpoints are expected to no longer be returning 502 errors. If you see differently please reach out to support directly at &lt;https://portal.usepylon.com/canvas-medical/forms/standard&gt;.</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>16:14:58</var> GMT+0</small><br /><strong>Resolved</strong> -
  The recent errors affecting FHIR API search endpoints have been resolved. We sincerely apologize for the interruption and appreciate your patience.

If you have any additional questions or concerns, please don’t hesitate to contact Canvas Support..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cma16v92y0010vtwejuyws44o</id>
  <published>2025-04-28T14:43:54.945+00:00</published>
  <updated>2025-04-28T15:19:08.134+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cma16v92y0010vtwejuyws44o"/>
  <title>Forced Logouts &amp; Failed EPCS Prescriptions</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> Prescribing, Web Application</p>
    <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>15:19:08</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our team continues to investigate this issue with the highest priority. .</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>14:43:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating reports of users being unexpectedly logged out of the platform. This issue appears to be impacting active sessions, causing users to be signed out without initiating a logout themselves.

Our team is actively working to identify the root cause and implement a solution.</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>15:39:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  We believe this issue is also impacting the ability to send controlled substances. We are continuing to investigate and will continue to provide updates approximately every 30 minutes.</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>17:05:45</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have identified that the cause of users being logged out of their Canvas sessions and unable to send controlled substances is due to a change in our outgoing network IP address, which was updated by our infrastructure provider over the weekend.

Our team is actively making the necessary updates and closely monitoring services to ensure stability.

We will provide further updates if there are any changes or once the incident has been fully resolved.

Thank you for your patience and collaboration as we work to address this issue..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>19:40:56</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We continue to monitor logout issues. We have an urgent request into DrFirst for resolution with prescriptions. .</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>00:38:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  Prescribing of controlled substances has now been fully restored across all instances.

Users may have experienced a disruption between 8:00–8:30 PM ET while we reconnected to the DrFirst service. This disruption is not expected to occur again, and we sincerely apologize for the inconvenience.

We have confirmed that services are operating normally and will continue to monitor to ensure continued stability.

Thank you for your patience and collaboration throughout this incident.  
  
Please reach out to Canvas Support immediately if you experience additional issues. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cm97ffyvf000mtdtq6py7elma</id>
  <published>2025-04-07T18:50:51.585+00:00</published>
  <updated>2025-04-12T04:43:51.716+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cm97ffyvf000mtdtq6py7elma"/>
  <title> Intermittent Issues with Log Streaming</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 9 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> SDK</p>
    <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>04:43:51</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>18:50:51</var> GMT+0</small><br /><strong>Investigating</strong> -
  Extension development with the SDK may be impacted by intermittent log streaming issues. We are currently investigating this incident and will provide updates as they become available..</p>
<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>19:08:11</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have cleared the error preventing the log streaming from publishing and have identified the root cause. We will continue to monitor as we implement an enhancement that prevents reoccurrence..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cm516fizv001xingsb6tzqe3h</id>
  <published>2024-12-23T15:13:08.013+00:00</published>
  <updated>2024-12-23T15:13:08.013+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cm516fizv001xingsb6tzqe3h"/>
  <title>Unable to process payments in Canvas</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Dec <var data-var='date'> 23</var>, <var data-var='time'>15:13:08</var> GMT+0</small><br /><strong>Investigating</strong> -
  Some users have reported they have been unable to process payments in Canvas. We are currently investigating the issue and have engineers working to resolve. The current workaround is to process the payment directly in Stripe and manually add the payment to reflect in Canvas.

We apologize for the inconvenience and will keep you posted as updates are received..</p>
<p><small>Dec <var data-var='date'> 23</var>, <var data-var='time'>15:46:07</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and are continuing to work on a fix for this incident. We will keep you posted on further updates..</p>
<p><small>Dec <var data-var='date'> 23</var>, <var data-var='time'>20:44:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Please notify us if you run into any further issues..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cm48yvf1c000ulyl0gt3tjs7m</id>
  <published>2024-12-03T21:23:59.674+00:00</published>
  <updated>2024-12-03T21:23:59.674+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cm48yvf1c000ulyl0gt3tjs7m"/>
  <title>Reports of faxing delays &gt;1 hour</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> Faxing</p>
    <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>21:23:59</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are getting reports of outgoing faxes being delayed &gt;1 hour. We have a case open with Sfax and will update as we receive updates. .</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>01:24:43</var> GMT+0</small><br /><strong>Resolved</strong> -
  All faxes have processed, we will continue to monitor for future reports. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cm3q0kljd001171ou4yltwv33</id>
  <published>2024-11-18T15:01:00.000+00:00</published>
  <updated>2024-11-23T00:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cm3q0kljd001171ou4yltwv33"/>
  <title>SFax delays inbound and outbound faxes</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 9 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> Faxing</p>
    <p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>00:20:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>15:01:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Sfax has an ongoing Sev 1 issue that is causing delays with their inbound and outbound faxes. We will update as information becomes available..</p>
<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>12:20:47</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Users began reporting faxing issues on 11/18/24\. Per Sfax, the root cause was identified on 11/20/24 as a performance issue causing significant delays in fax processing. Early this morning (11/21/24), following a 3-hour downtime, Sfax completed a migration to resolve the problem. Sfax assured us that a dedicated team manually processed any faxes received prior to, during and immediately after the downtime.

As of 7:00 AM ET today, Canvas has confirmed that both outgoing and incoming faxes are processing as expected. We will continue to monitor the situation closely. Please report any ongoing issues to [**support@canvasmedical.com**](mailto:support@canvasmedical.com) or [submit a Help Center ticket](https://portal.usepylon.com/canvas-medical/forms/standard).

We appreciate your patience as we navigated this situation and worked to ensure service was restored..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cm3bvjwut004c4jsixddpw8sz</id>
  <published>2024-11-10T17:34:40.297+00:00</published>
  <updated>2024-11-10T17:34:40.297+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cm3bvjwut004c4jsixddpw8sz"/>
  <title>Pharmacy Service Unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> Prescribing</p>
    <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>17:34:40</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating reports of prescriptions failing to send with an error of `Server Error (500)`..</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>18:11:22</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>18:44:57</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>19:44:37</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue has been resolved. Our certificate for communication with SureScripts unexpectedly expired ahead of schedule, but we’ve since replaced it.

All impacted customers have received a proactive help desk ticket with additional details.

Thank you for your patience as we worked through this..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cm0nupmxr0074fjrs4rslu7wf</id>
  <published>2024-09-04T12:45:14.882+00:00</published>
  <updated>2024-09-04T12:45:14.882+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cm0nupmxr0074fjrs4rslu7wf"/>
  <title>SSO Failure to Login</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>12:45:14</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are urgently investigating an issue that is preventing users with SSO from logging into Canvas. Updates will be provided as available. .</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>13:15:52</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue was caused by the recent release. We are working to correct and will update you once complete..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>13:33:28</var> GMT+0</small><br /><strong>Monitoring</strong> -
  All production instances should be back up and running. We are working to resolve on the lower environments. We will continue to update you on the progress..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>19:18:25</var> GMT+0</small><br /><strong>Monitoring</strong> -
  All production and dev instances are back up and running. We will continue to update you on the progress. Thank you!.</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>19:57:02</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

We deployed updates to enhance security with Content Security Policy (CSP), which unintentionally affected customers using single sign-on. We quickly mitigated the issue by temporarily reversing the changes. The removal of CSP will not compromise the security of your instance.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clxxt1sn8147753xdn1rppiuecw</id>
  <published>2024-06-27T21:57:18.860+00:00</published>
  <updated>2024-06-27T21:57:18.860+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clxxt1sn8147753xdn1rppiuecw"/>
  <title>Banner Display </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> SDK, Web Application</p>
    <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>21:57:18</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;ve identified an issue with the display of any banner protocols. We are working on a fix and will keep you updated. .</p>
<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>22:31:28</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been found and is being deployed. We will continue to monitor .</p>
<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>01:06:45</var> GMT+0</small><br /><strong>Resolved</strong> -
  While adding the ability to create banner alerts from plugins (our new SDK) we inadvertently broke the formatting of banner alerts created from protocols. We have now resolved this issue and restored normal functionality. We appreciate your patience and sincerely apologize for any inconvenience this may have caused. Thank you for your understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clw6ikorg68537bfodfiuz5kw1</id>
  <published>2024-05-14T14:54:35.104+00:00</published>
  <updated>2024-05-14T14:54:35.104+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clw6ikorg68537bfodfiuz5kw1"/>
  <title>Lab Result Messages</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> Patient Messaging </p>
    <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>14:54:35</var> GMT+0</small><br /><strong>Investigating</strong> -
  Lab results messages are failing to send to the Canvas patient app. Please share results with patients using alternative methods until this is resolved.

We will provide further updates as they become available..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>18:25:30</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and are working on a resolution. In the meantime, if you need to send a lab result message to the patient via the Canvas patient app, please add the Lab Result Review command directly into the note. Refrain from using the review modal from the provider or patient panels to send a lab result message to the patient, as this is where the issue is stemming from.

We will continue to provide you updates as they become available..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>21:21:55</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved, and lab result communications can now resume being sent to patients via the Canvas patient app through both the provider and patient panels..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clsxxpux6186902aporr6fv5yrt</id>
  <published>2024-02-23T00:49:28.567+00:00</published>
  <updated>2024-02-23T00:49:28.567+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clsxxpux6186902aporr6fv5yrt"/>
  <title>Change Healthcare Cyber Security Issue </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 12 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> Claims &amp; Eligibility, Prescribing</p>
    <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>00:49:28</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident that is preventing prescriptions from sending. We will provide updates as they become available..</p>
<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>01:05:38</var> GMT+0</small><br /><strong>Identified</strong> -
  Optum (Change Healthcare) is currently facing a network disruption linked to a cybersecurity issue. Their specialists are actively addressing the situation. Upon detecting the intrusion, Optum promptly took steps to safeguard their partners and patients by disconnecting their systems to mitigate any potential additional impact. It is anticipated that the disruption will persist at least throughout the day.

This disruption may affect the following functionalities in Canvas:

* ePrescribing
* Eligibility
* Claims

Updates from Change can be found here: [status.changehealthcare.com/incidents/hqpjz25fn3n7](http://status.changehealthcare.com/incidents/hqpjz25fn3n7)

We will provide updates as more information becomes available..</p>
<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>13:36:53</var> GMT+0</small><br /><strong>Monitoring</strong> -
  At the moment, prescriptions are being submitted successfully. We will continue to monitor until full resolution is confirmed by Change Healthcare.</p>
<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>16:06:26</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are diligently overseeing the current situation involving Change Healthcare.

* Prescriptions - While some medications are being processed, we anticipate delays. Consequently, you may notice certain medications listed as pending.
* Coverages - there are no updates available at this time.

We will promptly communicate any further developments as they arise..</p>
<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>18:13:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are diligently overseeing the current situation involving Change Healthcare.

* Prescriptions - No further update at this time
* Coverages - Update for ClaimMD users  
   * [Claim.MD](http://Claim.MD) is holding all transactions from sending/receiving to payers that use Change Healthcare for their EDI processing.  
   **Please note:**  
         * **Only payer connections that require Change Healthcare are affected. All other payers are processing normally.**  
         * [Claim.MD](http://Claim.MD) customers do not need to hold any data; we are holding all claims and other affected transactions from sending through Change Healthcare until it is determined to be safe to submit.  
         * Realtime eligibility is returning connectivity errors for any payers that process through Change Healthcare.  
         * Electronic Remittance Advice \[ERA\] are not returning from affected payers.  
         * Claim Status updates are not returning from affected payers.

We will promptly communicate any further developments as they arise..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>14:09:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The service disruption with Change Health Care is still ongoing - 

**Prescribing** : In an effort to support the continuous and safe delivery of controlled substance prescriptions, Surescripts has removed EPCS services for all pharmacies connected through Change Healthcare as of 10:30 a.m. ET on February 24\. EHR vendors and health systems will need to download an updated pharmacy file, then prescribers will be able to determine the appropriate method to prescribe controlled substances.

Once Change Healthcare’s cyber security issue is resolved, Surescripts will restore EPCS service for all pharmacies connected through Change Healthcare.

Regular updates on this incident are being provided by Change Healthcare: &lt;https://status.changehealthcare.com/incidents/hqpjz25fn3n7&gt;.

**Recommended Actions**: All EHR vendors and health systems that utilize EPCS must download the pharmacy export file by 7:00 a.m. ET on February 25 and ensure it is made available to prescribers. Each EHR vendor and health system can see when their unique file is available in Workbench (Directory Manager—Directory Download) by 6:00 a.m. ET on February 25.

If the updated pharmacy file is not downloaded, prescribers will continue to receive an asynchronous 900 “Transaction rejected code” because controlled substance prescriptions cannot be faxed.

**Coverages:** No updates at this time.

We will continue to keep you informed..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>21:48:45</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The service interruption with Change Healthcare is still ongoing - 

**Prescriptions:** Surescripts provided the following errors prescribers are seeing and the meaning behind them: 

&gt; Until the issue is resolved, prescribers may receive an error message when sending E-Prescribing messages. 
&gt; 
&gt; E-Prescribing messages that attempted fax delivery but were not successful because of a busy signal, transmission timeout or other fax related errors will receive an asynchronous 600 “Communication problem – try again later” error: 
&gt; 
&gt; Message Type: Error 
&gt; 
&gt; Code: 600 
&gt; 
&gt; Description: Fax receipt could not be confirmed 
&gt; 
&gt; Controlled substance prescriptions cannot be faxed and will result in an asynchronous 900 “Transaction rejected code”: 
&gt; 
&gt; Message Type: Error 
&gt; 
&gt; Code: 900 
&gt; 
&gt; _Upon receipt of this error message, prescribers should process controlled substance prescriptions in writing or via telephone. States with electronic prescribing mandates have exceptions that apply to cyber security incidents._ 

**Coverages:** No further updates at this time

We will continue to keep you informed.</p>
<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>21:42:27</var> GMT+0</small><br /><strong>Monitoring</strong> -
  # The service interruption with Change Healthcare is still ongoing.

## **Prescriptions:** 

### Surescripts has provided the following update:

&gt; ...On March 1, in an effort to restore E-Prescribing services with Surescripts, Change Healthcare launched a new E-Prescribing environment that is connected to servers that were not compromised. 
&gt; 
&gt; A third-party auditor reviewed the new E-Prescribing environment, and Surescripts validated the attestation provided by Change Healthcare. As of March 1, Change Healthcare resumed E-Prescribing operations in this new environment.
&gt; 
&gt; Surescripts is still working to restore EPCS service for all pharmacies connected through Change Healthcare. A notification will be sent as soon as this issue is fully resolved....

## **Coverages:** 

No further updates at this time.

We will continue to keep you informed. Direct updates from Change Health Care can be found here: [status.changehealthcare.com/incidents/hqpjz25fn3n7](http://status.changehealthcare.com/incidents/hqpjz25fn3n7).</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>13:27:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are continuing to monitor the ongoing service outage with Change Healthcare. Updates are below.

**Prescribing:** As of 3/2/2024: The Change Healthcare issue has been **resolved for prescribing both eprescribing and EPCS**. Added information from Surescripts below:  

&gt; On March 1, in an effort to restore E-Prescribing services with Surescripts, Change Healthcare launched a new E-Prescribing environment that is connected to servers that were not compromised. A third-party auditor reviewed the new E-Prescribing environment, and Surescripts validated the attestation provided by Change Healthcare. As of March 1, Change Healthcare resumed E-Prescribing operations in this new environment. 
&gt; 
&gt; On March 2, Surescripts resumed EPCS services for all pharmacies connected through Change Healthcare. 

**Coverages:** No further update at this time.

We will continue to update you with any further details we receive..</p>
<p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>14:15:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Providing the latest updates on the Change Healthcare Incident.

Prescriptions: 99% of Change Healthcare pharmacy network services, and we continue to work on remaining issues. However, there are still a few areas we continue to focus on:

* A small subset of pharmacies that are still offline.
* The disruption for infusion pharmacies.
* Challenges for some Medicaid fee-for-service customers.

Coverages:   
Change Healthcare&#039;s network has resumed processing medical claims following recent disruptions. Assurance resumed operations on March 18, and Relay Exchange, the largest clearinghouse, was back online by March 23\. Efforts are underway to reconnect with payers, trading partners, and submitters to restore the claims network. While core systems are operational, cooperation from stakeholders is crucial to expedite claims processing. Key points for stakeholders:

* Payers: Change Healthcare is reaching out to Relay Exchange payers to gather necessary information for reconnection. Once details are obtained, credentials will be reset for prompt connectivity restoration.
* Trading partners: Many partners have initiated reconnection efforts, with encouragement for swift action. If a clearinghouse serves as the exclusive gateway, direct reconnection with Relay Exchange is encouraged.
* Assurance customers: Live users can begin processing claims, with ongoing expansion of payer access and updates to the online payer list.
* Direct submitters/channel partners: Reconnection is straightforward, with assistance provided for setting up secure connections. While some features like Connect Center are pending activation, reconnection remains a priority.

Efforts are focused on rebuilding connectivity to restore online claims and remittance flows for impacted customer groups, with a commitment to swiftly reinstating key features..</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>12:52:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cls99c4bo17397dfoekhhuh2vc</id>
  <published>2024-02-05T18:20:28.655+00:00</published>
  <updated>2024-02-05T18:20:28.655+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cls99c4bo17397dfoekhhuh2vc"/>
  <title>Canvas Medical Performance Alert - Credit Card Payment Processing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 days, 17 hours and 32 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>18:20:28</var> GMT+0</small><br /><strong>Identified</strong> -
  A recent update by Stripe has caused credit card payment processing failures in Canvas. Our team has identified the cause and is working on a fix. We know these issues are disruptive to your work, and we apologize for the inconvenience. We will provide updates here on the status page as soon as we have more information available. Thank you for your patience..</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>21:50:55</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>23:50:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clpwrc0n8168489bflndxza4r0c</id>
  <published>2023-12-08T15:03:50.907+00:00</published>
  <updated>2023-12-09T17:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clpwrc0n8168489bflndxza4r0c"/>
  <title>Automations not populating in chart note</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>15:03:50</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident where automations are not populating in the dropdown of the chart note. We will provide you updates as they become available..</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>17:03:29</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>15:18:33</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and are working on a fix. We will keep you informed on any updates as they become available..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clornukse7549bioeemuvsic1</id>
  <published>2023-11-09T20:47:46.489+00:00</published>
  <updated>2023-11-09T20:47:46.489+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clornukse7549bioeemuvsic1"/>
  <title>Canvas Medical Performance Alert - Saved Failed Errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>20:47:46</var> GMT+0</small><br /><strong>Identified</strong> -
  We’ve identified an issue impacting performance, causing an increase in ‘Saved Failed’ errors and possible duplication of resources. related to last night’s release. We are currently working to roll back the changes. We know these issues are disruptive to your work, and we apologize for the inconvenience. We will provide updates here on the status page as soon as possible. Thank you for your patience..</p>
<p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>22:45:14</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have rolled back last night release that was causing an increase in ‘Saved Failed’ errors and possible duplication of resources and are currently monitoring the result. Please reach out to Canvas Support if you continue to experience any issues. .</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>00:33:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clonadkrn39856bkoqo70veuh1</id>
  <published>2023-11-06T19:19:33.600+00:00</published>
  <updated>2023-11-06T19:19:33.600+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clonadkrn39856bkoqo70veuh1"/>
  <title>Canvas Medical Performance Alert - Prescribing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 6 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> Prescribing</p>
    <p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>19:19:33</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’ve discovered an issue impacting our prescribing workflows. We know these issues are disruptive to your work, and we apologize for the inconvenience. We will provide updates here on the status page as soon as we have more information available. Thank you for your patience..</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>19:41:01</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue causing prescribing errors. Our EPCS partner DrFirst migrated their data center last night and due to issues encountered as a result, is now migrating back to their original data center. You can follow the incident here: **https://status.drfirst.com/**
.</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>20:02:40</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our Pharmacy service is now operational, with prescription messages being sent and received without errors.  The [DrFirst incident](https://status.drfirst.com/) is still ongoing and so we will continue to monitor. We thank you for your patience. .</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>21:02:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clo1ru1ti170065b2n9kgxx0btj</id>
  <published>2023-10-22T11:30:00.000+00:00</published>
  <updated>2023-10-22T20:57:00.690+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clo1ru1ti170065b2n9kgxx0btj"/>
  <title>Unable to send prescriptions</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> Prescribing</p>
    <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>20:57:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>21:54:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved and prescriptions should now send successfully..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident that is preventing prescriptions from sending. We will provide updates as they become available..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>19:38:59</var> GMT+0</small><br /><strong>Investigating</strong> -
  This is still under investigation as we are working to determine the root cause. There appears to be an issue between our hosting provider and our electronic prescription vendor. We will provide updates as they become available..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>20:11:41</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the root cause of the issue and are working to resolve. We will continue to provide updates as they become available..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/cln8zbqm23933cqmzf3wumh7o</id>
  <published>2023-10-02T14:21:42.918+00:00</published>
  <updated>2023-10-02T14:21:42.918+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/cln8zbqm23933cqmzf3wumh7o"/>
  <title>Vaccines Are Not Populating</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>14:21:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an issue where the immunization statement command is not populating vaccines. We will provide updates as they become available.





.</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>14:38:16</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the cause vaccines not populating when searching the Immunization Statement command.  Our team is currently working on a fix.  .</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>15:56:28</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>16:30:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

A deploy over the weekend to expand the CPT range for immunizations documented via the Immunization Statement command had unintended consequences.  We&#039;ve rolled back this change.  .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.canvasmedical.com,2005:Incident/clmta6z44148479bfn32raeyknk</id>
  <published>2023-09-21T14:41:36.777+00:00</published>
  <updated>2023-09-21T14:41:36.777+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.canvasmedical.com/incident/clmta6z44148479bfn32raeyknk"/>
  <title>Errors Observed With Command Insertion</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Web Application</p>
    <p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>14:41:36</var> GMT+0</small><br /><strong>Investigating</strong> -
  When the patient has a future appointment that is not checked in and the user selects a quick action command from the patient summary or action panel, a save failed error will occur.

We are currently investigating this issue.

Recommended workflow to avoid error:
- Place cursor in active note prior to selecting any quick action commands
.</p>
<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>16:19:25</var> GMT+0</small><br /><strong>Identified</strong> -
  We’ve identified the root cause of the issue and have a solution that we’re preparing to deploy.

We will provide future updates as they become available..</p>
<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>18:24:38</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have developed a fix and are finalizing on our end. We will notify you once it has been deployed.

.</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>00:27:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  We’re pleased to announce this issue has been resolved. Thank you for your patience. If you’re still experiencing issues, please reach out to your Customer Success associate or support@canvasmedical.com.</p>

        ]]>
  </content>
</entry>

</feed>