Avoidable hospital days are often described as discharge problems.
A patient is medically ready, but transportation has not been arranged. A skilled nursing facility has not accepted the referral. A medication requires authorization. Therapy has not completed an evaluation. A consultant recommendation is still pending. The family has not made a decision about the next level of care.
By the time one of these barriers becomes visible on the day of discharge, the additional hospital day can feel unavoidable.
But the delay often began earlier.
The more useful operational question is not simply:
“Why didn’t this patient leave today?”
It is:
“When did enough information exist to make the next decision, and what happened between that point and completion of the next action?”
That interval is decision latency.
In many hospital stays, avoidable time accumulates between four steps:
Information available → Decision made → Action executed → Patient progresses
Reducing that time does not mean rushing clinical decisions, discharging patients prematurely, or treating every additional hospital day as preventable.
It means reducing unnecessary waiting between clinically appropriate steps in care.
A Delay Seen Today May Have Started Yesterday
Consider a patient admitted with pneumonia who is improving but remains weak.
By hospital day two, it is becoming clear that the patient may not be able to return home independently. Physical therapy is not requested until late that afternoon. The evaluation occurs the next morning and recommends skilled nursing placement. Case management then begins discussing facilities with the family and sending referrals.
By hospital day four, the patient is medically ready but remains hospitalized awaiting placement.
The barrier recorded that day may be:
Awaiting skilled nursing facility acceptance.
That is accurate, but incomplete.
The decision latency may have started on hospital day two, when enough information existed to recognize that functional status and post-acute needs required earlier action.
The visible discharge barrier is often not where the delay began.
The same pattern occurs throughout inpatient care.
A specialty consultation is requested late even though the clinical question was apparent earlier. A diagnostic result is available but does not trigger a decision until the following day. Medication affordability, transportation, or post-acute needs are first addressed after everything else is complete. A goals-of-care discussion occurs later than the clinical trajectory warranted.
In each case, the visible barrier is real.
The operational question is how much time accumulated between recognizing the need, making the decision, and executing the next action.
Clinically Necessary Days and Operationally Created Days
Hospitals should be careful not to label every additional day as avoidable.
A patient who remains unstable, requires ongoing inpatient treatment, needs serial assessment, or is awaiting information genuinely necessary for a safe clinical decision has a clinically necessary hospital day.
That is different from a patient who is waiting primarily because the next step has not occurred despite sufficient information to move forward.
Operationally created time may include:
- A completed diagnostic study that has not triggered a decision
- A known barrier without a clear owner
- Therapy or case management involvement initiated too late
- Medication or transportation issues discovered only after other discharge work is complete
- A consultation requested without a defined decision that the recommendation is intended to support
Many additional days contain both clinical and operational elements.
The purpose of review is not to declare that a patient “should have been discharged.”
It is to determine whether progression stopped because the next clinically appropriate decision or action was delayed.
That distinction shifts the discussion away from individual blame and toward how the hospital moves work.
Sequential Work Creates Waiting
Many inpatient processes still operate sequentially:
Evaluation → Consultation → Testing → Decision → Therapy → Disposition planning → Medication access → Transportation
Some steps must occur in sequence.
Many do not.
A patient with a high likelihood of requiring rehabilitation can often receive a therapy evaluation while the diagnostic plan continues. Case management can begin understanding home support and post-acute options before medical readiness. Pharmacy can investigate coverage for a likely discharge medication while treatment is still being finalized. Family discussions can begin before the final discharge decision when a significant care transition is reasonably foreseeable.
Parallel work does not mean ordering unnecessary services early.
It means identifying dependencies early enough that they do not become the final unresolved barrier—particularly for patients whose transition requires several teams to act.
The goal is not to make every process happen sooner.
The goal is to prevent unnecessary sequential waiting.
Expected Date of Discharge Should Expose Decision Dependencies
Expected date of discharge can easily become another documentation field.
Used well, it is an operational tool.
If a patient is expected to discharge Thursday, the value is not simply having “Thursday” entered in the chart.
The value comes from asking on Tuesday:
What must be true for this patient to leave?
What information are we still waiting for?
What decisions will that information trigger?
Which services need to act?
Which barriers are already visible?
Who owns each unresolved dependency?
This is where expected date of discharge can reduce decision latency.
It creates a forward-looking reference point that helps the team identify work that must begin before the patient reaches medical readiness.
If the patient cannot leave on the expected date, the next question should be specific:
What decision or action is preventing progression?
If the answer is unclear, the plan may not yet have sufficient ownership.
Multidisciplinary Rounds Should Reduce Decision Latency
Multidisciplinary rounds can consume significant time while producing little forward movement.
Reviewing diagnoses, overnight events, tests, therapy status, disposition, and anticipated discharge may all be useful. But information exchange alone does not progress the patient.
Rounds should make the next decision visible and convert it into action.
For each meaningful barrier, the team should be able to answer:
What decision needs to be made today?
What action follows that decision?
Who owns completing it?
“Cardiology is following and we are waiting for recommendations” describes a state.
“We need cardiology’s recommendation on whether additional inpatient ischemic evaluation is necessary because that determines discharge. The primary team will escalate by noon if the recommendation is not available” defines the decision, dependency, owner, and timing.
Likewise, “patient may need placement” is not yet an action plan.
“Therapy will evaluate this morning. If skilled nursing is recommended, case management will begin facility discussions today rather than waiting for medical readiness” creates forward movement.
Effective rounds should shorten the interval between shared information and coordinated action.
A Simple Review of an Additional Hospital Day
Hospitals do not need a new software platform to begin identifying decision latency.
For a patient who remained hospitalized longer than expected, leadership teams can ask:
- What was the patient waiting for?
- When was that barrier first visible?
- When was enough information available to act?
- Who owned the decision or next action?
- What prevented it from occurring sooner?
- Was the delay clinically necessary, operational, or both?
The sequence matters.
If a patient stayed an additional day awaiting skilled nursing placement, labeling the case “placement delay” may obscure where the time was actually lost.
Perhaps placement genuinely could not occur sooner.
Or perhaps therapy was requested a day late. The family may not have been approached about facility preferences until medical readiness. Referrals may not have been sent because required documentation was incomplete. No one may have had clear ownership of moving the process forward.
The goal is to find the point where patient progression stopped and understand why.
Repeated case review can reveal recurring latency in specialty consultation, therapy evaluation, medication authorization, weekend diagnostics, family decisions, transportation, or escalation of unresolved barriers.
Those are operating conditions leaders can address.
A structured operational assessment can help organizations identify these patterns across workflows and distinguish isolated delays from recurring operational conditions.
“Length of stay is too high” is not.
Measure the Intervals Where Latency Accumulates
Average length of stay remains an important outcome measure, but it does not show where time is being lost.
A small number of operational intervals can provide more diagnostic value:
- Consult requested → consult completed
- Diagnostic result available → clinical decision
- Barrier identified → action assigned
- Medical readiness → discharge order
- Discharge order → patient departure
These measures should not become another large dashboard.
Their purpose is to identify where waiting consistently accumulates.
A long discharge-order-to-departure interval points to a different problem than delayed clinical decision-making. Slow consult turnaround requires a different response than medication authorization. A recurring delay between identifying a barrier and assigning an owner suggests a different operating problem altogether.
Length of stay tells leaders that time accumulated.
Decision and action intervals help explain where and why.
Length of Stay Reflects How the Hospital Converts Information Into Action
Length of stay is influenced by disease severity, patient complexity, post-acute capacity, payer requirements, community resources, and factors a hospital cannot fully control.
It also reflects how reliably the organization converts clinical information into coordinated action across the stay.
Physicians, nursing, case management, specialists, therapy, pharmacy, diagnostics, and operations all influence patient progression. No single department can independently control length of stay because the outcome depends on the connections between them.
That is why sustainable improvement requires more than asking physicians to discharge earlier or asking case managers to find placement faster. It requires understanding how work moves across the organization—and where unnecessary waiting, unclear ownership, and workflow gaps interrupt patient progression.
This is the focus of SummitPoint’s Operations & Throughput work: examining the operational processes that influence patient flow, discharge delays, inpatient length of stay, and workflow reliability.
The goal is not simply to make discharge faster.
It is to reduce unnecessary latency, strengthen coordination across teams, and make patient progression more reliable while preserving appropriate clinical judgment.
A SummitPoint Perspective
At SummitPoint Clinical Strategies, we view length of stay as an output of the hospital operating system.
The most useful reviews often focus less on the final barrier and more on three questions:
- When did the barrier become visible?
- When did enough information exist to act?
- Did the resulting decision have a clear owner and next action?
Our approach helps leaders distinguish clinical necessity from operational waiting and identify where the hospital can improve progression without compromising care.
When these patterns are examined across multiple cases, organizations can move beyond retrospective labels such as “placement delay,” “consult delay,” or “awaiting transportation.”
They can identify the underlying operating conditions that repeatedly create waiting—and redesign the work around them.
What decision or action most often keeps your patients in the hospital after the next step in care is already reasonably clear?