Description
Compare explicit study/series parent references and construct a scoped instance key from an ASCII numeric UID subset, without resolving DICOM objects.
An image grid has array indices as well as physical spacing, timing, and signal conventions. A calculation on supplied metadata describes one part of that grid or signal; it does not inspect an image, validate a complete file, or interpret anatomy.
Compare explicit study/series parent references and construct a scoped instance key from an ASCII numeric UID subset, without resolving DICOM objects.
When to use this tool
Use it for dicom study series sop reference pair when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter studyUid, seriesUid, sopUid, parentStudyUid, parentSeriesUid. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read hierarchyMatches, instanceKey. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Validate each supplied UID against the implemented numeric dotted subset, rejecting empty values, more than 64 characters, and leading zeros in multi-digit components. Compare study and series parent identifiers and serialize the study/series/instance tuple as instanceKey.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| studyUid | Study Uid | Required. Text; maximum UTF-16 length 8192. |
| seriesUid | Series Uid | Required. Text; maximum UTF-16 length 8192. |
| sopUid | Sop Uid | Required. Text; maximum UTF-16 length 8192. |
| parentStudyUid | Parent Study Uid | Required. Text; maximum UTF-16 length 8192. |
| parentSeriesUid | Parent Series Uid | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| hierarchyMatches | Hierarchy Matches | Required. Boolean. |
| instanceKey | Instance Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"studyUid": "1.2.3",
"seriesUid": "1.2.4",
"sopUid": "1.2.5",
"parentStudyUid": "1.2.3",
"parentSeriesUid": "1.2.4"
},
"output": {
"hierarchyMatches": true,
"instanceKey": "[\"1.2.3\",\"1.2.4\",\"1.2.5\"]"
}
}Limitations and assumptions
- Lexical validity and matching supplied parents do not establish UID ownership, global uniqueness, object existence, or referential integrity in a DICOM archive.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For dicom study series sop reference pair, check the source records and the supplied rule before comparing the result with another method. Use a full image reader and geometry or signal analysis when the task requires interpreting image data.
References
Similar or alternative tools
- DICOM Frame Increment Time Index Term
Constant Frame Time coordinate for one zero-based frame index; not a variable Frame Time Vector or acquisition datetime parser.
- DICOM Image Orientation Dot Orthogonality Gap
Check supplied DICOM row/column direction cosines for unit lengths and orthogonality using an explicit tolerance.