Date

Attendees

Agenda

  • Practitioner Qualifications working session, review the drafts worked on by Jane GilbertBrian PostlethwaiteRob Eastwood and Uday - see https://github.com/hl7au/au-fhir-base/pull/324
  • New - AU Base Practitioner Role: identifier:nationalProviderAtOrganisation has the format of "HPI-I@HPI-O", but currently has the constraint of "inv-npio-0: NPIO length is exactly 33 characters" which would allow any 33 characters.  Should there be further constraints such that characters 1-16 should conform to HPI-I, character 17 = "@" and characters 18 to 33 should conform to a HPI-O?

  • New - AU Base Organization: remove max length constraints as invariants perform this check. GitHub #336
    Agreed, however think that a min length and max length would be preferred, as these can be used in user interfaces too, and remove the invariant for the length. (and any other identifiers with this type of restriction)
  • New - AU Base Practitioner Role profile: minor detail - identifier:nationalProviderAtOrganisation.type.text is "NPIO" where as the text in other identifier slices is the display content of table 0203 and hence should identifier:nationalProviderAtOrganisation.type.text be "National provider at organisation identifier" rather than "NPIO"?
  • New -codesystem-au-hl7v2-0203: fix QA error but there are implications for implicit value set capability; see GitHub #327  ** Leave discussion til Feb 2020.  - implications?
  • New - AU Base Organization: consider Organization.contact extension reference for 0..* locations; see GitHub #337   ** Leave til 2020.
  •  AU Base Organization: add constraints for NATA identifier value  GitHub #335
  • AU FHIR Base profiles with sliced identifiers - bad use of pattern and fixed value  GitHub #319

  • BE : PD issues and questions from Scott Ferris Agency 

  • Review HL7 International Encounter modelling issues

  • Review HL7 International Patient Merge draft

  • Done New - Agency is reviewing "AU Base Address", should it be visible from the AU Base IG somewhere?
    Yes, include in the data types extensions (it is a best practice for AU addresses)
  • Done New - AU Base Address profile - being generated but not linked in IG (still has some STU3 references)
    Agreed - take out the STU3, as these are all version agnostic extensions. Updating some of the examples to check the validation rules (expected failing ones don't fail).

  • Connectathon - update
  • New - AU Base Organization: Australian localised terminology for au-organization.type: Currently has "Binding: OrganizationType (example)".  Refer to GitHub:  #333
    Note: Provider Directory (StructureDefinition-au-pd-organisation ) uses the default Binding: OrganizationType (example).
    Valueset not currently expanding, this seems like the correct path to be taking, and propose updating the binding strength to preferred or extensible if the values appear to cover the scope adequately and should be able to get wide support for them - the au-pd example set has other in it, which makes it problematic for an extensible binding. Would be good to walk through in Sydney at WGM
  • New - AU Base Organization: Australian localised terminology for au-organization.contact.purpose.  Current valueset (http://hl7.org/fhir/R4/valueset-contactentity-type.html) seems insufficient - would like to accommodate "emergency contact", "Out of hours". (GitHub issue #334)
    would be good to get more clarification on the definition of "emergency contact", and "out-of-hours" is more of an availability field rather than purpose, and also requires the context of what the hours are, which is possibly a location based thing... VhDir defined a complex extension http://build.fhir.org/ig/HL7/VhDir/StructureDefinition-contactpoint-availabletime.html, may consider this, or something a similar way.
  • New - AU Base Organization: NATA identifier has no invariant(s) controlling the quality of the value, whereas all other identifiers do. GitHub #335
    Makes sense, please gather the details (wink)
  • Yes, this makes sense, we should consider if there is any meaningful shortening of the above, but probably not.
  • New - AU Base Organization: remove max length constraints as invariants perform this check. GitHub #336
    Agreed, however think that a min length and max length would be preferred, as these can be used in user interfaces too, and remove the invariant for the length. (and any other identifiers with this type of restriction)

Minutes

  • BP to report on HL7 PA work international
  • Qualifications will need more discussion BP to report on international work
  • NPIO validation made into an issue #348
  • identifiers should have a max length if known; useful constraint for UI and databases; must be consistent with other constraints see  #336 RE will develop issue
  •  identifier:nationalProviderAtOrganisation.type.text  - text is an allocated short name for display; does not need to be related to type code display; no action
  • Get Liam to explain implications of GitHub #327  
  • Follow this with BP and PA international  GitHub #337 
  • Constraints for NATA identifier - some info via DM; further confirmation of leading 0's; confirm a plan for final contraint definition GitHub #335
  • https://github.com/hl7au/au-fhir-base/issues/319 see if RTO will withdraw this item after discussion
  • Scott Ferris federation likely needs provenance; there is no documented common approach so needs some more work on defining this practice - BE to respond
  • BE - breakdown these issues on PD to github issue; approval for HealthcareService as mandatory for PractionerRole and adding search for PractitionerRoles at a HealthcareService- need meeting with participants
  • PD resolve issues - improve validation in AU base ; ballot cycle for PD and AU Base - include SRA concerns
  • Look next time - Liam would be good to comment on - au-organization.type we can bind to NCTS valueset for better viewing - need agreement to proceed
  • RE - residential aged care medications chart; work may be on soon to include this 

Next Meeting

  •  

Action items

  • Brett Esler to contact HISA to see if they have any informatics people that can assist in the review of the data elements and terminologies
  • Brett Esler to check if there is a contact in the College of General Practice that can assist
  • Jane Gilbert to check with AHPRA if they are able to assist with this
  • Brian Postlethwaite to check with the US ONC folks for some examples on their usage



Attachments:

Comments:

FYI re National residential medication chart - link to home page (Australian Commission on Safety and Quality in Health Care)

https://www.safetyandquality.gov.au/our-work/medication-safety/national-residential-medication-chart

Posted by rob.eastwood at 12 Feb, 2020 16:57