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 Medicine List

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

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

This profile defines a list structure that localises core concepts for use as a medicines list in an Australian context. This profile is intended to offer a common structure and expectations for a list of medications associated with a patient in an Australian healthcare context.

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 or no history of vaccination), List.entry.item with a reference to a supported FHIR resource containing the record of assertion should be sent. AU Assertion of No Relevant Finding is defined in this implementation guide for this concept.
    • 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), List.emptyReason should be sent with an appropriate code from the ListEmptyReasons value set.
  • When a related person is the author of the list, the Author as a RelatedPerson extension is used and List.source is not included.
  • If both the List.entry.changeDescription extension and List.entry.flag are populated, the extension is expected to only be used to expand on the List.entry.flag concept and not contradict its meaning.

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 List

    NameFlagsCard.TypeDescription & Constraintsdoco
    .. List 0..* List A list of medications in an Australian healthcare context
    ... Slices for extension 0..* Extension Extension
    Slice: Unordered, Open by value:url
    .... extension:sourceRelatedPerson 0..1 Reference(RelatedPerson) Related person that defined the list contents (aka Author)
    URL: http://hl7.org.au/fhir/StructureDefinition/author-related-person
    ... entry 0..* BackboneElement Entries in the list
    .... Slices for extension 0..* Extension Extension
    Slice: Unordered, Open by value:url
    ..... extension:changeDescription D 0..1 string Change description
    URL: http://hl7.org.au/fhir/StructureDefinition/change-description
    .... flag 0..1 CodeableConcept Medicine item change
    Binding: Medicine Item Change (preferred)
    .... item 1..1 Reference(MedicationStatement | MedicationRequest | MedicationDispense | MedicationAdministration | Immunization | AU Assertion of No Relevant Finding) Actual entry

    doco Documentation for this format

    Terminology Bindings (Differential)

    PathConformanceValueSetURI
    List.entry.flagpreferredMedicineItemChange (a valid code from Medicine Item Change)
    http://terminology.hl7.org.au/ValueSet/medicine-item-change
    from this IG

     

    Other representations of profile: CSV, Excel, Schematron