The pharmacy distribution model is the strategic decision about where medications are prepared, stored, and dispensed across the building — and that decision is a primary driver of program area, vertical transport, electrical and IT infrastructure, and the layout of nearly every inpatient unit. Getting it right early lets the design team place the central pharmacy, size satellites, and lay in the automated-dispensing-cabinet (ADC) network as a coordinated whole rather than as an afterthought.
A medication has to travel from a receiving dock to a patient's bedside. The distribution model defines that journey: the degree of centralization, the number and location of preparation/dispensing nodes, the transport mechanism between them, and the technology that controls inventory and access along the way. Three families of models exist in U.S. hospitals, and most facilities run some blend of them.
| Model | Where doses are prepared/dispensed | Typical use |
|---|---|---|
| Centralized | A single central pharmacy prepares and dispenses nearly all doses; units receive cart-fill deliveries and replenishment | Small to mid-size hospitals; cost-efficient; minimizes duplicate cleanroom/automation capital |
| Decentralized | Pharmacy services are pushed out to satellites and unit-based ADCs near the point of care | Large academic medical centers, where travel distance and turnaround time at scale justify duplication |
| Hybrid (most common) | A strong central pharmacy for sterile/hazardous compounding, batch production, and inventory, plus a network of ADCs (and selected satellites) at the point of care | The dominant U.S. pattern — central compounding/control with decentralized first-dose and PRN access |
The practical reality in nearly all modern facilities is a hybrid: USP <797> sterile compounding and USP <800> hazardous-drug compounding are too capital-intensive and too tightly regulated to replicate, so those stay centralized, while routine inpatient dispensing is decentralized to ADCs on every unit. The design question is rarely "centralized or decentralized" — it is "how decentralized, and through what nodes."
Think of distribution as a tiered network. Each tier is a physical place that needs floor area, power, data, security, and (sometimes) refrigeration and environmental monitoring.
Distribution between tiers happens by some combination of staff courier, pneumatic tube, dumbwaiter/cartlift, autonomous mobile robots (AMRs), and — for routine bulk — scheduled cart exchange. The transport strategy is a building-systems decision that must be set with the pharmacy model, because it dictates tube-station counts, shaft locations, and corridor clearances.
A satellite is a decentralized pharmacy node placed close to a high-volume or high-acuity service so that pharmacists and doses are near the point of care. Satellites trade duplicated infrastructure cost for reduced turnaround time, shorter transport distances, and clinical pharmacist presence on the unit.
Common satellite locations:
Design implications of a satellite. A satellite is a small pharmacy and inherits a scaled version of the central pharmacy's requirements: secured access control and audit trail, possibly a small controlled-substance storage point (to DEA standards, with diversion-control monitoring), refrigeration with continuous temperature monitoring, dedicated and ideally emergency-backed power, robust data drops, and — if it compounds — its own classified cleanroom(s) with the attendant HVAC pressure cascade, HEPA filtration, ISO classification, and a certification gate. A compounding satellite is effectively a second cleanroom suite to commission, with all the schedule and cost that implies. Satellites should be justified by genuine volume and acuity, not convenience, because each one adds recurring staffing and infrastructure burden.