Glossary

The headline metric: the readiness and response metrics of the five subsystems, rolled into one number (Measurement & the Score). The operational response times are reported beside it.

• Not: an outcome measure, a producer ranking, or a compliance certificate.
• Misapplication: optimizing the Score instead of the system it summarizes.

The two single-owner clocks that time at the hospital splits into at the transfer of care, for which the nurse signature may be used as a surrogate: transfer of care (at destination until care is transferred; definitive care's metric) and return to service (transfer of care to crew available; patient transport's metric). See Measurement & the Score.

• Not: one shared at-hospital number jointly blamed on both parties.
• Misapplication: publishing a single at-hospital duration and letting each side point at the other.

Unit-hour procurement, the deployment plan, response-time accountability, and billing are held by a single body, the procuring entity. The four always live in patient transport; which body is the procuring entity is the model choice (System Structure).

• Not: a prescription of which body. Every delivery model can satisfy the rule.
• Misapplication: splitting the four across bodies and expecting incentives to survive.

See the definition in Foundations.

• Not: the number of trucks owned, or units on a roster.
• Misapplication: treating readiness as a fixed asset rather than a per-hour, per-place quantity that expires.

An output ratio of workload to unit hours produced. ODS does not use it as a measure of performance. It is unactionable (an output, not a lever), no link to performance has been demonstrated, however it is computed, it is routinely misreported as a bounded percent though it can exceed 1.0, and it does not compare across systems. The causal, actionable signal it is mistaken for is concurrency.

• Not: an efficiency target, a performance indicator, or a percent.
• Misapplication: using UHU to judge how well a system performs.

The diminishing gain in response compliance from each added unit hour, derived from time-series analysis of concurrency; used in Production Analysis to find optimal production against a chosen standard.

• Not: a retrospective grade and not a mandate to cut to the last profitable hour. It shows what a standard requires in unit hours. It does not set the standard and it does not capture demand above what is expected.

A standard stated as "X% of responses within N minutes." The PUM's reform on the average, but it has its own blind spot: it treats every non-compliant call the same (a miss by one second and by an hour score identically) and buries the tail. ODS uses it as one tool in a battery, never as the sole truth.

• Misapplication: reporting a lone fractile as "the" performance and treating everything inside the compliant bucket as equal.

ODS's measurement stance: report each metric with a standardized battery of appropriate statistics (minimum, maximum, mean, standard deviation, fractile, the full distribution) matched to the community's values and needs, against well-calibrated benchmarks, rather than a single favored summary statistic. An average needs its standard deviation; a fractile needs its histogram. Statistical rigor and benchmark calibration are each their own discipline. Benchmark anchors come from the system's own chosen plan (rubric → financial sustainability → deployment plan). NFPA and NEMSQA are sources for metric definitions, never for anchor values.

• Not: a preference for any one statistic.
• Misapplication: reducing a metric to one number and calling it the truth, or anchoring a benchmark to an inherited external threshold rather than the plan the community chose and funded.

The time from the request being initialized to a unit arriving on scene. There are two, first response time and transport response time. Operational response time is not clinical. Measured against a response-time standard, which is a matrix of allotments by call priority and area density, not a single number. In the framework it is an input, not the system's verdict: the axis of the marginal utility curve that prices a chosen standard (Financial Sustainability; Measurement & the Score).

• Not: a producer metric (it is jointly produced and belongs to the procuring entity, which holds the deployment plan) and not the grade of the system. It spans more than one subsystem. Its intervals are scored in the subsystems that own them and the whole clock is reported beside the score.
• Misapplication: charging the producer for a number it does not control, or treating an inherited threshold as the verdict on the system.

A dynamic, demand-following deployment technique: moving units continuously to shadow expected demand. ODS supports it as one valid deployment model among several and mandates none of them. The model is chosen on the values of those charged to deliver care and bounded by the cost benefit analysis, with demand as an input rather than the master of the schedule. See the Deployment Plan. See Public Utility Model (PUM) and System Status Management (SSM).

• Common misapplication: citing ODS to justify demand-chasing deployment at the crews' expense.