UCUM
- Stage boundary
- No direct role is recorded for Plan, Learn + reuse.
- Known 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.
Decision support
Compare standards by the job they do
Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.
Working set
Choose profiles
1 of 3 selected
UCUMTerminology
Decision lens
Compare roles before you compare maturity.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
- Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
- Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
- Test the boundary
Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.
Three-part assessment
See the reach, the gaps, and the evidence.
Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.
01 · Lifecycle reach
Where each profile contributes directly
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
| Profile | Plan | Acquire | Harmonize | Exchange | Learn + reuse |
|---|---|---|---|---|---|
| UCUMTerminology | Unified Code for Units of Measure has no direct role recorded in Plan. | Unified Code for Units of Measure has a direct role in Acquire. | Unified Code for Units of Measure has a direct role in Harmonize. | Unified Code for Units of Measure has a direct role in Exchange. | Unified Code for Units of Measure has no direct role recorded in Learn + reuse. |
Direct role recordedNo direct role recorded
02 · Boundaries
What each option does not cover
These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.
03 · Detailed assessment
Check the fit and evidence behind the map
Use the source, status, and limitation together. A higher maturity label does not erase a scope mismatch.
| Assessment | UCUMUnified Code for Units of Measure |
|---|---|
| Purpose & coverage | A machine-processable syntax and semantics for units, prefixes, compound units, and conversions. Best fitQuantitative values that must survive movement across instruments, laboratories, FHIR resources, CDISC datasets, and analytical stores. |
| Readiness stages | AcquireHarmonizeExchange |
| AI-ready contribution | Computable units prevent silent scale errors, but normalization must preserve original values, conversion rules, precision, and detection limits. |
| First limitation to test | Syntactic validity does not prove that a unit is clinically appropriate, that a numerical value is plausible, or that arbitrary units are mutually convertible. |
| Evidence | E1 + E2 High confidence Formal statusReleased UCUM specification 2.2 ReviewSource-checked |
| Maturity | Established Stable formal grammar with computable release artifacts and broad healthcare use |
| Sources & links | UCUM 2.2 specification (opens in a new tab)Read full profile |