Date
Attendees
- Brian Postlethwaite (Telstra Health)
- Brett Esler (Oridashi)
- Stephen Royce (The Australian ...)
- Angus Millar (The Australian ...)
- Shovan Roy Roy(Accenture)
- Grahame Grieve (Health Intersections)
- Jared Davison (Medical Objects)
- Jason Steen (himself)
- (no dial in attendees)
Agenda
Update on International Activities / STU3 development progress and timelines
Status of the Roadmap document and possible publication dates.
Local Profile Status
Continue Work on Patient Identifiers Profile
Connectathon notes
What to do next in PA?
other options: Service Provider Directories, linkages to other things like referrals (for supporting reasons)?
Notes
HL7 International is considering deferring the publication of STU3 from end of this year to end of February due to the volume of content coming in the ballot.
The HL7 International January WGM will continue to work on ballot reconciliation.
Only pushback so far has been internally from HQ International.
STU3 conformance, infrastructure, Patient (and a handful of other foundational resources) are targeted for a normative-ish status during this round.
Current Australian installations:
- 1.4.0 implemented in NCTS (ontoserver - NEHTA terminology server)
- 1.4.0 implemented in MyHealthRecord
- Majority of vendor implementations using DSTU2
Others are experimental operations
As advised by Nat Wong, the Roadmap document is to be presented for approved to release at the National Health CIO Forum (NHCIOF)
Lower than expected turnout for the FHIR Connectathon, more publicity and chasing would have been beneficial (organization/co-ordination was lower capability)
This should be some feedback to the new Board to facilitate the administration of this, and potentially introduce some v2 content and try and make things more focused and managed tracks.
The email notifications need some work/administration, consider maybe getting it published on Pulse-IT
Patient matching/v2 interactions/conversions?
FHIR apps Showcase? What IS possible now?
Support upcoming project needs to facilitate the use of FHIR.
Future PA Activities
Tracking the Argonaut profiles into relevant Australian profiles
AU Core - Patient/Encounter
Directory resources
Document management? (PA?) let IHE cover this first?
Existing Profile activities
Patient Medicare Number
After much discussion on the various proposals to date, settled on
Identifier system value will be "http://ns.electronichealth.net.au/id/medicare-number"
Motion raised by: Brett Esler Seconded by: Grahame Grieve 7/0/0, motion passes.
Brian Postlethwaite will update the profile examples and information on the appropriate pages/places.
Provide guidance on MRN usage and organizational/institutional boundaries
Profilng the address - geocodes, postal DPID
phone numbers?
profile surnames to singular (space separated)? unspoken names