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

change field in MSH segment.

  • Filter
  • Time
  • Show
Clear All
new posts

  • change field in MSH segment.


    I created a channel.
    I click on the Source Tab.
    I click on Edit Transformer.
    I click on add step.
    I change the step to type Javascript.
    I add the following

    tmp['MSH']['MSH.3']['MSH.3.1'] = "obgy";
    I return to channel and I configure the source and Destination tabs.

    I save the channel.

    I deploy the channel and I start it.

    From my source application I send a hl7 ADT A04 message, and on the estination port, I see the HL7 message is received. In mirth I see the HL7 ADT message is received on incomming port and is sent out to the outgoing port.

    However, the MSH.3.1 field has not changed to the new value.
    What is wrong. Why doesn't mirth change the MSH.3.1 field value.


  • #2
    Re:change field in MSH segment.

    Why doesn't Mirth have any documentation?


    • #3
      What was the solution to this?


      • #4
        Now there is a fantastic user guide that you can download.