Replies: 1 comment 2 replies
-
|
See https://github.com/OpenIntegrationEngine/engine/blob/main/donkey/src/main/java/com/mirth/connect/donkey/util/Base64Util.java, which is what ultimately is used. So just remove the line break, e.g. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Trying to add a B64 encoded jpeg into an outbound HL7 message results in a CRLF being inserted after every 77 characters of the B64 blob. The B64 data looks fine inthe channel map and tests OK in a B64 decoder but something in the HL7 output is breaking it with these repeated CFLF's.
This issue and question has been answered before in the old forum but the link to the answer is no longer working :(
https://forums.mirthproject.io/forum/mirth-connect/support/3389-converting-pdf-file-to-an-encoded-base64-blob
Any help would be much appreciated as I'm struggling to find the fix for this issue. Mirth channel is attached.
Dicom Snapshot HL7 to LIS.xml
------------ sorry to update this discussion, further checking the channel map data shows that the result of this function already has the line breaks after 77 characters, but why?
var B64jpg = DICOMUtil.convertDICOM('imagetype', connectorMessage)
Beta Was this translation helpful? Give feedback.
All reactions