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.

Formal identifier for the study.

Accession Number is an identifier related to some aspect of imaging workflow and data management. Usage may vary across different institutions. See for instance IHE Radiology Technical Framework Volume 1 Appendix A .

Other identifiers for the study.

Availability of study (online, offline or nearline).

A list of all the Series.ImageModality values that are actual acquisition modalities, i.e. those in the DICOM Context Group 29 (value set OID 1.2.840.10008.6.1.19).

The patient imaged in the study.

The encounter at which the request is initiated.

Date and Time the study started.

A list of the diagnostic requests that resulted in this imaging study being performed.

To support grouped procedures (one imaging study supporting multiple ordered procedures, e.g. chest/abdomen/pelvis CT).

The requesting/referring physician.

Who read the study and interpreted the images or other content.

Methods of accessing (e.g., retrieving, viewing) the study.

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.

The service type for accessing (e.g., retrieving, viewing) the DICOM instances.

The service URL for accessing the study. The interpretation of the URL depends on the type of the service specified in ImagingManifest.study.baseLocation.type.

This URL is to a service endpoint for the particular service indicated by ImagingManifest.study.baseLocation.type. Depending on the type of service, it is may be used to construct a URL to view, retrieve, or otherwise access the study or the study’s series or instances. For example, this element may be a DICOMweb WADO-RS endpoint.

Number of Series in Study.

Number of SOP Instances in Study.

Type of procedure performed.

Description of clinical codition indicating why the ImagingStudy was requested.

Institution-generated description or classification of the Study performed.

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

Formal identifier for this series.

The Numeric identifier of this series in the study.

The modality of this series sequence.

A description of the series.

Number of SOP Instances in Series.

Availability of series (online, offline or nearline).

Methods of accessing (e.g. retrieving) the series.

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.

The service type for accessing (e.g., retrieving) the DICOM instances.

The service URL for accessing the study. The interpretation of the URL depends on the type of the service specified in ImagingManifest.study.series.baseLocation.type.

This URL is to a service endpoint for the particular service indicated by ImagingManifest.study.series.baseLocation.type. Depending on the type of service, it is may be used to construct a URL to retrieve, or otherwise access, the series or the series’ instances. For example, this element may be a DICOMweb WADO-RS endpoint.

Body part examined. See DICOM Part 16 Annex L for the mapping from DICOM to Snomed CT.

Laterality if body site is paired anatomic structure and laterality is not pre-coordinated in body site code.

The date and time the series was started.

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

Formal identifier for this image or other content.

The number of instance in the series.

DICOM instance type.

The description of the instance.

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