ClinicalRate
Trust · The full storyNo black boxes

Methodology.

Every number you see in ClinicalRate carries its receipts. This is the full provenance chain from raw placement event to the percentile rendered in your browser.

Book a data demo →Read the chain
Sources
9 classes
Audit
Every row, every step
Refresh
24 hours
Statistical method
Empirical · winsorized
By the numbers

How defensibility shows up at each step.

9
Source classes

Public feeds, partner contributions, VMS ingests, public-domain.

0.92
Confidence floor

Records below threshold route to human review, never silently bucketed.

1.5×IQR
Winsorization

Crisis-rate outliers visible at p90 without bending the median.

n≥30
Distribution floor

Below floor, individual percentiles suppress and "thin market" surfaces.

The chain

From placement event to percentile, end to end.

01SOURCE

Permitted feeds, partner contributions, VMS ingests.

Nine source classes — public job-board feeds where re-use is permitted, contributing staffing agencies under data-share agreements, direct ingest from supported VMS platforms, and the curated public domain (BLS, state filings, public RFPs).

9 source classes · per-record provenance
02INGEST

Schema reconciliation.

Each source lands in a typed staging table with source ID, ingestion timestamp, and content hash. Duplicate detection runs before normalization — a single placement contributed by both an agency and a VMS is reconciled, not double-counted.

Idempotent · de-duped · hashed
03NORMALIZE

Resolve to canonical role.

Every record passes through the Taxonomy Mapper before it enters a distribution. Records that don't resolve at confidence ≥ 0.92 are routed to a human review queue, not silently bucketed.

428 roles · ≥0.92 threshold
04STATISTICS

Empirical percentiles, winsorized.

Linear-interpolated empirical percentiles on the trailing 30-day window, winsorized at 1.5×IQR to suppress single-record outliers. Never a mean masquerading as a median. Thin markets (n < 30) suppress individual percentiles and surface a "thin" indicator instead.

p10 → p90 · 1.5×IQR · n≥30
05SERVE

Provenance in every response.

Every UI cell and every API response carries as_of, sample_size, and the source-class distribution. Defensible by design — the buyer can always ask "where did this number come from" and you can answer in one click.

UI · API · CSV · all surfaces
What we don't do

Statistical pitfalls the platform refuses.

Pitfall

Mean dressed as median

Survey reports sometimes publish a "median" derived from a parametric fit. ClinicalRate uses empirical percentiles on the raw data — interpolation only, never assumption.

Pitfall

Mixed-cohort distributions

"RN" is not a role. The platform refuses to render a distribution that mixes ICU and Med/Surg, or travel and per diem, into one chart. Every distribution is a single canonical cohort.

Pitfall

Stale data dressed as fresh

Every cell carries its as_of timestamp. If a source feed lags, the affected distributions are flagged in the UI rather than served as current.

Pitfall

Outliers dragging the median

Crisis-rate placements ($300/hr Travel RN bookings during 2020) are real, but rare. Winsorization at 1.5×IQR keeps them visible at the 90th percentile without bending the 50th.

What you can verify

Open audits, on request.

Audit surfaceWhat you seeTier
Sample size on every celln events behind every percentile, in UI and API.All tiers
As-of timestamp on every cellMost recent ingest contributing to the cell.All tiers
Source-class distributionWhat share of the cell came from each of the nine source classes.Operator +
Per-record provenance traceDown to the individual record's source, ingest timestamp, and normalization confidence.Enterprise
Annual methodology audit by external firmReport shared under NDA.Enterprise
Comparison

ClinicalRate methodology vs. survey methodology.

The decisions that distinguish a defensible distribution from a polished number.

Capability
ClinicalRate
Empirical · winsorized · per-cell provenance
Conventional survey
Self-reported · annualized
Source
Reconciled placement events from 9 source classes
Self-reported employer/agency questionnaire
Refresh
Every 24 hours
Annual
Statistical method
Empirical percentiles, linear interpolation
Mean, parametric quartile fit
Cohort handling
Travel / per-diem / local separated
Often blended into one role row
Outlier handling
Winsorized at 1.5×IQR · visible at p90
Top-coded or removed silently
Per-cell provenance
Sample size + as-of + source mix
Methodology appendix
Thin-market handling
Suppress percentile, surface indicator
Render anyway, no warning
Enterprise tier · per-record provenance trace
The audit was three meetings, not three months. Every cell carried its receipts and our auditor signed off without a methodology dispute.
KP
Karen Park
Head of Internal Audit · Hospital system, 9 facilities
Where it shows up

Three teams who need methodology to be public.

What's included

Methodology access by tier.

ClinicalRate · Operator
From $4,000/ month

Provenance is a platform default, not an upgrade. Sample size and as-of on every cell, on every tier. Per-record trace and external audit on Enterprise.

Book a data demo →See full pricing
Included on this feature
  • Sample size on every cell (UI + API + CSV)
  • As-of timestamp on every cell
  • "Thin market" indicator below n=30
  • Source-class distribution (Operator+)
  • Per-record provenance trace (Enterprise)
  • Annual external methodology audit (Enterprise)
  • Versioned canonical taxonomy with changelog
  • No PHI, no patient data, ever
FAQ

Questions buyers ask about methodology.

A placement event is a contracted role × geography × rate × contract-class instance. We dedupe across source classes (a placement contributed by both an agency and a VMS lands once), retain only fields needed for the empirical distribution, and never ingest PHI or candidate-identifying fields.
They are real — and they belong at the 90th percentile, not the median. Winsorization at 1.5×IQR keeps them visible in the upper tail without dragging the central tendency. We never silently delete data points.
New roles are additive. When an existing canonical role is split or merged, we publish a versioned changelog with effective date, surface a banner on affected views, and keep the prior version queryable for 12 months for trend continuity.
Yes. We do not render distributions on cohorts below n=30; we do not publish individual employer/agency rates; we do not surface PHI under any contract. Every refusal is encoded in the platform, not a policy.
Other features

The rest of the surface.

Numbers with receipts.

Book a demo. Bring the question your CFO asked you that you couldn't answer — we'll show you where the answer lives in the chain.

Book a data demo →