...
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.
...
...
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.
...
Appendix 10 Addressing messages using Australian Profile for Provider Directory Services (Normative)
...
When using the Australian Profile for Provider Directory Services, the values from this field must match with the sending party's Endpoint[x].au-receivingfacility for receiving acknowledgements or responses to this message as published in the directory of the messaging system being used for the transaction.
Each component of the MSH-4 (HD) field must be valued with the FHIR valueString according to each of the extensions Endpoint resource's au-receivingfacility as per the following table. ...
HL7OO: resolve comment from Appendix 8 A8.12.2.5 PRD-5 Provider communication information (XTN)
...
HL7OO: resolve comment from A8.12.2.5.2 Healthcare Service providers
...
Each component of the MSH-5 (HD) field must be valued with the FHIR valueString according to each of the extensions Endpoint resource's au-receivingapplication as per the following table. ...
...
Each component of the MSH-6 (HD) field must be valued with the FHIR valueString according to each of the extensions Endpoint resource's au-receivingfacility as per the following table.
...
HL7OO: resolve comments on HealthcareService.location.address.line[0..*] from A8.12.2.3 PRD-3 Provider address (XAD)
...
Appendix 8 Simplified REF profile (Normative)
...
In the Australian setting for ORU messaging, the first repeat of this field is used to identify the target provider for this each message. A location specific ID is used and the field should not repeat as each message is unique for the target providerof the target provider for this message must be placed in the first repeat and will be unique for each instance of messages to be routed. Where available the Medicare provider number is used as this provides for a location specific identifier. Messages should be routed based on this field and only the first repeat is used.
The consulting doctors can be specified in the second or following repeats of this field.
In the Australian context, where possible, this XCN data must be populated using the method described in A10.1.2.1 XCN Datatype.
...
- 17. @Brett Esler - Update links to all Standards on the HL7 Australia O&O WG page – Australian Diagnostics and Referral Messaging – Localisation of HL7 v2.4 Standard is still referenced as ‘Current Draft Standard’ as per https://confluence.hl7australia.com/display/OO/Current+Draft+Standards – pending
- 32. @Kieron McGuire - Contact @Brett Esler to have pages for Profile URIs (FHIR Provider Directory) & update link for FHIR R4 Value sets to return user to correct version of HL7 Standard
- 33. @Jared Davison – create a checklist prior to final draft Standard being published
- 41. @David McKillop to provide presentation on ADHA Diagnostic Report FHIR Implementation Guide (20 – 30 mins) after 06 October meeting
- 43. @Jared Davison to review draft Standard to ensure no other reversions have occurred
- 45. @Jared Davison to prepare PDF of draft Standard
- 47. @Dalisay Giffard to share authorised outcomes of Queensland Health meeting discussions on gender identification
- 54. @Jakub Sielewicz to ensure @Jared Davison’s work on A10.1 Addressing messages Introduction is consistent with ADHA’s Secure Messaging Implementation Guidance Paper
...