[DICOM] Help Needed: Seeking Tips to Automate Presentation Contexts Export from Development to Production

Hello,
Please, we would need your help 🙂:

In a development environment, we have added quite a few presentation contexts to the DICOM configurations (the associations). We would need to find a way to export them from this environment to make it easier for us to import them in PRO (and avoid doing it by hand one by one).

We know that there is this method, the ImportAssociation(), that given a file, and the names of the local AET and the remote AET, creates it automatically:
    https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI...

We have already used this method to deploy in the test environments the theme of the associations, executing in the Terminal, like this for example:

    Do ##class(EnsLib.DICOM.Util.AssociationContext).ImportAssociation(“/opt/container/Mape_Syntax_Ensemble_LF.txt”, “[Local AET]”, “[Remote AET]”,0).

However, the file we have created by hand is very basic, it has very few associations, i.e. its content is something like this:

    1.2.840.10008.5.1.4.1.1.4\1.2.840.10008.1.2
    1.2.840.10008.5.1.4.1.1.1.3\1.2.840.10008.1.2
    1.2.840.10008.5.1.4.1.1.1.3\1.2.840.10008.1.2.1
    1.2.840.10008.5.1.4.1.1.1.3\1.2.840.10008.1.2.2
    1.2.840.10008.5.1.4.1.1.1.3\1.2.840.10008.1.2.4.50
    1.2.840.10008.5.1.4.1.1.1.3\1.2.840.10008.1.2.4.51
    [80 more lines]
    

Our need is the following: is there any way to export the presentation contexts of a particular association from the develop environment, and then import it into other environment (Production environment)?

We ask because we need to figure out how to do this when we deploy the integration.

For example, in develop we have all of these:

Is there any way to export all those abstract syntaxes and their transfer syntaxes?

We have read here:

https://docs.intersystems.com/irisforhealthlatest/csp/documatic/%25CSP.D...

but we can't find a way.

Another possible solution that you could provide us, is if there is a way to “allow that whatever abstract syntax the sender sends us in the DICOM file, the HealthShare interoperability engine allows and sends it”. That is, we need that the ESB does not make it impossible for the DICOMs to reach their destination, whatever abstract syntax the DICOM has.

Could you help us?

Thank you for your time, help and replies. Thanks. 🙂🙂🙂

Best regards