Hi all, 
I have a requirement to periodically poll a URL to fetch some XML data based on a list of query data, lets say every hour, and map what's returned to HL7 then send downstream, I mostly have everything contained within a business process and DTL but I'm lacking a way of invoking the process every X minutes, 
The client has a prefence for as much as possible to be done via out of the box components in the standard HL7 model of  "Service --> Process/Rule/DTL --> Operation" within the Web UI, 
I'm looking for something to act as the Service part that will trigger the  "Process/Rule/DTL -->

Hi all, 
I'm trying to output a XML file, mapped from a ORU_R01 2.3 HL7 message, with a file name based of fields in the source HL7 message in the following format, 
source.{PIDgrpgrp(1).PIDgrp.PID:PatientIDInternalID(1).ID}_"-"_
source.{PIDgrpgrp(1).PIDgrp.PV1grp.PV1:VisitNumber.ID}_"-"_
source.{PIDgrpgrp(1).ORCgrp(1).OBR:ObservationDateTime.timeofanevent}
To give something like RXR0000000-000000123-20211125105415.xml as the output filename,
I initially tried to extend the EnsLib.XML.Object.Operation.

Hi all, 
I'm using a snippet I found from Scott Roth to extract, decode, and save a PDF from a HL7 message and save it to a specified file path, but I'm running issues with the following error:

My approach was to a create a utility function accessible from a DTL like this:

Class ELHTPRODPKG.Functions.Utility.ExtractPDF Extends Ens.Rule.FunctionSet
{

     ClassMethod DecodeBase64HL7(base64 As %Stream.

Hi all, 
Just wondering if there's a quick way to get the DocType, without knowing it in advance, from a message body by building a string from the VersionID, MessageType, and TriggerEvent fields? (Similar to how it might be done dynamically in Rhapsody)
Can this then be used to set the DocType for a source message?
If this is not the best practice what is a suitable alternative approach?
Thanks for your help,
Ben

Hi all, 
I'm fairly new to this engine so I was wondering what the best approach for creating a dynamic mapper to downgrade from one HL7 version to another (e.g 2.4 to 2.3) with the DTL Editor,  It seems like something that would be quite commonly needed but I haven't found a method that works yet,
I would like to Map any 2.4 ADT message to the same event type in a lower version (e.g DocType 2.4:ADT_A01 to 2.3:ADT_A01), without having to create a specific map for each trigger event and without having to specify the DocType ahead of time.