Open rbeckman-nextgen opened 4 years ago
What exactly does supporting this entail? Currently in 2.2.1 adding a fifth encoding character to MSH.2 messes up the rest of the message due to our deserialization. However, that has been fixed in 2.2.2 and 3.0 with MIRTH-2353.
Imported Comment. Original Details: Author: narupley Created: 2013-05-09T07:54:54.000-0700
See forum thread http://www.mirthcorp.com/community/forums/showthread.php?t=8749
Imported Issue. Original Details: Jira Issue Key: MIRTH-2547 Reporter: nicovn Created: 2013-05-09T01:28:26.000-0700