AU Base Implementation Guide
5.0.1-ci-build - CI Build Australia flag

AU Base Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 5.0.1-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-base/ and changes regularly. See the Directory of published versions

Resource Profile: AU Base Composition

Official URL: http://hl7.org.au/fhir/StructureDefinition/au-composition Version: 5.0.1-ci-build
Standards status: Trial-use Maturity Level: 2 Computable Name: AUBaseComposition

Copyright/Legal: HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved.

This profile defines a composition structure that localises core concepts for use in an Australian context. The purpose of this profile is to provide national level agreement on core localised concepts. This profile does not force conformance to core localised concepts. It enables implementers and modellers to make their own rules, i.e. profiling, about how to support these concepts for specific implementation needs.

Usage Notes

Profile specific implementation guidance:

  • It is important to clearly differentiate between representing the extent of a system’s information for a patient versus clinical judgement of no relevant finding:
    • When asserting clinical judgement that there are no items of specific interest, (e.g. no current medications, no known allergies, or no history of vaccination), Composition.section.entry with a reference to a supported FHIR resource containing the record of assertion should be sent.
      • Guidance is provided in the core FHIR specification for AllergyIntolerance and Condition, and AU Assertion of No Relevant Finding is defined in this implementation guide to support additional concepts.
    • When a statement is about the nature or extent of the information the system has access to or is permitted to share, (e.g. not asked or information withheld), Composition.section.emptyReason should be sent with an appropriate code from the ListEmptyReasons value set.

Usage:

Changes since version 5.0.0:

  • No changes
  • Formal Views of Profile Content

    Description of Profiles, Differentials, Snapshots and how the different presentations work.

    This structure is derived from Composition

     

    Other representations of profile: CSV, Excel, Schematron