As a cloud-based service, RevolutionEHR has minimal technology requirements for the office. The main items to review are the amount of memory on your computers and the actual internet speed you are achieving through your Internet Service Provider. We highly recommend you review those two areas and the items listed below before going live with RevolutionEHR.

Hardware Requirements
As an internet application, the only hardware requirement to concern yourself with relates to your devices. We recommend:

• 4GB of RAM minimum
• 2.3GHz processor (1.8GHz processor minimum)
• Minimum 17″ monitor / 19″ wide-screen monitor, with high resolution setting (A larger screen provides a better user experience and faster operations due to less scrolling)

Supported Browsers
RevolutionEHR is designed to work with the latest version of any internet browser that supports Adobe Flash. We support operating with the following browsers:

• Google Chrome (latest version available for free at www.google.com/chrome/browser/)
• Mozilla Firefox (latest version available for free at www.mozilla.org/en-US/firefox/new/)
• Apple Safari (latest version available for free at www.apple.com/safari/)
• Microsoft Edge (latest version available for free at www.microsoft.com/en-us/windows/microsoft-edge)

Software Requirements
RevolutionEHR requires the latest version of the following software to be installed on all computers:

• Adobe Flash Player (latest version available for free at www.adobe.com)
• Adobe Reader (latest version available for free at www.adobe.com)
• Spreadsheet application (for accessing various data files which can be exported from RevolutionEHR)

Internet Speed Requirements
A critical area to analyze before implementing RevolutionEHR is the actual internet speed you are achieving in your office. Faster internet speed will result in better application performance. RevolutionEHR recommends:

• Minimum internet download speed of 4 Mb/s
• Minimum internet upload speed of 512Kb/s

The service level you purchase from your Internet Service Provider will define the download and upload speed but you want to analyze the actual speed you are achieving. There can be any number of reasons that cause you to achieve lower rates than those quoted by your ISP.

Your internet speed can be tested for free at http://speedtest.net. If you need assistance with running the tests or analyzing the data, contact RevolutionEHR customer service.

To view a PDF version of the RevolutionEHR System Requirements, click here

Apex has informed us that integration with RevolutionEHR has been restored. We are continuing to monitor the situation and will provide any further updates as needed.

We received a message from Apex that an update they performed last night has caused some provider’s log in credentials to stop working, which would prevent RevolutionEHR users from submitting claims through Apex. Apex is currently investigating the issue.

We will provide updates as we receive them from Apex.

Integration between Trizetto and RevolutionEHR has been restored. We are continuing to monitor the situation and will provide any further updates as needed.

Our engineers are investigating an issue with the Trizetto integration in RevolutionEHR that causes an error to display when submitting a claim. We are working with Trizetto to resolve this issue.

Some RevolutionEHR users may experience an error when printing encounters after the latest release. Our engineers are working to resolve this issue and release a patch.

Further updates will be posted to INSIGHT as more information becomes available.

RevolutionEHR is operating normally.

RevolutionEHR is operating normally.

A small subset of users are experiencing application performance issues. Our servers are currently functioning normally.

We are aware of application performance issues that are being affected in part by internet outages. We are investigating the issue and will update with more information.

Our engineers are investigating user reports of application performance.

Our engineers have resolved the issue and verified that access to RevolutionEHR in Canada has been restored.

We apologize for any inconveniences this may have caused.

Our engineers are aware of and investigating an issue affecting access to RevolutionEHR in Canada.

We will provide prompt updates as more information becomes available.

Our engineers have resolved the issue and verified that access to RevolutionEHR in Canada has been restored.

We apologize for any inconveniences this may have caused.

Our engineers identified the cause affecting access to RevolutionEHR in Canada and are implementing a fix.

We will continue to provide updates as more information becomes available.

Our engineers have identified a possible cause affecting access to RevolutionEHR in Canada and are working to implement a fix.

We will continue to provide updates as more information becomes available.

Our engineers are aware of and continue to investigate an issue affecting access to RevolutionEHR in Canada.

We will continue to provide updates as more information becomes available.

Our engineers are aware of and investigating an issue affecting access to RevolutionEHR in Canada.

We will provide prompt updates as more information becomes available.

Our engineers continue to see improved conditions and have confirmed the issue is resolved. If you continue to have issues uploading files, downloading files or printing please feel free to contact customer service.

We apologize for any inconvenience this may have caused.

Our engineers identified the cause of the issue and have implemented a fix.

We will continue to monitor the situation and post regular updates as more information becomes available.

This morning, our engineers are investigating an issue that is preventing printing and uploading files within RevolutionEHR.

An update will be posted as more information becomes available.

Based on our monitoring of the nationwide connectivity issue affecting multiple internet providers, it appears that connectivity has been restored. RevolutionEHR users should see their access to the application return to normal.

Based on our monitoring of the nationwide connectivity issue affecting multiple internet providers, it appears that connectivity is being restored. RevolutionEHR users should begin to see their access to the application return to normal.

We will continue to monitor the connectivity issues effecting our users and will provide updates as necessary.

Many users across the United States and Canada are experiencing internet connectivity issues with a variety of providers. This is impacting some RevolutionEHR users attempting to access the application. If you have a backup internet option, using that may provide better service until connectivity is restored.

We will continue to update insight as we have more information.

We recently made an update to myRev on Apple devices such as the iPhone and the iPad. It has been reported that users cannot successfully login until a Locale is selected. To update Locale, click on Settings on the login screen, choose your Locale (US or Canada) and Save. This setting will be saved for future logins. Once this is set you will be able to successfully login.

RevolutionEHR performance has returned to normal. Our engineers were able to determine the cause of the issue and restore application performance. We will continue to monitor the situation and post any updates as needed.

We are aware of an application issue that is impacting application performance. Our engineers are currently investigating the cause. More information will be posted to INSIGHT as it becomes available.

Our engineers have identified the issue with RevAssistant and pushed a fix. You should refresh the browser; the first time you launch RevAssistant you will then be prompted for the update. If you are not prompted for an update or still see an error, manually updating will solve the issue. If you have any questions, please contact customers support.

We are aware of an issue with RevAssistant. Our engineers are currently working to resolve the issue.

Integration between Trizetto and RevolutionEHR has been restored. If you have any questions, please contact customer support.

We are aware of an issue with Trizetto integration with RevolutionEHR. Trizetto is currently investigating the cause.

Integration between Solutionreach and RevolutionEHR has been restored.

If you are still experiencing any syncing issues, it is recommended by Solutionreach that you contact their customer support directly so they can assist you with restoring the sync.

Solutionreach is currently experiencing an outage that may affect their ability to sync information from RevolutionEHR, as well as other integrated PMS systems. Solutionreach is working to resolved this as quickly as possible.

There is also the possibility that a recent update from Solutionreach may be incompatible with some anti-virus programs, which would also impact syncing.  If you are experiencing any syncing issues after their current outage is resolved, it is recommended by Solutionreach that you contact their customer support directly so they can assist you with restoring the sync.

We are aware of an issue with Solutionreach integration where data from RevolutionEHR is not being properly synced for some practices. Solutionreach is aware of the issue and is currently working on a fix. We are working closely with Solutionreach and will offer updates once we have more information.

We are aware of an application performance issue affecting a subset of customers. Our engineers are currently investigating the cause. More information will be posted to INSIGHT as it becomes available.

Integration between Demandforce and RevolutionEHR has been restored. If you have any further questions, please contact customer support.

We are aware of an issue with Demandforce integration where data from RevolutionEHR is not being properly synced. Demandforce is aware of the issue and is currently testing a fix. We are working closely with Demandforce and expect a solution shortly.

Our engineers have found an issue with the aging report. When running the aging report for today’s date, the results are not including historical invoices. The team has determined the cause of the issue and will be deploying a patch tonight to remedy it. We suggest that you wait until tomorrow to run any aging reports to ensure the results are accurate.

Our engineers have implemented a resolution to fix the reporting server performance issue, which has resulted in reporting server performance returning to normal. If you are still experiencing application errors or slow performance, we recommend that you logout, clear your browser cache and login.

Our engineers have implemented a resolution to fix the reporting server performance issue. If you are still experiencing application errors or slow performance, we recommend that you logout, clear your browser cache and login.

Our engineers are aware of and working to resolve an issue with our reporting servers that is affecting reporting requests and performance.

At this time RevolutionEHR performance has returned to normal. We will continue to monitor the situation and post any updates as needed.

We are aware of an application performance issue affecting a subset of customers. Our engineers are currently investigating the cause. More information will be posted to INSIGHT as it becomes available.

We have an update on the issues affecting application performances. Our engineers have identified certain long-running processes that are consuming higher than normal server resources, which is causing slow response times for a small subset of users. The current application performance issues have been resolved and our engineers are working on a solution to the issue.

We are aware of an application performance issue affecting a subset of customers. Our engineers are currently investigating the cause. More information will be posted to INSIGHT as it becomes available.

At this time RevolutionEHR performance has returned to normal. We will continue to monitor the situation and post any updates as needed.

We are investigating user reports regarding application performance. More information will be posted to INSIGHT as it becomes available.

At this time RevolutionEHR performance has returned to normal. Our engineers are still looking into the root cause. We will continue to monitor the situation and post any updates as needed.

We are investigating user reports regarding application performance. More information will be posted to INSIGHT as it becomes available.

At this time RevolutionEHR performance has returned to normal. Our engineers are still looking into the root cause. We will continue to monitor the situation and post any updates as needed.

We are continuing to investigate an application performance issue that some users are reporting. We will post updates as soon as further information becomes available.

Last night, April 20^th, we released a patch to address the scanning integration issue with Google Chrome and to ensure future integration compliance with other supported browsers. When you first visit the scanning module, you will be prompted to download and install the new TWAIN driver. You can find full instructions here: https://insprorevehr.wpengine.com/?p=18829

If you have any further questions, please contact support.

We will be releasing an update tonight, April 20^th, to address the scanning integration issue with Google Chrome and to ensure future integration compliance with other supported browsers. Even if you are not experiencing issues now, there are a few steps that must be taken for scanner integration to work properly as well as steps that need to be performed after the update.

• All users need to ensure they are running the latest version of a supported browser. Instructions
• After the release, all users of scanning integration will be prompted to download the latest version of Dynamic Web TWAIN software.
• The first time the scanner integration is used, you will be prompted to install the newest TWAIN software. SAVE THE FILE. After saving the file, right click the file or icon and select to run as Administrator. this will ensure you have full permissions to run and use the program.

Google Chrome performed an update that affected our scanning integration when using Chrome. The appropriate adjustments were planned for our upcoming release in anticipation of the Chrome update. We are now working to provide those adjustments ahead of schedule. We will keep you informed related to the timing. In the interim you can use a browser other than Google Chrome for scanning integration.

Our data center engineers discovered and resolved a network traffic routing issue that was affecting connection speed and overall system performance for some users. Customer support is currently contacting any practice that reported this issue to confirm that performance has returned to normal.

If you are still experiencing issues, please contact customer support for further assistance.

We are working on an issue that is affecting approximately 5% of our customers. We have not yet been able to pinpoint an exact solution that will resolve this for everyone that is affected.

Our engineers are working with the support team and joining calls with customers to lend their expertise. As soon as we have a solution we will send it out to everyone that is experiencing problems.

We are aware that some customers are still experiencing application performance issues. We continue working with the effected customers to remedy the issue as quickly as possible. We will be posting updates to insight as they become available.

Customer support has identified a solution for the application performance issue some customers experienced. This issue was based on specific configuration settings on the effected customer’s local computers. If you are experiencing poor application performance, please contact customer support at 877-738-3471 ext 2 or customersupport@revolutionehr.com and a representative will work with you directly to solve your issue.

Our engineers continue to investigate an application performance issue that some users are reporting. We are working together with data center engineers to get to the bottom of this issue. We will post updates as soon as further information becomes available.

We are continuing to investigate an application performance issue that some users are reporting. We will post updates as soon as further information becomes available.

Our engineers are investigating application performance reports that some users are reporting.  We will post here as we have more information.  Please contact customer support at customersupport@revolutionehr.com if you are experiencing difficulty with application performance this morning.

Application performance has been restored. One of our service providers experienced a brief performance issue that has been resolved.

We are aware of application performance issues affecting Canadian customers and are investigating the issue. More information will be posted to INSIGHT as it becomes available.

At this time all aspects of RevolutionEHR have returned to normal operation. Our engineers are still looking into the root cause. We will continue to monitor the situation and post any updates as needed.

We are investigating user reports regarding application performance. More information will be posted to INSIGHT as it becomes available.

