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

XML generated by encoder.encode

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

  • XML generated by encoder.encode

    Hi, I have a question about the XML format generated by a call to encoder.encode(). I hope this is the correct forum.

    Is there a document somewhere that describes the mapping from HL7 to this XML format?

    I could not see one, so if there is not hopefully somebody here will be able to help me. Usually it seems field elements (e.g. MSH.3) are further divide into value elements (e.g. MSH.3.1), even if there is only one value. However in my test message the element MSH.1 contains an actual value ("|") and no value elements.

    Is MSH.1 unique in this respect, or is there a more general reason?

    Thanks for reading.
Working...
X