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 can have multiple series of different modality values.

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.

Allows identification of the imaging study as it is known by various participating systems and in a way that remains consistent across servers. ImagingStudy.identifier SHALL include exactly one Study Instance UID value if one or more series element values are present (see DICOM PS 3.3 C.7.2 .)

Note: This is a business identifier, not a resource identifier (see discussion ). It is best practice for the identifier to only appear on a single resource instance, however business practices may 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, or an accession number may MAY be used to relate a Task, an ImagingStudy and a DiagnosticReport. See discussion under Imaging Study Implementation Notes for encoding of DICOM Study Instance UID.

The current state of the imaging study. This is distinct from the status of any service request or task associated with the imaging study.

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

All the distinct values of series.modality. This may MAY be either an acquisition or a non-acquisition modality.

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 the imaging data represented by this ImagingStudy is made. imaging study was acquired.

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. If the ImagingStudy is associated with an Accession Number, this field should SHOULD include a reference to that value in the form: identifier.value = (Accession Number Value) identifier.type = ACSN. A reference value pointing to a ServiceRequest resource is allowed but is not required.

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

A larger event of The performed procedure(s) during which the data associated with this particular ImagingStudy is a component or step. For example, an ImagingStudy as part of a procedure. imaging study was created.

To link an ImagingStudy imaging study to an Encounter use encounter .

The 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 metadata without retrieving the actual instances; or IHE Invoke Image Display (IID), which provides standard invocation of an imaging web viewer. instances. See Imaging Study Implementation Notes on Endpoints .

The principal physical location where the imaging study 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).

Describes why the imaging study occurred in coded or textual form or indicates another resource whose existence justifies this imaging study.

This MAY correspond to the indications or reasons encoded in an associated service request.

Comments made about the imaging study by the performer, subject or other participants.

Description or classification of the imaging study.

Number of known Series in the Study. This value might be present even if the ImagingStudy.series element is empty or only partially populated.

Number of known SOP Instances in Study. This value might be present even if the ImagingStudy.series.instance elements are empty or only partially populated.

The set of Series belonging to the study. Each Series contains a set of SOP Instances, which could be images, waveforms, or other content.

The DICOM Series Instance UID of 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 be either an acquisition and modality (e.g., CT, MR) or a non-acquisition modalities. modality (e.g., segmentation, presentation state).

Description or classification of the series.

Number of SOP Instances in the Study. Series. The value given MAY be larger than the number of instance elements this resource series 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 for the study. See implementation notes for information about using DICOM endpoints .

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

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. imaging study..

Allows disambiguation of the types of involvement of different performers.

Indicates who or what performed the series. imaging study.

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.

Typically a well-known DICOM SOP Class UID but MAY be the UID of a private SOP Class

The number of the instance in assigned by the creator of the series. MAY or MAY NOT correspond to intended display order.

The description title of the instance.

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