HL7AU - FHIR WG : Meeting SM TWG 2017-11-16

16 Nov 2017

Agenda

Federation Discussion
1. Client (end user systems) secure access
  1. options OAuth2, OAuth2 as SMART-on-FHIR, Certificates
  2. select and reduce the number of options
2. Backend federated search (SM vendors) certificate mutual authentication with CSP NASH Certificates
Query from PA WG - Is Location 0..1 for HealthcareService required; can we allow 0..*; NOTE: service descriptions in HealthCareService must apply to all listed locations
Connectathon https://www.digitalhealth.gov.au/news-and-events/events/secure-messaging-connectathon-2017
1. Connectathon wiki page will appear shortly
2. Terminology work ANZSCO/ANZSIC to be completed
3. Static publication of FHIR specification ETA 23/11
4. Touchstone test cases are in development ETA 29/11

MO raised: MSH sending/receiving facility; Endpoint from directory - query need facility to be verified by certificate content; trust in certificate authority
Vendor certificate authority; no current general guidelines on how to trust certificates
#2 Meeting agreed no issue with relaxing 0..1 Location to 0..* to allow common service definitions across multiple locations; let this be managed based on desired location and endpoint needs
#1 Quickly ran through federation authentication options discussions as per agenda items
Recommended: consider SMART-on-FHIR (OAuth2) methodology; is likely part of FHIR STU4 published content
Provide directory acces authentication: check PRODA as potential authentication method for provider directory services
No decisions made