Description
Invoke the linked UID spelling inspector, count dot-separated components, and combine its length and leading-zero checks as encodingSpellingValid.
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.
Invoke the linked UID spelling inspector, count dot-separated components, and combine its length and leading-zero checks as encodingSpellingValid.
When to use this tool
Use DICOM UID Component Count when you need one bounded spelling, delimiter, or identifier component.
How to use the tool and how it works
- Enter uid. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read componentCount, encodingSpellingValid. Inspect encodingSpellingValid before interpreting the associated values.
Invoke the linked UID spelling inspector, count dot-separated components, and combine its length and leading-zero checks as encodingSpellingValid.1
The linked UID inspector supplies leading-zero indexes and the unpadded length flag; this wrapper combines them and adds a component count.2
DICOM UID components use decimal digits and prohibit non-significant leading zeros in their encoded spelling. Their numeric components must not be interpreted as clinical or object semantics; assignment and uniqueness require separate controls.3
| Input field | Meaning and units | Accepted input |
|---|---|---|
| uid | Uid | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| componentCount | Component Count | Required. Safe integer. |
| encodingSpellingValid | Encoding Spelling Valid | Required. Boolean. |
{
"input": {
"uid": "1.2.840.10008"
},
"output": {
"componentCount": 4,
"encodingSpellingValid": true
}
}Limitations and assumptions
- Component count does not reveal UID meaning, registration, or uniqueness; this checks an unpadded spelling rather than complete DICOM value encoding.
- 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
-
Calculation and input contract: health-informatics/dicom-uid-component-count — tool.io
-
Calculation or validation: health-informatics/dicom-uid-leading-zero-guard — tool.io
-
DICOM PS3.5: Unique Identifiers — DICOM Standards Committee / NEMA
Similar or alternative tools
- DICOM Decimal String Scale
Return fractionDigits, safe-integer exponent, and fractionDigits-exponent as lexicalScale.
- DICOM Decimal String Exponent Guard
Convert to a finite Number and return the trimmed lexical token and hasExponent.