Multiple OBX Segments in ORM For Xlate

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Multiple OBX Segments in ORM For Xlate

  • Creator
    Topic
  • #52243
    Anonymous

      I’m building an Xlate for ORM messages that have multiple OBX segments.  I can’t use the BulkCopy for these messages (which the multiple OBX segments show up fine for), but need to use PATHCOPY.  The problem I’m running into is that I can only get one OBX segment to come out.  What am I missing?  Thanks in advance for the help.

    Viewing 7 reply threads
    • Author
      Replies
      • #73535
        Charlie Bursell
        Participant

          Post the PATHCOPY statement you are using.  It should look something like:

          1(0).1(0).OBX.  DO NOT put (0) or anything after the OBX

        • #73536
          Jim Kosloskey
          Participant

            Phil,

            Also make sure your basis is set correctly in the ITERATE (are you using an ITERATE?).

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

          • #73537
            Anonymous

              I am using the ITERATE Action and have the following set:

              Action:  ITERATE

              Type:  Segment

              Basis: 2(0).1(0).1(0).0(0).OBX

              Variable:  %s1

              Nested in the ITERATE is the PATHCOPY with the following:

              Source:  2(0).1(0).1(0).0(0).OBX(%s1)

              Destination:  2(0).1(0).1(0).0(0).OBX(%s1)

            • #73538
              Jim Kosloskey
              Participant

                Phil,

                Double check this:

                Typically the OBX segment in an Order Message is part of a repeating Group it is not a repeating segment.

                One way to check where the repetition goes is to use the HL/7 tester for the variant with a message that has repeating OBX, turn the display level up and check the address path to see where the repetition happens in the path for the second and latere OBX.

                Another method is to use the Inbound tree to set the basis.

                I suspect your basis should be at the group level.

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

              • #73539
                Ryan Spires
                Participant

                  One thing i have found helpful is to run the data through the testing tool with your inbound variant defined (hl7)  The hl7 testing tool will show you exactly what path you should be iterating against.  (group vs segment) based on which numbers increase in the path detail.

                • #73540
                  Anonymous

                    I ran this through test and I’ve copied what I see for the two OBX segments.

                    2(0).1(0).1(0).0(0).OBX(0)  :  >|1|ST|LDVANT^Last Dose Date|1|01/31/2011<

                    2(0).1(0).1(0).0(1).OBX(0)  :  >|2|ST|LTVANT^Time of Last Dose|1|0000<

                    So I changed my ITERATE TO:

                    Type:  group

                    Basis:  2(0).1(0).1(0).0(0).OBX(%g1)

                    Variable:  %g1

                    But this errors out with:

                    Unable to get iteration basis address ‘2(0).1(0).1(0).0(0).OBX(%g1)’.

                  • #73541
                    Jim Kosloskey
                    Participant

                      Phil,

                      Your basis is still pointing to the segment.

                      But you are specifying a group iteration.

                      Use this 2(0).1(0).1(0).0 as your basis.

                      Then email me and off line I will explian how you can get comfortable with the basis settings.

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

                    • #73542
                      Anonymous

                        Jim, Thanks a million for your time!  It is most appreciated!  My Xlate is working like a charm now!

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