Description
Return zero-based indexes of multi-digit components starting with zero and whether the unpadded spelling has at most 64 characters.
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 zero-based indexes of multi-digit components starting with zero and whether the unpadded spelling has at most 64 characters.
When to use this tool
Use DICOM UID Leading Zero Guard 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 leadingZeroComponents, withinLengthLimit. Inspect withinLengthLimit before interpreting the associated values.
Require dot-separated nonempty decimal-digit components. Return zero-based indexes of multi-digit components starting with zero and whether the unpadded spelling has at most 64 characters.1
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.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| uid | Uid | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| leadingZeroComponents | Leading Zero Components | Required. Array of safe integer; maximum items 256. |
| withinLengthLimit | Within Length Limit | Required. Boolean. |
{
"input": {
"uid": "1.02.003"
},
"output": {
"leadingZeroComponents": [
1,
2
],
"withinLengthLimit": true
}
}Limitations and assumptions
- A successful call can report invalid encoding conditions; it does not verify UID root allocation, global uniqueness, actual DICOM assignment, or padding bytes.
- 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-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.