These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- ITSM for Healthcare and Hospitals
- Features
- Downtime and impact
Downtime and impact
Record care impact and restoration evidence.
OverviewClinical Impact Queue×
ITSM for Healthcare and Hospitals · Downtime and impact
New
Clinical Impact Queue
Clinical service impacts
| Id | Clinical service | Patient care impact | Downtime procedure | Incident | Clinical owner | |
|---|---|---|---|---|---|---|
| IDD-406 | CS-211 | Delayed | DP-353 | INC-2379 | ||
| IDD-258 | CS-925 | Unavailable | DP-848 | INC-6458 | ||
| IDD-701 | CS-262 | Delayed | DP-686 | INC-4005 | ||
| IDD-724 | CS-477 | Unavailable | DP-675 | INC-3430 | ||
| IDD-583 | CS-831 | Delayed | DP-671 | INC-4048 |
6 of 6 records
IDD-406Clinical service impacts · CSI-69469
DelayedClinical serviceCS-211
Downtime procedureDP-353
IncidentINC-2379
What you can do
Follow the working record
An outage delays patient intake. The responder links a clinical impact record to the incident, names the affected clinical service and clinical owner, and records the care impact. The attached downtime procedure guides temporary work. The downtime register holds the outage start and restored time against the same incident so the clinical owner can review the period of disruption.
The clinical impact record names the affected care service, impact level and clinical owner. Its procedure is an attachment on that record. The linked downtime register provides outage start and restoration times; those times require review against the incident because the register also carries store-oriented identifier fields.
How the work is organized
- Impact. The Incident Responder links the affected incident and records None, Delayed or Unavailable care impact.
- Procedure. Attach the downtime procedure used for the affected service and identify its clinical owner.
- Restoration. Record outage and restored times against the same incident, then compare them with the responder’s update.
A restored time should follow the outage start. Keep the care impact and technical restoration evidence together for clinical review.
What to agree during setup
Agree which clinical owner confirms the impact classification and which approved procedure applies to each service. Define who records the outage start, who confirms restored time and how the team handles partial restoration. Map the incident reference before importing older downtime entries.
Test a case where care was Delayed and a case where it was Unavailable. The owner should be able to locate the attached procedure and explain when normal work resumed. Do not infer care impact solely from an outage duration.
Check the handoff on an actual case
Rehearse a patient intake interruption. Link the impact record to the incident, name the clinical service and owner, then attach the procedure used by staff. Record the start of the interruption and later its restored time on a register entry linked to the same incident.
Have the clinical owner inspect the impact and the responder’s updates. If the recorded restoration precedes the start or points to a different incident, correct the reference before closing the case. The service manager can then review the complete history.
Keep the incident and impact reference together while the clinical area uses a temporary procedure. A technical restoration time and a care impact classification answer different questions. Ask the clinical owner whether the care service was again available, then let the service manager compare that account with the incident updates and outage times.
What your team sees
- Clinical Impact Queue — Review the filtered records and choose the next action.
- Open Clinical Incidents — Open related records before the handoff.
Follow the work through
What it keeps track of
Data model- Clinical service impacts
- Clinical Service Impacts records for IT service and asset operations.
- Clinical downtime register
- Register Outages records for IT service and asset operations.
- Incidents
- Clinical system incidents with priority, assignment and resolution state.
- People
- People records for IT service and asset operations.
Who uses it
Permissions- Incident Responder
- , Service Manager, Clinical Service Desk Analyst
Set up ITSM for Healthcare and Hospitals your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.