Smart Forms
0.3.0 - ci-build
Smart Forms, published by AEHRC CSIRO. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/aehrc/smart-forms-ig/ and changes regularly. See the Directory of published versions
Official URL: https://smartforms.csiro.au/ig/ImplementationGuide/csiro.fhir.au.smartforms | Version: 0.3.0 | |||
Draft as of 2025-04-17 | Computable Name: SmartForms | |||
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 implementation guide is provided to support the use of Smart Forms.
Smart Forms is a FHIR-based solution aimed to demonstrate effective undertaking of health care assessments. It leverages SMART App Launch and the Structured Data Capture specification to support better clinical outcomes, improved clinical workflow, enhance the usefulness of information in the practice record and improve interoperability of health information.
IG | Package | FHIR | Comment |
---|---|---|---|
csiro.fhir.au.smartforms#0.3.0 | R4 | ||
hl7.terminology.r4#6.2.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology | |
hl7.fhir.uv.extensions.r4#5.2.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack | |
hl7.fhir.au.core#1.0.0 | R4 | ||
hl7.fhir.uv.extensions.r4#5.1.0 | R4 | ||
hl7.fhir.au.base#5.0.0 | R4 | ||
hl7.terminology.r4#6.1.0 | R4 | ||
hl7.fhir.uv.smart-app-launch#2.2.0 | R4 | ||
hl7.terminology#5.5.0 | R4 | ||
hl7.fhir.uv.extensions.r4#1.0.0 | R4 | ||
hl7.fhir.uv.ipa#1.0.0 | R4 | ||
hl7.terminology.r4#5.0.0 | R4 | ||
hl7.fhir.uv.smart-app-launch#2.0.0 | R4 | ||
hl7.fhir.uv.sdc#3.0.0 | R4 |
Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00) |
Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00) |
Package hl7.fhir.au.base#5.0.0 This implementation guide is provided to support the use of FHIR®© in an Australian context. (built Wed, Jan 15, 2025 23:49+0000+00:00) |
Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.ipa#1.0.0 This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Sun, Mar 26, 2023 20:50+0000+00:00) |
Package hl7.fhir.au.core#1.0.0 This implementation guide is provided to support the use of FHIR®© in an Australian context, and defines the minimum set of constraints on the FHIR resources to create the AU Core profiles. This implementation guide forms the foundation to build future AU Realm FHIR implementation guides and its content will continue to grow to meet the needs of AU implementers. (built Wed, Jan 29, 2025 20:02+0000+00:00) |
Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. |
Smart Forms is also dependent on:
In addition, the following FHIR implementation guides are referenced:
This document is a working specification that may be directly implemented by FHIR®© system producers.
FHIR®© connectathon events are key to the verification of the guide as being suitable for implementation. This implementation guide will be used as the basis for Australian connectathon events.
This guide is divided into several pages which are listed at the top of each page in the menu bar.
This guide is the product of collaborative work undertaken with participants from: