Peer Intelligence
Knowing you are in the 40th percentile is not the same as knowing what to do.
Benchmark reports arrive annually, compare you to a peer group you did not choose, and stop exactly where the useful part starts — which cohort is driving the gap, whether it is real, and what closing it is worth.
Your own data against your own history is available immediately. Peer comparison where the group is genuinely comparable — and an honest signal when it is not.
The problem
Every organization has benchmark reports. Very few act on them.
The pattern is familiar. A benchmark report lands, someone circulates it, a few numbers get discussed in a meeting, and the file goes into a folder. Nobody is being lazy — the report genuinely does not contain the information needed to act.
A percentile tells you where you sit. It does not tell you whether the gap is a real performance difference or an artefact of how your organization codes, which service line or cohort accounts for it, whether it is widening or closing, or what the gap is worth in money or bed days. Answering those takes an analyst several days per number, so it happens for one or two metrics a year and not at all for the rest.
The deeper problem is comparability. A peer group assembled on bed count and region can contain organizations with a materially different case mix, payer mix and catchment. Comparing against them produces a number that looks authoritative and means very little — and acting on it wastes real effort.
- Benchmark reports are annual, and out of date by the time they are read
- Nobody can say whether a gap is a performance difference or a coding difference
- The peer group is not obviously comparable and nobody has tested whether it is
- A percentile gets quoted in a board paper with no attached action
- Internal variation between your own sites is larger than the gap to the benchmark, and unmeasured
- You cannot tell whether last year's improvement effort moved anything
Capabilities
What Vizier surfaces in benchmarking
Benchmarking is only useful when it points at something. Vizier evaluates position, movement and cause together, and is explicit about when a comparison is not sound enough to act on.
Position with attribution
Where you sit, and which service lines, sites or cohorts account for the gap — so the conversation starts at the part you can change.
Movement, not just level
Whether the gap is widening or closing, and how fast. A stable 40th percentile and a 40th percentile falling from the 60th are different problems.
Internal variation first
Variation between your own sites and providers, which is frequently larger than the external gap and considerably more actionable.
Comparability signal
An honest read on whether a peer comparison is sound given cohort size, case mix and coding pattern — including when the answer is that it is not.
Real gap versus coding artefact
Whether an apparent difference reflects performance or documentation, tested against your own coding patterns before anyone launches an improvement programme.
Quantified opportunity
What closing the gap is worth in the unit that matters — money, bed days, or measure points — where the evidence supports an estimate.
What a finding looks like
The system-level percentile was accurate and useless. It described nine sites as one number and implied a system-wide problem that did not exist.
Two of the checks in this finding exist to prevent wasted effort: case mix ruled out an acuity explanation, and coding depth ruled out a documentation artefact. Only after both is the gap worth an improvement programme.
The gap to the peer benchmark is real, but it sits entirely in one service line.
- System-level length of stay sits in the 38th percentile against the peer group.
- Seven of nine sites are at or above the median; two sit well below it.
- Case mix index at the two sites is in line with the peer group, so this is not an acuity difference.
- Coding depth is comparable across all nine sites, which rules out a documentation artefact.
Review elective orthopedic pathway design at the two affected sites against the practice at the seven performing in line with peers.
The reporting gap
Why benchmark reports stop where they do
Benchmark products are built to compare, and comparison is genuinely hard to do well at scale. Explaining a gap is a different problem and requires data the benchmark provider does not have — your internal variation, your coding patterns, your pathway design.
- Annual cadence means the number describes a year you can no longer influence.
- Aggregation to organization level hides the site or service line that actually drives the gap.
- Peer groups are assembled on structural similarity, which is a weak proxy for clinical comparability.
- Coding differences read as performance differences, and there is nothing in the report to separate them.
- No benchmark tells you what closing the gap is worth, so prioritization happens on intuition.
What this replaces
This replaces the annual benchmarking exercise
Most organizations buy or subscribe to benchmark data, then pay again in analyst time to make it usable — reconciling definitions, cutting to service line, testing whether the comparison holds, and building the paper that explains it.
That cycle runs once a year for a handful of metrics because that is what the capacity allows, which means most of your benchmark data is never interrogated at all.
Vizier does the interrogation continuously across every metric you feed it, and raises only the gaps that are real, moving and worth something.
- The annual benchmarking analysis and the board paper built from it
- Analyst time spent reconciling benchmark definitions against your internal ones
- Manual testing of whether a peer comparison is sound before acting on it
- Improvement programmes launched against gaps that turn out to be coding artefacts
- Internal variation going unmeasured because external comparison absorbed the available time
Who this is for
One percentile. Three questions it does not answer on its own.
COO / Operations
Where are we genuinely behind, and which site or service line accounts for it?
- 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
Population Health / Quality
Is this gap a real performance difference or a documentation difference?
- 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
CFO / Finance
What is closing this gap actually worth, and is it the best use of improvement capacity?
- Revenue leakage surfaced with the exposure quantified
- Reimbursement and payer performance movement, early
- Financial impact ranked so the biggest number gets attention first
Getting your data in
Start with your own data and your own history.
The most useful benchmark for most organizations is their own past and their own internal variation, and neither requires a data submission cycle.
- An operational or quality extract you already produce for reporting.
- Case mix and coding data, so an apparent gap can be tested against acuity and documentation.
- External benchmark data you already subscribe to, where you have 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
Where does the peer comparison data come from?
Where a meaningful comparison group exists, findings include the benchmark position. We are deliberately not going to overstate this: for some cohorts and some measures the comparison group is too small, too dissimilar or too differently coded to be sound, and in those cases Vizier says so rather than showing you a percentile you should not act on. A confident-looking number built on a weak comparison is worse than no number, because someone will spend money on it.
Can it use benchmark data we already subscribe to?
Yes, and that is often the best arrangement. If you already have national or specialty benchmark data, feeding it in means Vizier can do the attribution and comparability work against your internal data — which is the part the benchmark provider cannot do and the part that makes the number actionable.
How do you tell a real gap from a coding difference?
By testing the apparent gap against your own coding patterns and case mix before presenting it as a performance difference — comparing documentation depth and acuity distribution across the sites or cohorts involved. Where those explain the variance, the finding says so. This matters because launching an improvement programme against a coding artefact is one of the more expensive mistakes in healthcare operations.
Is internal benchmarking useful if we are a single site?
Often more useful than external. Variation between providers, units, shifts and time periods within one organization is usually substantial, entirely within your control, and rarely measured systematically. A single-site organization has plenty to work with.
How is this different from the benchmarking in our quality platform?
Quality platforms generally show your position against a benchmark for the measures they cover, on their reporting cycle. What they tend not to do is continuously test whether the gap is moving, attribute it to a specific cohort, rule out coding explanations, and price the opportunity. That gap between knowing your percentile and knowing what to do about it is what this addresses.
Related reading
See where you actually stand, and what it is worth.
Bring an operational extract. Thirty minutes, and you will know whether your biggest gap is external or sitting between your own sites.
Start with the data you already have. Connect your EHR when you’re ready.