At this time all aspects of RevolutionEHR appear to be operating normally and Amazon has confirmed full restoration of their services.

If you are still having issues, please do not hesitate to contact Customer Support.

At this time all aspects of RevolutionEHR appear to be operating normally. While Amazon’s service has been restored we are still waiting on a final update from Amazon indicating the service has returned to normal. We will continue to monitor and provide updates as they become available.

If you are still having issues, please do not hesitate to contact Customer Support.

We are seeing indications that Amazon’s service is being restored. We will continue to monitor progress and provide updates as they become available.

Amazon believes they have found the root cause and are working hard to restore service. Our engineers are monitoring the situation and we will continue to keep you up to date as we have more information. We do not currently have an ETA on a solution from Amazon.

Amazon, who provides our file hosting services, is experiencing a major outage. This outage is effecting all files hosted within RevolutionEHR including PDFs, doctor’s signatures, and patient images. Our engineers are monitoring the situation and we will continue to keep you up to date as we have more information. We do not currently have an ETA on a solution from Amazon.

One of our service providers is experiencing an outage, which is preventing any files from downloading within the RevolutionEHR application. This includes doctors signatures, patient images, PDFs, and any other files hosted within RevolutionEHR. Our engineers are monitoring the situation.

One of our providers continues to experience an outage, which is preventing any files from downloading within the RevolutionEHR application. Our engineers continue to monitor the situation.

Our engineers have determined that the issue concerning file downloads is due to an outage with one of our providers. We are working to remedy the issue.

Our engineers have restored printing services. We are still investigating the issue with file downloads.

We are aware of an issue with downloading any files and printing PDFs. Our engineers are investigating the cause.

Following the recent update by RxNT, some customers were unable to add medications listed in the claims history or fill data into current meds within RxNT and transfer that data to RevolutionEHR. After working together with RxNT on the issue, they have delivered a fix and the RxNT integration is back to normal.

Regarding the issues with printing PDFs and other documents, a problem with one of our data center partners was identified to be the cause of the interruption in downloading and printing functionality. Our engineering team worked with our data center to resolve the issue.

We are aware of an issue with downloading and printing PDFs. Support is finding that clearing the browser cache and refreshing the browser has solved all the issues they’ve seen so far. Please try clearing your cache and if that still hasn’t solved your issue, please reach out to support directly for help with this problem.

We are aware of an issue with RxNT integration where users are not able to add medications listed in the claims history or fill data into current meds within RxNT. We are working together to resolve this issue.

We have reports of a partial internet outage affecting the east coast.

http://downdetector.com/status/level3/map/

Application performance has been restored. Our engineers are still looking into the root cause. We will continue to monitor the situation and post any updates as needed.

We are investigating user reports regarding application performance in the U.S. More information will be posted to INSIGHT as it becomes available.

The Trizetto system maintenance was completed.

Please be aware that our integration with the Trizetto (Gateway EDI) system is temporarily unavailable for claim submission.

If you attempt to login to Trizetto directly, you will see the following message:  “Our system is temporarily unavailable.  Due to vital system maintenance, the TriZetto Provider Solutions website is currently unavailable.  We apologize for any inconvenience and request that you try back at a later time.”

Trizetto’s vital system maintenance is affecting our integration as well.

We are in contact with Trizetto and will provide updates here regarding their system status.

SES (Secure Exchange Solutions), our partner that provides the secure direct messaging technology for RevDirect, has notified us that service has been restored.

If you have any additional issues or concerns, please do not hesitate to contact customer support.

SES (Secure Exchange Solutions), our partner that provides the secure direct messaging technology for RevDirect, is reporting a service interruption.  Any attempts at sending a direct message will likely fail until they resolve the issues they are experiencing with their service.

We will provide updates regarding their service availability.

Trizetto has resolved the issue causing their service interruption.

Trizetto has made us aware that they are experiencing issues receiving claims from RevolutionEHR. When attempting to submit claims, you will see the message Connection Timed Out. Trizetto is working to correct the issue. Please monitor the Trizetto portal for more information.

We are investigating user reports regarding application performance in the U.S. More information will be posted to INSIGHT as it becomes available.

Our engineers have identified the issue that caused performance issues for some customers and confirmed that performance has returned to normal.  If you have any additional issues or concerns, please do not hesitate to contact customer support.

We are aware that some of our customers are still experiencing slow performance. Our engineers are working to resolve the issue. We will post an update as soon as more information becomes available.

We are investigating user reports regarding application performance in the U.S. More information will be posted to INSIGHT as it becomes available.

Trizetto has resolved the issue causing their service interruption.

Trizetto has made us aware that they are experiencing issues receiving claims from RevolutionEHR. When attempting to submit claims, you will see the message Connection Timed Out. Trizetto is working to correct the issue. Please monitor the Trizetto portal for more information.

Our engineers have identified the issue that caused the continued performance issues for some customers following the brief service interruption this morning. Service for all customers returned to normal at approximately 12:20 pm CDT. As always, we will continue to monitor performance and provide information on INSIGHT as it becomes available.

Following a brief service interruption from 11:49 to 11:54 am CDT we continue to receive sporadic reports of slow performance and error messages. We are currently investigating and will post an update as soon as information becomes available.

Friday was anything but stellar in terms of performance and access to RevolutionEHR. While many of you may have experienced just a few bumps in service, many others experienced ongoing access and performance issues over the course of a few hours with RevolutionEHR.

We owe you an explanation of what happened, how our team responded, and what we are doing to prevent any future interruptions in service.

Please know that there is no higher priority for our team than to provide you uninterrupted access and robust application performance with RevolutionEHR. With any case of compromised system performance or access, we take an all hands on deck approach to completely focus on restoring system performance and access as fast as possible until it is resolved.

So, what happened Friday?

Our release Thursday night went as planned. Early Friday morning we discovered a bug that prevented invoices from being created. The fix was assessed as very low risk to patch, but would require a 2 minute service interruption to implement. Our support team made a compelling argument (that I agreed with) that a 2 minute service interruption mid-morning was a much better solution than subjecting the entire user base to an entire day of not being able to create invoices. The patch was implemented successfully with a very minimal interruption in service.

Completely unrelated to the release and patch, and just a few minutes after the patch was implemented, our engineers were alerted to a hardware failure at our data center that was causing access and performance issues for more and more customers. Our engineers worked with data center engineers to troubleshoot and systematically restore system access to affected users.

As system access was returning to users affected by the hardware failure, somewhat unbelievably, yet another separate hardware failure occurred causing all users to lose access to RevolutionEHR. Our engineers quickly implemented a hardware failover procedure and system access returned to all users in a matter of minutes.

We are working with our data center engineers to identify and limit any potential effects of hardware failures on an ongoing basis.

Please accept our apologies for the interruptions in service you experienced Friday with RevolutionEHR. We are always grateful for your patience as our team works to resolve the unexpected.

Scott A. Jens, OD, FAAO
CEO
RevolutionEHR

We are getting reports that several users now able to access RevolutionEHR at this time. Our engineers continue to investigate and resolve any remaining issues.

Our engineers are aware that most users are unable to access RevolutionEHR at this time. We are investigating and more information will be posted as it becomes available.

Data center engineers have pinpointed the cause of the slow application performance and login issues. Engineers are working to implement a solution as soon as possible.

If you are unable to login at this time, please try refreshing your browser.

Our engineers are actively working with data center engineers to determine the cause and solution to slow application performance and system access.

Our engineers are investigating application performance issues that many are experiencing. More information will be posted to INSIGHT as it becomes available

An issue has been discovered with the latest release causing an error when an invoice is created for a patient that has a guarantor set in demographics or a transfer is made to that patient.

Since this is likely to impact your practice significantly, our engineers will be implementing a fix at 9:45 am CDT. The update will require a 5 minute window where RevolutionEHR will not be accessible.

With the new release, an error will occur when an invoice is created for a patient that has a guarantor set in demographics or a transfer is made to that patient. Our engineers are currently testing a fix and will issue an update as soon as possible. More information will be posted to INSIGHT as it becomes available.

The release of RevolutionEHR 6.2.18 has been completed. The system is now available.

For more information regarding this release, please click here.

The release of RevolutionEHR 6.2.18 is currently in progress. The system will be unavailable for approximately 4 hours beginning at 11:00pm CDT. If you are logged in at 11:00pm CDT on September 29th, you will receive an error message and may lose data currently being entered.
For more information regarding this release, please click here.

Our engineers have resolved the issue related to file uploads/downloads and printing. If you have any additional issues or concerns, please do not hesitate to contact customer support.

Users in the U.S. may be experiencing issues with uploading/downloading files and printing reports. Our engineers are aware of the issue and working towards a resolution.

The issue causing error messages when attempting to submit claims through Trizetto has been resolved.

Some RevolutionEHR users may be experiencing an error message when submitting claims through Trizetto. Trizetto is aware and is working to resolve the issue as soon as possible. More information will be posted to INSIGHT as it becomes available.

Our engineers have applied a patch to the Optical Summary screen to address application performance. If you are able to log out of RevolutionEHR and log back in this will apply the new patch to your session. As more users perform this action the application performance will gradually return to normal levels.

As always, we will continue to monitor application performance and provide updates when necessary. Thank you for your continued patience.

Our engineers have identified a performance issue related to the use of the optical summary screen.  We are working on a fix that will be implemented as soon as possible.

Our engineers identified several processes that could have impacted application performance and confirmed that performance returned to normal at approximately 3:55pm CDT. As always, we will continue to monitor performance and provide information on INSIGHT as it becomes available.

We are investigating user reports regarding application performance in the U.S. More information will be posted to INSIGHT as it becomes available.

We have applied a fix to resolve the issue related to multiple patient files being open. Feel free to return to your normal process for opening and viewing patient files. We appreciate your patience as we worked to resolve this issue.

If you have any questions or concerns, please do not hesitate to contact customer service.

Our developers are now testing a fix for the issue caused by having multiple patient files open at the same time.

After testing has been completed successfully, a patch will be released as soon as possible. More information regarding the timing of the patch will be posted to INSIGHT as it becomes available.

In the meantime, you can help alleviate the effect of the issue by keeping fewer patient tabs open at the same time.

Our developers have identified the cause of the performance issue that some customers experienced yesterday and are working on a fix. The issue is related to having multiple patient files open at the same time.

While our developers are working on the fix, you can help alleviate the effect of the issue by keeping fewer patient tabs open at the same time.

We’ll be releasing a patch as soon as possible to fix this issue.

Thanks for your patience and our apologies for this temporary inconvenience.

We are investigating user reports regarding application performance. More information will be posted to INSIGHT as it becomes available.

The system maintenance at our Toronto data center was completed by 7:00 am CDT on July 10th.

RevolutionEHR will be performing system maintenance on Saturday July 9th, beginning at 11:00 pm CDT.

The system will be unavailable for approximately 8 hours during this time. If you are logged in at 11:00 pm CDT on July 9th, 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 system maintenance period is required to upgrade infrastructure at our Toronto data center.

If you have any questions, please contact Customer Support.

Engineers at our Canadian Data Center reported that the emergency maintenance was completed in less than a minute and all systems have returned to normal operations.

Canadian Data Center Engineers have notified us that they will be performing Emergency Power Maintenance at 12:00pm CDT. Access to RevolutionEHR may be interrupted briefly and the outage is expected to last less than 5 minutes.

We are currently working with the Data Center to lessen the impact to RevolutionEHR customers and will provide updates when they become available.

TriZetto Provider Solutions was performing system maintenance today, Tuesday, June 7, 2016. As of 3:15 p.m. CST, the send and receive functions are now available on the client website.

Trizetto has reported they are currently performing system maintenance which may affect claim submission and payments. More information will be provided as it becomes available.

Our engineers quickly discovered an issue with a software update process that was the cause of the temporary connectivity issues. It has been resolved. Our apologies for the inconvenience this morning!

Our engineers are troubleshooting reports of sporadic application connectivity issues this morning. We will provide more updates as we have more information.

The issue where some users experienced an error message when printing statements has been resolved.

Some users in the U.S. may be experiencing an error when printing statements and clicking the “Mark Statements Printed” option. Our engineers are working to resolve the issue promptly. More information will be posted to Insight as it becomes available.

The release of RevolutionEHR 6.2.14 has been completed. The system is now available.

For more information regarding this release, please click here

The release of RevolutionEHR 6.2.14 is currently in progress. The system will be unavailable for approximately 4 hours beginning at 11:00pm CDT. If you are logged in at 11:00pm CDT on March 24th, you will receive an error message and may lose data currently being entered.

For more information regarding this release, please click here

