OR scheduling and inpatient bed management are often treated as separate operational domains at regional hospitals. Surgical services manages the block schedule, allocates case time, and coordinates the pre-op and PACU workflows. Bed management handles the inpatient census, bed assignments, and discharge planning. In most regional health systems, these two teams share a phone number and not much else.
The consequence shows up in PACU. When the OR runs longer than scheduled, when a same-day add-on case arrives, or when a block release generates three back-to-back case completions in a two-hour window, PACU fills faster than the inpatient floor can absorb it. OR first-case on-time start rates fall to 58 to 72 percent at hospitals where scheduling data lives in disconnected systems. The delay is not always a surgical delay — it is often a bed delay masquerading as a surgical delay.
PACU overflow follows a predictable pattern. A case completes ahead of schedule, or an add-on case was scheduled that morning without checking available post-op capacity. The recovery room fills. Patients who are clinically ready to transfer to inpatient beds cannot move because the inpatient units have not been notified, beds are not cleaned, or the house supervisor is managing a separate ED boarding crisis simultaneously.
The delay compounds because PACU nurses cannot take another patient from the OR while holding a patient ready for transfer. OR cases back up. Surgeons wait. The charge nurse in PACU makes phone calls while managing clinical care. The house supervisor, working from a printed census sheet or a four-click EHR view, does not have a clear picture of which inpatient beds are available and which will be available in the next hour.
Most of the information needed to prevent this sequence exists in Epic Surgical Services and the ADT feed. The OR schedule shows which cases are running and when completions are expected. The ADT stream shows which inpatient patients are discharge-flagged. Combining these two data sources with a simple prediction model would allow the house supervisor to anticipate PACU demand 90 to 120 minutes before it materializes — enough time to pull beds ahead of the wave.
Two OR scheduling events create disproportionate PACU strain: same-day add-on cases and block releases. Add-on cases, by definition, arrive outside the morning schedule. They increase post-op demand at a time when inpatient bed availability has not been adjusted to accommodate them. Block releases, where a surgeon returns unused OR block time on the day of surgery, create back-to-back case completions that PACU was not staffed to absorb.
Both events are detectable in Epic Surgical Services as they occur. A monitoring layer that flags these changes and cross-references them against current PACU and inpatient bed availability can identify a conflict before it becomes a crisis. The relevant question is not whether PACU is full right now — it is whether PACU will be full in two hours given the current case list and the current inpatient census.
When that conflict is identified 90 to 120 minutes ahead of time, the house supervisor has options: pull discharge-flagged patients ahead of the formal discharge order, request bed-cleaning to be prioritized on the unit most likely to receive PACU transfers, or alert the OR charge nurse to sequence the remaining cases in an order that spreads recovery-room arrivals. None of these interventions require new staff or additional beds. They require information on the right timeline.
The practical integration challenge is that Epic Surgical Services and the ADT bed-management workflow are managed by different clinical teams with different Epic module configurations. A patient flow tool that reads from both modules needs FHIR API access to the surgical services schedule as well as the ADT stream — two separate scopes with two separate approval paths in the Epic configuration.
Regional hospitals that have completed this integration report that the technical work is straightforward once the Epic administrator configurations are in place. The more common delay is organizational: surgical services and bed management need to agree on who receives the conflict alerts and who is responsible for acting on them. That coordination agreement is the prerequisite that takes the longest to finalize, not the technical integration itself.
The operational result, once both pieces are in place, is that the house supervisor sees PACU pressure before it arrives rather than after. OR on-time start rates improve as a secondary effect, because cases that would have been delayed waiting for PACU to clear are sequenced earlier in the day when post-op bed availability is higher. The benefit is not limited to PACU — the whole surgical throughput chain runs better when the bed side of the equation is visible to the people scheduling cases.
