#Ensemble

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.

Hello!

I am requesting feedback on the usage and experience of the Schema Viewer feature available in Interoperability-enabled products (IRIS, IRIS for Health, Health Connect). This feature is accessible via Interoperability > Interoperate. 

Some questions to jog your discussion/comments below:

1. What's one enhancement that would drastically change your experience or enable faster schema configurations?
2. If you are not a user of this feature (but need to create custom schemas/view your schemas), why do you not use the schema viewer?

Hi Team,

I am working on an ASTM interface using EnsLib.EDI.ASTM.Service.TCPService.

Environment

InterSystems Ensemble / IRIS (please specify your exact version)

Service class extending:

Class Custom.ASTM.Service.TCPService
Extends EnsLib.EDI.ASTM.Service.TCPService
{
Parameter EOTOPTIONAL = 1;

Parameter ADAPTER = "Custom.EDI.ASTM.Adapter.TCPAdapter"
}

Custom Adapter:

Include EnsEDIASTM
Class Custom.EDI.ASTM.Adapter.TCPAdapter Extends EnsLib.EDI.ASTM.Adapter.

The 2018.1.12 maintenance releases of InterSystems Caché^®, InterSystems Ensemble^®, and HealthShare^® Health Connect are now Generally Available (GA). 

Please share your feedback through the Ideas Portal using the category Post-Release Feedback so we can build a better product together.

Documentation

You can find the detailed change lists & upgrade checklists on this page:

• Caché® and Ensemble® Change Notes (2018.1.12)
• Upgrade Impact Checklist from 2018.1.11 to 2018.1.12

Early Access Programs (EAPs)

There are many EAPs available now. Check out this page and register to those you are interested.

Hi everyone,

I am currently integrating a Sysmex analyzer with InterSystems Ensemble/IRIS using a Moxa NPort 5110. I have successfully verified the physical and serial layers, but I am facing two specific issues: a protocol sync error and a persistent TCP connection state.
Environment:
Interface: ASTM.

Gateway: Moxa NPort 5110 (TCP Client Mode).

Server: Ensemble Business Service (EnsLib.ASTM.Service.TCPService).

Port: xxxx.

Current Status & Observations:
Serial Layer: Verified. The Moxa "Async Monitor" shows RxCnt increasing when the instrument sends data. Hardware pins (DSR/CTS) are ON.