Hex characters in messages

[Anonymous]

Hi All,

Sorry, I know this topic has been beaten a few times…. but, I’ve got a file that my engine is going to read from a FILESET/FTP Local (Oldest) protocol. It contains multiple HL7 messages.  The characters at the beginning of the message are x0bMSH, and then each MSH is proceded by the following characters, x0dx1cx0dx0bMSH. The message ends with x0dx1c. If I pick HL7 or new line terminated, nothing is read in. If I pick single message, the entire message is read into the engine. I do have the TRXID set to the HL7 variant I am using. Do I need a startup proc to read in the entire message and replace the x0dx1cx0dx0bMSH with LF’s?  🙄

Thanks in advance… Mary.

Topic

[Robert Kersemakers]

It looks like your messages are wrapped by MLP stop/start-characters. Quoting from the mlp_tcp.pdl:

Code:

/* This driver manages the transmission of messages using the HL7 defined
* MLP protocol.  Each message is bounded by a start character <0xb>
* and a stop string <0x1c><0xd>.
*
* The phrase basic-msg recognizes this message format.  Once recognized,
* the message data will be available from the ‘data’ field.
*/

So try reading these messages via tcp/ip by using the mlp-pdl. Or make sure the stop/start characters are removed when the messages are send by file.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Anonymous]

I chose to make the inbound interface a realtime feed set at a certain time each day. So now I do not have to manipulate the PDL characters.

Thanks for all your suggestions! Mary.

[Author]

Replies