Operational readiness is the work that turns a certified, equipped pharmacy shell into a department that can safely dispense a first dose to a real patient. It is where the physical build, the informatics build, and the staffed clinical workflow converge — and where an owner discovers whether the rooms, systems, and people were actually designed to work as one medication-use system rather than as three independent projects.
A pharmacy is unusual among hospital departments because its "go-live" is not a single event but a chain of interlocking activations: the cleanroom must be certified, the automation must be commissioned, the electronic health record (EHR) and pharmacy information system must be built and validated, the formulary must be loaded, the staff must be trained, and the closed-loop medication-administration technology must be working at the bedside. Operational readiness is the program that sequences and verifies all of this so that the medication-use process — prescribing, transcribing/order verification, dispensing, and administration — is safe from the first live order. The adjacent Articles in this chapter carry the deep detail on cleanroom certification and environmental sampling, on automation and first-dose activation, and on hazardous-drug safety and diversion control; this Article covers the operational-readiness program itself, the design of the medication-use workflow, and the EHR/pharmacy-informatics integration that ties the building to the clinical system.
Every design and activation decision in a pharmacy should trace back to the medication-use process — the sequence by which a drug reaches a patient. Understanding this process is what lets an owner judge whether a floor plan, an automation package, or an interface design is fit for purpose. The accepted framing of the process has five linked stages, each of which the facility and its systems must enable:
| Stage | What happens | What the facility/system must provide |
|---|---|---|
| Prescribing | Provider enters a medication order | Computerized provider order entry (CPOE) in the EHR with clinical decision support |
| Order verification (transcribing) | Pharmacist reviews and verifies the order | Pharmacy workstation, order queue, clinical-review tools, sightlines to verification area |
| Preparation/dispensing | Drug is compounded, packaged, and dispensed | Cleanrooms (USP <797>/<800>), carousels/packagers, IV workflow, automated dispensing cabinets (ADCs) |
| Administration | Nurse gives the drug to the patient | Barcode medication administration (BCMA) at the bedside, smart infusion pumps |
| Monitoring | Response and adverse effects tracked | EHR documentation, surveillance/alerting, pharmacist follow-up |
The two most consequential design ideas that flow from this process are closed-loop medication management and the five rights of safe administration (right patient, right drug, right dose, right route, right time). Closed-loop means that every stage is connected electronically and verified by barcode or other automated check, so that the order, the dispensed product, the cabinet, the pump, and the patient wristband are all reconciled against the same source of truth. A building that physically supports compounding and automation but is not wired for closed-loop verification has only solved half the problem. Operational readiness exists to prove that the loop actually closes.
Operational readiness planning (often called operational readiness and activation, transition planning, or simply "activation") is a structured program that runs in parallel with the late phases of construction and commissioning and continues through go-live. It is owned jointly by the activation/transition team and pharmacy leadership, and it is distinct from physical commissioning (functional performance testing of HVAC, power, controls) and from cleanroom certification (the regulated air and surface testing covered in the certification Article). Where commissioning asks "do the building systems perform?", operational readiness asks "can the department actually operate?"
A mature pharmacy readiness program typically organizes its work into a few recognizable streams:
The program is governed by an integrated activation schedule and a readiness-criteria checklist with explicit go/no-go gates. Each gate is owned, dated, and verified — a room is not "ready" because it looks finished; it is ready when it is certified, accepted, monitored, stocked, and staffed by trained people who have rehearsed the workflow in it.
The single largest non-construction workstream in pharmacy activation is the informatics build. Modern U.S. hospitals run an integrated EHR (the major vendors being Epic and Oracle Health/Cerner, with others such as MEDITECH in community settings) that contains the pharmacy module, CPOE, and the medication record. The pharmacy informatics build configures this system so that the medication-use process can run end to end.
The core build elements include: