11-11-2020 02:59 PM
Hello, still learning the trials and tribulations of HL7. Our customer is sending us $$FILEDATA but the base64 encode is too long for one segment. So they are continuing it in a second OBX segment.
Can this all be captured in one document? If so can someone tell me how they accomplished this? I'm not seeing this explained clear enough in the HL7 MRG.
11-11-2020 03:23 PM
Hi Pete, Yes you can have a single Base64 document that spans multiple OBX segments. There are a few Community posts and threads on the topic. Here is a recent one that goes into some detail on the topic that you may want to review:
Combining Multiple OBX segments into one document
11-11-2020 03:23 PM
Hi Pete, Yes you can have a single Base64 document that spans multiple OBX segments. There are a few Community posts and threads on the topic. Here is a recent one that goes into some detail on the topic that you may want to review:
Combining Multiple OBX segments into one document
11-12-2020 05:54 AM
Thanks Nick, that's a great thread. Glad it's fixed in EP3. For now, being on EP1, we won't be able to ingest a Base64 document spanning multiple OBX segments and have it concatenated by Onbase. It will need to be done by the vendor or another intermediary interface engine.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.