FHIR implementation guide for provider directory interfacing in an Australian Context
HL7 AU PA WG & SM TWG Joint
Every 2 weeks Thu, 11:30 AM - 12:30 PM AET
Next Meeting:
PC, Mac, Linux, iOS or Android: https://zoom.us/j/7479215691
or Phone: +61 (0) 2 8015 2088, Meeting ID: 747 921 5691
Specification
http://build.fhir.org/ig/hl7au/au-fhir-pd - Australian Provider Directory Profile FHIR Implementation Guide; draft material (constant integration build); this version my be inconsistent at times
http://hl7.org.au/fhir - Australian Provider Directory Profile FHIR Implementation Guide snapshots for event/connectathons are listed here; these are published to be stable for use during events
Reference Material
http://hl7.org/fhir/index.html - FHIR (STU3) core specification that is the basis of implementation guide work. It contains all core material for FHIR usage and also references tooling, open source projects, reference server implementations, testing tools and community material.
https://chat.fhir.org/ - The main instant messaging chat channel using the Zulip tool for international participation. This contains many streams of conversation on FHIR specifications, implementation and usage. There is an ‘australia’ channel focused on Australian context and many other channels of interest, commonly used for discussion, questions/answers and announcements.
http://hl7.org.au/fhir - Directory of FHIR Implementation Guide versions including AU Base FHIR Implementation Guide and AU PD Implementation Guide; the provider directory IG depends on the AU Base FHIR IG content (derives from).
http://build.fhir.org/ig/Healthedata1/Argo-PD/ - US Argonaut project draft documentation related to work undertaken by Argonaut vendors and the ONC provider directory workshop. Offers international perspective on provider directories functionality.
Example Provider Directory Search
Connectathons
- AU PD FHIR IG #4: 2018-04 Brisbane - Connectathon Streams - Intro, AU Base and Provider Directory
- AU PD FHIR IG #3: 2017-12 Melbourne - Provider Directory
- AU PD FHIR IG #2: 2017-09 Brisbane - Provider Directory
- AU PD FHIR IG #1: 2017-07 Brisbane - Intro / Provider Directory
- AU Base IG (related material): 2017-05 Sydney - Intro / AU Base / Terminology
Workshops
Meetings
- Meeting SM TWG 2019-09-05
- Meeting SM TWG 2019-08-08
- Meeting SM TWG 2019-07-25
- Meeting SM TWG 2019-07-11
- Meeting SM TWG 2019-06-27
- Meeting SM TWG 2019-06-13
- Meeting SM TWG 2019-05-16
- Meeting SM TWG 2019-05-02
- Meeting SM TWG 2019-04-18
- Meeting SM TWG 2019-03-21
- Meeting SM TWG 2019-03-07
- Meeting SM TWG 2019-02-21
- Meeting SM TWG 2019-02-07
- Meeting SM TWG 2019-01-24
- Meeting SM TWG 2018-12-13
- Meeting SM TWG 2018-11-15
- Meeting SM TWG 2018-11-01
- Meeting SM TWG 2018-10-18
- Meeting SM TWG 2018-10-04
- Meeting SM TWG 2018-09-20
- Meeting SM TWG 2018-09-06
- Meeting SM TWG 2018-08-23
- Meeting SM TWG 2018-08-09
- Meeting SM TWG 2018-07-12
- Meeting SM TWG 2018-06-28
- Meeting SM TWG 2018-06-14
- Meeting SM TWG 2018-05-31
- Meeting SM TWG 2018-05-03
- PD Terminology Discussion
- Meeting SM TWG 2018-04-05
- Meeting SM TWG 2018-03-22
- Meeting SM TWG 2018-03-08
- Meeting SM TWG 2018-02-22
- Meeting SM TWG 2018-02-08
- Meeting SM TWG 2018-01-25
- Meeting SM TWG 2017-12-14
- Meeting SM TWG 2017-11-30
- Meeting SM TWG 2017-11-30xx
- Meeting SM TWG 2017-11-16
- Meeting SM TWG 2017-11-02
- Meeting SM TWG 2017-10-19
- Meeting SM TWG 2017-10-05
- Secure Message Delivery POC
- Meeting SM TWG 2017-09-21
- Meeting SM TWG 2017-09-07
- Meeting SM TWG 2017-08-24
- Meeting SM TWG 2017-08-10
- Meeting PD Connectathon Pre-Event 2017-07-20
- Meeting SM TWG 2017-07-13
- Meeting SM TWG 2017-06-29
- Example Provider Directory Search
- Meeting SM TWG 2017-06-14
- 2017-06-08 Secure Message TWG Workshop
- Provider Directory IG Timelines
9 Comments
Brett Esler
Things to talk about from the connectathon
Jaco
Brett Esler -
As discussed last week at the Connectathon - just adding the notes hereto:
While reviewing the HealthcareService resource, we identified that the support for "eligibility" is somewhat limited - as the multiplicity is 0..1 and the "note" is stored separately...
Wondering if it would be possible to make a recommendation to HL7 International (or implement a Complex Extension as part of AU-BASE if not accepted) as follows:
I am proposing an improvement with a more supportive Eligibility structure:
Brett Esler
Thanks Jaco - what are some examples for this element?
Jaco
Apologies Brett - I missed your question on this comment. Here are two samples, each with a different method of modelling it.
Option B is over engineered.
Jaco
Brett Esler -
As per the discussion last week - the ContactPoint resource has the "use" attribute, bound to the valueSet (http://hl7.org/fhir/ValueSet/contact-point-use)
Supporting basically only, home and work.
Within the NHSD, there are more "contactPurposes" in use - and think that many other directories may have more context than just home / work.
Should we have to "map" all of our purposes to the current HL7 valueSet, I believe we would be losing a lot of context, however the data would still be accurate.
Would you agree that we look into the AU-BASE profile and allow for this "valueSet" to be extensible (1), or define a more detailed/supportive valueSet (2) for "contact-point-use"
Brett Esler
Thanks - is that for HealthcareService.telecom?
Jaco
The example was mostly focused towards HealthcareService.telecom, however an extensible (or AU-BASE) set of contactPurposes may also be applicable to Organization and even ProviderLocation.
Kieron McGuire
Can a link to the static version for the September2017 connectathon be added to the Specifications section?
Brett Esler
done now