Is there a way to change the standard component separator? #6320
Replies: 1 comment 3 replies
-
return message.replace(/\^/g,'~')Sorta gotta wonder why?
|
Beta Was this translation helpful? Give feedback.
-
|
Had a site claim a 3rd party vendor has problems with ^ separator(seems fishy) and they asked if we could replace it with ~. Pretty sure the answer is going to wind up being 'NO', but I got curious as to how it could be done. I appreciate your reply. |
Beta Was this translation helpful? Give feedback.
-
Yes it is fishy, but the HL7 standard is designed to support this. I remember that if you receive HL7 with non-standard separators that Mirth will automatically parse it. Are you receiving HL7, sending HL7, or both? @pacmano1 suggests an OK solution but I think there is a better way to support this in Mirth. It's HL7 renderer should inherently support parsing MSH.1 correctly. I searched for documentation: I searched the old forums, using Google because the Forum search is horrible I think this might be a solution https://forums.mirthproject.io/forum/mirth-connect/support/13329-having-issues-with-a-non-standard-hl7-delimiter -> See how Nick just changes the MSH.2 value? Internally Mirth is generating HL7 as XML. If MSH.2 is set with non-standard delimiters then when Mirth renders that XML to HL7 (LLP technically) it will use the separators defined in MSH.2 |
Beta Was this translation helpful? Give feedback.
-
|
I was just fixing the replace, lol. But I'd be on the call with the other side wondering if they really know what they are doing for a living. |
Beta Was this translation helpful? Give feedback.
-
Asking out of curiosity.
Standard separator is ^ IE FRESH^DOUG^E
Is there a way to change the ^ to ~ across the entire message?
I've tried message.replace(/^/g, '~'); in the preprocessor scripts but that has no change.
any help would be greatly appreciated
Beta Was this translation helpful? Give feedback.
All reactions