tag:status.revolutionehr.com,2005:/historyRevolutionEHR Status - Incident History2024-03-29T00:23:45-05:00RevolutionEHRtag:status.revolutionehr.com,2005:Incident/203044852024-03-28T16:03:41-05:002024-03-28T16:03:41-05:00Status of Received not updating on SmartFlow Orders via FAIT/WVA<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>16:03</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>19</var>, <var data-var='time'>15:54</var> CDT</small><br><strong>Investigating</strong> - Orders submitted via SmartFlow to FAIT/WVA are successfully being transmitted. However when the order is received at the office the order status is not updating and customers are unable to generate automated messages to patients for pick up. We are aware of this issue and engineers are investigating.<br /><br />In the interim there is a work around. On the order select the "Change Order" button, this will create a new order and cancel the initial order. In the new order change the processor to "Manual"; update the status to Received by clicking through the status options</p>tag:status.revolutionehr.com,2005:Incident/203885572024-03-28T10:41:01-05:002024-03-28T10:41:01-05:00RXNT medications not updating in RevolutionEHR<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>10:41</var> CDT</small><br><strong>Update</strong> - We are also receiving reports that users are not able to stop medications.</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>09:27</var> CDT</small><br><strong>Investigating</strong> - Some users are reporting that when writing an Rx in RXNT the medication is not being pushed back to RevolutionEHR. When trying to update the medication list in RevolutionEHR they receive an error. We are currently working with RXNT to resolve the issue.</p>tag:status.revolutionehr.com,2005:Incident/203612682024-03-26T11:16:56-05:002024-03-26T11:16:56-05:00Customer Support currently unavailable<p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>11:16</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>08:24</var> CDT</small><br><strong>Identified</strong> - We are currently experiencing technical issues that are preventing our Customer Support team from accessing phones, emails and live chats. We appologize for the inconvenience. Our IT department is working to resolve this issue as quickly as possible. This is an internal issue and does not impact any customer's ability to access and use RevolutionEHR.</p>tag:status.revolutionehr.com,2005:Incident/202439892024-03-19T15:54:18-05:002024-03-19T15:54:18-05:00Lag time with Trizetto claims<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>08:40</var> CDT</small><br><strong>Update</strong> - We have received notification from Trizetto that the update did not occur, we will continue to post updates as they become available"</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>16:10</var> CDT</small><br><strong>Update</strong> - Trizetto is planning on doing an update this weekend which should resolve this lagging issue once completed.</p><p><small>Mar <var data-var='date'>14</var>, <var data-var='time'>09:08</var> CDT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Mar <var data-var='date'>14</var>, <var data-var='time'>09:07</var> CDT</small><br><strong>Identified</strong> - Trizetto has notified us that they are experiencing high traffic on their websites which is causing slowness on their servers. Due to the slowness of TriZetto’s servers clients can experience slowness when sending claims or statements from RevolutionEHR to Trizetto. Although Trizetto is working to resolve this issue an eta is not known.</p>tag:status.revolutionehr.com,2005:Incident/201702372024-03-06T12:03:04-06:002024-03-06T12:03:04-06:00Connectivity Issues in California<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>12:03</var> CST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>15:18</var> CST</small><br><strong>Identified</strong> - RevolutionEHR is aware and monitoring on-going connectivity issues with customers utilizing Xfinity/Comcast to access our applications.</p>tag:status.revolutionehr.com,2005:Incident/199938822024-02-20T09:39:45-06:002024-02-20T09:39:45-06:00Issues with RXNT launch from RevolutionEHR<p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>09:39</var> CST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>16:10</var> CST</small><br><strong>Monitoring</strong> - RXNT has applied a resolution for this issue.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>09:58</var> CST</small><br><strong>Identified</strong> - RXNT has informed us that the current issue is on their end and may not be impacting all customers. They are needing to fix this issue at the individual user level. If you are experiencing a problem with RXNT launching from RevolutionEHR, please contact RXNT directly and they will assist you</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>12:20</var> CST</small><br><strong>Investigating</strong> - Some offices have reported that RXNT does not load when launching the integration. We are currently working with RXNT to resolve the issue.</p>tag:status.revolutionehr.com,2005:Incident/198616472024-02-02T02:01:00-06:002024-02-02T02:01:00-06:00System Maintenance February 1st US and Canada<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>02:01</var> CST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>23:00</var> CST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>15:49</var> CST</small><br><strong>Scheduled</strong> - We will be performing scheduled maintenance on Thursday, February 1st at 11:00 PM CDT. The system will be unavailable for 3 hours during this time. If you are logged in at 11:00 PM CDT on Thursday, you will receive an error message and may lose data currently being entered. It is very important that you log off prior to 11:00 PM CDT this Thursday.</p>tag:status.revolutionehr.com,2005:Incident/198710102024-01-31T01:02:00-06:002024-01-31T01:02:00-06:00Maintenance Window for US Tonight at 11:00 pm CST<p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>01:02</var> CST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>23:00</var> CST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>17:13</var> CST</small><br><strong>Scheduled</strong> - To address some intermittent latency issues experienced by some users today, we will be performing maintenance tonight, Tuesday January 30th, at 11:00 pm CST. The system will be unavailable for approximately 2 hours during this time. Please be sure to log off prior to 11:00 pm CST to avoid loss of connection that could impact any data being entered at that time. This window will only impact customers in the US.</p>tag:status.revolutionehr.com,2005:Incident/195929712024-01-02T11:49:26-06:002024-01-03T18:28:19-06:00Lag times and issues with logging into RevolutionEHR<p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>11:49</var> CST</small><br><strong>Resolved</strong> - This issue has been resolved. The engineers are completing final assessments and determining root cause as well as proactive actions to be taken to prevent this from occurring. We will provide a post mortem on this incident tomorrow after 4:00 pm CDT with the full explanation</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>10:51</var> CST</small><br><strong>Monitoring</strong> - All logins have been enabled and stability is good. We will continue to monitor very closely</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>10:41</var> CST</small><br><strong>Update</strong> - Engineering is slowly allowing some log ins to occur. This process is to ensure stability remains. Additional log ins will be continually added in batches while monitoring occurs.</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>10:32</var> CST</small><br><strong>Update</strong> - Additional changes are still being implemented. Once completed testing will resume</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>09:48</var> CST</small><br><strong>Update</strong> - Testing has determined that the instability still exists, additional changes are currently being implemented</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>09:26</var> CST</small><br><strong>Update</strong> - Testing is continuing on the potential fix, we will continue to provide updates as they become available</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>08:53</var> CST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>08:32</var> CST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>08:18</var> CST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.revolutionehr.com,2005:Incident/195537832023-12-31T02:00:10-06:002023-12-31T02:00:10-06:00System Maintenance, Saturday, December 30th for US Only<p><small>Dec <var data-var='date'>31</var>, <var data-var='time'>02:00</var> CST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>30</var>, <var data-var='time'>23:00</var> CST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>28</var>, <var data-var='time'>16:33</var> CST</small><br><strong>Update</strong> - This will impact the US only</p><p><small>Dec <var data-var='date'>28</var>, <var data-var='time'>16:26</var> CST</small><br><strong>Scheduled</strong> - We will be performing scheduled maintenance on Saturday, December 30th at 11:00 PM CST. The system will be unavailable for 2 hours during this time. If you are logged in at 11:00 PM CST on Saturday, you will receive an error message and may lose data currently being entered. It is very important that you log off prior to 11:00 PM CST this Saturday.</p>tag:status.revolutionehr.com,2005:Incident/195433462023-12-27T14:42:31-06:002023-12-27T14:42:31-06:00Issues with RXNT launch from RevolutionEHR<p><small>Dec <var data-var='date'>27</var>, <var data-var='time'>14:42</var> CST</small><br><strong>Resolved</strong> - RXNT was able to identify an issue with a recent update that is causing issues when launched via SSO (single sign on) from another system. They have rolled back the update causing the problem.</p><p><small>Dec <var data-var='date'>27</var>, <var data-var='time'>09:04</var> CST</small><br><strong>Investigating</strong> - We are currently investigating an issue with RXNT that is preventing the RXNT page from loading when using the "Launch RXNT" button from RevolutionEHR. We have also reached out to RXNT. All updates will be posted here when new information is available.</p>tag:status.revolutionehr.com,2005:Incident/194500922023-12-19T08:14:39-06:002023-12-19T08:14:39-06:00Scanning integration update<p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>08:14</var> CST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>15:57</var> CST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>13:06</var> CST</small><br><strong>Identified</strong> - The issue has been identified.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>08:40</var> CST</small><br><strong>Investigating</strong> - We are receiving reports of a trial key error with the scanning integration update and we are currently investigating this error.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>13:31</var> CST</small><br><strong>Monitoring</strong> - We will continue to monitor.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>12:51</var> CST</small><br><strong>Update</strong> - Clearing cache appears to fix this issue but if you still experience the issue contact support. https://help.revehr.com/hc/en-us/articles/360035874154-Contact-Customer-Support<br /><br />How to clear computer cache-https://help.revehr.com/hc/en-us/articles/360039706874-Clear-Computer-Cache</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>10:36</var> CST</small><br><strong>Investigating</strong> - We are aware that some customers are experiencing issues with the scanner update from last night and our engineers are investigating the issue and updates will be posted as they are available</p>tag:status.revolutionehr.com,2005:Incident/194023032023-12-14T02:00:15-06:002023-12-14T02:00:16-06:00System Maintenance December 13th US Only<p><small>Dec <var data-var='date'>14</var>, <var data-var='time'>02:00</var> CST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>23:00</var> CST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>09:54</var> CST</small><br><strong>Scheduled</strong> - We will be performing scheduled maintenance on Wednesday, December 13th at 11:00 PM CDT. The system will be unavailable for 3 hours during this time. If you are logged in at 11:00 PM CDT on Wednesday, you will receive an error message and may lose data currently being entered. It is very important that you log off prior to 11:00 PM CDT this Wednesday.</p>tag:status.revolutionehr.com,2005:Incident/193387512023-12-05T17:00:30-06:002023-12-05T17:00:30-06:00Reports of lagging in RevolutionEHR<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>17:00</var> CST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>14:48</var> CST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>13:50</var> CST</small><br><strong>Investigating</strong> - We are currently investigating the cause of some recent reports of lagging in the system. We will provide an update here as soon as more information becomes available</p>tag:status.revolutionehr.com,2005:Incident/186019142023-09-25T13:13:23-05:002023-09-25T13:13:23-05:00Reports of lagging in RevolutionEHR<p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>13:13</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved. Additional information will be provided in the post mortem</p><p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>11:24</var> CDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>10:46</var> CDT</small><br><strong>Identified</strong> - We believe we have identified the cause of the issue and are working to confirm and resolve</p><p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>09:58</var> CDT</small><br><strong>Investigating</strong> - We are currently investigating the cause of some recent reports of lagging in the system. We will provide an update here as soon as more information becomes available</p>tag:status.revolutionehr.com,2005:Incident/185566202023-09-20T10:09:25-05:002023-09-20T10:09:25-05:00RXNT is experiencing a partial outage<p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>10:09</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>09:48</var> CDT</small><br><strong>Identified</strong> - The following message was sent to RevolutionEHR from RXNT: Customers are experiencing a partial system outage impacting EHR/ERx products. This issue has been flagged as a priority 1 issue, which means our engineering team will work around the clock until the issue is resolved.</p>tag:status.revolutionehr.com,2005:Incident/179467442023-09-18T11:14:01-05:002023-09-18T11:14:01-05:00Attention RevDirect Users Only: RevDirect partner is currently unable to add new RevDirect addresses<p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>11:14</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>27</var>, <var data-var='time'>16:12</var> CDT</small><br><strong>Update</strong> - Secure Exchange Solutions is still actively working to resolve this issue, we do not have any new updates from them at this time, but will post information as it becomes available</p><p><small>Jul <var data-var='date'>24</var>, <var data-var='time'>10:43</var> CDT</small><br><strong>Investigating</strong> - RevolutionEHR users are receiving an error when attempting to create new RevDirect addresses. We are currently working with Secure Exchange Solutions to resolve the issue and will post any updates as they become available at the end.</p>tag:status.revolutionehr.com,2005:Incident/185039342023-09-15T08:33:26-05:002023-09-15T08:33:26-05:00TAB Syncing Issue<p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>08:33</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>14</var>, <var data-var='time'>16:37</var> CDT</small><br><strong>Monitoring</strong> - We are monitoring this at this time.</p><p><small>Sep <var data-var='date'>14</var>, <var data-var='time'>14:31</var> CDT</small><br><strong>Investigating</strong> - We have been receiving reports of issues with TAB syncing today. Anyone experiencing this issue should start all Encounters directly in RevolutionEHR. Until this issue has been resolved, it's recommended all Appointments, with the appropriate Subcategory, be scheduled directly in RevolutionEHR. <br /><br />An update will be posted as more information becomes available.</p>tag:status.revolutionehr.com,2005:Incident/181430912023-08-14T12:10:13-05:002023-08-14T12:10:13-05:00Application Performance Issue<p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>12:10</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>11:39</var> CDT</small><br><strong>Monitoring</strong> - The performance issue has been resolved, but our engineering team will continue to monitor.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>11:23</var> CDT</small><br><strong>Investigating</strong> - We are aware of an issue that is impacting application performance. Our engineers are currently investigating the cause.</p>tag:status.revolutionehr.com,2005:Incident/180237082023-08-01T17:48:41-05:002023-08-01T17:48:41-05:00Delay in reports and claim status<p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>17:48</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>14:21</var> CDT</small><br><strong>Investigating</strong> - There is currently a delay of approximately 10-15 minutes as it relates to reports which also includes claim status. Any new data entered can take up to 15 minutes to appear in an associated report and any change in claim status will also be delayed. For example, authorizing an invoice may take up to 15 minutes for the claim to appear in the Claims to Submit list.</p>tag:status.revolutionehr.com,2005:Incident/180135282023-07-31T16:16:46-05:002023-07-31T16:16:46-05:00Attention US Customers: Delay in reports and claim status<p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>16:16</var> CDT</small><br><strong>Resolved</strong> - All delays have been resolved</p><p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>15:17</var> CDT</small><br><strong>Update</strong> - Current delay is approximately 10 to 12 minutes.</p><p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>14:33</var> CDT</small><br><strong>Investigating</strong> - There is currently a delay of approximately 6 minutes as it relates to reports which also includes claim status. Any new data entered can take up to 6 minutes to appear in an associated report and any change in claim status will also be delayed. For example, authorizing an invoice may take up to 6 minutes for the claim to appear in the Claims to Submit list.</p>tag:status.revolutionehr.com,2005:Incident/179034032023-07-19T17:30:14-05:002023-07-19T17:30:14-05:00Delay in reports and claims status<p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>17:30</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>16:31</var> CDT</small><br><strong>Update</strong> - A resolution has been applied, however delays remain between 15 and 20 minutes. As demand decreases, the reporting servers will begin to catch up more quickly. We will continue to post updates as it improves.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>14:06</var> CDT</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>13:56</var> CDT</small><br><strong>Investigating</strong> - There is currently a delay of approximately 10 to 15 minutes as it relates to reports which also includes claim status. Any new data entered can take up to 10 to 15 minutes to appear in an associated report and any change in claim status will also be delayed. For example, authorizing an invoice may take up to 15 minutes for the claim to appear in the Claims to Submit list.</p>tag:status.revolutionehr.com,2005:Incident/178804962023-07-18T09:42:21-05:002023-07-18T09:42:21-05:00Application Performance Issue<p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>09:42</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>14:21</var> CDT</small><br><strong>Monitoring</strong> - The performance issues have been resolved, but our engineering team will continue to monitor.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>12:31</var> CDT</small><br><strong>Investigating</strong> - We are aware of an issue that is impacting application performance. Our engineers are currently investigating the cause. <br /><br />More information will be posted as it becomes available.</p>tag:status.revolutionehr.com,2005:Incident/177305232023-06-30T16:37:02-05:002023-06-30T16:37:02-05:00Slow response time<p><small>Jun <var data-var='date'>30</var>, <var data-var='time'>16:37</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>30</var>, <var data-var='time'>10:40</var> CDT</small><br><strong>Monitoring</strong> - Stability has been restored and we will continue to monitor</p><p><small>Jun <var data-var='date'>30</var>, <var data-var='time'>10:33</var> CDT</small><br><strong>Investigating</strong> - We are seeing slower response times in RevolutionEHR. The team is working to restore normal response times</p>tag:status.revolutionehr.com,2005:Incident/176880152023-06-26T11:58:16-05:002023-06-26T11:58:16-05:00VisionWeb is currently down<p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>11:58</var> CDT</small><br><strong>Resolved</strong> - VisionWeb has reported that their site is now back up and functioning as expected.</p><p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>11:26</var> CDT</small><br><strong>Identified</strong> - No new information is available at this time. VisionWeb has followed up that they are working to resolve this issue as quickly as they can.</p><p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>08:13</var> CDT</small><br><strong>Investigating</strong> - We have received notice from VisionWeb that there site is currently down. This will cause an error in RevolutionEHR when trying to open, edit or create an optical order where VisionWeb is selected as the processor. Currently VisionWeb does not have an ETA on a resolution but we will post any additional information as we receive updates from VisionWeb</p>