Cerner to CBord

Tim,

My guess is that this is something that is configurable within CBORD.  We have multiple interfaces with CBORD using the very same pdl but don’t have these issues.  Sounds like the vendor is wanting you to do his work for him.

Tom Rioux

The sequence is the end of the MLP wrapper that surrounds the HL7 message. The entire piece is .

At the end of each segment you will have a . The last segment of the message will also have a indicating the end of the message. Then the whole thing is surrounded by the MLP wrapper.

We have an ADT interface to CBORD and what I saw on your original post did not look right to me so I did a TCP/IP trace to confirm what I suspect is the case were I work.

I immediately got suspicous when you said the message ended in

0D 0A + encapsulation of 1C 0D

The 0A (new line character) is an extra character that often appears on a windows platform but is incorrect according to my understanding and I know from experience that spurious new line characters cause some interfaces a problem.

The HL7 standard I believe says to terminate each segment with 0D (carriage return character) but the 0A (new line character) is spurious and undesirable in a standard real-time mlp-pdl interface according to what I believe.

What I believe to be correct is as follows

HL7 message with segments terminated with carriage return character (0D) and no new line character (0A)

Personally I would consider what you described

1B HL7_message 0D 0A 1C 0D

to be inncorrect and I would make it to be

1B HL7_message 0D 1C 0D

As far as getting rid of the spurious 0A (new line character) I would first check if it is coming that way from the source and correct that.

Also this is not the first time others have had a similar issues with spurious and undesirable new line characters.

Seems like I remember posts about each segment being terminated with a newline character and how to get rid of them.

I believe if you search clovertech you can find some of them but here is one to get you started that I replied to that illustrates how to use our TPS proc called tps_regsub_all:

<a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=1663&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1663

When transmitting an Hl7 message in newline format, the indicates the end of the message. You don’t see this character in SMAT files because the messages are indexed. In newline-terminated files of messages, the is the end of message indicator. In BLE (binary length encoded) format, the message begins with a number indicating the character count of the message and no terminator character is necessary.

An HL7 message can be thought of as a single line of text. As far as platform-specific line terminations go,

    DOS/Windows uses

    Unix uses

    Apple/Mac uses

Setting an FTP program to ASCII/Text mode, rather than Binary, converts line terminations so they are appropriate for the destination platform.  HL7 messages should be moved as binary. If you move a message file from DOS to Unix in text mode, the FTP routine will convert all the segment terminators to , and the engine will read each segment as a separate message..