|
Getting Strange Sequences Like \F\ in MSH Type FieldsThis is quite a common problem that occurs in two typical instances:
An example of the first problem would be an Message Identity like this: ![]() This results in Field 9 of the MSH Segment being generated as follows: |ADT^A01\F\A04\F\A08|. Chameleon is using the HL7 escaping convention to translate the | characters to \F\ characters. Testing the HL7 Escaping Convention
To test the HL7 escaping convention:
![]() Testing the HL7 Escaping Convention You will immediately notice that the message identity appears as follows: |ADT^A01\F\A04\F\A08|. The solution is to use a message definition file intended for generating messages, not message parsing. To fix this problem, you would just need to ensure that your Message Identity is set up so that each message identifier has one value each. Regular expressions should not be used to identify messages. Using the above example it would be good to pick ADT and one of the following: A01, A04 or A08. ![]() Fixed Message ID |