Replies: 5 comments 17 replies
-
Great first post. Welcome to the community. Please share what you searched for and where you looked. Github discussions are good. https://forums.mirthproject.io/ has decades of old threads. Please also make sure your screenshots do not contain real patient information. If you can, please also edit your post to include:
This is definitely an XML escaping issue but I can't quite see where the problem is. The inbound |
Beta Was this translation helpful? Give feedback.
-
Hi Jo,. Raw Message Transformed & Encoded Part of the Sent message, I can't show all of it due to medical info [ATTACHMENTS] [CONTENT] Response Error |
Beta Was this translation helpful? Give feedback.
-
We are getting the following SOAP Error; ERROR: Error creating web service dispatch [SOAPExceptionImpl: Error during saving a multipart message] WSDL URL: https://njiis-uat.nj.gov:443/ims/service?wsdl [ATTACHMENTS] [CONTENT] |
Beta Was this translation helpful? Give feedback.
-
Success, I think. See below. <soapenv:Envelope xmlns:env="http:https://www.w3.org/2003/05/soap-envelope" xmlns:soapenv="http:https://www.w3.org/2003/05/soap-envelope"> |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hi All, First post, apologies if this has been answered before. I tried searching and found posts kinda related but not exactly my problem.
This is our first time using Mirth, We are using Mirth to convert a CSV file to HL7 file and then send the HL7 file through a web service in a SOAP wrapper.
The HL7 file get created fine and has been validated. Looks like when MIRTH converts the HL7 file to XML, MIRTH converts & to &: from MSH|^
**&**| to <MSH.2>^**&:**</MSH.2> causing problems in the webservice file transfer. At least that is what the vendor tells me.Is there a way to prevent this conversion of & to &:?
Thanks,
Ralph
Beta Was this translation helpful? Give feedback.
All reactions