Last night, our engineers implemented a configuration change to address the performance issues and application errors you may have experienced at various times during the day yesterday.

Our performance monitoring continues to affirm that the configuration change was successful.

We appreciate your patience as we continue the process of implementing our enhanced infrastructure to better serve you – and please accept our apologies for any disruption in service you and your practice may have experienced yesterday.

If you continue to experience any performance issues or application errors today, please contact Customer Support.

System Maintenance in the U.S. has been completed.

We are currently performing system maintenance in the U.S. which began at 11:00pm CST and will be complete by 1:00am CST. If you are logged in after 11:00 pm CST tonight, 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.

We appreciate your patience as we prepare tonight to resolve the configuration issue that has caused sporadic performance issues and errors this afternoon. Resolving the issue requires a significant enough downtime for all users that we chose not to implement during working hours.

Our engineers are aware of the current performance issues and are preparing the resolution which will be implemented during the maintenance period tonight at 11:00 CST.

Our engineers identified a configuration issue that may cause periods of slow performance this afternoon.

We are scheduling a maintenance window TONIGHT beginning at 11:00pm CST until 1:00am CST to resolve this configuration issue. If you are logged in at 11:00 pm CST tonight, 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.

RevolutionEHR completed all system maintenance by 1:00 am CST.

This system maintenance period was required to implement the next step in our planned infrastructure upgrades.

RevolutionEHR will be performing system maintenance on Thursday March 3rd, beginning at 11:00 pm CST.

The system will be unavailable for approximately 2 hours during this time. If you are logged in at 11:00 pm CST on March 3rd, 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 system maintenance period is required to implement the next step in our planned infrastructure upgrades after successfully completing a significant upgrade this past Sunday.

If you have any questions, please contact Customer Support.

As of 3:00pm CST the performance issue reported earlier has been resolved. Our engineers continue to monitor for any additional changes to the performance of RevolutionEHR.

Our engineers are aware of and investigating a performance issue for users in the U.S. We will provide more information as it becomes available.

Our engineers are reporting significant improvements in performance and will continue to monitor for any additional changes.

Our engineers are aware of and investigating a performance issue for users in the U.S. We will provide more information as it becomes available.

RevolutionEHR users in Canada are now able to access all functions of RevolutionEHR. If you continue to experience any issues with RevolutionEHR, please do not hesitate to contact customer service.

Reporting for RevolutionEHR customers in Canada is functioning normally at this time. Some integrations may still be impacted and our engineers continue the work to resolve this issue.

Our engineers have resolved an issue causing an error message when attempting to login to RevolutionEHR in Canada. Certain reports and integrations may still be impacted and engineers continue to work to resolve the issue.

Our engineers have identified an issue affecting RevolutionEHR users in Canada. We are actively working to resolve the issue and more information will be posted as it becomes available.

RevDirect Messages are now being transmitted and received properly. Any DIRECT messages that were transmitted to RevolutionEHR customers during this period were queued and will be delivered shortly.

If you continue to experience issues sending or receiving RevDirect messages, please contact customer support.

Our engineers are currently investigating an issue with RevDirect messages not being transmitted. You may receive an error message when sending a message through RevDirect. More information will be posted as it becomes available.

Many customers in the U.S. are reporting success connecting to RevolutionEHR at this time.

Our engineers have confirmed that the disruption in service that some users experienced today was caused by a configuration change at the data center to prepare for further updates overnight. We apologize for the disruption and have taken necessary steps with data center engineers to ensure such work is not performed during practice hours.

Some customers in the U.S. are reporting issues connecting to RevolutionEHR. Data Center engineers are investigating a regional internet issue as a potential cause. More information will be posted as it becomes available.

Our engineers continue to monitor application performance and are reporting a significant improvement over conditions experienced earlier in the day.

Our engineers are reporting continued improved performance indicators since the connectivity and slowness issues that were reported earlier.

Our engineers continue to investigate the connectivity or slowness issues that have been reported by RevolutionEHR users.

Some users may be experiencing issues connecting to RevolutionEHR or slowness when using the application. Our engineers are currently investigating these reports. More information will be posted as it becomes available.

Many RevolutionEHR users are reporting success accessing the software. Our engineers will continue to actively monitor and more information will be posted as it becomes available.

Our engineers quickly identified the cause of the connectivity issues some users are experiencing and are working to resolve the issue. At this time, several users are reporting success accessing the system but engineers will continue to monitor.

Some users in the U.S. have reported issues connecting to RevolutionEHR. Our engineers are currently investigating and working to resolve the issue as soon as possible. More information will be posted as it becomes available.

Our data center engineers have resolved the connectivity issues a small number of RevolutionEHR customers may have experienced.

If you continue to have any issues connecting to RevolutionEHR, please contact customer support.

Data center engineers are working to completely resolve the connectivity issues a small number of RevolutionEHR customers may have experienced overnight. We do not believe RevolutionEHR customers are impacted at this time but engineers are actively monitoring infrastructure resources.

If you do experience connectivity issues, please contact customer support.

Data center engineers have identified the cause of the reported connectivity issues, work to resolve the issues is in progress.

Beginning at approximately 10:15 pm CST some users may be experiencing issues connecting to RevolutionEHR. Our data center engineers are currently investigating and more information will be posted as it becomes available.

Our data center engineers in Canada informed us that another site at the center experienced a distributed denial of service attack at approximately 10:49am CST. While this attack was not directed at RevolutionEHR, infrastructure resources used by RevolutionEHR were affected which was the cause of a brief service disruption which lasted until approximately 10:57am CST.

Data center engineers resolved the service disruption by separating RevolutionEHR from these shared resources.

All Canada based systems are now available. Our data center engineers continue to monitor and investigate the cause of the two brief disruptions in service that occurred this morning. More information will be posted as it becomes available.

RevolutionEHR engineers are aware of and troubleshooting a service interruption for Canadian customers that occurred at 10:49 am CST. More information will be posted as it becomes available.

All Canada based systems are now operating normally.  Our data center engineers are investigating the cause of the very brief disruption in service.

Our engineers are aware of and troubleshooting a service disruption for Canadian customers.  We will provide updates as we work to resolve the problem.

RevolutionEHR engineers have identified the cause of the service interruption for Canadian customers and the issue has been resolved.

We understand the impact these interruptions have on your practice and apologize for any inconvenience this may have caused.

RevolutionEHR engineers are aware of and troubleshooting a service interruption for Canadian customers. More information will be posted as it becomes available.

Our engineers have implemented a resolution for the appointment syncing issue with TAB which has been affirmed by customers who were experiencing the issue.

If you continue to experience appointment syncing issues with TAB, please contact customer support.

Our engineers have implemented a series of resource configuration changes and updates, including a patch over night, to resolve the connectivity issues some customers experienced Monday afternoon.

We will continue to monitor related performance and connectivity and adjust resources as necessary.

If you experience slowness or connectivity issues please contact customer support.

Additional infrastructure resources were configured overnight and engineers are actively monitoring the performance.

A small portion of RevolutionEHR customers may have experienced slowness or connectivity issues around 1:35pm CST but these issues have since been resolved.

If you continue to experience slowness or connectivity issues please contact customer support.

Our engineers reconfigured the application resources that were causing slowness and connectivity issues.  Performance monitoring and positive customer feedback indicate the issues with the affected application resources have been resolved.

RevolutionEHR and Data Center Engineers are working to reconfigure application resources that may be causing slowness and connectivity issues. This reconfiguration will take place at 4:00pm CST and will cause some RevolutionEHR customers to be briefly disconnected and receive an error message.

If you are disconnected, please wait up to 5 minutes and refresh your browser to reconnect to RevolutionEHR.

RevolutionEHR and Data Center Engineers are working to reconfigure application resources that may be causing slowness and connectivity issues. This may cause some RevolutionEHR customers to be disconnected and receive an error message.

If you are disconnected, please wait a minute and refresh your browser to reconnect to RevolutionEHR.

Some RevolutionEHR customers in the U.S. are reporting slowness and connectivity issues when using RevolutionEHR. Our engineers are actively investigating this issue and more information will be posted as it becomes available.

Our engineers are working with the TAB team to investigate an issue with appointment syncing between TAB and RevolutionEHR.  We will provide updates as we understand more.

RevolutionEHR 6.2.12 was successfully released and is now available.

This release brings several enhancements and fixes to RevolutionEHR, to learn more click here.

The release of RevolutionEHR 6.2.12 began at 11:00pm CST and the system will be unavailable for approximately 2 hours.

If you are logged in, you will receive an error message and may lose data currently being entered. It is very important that you log off at this time.

RevolutionEHR customers in the southeast U.S. have reported that all connectivity issues have been resolved.

At approximately 12:20 pm CST, data center engineers identified an external internet backbone provider failure which was impacting the availability of RevolutionEHR as well as other web services to customers in the Southeast U.S.

After data center engineers diverted traffic through other providers, RevolutionEHR availability was immediately restored to those affected customers. Our data center engineers are investigating the cause of this external failure and will be implementing protocols to reduce the effects of external provider failures in the future.

Some RevolutionEHR customers in the Southeast U.S. are reporting connectivity issues to RevolutionEHR and Insight. RevolutionEHR engineers have confirmed that internal systems are operating normally and are in contact with our Data Center to investigate the issue.

More information will be posted as it becomes available.

RevolutionEHR engineers have confirmed the RevDirect service is now operating normally. If you continue to have any issues, please do not hesitate to contact customer service.

RevDirect is currently unavailable and sending a Direct provider-to-provider message may result in an error message being displayed. RevolutionEHR engineers are in active communication with our Direct messaging provider to receive updates on when the issue will be resolved. More information will be posted as it becomes available.

Please note this does not affect internal office messages or patient to provider messages from RevolutionPHR.

We have been receiving reports from Verizon and Bright House customers that speed and connection has been improving throughout the day. Internetpulse.com is also showing marked improvement.

We have received confirmation from our data center that all RevolutionEHR servers are operating normally as well as our data center’s network infrastructure. Current indications are that the issue is related to a backbone leading to our data center for Verizon customers. This would also include Bright House customers. A backbone is a principal data route between large interconnected computer networks like an ISP and our data center. At this time the data center engineers continue monitor the situation and will take action as appropriate.

We are receiving reports of spinning clocks and connection errors from customers with Verizon and Bright House Internet Service Providers (ISP).  It appears that there is a connectivity issue for these customers.  We are currently awaiting additional information and will post an update as soon as one is available.

As of 5:30 pm CST on 11/17/15 data center engineers have confirmed that all internet connectivity issues related to Comcast have been resolved.

At approximately 10:10 AM CST, data center engineers were alerted to connectivity issues with Comcast and Time Warner customers.

At approximately 10:27 AM CST, data center engineers made internet routing configuration changes aimed at alleviating these connectivity issues and will continue to monitor the situation. Systems appear to be operating normally at this time. If you are still experiencing connectivity issues, please contact customer support.

RevolutionEHR users are currently reporting issues accessing the software. Engineers are currently evaluating the situation and more information will be posted as soon as it becomes available.

Some RevolutionEHR customers are reporting slow connectivity. At this time the data center has reported that all internal systems are operating normally but there are indications of regional internet backbone issues. This likely affects access to different websites based on internet routing, not just RevolutionEHR but it may appear that some sites are working properly while others are not.

Internet Health Report is reporting several internet backbone issues at the current time. Data center engineers are monitoring the situation. Another update will be posted as soon as more information becomes available.

CabMD has reported that their service is now available. If you continue to have any issues submitting claims to CabMD, please contact customer support.

CabMD has reported that their service is currently unavailable. RevolutionEHR customers in Canada may see errors when submitting claims as a result of this disruption. Our team is in communication with CabMD and an update will be posted as soon as it is made available.

Our engineers are monitoring system load and all indications are that the system continues to operate normally.

According to http://internethealthreport.com the internet backbone issue reported earlier has been resolved. Data Center engineers will continue to monitor and take action if needed.

Our engineers continue to monitor system load and all indications are that the system continues to operate normally.

According to http://internethealthreport.com some practices using certain ISPs may be experiencing issues accessing RevolutionEHR due to packet loss occurring between two internet backbones. Data Center engineers continue to monitor and will optimize the routing of internet traffic where possible.

Our engineers are proactively working to optimize internal network traffic. System load is trending downward for the time being and all indications are that the system is operating normally.

Our engineers continue to monitor the status of RevolutionEHR, system load is higher than normal but all indications are that the system is operating normally.

Our engineers continue to monitor the status of RevolutionEHR and are playing close attention to any issues that might arise. System load is higher than normal but all indications are that the system is operating normally.

