Some clients of mine hand edited a HL7 result message to fix bad OBX-5
values. I'm not sure why but they padded the value with spaces.
OBX Line:
OBX|5|NM|2231^Sodium||140 |mEq/L|133-146||||F|||20160706073500|ML||||||||||
Because this was a NM type it threw a exception, but how can I attempt to
trim these values prior to parsing?
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
