Date

Attendees

Agenda:

Identifier Datatypes

Review Github issues + AU Base commits

AU Base Ballot

Minutes:

Rob Eastwood: identifier datatype profiles

Good progress on this, the profiles look good - Danish Agency is using this approach combined with slicing in the Patient profile to "introduce" the identifier, and then let the datatype profile define the content.

https://docs.ehealth.sundhed.dk/latest/ig/StructureDefinition-ehealth-skrs-patient.html https://docs.ehealth.sundhed.dk/latest/ig/StructureDefinition-ehealth-patient.html

Agree to base patient profile to leverage the datatype profile on the slices (and done elsewhere too)

Github issues:

https://github.com/hl7au/au-fhir-base/issues/313 - This is the issue discussed above, now able to proceed with ADHA doing the work on the resources/identifiers required to support the SRA

AHPRA registration details - profession associated with the registration, subtypes etc. This extended content would sit within the qualification, not the identifier on practitioner.

Discussion on the SRA Address profile to include the GNAF identifier, and possibly the DPID (currently only profiled GNAF)

https://sra.digitalhealth.gov.au/fhir/StructureDefinition-sra-address.html

Pondered the issues around the selection of Identifier as the extension type, rather than string - benefits both ways, (will see how it proceeds with the DPID as well)

It was noted that this extension is on the address datatype and not on location, this then permits it to be used in patients, locations, relatedpersons etc.

Follow up:

  • AGENCY: Review all valueset references to NCTS make FHIR IG valuesets - priortise this to SRA scope 
  • JD: direct service correspondence to a nominated specific individual; HealthcareService extension
  • JD: backup delivery person as PractitonerRole extension - HL7 V2 STF
  • Rob Eastwood: Continue to "cleanup" the identifier datatypes now that the approach is good
  • BE: put PD POC changes in a github issues and work on the changes in CI build of PD spec; review next time
  • BP: Chase up if existing work on AHPRA registration extensions already exists