Our engineers are aware of and investigating application performance this am.  Updates will be posted regularly as we work to resolve.

Today we received several user reports of slow application performance.   Our data center and application engineers have been focused on troubleshooting, diagnosing and addressing the issues reported. Here is a summary of their findings and our plans for moving forward.

We experienced a much higher than average amount of system activity for a Monday. This abnormally high level of system activity resulted in our database servers having to work harder than usual to serve requests and fell behind at times.

We regularly analyze our system load to ensure that our overall application server and database architecture is scaled and tuned to stay ahead of our continued growth as we add new users to our community each day.

While we don’t anticipate the level of activity we experienced today to be the norm, we are escalating the timeline on some of our planned system enhancements to further scale the system for growth. These planned scaling enhancements include a variety of ongoing database optimizations, data routing strategies, additional hardware, increased storage performance and increased network connectivity.

We will continue monitoring system performance and will keep you updated with our progress.

We apologize for the inconvenience to you and your practice today.

Our engineers are investigating user reports about application performance.  We will post updates as we have more information.

Our marketing website, revolutionehr.com, is currently unavailable. Access to RevolutionEHR is unaffected and can still be utilized by navigating directly to https://revolutionehr.com/pms/ to login.

Data Center engineers are currently working to resolve the issue and more information will be provided as it becomes available.

Practices utilizing Time Warner as their internet service provider are now reporting that connectivity to RevolutionEHR has been restored. Time Warner has not confirmed the exact issue but seems to have the issue resolved.

If you continue to have any issues connecting to RevolutionEHR, please contact customer support.

We have received several reports that practices in the North Carolina area are not able to connect to RevolutionEHR despite being able to access other websites.  All practices reporting issues utilize Time Warner as their internet service provider.

RevolutionEHR systems are operating normally, however data center engineers will continue to monitor the situation and if possible will re-route traffic to minimize impact to practices. More information will be provided as it becomes available.

The PHR in the U.S. and Canada, along with myRev in Canada are now available.

The patient portal in both U.S. and Canada, along with myRev access in Canada are currently unavailable. RevolutionEHR engineers are working to restore access and Insight will be updated as more information becomes available.

As of 9/3/15 at 8:30am CDT patches have been released to all practices that should resolve the following:

• Delay when clicking the ‘Add’ button to search for a diagnosis code.
• Delay when loading messages.
• RevDirect Messages not being sent or received.
• In the scheduling pod, the colors of the status icons have been changed slightly for better distinction.
• ‘Recent Patients’ list does not update when using the new ‘Patient Search’.
• Task screen missing the patient folder icon.
• When a user scans or manually enters a SKU or UPC using the new ‘Quick Add’ feature the original SKU or UPC was not being removed.
• When a practice had more than 10 locations, all locations were not displayed in the top menu.
• Issue uploading files or an employee image.

We are still working to resolve the following:

• Premature idle timeout messages.

If you are experiencing an error message when using Marco Connect a small manual change on your practice computer is needed to resolve this issue.

Please visit https://insprorevehr.wpengine.com/?p=15099 for more information on making this change.

If you have any questions or concerns, please do not hesitate to contact customer service.

RevolutionEHR engineers are aware of and working to fix the following issues:

• Marco Connect – Practices are not able to upload data from Marco instruments. Data center engineers are working to resolve the connectivity with the Marco Connect software.
• File Upload – Users are not able to upload files to a patient chart within RevolutionEHR. This is affecting practices using Firefox and Safari, but Chrome is operating as expected.
• Messages – If a user has enabled RevDirect, the messaging module is loading messages slowly (up to 60 seconds) and the user is not able to send or receive Direct messages.

Our engineers are troubleshooting and working to resolve an issue with our Marco device integration.

At this time all indications are that traffic routing thru the TW Telecom and other internet backbones has returned to normal. If you are still experiencing access issues, please contact customer support.

Data center engineers have isolated the cause to an issue impacting an upstream internet service provider, TW Telecom, servicing the Midwest. The data center engineers have taken actions to disable connections with this provider and is routing all traffic through redundant links.

Practices with an ISP that relies on the TW Telecom backbone may still be experiencing issues. As always, updates will be provided as information becomes available.

Some RevolutionEHR users are not able to access RevolutionEHR or several related websites. At this time the data center has reported that all internal systems are operating normally but there are indications of regional internet backbone issues. This likely affects access to different websites based on internet routing, not just RevolutionEHR but it may appear that some sites are working properly while others are not.

Data center engineers are evaluating the situation and working with the appropriate teams to resolve these issues. Another update will be posted as soon as more information becomes available.

At this time reporting information for August 10th, 2015 is up to date and you should be able to resume your daily reporting activities as needed.

The reporting servers for U.S. customers are currently experiencing a delay. The effect is that posted sales, payments, claims and inventory changes may not be reflected immediately in reports. Please note that all transactions are being posted correctly and no data loss is occurring.

We realize that delayed availability of reporting information can cause a disruption in your daily routine, especially for your end of the day closing activities. Please note that reporting information is normally up to date in the evening hours.

Engineers have been working diligently to resolve these reporting delays and have made several positive adjustments that have resulted in better performance. RevolutionEHR engineers and database specialists continue to monitor the delays and implement additional enhancements to reduce the chance of reoccurring delays.

We will update Insight once reporting information is up to date so you may resume your activities if necessary.

We received a few reports of appointments not syncing between TAB and RevEHR on Friday (8/7/15). After looking into the cause, it was determined there was a data flow interruption which started on Thursday and was fixed by Friday evening. If you were affected, please make sure you have re-started TAB and RevEHR and refreshed both systems since Friday evening.

If you are still experiencing problems with appointments or patient data syncing from one system to the other, please contact customer support. We appreciate your patience as we worked to resolve the situation.

We appreciate your patience while data center engineers worked to resolve this issue. At approximately 6:15pm CDT engineers at the U.S. data center were alerted to an issue with a network storage unit causing users to lose connection to RevolutionEHR. Data center engineers immediately began work to restore connectivity and then perform integrity checks on the database. Access to RevolutionEHR was restored at 6:56 pm CDT

We do understand the impact that downtime has on your practice and restoring your access to RevolutionEHR is always our top priority. We sincerely apologize for the inconveniences caused by this issue.

We are currently rebooting the database servers due to an internal hardware issue. Engineers are working to resolve this situation as quickly as possible and more information will be provided as it becomes available.

We have received reports from some customers that appointments are not syncing from TAB to RevEHR. At this time we believe the issues are only being experienced by some accounts using the RevEHR – TAB integration. We are looking into the cause and will provide an update when this has been resolved. In the meantime, appointments and encounters will need to be started manually.

At this time reporting information for August 4th, 2015 is up to date and you should be able to resume your daily reporting activities as needed.

Here is the latest update on the progress to resolve the recent reporting delays. Data center engineers, database specialists and RevolutionEHR engineers are actively working towards a resolution. Until the resolution is in place we anticipate reporting delays will continue to occur and reporting may be delayed over an hour at times throughout the day.

We realize that delayed availability of reporting information can cause a disruption in your daily routine, especially for your end of the day closing activities. Please note that reporting information is normally up to date in the evening hours.

We will update Insight once reporting information is up to date so you may resume your activities if necessary.

We do apologize for the inconveniences caused by this issue and are working to resolve this issue as soon as possible.

The reporting servers for U.S. customers are currently experiencing a delay. The effect is that posted sales, payments, claims and inventory changes may not be reflected immediately in reports. This also effects the unread tasks counter displayed in navigation bar however tasks are displayed in real-time when opening the task module.

Please note that all transactions are being posted correctly and no data loss is occurring. All reports will continue to be updated as the delay diminishes. Engineers are monitoring the delay and designing a solution to keep the delays from occurring again. More information will be posted on Insight as it becomes available.

Engineers have implemented a resolution and continue to monitor performance, however access may be slower than normal as practices begin to login.

Engineers have diagnosed the issue and a system restart is necessary for resolution. Estimated downtime will be approximately 10-15 minutes.

We are aware of performance issues at our U.S. data center which is affecting RevolutionEHR users. Engineers are actively engaged in resolving the situation and more information will be provided as it becomes available.

At approximately 7:03 pm CDT today the reporting server returned to normal status and is no longer experiencing delays when processing transactions.

We realize that delayed reports cause a significant disruption in your daily activities, especially near the end of the day. Engineers are still investigating the root cause of the reporting delays today and will ensure steps are taken to avoid this in the future. We appreciate your patience and please accept our apologies for this inconvenience.

The reporting server for U.S. customers is currently experiencing a delay of nearly an hour. The effect is that posted sales, payments, claims and inventory changes may not be reflected immediately in reports.

Please note that all transactions are being posted correctly and no data loss is occurring. All reports will continue to be updated as the delay diminishes. Engineers continue to monitor the delay and discover the root cause of the issue, more information will be posted on Insight as it becomes available.

We are aware of performance issues at our U.S. data center which could affect RevolutionEHR users. Engineers are actively monitoring the situation and more information will be provided as it becomes available.

The earlier issue that caused some users to experience login issues has been resolved. The cause of the issue was due to a temporary server slowdown that was resolved automatically.

Engineers continue to monitor all servers to ensure no additional action needs to be taken.

Some practices are reporting issues with slowness and/or troubles logging in to RevolutionEHR, engineers are currently investigating this issue and we hope to have this resolved as soon as possible.

TriZetto has informed us that the issue with file uploads and downloads from this morning has now been resolved. If you continue to have issues submitting claims through TriZetto, please contact RevolutionEHR customer support.

Due to Trizetto system issues, the capability to upload and download files from TriZetto Provider Solutions is currently unavailable.

We will post an update on INSIGHT when we are informed that the issue has been resolved.

Network engineers have resolved the connectivity issue at the Canada data center and it appears that operations are returning to normal. Our team, along with the data center engineers will continue to monitor traffic and investigate the cause of this interruption. A detailed report will be provided as more information becomes available.

Our engineers are currently investigating a service interruption for RevolutionEHR customers in Canada. The issue has been narrowed down to a network traffic issue at data center. Updates will be posted to INSIGHT as more information becomes available.

Please note: this does not affect customers in the U.S.

RevolutionEHR servers in Canada are now operating normally. A full report will be provided in the near future.

The connectivity issue for RevolutionEHR customers in Canada has been resolved. Engineers are continuing to monitor and investigate the issue and we will provide a full report soon.

At approximately 6:00pm EDT RevolutionEHR servers in Canada started experiencing connectivity issues that is affecting the ability to access RevolutionEHR. Engineers are currently investigating the issue and working towards a resolution.

Please note, this does not affect connectivity for U.S. customers.

At approximately 1:20 CDT today, the RevolutionEHR Reporting Server crashed and immediately began its auto-recovery process. Upon re-starting the database layer on the server, a database integrity check began which took approximately 30 minutes to complete. During that time, database connections were disabled which also affected user logins.

At no time was the data on our primary database server at risk or affected.

Our engineers are working with the data center to understand the cause of the Reporting Server crash and are also working on ensuring that overall system access is not dependent on the Reporting Server.

We apologize for the disruption today and wish everyone a very safe and happy holiday weekend.

RevolutionEHR servers are now operating normally. We will continue to monitor connectivity and investigate the cause of this issue.

At approximately 1:35 CDT, RevolutionEHR began experiencing connectivity issues which is impacting access to the system. Our engineers are investigating and working towards a resolution, more information will be posted as it becomes available.

The issue with the RxNT integration has been resolved. We were informed by RxNT that a problem occurred on their side this morning which has since been fixed. We have confirmed that the integration is now working, we apologize for the interruption.

The RxNT integration is currently unavailable. Our engineers are actively investigating the cause and working toward a resolution. We will provide more details on INSIGHT as more information becomes available.

The issue at our data center in Canada has been resolved.   There was a problem with network related hardware which our data center engineers identified and resolved.   We will be reviewing the incident with the data center to assess how the issue occurred, the process of identifying and resolving it and future prevention strategies.

The RevolutionEHR servers for Canada are down.  Our engineers are working with the data center to rectify the situation.   We will provide updates as soon as we have more information.

This issue only applies to the Canada servers, not the U.S. servers.

SES has completed their maintenance.

SES, our partner that provides direct messaging will be performing maintenance on their systems this evening, June 11th at 9 p.m. CST which will last approximately 2 hours.

During this time you may not have the ability to send DIRECT messages from the messaging module.

We apologize for the inconvenience and thank you for your patience as we experienced some connectivity and performance issues with the application this morning. The following is a summary of the causes of those issues as well as the corrective actions taken to resolve them.

