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

conversion of HL7 version to another...

  • Filter
  • Time
  • Show
Clear All
new posts

  • conversion of HL7 version to another...

    I am a newbie. Is there a way to convert HL7 message from one version to another? Say if I wanna convert from HL7 v.2.3.1 to HL7 v.3.0. How do I do that? I don't want the message content (v.2.3.1) to be changed. There is no mapping present. Its just LlpSender --> FileWriter and FileReader --> LlpSender. There are no transforms for the v.2.3.1 message. But I need the message in v.3.0. Is it possible in mirth 1.6.1? If so, please guide me...


    Kurian Thayil.

  • #2
    Re:conversion of HL7 version to another...

    Converting between the 2.x variants is pretty easy and almost fully automated.

    However, going from 2.x to 3.0, though doable, requires that you create the mappings yourself. Either using javascript or something like XSLT. So though it's doable in principle, right now it will take a lot of work on your part.

    If you're looking for a quick and painless 2.x -> 3.0 transformation solution, you're out of luck.

    Besides that, the spec for lab results (typically what 2,x is used for the most) in 3.0 isn't even out yet.