What part are you finding overly complicated? If the text embedded within OBX-5 isn't too large you could treat it as a String rather than Stream, but I don't think that saves you much. Am I even correct that you're trying to modify unstructured text? In re-reading this it looks like maybe some of the criteria are in structured fields, e.g., Order Type. Can you give an example of input and desired output?
If I'm reading this right, you need to modify the text you're receiving in OBX-5.
If that's the case, this documentation link should help. It'll show you how to extract the content from OBX-5 to a Stream object, and save the modified text back into the HL7 Message.
https://docs.intersystems.com/healthconnect20251/csp/docbook/DocBook.UI....
This one will help with processing the text using Stream objects.
https://docs.intersystems.com/healthconnect20251/csp/docbook/DocBook.UI....
I think the general approach would be:
- Use a method like GetFieldStreamRaw() or GetFieldStreamBase64() to extract the content from your HL7 message to a Stream object.
- Read through the stream applying your rules and write modified text to a new output stream.
- Use a method like StoreFieldStreamRaw() or StoreFieldStreamBase64() to replace the original content with your edited version.
You could use a Record Map with a single field. Just make sure you set MAXLEN to a big enough value to hold the entire line. That would send each line in the file to your Process as text, ignoring that it's actually JSON. Your Process could convert it to a Dynamic Object if necessary. That doesn't seem to add much value over just having your Process read the file though.