Starting at approximately 8:00am CDT and spanning for approximately 15 minutes, data center engineers detected two brief denial of service attempts on their network. These denial of service attempts affected overall network connectivity resulting in connectivity issues for RevolutionEHR and other data center customers. Data center engineers immediately began denying those attempts and have prevented any further connectivity disruption by isolating the target of those attempts from the rest of the network.

Later, at approximately 11:30am CDT and spanning for approximately 15 minutes, RevolutionEHR application performance slowed as a result of a process running on our data conversion server that adversely affected the amount of resources available to our database servers.  As soon as our engineers identified the process that was the cause of the database performance degradation, they immediately terminated the process and database performance returned to normal levels.

Each of the events we experienced this morning were isolated, one time events and not indicative of any general application or system issue going forward.

The engineers at our data center have detected a connectivity issue similar to the one experienced on Wednesday but we are still waiting on more information to confirm. Our developers are monitoring the servers but at this time we do not expect these issues to be related to the release last night.

We have new information to share regarding the performance issue from this morning. Our data center detected a distributed denial of service attack and was able to resolve it. Please contact customer support if you experience any issues going forward.

The issues from earlier this morning have been cleared. We will post more on the root of the problem when we receive a complete summary from our data center.

The engineers at our data center are troubleshooting a service interruption.  We will provide more information when it becomes available, but reports we have received have stated that the issue is clearing and they are continuing to monitor.

Our engineers have resolved the issue with application access for Canadian users and are monitoring access.

Our engineers are aware of and currently troubleshooting application access issues for our Canadian users. We will post updates as the problem is resolved.

Application performance has resumed to normal operations.  Our engineers will continue monitoring performance indicators.

Our engineers are troubleshooting and working to resolve an application performance issue for our Canadian customers.   We will post updates as we have more information.

We are aware of a service interruption with the TAB integration.  Our developers are working with TAB to help with a resolution.

Our application servers are all operating normally.  Earlier, our server monitoring identified higher than normal usage on a few of our application servers causing slow performance for some of our users.  Shortly after our engineers began troubleshooting the incident, the usage on those application servers returned back to normal.

Data center engineers are investigating the cause of the temporary usage increase and will be reporting on their findings.

We will share the results of their analysis here when it becomes available to us.

Our engineers are aware of and troubleshooting a performance issue with our application servers this morning.  We will continue to provide updates as we have more information.

The RevDirect service issues have been resolved and it is now operational.

We are aware of an issue that started with RevDirect this morning that is affecting all users. You will receive an error message when trying to use the service today. Our engineers anticipate that this will be fixed by tomorrow morning.

I’m very pleased to inform you that we are confident that the performance issues we have experienced over the last few weeks have been fully resolved.  Our key fix was actually implemented mid last week, but it was important that we monitor application performance for a few days before sounding the “all clear” to you.

For those of you who are curious about what happened technically and how we went about diagnosing, troubleshooting and ultimately resolving the problem, here is a detailed summary of the events:

In mid November, our primary database server raised an overheating alarm on two different occasions over the course a few days.  By design, the server would throttle down to prevent any real damage to the server hardware.  The result was an application performance decline as the server cooled.  Upon learning of the overheating alarms, we began the process of preparing and scheduling the installation of a replacement server.

Shortly thereafter, the cooling fans on the server completely failed and we had to replace the server immediately, recovering relatively quickly from a major hardware failure.

Even with this new equipment in place, we still saw the same symptoms… on some afternoons we experienced a sudden slowdown.  After further analysis, our data center engineers suspected yet another hardware failure.  We brought in an engineer from HP (our server brand) and he agreed with the conclusion, given the lack of any other obvious causes. We pulled a newer model server from our disaster recovery site and installed it as the primary database server for our system. Concurrently, our system engineers began a deeper analysis of our database design to identify any optimizations that we could implement to help alleviate the problem as well.

The system performed nicely that Wednesday, but it was a false positive. Performance issues started again that Thursday and hit us especially hard last Monday, typically our heaviest load day of the week. With hardware issues completely ruled out, we continued to focus on our database efficiency to address the afternoon performance anomalies.

Each day we identified and implemented a few database optimizations.  At the same time, our data center engineers continued their analysis/research at the system level.  Last Monday, they found documentation that exposed a correlation between our system performance behavior during a slowdown and the version of our database software layer.  We immediately upgraded and installed the enhanced monitoring and query analysis tools to troubleshoot and confirm this type of performance behavior.

Last Tuesday, the suspected cause and solution were confirmed by both the monitoring tool and a follow-up call with a MySQL/Oracle consultant. That night, we installed the upgraded database software layer to resolve the issue.

Wednesday, the system performed beautifully. We experienced some spikes in usage, and the system handled it gracefully, as it should. Then around 3pm, the same time when things have typically “gone bad” over the last few weeks, we had another slowdown. Frankly, we couldn’t believe it. The system stats that we had been watching didn’t look the same as they had in the previous events.  The timing couldn’t have been worse. While we are still gathering information, this particular event appears to be a user mistake at the data center (someone accidentally doing something that shouldn’t have been done… especially at that time of day). We had a call with their CEO and he said as much, but a more detailed report is coming.

Since then, the system has been performing very, very well.  And, we remain very confident that this particular, rather elongated, time of turbulence with the application is now fully behind us.

Again, my apologies for the frustrations and I appreciate your patience as our team worked non-stop to resolve an elusive problem.

Jim Schneider
CTO
RevolutionEHR

The Eyefinity site for processing VSP authorizations and claims is operational.

The Eyefinity website for processing VSP authorizations and claims is currently down.

We’re experiencing a performance degradation and taking action to restore performance back to normal levels.

Our engineering teams continue to analyze the performance improvements we have been implementing over the last several nights and their affect on the system.

We are still anticipating a period of sluggishness this afternoon but with less intensity as was experienced yesterday as a result of the updates implemented last night.

Tonight, we have scheduled another maintenance window to implement changes that we believe will have the most significant impact on performance going forward. Please see the details of the maintenance window below:

RevolutionEHR will be performing system maintenance tonight, Tuesday December 16th. The maintenance period will begin at 11:00pm CST tonight and extend until 3:00am CST tomorrow morning. The system will be unavailable during this time.

Logins will be disabled at 10:45pm CST. If you are logged in before 10:45pm CST tonight, you can continue to work until 11:00pm CST – however, please note that you will receive an error message at 11:00pm CST and may lose data currently being entered. It is very important that you log off prior to 11:00pm CST tonight, Tuesday December 16th.

Our reporting servers are back online after experiencing an unexpected hardware fault this afternoon.

Our engineers continue to investigate the current performance issues and are making progress. We will continue to provide updates.

Our reporting server is experiencing access issues. Our engineering teams are working on a solution.

We are experiencing a performance decline that is affecting application access. Our engineering teams are troubleshooting and focusing on alleviating the problem.

We experienced a very brief performance decline for approximately 10 minutes this morning that affected response times for some users. Our engineers are monitoring the servers very closely and we will provide more updates throughout the day.

Last night we replaced one of our database servers to address a hardware anomaly discovered during troubleshooting our recent performance slowdowns.

This completes our first major step to resolve the afternoon performance slowdown. We also implemented a set of optimizations that are designed to redirect certain data requests to other database and processing servers.

There are more optimizations being readied for implementation shortly and we will notify you when those have been implemented.

We are monitoring the performance of the new hardware closely and will continue to monitor all aspects of system performance.

Our engineering teams are focused on alleviating the performance decline that we are currently experiencing.

Overall application usage is trending higher today. There is a chance that we will experience some periodic slowdowns at peak usage times in the mid to late afternoon.

As we continue to prepare for moving our broader optimization updates into production, our engineering teams stay focused on monitoring realtime performance and minimizing the extent of any slowdown period should it occur.

Our integration servers have been re-enabled.

Our system engineers and data center engineers are actively continuing the work to resolve the performance issues.

We have temporarily disabled our integration servers as a precaution and resource freeing measure to better address and monitor application performance during the afternoon hours today.

This means that partner integrations, such as TAB, will not function until further notice.

Device integrations and other partner launched integrations such as RxNT and VisionWeb are still functional.

We apologize for the slow performance. Our engineers are actively working on a resolution. This is our highest priority. We will continue to post updates regularly.

Our engineers are actively looking into performance slowdowns that are affecting some of our users. We will provide an update when we have more information.

Our data center has provided more information on the network connectivity issue today – please see the following message for details:

Data center engineers determined an Internet routing issue occurred, affecting one or more of its upstream providers. Engineers isolated the affected providers and disabled those connections. At that time, the issue appeared to be resolved and all routing services returned to normal.

During this issue, some customers may have noticed intermittent routing and service availability. The Data Networks Operations Center is monitoring the situation closely and will update clients should any additional issues reappear.

Our data center engineers notified us about internet connectivity issues with a segment of their network that lasted for approximately 15 minutes.  Most users were not affected.  We are awaiting more details about what occurred and will share the information when it is available.

The application is performing normally. Our engineers are investigating the cause of the temporary decline in performance.

We are aware of and investigating performance issues with the application. We will continue to post updates as we have more information.

The application is performing normally. We continue to analyze events that contributed to the period of slow performance earlier this afternoon.

We are seeing an improvement in the application performance after a brief period of slow performance. We continue to troubleshoot the cause of the performance issue.

We are troubleshooting an issue causing limited access to the application and are working toward a resolution. We will continue to post updates as we have more information.

The issue with the Eyefinity link has been fixed. You can now utilize the VSP integration.

Our link to Eyefinity is currently experiencing technical issues. We are actively working with Eyefinity to resolve those issues. As we have more information to share, we will post updates.

RevolutionEHR is now operating normally. If you are still experiencing any performance issues, please contact customersupport@revolutionehr.com.

While our engineers are still seeing some delays, the lag should be improving some as the load has decreased.

We are experiencing a high load on our database server right now that is causing some slow performance issues. Our engineers are assessing the issues and working on a resolution. There is no indication that this is a hardware issue residual from yesterday.

At approximately 2:00 pm CST, we experienced a hardware failure on the primary database server.  The hardware failure triggered an automatic and orderly server shutdown which is designed to safely shut down the database.

At the time of the server shutdown, our disaster recovery processes immediately went into motion.  Our data center and system engineers quickly began the process of swapping to a “stand by” primary server that we have as a part of our disaster recovery procedures.

At 3:00pm CST, the primary server swap was completed with the new hardware running normally and the application beginning to process user requests.  Database integrity checks as a part of re-starting the database confirmed that there was no risk of data loss as a part of the hardware failure event.

While the recovery process for this type of a catastrophic hardware event went smoothly from a data integrity and recovery perspective, we are committed to reducing downtime through quicker fail-over procedures.  We are continually assessing risk and planning to improve disaster recovery scenarios.

Please accept our apologies for the inconvenience to your office and staff this afternoon.  We understand the down time you experienced today significantly impacted your patient care.

Our engineers have completed the primary server replacement and the application is now servicing user requests.

We anticipate application performance to initially be a bit slow and then improve steadily to normal as all users begin to access the system.

The hardware failure we experienced was on a primary server.  Another primary server is in place and in the process of being brought online.

We experienced a hardware failure on one of our servers which affected user access and our engineers are swapping to another server.  We expect the application to be back up and running shortly.

We are aware of and troubleshooting a problem with the application.  We will post updates as we have more information.

Our engineers have resolved the issue with the Reporting Server delays.

Our engineers have resolved the issue with application performance and it has returned to normal.

Our engineers are working to resolve an application performance issue.  We will post updates as we have more information.

We are aware of and working to resolve a Reporting Server delay.  Our engineers are actively troubleshooting the issue.  We will keep you posted with updates as we have more information to share.

Application performance has returned to normal.

Our engineers have identified the source of the performance issue and performance is returning to normal.

Our engineers have resolved the reporting server performance delays.

Our engineers are working to resolve an application performance issue.  We will post updates as we have more information.

We are aware of and working to resolve a performance issue with the Reporting Server.  Our engineers are actively troubleshooting the issue.  We will keep you posted with updates as we have more information to share.

Our engineers isolated the root cause of the Canada performance issue from last week and it has been resolved.  Application servers are operating normally.

Our engineers have been troubleshooting sporadic performance degradation on the Canadian servers, resulting in some periods of downtime.

Last night, we did an emergency patch to add more memory and modify storage to the database server which will fully be applied this morning.

We continue to investigate the root cause of the performance issues to ensure that our solution addresses the root cause. We will also continue the process of adding more resources/hardware to that environment as well.

If you have any questions, please contact Customer Support

