01
Where it fits and where it does not
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.
- Limits
- 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
- Cross-cutting and Laboratory and Clinical teams working across Acquire → Harmonize → Exchange.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Cross-cutting and Laboratory and Clinical source data, metadata, and local mappings
- UCUMWhat changes
Use UCUM as a pinned terminology across Acquire → Harmonize → Exchange
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
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.
- Metadata vocabularyDPV
Both support Clinical and Cross-cutting work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - TerminologyLOINC
Both support Laboratory and Clinical work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileMIABIS
Both support Clinical and Laboratory work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - FrameworkFAIR
Both support Cross-cutting work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision UCUM must support.
Pin the exact version and companion artifacts: 2.2 · 2024-06-17.
Map one representative input to the required terminology artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
Syntactic validity does not prove that a unit is clinically appropriate, that a numerical value is plausible, or that arbitrary units are mutually convertible.
Run one representative end-to-end pilot and record exactly where UCUM loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
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
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
UCUM 2.2 specification
Official publisher or steward guidance for this terminology profile.
- Publisher
- Regenstrief Institute · UCUM Organization