Terminology · 2.2 · 2024-06-17

Unified Code for Units of Measure

Maintained by Regenstrief Institute · UCUM Organization

What it helps you do

Use UCUM when you need a machine-processable syntax and semantics for units, prefixes, compound units, and conversions.

  • Cross-cutting
  • Laboratory
  • Clinical
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits—and where it doesn’t

Use these four checks before committing implementation time.

Use it when
Quantitative values that must survive movement across instruments, laboratories, FHIR resources, CDISC datasets, and analytical stores.
Do not use it as
Do not treat UCUM as a complete solution on its own. Syntactic validity does not prove that a unit is clinically appropriate, that a numerical value is plausible, or that arbitrary units are mutually convertible.
Best for
Teams working with Cross-cutting and Laboratory and Clinical data across Acquire → Harmonize → Exchange.
Maturity
EstablishedEstablished enough for serious use; still pin the exact release and any implementation profile.

02

See it in the workflow

A standard creates value by changing a handoff, not by existing in a catalog.

  1. InputWhat starts

    Cross-cutting and Laboratory and Clinical data, metadata, and the local decisions around them

  2. UCUMWhat changes

    UCUM applies a shared terminology across Acquire → Harmonize → Exchange

  3. OutputWhat becomes possible

    A more consistent, reviewable handoff for the next system or team

Readiness gateBefore scaling: Syntactic validity does not prove that a unit is clinically appropriate, that a numerical value is plausible, or that arbitrary units are mutually convertible.

03

A concrete example

A pipeline stores the original result and display unit, validates the UCUM expression, and performs only dimensionally valid, provenance-recorded conversions.

Why it matters: Computable units prevent silent scale errors, but normalization must preserve original values, conversion rules, precision, and detection limits.

04

What it fits with

Complements LOINC observation identity, supplies FHIR Quantity units, and supports unit-bearing CDISC and clinical-safety data.

05

Implementation starter

Start with one bounded handoff. Pin, test, and review it before scaling.

  1. Name an accountable owner and the decision UCUM must support.

  2. Pin the exact version and companion artifacts: 2.2 · 2024-06-17.

  3. Map one representative input to the required terminology artifacts.

  4. Test the result against the canonical source and record every exception.

  5. Preserve the source data, mappings, and review evidence before scaling.

06

Limitation to test first—and the tests that catch it

Risk

Syntactic validity does not prove that a unit is clinically appropriate, that a numerical value is plausible, or that arbitrary units are mutually convertible.

Test

Run one representative end-to-end pilot and record exactly where UCUM loses context, needs an extension, or depends on another standard.

Risk

A structured or machine-readable result can still be unfit for analysis or AI.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Computable units prevent silent scale errors, but normalization must preserve original values, conversion rules, precision, and detection limits.

07

Why we believe this

Checked against the canonical source plus independent operational evidence from an adopter, regulator, or implementation report.

Evidence notation: E1 + E2. The code is shorthand; the plain-language statement above is the claim.

Formal status
Released UCUM specification 2.2
Confidence
High
Review state
Source-checked
Reviewed by
Scientific units reviewer
Last verified
13 July 2026
Review again when
Specification, essence-file, erratum, or implementation-binding update
How the evidence method works

08

Source shelf

Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.

  • Primary source2.2 · 2024-06-17

    UCUM 2.2 specification

    The canonical publisher or steward source used to verify this terminology profile.

    Publisher
    Regenstrief Institute · UCUM Organization
    Rights
    Rights remain with the publisher; this knowledge base links to the source rather than copying it.
    Access
    Opens the publisher's source in a new tab; no external media loads on this page.
    Verified
    2026-07-13
    Open at source

Next action

Put this profile in context

Compare its role with adjacent standards or place it inside an end-to-end data pathway before choosing an implementation.