Processing MSH-11 3 R BusProc The following values must be used: P – normal processing D – debugging T – training P is the default Version ID MSH-12 60 R BusProc Format: ‘2.4’ HL7 version 2.4 format can optionally extend to the ‘Internationalisation Code’ and ‘International Version ID’ components allowed by HL7. MSH-1 – field separator The field separator character will be ‘|’. Example: MSH|^~\&|DELPHIC... MSH-2 – encoding characters This field contains the separator characters for component, repeat and the escape character and respectively. We strongly recommend that this field contain ‘^~\&’. Please see the section above on separators. Example: MSH|^~\&|DELPHIC|MEDLAB|LABRESULT|... MSH-3 – sending application This field should be filled in with the name of the sending application. Since this message is usually sent from a laboratory, this normally contains the name of the laboratory application. If the laboratory application is not named, this field should contain the text ‘LABRESULT’; most messages use this value. Example: In this case the sending laboratory uses the Delphic Laboratory Results module: MSH|^~\&|DELPHIC|ediaccnt|LABRESULT|... MSH-4 – sending facility This field should be filled in with the EDI account name of the sending facility. This must be filled in correctly so that message acknowledgements can be correctly processed. This field should not be more than eight characters in length and should always be in lower case. Example: MSH|^~\&|DELPHIC|ediaccnt|EPISURV|...
Processing MSH-11 3 R BusProc The following values must be used: P – normal processing D – debugging T – training P is the default Version ID MSH-12 60 R BusProc Format: ‘2.4’ HL7 version 2.4 format can optionally extend to the ‘Internationalisation Code’ and ‘International Version ID’ components allowed by HL7. MSH-1 – field separator The field separator character will be ‘|’. Example: MSH|^~\&|DELPHIC... MSH-2 – encoding characters This field contains the separator characters for component, repeat and the escape character and respectively. We strongly recommend that this field contain ‘^~\&’. Please see the section above on separators. Example: MSH|^~\&|DELPHIC|MEDLAB|LABRESULT|... MSH-3 – sending application This field should be filled in with the name of the sending application. Since this message is usually sent from a laboratory, this normally contains the name of the laboratory application. If the laboratory application is not named, this field should contain the text ‘LABRESULT’; most messages use this value. Example: In this case the sending laboratory uses the Delphic Laboratory Results module: MSH|^~\&|DELPHIC|ediaccnt|LABRESULT|... MSH-4 – sending facility This field should be filled in with the EDI account name of the sending facility. This must be filled in correctly so that message acknowledgements can be correctly processed. This field should not be more than eight characters in length and should always be in lower case. Example: MSH|^~\&|DELPHIC|ediaccnt|EPISURV|...
hiso-10008-3-2017-notifiable-disease-messaging-implementation-guide-mar17.docx