Out of Order warning message

[Vinita Dutta]

I am have to convert an A31 (Allergy message) to an A60 message and keep getting out of order warning messages. Variant looks fine.

Inbound A31 MESSAGE

MSH|^~&||SGR||11|201101131237||ADT^A31|Q396316593T400147275|T|2.2

EVN|A31|20110113123730

PID|1|106011223|02000568^^^SGR||CVTSTING^LALLIE||19790101|F||WHH|CA||||ENG|||82000972|||||||0

PV1|1|O|EDT||||56811^Kobernick^Marc^^MD|||MED||||HMH|||56811^Kobernick^Marc^^MD|OPE||S|||||||||||||||||||SGR|||||201012160855

AL1|1|MA|^NKA

ZAL|ADD||1316470|1316470|Allergy|Active||||||^Abuid^Lorelai^^^^^^^Personnel|0

AL1|2|MA|^aspirin

ZAL|SNAPSHOT|20110113123721|1316469|1198470|Allergy|Canceled|^Rash^1241||||20110113123720|^Abuid^Lorelai^^^^^^^Personnel|0

Outbound A60 message after translation

[0:TEST] [mid:0x3000053c] The # 3 segment encountered ‘MSH’ is out of order for message type ‘ADT_A60’.  Segment ignored.

[0:TEST] [mid:0x3000053c] The # 4 segment encountered ‘EVN’ is out of order for message type ‘ADT_A60’.  Segment ignored.

[0:TEST] [mid:0x3000053c] The # 5 segment encountered ‘PID’ is out of order for message type ‘ADT_A60’.  Segment ignored.

0(0).MSH(0)  :  >|^~&|SHC_HNAM|SGR|dbM|11|201101131237||ADT^A60|Q396316591T400147273|T|2.4< 0(0).EVN(0)  :  >|A60|20110113123721||||20110113123721< 0(0).PID(0)  :  >|1|106011223|106011223^^^SHC^MR~02000568^^^SGR^MR||CVTSTING^LALLIE||19790101|F||WHH|CA||||ENG|||82000972|||||||0< 0(0).IAM(0)  :  >|1|MA|^aspirin|||UPDATE|1198470||^Rash^1241||||||||Canceled|^Abuid^Lorelai^^^^^^^Personnel< MESSAGE 2 [0:TEST] [mid:0x3000073c] The # 3 segment encountered ‘MSH’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 4 segment encountered ‘EVN’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 5 segment encountered ‘PID’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 7 segment encountered ‘MSH’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 8 segment encountered ‘EVN’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 9 segment encountered ‘PID’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 11 segment encountered ‘MSH’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 12 segment encountered ‘EVN’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 13 segment encountered ‘PID’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 15 segment encountered ‘MSH’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 16 segment encountered ‘EVN’ is out of order for message type ‘ADT_A60’.  Segment ignored. [0:TEST] [mid:0x3000073c] The # 17 segment encountered ‘PID’ is out of order for message type ‘ADT_A60’.  Segment ignored. 0(0).MSH(0)  :  >|^~&|SHC_HNAM|SCV|dbM|6|201101131301||ADT^A60|Q396318594T400149280|T|2.4< 0(0).EVN(0)  :  >|A60|20110113130136||||20110113130136< 0(0).PID(0)  :  >|1|106011197|106011197^^^SHC^MR~00581005^^^SCV^MR||SCV^DESIREEMOM||19780905|F||WHH|CA||||ENG|||61045063|||||||0< 0(0).IAM(0)  :  >|1|MA|^Peanuts|Severe|anaphylaxis|ADD|1324469||^anaphylaxis||||||||Active|^Baltazar^Desiree^^^^^^^Personnel< 0(0).IAM(1)  :  >|2|MA|^clarithromycin|Medium|anaphylaxis|SNAPSHOT|1320469||369546013^Hives^673967||20110113125625||||||Canceled|^Baltazar^Desiree^^^^^^^Personnel< 0(0).IAM(2)  :  >|3||60^shellfish|Medium|anaphylaxis|SNAPSHOT|1318470||369546013^Hives^673967||20110113125839||||||Active|^Baltazar^Desiree^^^^^^^Personnel< 0(0).IAM(3)  :  >|4|MA|^NKA||anaphylaxis|SNAPSHOT|1224469||||20110113124625||||||Canceled|^Baltazar^Desiree^^^^^^^Personnel<

Topic

[Vince Angulo]

Double-check your translation in ‘Reconfigure’ to make sure the IB message type is A31, and OB is A60.  The log makes it look like they’re both set to A60.

[Vinita Dutta]

I is set-up to IB – A31, OB A60

[Chris Williams]

Cloverleaf is unable to tell where one message ends, and the next one begins.

Look to your inbound. Are there any procs involved, or is all the work done in the Xlate? Turn up the EO Config and look in the process log to see what characters are being sent.

What protocol are you using on your inbound thread? Is this a tcp/ip connection? Are using the mlp_tcp.pdl?

Are you pulling these messages from a file? Do you have line-feeds terminating each message?

Lots of places to look, but here are a few places to start.

Chris

[Author]

Replies