We are aware of and are investigating an issue causing access to RevolutionEHR in Canada.  The issue is intermittent but will cause a brief loss of access.  The development team is working to isolate the cause and determine if it is related to similar issues experienced in Canada last week.  We will continue to post updates whenever new information becomes available.

Our engineers determined that a heat sensor on our database server was reporting an erroneous overheating condition – which by design caused our database server to auto-throttle to a slower processing state to cool the server.  Application performance suffered during those times.

We are working with our data center to resolve the issues with the heat sensors as well as the response of the server when an overheating event is detected.

At the same time, we have been monitoring a variety of general latency issues that many internet service providers have been experiencing throughout today which may also have contributed to application performance issues.

Our engineers are aware of and investigating a performance issue with RevolutionEHR this morning.  You may experience varying levels of performance.  We will provide updates as we work to troubleshoot and resolve the issue.

The reporting servers are operating normally

We are aware of and investigating an issue causing access problems to RevolutionEHR in Canada. Our engineers are working on the problem and we will continue to post updates.

While the reporting servers have restarted, they are processing data to get up to date for today.  This is causing some performance issues with reporting.

We recommend running reports end of day to allow the reporting servers to complete their updating processes.

Our engineers are restarting the reporting servers.  This is expected to take up to 30 minutes.  While the reporting servers are restarting, you may experience slower performance using the application.

You may notice that some reports are not displaying data for today.  Please be assured that reporting data is being saved in the database properly.  The reason you may not see data from today in your reports stems from a problem with the data being sent to the reporting servers.

Our development team is aware of this issue and is currently working on a resolution.

Our Gateway partners have informed us that their client website is now operating normally.

We have confirmed that their site is operational.

Our partners at Gateway have notified us that their client website is currently down. Clients are getting an error when trying to log into the client website.

Their team is working diligently to get the website up and running again.

As we have more information to share, we will post updates.

Reports of difficulty accessing RevolutionEHR waned throughout the day yesterday and several of those who reported issues have confirmed that their internet issues have been resolved.

As always, we encourage customers experiencing difficulty accessing RevolutionEHR to check with their internet service providers and/or switch to a backup internet connection such as DSL or 4G card when available.

We are receiving calls from some customers, primarily on the east coast, reporting difficulty accessing RevolutionEHR. All RevolutionEHR servers and data center services are operating normally. We are working to understand the source of the internet access issues for those customers and we are investigating reports of internet service provider performance issues and outages in those areas.

We encourage customers experiencing difficulty accessing RevolutionEHR to check with their internet service providers and/or switch to a backup internet connection such as DSL or 4G card if available.

As an update to the Session Expired errors that were received by some users last week, we are happy to report that infrastructure assessments have identified a couple of the likely causes.  Enhancements to the system have resulted in normal operations as seen by internal RevolutionEHR monitoring services.

If there are any consistent issues of “session expired” notices seen, please contact us at customersupport@revolutionehr with details.  Otherwise, it is no longer necessary to provide any additional data from any practices as requested last week.

We have been receiving reports from some users that they are experiencing instances of being kicked out of the program while receiving a Session Expired error even though they are actively working in the app when this occurs.  This can occur multiple times per day and the user may also have difficulty logging back in, forcing them to refresh the program.

This is not affecting all RevolutionEHR customers and seems to be isolated to a smaller subset of users.  If you are not experiencing any of the issues described above, you may disregard this message.  If you are one of the affected users receiving Session Expired errors, we are hopeful that you can assist us in diagnosing this issue by providing some information.

Please return to feedback@revolutionehr.com the following data:

• Username of any employees in your practice currently experiencing the issues described above
• Browser and browser version.  The version can be found in browser’s menu by clicking on “About Google Chrome” or “About Firefox”, etc.
• Your Internet Service Provider (ISP)
• Your IP address.  This can be found by going to http://www.whatsmyip.org/
• Are all computers in the office affected?  If no, is it always the same computers that are affected?

We thank you in advance for your assistance in providing this information, and for your continued patience as we troubleshoot these issues.  We understand the impact that this has on your practice.  As new information becomes available, we will continue to provide updates.

As of this morning, we are still receiving isolated reports of lost connections and slow system response. Our engineers continue to investigate the issue with our data center.

We are currently experiencing some database issues that are causing slow performance and some users to disconnect. Our engineers are aware of this issue and are working with our data center to find a resolution. We will provide an update when we have more information.

Connectivity issues with certain ISPs were resolved shortly after being reported earlier.   As always, we appreciate user feedback regarding ISP related issues as they surface and are resolved.

We are receiving a handful of reports of connectivity issues to RevolutionEHR.  The application and data center are operating normally.  We are investigating some issues surfacing with certain ISPs having difficulties.

We are no longer receiving reports on Comcast or CenturyLink related internet issues. If you are a Comcast or CenturyLink customer and are having issues with the RevolutionEHR application, we encourage you to contact Comcast or CenturyLink directly to troubleshoot internet connectivity and/or DNS related issues.

We have been getting reports of intermittent internet issues from RevolutionEHR customers using CenturyLink and Comcast.  The reports started yesterday and continue today.  We will continue to pass on information as we learn more.

If you are a CenturyLink customer, please see the following message that CenturyLink support sent to another RevolutionEHR customer:

“Our goal at CenturyLink is to provide you with the best possible service and timely information regarding changes that impact your account.  We are upgrading to a new architecture at no additional cost to you that will automatically fail over, thereby minimizing the potential for outages related to DNS (Domain Name System) and should eliminate the need for you to make similar DNS changes in the future. 

Effective immediately, please update your DNS server IP addresses to reflect; Primary DNS:  205.171.3.26; Secondary DNS:  205.171.2.26, on all Static IP services or you may be unable to access the internet after July 16th.

If you have any questions about how to make these updates, please visit http://internethelp.centurylink.com/internethelp/modems-dns.html and follow the instructions based upon your modem type.  If you have further questions about this notice or need additional support, please follow the online prompts to contact an agent.

Thank you for choosing CenturyLink for your communication needs—we value you as our customer.”

We have received some reports of spinning clocks and slow performance. Our engineers have been in contact with the data center and configuration adjustments have been made that seem to have resolved any issues.

We can confirm through our own testing and from reports of several doctors that RxNT submissions are no longer generating an error notice.

The application is operating normally.  We continue to monitor performance.

RevolutionEHR will be performing system maintenance TONIGHT, April 9th, at 11:00 pm CDT.

During this system maintenance period our engineers will be applying a patch that contains several fixes to address recent performance issues, customer reported issues and MU scorecard issues.

The system will be unavailable for approximately 30 minutes during this time. If you are logged in at 11:00 pm CDT tonight, 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 TONIGHT.

At approximately 3:20pm CDT yesterday we experienced an excessive load on our database which caused issues accessing RevolutionEHR.

Our engineers took immediate steps to restore access and the system has been operating normally since. Our highest priority is providing you access to RevolutionEHR.

We continue to investigate the cause of the excessive database load event as we closely monitor our system performance and accessibility.

We are aware of and investigating an issue causing access problems to RevolutionEHR. Our engineers are working on the problem and we will continue to post updates.

A new version of RxNT has been released and is integrated with RevolutionEHR.

PLEASE NOTE:  While you will get an error message when you send the Rx, YOUR Rx WILL BE TRANSMITTED TO THE PHARMACY even with the error.

We are working with RxNT to remove the error message.

The performance issues related to this week’s release have been identified and resolved.  We continue to work on  some functionality and browser compatibility issues that have been reported.  We will be monitoring our server and network infrastructure very closely.   If you are experiencing performance or stability issues, please contact us.

We identified the issue that caused this morning’s outage. The problem was related to importing of inventory which caused an extensive load on our database. Our engineers have fixed the problem and it has been updated in production. We continue to closely monitor the operation and performance of the release.

This morning while our technology team was continuing to monitor our system for smooth operation, a report request from one practice caused traffic backups like those that happened on Tuesday.  Diagnosing this issue took about 20 minutes, and with the added input of slowness from customers, we decided to perform the same component restart that we did on Tuesday to minimize the negative impact on your business.  We are 100% aware of how these episodes impact you, and we have committed every resource at our discretion to keep you from being aware of these.  I am working with our team directly to put a permanent end to this process, which we believed was successfully remedied yesterday and this morning. We are sorry for these episodes, because even though they are limited in scope, we understand they are significant for everyone.

Our engineers are actively looking into the connection interruptions at this time. We will be able to provide more information as it becomes available. We are doing everything possible to resolve this.

A new version of RxNT was intended to be released in conjunction with the 6.2 release.   Due to an issue on the RxNT side, this did not happen.   Currently, if you launch RxNT, the following will occur:
• You will see a view of their entire EHR available for writing Rxs.
• You will get an error message when you send the Rx
• THE Rx WILL BE TRANSMITTED TO THE PHARMACY even with the error.

Please Note:  In some browsers, pressing “Launch RxNT” appears not to do anything.  If you see that it is likely due to your browser’s popup blocker being enabled.

We expect RxNT to be enabling the new RevolutionEHR-RxNT interface tomorrow which will reduce the view to e-prescribing only.

We have found and fixed an issue that was causing high network traffic. The bandwidth statistics that we monitor have improved dramatically. We have not yet determined if this contributed to our two issues yesterday. We continue to monitor the situation closely with our data center.

We are aware of the slowdown that recently started. Our engineers are looking into the issue and working on a resolution.  We will update again when we have more information to provide.

Our engineering team believes it has found the root cause of this morning’s performance issue.  The search process related to the new RxNorm drug database was returning larger than expected amounts of data which ultimately affected the performance of the database and the application.  The problem was a load issue that went undetected in our testing.

To rectify the problem we have changed the drug search function to require at least 3 characters.  This has been put in place and things are running normally from our side.   We apologize for the rough morning, we understand the affect this has on your practice and your patients.

We are continuing to investigate the performance issue and are actively working with our data center to isolate the issue. We will update you as soon as we have something more definitive.

Our engineers are aware of and investigating an issue causing performance degradation.  We will provide updates as soon as they are available.

We are aware of some connectivity issues that are affecting some users. Our engineers are looking into the issue and we will provide updates as we have more information.

Our data center experienced a power event during a facility generator test at 23:10 which has been resolved.   The RevolutionEHR servers were subsequently restored to operational status.   We will be reviewing the root cause of the event with the data center.

Our data center is currently experiencing problems. We will provide updates as we get more information.

At this time, XO is still working to alleviate the bandwidth usage on their link.

Our data center has adjusted routing to force traffic from your environment through our Level 3 link to the internet. This eliminates use of XO’s strained links which is why we’re seeing resolution at this time.

Our data center engineers will continue to internally follow up with XO and revert our routing preferences to their previous settings once we get the all clear from their end.

We wanted to update everyone on what our engineers have found so far.  The issue appears to be with the  XO to AT&T connection in Chicago. This is not something that our data center can reroute on their end, but they are working with XO to have it re-routed overnight tonight. It seems the connection is overloaded and it is the only connection between these two carriers in the Midwest. So while things might be better, the issue is not yet resolved but we hope it will be by tomorrow.  Our engineers will be monitoring this throughout the evening and overnight.

We will update everyone as soon as we have more information.

A few of our customers have been reporting intermittent issues accessing RevolutionEHR since Monday afternoon.

While RevolutionEHR servers have been operating normally during this period, we asked our data center to investigate.

Our data center is reporting that traffic routing issues have been occurring with AT&T and Comcast.  Data center engineers are working directly with those carriers to assist them with the traffic routing issues that may be specifically affecting our customers.

For those customers who depend on AT&T or Comcast for your internet service, if you are experiencing problems accessing RevolutionEHR, we advise you to switch to a backup internet service if you have one available.

We will continue monitoring and providing updates as we learn more.

We have received reports from customers stating that they are experiencing significant lag when running RevolutionEHR.  All Revolution servers are responding normally. With the exception of one report, there is an ISP that appears to be the common thread. We are continuing to investigate with our data center to confirm whether this ISP is having issues or whether there is something else at play.

After investigation, Atomic Data Engineers determined that there was an external network issue which affected parts of the Midwest region. At this time, all network connectivity is operating normally. If you are still experiencing connection problems, please contact customer care at customersupport@revolutionehr.com.

We are currently investigating some regional internet issues experienced by some of our  users. We will provide more updates as they become available.

Our engineers detected the problem with device integration and applied a fix. We appreciate your patience during this brief interruption with device integration.

