Skip to content

Main content

Clinical Unit Case Sensitive Prefix Tag Tool

Detect exact versus case-only unit spelling differences; no automatic UCUM case normalization or dimensional equivalence is asserted.

Loading tool…

Description

Return exactMatch and caseOnlyDifference when unequal spellings become equal under JavaScript lowercase.

Clinical exchange formats use exact delimiters, character grammars, and scoped identifiers. A local token check addresses one syntax condition and can succeed without validating a complete message or its clinical meaning.

Return exactMatch and caseOnlyDifference when unequal spellings become equal under JavaScript lowercase.

When to use this tool

Use Clinical Unit Case Sensitive Prefix Tag when you need one bounded spelling, delimiter, or identifier component.

How to use the tool and how it works

  1. Enter firstUnit, secondUnit. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read exactMatch, caseOnlyDifference. Inspect exactMatch, caseOnlyDifference before interpreting the associated values.

Require nonempty firstUnit and secondUnit. Return exactMatch and caseOnlyDifference when unequal spellings become equal under JavaScript lowercase.1

UCUM defines a case-sensitive symbol representation. Lowercase similarity is therefore a spelling diagnostic, not a justification for changing the case of a clinical unit code.2

Input fieldMeaning and unitsAccepted input
firstUnitFirst UnitRequired. Text; maximum UTF-16 length 8192.
secondUnitSecond UnitRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
exactMatchExact MatchRequired. Boolean.
caseOnlyDifferenceCase Only DifferenceRequired. Boolean.
json
{
  "input": {
    "firstUnit": "mL",
    "secondUnit": "ml"
  },
  "output": {
    "exactMatch": false,
    "caseOnlyDifference": true
  }
}

Limitations and assumptions

  • Case similarity is a diagnostic rather than permission to normalize units; full unit grammar, prefixes, dimensional equivalence, and safe conversion are not evaluated.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use the relevant full standard, implementation profile, and validated parser when interoperable or clinical record validity matters.

References

  1. Calculation and input contract: health-informatics/clinical-unit-case-sensitive-prefix-tag — tool.io

  2. The Unified Code for Units of Measure, Version 2.2 — UCUM Organization

Similar or alternative tools