- This topic has 6 replies, 3 voices, and was last updated 4 years, 8 months ago by
.
-
Topic
-
-
Replies
-
-
-
-
If you get a warning in a translation it is most likely a segment that is not supported by the version/variant you are using. These warnings will not make the message go into the error database; there will only be a mention of the warning in the logging of the process. And of course you can’t use/process the segments in question.
What kind of warning do you get? Please give an example.
Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
-
I modified the route to treat translations as warnings and some things are showing up in the error db now. I do notice that in allot of these errors show a bulkcopy failure which would cause an empty message which could be why I can’t find the translated message. However, I can’t seem to find the original message in order to review.
I also created a custom message type but still receive an error for the type in the MSH. For example, I received a error that ADT_A11 does not contain the ROL segment even though I set the format to the new message type. Will Cloverleaf look at what definition to use based on the MSH|9 field instead of what’s defined in the message format
[msg :RecP:ERR /0:prod_adt_xlate:02/03/2020 11:52:53] [0.0.463688] The # 160 segment encountered ‘DG1’ is out of order when parsing hl7 (2.4 meditech) for message type ‘ADT_A03_ADT_A03’ during the translation(edie_ob.xlt). Segment ignored.
[xlt :xlat:ERR /0:prod_adt_xlate:02/03/2020 11:52:53] [0.0.463688] Xlate ‘edie_ob.xlt’ failed: Bulkcopy failure: The # 160 segment encountered ‘DG1’ is out of order when parsing hl7 (2.4 meditech) for message type ‘ADT_A03_ADT_A03’ during the translation(edie_ob.xlt). Segment ignored.
[xlt :rout:ERR /0:prod_adt_xlate:02/03/2020 11:52:53] Xlate error in route detail ‘XLATE edie_ob.xlt’ under Trxid ‘_HCI_static_route_’ to Dest ‘edie_ob'[msg :RecP:ERR /0:prod_adt_xlate:02/03/2020 11:53:03] [0.0.463794] The # 72 segment encountered ‘DG1’ is out of order when parsing hl7 (2.4 meditech) for message type ‘ADT_A03_ADT_A03’ during the translation(edie_ob.xlt). Segment ignored.
[xlt :xlat:ERR /0:prod_adt_xlate:02/03/2020 11:53:03] [0.0.463794] Xlate ‘edie_ob.xlt’ failed: Bulkcopy failure: The # 72 segment encountered ‘DG1’ is out of order when parsing hl7 (2.4 meditech) for message type ‘ADT_A03_ADT_A03’ during the translation(edie_ob.xlt). Segment ignored.
-
I updated the HL7 configuration/variant for each type of ADT message that we receive from our EMR and I’m now receiving very few errors/warnings. However, I still need to be able to review the messages that are receiving the error / warning. I do have the inbound thread set to save incoming messages.
-
In the translation you can specify which variant to take and even the message you want to translate. However after translation, Cloverleaf will verify the resulting message based on MSH-9 (so ADT^A11) against this message in the specified variant.
If after your translation ADT^A11 still contains a ROL segment, you can do 2 things:
1 – alter your Xlate so ROL segment is removed if the message is ADT^A11.
2 – change message ADT^A11 in your specified variant and remove the ROL segment.Option 2 is not according to HL7 rules, so better stick with option 1.
Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
-
-
- You must be logged in to reply to this topic.
