2.4 standard states:
"2.9.48 TX - text data
String data meant for user display (on a terminal or printer). Such data would not necessarily be left jus-tified since leading spaces may contribute greatly to the clarity of the presentation to the user. "
Unless I've missed a config option or rule, escape() function in Escape.cs always trims leading and trailing spaces for type TX i.e. return result.ToString().Trim();
Perhaps it should be changed to only TrimEnd?
Example OBX...
Before...
OBX|23|TX|^Report Line 23|| Sample stored as serological investigations on samples taken within||||||C|||201607270920
After...
OBX|23|TX|^Report Line 23||Sample stored as serological investigations on samples taken within||||||C|||201607270920
The XMLParser works fine as it has KeepAsOriginalNodes property which the PipeParser does not have
2.4 standard states:
"2.9.48 TX - text data
String data meant for user display (on a terminal or printer). Such data would not necessarily be left jus-tified since leading spaces may contribute greatly to the clarity of the presentation to the user. "
Unless I've missed a config option or rule, escape() function in Escape.cs always trims leading and trailing spaces for type TX i.e. return result.ToString().Trim();
Perhaps it should be changed to only TrimEnd?
Example OBX...
Before...
OBX|23|TX|^Report Line 23|| Sample stored as serological investigations on samples taken within||||||C|||201607270920After...
OBX|23|TX|^Report Line 23||Sample stored as serological investigations on samples taken within||||||C|||201607270920The XMLParser works fine as it has KeepAsOriginalNodes property which the PipeParser does not have