DICOM Attribute

Instance Creation Date (0008,0012)

Keyword
InstanceCreationDate
VR
DA
VM
1

Definition

Date the SOP Instance was created. This is the date that the SOP Instance UID was assigned, and does not change during subsequent coercion of the Instance.

From NEMA PS3.3 §C.12.1.

Attribute Metadata

This attribute is part of the current DICOM Standard. Its value representation is DA with multiplicity 1.

Used in 3 Modules

This attribute uses the DA 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

No direct FHIR ImagingStudy mapping published for this attribute. Some tags map indirectly via the Patient, Endpoint, or ImagingSelection resources — Phase 2b will expand coverage to those.

HL7 v2 Equivalent

No standard HL7 v2 equivalent published for this attribute. Imaging-only attributes (Image Pixel data, technical acquisition parameters, modality-specific values) typically have no HL7 v2 carrier.

Cloud DICOM Support

AWS HealthImaging, Azure DICOM, and GCP Healthcare DICOM coverage rolls out by attribute. The QIDO-RS matching keys + Patient/Study/Series core (~50 attributes) are documented; lower-traffic attributes will be added as Saga teams encounter them in production.

Real-World Sample Values

  • 20040119 CT_small.dcm
  • 20040826 MR_small.dcm
  • 20030903 rtplan.dcm

Extracted from pydicom test fixtures (MIT, de-identified).

Mirth Connect Example

JavaScript transformer snippets for the most-queried tags will be added as coverage expands.

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 InstanceCreationDate or the broader (0008,0012) context: