Practical software guides
A clinic losing connectivity needs its approved clinical downtime procedure. This article only discusses testing access to administrative scheduling information; it does not prescribe emergency treatment, prescribing authority or a replacement patient record.
Use synthetic records for the software drill
| Step | Pass condition |
|---|---|
| Disconnect the test workstation | Authorised staff can read the approved minimal schedule |
| Use another staff role | Restricted information remains unavailable |
| Record a scheduling change | A unique temporary reference prevents duplicate re-entry |
| Restore connectivity | An authorised reviewer resolves conflicting changes |
| End the drill | Temporary copies are accounted for and securely removed under policy |
Do not interpret downtime as permission to copy a full patient database to personal phones, open public spreadsheets or shared chat channels. Any emergency access must follow the institution’s approved authority and be logged and reviewed.
Have clinical leadership, the privacy officer and the system supplier approve what may be available offline, how devices are protected and how changes re-enter the record. The SAFER Guides offer US health-IT safety guidance; they are not Bahamian law or validation of this specimen. The general outage playbook covers ordinary business recovery. No clinical drill or healthcare deployment is claimed.