Clovertech

TCL vs XLATE

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › TCL vs XLATE

  • Creator
    Topic
  • June 3, 2009 at 4:03 pm #50934
    Tim Faul
    Participant

      We’re running Cloverleaf 5.5 on HPUX and are in the process of converting some of our tcl scripts into Xlates.

      The only issue I’m running into is that the Xlate strips off empty fields and subfields from the end of segments and fields.

      So far it hasn’t caused any issues, but it is making it impossible to get the before and after to be identical.

      Any thoughts on why it’s doing that, or how to change that?

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • June 3, 2009 at 4:25 pm #68071
        Jim Kosloskey
        Participant

          Tim,

          Xlate is fololowing the standard. Apparently your Tcl code is not.

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

        • June 3, 2009 at 4:52 pm #68072
          Tim Faul
          Participant

            Jim Kosloskey wrote:

            Tim,

            Xlate is fololowing the standard. Apparently your Tcl code is not.

            The interesting part there is that it’s happening where I’m not coding it to make any changes to the message. I’ve converted a filter TCL into an Xlate.

            The TCL checked the patient type and continues or kills the messages, and I setup the Xlate to check the patient type and either bulk copy or suppress the message.

            Here’s an example from out test system

            First message is with the Tcl and the second is with the Xlate

            MSH|^~&||L||L|200906030900|44|ADT^A04|70491076|D|2.2|70491076||AL||

            EVN|A04|200906030900||

            PID||00968416|00831268^^^L|31070^L219670|SIMPSON^HOMER^^JR||19500627|M||1|41 SHORT LANE^^BETHLEHEM^PA^18015^^C||(610)865-0000||ENGLISH^E^|D|^|0915400004^^^L|555-99-7410|

            PD1||||529^SCOBLIONKO^DAVID^P

            NK1|1|SIMPSON^RALPH|H^^|96 OLD LANE^^BATH^PA^18014^|

            PV1||E|ED^^^L^^^||||996^UNKNOWN^DOCTOR|||OUT|||||||996^UNKNOWN^DOCTOR|LQR^^L|0915400004^^^L|0|||||||||||||||||||L|||||200906030859||| 0.00||

            AL1|||^|||

            DG1|0|I9|789.00|ABDMNAL PAIN UNSPCF SITE||ADMITTING||||||||

            DG1|99|I9|789.00|ABDMNAL PAIN UNSPCF SITE||WORKING||||||||

            GT1|1|31070|SIMPSON^HOMER^^JR||41 SHORT LANE^^BETHLEHEM^PA^18015^^C|(610)865-0000||19500627|M||S|555-99-7410|||1|AT&T WIRLESS^|45 PHONE STREET^^ALLENTOWN^PA^18102^^|||5

            IN1|1|||||||||||||||^^|||||||||||||||||||||||||||||

            ZCA|||^^^

            ZCV|||ART||||LQR|0

            MSH|^~&||L||L|200906030900|44|ADT^A04|70491076|D|2.2|70491076||AL

            EVN|A04|200906030900

            PID||00968416|00831268^^^L|31070^L219670|SIMPSON^HOMER^^JR||19500627|M||1|41 SHORT LANE^^BETHLEHEM^PA^18015^^C||(610)865-0000||ENGLISH^E|D||0915400004^^^L|555-99-7410

            PD1||||529^SCOBLIONKO^DAVID^P

            NK1|1|SIMPSON^RALPH|H|96 OLD LANE^^BATH^PA^18014

            PV1||E|ED^^^L||||996^UNKNOWN^DOCTOR|||OUT|||||||996^UNKNOWN^DOCTOR|LQR^^L|0915400004^^^L|0|||||||||||||||||||L|||||200906030859||| 0.00

            DG1|0|I9|789.00|ABDMNAL PAIN UNSPCF SITE||ADMITTING

            DG1|99|I9|789.00|ABDMNAL PAIN UNSPCF SITE||WORKING

            GT1|1|31070|SIMPSON^HOMER^^JR||41 SHORT LANE^^BETHLEHEM^PA^18015^^C|(610)865-0000||19500627|M||S|555-99-7410|||1|AT&T WIRLESS|45 PHONE STREET^^ALLENTOWN^PA^18102|||5

            IN1|1

            ZCV|||ART||||LQR|0

          • June 3, 2009 at 6:11 pm #68073
            Tom Rioux
            Participant

              Tim,

              An xlate is going to be built based on an HL7 standard.   It will take into accocunt any segments that are optional or any optional empty fields at the end of the segment.  That is one reason why you don’t see the AL1 message in your xlated message.  It is probably defined as an optional segment in the HL7 variant you defined for the xlate. (see “reconfigure” under the “File” selection in your xlate).  This would also be the reason why you don’t see the empty fields at the end of the segments.

              Your Tcl code probably isn’t taking into account any particular HL7 variant and such is simply sending out whatever you dictate in the code.  It is taking the message in, making the changes you request, and then sending the same yet updated message out.  Thus it will leave any optional segments or fields in the message.

              Hope this helps…

              Tom

            • June 3, 2009 at 6:39 pm #68074
              Tim Faul
              Participant

                Thomas Rioux wrote:

                Tim,

                An xlate is going to be built based on an HL7 standard.

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