Beyond the EHR: Extending Downtime Preparedness to Lab, Pharmacy, and Imaging Systems

18 November 2026

AUTHORED BY: Chloe Williams

Ask most hospitals about their downtime plan and you will hear about the EHR: the census, the medication administration record, registration, and documentation. Ask about the laboratory information system, the pharmacy system, or the imaging systems, and the answer is often that each department has its own procedure somewhere.

That gap matters because ancillary systems fail in ways an EHR-centered plan does not anticipate. They have their own vendors, their own downtime modes, and their own interfaces to the EHR. A patient can be harmed by a lab result that never posts, a medication order that never reaches the pharmacy, or a radiology report that never returns, all while the EHR appears to be running normally.

Planning beyond the EHR means treating each ancillary system as a link in a chain and asking what happens when any link breaks.

Three Outage Patterns to Plan For

  • EHR down, ancillary systems up. Orders cannot be entered, but analyzers keep running, pharmacy cabinets keep operating, and scanners keep scanning. The risk is lost orders and untracked results
  • Ancillary system down, EHR up. Orders flow out of the EHR, but nothing comes back. Clinicians may not realize results are delayed because the EHR looks normal
  • Interface down, both systems up. Messages stop flowing between systems. This is the quietest failure and often the most dangerous, because no one sees an error screen

The third pattern is why interface monitoring belongs in your downtime plan. Our post on what HL7 is and why it matters explains how these message feeds work. Our FAQ on using dbtech during a partial outage covers the mixed scenario.

Build a Dependency Map

Start with an inventory. For each ancillary system, record:

  • System name, vendor, and internal owner
  • Upstream sources and downstream consumers, including the interface engine
  • What it does for patient care in plain language
  • Its built-in downtime mode, if any, and how long it can run in that mode
  • The manual fallback and who is trained to use it
  • How data is reconciled after recovery
  • How you will know it is down, including interface alerts
  • The maximum acceptable downtime before patient safety is at risk
  • The date of the last test

The ONC SAFER Contingency Planning guide is a useful self-assessment for the EHR side of this work, and you can apply the same questions to each ancillary system.

Laboratory

What usually continues: analyzers, point-of-care testing, and specimen processing in many cases. What usually stops or degrades: order entry, specimen labeling from the EHR, result posting, and critical value alerts.

  • Prepare downtime requisitions that capture patient identifiers, ordering provider, tests, priority, and collection details. Our post on lab orders during EHR downtime describes how electronic requisitions and barcoded labels can be handled from downtime workstations
  • Define how results are delivered: printed, phoned, or logged, with a result log that records who received what and when
  • Require read-back and a written record for critical values
  • Confirm that the LIS can register patients with downtime encounter numbers and that those numbers can be matched back after recovery
  • Include blood bank and transfusion with strict two-person patient identification and your transfusion service’s own downtime procedures. AABB publishes standards for transfusion services
  • Review accreditation and regulatory requirements with your laboratory director, including CAP accreditation requirements and CLIA record-keeping expectations

Pharmacy

What usually continues: automated dispensing cabinets in a downtime or override mode, compounding, and manual dispensing. What usually stops or degrades: electronic order verification, eMAR and barcode medication administration, interaction and allergy checking, and charge capture.

  • Define how orders reach pharmacy when the EHR is unavailable, and who verifies them
  • Specify override rules for dispensing cabinets and who reviews overrides afterward
  • Provide nurses with the most recent medication administration record available, and set rules for documenting administrations on paper or electronic downtime forms
  • Apply independent double checks for high-alert medications according to your policy
  • Plan for reconciliation between cabinet transaction logs, downtime administration records, and the restored MAR
  • Use medication safety resources from ISMP and ASHP when building or reviewing these procedures

Our posts on ICU downtime and OR downtime show how medication and documentation risks play out in high-acuity settings.

Imaging

What usually continues: image acquisition on many modalities. What usually stops or degrades: orders and scheduling, modality worklists, access to prior images, reporting, and result delivery.

  • Prepare downtime order forms with patient identification, clinical indication, allergy and renal function information when contrast is involved, and ordering provider contact
  • Plan how technologists confirm patient identity at the modality when worklists are unavailable
  • Define how critical imaging findings are communicated and documented
  • Decide how reports are delivered if the results interface is unavailable
  • Consider teleradiology and off-site reading arrangements, and what they depend on
  • Review professional guidance from the American College of Radiology as you refine procedures
  • Plan how accession numbers and downtime encounter numbers are matched after recovery

The Cross-Department Chokepoints

  • Patient identification. Barcoded wristbands and labels are the connecting thread across departments. Our post on accurate patient identification during downtime explains why this matters
  • Downtime encounter numbers. Test whether every ancillary system accepts them and maps them back to the final EHR encounter
  • Time stamps. Specify how time is recorded when systems disagree
  • Safety checks. Contrast and medication safety checks depend on lab values, which means a lab outage can affect imaging and pharmacy
  • Charge capture. Ancillary services generate a large share of billable events, so documentation during an outage affects revenue recovery

Governance for the Wider Plan

  • Add ancillary directors to the downtime governance group
  • Maintain one downtime plan with department appendices rather than separate unconnected plans
  • Review vendor contracts for downtime support terms and response times
  • Monitor interface health continuously and assign someone to act on alerts
  • Include ancillary scenarios in drills, such as an LIS outage that lasts six hours or an interface that fails silently overnight
  • Measure time to detect, not only time to recover

Where dbtech Fits

dbtech does not replace your LIS, pharmacy system, or PACS, and it does not replace their built-in downtime modes. It supports the information and documentation layer around them. Depending on your configuration, the HL7 feed can keep patient demographics, census, and other configured data available on downtime workstations, eForms can provide requisitions, logs, and handoff forms, barcoded wristbands and labels support identification, and eFolders can store scanned documents and result logs for retrieval. Ask your dbtech team which message types are included in your configuration and how they apply to ancillary workflows.

To review where your plan stops at the EHR boundary, schedule a Downtime Audit Assessment or request a demo.

Want to learn more? Fill out the form below and a representative will call you ASAP!