This page is part of the FHIR Specification (v1.4.0:
STU
3 Ballot 3). The current version which supercedes this version is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
. For a full list of available versions, see the
Directory of published versions
|
|
Compartments
|
A manifest of a set of DICOM Service-Object Pair Instances (SOP Instances). The referenced SOP Instances (images or other content) are for a single patient, and may be from one or more studies. The referenced SOP Instances have been selected for a purpose, such as quality assurance, conference, or consult. Reflecting that range of purposes, typical ImagingObjectSelection resources may include all SOP Instances in a study (perhaps for sharing through a Health Information Exchange); key images from multiple studies (for reference by a referring or treating physician); a multi-frame ultrasound instance ("cine" video clip) and a set of measurements taken from that instance (for inclusion in a teaching file); and so on.
This resource summarizes a set of images or other instances gathered for some specified purpose, and provides references to where the images are available using WADO-RS. This resource is used to make available information concerning images etc. that are intended to be exchanged into other clinical contexts such as diagnostic reports, Care Plans, etc.
This resource is referenced by diagnosticreport
Structure
| Name | Flags | Card. | Type |
|
|---|---|---|---|---|
|
Σ | DomainResource |
|
|
|
Σ | 1..1 | oid |
|
|
Σ | 1..1 | Reference ( Patient ) |
|
|
Σ |
|
|
|
|
Σ | 0..1 |
|
|
|
Σ |
|
|
KOStitle ( Required ) |
|
Σ | 0..1 |
|
|
|
Σ | 1..* | BackboneElement |
|
|
Σ | 1..1 | oid |
|
|
Σ | 0..1 | uri |
|
|
Σ | 0..1 | Reference ( ImagingStudy ) |
|
|
Σ | 1..* | BackboneElement |
|
|
Σ |
|
oid |
|
|
Σ | 0..1 | uri |
|
|
Σ | 1..* | BackboneElement |
|
|
Σ | 1..1 | oid |
|
|
Σ | 1..1 | oid |
|
|
Σ | 1..1 | uri |
|
|
Σ | 0..* | BackboneElement |
|
|
Σ | 1..* | unsignedInt |
|
|
Σ | 1..1 | uri |
|
Documentation for this format
|
||||
UML
Diagram
UML Diagram
XML
Template
XML Template
<ImagingObjectSelection xmlns="http://hl7.org/fhir"><!-- from Resource: id, meta, implicitRules, and language --> <!-- from DomainResource: text, contained, extension, and modifierExtension --> <uid value="[oid]"/><!-- 1..1 Instance UID --> <patient><!-- 1..1 Reference(Patient) Patient of the selected objects --></patient>
<</title> <<authoringTime value="[dateTime]"/><!-- 0..1 Time when the imaging object selection was created --> <author><!-- 0..1 Reference(Practitioner|Device|Organization|Patient| RelatedPerson) Author (human or machine) --></author><<title><!-- 1..1 CodeableConcept Reason for selection --></title> <description value="[string]"/><!-- 0..1 Description text --> <study> <!-- 1..* Study identity of the selected instances --> <uid value="[oid]"/><!-- 1..1 Study instance UID --> <url value="[uri]"/><!-- 0..1 Retrieve study URL --> <imagingStudy><!-- 0..1 Reference(ImagingStudy) Reference to ImagingStudy --></imagingStudy> <series> <!-- 1..* Series identity of the selected instances --><<uid value="[oid]"/><!-- 1..1 Series instance UID --> <url value="[uri]"/><!-- 0..1 Retrieve series URL --> <instance> <!-- 1..* The selected instance --> <sopClass value="[oid]"/><!-- 1..1 SOP class UID of instance --> <uid value="[oid]"/><!-- 1..1 Selected instance UID --> <url value="[uri]"/><!-- 1..1 Retrieve instance URL -->< < < </frames><frame> <!-- 0..* The frame set --> <number value="[unsignedInt]"/><!-- 1..* Frame reference number --> <url value="[uri]"/><!-- 1..1 Retrieve frame URL --> </frame> </instance> </series> </study> </ImagingObjectSelection>
JSON
Template
JSON Template
{
"resourceType" : "ImagingObjectSelection",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"uid" : "<oid>", // R! Instance UID
"patient" : { Reference(Patient) }, // R! Patient of the selected objects
"
"
"authoringTime" : "<dateTime>", // Time when the imaging object selection was created
"author" : { Reference(Practitioner|Device|Organization|Patient|
RelatedPerson) }, // Author (human or machine)
"
"title" : { CodeableConcept }, // R! Reason for selection
"description" : "<string>", // Description text
"study" : [{ // R! Study identity of the selected instances
"uid" : "<oid>", // R! Study instance UID
"url" : "<uri>", // Retrieve study URL
"imagingStudy" : { Reference(ImagingStudy) }, // Reference to ImagingStudy
"series" : [{ // R! Series identity of the selected instances
"
"uid" : "<oid>", // R! Series instance UID
"url" : "<uri>", // Retrieve series URL
"instance" : [{ // R! The selected instance
"sopClass" : "<oid>", // R! SOP class UID of instance
"uid" : "<oid>", // R! Selected instance UID
"url" : "<uri>", // R! Retrieve instance URL
"
"
"
"frame" : [{ // The frame set
"number" : ["<unsignedInt>"], // R! Frame reference number
"url" : "<uri>" // R! Retrieve frame URL
}]
}]
}]
}]
}
Structure
| Name | Flags | Card. | Type |
|
|---|---|---|---|---|
|
Σ | DomainResource |
|
|
|
Σ | 1..1 | oid |
|
|
Σ | 1..1 | Reference ( Patient ) |
|
|
Σ |
|
|
|
|
Σ | 0..1 |
|
|
|
Σ |
|
|
KOStitle ( Required ) |
|
Σ | 0..1 |
|
|
|
Σ | 1..* | BackboneElement |
|
|
Σ | 1..1 | oid |
|
|
Σ | 0..1 | uri |
|
|
Σ | 0..1 | Reference ( ImagingStudy ) |
|
|
Σ | 1..* | BackboneElement |
|
|
Σ |
|
oid |
|
|
Σ | 0..1 | uri |
|
|
Σ | 1..* | BackboneElement |
|
|
Σ | 1..1 | oid |
|
|
Σ | 1..1 | oid |
|
|
Σ | 1..1 | uri |
|
|
Σ | 0..* | BackboneElement |
|
|
Σ | 1..* | unsignedInt |
|
|
Σ | 1..1 | uri |
|
Documentation for this format
|
||||
XML
Template
XML Template
<ImagingObjectSelection xmlns="http://hl7.org/fhir"><!-- from Resource: id, meta, implicitRules, and language --> <!-- from DomainResource: text, contained, extension, and modifierExtension --> <uid value="[oid]"/><!-- 1..1 Instance UID --> <patient><!-- 1..1 Reference(Patient) Patient of the selected objects --></patient>
<</title> <<authoringTime value="[dateTime]"/><!-- 0..1 Time when the imaging object selection was created --> <author><!-- 0..1 Reference(Practitioner|Device|Organization|Patient| RelatedPerson) Author (human or machine) --></author><<title><!-- 1..1 CodeableConcept Reason for selection --></title> <description value="[string]"/><!-- 0..1 Description text --> <study> <!-- 1..* Study identity of the selected instances --> <uid value="[oid]"/><!-- 1..1 Study instance UID --> <url value="[uri]"/><!-- 0..1 Retrieve study URL --> <imagingStudy><!-- 0..1 Reference(ImagingStudy) Reference to ImagingStudy --></imagingStudy> <series> <!-- 1..* Series identity of the selected instances --><<uid value="[oid]"/><!-- 1..1 Series instance UID --> <url value="[uri]"/><!-- 0..1 Retrieve series URL --> <instance> <!-- 1..* The selected instance --> <sopClass value="[oid]"/><!-- 1..1 SOP class UID of instance --> <uid value="[oid]"/><!-- 1..1 Selected instance UID --> <url value="[uri]"/><!-- 1..1 Retrieve instance URL -->< < < </frames><frame> <!-- 0..* The frame set --> <number value="[unsignedInt]"/><!-- 1..* Frame reference number --> <url value="[uri]"/><!-- 1..1 Retrieve frame URL --> </frame> </instance> </series> </study> </ImagingObjectSelection>
JSON
Template
JSON Template
{
"resourceType" : "ImagingObjectSelection",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"uid" : "<oid>", // R! Instance UID
"patient" : { Reference(Patient) }, // R! Patient of the selected objects
"
"
"authoringTime" : "<dateTime>", // Time when the imaging object selection was created
"author" : { Reference(Practitioner|Device|Organization|Patient|
RelatedPerson) }, // Author (human or machine)
"
"title" : { CodeableConcept }, // R! Reason for selection
"description" : "<string>", // Description text
"study" : [{ // R! Study identity of the selected instances
"uid" : "<oid>", // R! Study instance UID
"url" : "<uri>", // Retrieve study URL
"imagingStudy" : { Reference(ImagingStudy) }, // Reference to ImagingStudy
"series" : [{ // R! Series identity of the selected instances
"
"uid" : "<oid>", // R! Series instance UID
"url" : "<uri>", // Retrieve series URL
"instance" : [{ // R! The selected instance
"sopClass" : "<oid>", // R! SOP class UID of instance
"uid" : "<oid>", // R! Selected instance UID
"url" : "<uri>", // R! Retrieve instance URL
"
"
"
"frame" : [{ // The frame set
"number" : ["<unsignedInt>"], // R! Frame reference number
"url" : "<uri>" // R! Retrieve frame URL
}]
}]
}]
}]
}
Alternate
definitions:
Alternate definitions:
Schema
/
Schematron
,
Resource
Profile
(
, Resource Profile (
XML
,
,
JSON
),
),
Questionnaire
| Path | Definition | Type | Reference |
|---|---|---|---|
|
|
|
Required | KOStitle |
Amy, a family physician, is accessing a cross-enterprise document registry that contains radiology objects (
IHE Radiology XDS-I
), to discover studies for her patient, Alex. Her EHR client makes a FHIR call for all
ImagingObjectSelection
objects available for Alex. In the response, she is able to get study identifiers for each study that has been published to the registry. There is enough information provided in the response to obtain a thumbnail via a WADO-RS call, or to launch a viewer using an
IHE Radiology - Invoke Image Display (IID)
profile call using the url elements found in the
ImagingObjectSelection
. In each result, there is a reference to the
ImagingStudy
FHIR object which can provide more information about each study.
Joe Angina complains of shortness of breath and occasional chest pain to his primary care physician, Dr. Pat Down at Local MultiClinic, who orders a stress echocardiogram; the order is created as a FHIR
Order
resource
to
manage
the
workflow,
with
a
link
to
a
resource to manage the workflow, with a link to a
DiagnosticOrder
resource
with
the
details
of
the
request.
The
order
is
scheduled
and
assigned
to
cardiologist
Dr.
Art
Skann,
also
at
Local
MultiClinic.
On
the
scheduled
day
of
the
exam,
Joe
arrives
at
the
echo
lab
to
meet
with
Dr.
Skann
and
have
the
study
done.
Dr.
Skann’s
workstation
shows
the
daily
list
of
Orders,
and
he
follows
the
link
to
retrieve
the
DiagnosticOrder.
(He
may
follow
the
links
through
the
referenced
resource with the details of the request. The order is scheduled and assigned to cardiologist Dr. Art Skann, also at Local MultiClinic.
On the scheduled day of the exam, Joe arrives at the echo lab to meet with Dr. Skann and have the study done. Dr. Skann’s workstation shows the daily list of
Order
, and he follows the link to retrieve the
DiagnosticOrder
. (He may follow the links through the referenced
Patient
resource
to
access
Joe’s
electronic
medical
record,
but
that
is
not
the
concern
of
this
storyboard.)
The
Order/DiagnosticOrder
has
been
transcoded
to
a
DICOM
Modality
Worklist
Scheduled
Procedure
Step,
and
in
the
echo
lab
the
equipment
has
downloaded
the
Modality
Worklist.
The
study
is
performed,
and
the
acquired
images
and
sonographer’s
preliminary
measurements
are
stored
in
the
Local
MultiClinic
Picture
Archiving
and
Communication
System
(PACS).
The
PACS
creates
an
resource to access Joe’s electronic medical record, but that is not the concern of this storyboard.)
The
Order
and
DiagnosticOrder
has been transcoded to a DICOM Modality Worklist Scheduled Procedure Step, and in the echo lab the equipment has downloaded the Modality Worklist. The study is performed, and the acquired images and sonographer’s preliminary measurements are stored in the Local MultiClinic Picture Archiving and Communication System (PACS). The PACS creates an
ImagingStudy
resource
for
each
study
it
manages.
Dr.
Skann
interprets
the
study
on
a
PACS
workstation,
and
he
selects
two
key
image
frames
to
be
included
in
the
diagnostic
report;
this
selection
is
stored
back
to
the
PACS
as
a
DICOM
Key
Object
Selection
with
the
title
"For
Report
Attachment",
and
the
PACS
makes
it
available
(transcodes
it)
as
a
FHIR
resource for each study it manages.
Dr. Skann interprets the study on a PACS workstation, and he selects two key image frames to be included in the diagnostic report; this selection is stored back to the PACS as a DICOM Key Object Selection with the title "For Report Attachment", and the PACS makes it available (transcodes it) as a FHIR
ImagingObjectSelection
resource.
Dr.
Skann
dictates
the
report
using
a
structured
data
entry
report
writing
program,
including
a
recommendation
for
a
cardiac
catheterization
procedure,
and
signs
it.
The
report
writing
program
formats
the
report
as
a
CDA
resource. Dr. Skann dictates the report using a structured data entry report writing program, including a recommendation for a cardiac catheterization procedure, and signs it. The report writing program formats the report as a
CDA
document,
retrieves
the
document, retrieves the
ImagingObjectSelection
resource,
and
inserts
the
referenced
key
images
into
the
report.
Dr.
Down
meets
again
with
Joe,
and
they
review
the
results
of
the
stress
test.
Joe
has
a
question
about
the
findings
that
the
key
images
in
the
report
do
not
show,
so
Dr.
Down
uses
the
Local
MultiClinic
EMR
to
query
the
PACS
for
the
full
resource, and inserts the referenced key images into the report.
Dr. Down meets again with Joe, and they review the results of the stress test. Joe has a question about the findings that the key images in the report do not show, so Dr. Down uses the Local MultiClinic EMR to query the PACS for the full
ImagingStudy
resource,
and
uses
the
references
there
to
open
an
image
display
for
the
full
study.
Joe
agrees
to
proceed
to
catheterization,
and
Dr.
Down
sends
a
referral
to
the
Ginormous
University
Hospital
cath
department,
and
triggers
the
PACS
to
share
the
echo
study
through
the
Metropolitan
Health
Information
Exchange.
The
PACS
creates
a
manifest
of
the
study
as
an
resource, and uses the references there to open an image display for the full study. Joe agrees to proceed to catheterization, and Dr. Down sends a referral to the Ginormous University Hospital cath department, and triggers the PACS to share the echo study through the Metropolitan Health Information Exchange.
The PACS creates a manifest of the study as an
ImagingObjectSelection
resource,
which
includes
all
the
images
but
excludes
the
sonographer’s
preliminary
measurements
(which
as
a
matter
of
policy
are
not
shared
outside
the
Local
MultiClinic).
The
manifest
is
published
to
the
Metro
HIE.
(In
accordance
with
IHE
XDS-I,
the
images
themselves
are
not
directly
published
to
the
HIE,
but
available
for
on-demand
retrieval
from
the
PACS.)
At
Ginormous
Hospital,
Dr.
Cora
Plummer
receives
the
cath
referral,
and
looks
up
the
study
in
the
Metro
HIE
registry.
She
retrieves
the
study
manifest
ImagingObjectSelection,
and
uses
it
to
access
the
shared
images,
which
she
uses
to
prepare
for
the
cath
procedure.
resource, which includes all the images but excludes the sonographer’s preliminary measurements (which as a matter of policy are not shared outside the Local MultiClinic). The manifest is published to the Metro HIE. (In accordance with
IHE XDS-I
, the images themselves are not directly published to the HIE, but available for on-demand retrieval from the PACS.)
At Ginormous Hospital, Dr. Cora Plummer receives the cath referral, and looks up the study in the Metro HIE registry. She retrieves the study manifest ImagingObjectSelection , and uses it to access the shared images, which she uses to prepare for the cath procedure.
Search parameters for this resource. The
common parameters
also apply. See
Searching
for
more
information
about
searching
in
REST,
messaging,
and
services.
for more information about searching in REST, messaging, and services.
| Name | Type | Description | Paths |
| author | reference |
|
ImagingObjectSelection.author
( Device |
| authoring-time | date |
|
ImagingObjectSelection.authoringTime |
| identifier | uri |
|
ImagingObjectSelection.uid |
| patient | reference |
|
ImagingObjectSelection.patient
( Patient ) |
| selected-study | uri |
|
ImagingObjectSelection.study.uid |
| title | token |
|
ImagingObjectSelection.title |