SMART Imaging Access
0.1.0 - ci-build International flag

SMART Imaging Access, published by Argonaut Project. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/argonautproject/smart-imaging/ and changes regularly. See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

SMART Imaging Access Server

Requirements for a SMART Imaging Access FHIR endpoint.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

SMART ImagingStudy

An ImagingStudy as returned by a SMART Imaging Access server.

Guarantees the two things an app needs from every study: the DICOM Study Instance UID (as an identifier) and at least one WADO-RS Endpoint from which the study's DICOM data can be retrieved.
SMART WADO-RS Endpoint

A DICOM WADO-RS endpoint referenced from a SMART ImagingStudy.

The address is a WADO-RS base URL: the app appends /studies/{Study Instance UID} (and optionally deeper paths) to retrieve DICOM data. The requires-access-token extension says whether the app presents its SMART access token on those requests.

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Requires Access Token

Indicates whether retrieving data from this endpoint requires the same access token that authorized the request which returned the endpoint.

When true on a WADO-RS Endpoint returned by a SMART Imaging Access server, the app presents the same SMART access token it used for the ImagingStudy search when it retrieves DICOM data from the endpoint.

This mirrors the requiresAccessToken concept from the FHIR Asynchronous Bulk Data Request Pattern, expressed as an extension so it can travel on an Endpoint resource.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Example Patient

A patient with an MRN, as known to the EHR.
ImagingStudy search response

What an app receives from GET [imaging-base]/ImagingStudy?patient=...&_include=ImagingStudy:endpoint.
ImagingStudy with contained Endpoint

A CT study whose WADO-RS Endpoint is contained in the resource.
ImagingStudy with external Endpoint

An MR study that references a standalone WADO-RS Endpoint resource.
Standalone WADO-RS Endpoint

A WADO-RS Endpoint published as its own resource and shared by many studies.