STU 3 Ballot

This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

10.7.6 Resource ImagingStudy - Detailed Descriptions

Detailed Descriptions for the elements in the ImagingStudy resource.

ImagingStudy
Definition

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.

Control1..1
ImagingStudy.uid
Definition

Formal identifier for the study.

Control1..1
Typeoid
Alternate NamesStudyInstanceUID
Summarytrue
ImagingStudy.accession
Definition

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 .

Control0..1
TypeIdentifier
Alternate NamesAccessionNumber
Summarytrue
ImagingStudy.identifier
Definition

Other identifiers for the study.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Alternate NamesStudyID
Summarytrue
ImagingStudy.availability
Definition

Availability of study (online, offline or nearline).

Control0..1
BindingInstanceAvailability: Availability of the resource (Required)
Typecode
Alternate NamesInstanceAvailability
Summarytrue
ImagingStudy.modalityList
Definition

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).

Control0..*
BindingAcquisition Modality Codes: Type of acquired data in the instance (Extensible)
TypeCoding
Alternate NamesModalitiesInStudy
Summarytrue
ImagingStudy.patient
Definition

The patient imaged in the study.

Control1..1
TypeReference(Patient)
Summarytrue
ImagingStudy.context
Definition

The encounter at which the request is initiated.

Control0..1
TypeReference(Encounter | EpisodeOfCare)
Summarytrue
ImagingStudy.started
Definition

Date and Time the study started.

Control0..1
TypedateTime
Alternate NamesStudyDate; StudyTime
Summarytrue
ImagingStudy.basedOn
Definition

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

Control0..*
TypeReference(ReferralRequest | CarePlan | DiagnosticRequest | ProcedureRequest)
Requirements

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

Summarytrue
ImagingStudy.referrer
Definition

The requesting/referring physician.

Control0..1
TypeReference(Practitioner)
Alternate NamesReferringPhysiciansName
Summarytrue
ImagingStudy.interpreter
Definition

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

Control0..1
TypeReference(Practitioner)
Alternate NamesName of Physician(s) Reading Study
Summarytrue
ImagingStudy.baseLocation
Definition

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

Control0..*
Requirements

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.

Summarytrue
To Dolikely change to Endpoint Resource reference.
ImagingStudy.baseLocation.type
Definition

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

Control1..1
BindingdWebType: The type of the service endpoint (Extensible)
TypeCoding
Summarytrue
ImagingStudy.baseLocation.url
Definition

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.

Control1..1
Typeuri
Summarytrue
Comments

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.

ImagingStudy.numberOfSeries
Definition

Number of Series in Study.

Control1..1
TypeunsignedInt
Alternate NamesNumberOfStudyRelatedSeries
Summarytrue
ImagingStudy.numberOfInstances
Definition

Number of SOP Instances in Study.

Control1..1
TypeunsignedInt
Alternate NamesNumberOfStudyRelatedInstances
Summarytrue
ImagingStudy.procedure
Definition

Type of procedure performed.

Control0..*
TypeReference(Procedure)
Alternate NamesProcedureCodeSequence
Summarytrue
Comments

For the Procedure.code, LOINC radiology orderables would be a good value set to use.

ImagingStudy.reason
Definition

Description of clinical codition indicating why the ImagingStudy was requested.

Control0..1
BindingImagingReason: The reason for the study
TypeCodeableConcept
Summarytrue
ImagingStudy.description
Definition

Institution-generated description or classification of the Study performed.

Control0..1
Typestring
Alternate NamesStudyDescription
Summarytrue
ImagingStudy.series
Definition

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

Control0..*
Summarytrue
ImagingStudy.series.uid
Definition

Formal identifier for this series.

Control1..1
Typeoid
Alternate NamesSeriesInstanceUID
Summarytrue
ImagingStudy.series.number
Definition

The Numeric identifier of this series in the study.

Control0..1
TypeunsignedInt
Alternate NamesSeriesNumber
Summarytrue
ImagingStudy.series.modality
Definition

The modality of this series sequence.

Control1..1
BindingAcquisition Modality Codes: Type of acquired data in the instance (Extensible)
TypeCoding
Alternate NamesModality
Summarytrue
ImagingStudy.series.description
Definition

A description of the series.

Control0..1
Typestring
Alternate NamesSeriesDescription
Summarytrue
ImagingStudy.series.numberOfInstances
Definition

Number of SOP Instances in Series.

Control1..1
TypeunsignedInt
Alternate NamesNumberOfSeriesRelatedInstances
Summarytrue
ImagingStudy.series.availability
Definition

Availability of series (online, offline or nearline).

Control0..1
BindingInstanceAvailability: Availability of the resource (Required)
Typecode
Alternate NamesInstanceAvailability
Summarytrue
ImagingStudy.series.baseLocation
Definition

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

Control0..*
Requirements

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.

Summarytrue
To Dolikely change to Endpoint Resource reference.
ImagingStudy.series.baseLocation.type
Definition

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

Control1..1
BindingdWebType: The type of the service endpoint (Extensible)
TypeCoding
Summarytrue
ImagingStudy.series.baseLocation.url
Definition

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.

Control1..1
Typeuri
Summarytrue
Comments

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.

ImagingStudy.series.bodySite
Definition

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

Control0..1
BindingSNOMED CT Body Structures: Codes describing anatomical locations. May include laterality. (Example)
TypeCoding
Alternate NamesBodyPartExamined
Summarytrue
ImagingStudy.series.laterality
Definition

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

Control0..1
BindingLaterality: Codes describing body site laterality (left, right, etc.). (Example)
TypeCoding
Summarytrue
ImagingStudy.series.started
Definition

The date and time the series was started.

Control0..1
TypedateTime
Summarytrue
ImagingStudy.series.instance
Definition

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

Control0..*
ImagingStudy.series.instance.uid
Definition

Formal identifier for this image or other content.

Control1..1
Typeoid
Alternate NamesSOPInstanceUID
ImagingStudy.series.instance.number
Definition

The number of instance in the series.

Control0..1
TypeunsignedInt
Alternate NamesInstanceNumber
ImagingStudy.series.instance.sopClass
Definition

DICOM instance type.

Control1..1
Typeoid
Alternate NamesSOPClassUID
ImagingStudy.series.instance.title
Definition

The description of the instance.

Control0..1
Typestring
Comments

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