DICOM Attribute
Study ID (0020,0010)
- Keyword
StudyID- VR
SH- VM
1
Definition
User or equipment generated Study identifier.
From NEMA PS3.3 §C.7.2.1.
Attribute Metadata
This attribute is part of the current DICOM Standard. Its value representation is SH with multiplicity 1.
Used in 2 Modules
Value Representation
This attribute uses the SH
Value Representation. Multiplicity 1 governs how many values may be encoded.
Integration Notes
Real-world integration guidance for engineers implementing this attribute in Mirth Connect, FHIR gateways, HL7 v2 bridges, and cloud DICOM services. Authoritative source data where available; reference examples and operational notes where they add value.
FHIR Mapping
-
ImagingStudy.identifierStudyInstanceUID (0020,000D) | study ID (0020,0010)
Source: HL7 FHIR R5 ImagingStudy (CC0).
HL7 v2 Equivalent
-
OBR-19Placer Field 2 (Study ID) site-dependentORMORUOlder convention. DICOM StudyID is SH 16 chars; OBR-19 (or sometimes OBR-20) carries it in radiology workflows.
Source: common convention
Verify against IHE Radiology TF Vol 2 and your facility's interface specification before production use.
Cloud DICOM Support
- AWS HealthImaging Queryable
- Azure DICOM Queryable
- Google Cloud Healthcare Queryable
Study ID is a Study-level QIDO-RS matching key on all three platforms.
Per-vendor source URLs and verification date in src/content/dicom/cloud-support.json#_meta.
Status taxonomy: required (mandated on Store), queryable (QIDO-RS matching key), preserved (stored as-is), promoted (AWS top-level metadata), unsupported (stripped/rejected).
Real-World Sample Values
-
1CT1CT_small.dcm -
4MR1MR_small.dcm -
study1rtplan.dcm
Extracted from pydicom test fixtures (MIT, de-identified).
Mirth Connect Example
Generate Study ID when missing (legacy modality workaround) — DICOM Study ID (0020,0010) is SH 16 chars and not always populated by older moda
DICOM Study ID (0020,0010) is SH 16 chars and not always populated by older modalities. Generate from Accession Number or Study UID hash for downstream consistency.
// (0020,0010) Study ID — derive from Accession Number when source omitted it
var studyId = String(msg.dataset.attr.(@tag == '00200010').value).trim();
if (!studyId) {
var accNum = channelMap.get('accession');
if (accNum) {
studyId = accNum.substring(0, 16); // SH 16 char cap
} else {
var studyUid = String(msg.dataset.attr.(@tag == '0020000D').value);
studyId = String(studyUid.substring(studyUid.length - 16)); // last 16 chars
}
channelMap.put('study_id_generated', 'true');
} Reference only — validate before production. Snippets are starting points, not turnkey solutions. Always test against your channel's specific message structure and your facility's interface specification. See Mirth Connect User Guide + NEMA PS3.6 + your vendor conformance statement for authoritative specification.
Common Operational Errors
Operational error patterns for the most-queried tags will be added as coverage expands.
DICOM Integration Services
Saga IT builds production DICOM integrations across Mirth Connect, FHIR gateways, and cloud imaging platforms. If you're working with StudyID or the broader (0020,0010) context:
- Medical Imaging & DICOM Integration — end-to-end PACS, VNA, and cloud imaging deployments
- Mirth Connect Services — production-grade Mirth channel development
- Healthcare AI Integration — DICOM pipelines for AI/ML inference