Skip to content

Main content

DICOM SOP Instance Reference Token

Record supplied DICOM study, series, and instance UID strings without resolving images or validating UID assignment.

Loading tool…

Description

Record supplied DICOM study, series, and instance UID strings.

Medical-image metadata separates patient position, laterality, pixel spacing, slice spacing, padding and frame timing. Row and column spacing order matters, and slice spacing is distinct from slice thickness. A rectangular voxel or constant-frame model uses declared geometry; it does not inspect images, confirm a patient or establish a clinical finding.

Record supplied DICOM study, series, and instance UID strings.

When to use this tool

Use DICOM SOP Instance Reference Token when you already have studyUid, seriesUid, instanceUid and need to record supplied DICOM study, series, and instance UID strings.

How to use the tool and how it works

  1. Enter studyUid, seriesUid, instanceUid. 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 token. Use the output convention below.

Enter studyUid, seriesUid, instanceUid using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
studyUidStudy UidRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
seriesUidSeries UidRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
instanceUidInstance UidRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "studyUid": "1.2.3",
    "seriesUid": "1.2.3.4",
    "instanceUid": "1.2.3.4.5"
  },
  "output": {
    "token": "[\"1.2.3\",\"1.2.3.4\",\"1.2.3.4.5\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without resolving images or validating UID assignment. Sources and asserted relationships are not independently authenticated.
  • 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

Inspect the original DICOM attributes and complete image geometry when validating an image record. Use the relevant attribute and value-representation checks for format compliance, and actual per-frame timing when constant spacing or frame time is inadequate.

References

  1. Calculation and input contract: radiology/dicom-sop-instance-reference-token — tool.io

Similar or alternative tools