2020-11-17 Meeting Notes

Date: Nov 17, 2020

Attendees

@Andrew McIntyre (Co-Chair)

@Michael Legg (Co-Chair)

@Dalisay Giffard

@Kieron McGuire

@Kyle Macdonald

@Philip Wilford

@Scott Ferris

@Tony Cruice

@Vincent McCauley

@Vanessa Cameron (Secretariat)

Apologies

@Angus Millar

@Brett Esler

@Christian Holmes

@Danielle Tavares-Rixon

@Lars Becker

@Liam Barnes

@Michael Czapski

@Michael Osborne

@Nick Ferris

@Paul Carroll

@Roger Hill

@Robert Flatman

Goals: 1) Address remaining HL7v2-FHIR issues not discussed in Meeting 20 Tue 03 Nov 2020

Discussion items (included the following):

Notes from Meeting 20 on 03 November 2020 were accepted by members in attendance.

Appendix 8 Simplified REF profile (Normative)

http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706-L1 - Url is broken even adding the "-L1" at the end which appears to not highlight when hovering doesn't fix the issue. There is a note below about these being URIs and may not resolve. Resolved.

It is not always feasible for sending systems to have access to the messaging system directory. Rather than being prescriptive about the values being "copied from" the directory, we should just say that they should match. See also my comment on HL7au:00045.7 re ensuring that they match. Resolved via comment about endpoint content matching - When using the Australian Profile for Provider Directory Services, the values from this field must be copied from match with the sending party's HealthcareService.Endpoint[x].au-receivingfacility as published in the directory of the messaging system being used for the transaction.

There may be multiple identifiers in the PractionerRole identifier list. It is important to map the routable identifers in the order specified in the directory entry. Note that HL7v2 systems often will consider only the first repeat of this field.

The current AU-FHIR-PD profile does not support ordering of identifiers, hence the order cannot be guaranteed.

HL7OO: Request extensions as drafted by Jared to HL7AU PA:

e.g.

</extension>

</extension>

</identifier>

copied from

It is not always feasible for sending systems to have access to the messaging system directory. Rather than being prescriptive about the values being "copied from" the directory, we should just say that they should match. See also my comment on HL7au:00045.7 re ensuring that they match.

HL7OO: drafted fix in A10.1.3.1 MSH-3 Sending application (HD)

HealthcareService

The provider directory IG allows endpoints to be referenced from HealthcareServices, PractitionerRoles, and Locations. There are valid scenarios where the acknowledgement endpoint may not be referenced from the HealthcareService. We should just say the endpoint that the acknowledgements are to be sent to rather than specifying "HealthcareService".

HL7OO: drafted in A10.1.3.1 MSH-3 Sending application (HD)

au-receivingfacility

this link does not resolve - i think it should be -

http://build.fhir.org/ig/hl7au/au-fhir-pd/StructureDefinition-au-pd-sm-endpoint-definitions.html#Endpoint.extension:receivingFacility

as per other links for HCS and Endpoint

PractitionerRole.location.address

Should this be PractitionerRole.location.address.line? Move done.

HealthcareService.location.address

Should this be HealthcareService.location.address.line? Move done.

Appendix 5 Conformance Statements (Normative)

HL7au:00044.5.6 CNE datatype conformance points and HL7au:00044.6.6 CWE datatype conformance points: <alternate text (ST)> component must be valued and this must be whit is intended for display to the user.

This implies that alternate text is mandatory; which is not true if no alternate text exists.