This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
(v4.0.1:
R4
-
Mixed
Normative
and
STU
3).
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
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
R4
R3
R2
Imaging
Integration
Work
Group
|
Maturity Level : 3 | Trial Use | Security Category : Patient | Compartments : Patient |
Detailed Descriptions for the elements in the ImagingStudy resource.
| ImagingStudy | |
| Element Id | 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. |
|
|
|
| Type |
|
|
|
|
|
|
|
| Definition |
|
| Note |
This
is
a
business
|
|
|
0..* |
| Type | Identifier |
| Requirements |
If
one
or
more
series
elements
are
present
in
the
ImagingStudy,
then
there
shall
be
one
DICOM
Study
UID
identifier
(see
DICOM
PS
3.3
C.7.2
|
| Alternate Names |
|
| Summary | true |
| Comments | See discussion under Imaging Study Implementation Notes for encoding of DICOM Study Instance UID. Accession Number should use ACSN Identifier type. |
|
|
|
| Element Id | ImagingStudy.status |
| Definition |
|
|
|
|
| Terminology Binding |
|
| Type | code |
| Is Modifier |
|
| Summary | true |
| Comments | 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. |
|
|
|
| Element Id | ImagingStudy.modality |
| Definition |
A
list
of
all
the
|
|
|
0..* |
| Terminology Binding |
(
Extensible
)
|
| Type | Coding |
| Alternate Names | ModalitiesInStudy |
| Summary | true |
|
|
|
| Element Id | ImagingStudy.subject |
| Definition |
The
|
|
|
1..1 |
| Type | Reference ( Patient | Device | Group ) |
| Summary | true |
| Comments | QA phantoms can be recorded with a Device; multiple subjects (such as mice) can be recorded with a Group. |
|
|
|
| Element Id | ImagingStudy.encounter |
| Definition |
The
|
|
|
0..1 |
| Type |
Reference
(
Encounter
|
| Summary | true |
| Comments | 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). |
| ImagingStudy.started | |
| Element Id | ImagingStudy.started |
| Definition |
Date and time the study started. |
|
|
0..1 |
| Type | dateTime |
| Alternate Names | StudyDate; StudyTime |
| Summary | true |
| ImagingStudy.basedOn | |
| Element Id | ImagingStudy.basedOn |
| Definition |
A list of the diagnostic requests that resulted in this imaging study being performed. |
|
|
0..* |
| Type |
Reference
(
|
| Requirements |
To support grouped procedures (one imaging study supporting multiple ordered procedures, e.g. chest/abdomen/pelvis CT). |
| Summary | true |
| ImagingStudy.referrer | |
| Element Id | ImagingStudy.referrer |
| Definition |
The requesting/referring physician. |
|
|
0..1 |
| Type | Reference ( Practitioner | PractitionerRole ) |
| Alternate Names | ReferringPhysiciansName |
| Summary | true |
| ImagingStudy.interpreter | |
| Element Id | ImagingStudy.interpreter |
| Definition |
Who read the study and interpreted the images or other content. |
|
|
0..* |
| Type | Reference ( Practitioner | PractitionerRole ) |
| Alternate Names | Name of Physician(s) Reading Study |
| Summary | true |
| ImagingStudy.endpoint | |
| Element Id | ImagingStudy.endpoint |
| Definition |
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
|
|
|
0..* |
| Type | Reference ( Endpoint ) |
| 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. |
| Summary | true |
| Comments |
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. |
| ImagingStudy.numberOfSeries | |
| Element Id | ImagingStudy.numberOfSeries |
| Definition |
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. |
|
|
0..1 |
| Type | unsignedInt |
| Alternate Names | NumberOfStudyRelatedSeries |
| Summary | true |
| ImagingStudy.numberOfInstances | |
| Element Id | ImagingStudy.numberOfInstances |
| Definition |
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. |
|
|
0..1 |
| Type | unsignedInt |
| Alternate Names | NumberOfStudyRelatedInstances |
| Summary | true |
| ImagingStudy.procedureReference | |
| Element Id | ImagingStudy.procedureReference |
| Definition |
|
|
|
|
| Type | Reference ( Procedure ) |
| Summary | true |
| ImagingStudy.procedureCode | |
| Element Id | ImagingStudy.procedureCode |
| Definition |
The code for the performed procedure type. |
|
|
0..* |
| Terminology Binding |
:
|
| Type | CodeableConcept |
| Alternate Names | ProcedureCodeSequence |
| Summary | true |
|
|
|
| Element Id | ImagingStudy.location |
| Definition | The principal physical location where the ImagingStudy was performed. |
| Cardinality | 0..1 |
| Type | Reference ( Location ) |
| Requirements | 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). |
| Summary | true |
| ImagingStudy.reasonCode | |
| Element Id | ImagingStudy.reasonCode |
| Definition |
Description of clinical condition indicating why the ImagingStudy was requested. |
|
|
|
| Terminology Binding | Procedure Reason Codes ( Example ) |
| Type | CodeableConcept |
| Summary | true |
| ImagingStudy.reasonReference | |
| Element Id | ImagingStudy.reasonReference |
| Definition | Indicates another resource whose existence justifies this Study. |
| Cardinality | 0..* |
| Type | Reference ( Condition | Observation | Media | DiagnosticReport | DocumentReference ) |
| Summary | true |
| ImagingStudy.note | |
| Element Id | ImagingStudy.note |
| Definition | 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. |
| Cardinality | 0..* |
| Type | Annotation |
| Summary | true |
| ImagingStudy.description | |
| Element Id | ImagingStudy.description |
| Definition |
The Imaging Manager description of the study. Institution-generated description or classification of the Study (component) performed. |
|
|
0..1 |
| Type | string |
| Alternate Names | StudyDescription |
| Summary | true |
| ImagingStudy.series | |
| Element Id | ImagingStudy.series |
| Definition |
Each study has one or more series of images or other content. |
|
|
0..* |
| Summary | true |
| ImagingStudy.series.uid | |
| Element Id | ImagingStudy.series.uid |
| Definition |
|
|
|
1..1 |
| Type |
|
| Requirements | DICOM Series Instance UID. |
| Alternate Names | SeriesInstanceUID |
| Summary | true |
| Comments |
See
DICOM
PS3.3
C.7.3
|
| ImagingStudy.series.number | |
| Element Id | ImagingStudy.series.number |
| Definition |
The numeric identifier of this series in the study. |
|
|
0..1 |
| Type | unsignedInt |
| Alternate Names | SeriesNumber |
| Summary | true |
| ImagingStudy.series.modality | |
| Element Id | ImagingStudy.series.modality |
| Definition |
The modality of this series sequence. |
|
|
1..1 |
| Terminology Binding |
(
Extensible
)
|
| Type | Coding |
| Alternate Names | Modality |
| Summary | true |
| ImagingStudy.series.description | |
| Element Id | ImagingStudy.series.description |
| Definition |
A description of the series. |
|
|
0..1 |
| Type | string |
| Alternate Names | SeriesDescription |
| Summary | true |
| ImagingStudy.series.numberOfInstances | |
| Element Id | ImagingStudy.series.numberOfInstances |
| Definition |
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. |
|
|
0..1 |
| Type | unsignedInt |
| Alternate Names | NumberOfSeriesRelatedInstances |
| Summary | true |
|
|
|
|
|
|
| Definition |
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
|
|
|
0..* |
| Type | Reference ( Endpoint ) |
| 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. |
| Summary | true |
| Comments |
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. |
| ImagingStudy.series.bodySite | |
| Element Id | ImagingStudy.series.bodySite |
| Definition |
The anatomic structures examined. See DICOM Part 16 Annex L (http://dicom.nema.org/medical/dicom/current/output/chtml/part16/chapter_L.html) 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. |
|
|
0..1 |
| Terminology Binding | SNOMED CT Body Structures ( Example ) |
| Type | Coding |
| Alternate Names | BodyPartExamined |
| Summary | true |
| ImagingStudy.series.laterality | |
| Element Id | ImagingStudy.series.laterality |
| Definition |
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. |
|
|
0..1 |
| Terminology Binding | Laterality ( Example ) |
| Type | Coding |
| Summary | true |
| ImagingStudy.series.specimen | |
| Element Id | ImagingStudy.series.specimen |
| Definition | The specimen imaged, e.g., for whole slide imaging of a biopsy. |
| Cardinality | 0..* |
| Type | Reference ( Specimen ) |
| Summary | true |
| ImagingStudy.series.started | |
| Element Id | ImagingStudy.series.started |
| Definition |
The date and time the series was started. |
|
|
0..1 |
| Type | dateTime |
| Summary | true |
| ImagingStudy.series.performer | |
| Element Id | ImagingStudy.series.performer |
| Definition |
|
| Cardinality | 0..* |
| Requirements |
The
performer
is
recorded
at
the
series
level,
since
each
series
in
a
study
may
be
performed
by
a
different
|
| Alternate Names | PerformingPhysicianName; OperatorName |
| Summary |
|
| Comments |
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. |
| ImagingStudy.series.performer.function | |
| Element Id | ImagingStudy.series.performer.function |
| Definition | Distinguishes the type of involvement of the performer in the series. |
| Cardinality | 0..1 |
| Terminology Binding |
ImagingStudy
series
performer
function
(
|
| Type |
|
| Requirements | Allows disambiguation of the types of involvement of different performers. |
| Summary | true |
| ImagingStudy.series.performer.actor | |
| Element Id | ImagingStudy.series.performer.actor |
| Definition | Indicates who or what performed the series. |
| Cardinality | 1..1 |
| Type | Reference ( Practitioner | PractitionerRole | Organization | CareTeam | Patient | Device | RelatedPerson ) |
| Summary | true |
| ImagingStudy.series.instance | |
| Element Id | ImagingStudy.series.instance |
| Definition |
A single SOP instance within the series, e.g. an image, or presentation state. |
|
|
0..* |
| ImagingStudy.series.instance.uid | |
| Element Id | ImagingStudy.series.instance.uid |
| Definition |
|
|
|
1..1 |
| Type |
|
| Requirements | DICOM SOP Instance UID. |
| Alternate Names | SOPInstanceUID |
| Comments |
See
DICOM
PS3.3
C.12.1
|
|
|
|
| Element Id | ImagingStudy.series.instance.sopClass |
| Definition |
|
|
|
|
| Terminology Binding |
sopClass
:
|
| Type |
|
| Alternate Names |
|
|
|
|
| Element Id | ImagingStudy.series.instance.number |
| Definition |
|
|
|
|
| Type |
|
| Alternate Names |
|
| ImagingStudy.series.instance.title | |
| Element Id | ImagingStudy.series.instance.title |
| Definition |
The description of the instance. |
|
|
0..1 |
| Type | string |
| Comments |
Particularly for post-acquisition analytic objects, such as SR, presentation states, value mapping, etc. |