Announcement

Collapse

NextGen Connect 3.10.1 Released!

NextGen (Mirth) Connect 3.10.1 is now available as an appliance update and on our GitHub page. This release contains bug fixes. See the release notes for the list of fixes.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

messages containg multiple PID, PV1, etc...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • messages containg multiple PID, PV1, etc...

    I have a question regarding the format used in composing messages with multple segments with the same name such as ADT-A17 and ADT-A37. I thought that the labels were the same, but when sent to mirth, i get this:

    ERROR-301: Transformer conversion error
    ERROR MESSAGE: Error adapting message

    what i sent (simply as a test) was:

    MSH|^~\\&|Mirth|1|||2006044535||ADT^A37|603340|D|2 .3.1
    EVN|A04|20060404090742
    PID|1|800888^^^Mirth^PN|999945682^^^AccMgr^MR^1||T EST^PATIENT MF||19570414|M||W|21 PALM MANOR^^EAST SYRACUSE^NY^130570000^^M|31|||E|M|||6635130^^^Mirt h^VN^1|000987655|||2|||||NOT A VETERAN
    PV1|1|E|ED^^^1|1|||1281^MARKHAM^JOSEPH^^^^^^AccMgr ^^^^CI|1281^LANG^JOE^^^^^^Mirth^^^^CI||ED||||7|S|| |62|6635130^^^AccMgr^VN^1|865^SP KOPP|||||||||||||||||||1||A||||20060404090500
    PID|2|11111^^^Mirth^PN|999945682^^^AccMgr^MR^1||TE ST^PATIENT MF||19570414|M||W|21 PALM MANOR^^EAST SYRACUSE^NY^130570000^^M|31|||E|M|||6635130^^^Mirt h^VN^1|000987655|||2|||||NOT A VETERAN
    PV1|2|E|ED^^^1|1|||1281^MARKHAM^JOSEPH^^^^^^AccMgr ^^^^CI|1281^LANG^JOE^^^^^^Mirth^^^^CI||ED||||7|S|| |62|6635130^^^AccMgr^VN^1|865^SP KOPP|||||||||||||||||||1||A||||20060404090500


    However, when i checked the raw message tab in mirth, it had the abouve message plus an added three lines attached to the bottom that were not in the message i sent:

    PID22|2|11111^Mirth^PN|999945682^AccMgr^MR^1||TEST ^PATIENT MF||19570414|M||W|21 PALM MANOR^EAST SYRACUSE^NY^130570000^M|31|||E|M|||6635130|0009876 55|||2|||||NOT A VETERAN
    PD122
    PV122|2|E|ED^1|1|||1281^MARKHAM^JOSEPH^AccMgr^CI|1 281^LANG^JOE^Mirth^CI||ED||||7|S|||62|6635130^AccM gr^VN^1|865^SP KOPP|||||||||||||||||||1||A||||20060404090500


    I'm pretty sure this is a simple message formatting problem, but i'm new to HL7 and mirth so any help would be greatly appreciated. A sample of a correct ADT-A37 or A17 would help alot as well.
    ~Patrick

  • #2
    Re:messages containg multiple PID, PV1, etc...

    sorry about the formatting on the message boards, the lines are to big to fit on one line of the boards

    Comment


    • #3
      Re:messages containg multiple PID, PV1, etc...

      You can use the "code" tags around your HL7 so the formatting is preserved. Open bracket, code, close bracket. Then at the end, open bracket, forward slash,, code, close bracket.

      As far as your issue in Mirth, what version are you using? What connector are you using? Can you post your channel?

      Thanks!
      Chris Lang

      Comment


      • #4
        Re:messages containg multiple PID, PV1, etc...

        Do you think you could just post a simple, working ADT-A17 message that i can compare to mine to see if there are any differences. Thanx
        ~Patrick

        Comment


        • #5
          Re:messages containg multiple PID, PV1, etc...

          i have attached the xml of my channel hopefully this helps client_to_server.xml (7894 bytes)

          Comment


          • #6
            Re:messages containg multiple PID, PV1, etc...

            What system is sending the messages to Mirth? The issue you are seeing looks like a problem on the sending server side.
            Chris Lang

            Comment


            • #7
              Re:messages containg multiple PID, PV1, etc...

              Its a hl7 sending client I created myself. I don't think that is the issue though, because the message raw message source comes into Mirth fine, its in the destination message that the message becomes corrupted. That seems to indicate something inside of Mirth. All that my client does is read the message to a stream and sends it to Mirth.

              Post edited by: pjzuber, at: 06/04/2007 06:22

              Comment


              • #8
                Re:messages containg multiple PID, PV1, etc...

                Go to each transformer in both the source and destination. On both the incoming and outgoing data tabs, hit properties. Turn off "use strict parser". Redeploy.
                Chris Lang

                Comment


                • #9
                  Re:messages containg multiple PID, PV1, etc...

                  Excellent!!! Exactly what i was looking for. Thanx alot!!!!
                  ~Patrick

                  Comment


                  • #10
                    Re:messages containg multiple PID, PV1, etc...

                    FYI - the non-strict parser is the default parser in 1.5
                    Chris Lang

                    Comment

                    Working...
                    X