Hello, I am trying to get some fields from HL7 message and create a file using BPL. The values I need are in a repeating segment (AIG). Even in the repeating segment, I just want the iteration that has a certain field (AIG:3 populated). With the help of documentation and community posts, I was able to create the BPL to loop through all of AIG and create the file. But when I try to narrow the results even further (AIG:3 present), the process gets stuck. I am not sure I am missing anything or have anything incorrectly set up. Also, since the process gets stuck, it doesn't even seem to h
I want to consume an API that provides HL7 messages. To achieve this, I have thought of the following workflow:
I have created a business service that periodically triggers a business process. The trigger request is forwarded to a business operation. There, a %Net.HttpRequest is assembled from scratch and then sent to the API endpoint. The corresponding HttpResponse then contains several HL7 messages encoded in UTF-8 in the message body. To further process the HL7 messages, the operation sends the HttpResponse back to the business process as EnsLib.HTTP.GenericMessage.
I have always struggled with Iterating through a JSON response to pull out certain fields into a Data Class Structure to use to populate fields in a DTL. So I defined the whole structure for the following JSON, with the base structure extending Ens.Response, %XML.Adaptor, and %JSON.Adaptor.
https://www.youtube.com/embed/ZcrsyBvKFsw [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
The third developer previews of InterSystems IRIS® data platform,InterSystems IRIS® for Health, and HealthShare® Health Connect 2026.1 have been posted to the WRC developer preview site. Containers can be found on our
TL;DR This article explains how to deploy InterSystems IRIS Community Edition on Azure using the Azure Marketplace and a Virtual Machine. It covers prerequisites, instance selection, authentication, SSH access, first verification steps, and how to delete resources to avoid charges. The deployment can typically be done using Azure free credits and is suitable for developers who want to quickly start working with IRIS in the cloud.
Who this guide is for. This guide is intended for developers, solution architects, and DevOps engineers who want to deploy InterSystems IRIS Community Edition on Microsoft Azure. No prior Azure automation experience is required, but basic familiarity with the Azure Portal and SSH is helpful.
After following this guide, you will be able to:
Launch InterSystems IRIS Community Edition from the Azure Marketplace
Configure a small, secure Azure VM
Connect to IRIS using SSH and the Management Portal
Reset the default IRIS password and verify that IRIS is running
Prerequisites
An active Azure subscription (new accounts may have free credits)
Permissions to create resource groups, VMs, and networking resources
An SSH client and a private key (.pem) you can store securely
Basic knowledge of Linux command line
Deployment overview
Open the IRIS Community Edition listing in Azure Marketplace and click Get it now
In Azure Portal, choose Start with a pre-set configuration (or Create)
Configure Basics: subscription, resource group, VM name, region, image, and size (a small VM is usually sufficient)
Choose SSH key authentication and generate/download the key if needed
Review + Create, accept terms, and deploy; then Go to resource → Connect → SSH
First SSH login: run iris password to change _SYSTEM/SYS; start a session with iris session iris
For those of us building InterSystems workloads on Kubernetes, we are definitely spoiled with the InterSystems Kubernetes Operator (IKO) doing the heavy lifting and mirroring on day one. Where us spoiled brats jump up and down is when we try to add additional databases/namespaces when we provision from HealthConnect containers on day two, while others get to utilize HealthShare Mirroring for this task, the prerequisite of mirroring HSSYS out of the gate has been somewhat elusive. Here is example on how you can this powerful feature up and running with the employment of IKO and IrisClusters.
InterSystems France & Benelux Ready 2026 is all about learning, sharing, and connecting. And we’re extending the experience to the Developer Community with a fun, light Bingo challenge.
https://www.youtube.com/embed/TLWXlDCpU84 [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
In Part 1, we laid the technical foundation of MAIS (Multi-Agent Interoperability Systems). We have successfully wired up the 'Brain', built a robust Adapter using LiteLLM, locked down our API keys with IRIS Credentials, and finally cracked the trick code on the Python interoperability puzzle.
France & Benelux READY 2026 has just come to an end, and once again, these two days demonstrated how dynamic, curious, and engaged the Developer Community truly is. Here is a look back in words and images at this great edition.
The event kicked off with welcome remarks from @Adeline Icard and @Geoffroy Vitoux, setting the tone for the days ahead: innovation, sharing, and collaboration.
In my previous HttpRequests, I have used Content-Type = application/json but I have a vendor that is requesting we send application/x-www-form-urlencoded. How would I go about formatting the Payload as x-www-form-urlencoded?
By update
.png)
.png)
Open Exchange app
