Slowness with Clinical Encounters

Incident Report for RXNT

Resolved

This incident has been resolved.
Posted Apr 28, 2026 - 07:50 EDT

Monitoring

The solution is now live, and initial data shows that the module has returned to its optimal performance levels. To ensure the system remains stable and responsive under all conditions, our engineering team will continue to monitor the results closely throughout the weekend.
Posted Apr 24, 2026 - 15:30 EDT

Update

We have made significant progress in addressing the intermittent slowness and performance lag reported within the Encounter Module.

Our engineering team has successfully traced the issue to how internal processes manage system memory during specific tasks.

A fix has been developed and is currently undergoing rigorous testing in our Quality Assurance (QA) environment. We are verifying the solution to ensure it fully restores performance without introducing any new issues. This is strictly a performance-only issue. Your data remains secure and fully intact. No other modules or areas of the platform are affected by this behavior.

We will provide a final update as soon as the fix is cleared for deployment. We sincerely apologize for the frustration this has caused and appreciate your patience as we finalize the resolution.
Posted Apr 24, 2026 - 13:00 EDT

Identified

The issue has been identified and a fix is being implemented.
Posted Apr 24, 2026 - 09:00 EDT

Monitoring

We are monitoring the results of the fixes.

If you have not already done it, please clear your browser's cache and cookies. More information on the link below: https://help.rxnt.com/hc/en-us/articles/360058631093-RXNT-System-Requirements#h_01HBRNVCH6MV01ZQRG23TMTJE6
Posted Apr 23, 2026 - 14:06 EDT

Identified

In order to improve system stability, we rolled back some of the recent encounter changes around 10:00 AM ET.

If you have not already done it, please clear your browser's cache and cookies. More information on the link below: https://help.rxnt.com/hc/en-us/articles/360058631093-RXNT-System-Requirements#h_01HBRNVCH6MV01ZQRG23TMTJE6
Posted Apr 23, 2026 - 10:58 EDT
This incident affected: Electronic Health Records (Clinical Encounter).