AU Core Implementation Guide
0.1.0-draft - Draft
This page is part of the AU Core Implementation Guide 0.1.0 Draft. It is based on AU Base 4.1.0. For a full list of available versions, see the Directory of published versions
Page standards status: Informative |
Systems may deploy, and support, one or more AU Core profiles (i.e. the profiles governed by this guide) to represent clinical information. Each profile defines the FHIR structures required, the data element definitions, their associated rules of usage including the use of extensions and terminology, references the additional profiles necessary to assert conformance.
A system SHOULD support all AU Core profiles unless the system does not anticipate supplying or consuming a certain type of data, usually by virtue of playing a limited or specialised role in clinical or information workflows. For example, a pathology laboratory may support AU Core DiagnosticReport, but not AU Core MedicationRequest.
To support an AU Core profile:
CapabilityStatement.rest.resource.supportedProfile
elementTo support an AU Core CapabilityStatement:
CapabilityStatement.instantiates
element: http://hl7.org.au/fhir/core/Structure/CapabilityStatement/au-core-tbd