Attendees
- Angus
- Argus
- Brett Esler
- Brian Postlethwaite brian.postlethwaite@health.telstra.com
- HL7 Australia treasurer@hl7.org.au
- Jaco (Healthdirect)
- Jared Davison (Medical-Objects) jared@medical-objects.com.au
- Jeremy Crawford (MD)
- Kyle (HealthLink)
- Lawrence (HealthLink)
- Murukesh
- peter young pyoung@healthconnex.com.au
- Rob Dawson robert@rojotek.com
- Steven
- Sushant
- Thomas Ellis thomas.ellis@medical-objects.com.au
- Yoel sales@coreplus.com.au
Agenda
- PD FHIR Implementation Guide updated - http://build.fhir.org/ig/hl7au/au-fhir-pd/index.html quick walkthrough of updates
- Connectathon Event - planned 25th July 2017 Brisbane
- Draft Publication timeline - IG connectathon branch (6th July; Review until 13th July - next meeting); examples added up to the event
- Validation tooling - in progress for instance validation based on the profiles
- Follow-up LDAP reference usage
- HealthcareService roles: category, type, specialty ? Which to require - just specialty?
- Follow-up: role codes - service + practitioner (will work up some CodeSystems and look at mapping)
- Review basic API for search (for Connectathon) http://build.fhir.org/ig/hl7au/au-fhir-pd/guidance.html
- Example services will be populated with example data - so can see searches being made
Address searching which to require?
Name Type Description Expression address string A (part of the) address of the location Location.address address-city string A city specified in an address Location.address.city address-country string A country specified in an address Location.address.country address-postalcode string A postal code specified in an address Location.address.postalCode address-state string A state specified in an address Location.address.state address-use token A use code specified in an address Location.address.use
Minutes
- Update on implementation guide content and connectathon plans
- Recommendation to approach agency to support use of Aegis testing tools (cost)
- LDAP certificate references are currently used in production
- Concern raised that certificate references create end-user usability issued compared to value (PEM) entries
- Resolved to retain the certificate reference element in Endpoint extension to support current usage; vendors can move to value (PEM) entries based on client user feed back when if/when desired.
- Further discussion on HealthcareService, PractitionerRole roles use - no firm resolution with different granularities and coding
- Quick discussion on search API; request for feedback on required scope
Action items
Brett: notify formally of connectathon event