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

Special characters encoding

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

  • Special characters encoding

    Hello,

    I transformed all special characters :
    http://www.neotool.com/blog/2007/09/...or-characters/

    Here is my HL7 message :
    MSH|^~&|TEST|1|TEST|TEST|20080320151102||ORU^R01|M 20080320151102|P|2.3|||AL|||8859/1
    OBR|1|145613|145613|TST^Test^4
    EVN|R01
    OBX||TX|^SR Text||<>'" [backslash]F[backslash] [backslash]S[backslash] [backslash]T[backslash] [backslash]R[backslash] [backslash]E[backslash]||||||F
    PID|1|25425|25425||TEST^Toto^^^^^L| |19800201|M||| ^^^^ ^ ||__________||||||
    PV1|1||||||||||||||||||

    I received it with DCM4CHEE , but I see [<>'" F S T R E] instead of special characters.

    Am I missing something about HL7 ?

    Post edited by: magikbanana, at: 09/11/2008 09:00

    Post edited by: magikbanana, at: 09/11/2008 09:01

  • #2
    Re:Special characters encoding

    Please, if someone already did this to say if it is working.

    Thanks !

    Comment


    • #3
      Re:Special characters encoding

      Have you tried to put a preprocessor like:
      --
      return urlencode(message);
      --

      To escape all the special characters ?

      Comment


      • #4
        Re:Special characters encoding

        Hello,

        I replaced 'return message' with 'return urlencode(message)' in global script/preprocessor but I got an error.

        Was it the right place to put this command ?

        Thanks

        Comment


        • #5
          Re:Special characters encoding

          Sorry, I've found that the function seems to be accessible from a destination, and it's called

          ${encoder.encode()}

          So, I don't know the exact way to put this into a preprocessor. Alternatively, you can try the: FileUtil.encode(data) to get the BASE64 representation of the message and the parser will not raise exceptions ...



          Hope that helps

          Comment

          Working...
          X