We love hearing from our users. Tell us what you want to see next and upvote ideas from the community. * Bugs and troubleshooting should as usual go through InterSystems support.
Create DTL on the fly from within a Business Process
When working on a new Business Process, and you add a Translation as an object to the Business Process it requires that the DTL already be built so you can insert it into the required values. It would be nice if we could create a DTL on the fly within the Business Process.
ADMIN RESPONSE
Nov 20, 2024
Thank you for submitting the idea. The status has been changed to "Planned or In Progress".
This is not a commitment; plans are subject to change. Stay tuned!
InterSystems is working on a new user experience for Interoperability Productions, which includes the capability to look at two screens at the same time within the same browser tab (a split panel view). You can take a look at this concept in Health Connect Cloud instances if you are interested. This will allow us to easily provide a flow where you can create the DTL as part of the Transformation action.
Would this be similar to the rule creation? If yes how would the process pick the Class and Doc Type the DTL needs to start with? Maybe default to EnsLib.HL7.Message and 2.1:ACK. Issue with that is when the DTL is not HL7 so then you would need prompts. If we get this far then why didn't we start with creating the transform?
InterSystems is working on a new user experience for Interoperability Productions, which includes the capability to look at two screens at the same time within the same browser tab (a split panel view). You can take a look at this concept in Health Connect Cloud instances if you are interested. This will allow us to easily provide a flow where you can create the DTL as part of the Transformation action.
Many thanks for your suggestion!
Scott, thank you for your idea.
There is a comment on your idea. Please answer it to help your idea to be promoted.
Would this be similar to the rule creation?
If yes how would the process pick the Class and Doc Type the DTL needs to start with? Maybe default to EnsLib.HL7.Message and 2.1:ACK. Issue with that is when the DTL is not HL7 so then you would need prompts. If we get this far then why didn't we start with creating the transform?