Issue with Scribe "Sent to Colleague" status

Update
A fix has been released to all impacted organisations and workspaces. Accurx will continue closely to monitor this incident and provide relevant data directly to assist those impacted.

If you have any immediate questions or concerns, please reach out to our Support Team.

Update
The proposed fix is being trialled at a single organisation. We are continuing to verify the success of this and we will deploy the change to all impacted users upon confirmation of success across all Send to colleague flows.

If you have any immediate questions or concerns, please reach out to our Support Team.

Update
We are continuing to carry out further tests across workspaces. Pending successful verification, we will deploying this fix to all impacted users.

Next update: 15:00 PM.

If you have any immediate questions or concerns, please reach out to our Support Team.

Update
A fix has been developed and is currently undergoing testing in a pilot environment. Pending successful verification, we expect to begin deploying this fix to all impacted users by 12:00 PM tomorrow.

Next update: Tomorrow by 12:00 PM.

If you have any immediate questions or concerns, please reach out to our Support Team.

Summary
An issue has been identified with the Scribe ‘Send to colleague’ flow where a consultation will be shown as ‘Sent to colleague’ even if a user exited the flow before clicking the final ‘Send’ button. In such cases, the letter/note will not have been sent.

Impact
The issue only affected cases where users selected the ‘Send to colleague’ button, but then abandoned the flow. If users completed the flow by clicking on the send button, the scribe note will have been sent successfully.

We have contacted affected users and organisations directly, and are working on a fix for this issue.

We will keep this page updated as we progress.
If you have any immediate questions or concerns, please reach out to our Support Team.