Smart Forms
0.2.0-draft - trial-use
This page is part of the Smart Forms (v0.2.0-draft: R1 Draft) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions
| Official URL: https://smartforms.csiro.au/ig/CapabilityStatement/SmartFormsApplication | Version: 0.2.0-draft | |||
| Draft as of 2023-06-16 | Computable Name: SmartFormsApplication | |||
Copyright/Legal: Copyright © 2022+ Australian Government Department of Health and Aged Care - All rights reserved. This content is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. See https://creativecommons.org/licenses/by-sa/4.0/. |
||||
This CapabilityStatement describes the capabilities of the Smart Forms Application. These capabilities include supported FHIR profiles, RESTful operations, and search parameters. It covers supported tasks such as SMART App launch context, prepopulation and completion of forms.
Raw OpenAPI-Swagger Definition file | Download
jsonNote to Implementers: FHIR Capabilities
Additional FHIR capabilities may be 'allowed' by the system. Only the capabilities relevant to Smart Forms have been included in this capability statement.
clientThe Smart Forms Application performs interactions to support SMART App Launch, form prepopulation and form filling.
- TBD requirements and deployment considerations.
- See the Structured Data Capture Security Details section for general considerations and recommendations.
- Supports the
transactioninteraction.- Supports the
batchinteraction.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revincluderead.read.read.search-type.| Parameter | Type | Documentation |
|---|---|---|
| patient | reference | The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. |
| clinical-status | token | The client SHALL provide at least a code value and MAY provide both the code and system values. The server SHALL support both. |
| Parameters | Types |
|---|---|
| patient+ clinical-status | reference+token |
search-type.| Parameter | Type | Documentation |
|---|---|---|
| patient | reference | The client SHALL provide at least an id value and MAY provide both the Type and id values. The server SHALL support both. |
| code | token | The client SHALL provide at least a code value and MAY provide both the code and system values. The server SHALL support both. |
| _count | number | The client supports search result limiting. |
| _sort | string | The client supports search result sorting by date and MAY support other values. |
search-type, create.read, search-type, update, create.patient parameter.| Parameter | Type | Documentation |
|---|---|---|
| patient | reference | The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. |
| questionnaire | reference | The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. |
| questionnaire.title | string | The client and server SHALL support chained search questionnaire.title using the search modifier :contains. |
| status | token | The client SHALL provide at least a code value and MAY provide both the code and system values. The server SHALL support both. |
| _count | number | The client supports search result limiting. |
| _sort | string | The client supports search result sorting by authored and MAY support other values. |
| Operation | Documentation |
|---|---|
| $expand | |