Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study MAY have multiple series of different modalities.

Business identifiers assigned to this imaging study by the performer and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server. Typically this will include the DICOM Study Instance UID and Accession Number.

ImagingStudy.identifier SHALL contain exactly one Study Instance UID value if one or more series element values are present (see DICOM PS 3.3 C.7.2 .)

It is best practice for the identifier to only appear on a single resource instance, however business practices MAY occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. See discussion under Imaging Study Implementation Notes for encoding of DICOM Study Instance UID and Accession Number.

The current state of the ImagingStudy resource. This is not the status of any ServiceRequest or Task resources associated with the ImagingStudy.

Unknown does not represent "other" - one of the defined statuses SHALL apply. Unknown is used when the authoring system is not sure what the current status is.

A list of all the distinct values of series.modality. This MAY include both acquisition and non-acquisition modalities.

The subject, typically a patient, of the imaging study.

QA phantoms can be recorded with a Device; multiple subjects (such as mice) can be recorded with a Group.

The healthcare event (e.g. a patient and healthcare provider interaction) during which this ImagingStudy is made.

This will typically be the encounter the event occurred within, but some events MAY be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission test).

Date and time the study started.

A plan or order that is fulfilled in whole or in part by this imaging study.

Allows tracing of authorization for the imaging study and tracking whether proposals/recommendations were acted upon.

One imaging study MAY support multiple ordered procedures, e.g. chest/abdomen/pelvis CT orders being fulfilled by a single imaging study.

A larger event of which this particular ImagingStudy is a component or step. For example, an ImagingStudy as part of a procedure.

To link an ImagingStudy to an Encounter use encounter.

The requesting/referring physician.

The network service providing access (e.g., query, view, or retrieval) for the study. See implementation notes for information about using DICOM endpoints. A study-level endpoint applies to each series in the study, unless overridden by a series-level endpoint with the same Endpoint.connectionType.

Access methods for viewing (e.g., IHE's IID profile) or retrieving (e.g., DICOM's WADO-URI and WADO-RS) the study or the study's series or instances. The study-level baseLocation applies to each series in the study, unless overridden in series by a series-level baseLocation of the same type.

Typical endpoint types include DICOM WADO-RS, which is used to retrieve DICOM instances in native or rendered (e.g., JPG, PNG), formats using a RESTful API; DICOM WADO-URI, which can similarly retrieve native or rendered instances, except using an HTTP query-based approach; DICOM QIDO-RS, which allows RESTful query for DICOM information without retrieving the actual instances; or IHE Invoke Image Display (IID), which provides standard invocation of an imaging web viewer. See Imaging Study Implementation Notes on Endpoints.

This field corresponds to the DICOM Procedure Code Sequence (0008,1032). This is different from the FHIR Procedure resource that MAY include the ImagingStudy.

The principal physical location where the ImagingStudy was performed.

Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).

Description of clinical condition indicating why the ImagingStudy was requested, and/or Indicates another resource whose existence justifies this Study.

Per the recommended DICOM mapping, this element is derived from the Study Description attribute (0008,1030). Observations or findings about the imaging study SHOULD be recorded in another resource, e.g. Observation, and not in this element.

The Imaging Manager description of the study. Institution-generated description or classification of the Study (component) performed.

Number of Series in the Study. This value given MAY be larger than the number of series elements this Resource contains due to resource availability, security, or other factors. This element SHOULD be present if any series elements are present.

Number of SOP Instances in Study. This value given MAY be larger than the number of instance elements this resource contains due to resource availability, security, or other factors. This element SHOULD be present if any instance elements are present.

Each study has one or more series of images or other content.

The DICOM Series Instance UID for the series.

DICOM Series Instance UID.

See DICOM PS3.3 C.7.3 .

The numeric identifier of this series in the study.

The distinct modality for this series. This MAY include both acquisition and non-acquisition modalities.

A description of the series.

Number of SOP Instances in the Study. The value given MAY be larger than the number of instance elements this resource contains due to resource availability, security, or other factors. This element SHOULD be present if any instance elements are present.

The network service providing access (e.g., query, view, or retrieval) for this series. See implementation notes for information about using DICOM endpoints. A series-level endpoint, if present, has precedence over a study-level endpoint with the same Endpoint.connectionType.

Access methods for retrieving (e.g., DICOM's WADO-URI and WADO-RS) the series or the series' instances. A baseLocation specified at the series level has precedence over a baseLocation of the same type specified at the study level.

Typical endpoint types include DICOM WADO-RS, which is used to retrieve DICOM instances in native or rendered (e.g., JPG, PNG) formats using a RESTful API; DICOM WADO-URI, which can similarly retrieve native or rendered instances, except using an HTTP query-based approach; and DICOM QIDO-RS, which allows RESTful query for DICOM information without retrieving the actual instances. See Imaging Study Implementation Notes on Endpoints.

The anatomic structures examined. See DICOM Part 16 Annex L for DICOM to SNOMED-CT mappings. The bodySite MAY indicate the laterality of body part imaged; if so, it SHALL be consistent with any content of ImagingStudy.series.laterality.

The laterality of the (possibly paired) anatomic structures examined. E.g., the left knee, both lungs, or unpaired abdomen. If present, SHALL be consistent with any laterality information indicated in ImagingStudy.series.bodySite.

The specimen imaged, e.g., for whole slide imaging of a biopsy.

The date and time the series was started.

Indicates who or what performed the series and how they were involved.

The performer is recorded at the series level, since each series in a study MAY be performed by a different performer, at different times, and using different devices. A series MAY be performed by multiple performers.

If the person who performed the series is not known, their Organization MAY be recorded. A patient, or related person, MAY be the performer, e.g. for patient-captured images.

Distinguishes the type of involvement of the performer in the series.

Allows disambiguation of the types of involvement of different performers.

Indicates who or what performed the series.

A single SOP instance within the series, e.g. an image, or presentation state.

The DICOM SOP Instance UID for this image or other DICOM content.

DICOM SOP Instance UID.

See DICOM PS3.3 C.12.1 .

DICOM instance type.

The number of instance in the series.

The description of the instance.

Particularly for post-acquisition analytic objects, such as SR, presentation states, value mapping, etc.