xlate issue

  • Creator
    Topic
  • #51554
    Andrew Deters
    Participant

      This is my attempt at an xlate to split P03’s into multiple messages for each FT1 segment.  I think sometimes you just have to step away from a problem to figure out what is wrong…..can anyone help figure out why the string MR wouldn’t populate the right way.  Everything else seems to be working.  Please see the attachment.

    Viewing 4 reply threads
    • Author
      Replies
      • #70756
        Tom Rioux
        Participant

          When you say it “wouldn’t populate the right way”, what exactly do you mean?   Please post examples of your output so far.

          Thanks….

          Tom

        • #70757
          Andrew Deters
          Participant

            I have a test message with 2 FT1 segments.  I want the xlate to send a message for each FT1 segment.  The more i look at the test results, i have bigger problems than not getting MR in that part of the message.  When i run this through the testing tool, i get 2 messages.  The first message has the first FT1 segment.  The second message in the testing tool is the orignal message with both FT1 segments.  It looks like the test message is getting sent in it’s entirety after the first FT1 segment is sent with both FT1 segments.

            The PID segment field 3 comes out with

            |001234567^^^PMaCnk|  

            What i want to see is

            |001234567^^^PMaCnk^MR|

          • #70758
            Robert Milfajt
            Participant

              Your first problem, FT1 segments in resulting message is easy. Change PATHCOPY statment to:

              Code:

              PATCHCOPY 0(0).FT1(%s1)->0(0).FT1(0)

              I would check the outbound HL7 format to see if PID.3 has the right format.  You may need to modify something there.

              Hope this helps,

              Robert Milfajt
              Northwestern Medicine
              Chicago, IL

            • #70759
              Andrew Deters
              Participant

                taking the %s1 out of the FT1 destination worked.  

                I’ll take a look at the format.

                Here is the original message.

                MSH|^~&|Practice Partner|123 Family Care Anywhere|PMS|PMS Client|20100204121919||DFT^P03|0000|D^T|2.4|1^MPID|1||00001234567||SMITH^PATIENT||19000101|F|||1234 RT 123^^BFE^EG^12345^USA||1234561212|||S|||1234567890^MPV1|1||||||||||||||||||B1900110901392^MFT1|1|0000||19001209000000|20100204121919|AA|0000^VITAMIN B12 INJEC|||1|||||||||281.1^OTH VITAMIN B12 DEFICIENCY ANEMIA^ICD9|^Smith^John^S^DO^^^L~111111^Smith^John^S^DO^^^U|||||J0000^VITAMIN B12 INJECTION^CPT^J0000^VITAMIN B12 INJECTION^CPT|^MFT1|2|0000||1900|20100204121919|AA|0000^ROUTINE VENIPUNCT|||1|||||||||281.1^OTH VITAMIN B12 DEFICIENCY ANEMIA^ICD9|^Smith^John^S^DO^^^L~111111^Smith^John^S^DO^^^U|||||00000^COLLJ VEN BLD VNPNXR^CPT^00000^COLLJ VEN BLD VNPNXR^CPT|^MGT1|1||SMITH^PATIENT||1234 RT 123^^BFE^EG^12345^USA|1234561212||||||1234567890^MIN1|1||11111|123 ASOP HEALTHCARE PLAN|PO BOX 000^^Anywhere^EG^11111||111111|111111||||19000101||||SMITH^PATIENT||||||1||||||||||||||11111111111

                and here is the output of the testing tool…

                0(0).MSH(0).00001(0).[0].[0]

              • #70760
                Andrew Deters
                Participant

                  yeah it was the length of that part of the PID segment.  I extended it and it works now.

                  Thanks.

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