Patient Flow Intelligence
The department where the queue forms is rarely the department causing it.
Flow problems present where they are visible — the emergency department, the recovery unit, the corridor. The constraint that created them is usually somewhere else entirely, and several hours upstream.
Works from bed state and discharge records your organization already captures daily.
The problem
Everyone knows flow is the problem. Nobody agrees where it starts.
Ask five leaders in the same hospital why flow is poor and you will get five confident, incompatible answers. The emergency department says beds. The wards say discharge. Discharge says pharmacy and transport. Pharmacy says they get the orders late. Each is describing something true from where they sit.
The reason the argument does not resolve is that nobody has the full sequence in one place. Flow data exists — admission times, bed assignments, discharge orders, actual departures, transfer requests — but it lives across systems and gets reported as departmental averages. A departmental average is precisely the format that hides a handoff problem, because the delay falls in the space between two departments and is therefore in neither one's report.
So improvement effort goes to whichever department is loudest or most recently escalated, the constraint moves somewhere else, and six months later the same meeting happens with different participants.
- Flow is discussed constantly and the constraint has never been definitively located
- Each department's own metrics look acceptable while the system performs badly
- Discharge orders are written at a reasonable hour and patients still leave late
- Boarding time is tracked as an average, which hides the hours it concentrates in
- Weekend and out-of-hours performance is known to be worse and is not quantified
- Improvement effort moves the constraint rather than removing it
Capabilities
What Vizier surfaces in flow data
Vizier evaluates movement through your organization continuously and raises where it is constrained — with the delay located at a specific step rather than attributed to a department.
Where the delay actually sits
The step in the sequence where time is being lost — between decision and action, between request and response — rather than the department where the consequence becomes visible.
Discharge timing and its causes
The distance between when a discharge decision is made and when the bed is actually released, and what accounts for the gap on the days it is worst.
Boarding and admission delay
Where admitted patients wait, for how long, and whether the constraint is bed availability or the process that releases beds.
Capacity loss, priced
What the constraint costs in bed days and available capacity, so flow competes for investment on the same terms as everything else.
Time-of-day and day-of-week pattern
When the constraint bites hardest, which is usually the difference between a staffing decision and a redesign programme.
Deterioration, early
Flow degrading on a specific unit or pathway while system-level metrics still look normal.
What a finding looks like
This is the finding that ends the argument. The wards were right that they were discharging on time, and the emergency department was right that beds were not appearing. Both were true, and the delay was in neither department's report because it fell between them.
Naming the window — weekday afternoons, 14:00 to 18:00 — turns a strategic flow programme into a scheduling question.
Discharge orders are written on time. The bed is not released for another five hours.
- Median time from discharge order to bed release is 5.1 hours on weekday afternoons.
- The same interval is 1.9 hours on weekday mornings, with comparable patient volume.
- The gap concentrates between 14:00 and 18:00 and does not appear at weekends.
- Discharge order timing itself is unchanged across all periods, so the delay is downstream of the clinical decision.
Review afternoon transport and discharge-pharmacy turnaround against the morning process, focusing on the 14:00 to 18:00 window on weekdays.
The reporting gap
Why departmental reporting cannot find a handoff problem
Flow is a property of the whole sequence. Reporting is organised by department. That mismatch is the entire difficulty, and no amount of departmental reporting resolves it.
- A delay between two departments appears in neither department's metrics.
- Averages across a full day conceal a constraint that bites for four hours.
- Each department optimises its own measure, which can push delay next door rather than remove it.
- Flow data is spread across systems and rarely assembled into one sequence.
- By the time a system-level metric moves, the constraint has been operating for weeks.
What this replaces
This replaces the flow improvement programme that keeps restarting
Most hospitals have run a flow programme. Many have run several. They typically begin with a diagnostic phase — often external, always expensive — that produces a point-in-time picture of where delay sits.
The picture is usually accurate and immediately begins to decay, because flow constraints move as soon as you change anything. Twelve months later the organization commissions another diagnostic.
Vizier does that diagnostic continuously from data you already capture, so when the constraint moves you find out in weeks rather than at the next engagement.
- External flow diagnostic engagements, and the decay of their findings
- Manual time-and-motion studies to establish where delay sits
- Analyst work assembling flow data across systems into one sequence
- The recurring cross-departmental meeting that relitigates the same disagreement
- Improvement capacity spent on the visible symptom rather than the located constraint
Who this is for
One constraint. Three teams who have been arguing about it.
COO / Operations
Where is the actual constraint, and what does removing it release?
- 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
What is flow costing us in capacity we are already paying for?
- Revenue leakage surfaced with the exposure quantified
- Reimbursement and payer performance movement, early
- Financial impact ranked so the biggest number gets attention first
Analytics / Data
How do we assemble flow data across systems without rebuilding it every time?
- Consistent definitions so two leaders asking the same question get the same answer
- Self-service investigation that does not generate another ticket queue
- Governance, access control and audit logging that survive review
Getting your data in
Start with bed state and discharge records.
Flow data is usually already captured — it is just captured in several places and reported departmentally.
- Daily bed state and census records you already produce.
- Admission, discharge and transfer timestamps from your EHR or PAS.
- Emergency department attendance and admission decision records.
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
Do you need real-time data?
No, and this is worth being clear about. Vizier is not a real-time bed management or command centre product — it does not tell you which bed is free right now, and if that is what you need, that is a different purchase. What it does is find the structural constraints in how your organization moves patients, from historical data, so you can remove them. Those two things are frequently confused during evaluation.
How does this relate to a capacity command centre?
They solve different problems and can coexist sensibly. A command centre manages flow as it happens. Vizier explains why flow is constrained in the first place and what removing the constraint would release. Organizations with a command centre often still cannot answer the second question, because operating a system and analysing it are different activities.
Our flow data is spread across several systems. Is that a problem?
It is the normal starting condition and one of the reasons this analysis rarely gets done internally. Vizier reads from multiple sources and assembles the sequence, which is precisely the work that otherwise consumes analyst weeks. Starting with two or three sources is fine; more improves the picture.
Can it separate avoidable delay from clinically necessary time?
It can identify where time is being lost outside the clinical decision — the interval between a discharge decision and the bed being released, for instance, which is by definition not clinical care. Where the question is genuinely clinical, that judgement stays with your team. The finding above is a good example: the clinical decision timing was unchanged, which is what made the downstream delay visible as a process problem.
How long before we see something useful?
Usually the first working session. Flow constraints tend to be strongly patterned by time of day and day of week, and that patterning is exactly what departmental averages remove — so it is often visible immediately once the data is assembled as a sequence.
Related reading
See where your flow constraint actually is.
Bring eight weeks of bed state and discharge records. Thirty minutes is usually enough to settle an argument that has run for a year.
Start with the data you already have. Connect your EHR when you’re ready.