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

SOAP Listener channel

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

  • SOAP Listener channel

    Hi,

    I just started with Mirth and am trying to setup a small project that performs an ADT-A19 request from a SOAP message. I have some issues with this setup however.

    1) Apparently I can name the URI target anything I want but it's always based in a folder called "services" and has a single fixed name method called "AcceptMessage".

    2) After a really frustating day I discovered that in order to have the channel accept the obvious data format XML I have to urlencode the data in the SOAP message. I wouldn't even know where to start with the other formats I can choose from but I'm sure that if I did I would never put those in SOAP.

    3) There appears to be no way to format the SOAP response, so now I have an "acceptMessageReturn" that contains a bunch of HL7 codes the application won't understand.

    So now I'm thinking I need some kind of http(s) wrapper page that will do the necesary renaming and translations from application level to something Mirth can use and back. But I can't even find the documentroot

    Would this really require me to have a second webserver active to translate and route to Mirth? Also, how can I set listening addresses for Mirth to localhost?
Working...
X