Forum Replies Created
-
AuthorReplies
-
Hi Troy,
thanks for your suggestion, right now the trick with the manual adjustment of the length setting works fine for us.
Troy Morton wrote:Hi Rainer,
Another option is to send only a pointer to the PDF file in HL7 through the engine, then on the backend (OB TPS) write a proc that puts the PDF back into the message just before its sent to the desitnation.
Sending large messages through the engine can be problematic to performance and the amount of memory or swap space used by Cloverleaf especially in a high message volume environment.
Troy
Jim, many thanks for your help. You pointed me to the helpful documentation. Hcixltconvert claimed to convert the xlates, however the paths for HL7 2.5 MDM_T02 message were still wrong afterwards. I had to adjust them manually. Anyway, everything seems to work now.
Rainer
Traci, your solution works for me!
I manually edited the “fields” file and set the length to ‘-1’ (as Jim proposed). Now, inbound and outbound size seem to not be limited any longer. I tested with a pdf file larger than 100000 characters which is now transmitted correctly.
Many thanks to you and all who replied.
Rainer Hurle
Jim, I’d appreciate your advice on how to set this value to “infinite”. I tried several methods but didn’t succeed (leaving the field blank causes Cloverleaf to use a default of “0”). Thank you.
Rainer Hurle
Jim, I tried as you proposed. I created a variant and used the “HL7 Configurator” to modify field 00537 and segment OBX-5. In the “Field Length” edit control, I cannot enter a negative value. So, after setting field length to “0” and replacing the field in the OBX message, I resent the message: OBX-5 in the HL7 message is empty!
Am I doing something wrong? I use HL7 2.3.1 and Cloverleaf 5.2, if that matters.
Rainer
-
AuthorReplies