SMART Imaging Access
0.1.0 - ci-build
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
| Official URL: http://fhir.org/argonaut/smart-imaging/CapabilityStatement/smart-imaging-server | Version: 0.1.0 | |||
| Draft as of 2026-08-21 | Computable Name: SmartImagingAccessServer | |||
Requirements for the Imaging Server's FHIR endpoint. In addition to the FHIR behavior described here, the server hosts or links to WADO-RS endpoints as described in Retrieving images, and validates SMART access tokens as described in Authorization.
Raw OpenAPI-Swagger Definition file | Download
jsonNote to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
serverRequests carry a SMART on FHIR access token issued by the EHR's authorization server. The Imaging Server validates the token (for example, via SMART Token Introspection) and enforces patient context and scopes.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| ImagingStudy | Supported Profiles SMART ImagingStudy | y | patient, identifier, _lastUpdated | ImagingStudy:endpoint |
The server SHALL support searching ImagingStudy by patient, alone and in combination with
_lastUpdatedandidentifier(a DICOM Study Instance UID inurn:oid:...form). The server SHALL support_include=ImagingStudy:endpointso apps receive the WADO-RS Endpoint for each study, whether contained or external.If results are not yet available (for example, the server is querying an underlying PACS), the server MAY respond
503with aRetry-Afterheader; the app retries after the indicated number of seconds.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | patient | reference | The patient whose studies are requested. SHALL be supported alone and in combination with |
| SHALL | identifier | token | A DICOM Study Instance UID in |
| SHALL | _lastUpdated | date | Used with |