Created by Dusica Bojicic, last modified by Brett Esler on 28 Apr, 2020

Attendance

Apology 


Agenda


Minutes

    • #320 Pharmacy shared medicines list 
      • e.g. rural and remote - no long standing relationship with pharamcist; no patient contact
      • patient interview can produce this
      • context of use needs to be defined
      • identify cases where this applies
      • state this is not the preference if item level info is available
      • maybe list only as an extension (not referenced)
      • DM and BE to talk to Danielle B
    • #397 
      • pharmacy shared medicines list; medicines review
        • desire to indicate the DAA at the items level
        • consider multiple DAA
        • perhaps type of DAA.
      • DAA as List
        • perhaps for planned/managed administration to individual 
        • use Medication modelling for manufactured 
      • Could do extension on MedicationRequest, MedicationStatement etc. to indicate standalone


Actions

      • Datatype profile for medication codeableconcept - AU base (Medications DataType profiles #312) - profile emailed to Brett for inclusion in the AU Base content
      • DB - follow up with NCTS on suitable content for MedicationStatement.statusReason valueset - expand on https://healthterminologies.gov.au/fhir/ValueSet/medication-reason-not-taken-1 - discussed with Agency BAs & raised a request for a new value set
      • 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 chatBE: 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 
              • Check on where updates are published for others to view/review