Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

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

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

HL7 Component Seperator issue

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

  • HL7 Component Seperator issue

    Mirth Version: 1.6.2750

    Hi All,

    When I run the below message in Mirth, it does not pick up the Component Seperator '_' (in encoding characters) from the message. Instead Mirth uses default Component Seperator '^' to parse the message. As a result Patient Name like:
    First Name = Test
    Last Name = Patient

    is parsed as First Name = Blank
    Last Name = Test_Patient

    Is there a way I can over come this. This is very crucial for us as most of the messages we receive are heavily customized and use varying 'Encoding Characters'.

    Thank you,
    Ali

    Message:
    MSH!_~\?!XXX!TTT!!!200805220317!!ADT_A01!CHPFADIT! P!2.3
    EVN!A01!200805211438!!!TXTADT
    PID!!!003237138!!TEST_PATIENT!HARVELYN!19521028!F! GARDNER!7!!!!!!M!!000035147321!
    PV1!!IA!EDIP_EDIP_AA__D!X!!!999999_DOC_TEST_!!!NUR !!N!!EO!!!!S!!R!!!!!!!!!!!!!!!!!!!!!!!200805211438

  • #2
    Re:HL7 Component Seperator issue

    Hi All,

    Has anybody come across this problem ? Can somebody help me out here!

    Thanks,
    ali

    Comment


    • #3
      Re:HL7 Component Seperator issue

      Hrmmm.

      Mirth *should be* able to cope with this as its part of the HL7 2.3 spec.

      Are the messages consistent enough that you could do a string substitution and convert it back to the normal characters???

      If so put something like this in your preprocessor:

      Code:
      message = message.replace("!", "|"«»);
      You should also be able to do some poking around and find the encoding chars first then sub in the standard ones.
      Jon Bartels

      Zen is hiring!!!!
      http://consultzen.com/careers/
      Talented healthcare IT professionals wanted. Engineers to sales to management.
      Good benefits, great working environment, genuinely interesting work.

      Comment


      • #4
        Re:HL7 Component Seperator issue

        Please try the latest version of Mirth (1.7.1). This issue was fixed around 1.7.
        Jacob Brauer
        Director, Software Development
        NextGen Healthcare

        sigpic

        Comment


        • #5
          Re:HL7 Component Seperator issue

          Jbartels & Jacobb,

          Thank you for your response!

          I will try the new Mirth (1.7.1)

          Post edited by: mac_3785, at: 06/11/2008 23:25

          Post edited by: mac_3785, at: 06/11/2008 23:27

          Comment


          • #6
            Re:HL7 Component Seperator issue

            Gentlemen Thank you very much, this works as expected in Mirth 1.7!

            Comment

            Working...
            X