Ensemble supports Data Transformation Language (DTL) for describing data transformations. DTL is an XML language. Ensemble provides wizards and graphical tools for creating, editing, and testing DTL transformations. A data transformation is a Caché class like the following. If you prefer you can use Studio to edit the class definition directly and bypass the wizards and graphical tools.
My organization has been tasked with parsing raw EDI 271 messages into JSON strings in order to feed a downstream application. A few key details about the task:
Do you find yourself commonly adding code actions to your data transformations? If so, what do these contain? Is there a reason you choose to add a code action over creating a custom function that you can call?
when I run the process I end up with the following error:
----
ERROR <Ens>ErrBPTerminated: Terminating BP Propirion.BP.GetServices # due to error: ERROR <Ens>ErrGeneral: Object is immutable + ERROR <Ens>ErrGeneral: Object is immutable
----
I have created a context named : HL7Message type of: EnsLib.HL7.Message and in the start of the BP assigned the request to it (using set in assigned activity)
Is there an out-of-the-box or accepted standard method for loading up mappings between different code sets and then referencing these mappings (both directions) from DTL? First thought was the built in Lookup() and corresponding data tables but these only work in one direction (key -> value) and not the reverse. Obviously I can build my own classes to support a two way mapping but am wondering if there's a standard way of achieving this. The mapping should contain the code and display name from each of the code sets and allow mapping based on either code or display name.
I am trying to create a simple Ensemble DTL transform using the GUI. In order to test something very simple, I have created a transform that does nothing.
Does anyone have a sample that demonstrates how to use the Data Transformation option create='existing', in order to update an existing object by its ID? My use-case is that I have an HL7 message coming in which contains data on a patient that may or may not already exist in a (non-HL7) table. I want to use the PatientID from the (source) HL7 message, check if that patient exists in the (target) object, and if so, insert some new data into the existing patient, or if not, create a new patient.
I am trying to use data transformation (DTL) to map a JSON to SDA. My elements in the source JSON is not one to one with SDA object. That means I have to add code to loop through these objects in order to complete the mapping. Can someone send me a sample that can look to create that? I am not very comfortable with scripting language used in Health Share. Appreciate your help.
We are receiving XML documents and storing them. When we click to go into the clinician portal and again to view a patient, we can see the documents but none of the data is mapped to their respective buckets, i.e. allergies or medications.
I am thinking that I need to build an XSLT parser and change the format to SDA3, is this an appropriate approach? Or would using the Data Transformation (Ensemble -> Build -> Data Transformation) be a better idea? Lastly, if the XSLT idea is preferred, where would I call it within the stack?
What would be the preferred method to create an HL7 message from an input that is not HL7?
Would it be better to take the non-HL7 input and construct an HL7 message in the business service that then gets passed off to a routing process, or would it be best to just pass the non HL7 message to a routing process that called a data transformation to create the HL7 message?
My thought is the later, due to the fact that updates to the creation of the HL7 message are done using the graphical DTL editor rather than editing COS in the service.
I installed Atelier on Windows in order to take a look at how the BPL and DTL graphical editors accessible via the "Open diagram editor" action work. The diagram editor is opened but I get the following error:
Message from webpage --------------------------- Unable to load SVG diagram. Please ensure your browser is supported for portal access.
It looks like Atelier uses IE in order to display the editor even though my Windows default browser is Chrome.
Hi this is my first post, so a little about my background. I've been programming in PHP/JavaScript for about 10 years. I've got quite a bit of knowledge surrounding object orientated programming and know the basics.
Last year I looked into the Mirth integration engine and did some work around that.
I've now moved jobs and I'm doing some work (surprise, surprise) with Ensemble.
I have imported a schema (HL7 v2.5 XML schema) using the "Ensemble > Interoperate > XML" and I have built a Web Service that receives a string with an XML document that follows the schema. I have used EnsLib.EDI.XML.Document as follows to consume the string and produce the XML vDoc:
Ensemble is based on message flow, and a data transformation is a way to convert from one message type to another. DTL (Data Transformation Language) adds a layer to this - it provides a graphical way to do the conversion. This is really helpful because most of the time, people with domain-specific knowledge may not have extensive coding skills. However, you always have the ability to do some coding, so if you need or want to, this is available.
DTL has several components: the data transformation engine, the language itself, and the DTL editor.
By update