InterSystems Ensemble is a complete and easy-to-use integration platform that enables users to connect people, processes, and applications in record
time.
Hello,
I am receiving the following message structure on Ensemble from a lab machine, and it is still being processed. I am using the ASTM format with the EnsLib.EDI.ASTM.Service.TCPService service. I have reviewed multiple ASTM messages and verified the schema structure. Logs are not showing any error or TCP connection is not disconnecting. I am not able to understand why am I receiving this. Please let me know if any additional details are required.
Currently have an extension of the ..lookup function as a custom version of the lookup. Is there any easy way to get it to display it as a list of the lookup tables
ClassMethod LookupV3(table As %String = "",
and the one i'm trying with
Hi Communtiy,
I am a begineer who is working and trying to understand Intersystems. I am developing an Ensemble interface which receives a XML message and converts it into HL7 format without using enslib.HL7 classes.
Requirement
Hello everyone, thanks for reading this question.
I am currently working with Ens.Alerting.ManagedAlert in an interoperability production and I am using the alert suppression mechanism to avoid generating duplicate alerts within a defined time window (for example, 30 minutes).
The configuration works correctly in terms of preventing duplicate alerts from being generated, but I have a question regarding observability.
When an alert is suppressed during the configured time window, I can see log messages such as:
"Managed alert not created for AlertRequest with ID 'XXXX' due to rule 'Rules.
We have an HL7 feed that contains Lab Results. Each message contains a set of results, identified by a LabReportId. Some LabReportIds can get more than one message / set of results - these are updates, as new results become available, and must be processed in order. Results for different LabReportIds can be processed in any order.
As each message is used to build a PDF, which takes time, we want to run these through a production where the key business process has a Pool Size > 1, while still ensuring that messages for each LabReportId are processed in order.