Mirth Connect 4.0.1 Released!

Mirth Connect 4.0.1 is now available as an appliance update and on our GitHub page. Mirth Connect 4.0.1 is a patch release containing a bug fix which includes fixing a Jetty keystore regression that caused Connect servers using a PKCS12 keystore containing a wildcard certificate and/or a certificate with a SAN to throw an exception on startup. 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

element names in XML from ASCII HL7

  • Filter
  • Time
  • Show
Clear All
new posts

  • chrisl
    Re:element names in XML from ASCII HL7

    This is a parser setting. Inside the transformer, click on "properties" on the inbound tab. Turn on strict parsing and you will have the proper composite names.

    Leave a comment:

  • skohalmi
    started a topic element names in XML from ASCII HL7

    element names in XML from ASCII HL7

    Can someone please point me to where Mirth controls how an ASCII HL7 message is parsed into XML such that msg['PID']['PID.2']['CX.1'] can be used to access a value rather than msg['PID']['PID.2']['PID.2.1'] in a transformer script?

    No matter what I have tried for options, HL7 versions, etc. the msg['PID']['PID.2']['PID.2.1'] method gets me the data but msg['PID']['PID.2']['CX.1'] does not get defined in the XML form of the message read in.

    Thank you!