Concurrency Locking
To prevent conflicting edits, AdvaPACS applies a concurrency lock whenever a user begins reporting an order. In rare cases, such as an unexpected browser closure or network interruption, a lock may remain after the user has left the reporting session.
The Concurrency Locking page enables administrators to review active locks and safely remove them when required.
Only unlock an order after confirming that the user is no longer actively reporting it. Unlocking an active reporting session may cause unsaved report content to be lost.
Accessing Concurrency Locking
To view and manage reporting locks:
- Navigate to Admin > Concurrency Locking.
- The Concurrency Locking page opens, displaying all currently locked orders.
- Use the available search and filter options to locate a specific lock if required.
Unlocking an Order
Before unlocking an order, confirm that the assigned user is no longer actively reporting. Removing a lock while a report is being edited may result in unsaved changes being lost. To unlock an order:
- Locate the order you want to unlock.
- Select the Unlock (🔓) icon.
- When prompted, type unlock to confirm the action.
- Click Confirm.
What Happens After Unlocking?
Once an order has been unlocked, it is immediately available for another authorised user to open and report.
If the original user was no longer connected to AdvaPACS, no further action is required. However, if they were still actively reporting when the lock was removed, any unsaved changes made during that reporting session may be lost.