A number needs its definition beside it

State the unit, numerator, denominator, period, source, and as-of date before interpreting a result.

Without those details, readers cannot tell what was counted or whether two values are comparable. The figures below are fictional, authored examples—not live analytics, a service benchmark, or a claim about any organization. A small sample describes only the reviewed entries in its stated context.

Sample measure dictionary

Fictional Harborview coordination-note example; no patient-level information is represented.

Sample measure dictionary
Measure Definition and context
Named-owner completeness Numerator: sampled handoff entries with a next owner explicitly recorded. Denominator: all handoff entries reviewed for the period. Unit: percent of entries.
Sample period Four weekly reviews, 6–27 April 2026. Example count: 80 entries reviewed across four samples.
Source Fictional manual review of the shared meeting-note entries; the example does not represent a connected data source.
Balancing consideration Team-reported time needed to complete the note, recorded as minutes per meeting; use a consistent local method if this is measured.
Limit This local, illustrative sample does not establish performance in other workflows or settings.

Illustrative values—not live metrics

Fictional sample only; source: manual review of 80 meeting-note entries over four weekly reviews, 6–27 April 2026; as of 27 April 2026.

60%

Baseline: 12 of 20 entries named a next owner in the first sample

75%

Final sample: 15 of 20 entries named a next owner in week four

4

Weekly samples reviewed; 20 entries per sample

Read the result with its limits

What was counted

Process measure

Named-owner completeness describes whether the agreed note field appears in sampled entries. It indicates a documentation process feature, not the quality or outcome of a care decision.

  • Keep the numerator and denominator visible.
  • Use the same inclusion rule each review.
  • Record missing or unavailable entries rather than silently excluding them.
What else matters

Balancing consideration

A team may also observe whether completing the note adds time or friction. That observation needs its own defined method and should be interpreted in context.

  • Do not infer causation from a before-and-after comparison alone.
  • Do not generalize a small local sample to another service.
  • Discuss unexpected effects with the relevant workflow owner.