Our engineers are looking into a problem with equipment integration that is affecting RevIntgrator and MarcoConnect from logging into RevolutionEHR.  For the near term, you can manually enter data from refractive devices using keyboard shortcuts.  We apologize for this inconvenience and will post updates as soon as we learn more.

Good Evening,

Beginning around 3:40pm CST, our data center observed a network connectivity issue. Data center engineers immediately investigated and determined a distributed denial-of-service attack was in progress and immediately began to work to identify the exact nature of the attack and began remediation steps to resolve the issue. At 3:55pm CST, the attack subsided and traffic flow was returned to a normal state.

During this period, RevolutionEHR was operating normally, but you may have experienced limited accessibility. Data center engineers are continuing to review data captured during the event to help prevent and mitigate the effects of any similar events in the future.

We appreciate your patience during this issue. If you have any questions of concerns related to this issue, please contact Customer Support.

Jim Schneider
CTO
RevolutionEHR

INTERNET ISSUE:  The data center is reporting a significant internet traffic issue.  Immediate action is being taken to review options for accessibility.

Data Center engineers have determined that the issue with network connectivity was caused by an issue with an upstream internet provider.  All traffic has been automatically routed to alternate upstream providers until the core issue has been resolved.

Some customers are reporting slow application response times. Several internet status websites are currently showing general internet latency issues. We will continue to post updates as we learn more.

One such monitoring site is www.internetpulse.net.

We have confirmed that Time Warner Cable experienced a wide spread outage in their service this morning.

The following links show a graphical representation of the history and state of the outage:

http://downdetector.com/status/time-warner-cable
http://downdetector.com/status/time-warner-cable/map/

Network engineers have confirmed that the routing issue deep within the Time Warner Cable network has been resolved.  We also have reports that Time Warner Cable customers are successfully logging back into the system at this time.

We have determined the connectivity issues are only affecting those with Time Warner Cable. Our data center is in contact with them at this time to find the solution. If you have a phone or other device with WiFi hotspot, you can get around Time Warner for now and access RevolutionEHR. We will provide another update when we have more information on this issue.

We are having reports of some customers experiencing problems connecting to RevolutionEHR.   It is only a subset of customers and they all appear to be using Time Warner as their ISP.  We are actively investigating.  Please contact us if you are having problems and let us know in the message what ISP you are using.

RevolutionEHR usage and performance statistics continue to look normal today. Performance feedback has remained positive from users in all timezones. The data center team continues on high alert as we monitor traffic throughout the day.

The data center has replaced the load balancers and early statistics used in monitoring are looking normal. Early feedback from our East coast customers is also positive. The data center team is staying on high alert as we all monitor the increased traffic that builds throughout the day.

Dear RevolutionEHR Customers,

Many of you experienced significant performance delays with RevolutionEHR today.  Obviously, this follows in a string of disconnected system issues that is causing growing grief.  As I apologize once again for unforeseen issues, I want to take this opportunity to let you know what happened and what we are doing to resolve the problem.

Just as we are committed to updating our software for better performance and accessibility for our customers, our world-class data center partner is also committed to updating their infrastructure for better performance.  On Saturday night, the data center initiated an infrastructure update to provide better performance and service to all of their customers – including RevolutionEHR and our customers.

One of the improvements that the data center implemented overnight on Saturday was an upgrade to their load-balancing technology.   Load-balancing spreads the internet traffic across hardware that runs RevolutionEHR to provide every user with a seamless experience in accessing the system and requesting and delivering data.

This upgrade was completed early on Sunday morning and we provided testing resources to monitor the result of these infrastructure upgrades throughout the day on Sunday.  After several hours of testing and monitoring by our engineers and the data center engineers, in addition to personal testing by our CTO, Jim Schneider, and me, all indications were that RevolutionEHR was performing optimally.

Early today, we started getting reports about poor application performance from our users.   The data center quickly determined that the service interruptions and outages you may have experienced today were caused by a significant issue with the new load-balancing technology brought online as a part of their infrastructure update over the weekend.   These issues not only affected the RevolutionEHR application and our users, but several other vendor applications that the data center hosts for their other customers.

Unfortunately, there was little that our RevolutionEHR engineers could do today but to assist them in their troubleshooting efforts to resolve the problem.  All involved worked every minute of the day to attempt to bring you a return to normal service.

Here is where we stand tonight.  We have the commitment of the data center to execute a plan that focuses on ensuring RevolutionEHR is available and operating optimally for all of you at the beginning of business tomorrow.

The data center engineers are in the process of executing their plan to resolve the problem with load-balancers and will work overnight to implement their resolution.  We are dedicating our resources for testing and confirmation of their resolution.

In many questions and comments today, our commitment to the proper focus and effort has come into question.  I accept those comments due to the extremely unsettling impact that yet another issue has caused.  However, I would not be forthright if I didn’t strongly respond by saying that we have left no effort undone and that we never, ever try to put forth anything but the best effort and best result.  Unfortunately, our efforts are falling short of expectations.  I will keep our team and our partners moving forward toward excellence for your benefit, and I sincerely hope that is enough for you to continue on this journey with us.  As always, feel free to message me at sjens@revolutionehr.com if you want to discuss anything personally.

Our data center is monitoring the performance of the new load balancer. We understand many users are experiencing inconsistency with access and performance with application. Our data center engineers continue to investigate.

Our data center is bringing on the new load balancer at 3:15pm CST. At that time, you might lose your current session and need to login again.

Our data center has informed us that the new load balancer will be ready now at 2:30pm CST today. We apologize for this delay and appreciate your patience as our data center works on this resolution.

Our data center engineers are working on incorporating a new load balancer to resolve the application performance and accessibility issues that some customers are experiencing. They expect the new load balancer to be operational at approximately 1:30pm CST today.

Despite our ongoing efforts to enhance the system’s reliability, an issue arose after our data center scheduled maintenance on Sunday morning. The load balancers at our data center are experiencing intermittent failures. A load balancer is similar to a traffic cop – its job is to control and direct traffic equally across our application servers. This morning, some of our customers have effectively experienced traffic jams that are causing slow performance or on/off access to the application. Our data center engineers are working diligently to resolve the issues with the load balancers.

Some users are reporting slow performance with RevolutionEHR this morning. Our engineers are monitoring the situation.

Everyone should be able to login to RevolutionEHR at this time. If you still see version 6.0.0 on the login screen, you will need to clear your browsing history. Our development team will continue to monitor our servers for the time being.

This morning, we experienced performance issues with our application servers. We determined that a change made in our 6.0.0 release did not respond properly to high usage of the application and caused the system instability.

After several attempts to isolate and fix this problem this morning, we have decided to back out the 6.0.0 release.

We know how frustrating it is for you when RevolutionEHR is not available.  We sincerely apologize for this inconvenience.  We are doing everything we possibly can to resolve this problem.

The system will be unavailable as we revert to release 5.4.7.  We estimate the application will be reverted to 5.4.7 by 10:45am CST.

Our engineers are continuing to resolve the issues with the application servers. We apologize for this interruption this morning!

Our engineers have identified the application server issue and it is currently being resolved.

Our engineers have detected an issue with the servers that is causing limited access. We are in contact with our data center and will continue to provide updates.

Eyefinity reports that their system is now operating normally.

We have been notified that Eyefinity is currently experiencing a system degradation. They are addressing the problem and expect to have this resolved soon. You may experience problems submitting VSP orders until the issue is resolved.

Currently, the system is running and you should be able to login normally. The engineers are investigating the cause behind this brief interuption. We will keep you updated if anything changes. We apprecaite your patience during this time.

RevolutionEHR is experiencing some problems at this time. Our development team is already aware of this interruption and working on a quick resolution. I’ll provide more information as it becomes available.

This morning, we experienced an onset of significant performance degradation with the interface to the data storage system, eventually causing our database to reject connection attempts.

Our engineers immediately began troubleshooting the problem and identified a connection related to the application server. They restarted the application servers and this appeared to fix the problem initially. However, the symptoms resurfaced shortly after the servers came back online.

After deeper review, we isolated the issue to the interface to the data storage subsystem. Once we restarted the database system, the performance issue was resolved.

As a result of this event, we are escalating our plans to move to our new data system platform to continue to provide additional redundancies and scalability.

At this time the system is back up and running. We are continuing to monitor the servers very closely and we will notify you of any changes. Again, we appreciate your understanding as we work through these issues.

As you know we are experiencing an outage with RevolutionEHR. We are working as diligently as possible to get the service back online.  As of yet, we do not have an estimate time for the resolution.   We understand the problems this causes your practice and are doing everything we can to rectify the situation. The issue we are facing is an access one, not an issue with the integrity of the data.

We apologize for the outage and will resolve it as quickly as possible.

We are aware that the issue has not been resolved yet and we are still working with the data center on a resolution.

RevolutionEHR is back to operating normally. We recommend that you refresh your browser before logging in. If you are still having problems, please notify us. Thank you for your patience this morning as we continue to monitor.

The developers at RevolutionEHR are doing everything they can to resolve this issue as quickly as possible. We take these situations very seriously as we know how much this affects everyone. We will provide you with more answers when we have determined the cause.

RevolutionEHR is currently experiencing some issues. We will post more information as soon as it becomes available.

Our reporting servers are operating normally.  Our recent work with our data center to add additional infrastructure and redundancy to the reporting servers continues.

We appreciate your patience over the last several weeks as we have worked to improve reporting performance.

The data for our reporting servers is back up to date with the production database.    All of your reports will now have the most current data.   We are working with our data center to add additional infrastructure and redundancy to the reporting server to minimize the risk of this type of situation in the future.

We appreciate your patience while we dealt with this issue.

We are moving the accounting related reports to our primary database server so that any report run related to accounting data today will contain current information.  We encourage you to limit the accounting reports you run today to those that are needed for daily operations to keep the demand on the primary database server low.

All other reports, including but not limited to queries, custom reports, partner integrations, etc. will only contain data that was entered prior to 9:00 pm on September 1st.   These reports will return to real time data tomorrow morning.

We have an issue this morning with replication to our reporting servers.   This means the reporting servers are not being updated with new data and reports run will not include data from today’s activity.   Reports run today will be accurate through Saturday, Aug. 31.

There is no concern on the integrity of the data that has been entered or will be entered today.  The issue is a temporary one related to updating our reporting servers.

We will keep you informed of our progress on the issue.

The application is operating normally at this time.  Based on our assessment we will be adding additional application servers to our infrastructure.

We have been experiencing intermittent issues with some of our application servers that required us to restart them.   This has been done and we are continuing to monitor the situation.

Our data center is reporting that all systems are operating normally.

Our data center is experiencing some latency.  We are monitoring the situation.  You may experience some slow response times when accessing the application.  We will be providing further updates regarding this issue.

We have experienced delays recently with our reporting server. Our development team is aware of the lag that you continue to see and they are working to fix the issue. We are anticipating a resolution to the problem in the next week or two. We apologize for the frustrations that this is causing and we thank you for your patience as we work towards a solution. We will continue to update on the progress as more information becomes available.

The application is operating normally.

The following is a timeline of the events the followed our servers going offline temporarily this afternoon.

• 1:53 pm – our engineers were first notified of an issue by a monitoring event at our data center.  Our engineers and our data center engineers immediately began investigating the event.
• 2:07 pm – our data center engineers detected that a LUN on one of our database servers was remapped, causing issues for our database servers.
• 2:12 pm – our database server was restarted.
• 2:15 pm – all LUNs at our data center were confirmed online.
• 2:16 pm – our engineers began the process of running database checks, verifying the integrity of data.
• 2:26 pm – our engineers completed running checks on the database.
• 2:28 pm – our engineers performed some manual, random inspection of data.
• 2:30 pm – our application servers were restarted.
• 2:34 pm – our application servers were back online.

Our data center engineers will continue to investigate the cause of the LUN remap that caused our servers to go offline.

All data center resources are operating normally.

All servers are back online. At this time we believe the problem has been corrected and you should be able to login. It may be necessary for you to refresh your browser before logging in. If you are still unable to login, please contact customer support. We appreciate your patience as we continue troubleshooting this occurrence.

Our database servers are back on line and the database has been verified.

Our database servers are back online. We are performing checks on the database and expect the application to be available shortly.

Our servers are down at this time. Our engineers are working with our data center to resolve this issue as soon as possible. We will provide more information as it becomes available. We apologize for this inconvenience.

We are currently experiencing a problem with the application not responding. Our engineers are aware of the problem and investigating.

The reporting server is back to running properly. You should not be seeing any delays when running reports. If you are still seeing delays at this time, please send us an e-mail at customersupport@revolutionehr.com. Thank you for your patience as we resolved this problem.

