HL7AU - FHIR WG : Meeting SM TWG 2019-05-02


Attendees:

  • Brett Esler

Apologies:

  • Adrian Wilde (XVT)
  • Brian Postlethwaite
  • Reuben Daniels
  • William Durnford
  • Kyle MacDonald
  • John Carter
  • Murukesh Chandran
  • Jakub Sielewicz
  • Jaco Olivier
  • Jared Davison
  • Philip Wilford
  • Jeremy Crawford
  • Kieron McGuire
  • William Durnford
  • Steven Whittington
  • Philip Loya
  • Thomas Clarke

Agenda

  • AU Base Update
  • Search parameters addition
  • Where next for SM TWG?

Minutes

  • PD can pre-apply changes before 
  • PD → R4 ; AU Base (PD relevant content only) → R4  BE + DTR get a timeline together
  • Search for Locations by managingOrganization (existing core FHIR search parameter 'organization' is available) - Can use search on HealthcareService, PractitioneRole ( organization.identifier ) and then get locations to present from result using current capability requirements
  • HealtcareService.name implies a single location due to constraints
  • JC: aliases need to be thought about as HealthcareService does not support alias - raise issue with PA WG (international) HealthcareService.name being string 0..1 need other names alias etc. just like Organization (maybe add a type)  raise with BP 
  • Clarify name search on Organization is across alias names also in PD spec (BE to do)

Action items

  • BE: investigate why valueset expansion no longer happening
  • include: X509 mutual Auth referenced will be mandatory profile 
  • include: x-API-key documented as an optional profile
  • include: SMART on FHIR as an optional profile reference client profile http://www.hl7.org/fhir/smart-app-launch/ ;  informative B2B informative work progressing - BP send link
  • future: keep an eye on PRODA progress (B2B PRODA)
  • BE: Change reference to SMD standard ATS 5822-2010 rather than 2013 http://build.fhir.org/ig/hl7au/au-fhir-pd/guidance.html
  • BE: specialty is R4 only - so needs to be noted as custom for STU3
  • BE: followup on Touchstone when profiles available
  • BE: follow up on other territories for the states ValueSet not needed at this stage
  • HealthcareService.type binding will be to valueset descendant-of 224930009 BE: to add to CI build
  • HealthcareService.specialty binding - potentially descendant-of 223366009 / 394658006 
    • resolve to have sliced element with slice for each valueset 
    • keep the current ValueSet 224891009 (Healthcare services) as a slice
    • BE: add to CI build
  • Header x-API-key MAY be supported by client/server systems. BP provide some information on this profile : discussion will continue on this


Attachments: