Short answer: When PACS, the diagnostic viewer or the worklist fails, your first jobs are to confirm the scope, keep modalities scanning safely, protect patient identifiers, and activate a documented catch-up plan so studies are not lost or mislabeled. A downtime playbook that names who to call, how techs will work without MWL, where temporary images go, and how you reconcile when the system returns will cut chaos in the first hour and the backlog afterward.

PACS outages happen. Storage fills up, a network path drops, a vendor patch breaks a viewer, an HL7 feed stalls the worklist, or a single point of failure takes down the archive. Imaging cannot stop for long. Emergency and inpatient exams still need to be acquired and read. The difference between a controlled downtime and a messy one is almost always preparation.

Confirm what is actually down

Before you page everyone, spend two minutes defining the problem.

Write the scope on a shared channel or whiteboard so techs, radiologists and help desk share the same picture. If images are not arriving at all, our DICOM send troubleshooting guide covers the common causes. For worklist-only failures, see the modality worklist troubleshooting guide.

Hospital IT specialist on a phone call coordinating PACS support from an admin desk

Who to call in the first fifteen minutes

Have a one-page contact list that is not locked inside the system that just failed.

  1. Imaging IT / PACS admin — own the technical triage and vendor tickets.
  2. RIS / EHR interface owner — if orders or MWL look wrong.
  3. Network / server team — if storage, DNS, VPN or load balancers are involved.
  4. PACS vendor support — open a severity-1 ticket early with AE titles, error codes and a timeline.
  5. Radiology leadership and ED charge — so clinical teams know what to expect for turnaround.
  6. Reporting / speech system owner — if PowerScribe or another reporting tool depends on the same worklist or study open.

Escalate on a clock, not on hope. If the first responder has not restored service or a clear workaround in 15–30 minutes, call the next layer and the vendor.

Keep scanning without making a bigger mess

Modalities can usually keep acquiring. The risk is wrong patient IDs, lost studies and unreadable temporary media.

Never “guess” an accession to get the scanner moving. Fixing a misidentified study later costs far more than a short delay to verify IDs.

Reading and reporting during downtime

Radiologists need a defined path for STATs and for everything else.

Home reading stations often fail differently from on-site stations (VPN, MFA, DNS). Test those paths in drills, not during a real outage. Our home reading station checklist covers the basics.

Radiology technologist at a CT console continuing to scan during system downtime

Catch up when PACS comes back

Restoration is only half the work. Catch-up is where studies get lost if you skip the checklist.

  1. Confirm C-STORE and MWL with a test patient before releasing the flood of queued studies.
  2. Send from modalities in a controlled order — STATs and ED first, then inpatient, then outpatient backlog.
  3. Reconcile the downtime log against the PACS worklist and RIS: every downtime accession should exist once, with the correct patient.
  4. Check for duplicates and orphans — same study sent twice, or studies with temporary IDs that need merge/fix.
  5. Verify priors for the first wave of reads so radiologists are not comparing against incomplete history.
  6. Interface catch-up — confirm HL7 orders and results that queued during the outage drained cleanly into RIS/EHR and reporting.
  7. Hold a short debrief the same day: root cause, duration, what worked, what to change in the playbook.

Prevent the next outage

Most “sudden” PACS downs were visible in monitoring or capacity trends for weeks.

If your archive is aging or you are planning a move, a deliberate PACS migration or VNA strategy reduces the chance that the next failure is unrecoverable.

Frequently asked questions

Should we stop all scanning when PACS is down? Usually no. Keep acquiring emergency and necessary inpatient exams with a documented downtime ID process. Elective outpatient imaging may be delayed depending on how long the outage is expected to last.

What is the biggest downtime risk? Mislabeled or lost studies — wrong MRN/accession entered at the console, or queued images never sent after recovery.

Is a slow PACS the same as downtime? Not always, but a severely slow system can force the same workarounds. See our guide on why PACS gets slow.

How often should we drill? At least annually, and after major PACS, network or reporting changes.

Get help hardening your PACS and downtime plan

Sacred Heart Imaging Solutions provides PACS install and upgrade support, data migration, EHR/RIS integration, PowerScribe-related workflow help and practical radiology IT consulting, remote from Murrieta, CA. Cesar Ramirez works as a PowerScribe Implementation Engineer on Nuance/Microsoft PowerScribe One and mPower rollouts and has years of PACS administration experience across hospital environments. You can read more about his background at CesarRamirez.com.

If your team needs a downtime playbook review, a PACS health check or help after a painful outage, contact us or email [email protected] to talk with a PACS consultant.