Turning it off leaves a task behind
If a system helps prioritize a queue, disabling it does not remove the queue. Someone needs a workable alternative for prioritization and a way to identify items that may have been delayed or misrouted.
The fallback should be usable under the conditions that caused the problem.
Four decisions to make in advance
- Who has authority to suspend use?
- Which evidence or failure conditions trigger review?
- How are users told what changed and what to do instead?
- How are potentially affected cases identified for follow-up?
These are operational choices that should fit the clinical setting and governance process.
Reverting software may not revert data
A new version may have changed stored fields or produced outputs that remain in the record. Returning to an older model does not automatically remove those effects. Preserve an audit trail and define how corrections are handled.
Rehearse the fallback
A plan that depends on an unavailable account, an unknown contact, or an untested manual process may fail when needed. A controlled exercise can reveal these gaps.
Rollback is one response option. Some failures require fixing an input source, restricting use, or stopping entirely rather than restoring an older configuration that shares the same problem.
