Skip to main content
ID
DG-3126
Type
Guide
Status
Active

Successful message exchange is dependent upon the correct population of segments MSH-3, MSH-4, MSH-5 and MSH-6 of outgoing messages, using information that matches the information held in an online Provider Directory. Detailed instructions on how to populate these fields can be found in the REF-I12 specification (links to the relevant parts of the specification are provided below). These instructions apply equally to the population of the MSH-3, MSH-4, MSH-5 and MSH-6 segments found in MDM-T02 messages.

Sender Information:

Message sender information is specified in segments MSH-3 and MSH-4 of the message.

MSH-3 must be populated with information that matches the information specified in the au-receivingapplication property of the sender's Endpoint (the one on which the RRI-I12 or ACK-T02 acknowledgement will be received) in the online provider directory (i.e. HealthcareService.Endpoint[x].au-receivingapplication or PractitionerRole.Endpoint[x].au-receivingapplication). MSH-3 may be left blank if no au-receiving application is specified in the online directory.

MSH-4 must be populated with information that matches the information specified in the au-receivingfacility property of the sender's Endpoint (the one on which the RRI-I12 or ACK-T02 acknowledgement will be received) in the online provider directory (i.e. HealthcareService.Endpoint[x].au-receivingfacility or PractitionerRole.Endpoint[x].au-receivingfacility).

Recipient Information:

Message recipient information is specified in segments MSH-5 and MSH-6 in the message.

MSH-5 must be populated with information that matches the information specified in the au-receivingapplication property of the recipient's Endpoint (the one being used for the messaging transaction) in the online provider directory (i.e. HealthcareService.Endpoint[x].au-receivingapplication or PractitionerRole.Endpoint[x].au-receivingapplication). MSH-5 may be left blank if no au-receiving application is specified in the online directory.

MSH-6 must be populated with information that matches the information specified in the au-receivingfacility property of the recipient's Endpoint (the one being used for the messaging transaction) in the online provider directory (i.e. HealthcareService.Endpoint[x].au-receivingfacility or PractitionerRole.Endpoint[x].au-receivingfacility).

Further information can be found in the following specifications: 

REF-I12 specification – instructions for populating MSH-4 and MSH-6: 
https://confluence.hl7australia.com/display/OOADRM20181/Appendix+8+Simplified+REF+profile#Appendix8SimplifiedREFprofile-A8.12.1Facility/Organisationalleveladdressing

REF-I12 specification – instructions for populating MSH-3 and MSH-5:
https://confluence.hl7australia.com/display/OOADRM20181/Appendix+8+Simplified+REF+profile#Appendix8SimplifiedREFprofile-A8.12.3Applicationleveladdressing

FHIR PD2 specification for Endpoints:
http://hl7.org.au/fhir/pd/pd2/StructureDefinition-au-pd-sm-endpoint.html