The ObjectScript code looks convincing but is wrong..
We don't have a method Parse() in the EnsLib.HL7.Message class, instead we use ImportFromString(). The DocType should be 2.4:ORU_R01 or similar with message category and doctype combined, and set with PokeDocType() method. 

Further, we don't have a FHIR.Resource.Observation package and cannot get value from the HL7 message directly using "src.MSH.GetSendingApplication()". There are more issues like this..

ChatGPT still has a long way to go and a lot to learn..

Gigi was advised to work with a Sales Engineer on a custom Business Process.

Hi Sansa,

This is something you might want to contact InterSystems Worldwide Response Center with. To contact them regarding this issue, you could either log into the WRC app and create a new issue, or email support@intersystems.com with a brief description of your question, or call at +1 617-621-0700. A support advisor will be available to investigate how the business service is customized and why doesn't it receive an acknowledgement.

Thank you.

Yes that is a viable approach. 

In Ensemble documentation we have this piece to reference: 

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

Are there any use cases where message bodies are required to be kept while message headers can be purged?

This could also be very useful when you would like to configure your Ensemble production to start automatically on UNIX OS boot. It can be done in two steps: 1. Put "ccontrol start <INSTANCE NAME>" in a script that would run at OS start up; 2. Configure the production to start automatically upon Ensemble instance start up through the Management Portal -> Ensemble -> Manage -> Auto-Start Production.