copy of TS field changes time

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf copy of TS field changes time

  • Creator
    Topic
  • #54131
    Paul Bishop
    Participant

      Cloverleaf version 5.8.5

      AIX version 6.1

      I ran across an interesting situation that I’m scratching my head on.  When a copy (either by bulkcopy, pathcopy, or field copy) is done on a TS field and the data has the timezone of anything except 0500, it is changing the timezone to 0500 and adjusting the time accordingly.  The problem with this is that we are in the Central time zone (0600)  and the destination system does not recognize the time zone designation, so the timestamps are incorrect when filing into the EMR.

      Then, during our debugging tries of determining what is happening, we discovered that if you mark “Use Custom Time” on the DATECOPYOPT command, Post Proc commands will no longer work when copying from a TS type field to a TS type field.  Is this a bug or feature?

      Issuing the date command in the AIX system shows we are set for CDT:

      > Mon Mar 31 13:11:16 CDT 2014

      Where does Cloverleaf get its timezone information for when a TS field to TS field copy is being done?

      Has anybody else seen either of these issues (time changing/post proc not working)?

      Thanks for your input!

      Paul Bishop
      Carle Foundation Hospital
      Urbana, IL

    Viewing 5 reply threads
    • Author
      Replies
      • #80276
        Jim Kosloskey
        Participant

          Paul,

          If the precision (offset) is in the inbound TS then Clovelreaf will properly adjust to your time zone.

          If you do not want that adjustment, try using a Xlate pre proc to strip off the offest. The reult should be an unchanged date/time basis.

          The Xlate post proc cannot change anything. You could of course use a post Xlate route proc but that seems to be more work than necessary.

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

        • #80277
          Paul Bishop
          Participant

            not sure if I’m grasping what you’re saying.  Here is an example.  This OBR is from our lab system before any translate touches it:

            OBR|2|71388371-1^EPIC^1.2.840.114350^ISO|1-1^CARLE^2.16.840.1.113883.3.3013.25.19^ISO|50545-3^Bacterial susceptibility panel by MIC3^LN^MIC^Bacterial susceptibility panel by MIC3^L^2.40^NA^Bacterial susceptibility panel by MIC3|||201402111616-0600||||G|||||1871722868^DEWITT^KELLIE^^^PA^^90770^EPIC&1.2.840.114350&ISO^L^^^NPI^CARLE&1.2.840.114350.12&ISO^^^^^^^|^WPN^PH^^^815^8894241^^~^ORN^FX^^^815^8894035^^|||||20140331070200-0500|||F|634-6&Bacteria XXX Aerobe Cult&LN&RO&AEROBIC CULTURE, ROUTINE&L&&&AEROBIC CULTURE, ROUTINE^1|||71388371&EPIC&1.2.840.114350&ISO^1&CARLE&2.16.840.1.113883.3.3013.25.19&ISO

            This is the same OBR after doing a pathcopy on the segment:

            OBR|2|71388371-1^EPIC^1.2.840.114350^ISO|1-1^CARLE^2.16.840.1.113883.3.3013.25.19^ISO|50545-3^Bacterial susceptibility panel by MIC3^LN^MIC^Bacterial susceptibility panel by MIC3^L^2.40^NA^Bacterial susceptibility panel by MIC3|||201402111716-0500||||G|||||1871722868^DEWITT^KELLIE^^^PA^^90770^EPIC&1.2.840.114350&ISO^L^^^NPI^CARLE&1.2.840.114350.12&ISO^^^^^^^|^WPN^PH^^^815^8894241^^~^ORN^FX^^^815^8894035^^|||||20140331070200-0500|||F|634-6&Bacteria XXX Aerobe Cult&LN&RO&AEROBIC CULTURE, ROUTINE&L&&&AEROBIC CULTURE, ROUTINE^1|||71388371&EPIC&1.2.840.114350&ISO^1&CARLE&2.16.840.1.113883.3.3013.25.19&ISO

            what is causing the OBR-7 field to change the time zone and time?

            Paul Bishop
            Carle Foundation Hospital
            Urbana, IL

          • #80278
            Jim Kosloskey
            Participant

              Paul,

              Sorry I mis-read your post.

              It does appear Cloverleaf is not using the system TZ from the system.

              I duplicated it on our system AIX 6.x Clovelreaf 6.0 platform with the same result. We don’t have any TS data items with the offset so we have not experienced this.

              Everything I see indicates the system TZ should be used without having to do anything but it appears it is not.

              Unless someone else has some wisdom, this might be a support issue.

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

            • #80279
              Jim Kosloskey
              Participant

                Paul,

                If the receiving system does not need the offset you could use an xltp type proc to strip the offset from the inbound field with the COPY then the time won’t be changed.

                The above is a workaround and does not really address the issue.

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

              • #80280
                Kevin Kinnell
                Participant

                  Paul —

                  Is it possibly an issue with daylight savings time?  If AIX switched to CDT then -0500 would be correct with respect to UTC.

                  What happens if you send a message through with a TS containing -0500?

                • #80281
                  Bob Richardson
                  Participant

                    Greetings,

                    If you do not need to pass the time zone piece you could do an inline TCL

                    code with string range to pass only the first 12 characters here.

                    Like:

                    set xlateOutVals

                      0 11 ]]

                      And you try turning off date precision too in the Xlate itself by using DateCopyOpt (no precision).  We have 5.8.7.0 and there is an IDE setting for Xlate time precision that you can uncheck too.

                      Hope this doesn’t muddy up the waters!

                  Viewing 5 reply threads
                  • The forum ‘Cloverleaf’ is closed to new topics and replies.