Operational Intelligence
Average length of stay is an average of two very different things.
Most stays run close to expected. A small number run very long, and they account for most of the excess days. Reporting the mean blends them together and tells you nothing about either.
Case-mix adjusted from the start, because an unadjusted LOS comparison is an acuity comparison wearing a disguise.
The problem
Your LOS went up 0.4 days. That number contains no information.
It could mean every patient stayed slightly longer, which would suggest a systemic process change. It could mean eleven patients stayed three weeks each, which is a completely different problem with completely different actions. The mean cannot distinguish them, and the mean is what gets reported.
The second difficulty is acuity. Length of stay is supposed to move with case mix — sicker patients stay longer, and that is correct rather than a failure. Comparing raw LOS across units, sites or time periods without adjusting for that produces conclusions that are confidently wrong, and improvement effort gets spent on units that were never underperforming.
The third is that excess days concentrate. In most organizations a small proportion of admissions accounts for a large share of the days above expected, and those admissions usually share something — a discharge destination, a specific pathway, a dependency on a service that is only available on weekdays. Finding what they share requires cutting the data several ways, which requires an analyst, which is why it happens rarely.
- LOS is reported as a mean, and the discussion never gets past whether it went up or down
- Comparisons between units are made without adjusting for case mix
- Long-stay outliers are known about individually and never analysed as a group
- Nobody can say how many of your excess days are clinically necessary
- The weekend effect is assumed to exist and has never been quantified
- Improvement targets are set on the mean, which the outliers then dominate
Capabilities
What Vizier surfaces in length of stay data
The useful questions about LOS are all distributional. Vizier evaluates the distribution rather than the average, adjusted for case mix, and raises where excess days concentrate.
Case-mix adjusted position
Length of stay compared against expected for the actual patient mix, so a unit treating sicker patients is not flagged for treating sicker patients.
Outlier concentration
Which admissions account for the excess days, and what they have in common — pathway, destination, dependency, day of week.
Where the days accumulate
Whether excess time sits at the front of the admission, in the middle, or in the final period before discharge. Each implies a different cause and a different fix.
Avoidable versus necessary
Separating time attributable to process — waiting on a service, a destination, a decision — from clinically required stay.
Deterioration, early
A unit or service line drifting while the organization-level figure still looks stable.
Capacity released
What closing the gap is worth in bed days and the admissions that capacity would support.
What a finding looks like
The organization-level mean had moved by less than half a day, which is the kind of movement that gets noted and not acted on.
Underneath it, ninety-one percent of admissions were performing as expected and a small group was running eleven days long for a reason that has nothing to do with clinical care — and a weekday pattern that points straight at a specific process.
Nine percent of admissions account for forty-one percent of the excess bed days.
- Case-mix adjusted length of stay is close to expected for 91% of admissions.
- The remaining 9% run a median of 11.2 days beyond expected.
- Two-thirds of that group are waiting on an onward care placement rather than clinical readiness.
- Placement waits are markedly longer for admissions where the decision is made on a Thursday or Friday.
Review the onward placement referral process for decisions made late in the week, starting with what changes in availability between Thursday and Monday.
The reporting gap
Why the mean is the wrong statistic for this
Length of stay distributions are heavily skewed. Applying a measure of central tendency to a skewed distribution and then managing to it is a well-understood error, and it is what almost every LOS report does.
- The mean is dominated by outliers, so it moves for reasons that do not describe most patients.
- Unadjusted comparison between units is an acuity comparison, not a performance comparison.
- Reporting total LOS hides where in the admission the time is being lost.
- Long-stay patients are managed individually and rarely analysed as a cohort with a shared cause.
- Monthly reporting is too coarse to expose day-of-week effects, which are frequently the strongest signal.
What this replaces
This replaces the long-stay review that runs on individual patients
Most hospitals review long-stay patients — a weekly meeting, a list, a discussion of each case and what is holding it up. That review is clinically valuable and should continue.
What it cannot do is see the pattern. Reviewing patients one at a time is exactly the format in which a shared cause across forty admissions stays invisible, because each case has its own explanation and nobody is comparing them.
Vizier analyses the cohort rather than the case, and surfaces what the long stays have in common — which is where the systemic fix is.
- Analyst work to case-mix adjust LOS comparisons by hand, each time someone asks
- The monthly LOS report that reports a mean and prompts no action
- Manual review of long-stay lists to find a pattern nobody has time to look for
- External benchmarking exercises that report a percentile without a cause
- Improvement targets set on an average the outliers will dominate anyway
Who this is for
One skewed distribution. Three decisions hidden inside it.
COO / Operations
Where are the excess days, and what do they have in common?
- Throughput and patient flow constraints identified by location and service line
- Performance variability between sites made visible rather than averaged away
- Operational deterioration flagged while it is still a trend, not a crisis
CFO / Finance
How much capacity are avoidable days consuming, and what would releasing it support?
- Revenue leakage surfaced with the exposure quantified
- Reimbursement and payer performance movement, early
- Financial impact ranked so the biggest number gets attention first
Population Health / Quality
Is this variation clinical, or is it process?
- Care gaps and rising-risk cohorts prioritized by impact
- Measure performance variation against peer benchmarks
- Programs ranked by what the evidence says will actually move outcomes
Getting your data in
Start with discharge records you already produce.
LOS analysis needs less data than most people expect — admission and discharge timestamps with diagnosis coding are enough to get case-mix adjusted answers.
- A discharge extract with admission and discharge timestamps.
- Diagnosis and procedure coding, so comparison can be adjusted for case mix.
- Discharge destination and delay reason where your organization records it.
01
Upload
CSV, Excel, or an export you already produce. Drop it in and Vizier reads it. This is where most organizations start, and it is enough to see real findings against your own numbers.
02
Scheduled
A recurring feed over secure transfer, on whatever cadence your team already runs. No one re-uploads anything by hand, and nothing about your source systems has to change.
03
Connected
Direct read-only connectivity to your EHR or source systems via FHIR R4, HL7 v2, or vendor APIs. Vizier reads; it never writes back.
Connect your EHR when you’re ready. See supported systems.
Security and governance
The page your CIO will ask for
Security questions get answered before a demo, not after procurement stalls.
HIPAA compliant
PHI handled under HIPAA Security Rule safeguards.
BAA included
Executed within one business day, on every plan.
Encrypted throughout
AES-256 at rest, TLS 1.3 in transit.
Read-only access
Vizier reads from source systems. It never writes back.
Role-based access control
Scoped permissions with SSO available.
Audit logging
Every query logged with account, timestamp and result size.
Tenant isolation
Your data is segregated from every other customer's.
SOC 2 Type II audit underway
Not yet certified. Report available under NDA on completion.
FAQ
Questions buyers ask
How do you adjust for case mix?
By comparing observed length of stay against expected for the diagnosis, procedure and acuity profile of the actual patients, rather than comparing raw averages. This matters more than almost anything else in LOS analysis — an unadjusted comparison between a tertiary unit and a community one tells you which treats sicker patients, which you already knew. Where the coding depth is not sufficient to adjust reliably, Vizier says so rather than presenting an adjustment you should not trust.
Can it tell us which days were avoidable?
It identifies where time is being lost outside clinical care — waiting on a placement, a service, a decision, a destination — and how that concentrates. Whether a specific day was clinically avoidable is a judgement your clinicians make, and it should stay with them. What changes is that the judgement gets made about a pattern affecting forty admissions rather than one case at a time.
We already track LOS in our EHR. What does this add?
Your EHR reports the metric accurately. The questions that lead to action are distributional and comparative — which admissions drive the excess, what they share, whether the gap survives case-mix adjustment, where in the stay the time goes — and answering those means cutting the data several ways, repeatedly. That is analyst work, and it is the work this replaces.
Does this cover observation and short stay?
Yes, and the short end of the distribution is often more interesting than people expect. Stays that are unusually short relative to expected can indicate premature discharge, and where they correlate with readmission that connection is worth seeing — which is why LOS and readmission analysis belong in the same platform rather than two.
How does this differ from your patient flow page?
Length of stay is the metric; flow is the movement that produces it. This page is about the distribution of stay and what drives its tail. Patient flow analytics is about where in the sequence of movement through your organization time is being lost. They answer different questions from overlapping data, and most organizations end up wanting both.
Related reading
See where your excess bed days actually are.
Bring six months of discharge records. Thirty minutes, case-mix adjusted, and you will know which nine percent to look at.
Start with the data you already have. Connect your EHR when you’re ready.