FRL to HL7 xlate – 5.6

I would check you HL7 variants.

Make sure that the EVN segement is defined the same on both.

It may be that simple.

I’m betting somewhere in the translation it copies MSH 9 to the EVN. But the EVN is not defined in your variant so it fails.

This is just a guess it could be something else but this is where I would start.

Well, first of all, the HL7 variants are the same.

Could there be a Tcl proc somewhere?

I would check the Pre & Post Procs on your Route and the TPS Outbound on your thread.

Nope…..no Tcl procs anywhere.  This ain’t my first rodeo. I’ve checked all the usual suspects and the only conclusion I can come up with is that Cloverleaf is doing something in the background to populate (or in the case of 5.6) or not populate the MSH.9 and EVN.1 based on the output record format defined under the “reconfigure” selection within the xlate.  Maybe someone with Quovadx can confirm this or not.  

Thanks…

Tom Rioux

Could there be a Tcl proc somewhere?

I would check the Pre & Post Procs on your Route and the TPS Outbound on your thread.

Nope…..no Tcl procs anywhere.  This ain’t my first rodeo. I’ve checked all the usual suspects and the only conclusion I can come up with is that Cloverleaf is doing something in the background to populate (or in the case of 5.6) or not populate the MSH.9 and EVN.1 based on the output record format defined under the “reconfigure” selection within the xlate.  Maybe someone with Quovadx can confirm this or not.  

Thanks…

Tom Rioux

I made a copy of the xlate and already have it down pretty simple.  I’m only doing some hard copies in the MSH segment (but not MSH.9) and one field in the PID segment.  It is still not populating the EVN.1 like it was in 5.2.  

Dazed and confuzed….