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

Base64 encoded DICOM in OBX segment

  • Filter
  • Time
  • Show
Clear All
new posts

  • Base64 encoded DICOM in OBX segment

    I need to encapsulate a DICOM image file into an OBX segment and I cannot make it happen. The channel receives a DICOM file, I then use DICOM.Util.getDICOMRawData(connectorMessage) as it seems like it will return what I need.

    Yet no matter what I do I get an error message for a message about the namespace where it says an element type must be followed byt a ">" or "/>" Unchecking "strip namespaces" does not change this.


  • #2
    Why would it be using namespaces at all? Are you reading in or outputting XML files? DICOM has its own datatype in Mirth.