Hi everyone, please check out our new discussion forum located in our GitHub site: https://github.com/nextgenhealthcare/connect/discussions. Let us know your feedback as we try out this new part of GitHub! Don't worry, the content in these forums won't be going away and will at a minimum be preserved for historical reference.
Announcement
Collapse
Mirth Connect 4.1.0 Released!
Mirth Connect 4.1.0 is now available as an appliance update and on our GitHub page. Mirth Connect 4.1.0 includes new features such as new event log messages, additional fields to the Welcome to Mirth Connect screen, new information included in alerts as well as many smaller changes, updates, and improvements. This release also contains several improvements to commercial extensions. See the release notes for the list of fixes and updates.
I'm using a xml channel. It reads from files and send a HL7 (xml)message (no transformation) to a third party application. The end & start character are '0x0B' and '0x1C'. It is sended fine, but when I received the ACK the xmlParser try to parse the whole message including end & start characters and it doesn't work.
See my other reply, but you need to use TCP and manually append the LLP characters. The LLP Sender can't handle XML ACKs. If you would like this as a feature, please add it to the Jira - www.mirthproject.org/jira
You can still accomplish what you need with a TCP Sender and use the post processor to check the ACK.
You can still accomplish what you need with a TCP Sender and use the post processor to check the ACK.
Please, please, how can I check the ACK before Mirth parses and shows parsing errors?
I supouse I have to introduce some script in post-process tab to get the ACK (that's ok?) and to remove separator characters, but what is the appropiate sentence to get the ACK and to set the new value of the ACK?
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Tweet
Comment