GMT offset in 5.4

[Daniel Lee]

I know this is a rookie question but I’ve lived with it for a long time and want to get to the bottom of it.

Whenever I do a BULKCOPY in my Xlate the date/time fields always come out of the Xlate with a GMT offset even when I sent them into the Xlate as YYYYMMDD.  I’ve been dealing with this by setting the outbound variant to only be 8 characters long but it’s a pain to have to touch every date when I just want the BULKCOPY to leave the dern thing alone and pass it along untouched to the outbound variant.

Why is the Xlate doing this and how do I get around it?  I shouldn’t need a DATECOPY for every date in the HL7 message should I?

What finally drove me to the breaking point is we are converting from 3.8.1P to 5.4 and now not only does 5.4 put a GMT offset on all the dates but it also throws in the system time on the date/time field if the time comes into the Xlate blank.

Topic

[Jim Kosloskey]

Dan,

I don’t know if this will answer your question but you only need to set DATECOPYOPT once if you want precision off for ALL dates (I usually do this first in the Xlate if the receiving system has indicated they do not want precision for ANY dates).

If you have some dates which should have precision and some that don’t then I usually set and reset DATECOPY at each COPY, etc.

BULKCOPY may add some differences to the above, I rarely use BULKCOPY.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Daniel Lee]

Thanks Jim.  That’s the answer I was looking.   😀

[Author]

Replies