Date
Attendees
- Brian Postlethwaite (Telstra Health) - chair
- Brett Esler (Oridashi)
- Angus Millar (Australian Digital Health Agency)
- Jaco Olivier (HealthDirect)
- Eric Browne (Montage)
Apologies
- Jane Gilbert (Telstra Health)
- David McKillop (Australian Digital Health Agency)
- Rob Eastwood (Australian Digital Health Agency)
- Vikas Mittal (Australian Digital Health Agency)
- Paul McMahon
- Richard Townley-O'Neill
- Uma (Health Direct)
- Uday Chandrupalta (Australia Digital Health Agency)
- Faraz Ahmed
- Satya Yelisetti (Australian Digital Health Agency)
- Stephen Royce
- Jared Davison (Medical Objects)
Agenda
- Updates review
- Summary text generator XSLT; extensions still to do
- Pull requests review
- Jaco: may send report on terminology work re. service type
- AU Base QA scope and timelines
Minutes
Jaco: Re-usable codesystems for characteristics? Can we have a simple concept here? Extensible base set? (conversation for a future meeting)
Updates review (Brett): IG Builder is progressing, and have had a large number of updates over the last few days, NATA is now in for the Organization.
HL7 Au Event is planned to occur in Melbourne September 13 & 14 (Thu/Fri), face to face working group meetings expected, hope to have this as a walkthrough and feedback review cycle on the Guides as they are.
ADHA has recommended to incorporate the STU3 (fhir version) into the canonical URL, discussion on the group thinks this is not a good idea, and other groups elsewhere aren't doing this either.
The Business Version number in the StructureDefinitions is the indicator of the versioning if older versions of the IGs do not update.
The CanonicalUrl is the concept that can span FHIR versions, and yes the representation may be different, but its the same concept.
The R4 spec has this described at http://build.fhir.org/versioning.html (2.8.3 Version Specific Profile), also check the business version in http://build.fhir.org/references.html#canonical
Action items
- Brett: add NATA identifiers to AU Base
- Proposal NATA accreditation number as Organization.identifier this how NATA refers to lab managing organisations
- Proposal NATA site number as Location.identifier this is how NATA refers to specific lab sites
- Brett: look at registry.fhir.org + simplifier for profile pub
- Brett: publish HL7 AU terminology to HL7 AU ontoserver
- Brian: follow up Tz database CodeSystem allocation with PA WG hl7.org
Attachments:
Comments:
|
Brett Esler / Brian Postlethwaite - would it be possible to discuss the COMMUNICATION CodeSystem next time round (or near future)... I am OK to accept what is provided as is, however I would like to ensure it is agreed prior to making changes on our side (since we have to update the codes on our side in the next few weeks) Reference: http://hl7.org/fhir/STU3/valueset-languages.html it is on Patient / as EXT on HCS and on Practitioner. eg. Patient.communication http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-practitioner.html |
||||||||||||||||||||||||||||||||
|
Brett Esler - can we add a HCS.characteristics binding to the topics for discussion... Specifically to define the facilities at the HealthcareService... technically, most of these "facilities" are bound to the Location, however it may change the role of location... or require an extension to be added.
|