Page tree
Skip to end of metadata
Go to start of metadata

Attendance

Apology 

Agenda

    1. Regulation 24 change made (thanks BP) merged today for review 
    2. RTO query: 
      I’m working on AU Base Organization. It currently does not provide guidance on pharmacy approval numbers, which I assume are best modelled as a type of organisation identifier.
      See https://github.com/hl7au/au-fhir-base/issues/370
      Has a design for this been included in the ETP work? Is it on its way to HL7 AU?
    3. Datatypes profiles on identifiers changes in PA what to do with MedicationRequest.code, Medication.code, MedicationDispense.code, MedicationAdministration.code wrt datatype profiles

Minutes

    • BE/DB meet to confirm further content to include in AU Base ; including
      • pharmacy approval number for Organization : Organisation.identifier:pharmacyapprovalNumber ** need to get Brett to add to AU base** 
      • many other extension and representations
      • Note: RTO this is the plan for this
    • BE will check the merge of Reg 24
    • Datatype profiles discussed
      • Medication related identifiers datatype profiles to be drafted (pharmacy approval number, etp vendor identifiers etc au-fhir-base - creation of Identifier datatype profiles)
      • for CodeableConcept (e.g. MedicationRequest.code)
        • create a CodeableCodeable concept datatype to be reused in MedicationRequest, MedicationAdministration, MedicationDispense, Medication
        • name: AU Medication CodeableConcept
        • CodeableConcept profile will have CodeableConcept.coding as a Datatype choice where there is one datatype per medication coding system
        • For example Datatype profiles for AMT, MIMS, PBS, GTIN + TGA etc. defined as profile on Coding
        • See “AUST L”
 https://www.tga.gov.au/listed-medicine"

Actions

      • BE: discuss with Primary Care project; Agency and eHealth NSW intensive care handover project wrt medicines list
      • BE: Verifier role - describe usage; checked by e.g. student or policy of second observe
      • BE: discussed Composition.section code use across multiple IGs; potential AU Base guidance; maybe valueset for section type; rules on section content
      • BE: AU Base Body Site - > naming in narrative
      • BE: container types element in R4 query zulip chat
      • BE: check international MedicationStatement needs informationSource 
      • BE: diluent zulip chat feedback requiredDanielle to catch up with Brett on progress around new fields for the AU Base and get some idea of timelines 
      • DM: contact the Agency regarding the Medication Reason Taken feedback in the minutes
            • Check on where updates are published for others to view/review
  • No labels