Active Incident

Updated a few seconds ago

Incident Status

Partial Service Disruption

Components

QuickMAR, QuickMAR RX/Interface

Environments

QuickMAR RX/Interface, QuickMAR



June 19, 2024 2:48PM EDT
[Monitoring] Teams have implemented a fix last evening to address the cause of system slowness and have monitored throughout the day to confirm that the issue has been resolved. Teams have resolved the issues impacting some active integrated 3rd party vendors, preventing users from accessing their data on those platforms. Teams plan to enable scheduled task emails tomorrow to restore data review and reorder functionality. Further updates will be shared when available.

June 18, 2024 1:53PM EDT
[Investigating] Issues causing internal messaging performance slowness and "Application Error: Failed to Retrieve MessageList" errors in Messaging Center between Facilities & Pharmacies have been resolved. Investigations into performance degradation continue as issues are reported. Teams continue to investigate an issue impacting some active integrated 3rd party vendors that may prevent users from accessing their data on those platforms. Further updates will be shared as they become available. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 13, 2024 5:26PM EDT
[Investigating] We have resolved an issue that may have caused some pharmacies using the QuickMAR WebService to receive 502 gateway errors when posting messages between 1:00pm to 4:00pm EST today. We have been alerted to an issue with some active integrated 3rd party vendors that will prevent users from accessing their data on those platforms. We're investigating and will provide updates when available.

June 13, 2024 2:32PM EDT
[Investigating] Teams have confirmed that issues blocking data review, reorder emails and Framework reorders have been resolved as of 11:40pm EST yesterday (6/12). Issues leading to errors when accessing install links and request forms on the QuickMAR website or when attempting to login to the pharmacy portal have been resolved as of 12:25pm EST today. Investigations into performance degradation continue as issues are reported. Reports of degraded internal messaging performance causing slowness and "Application Error: Failed to Retrieve MessageList" errors in Messaging Center between Facilities & Pharmacies are being actively investigated. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 12, 2024 12:15PM EDT
[Investigating] Issues causing outdated data between Monday June 10th at 9:00am EST and Tuesday June 11th at 12:00pm EST in corporate console reports has been resolved. The cause of 502 gateway errors for pharmacy QuickMAR webservice message posting and slowness for clients receiving pharmacy orders have been resolved. Changes have been made to resolve blocking of data review and reorder emails, teams are currently monitoring and working to confirm resolution. Teams are monitoring performance and working to resolve any causes of impact. Teams are investigating errors when accessing the install links and request forms on QuickMAR website or when attempting to login to the pharmacy portal. Reports of degraded internal messaging performance causing slowness and "Application Error: Failed to Retrieve MessageList" errors in Messaging Center between Facilities & Pharmacies are being actively investigated. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 11, 2024 8:19PM EDT
[Investigating] Teams have been working diligently to resolve issues following the migration. As a result, creation of new training databases has been temporarily postponed.

June 10, 2024 3:04PM EDT
[Investigating] Teams have been alerted to issues starting this morning, leading to degraded performance of the QuickMAR application and are working to resolve. Some users may experience corporate console reports with stale data as of this morning. Some pharmacies using the QuickMAR WebService may receive 502 gateway errors when posting messages. Clients may experience slowness receiving Pharmacy orders. Teams are investigating errors when accessing the install links and request forms on QuickMAR website. System alerts triggered by disabled pharmacy interfaces will currently not send. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 7, 2024 12:58PM EDT
[Investigating] Teams are investigating an issue preventing the use of the install links in the QuickMAR pharmacy portal. Some pharmacies using the QuickMAR WebService may receive 502 gateway errors when posting messages, teams are currently investigating. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 6, 2024 4:24PM EDT
[Identified] Work to restore QuickMAR functionality continues to progress, teams will continue throughout tonight and will share updates in the morning. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 6, 2024 11:28AM EDT
[Identified] Teams continue to restore QuickMAR functionality and expect to have conclude the work today. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 5, 2024 5:46PM EDT
[Identified] Work to restore QuickMAR functionality continues, further updates will be shared in the morning. Pharmacies that have not yet restarted following the the Azure migration need to stop and restart their interface service.

June 5, 2024 3:25PM EDT
[Investigating] Teams are working to re-enable functionality of the QuickMAR and QuickMAR RX/Interface. Further updates will be shared as the work progresses.

June 5, 2024 1:27PM EDT
[Investigating] Teams continue to investigate and resolve potential causes of slowness, system health has improved as a result. Work to address login latency is currently underway. Some functionality such as scheduled task emails including data review and reorders are not currently operational.

June 5, 2024 11:58AM EDT
[Investigating] Teams are working to resolve the underlying issues causing performance degradation and intermittent errors on some pages. Some functionality including scheduled task emails including data review and reorders are not currently functional.

June 5, 2024 10:14AM EDT
[Investigating] Teams have been alerted to "Failed to retrieve MedsPassedList." errors and are investigating. Some functionality is still disabled, scheduled task emails including data review and reorders are not currently functional.

June 5, 2024 9:56AM EDT
[Investigating] Teams are investigating an issue that's causing some pages to intermittently fail to load starting at 4:00am EST. Some functionality is currently disabled, as a result pharmacy reorder messages will not currently send. As a result of the Azure migration all pharmacies need to stop and restart their interface service.

Senior Care EHR Application




Operational

Integrated Messaging Service




Operational

Skin & Wound




Operational

Secure FTP




Operational

Data Relay




Operational

PointClickCare Partner Marketplace




Operational

Nutrition Management




Operational

Home Health Care




Operational

Infection Prevention & Control




Operational

QuickMAR




Partial Service Disruption

QuickMAR RX/Interface




Partial Service Disruption

Care Insights




Operational

PAC Management




Operational

Performance Insights




Operational

Pharmacy Connect




Operational

Secure Conversations




Operational

Connected Care Center




Operational

National Care Collaboration Network (formerly Collective Medical)




Operational

PDPM Coach




Operational

Secure File Exchange




Operational

You can ascertain which environment your organization is operating in by looking at bottom right of any page after you have logged into the PointClickCare application.
You will find a line showing what server the page is being served up from similar to the following:
Version 3.7.7.2.8 - WWW2-012011-012011
The portion show in the example as "WWW2" portion will contain the environment from which your organization is being serviced.