You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The HL7 spec expects CR (ascii 13) characters to deliminate segments of an HL7 message, however certain vendors only deliminate thier lines with \n (ascii 10). Mirth should stay compatabile with these vendors by allowing the option to specify the end of segment encoding character.
The property "segmentEnd" has been added to the TCP connector. The LLP listener and sender panels now need a field to set this property on the connector. The format should be the same as the other protocol encoding properties.
Imported Comment. Original Details:
Author: geraldb
Created: 2006-09-21T07:58:32.000-0700
The HL7 spec expects CR (ascii 13) characters to deliminate segments of an HL7 message, however certain vendors only deliminate thier lines with \n (ascii 10). Mirth should stay compatabile with these vendors by allowing the option to specify the end of segment encoding character.
Imported Issue. Original Details:
Jira Issue Key: MIRTH-29
Reporter: chrisl
Created: 2006-09-12T14:05:54.000-0700
The text was updated successfully, but these errors were encountered: