Xlate’s gone blind!

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Xlate’s gone blind!

  • Creator
    Topic
  • #49285
    Gene Salay
    Participant

      I am trying to convert an ORU^R01 to an MDM.    The message coming in is HL7 2.4.   I’m converting it to 2.3.    In the testing tool, my 2.4 variant sees the message fine.   When I test the xlate, the only data it populates are direct assigns (copy with =something in the source)!!!   It’s like it can’t see the inbound message.   I’m on 5.3, w/AIX 5.2

      Gee those cars look small…  drat you pigeons get your own ledge!!

    Viewing 1 reply thread
    • Author
      Replies
      • #61376
        Russ Ross
        Participant

          Sounds like you are learning about what many of us preach, “avoid using bulkcopy”.

          If you want to do “wam bam thank you mam” and then leave someone behind unsatisfied perhaps it makes sense, but not if you are going to hang around.

          This is especialy true when converting a message from one version of HL7 to another.

          Bulkcopy only copies the items that have identical paths.

          If you are using bulkcopy and look at the field pathing in the IDE Xlate coming in and the field pathing in the IDE xlate going out and see they are not identical, then don’t expect bulkcopy to map them.

          Thanks to Jim kosloskey and some experience of my own I don’t readily embrace using bulkcopy anymore, so I would copy every field I want to come across individually.

          For me this typically adds an extra 2 days of work but I believe I get it back later on for more reasons than the one we are talking about.

          It also gives you good practice with doing iterations since you are likely to have repeating groups and segments.

          If you do decide to use bulkcopy then one way to trick bulkcopy is to modify one of the HL7 variants until the pathing matches.

          In some cases this might even require editing the variant file with a text editor because the IDE might be too smart to let you do just anything.

          A long time ago I used this approach to convert HL7 2.3 messages to HL7 2.2 for older systems.

          With my current experience I would definitely not use that approach in favor of the field by field copy.

          I understand their is a pathcopy which might be another alternative but I’ve never used pathcopy.

          Russ Ross
          RussRoss318@gmail.com

        • #61377
          Gene Salay
          Participant

            Thanks Russ.   I actually wasn’t doing a bulkcopy, but thanks for the wisdom.   I did have several pathcopies in there, but the problem turned out to be the message I was using in my ib variant.   I gave it a fancy name instead of what it would find in MSH-9.   And I had a problem with my iterate.    Looks good now.

            Pigeons can have their ledge back.

            BIG thanks to another party – not sure if you want rolling credits here, but you know who you are, and I appreciate the assistance.

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