¡Buenas @Kurro Lopez ! Por mi experiencia con la versión Community, no es necesario definir los entornos virtuales de Python, si quieres, echa un vistazo a este ejemplo que está trabajando con InterSystems IRIS Community:

https://github.com/intersystems-ib/inquisidor/blob/main/iris/Dockerfile

Básicamente es esto:

RUN apt-get update && apt-get install -y python3 && apt-get -y install curl

# install required packages
COPY --chown=$ISC_PACKAGE_MGRUSER:$ISC_PACKAGE_IRISGROUP /requirements.txt /
RUN chmod 777 /requirements.txt

RUN pip3 install -r /requirements.txt --break-system-packages

Como ves, instalamos previamente python3 y a continuación ejecutamos un pip3. Si miras el docker-compose de dicho proyecto no estamos configurando ningún entorno virtual. Prueba a adaptar tu código como el de este proyecto y nos comentas.

I guess that you are using a Enslib.HL7.Service that uses EnsLib.File.InboundAdapter as Adapter. The problem is that the name of the file is not a property of Enslib.HL7.Message class, so you have to follow these steps:

1. Create your own service that extends to Enslib.HL7.Service.
2. Overwritte OnProcessInput process to get the name of the readed stream:
   

   Set tFileName=pInput.Attributes("Filename")
   set sessionID = $$$JobSessionId
   set ^GlobalName("Session", sessionID) = tFileName
   do ##super()

3. From DTL use code to get the global that you created before getting the ID session from Enslib.HL7.Message and assign it to MSH property:

4. Set globalValue = $GET(^GlobalName("Session", sessionID))
   

5. And finally assign globalValue variable to the MSH propery (using SET from the DTL):
   

   target.{MSH.PropertyName} = globalValue

    

You could create your own adapter based using Embedded Python. Here you can find an example of connection with Python and here an example of a similar adapter that I created for connection with Firebase.

I'm not very sure that you should extend EnsLib.REST.Service to define a REST service with URLMap, but anyway, EnsLib.REST.Service is using EnsLib.HTTPInbound.Adapter so you can get the input data from OnProcessInput like this:

Method OnProcessInput(pInput As %GlobalCharacterStream, Output pOutput As %RegisteredObject) As %Status
{
     set authorization = pInput.Attributes("authorization")
...

Here is the doc related: https://docs.intersystems.com/healthconnect20251/csp/docbook/DocBook.UI…

If the class of the message extends Ens.Request you can send whatever you want. To validate the class of the message you only need $CLASSNAME method.