We are currently experiencing a slight delay with our reporting server. It could take up to an hour for data to show up in a report. We are working with our data center to resolve this issue and we will let you know as soon as this server is back to normal operations.

The temporary access disruption experienced earlier today has been fully resolved by our data center. While a root cause analysis is still being reviewed, the application is fully operational.

RevolutionEHR experienced a temporary but complete access outage to the service from 11:02 am to 11:13 am that appears to be cleared. Technical engineers will continue to monitor the situation carefully. More information to come.

The RevolutionPHR Patient Portal is back up and operating normally.

The RevolutionPHR Patient Portal is down. Our engineers are investigating and we will provide updates as soon as they are available.

Our Application Servers are operating normally.

Please take a moment to view a very important message from our CEO, Scott Jens, regarding the recent RevolutionEHR outages.  Click here:  Status Update from CEO, Scott Jens

 We became aware of a server related issue this afternoon that had many users experiencing connection issues for about 15 minutes. If you are still unable to access RevolutionEHR, please refresh your browser and try again. At this time, we will leave the status at “yellow” as our engineers are still investigating. We know this is very frustrating to your practice but please know that we are utilizing a lot of different resources to find a definite solution.

We have detected a server related issue and our development team is looking into the cause immediately. An update will be provided as soon as we know more. Thank you for your patience at this time.

We have made some adjustments to resolve the data load issues with the Application Servers. At this time the Application Servers are running smoothly and we will continue to monitor them.

There are no new issues to report, however we continue to monitor the Application Servers.

At 3:40 this afternoon, we experienced a server load issue that required us to restart all servers. At this time, all servers are back to operating normally. If you are still seeing issues, please refresh your browser and try to login again. We know how much even momentary interruptions in connectivity can disrupt a practice, and we are working actively on trying to find a resolution.

We have not seen any additional load spikes on the application servers since yesterday.  However, because we are still diagnosing the root cause, we will continue to leave the status at yellow.

We continue to experience intermittent data load spikes on our application servers. This is related to the same issue from last week. The consultants have developed some theories to the cause and we continue to work towards a resolution. Additional updates will be posted as they become available.

Application Servers are back to normal

Recently we have been experiencing data load spikes on our application servers. This has resulted in intermittent slow downs as well as loss of connection for many users. The development team has been working diligently to locate the source of this problem, but at this time have been unable to pinpoint the exact cause. We have contacted the data center and are working with a consultant to assist in the investigation.

We understand the significant disruption this causes to each office and want to assure you that we are using every available resource to locate and resolve the cause of the recent server issues. We will continue to post updates as they become available.

All application servers are operating normally. We have confirmed the intermittent connectivity issues have been resolved and continue to investigate the cause.

We have restarted our servers in an effort to clear the connectivity issues. At this time, the servers are performing normally but we will be leaving the status level at yellow until we have confirmed that it has been resolved. We are currently investigating the cause of the problem and will continue to closely monitor the servers. Additional updates will be provided as they become available.

We are currently experiencing intermittent connectivity issues on our application servers that may cause a session time out error.  We are investigating the cause and will provide an update as soon as possible. Thank you for your patience.

At approximately 9:00 am Central some RevolutionEHR users experienced sporadic connectivity issues within the application.   The data center housing the RevolutionEHR servers reported that they were experiencing some problems that may have caused the connectivity instability.  They are still investigating the cause, but by 9:30 am the issue had been resolved.  We will provide more information as it becomes available.

Early this morning, an issue from last night’s release resulting in one of our reporting servers not accepting updates from our primary database. As a result, some of the reports/searches that you may have performed today did not return the correct results because the reporting server was not yet up to date. We have fixed the issue from the release, and have taken measures to prevent this particular issue from happening again.  Please refresh your browser if you have not yet done so, and your searches and reports will now return the results you expect.

We have discovered an issue that is affecting the deposit report, unassigned items report and the search screen under claims. Our engineers are actively working on a solution and we anticipate that this will be fixed soon. Thank you for your patience

The recent latency issues reported have cleared up. Our developers will continue monitoring the situation.

We are currently experiencing some latency and errors on one of our servers, the developers are assessing the issue. We will provide an update as soon as it is available

Some of our users experienced problems from spinning clocks to error messages. Our engineers identified an issue with one of the servers. Within 15 minutes of the first sign of a problem the offending server was restarted and is now operating normally. If you are still experiencing a problem, please refresh your browser.

We are currently experiencing some latency and errors on one of our servers, the developers are assessing the issue.  we will provide an update as soon as it is available

At approximately 7:34am CST today, RevolutionEHR experienced an outage. Data center and RevolutionEHR engineers were notified immediately and began troubleshooting. The root cause of the issue was a failed hardware switch at the data center that caused our database to go offline. Once the switch was back online, we were successfully able to bring the database up and RevolutionEHR application access was restored at approximately 8:10am CST.

We are working with the data center to understand how such a failure could affect the entire RevolutionEHR system and to come up with a solution to mitigate this risk in the future. We realize that any inability to access RevolutionEHR is a major impact to your practice. We continue to work closely with our data center partner to enhance the RevolutionEHR architecture to improve our system’s reliability and performance through increased redundancy and scalability.

We apologize for this morning’s outage and any inconvenience it caused your practice.

RevolutionEHR is currently down and we are working on resolving the issue as soon as possible.

Thank you for your patience over the past week as we have worked to resolve performance issues with our database.

The following is a summary of what caused the performance issues, what we did to resolve them and what we are doing to further improve performance in the near future.

Early last week we experienced performance problems with our database.  After a series of diagnostic tests over the course of a few days and with the help of our data center we were able to determine the cause of the problem to be related to a faulty hardware component on the SAN (Storage Area Network) on which the RevolutionEHR database is hosted.

Last night our data center replaced the faulty hardware component on the SAN and we have been monitoring the production environment today and have thus far seen the systems return to normal.

We are constantly monitoring RevolutionEHR performance to stay ahead of the resource load placed on the application.  We are on schedule to add more server resources to our data center next week which will boost our Reporting Server capacity and provide additional server resources for the application as needed.

Also, as a result of our database performance diagnostic testing, we are adding a number of performance improvement changes to the system that will go out with our next release.

Thanks again for your patience over this past week.  We are committed to providing you the best possible experience with RevolutionEHR.

Our partner integration functionality is now operating normally.

We have been monitoring the performance of the Reporting Server since our issue last night and can report that it is now operating normally.

The internet latency issues that were being reported over the past several days by www.internetpulse.net have substantially cleared up.

Due to the recent problems with the reporting server, some partner integration capabilities are not functioning.  We are working on the problem and will post updates as we have more information.

The reporting server is back up and we are monitoring its performance.

Our reporting server is experiencing a memory error – we are working on getting it back up.

We are aware of known internet latency issues today which have been detected on the Verizon backbone and possibly others. http://internetpulse.net/ is a site used to report internet health and is currently showing some areas of “critical” concerns.

Other sites are available to also report problem areas related to internet health. http://www.gomez.com/internet-health-map can be used to view different metrics in your area. When accessing this site change the “Location” to “US” and check the different options available in the “Metric” drop down.

While we are seeing better database performance over all, we continue to monitor the performance closely to ensure all issues are being resolved.

The issue related to accessing downloaded files on one of the application is resolved. Downloads of existing documents or images from the patient file is operational.

Currently an issue exists related to accessing downloaded files. This is only a problem on one of the application servers so not all practices are being affected by this problem. Those that are affected are not able to download any existing documents or images from the patient file.

We have been experiencing an unusually high load in the database that is causing intermittent slow downs to occur in the application. System maintenance will be performed this evening to assess the issue and work toward a resolution.

Our application servers are performing normally.

RevolutionEHR has experienced some slowness within our application servers today. In order to resolve this issue we will perform a restart of the servers. This will require taking the system down for a matter of minutes.
We are scheduling the restart for 12:45 pm Central Time. Please log out of RevolutionEHR prior to 12:45 pm Central. If you are logged in at that time you will lose your connection and will lose any data that is being entered at that time.

We appreciate your patience as we resolve this performance problem.

We are happy to notify you that the issue with posting payments has been resolved.  The development team determined that large queries being run caused some bottleneck interruptions. This problem has now cleared and you can resume posting your payments.

There is currently a problem with the posting of payments that is generating an error message when applying. The development team is currently working to resolve this and we will have an update very soon. We advise that you wait to post any payments until this issue has been resolved. Thank you for your patience.

The connectivity problems turned out to be a routing issue with an internet provider “upstream” from our data center.   Our data center was able to route around this issue.  And subsequently the underlying routing issue was also resolved.   All customers should be able to access RevolutonEHR.   Please contact us if you are sill having access issues.

We have recieved reports of some internet routing issues.   These are causing some customers difficulty in connecting to RevolutionEHR.   The symptoms are such that these customers may be able to hit other web sites but not maintain a consistent connection to the RevolutionEHR applications servers.

Our servers and database are running fine.  Our datacenter is also operational.  The issue appears to be with establishing a connection through the Internet to our data center.

We are monitoring the issue with our data center and will provide updates here.

The application server which was causing slowdowns today has been restarted after identifying the problem.  Users that were logged in to this server saw an interruption in their session and were required to login for a new session.

Some users are experiencing intermittent slowdowns when using the application this morning. The problem does not appear to be related to last night’s release. One of our application servers is overloaded and we are investigating the problem.

Our phone service has been restored.  We appreciate your patience during this time.

We are currently experiencing some intermittent outages with our phone system.  If you are unable to get through via phone please send a request through feedback for a call and our support team will return your call as soon as possible.

Our data center has resolved the temperature problems and have brought our database servers back online.

If you receive a system down page when attempting to access the system please try to clear your browser cache and reload the application.

Again, thank you for your patience,

Your RevolutionEHR Team

Our data center provider has informed us that they are experiencing environmental temperature problems in one of our server locations.  This has forced them to shutdown our database servers to prevent overheating and possible damage to server hardware.  They are working on the problem and hope to have it resolved soon.

Currently the application servers are operating but users will not be able to login until the database has been restarted.

Thank you for your patience,

Your RevolutionEHR Team

The carrier routing issues that were causing connection errors for some customers last week have subsided.   Please contact us if you are seeing any similiar issues as last week and we will investigate.

We have been closely monitoring our RevolutionEHR servers since this morning’s incident and they are currently functioning normally.   

The internet routing issues which we reported still appear to exist.  We continue to monitor this and are in communication with our data center regarding the larger overall internet status.

We have noticed some status issues with various internet networking carriers.  You can review status at http://internetpulse.net/    At this time our RevolutionEHR servers are operating normally.  We are in contact with our data center to assess whether the internet issues are effecting the data center. 

If you are kicked off the application, we recommend you reload your browser and log back in.   Please let us know if issues persist.

We are continuing to monitor the situation.

We have noticed a performance issue on one of our servers.    As the system adjusted users have been automatically moved over to another server.   This may have resulted in users being kicked out of the application.   Logging back allows the user to continue.

We are monitoring the situation.

The issue causing an error when logging into the patient portal has been resolved and RevolutionPHR is working normally.  We thank you for your patience while this problem was being addressed.

We are still investigating the cause of the RevolutionPHR log in error, but it is not resolved at this time.  We will continue to post updates as they become available.

Currently the log in for RevolutionPHR (the patient portal) is producing a general error message for all patients attempting to log in.  Our technicians are working to resolve this issue.  This problem is in no way affecting the RevolutionEHR functionality or performance, and is related only to RevolutionPHR.  We will continue to post updates as they become available.

Eyefinity reports that the issues they were having with their production environment have been resolved.

Eyefinity is currently experiencing a system degradation. They are addressing the problem, and expect to have this resolved soon. You may experience problems pulling authorizations or submitting VSP orders until the issue is resolved.

GatewayEDI has resolved the problem that was affecting claims submission.  You may begin submitting claims as normal.

IMPORTANT NOTE:  GatewayEDI is currently experiencing an outage that is preventing RevolutionEHR customers from submitting claims at this time.  All technicians at Gateway are working the problem.  If you receive an error message when submitting claims please wait and try again later.

Our data center discovered an issue with one of their primary internet connection partners.  Upon finding this, they altered the network configuration to bypass that connection until the issue was resolved.  The connection partner has since resolved their issue and network traffic has been restored to normal.

The issue appears to be resolved at this time but we are still waiting on final confirmation.

The data center has identified the issue and is currently working to resolve it.

Currently some RevolutionEHR users are experiencing very slow performance.  The RevolutionEHR servers are operating normally but it appears that it may be an issue in the network.  We are working with the data center to locate the problem and will continue to provide updates here.