Hey Community!

We're happy to share a new video from our InterSystems Developers YouTube:

     ⏯ Develop the Next Generation of Health IT with InterSystems@ Ready 2025

Hi,

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.

The 2025.1.3 maintenance releases of InterSystems IRIS^® data platform, InterSystems IRIS^® for Health, and InterSystems Health Connect™ are now Generally Available (GA).

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.

Hey Community!

We're happy to share a new video from our InterSystems Developers YouTube:

     ⏯  Vector Search Performance @ Ready 2025

Hi Community,

We’re excited to invite you to take part in shaping the next generation of ObjectScript development tools. We’re working on an AI-powered ObjectScript coding assistant designed specifically for IRIS developers. Not a generic AI adapted for ObjectScript, but a solution built from the ground up to understand ObjectScript idioms, IRIS APIs, interoperability productions, and real-world developer workflows.

To make sure we build something truly useful, we need your input.

👉 ObjectScript Coder Agent Developer Survey 👈

The third developer previews of InterSystems IRIS^® data platform, InterSystems IRIS^® for Health, and InterSystemsHealth Connect™ 2026.1 have been posted to the WRC developer preview site.  Containers can be found on our container registry and are tagged latest-preview.

These developer previews includes the dropping of Mac Intel support starting from 2026.1.0, and the adding back of Windows Server 2019 support to 2026.1.0.

Initial documentation can be found at these links below:

• InterSystems IRIS Data Platform 2026.1 | Documentation Home Page
• HealthShare Health Connect 2026.1 | Documentation Home Page

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
• Management Portal: http://YOUR_VM_IP:52773/csp/sys/UtilHome.csp

Hi Community! 👋
As 2026 gets underway, we’d love to hear what you’re focusing on this year.

This discussion is a space to share your resolutions, goals, and focus areas for 2026 - technical, professional or community-related.

These don’t have to be traditional New Year’s resolutions. Think of them as intentions or priorities you’d like to work on this year.

Hi Community! 👋

You’ve asked for easier ways to connect with other Global Masters and we heard you!
Random Coffee Chat is an easy way for Global Masters to connect and have an informal 1:1 conversation. ☕

🗓 When: January 26 – February 15

This thread is for participants based in North, Central, and South America who’d like to connect and schedule a short coffee chat directly with each other.

Enabling HSSYS Mirroring Out of the Gate with IKO

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.

PEP 578 added Python Audit hooks. A rich variety of events (module load, os interactions and so on) triggers audit events which you can subscribe to.

Here's how to do that. First create an embedded python hook:

Class/// do ##class(User.Python).Audit()ClassMethod

In this example we:

• Terminate the process if numpy starts loading
• Output event and arguments for compile/exec events
• Ignore code events
• Log all other events

All of that will be written to the default STDOUT.

Developer required to join a team working with and extending an existing CACHE application and subsequent migration to IRIS.

4yrs Minimum experience.

Applicants must have good general knowledge of development approaches and patterns.

SQL 

Opportunity from 6 Month contract to Permanent, depending on experience. Immediate start

Applications to chris.clipston@mtivity.com

Hello everyone,

My team lead mentioned that users can sometimes create globals directly without associating them with tables or classes. In this case, these globals would not be accessible via SQL.

Is this correct? Can a global exist independently in this way, and if so, is there a specific approach to access or manage them without SQL?

10:47 AM — Jose Garcia's creatinine test results arrive at the hospital FHIR server. 2.1 mg/dL — a 35% increase from last month.

What happens next?

• Most systems: ❌ The result sits in a queue until a clinician reviews it manually — hours or days later.
• This system: 👍 An AI agent evaluates the trend, consults clinical guidelines, and generates evidence-based recommendations — in seconds, automatically.

No chatbot. No manual prompts. No black-box reasoning.

This is event-driven clinical decision support with full explainability:

✅ Triggered automatically by FHIR events ✅ Multi-agent reasoning (context, guidelines, recommendations) ✅ Complete audit trail in SQL (every decision, every evidence source) ✅ FHIR-native outputs (DiagnosticReport published to server)

Built with:

• InterSystems IRIS for Health — Orchestration, FHIR, persistence, vector search
• CrewAI — Multi-agent framework for structured reasoning

You'll learn: 🖋️ How to orchestrate agentic AI workflows within production-grade interoperability systems — and why explainability matters more than accuracy alone.

Hi Community!

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.

Hey Community!

We're happy to share a new video from our InterSystems Developers YouTube:

⏯  Taking the Fear out of FHIR - Fast Tracking Organizational FHIR Readiness @ Ready 2025

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.

However, right now our system is merely a raw pipe to an LLM. It processes text, but it lacks identity.

Today, in Part 2, we will define the Anatomy of an Agent We will move from simple API calls to structured Personas.

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?

Thanks

RIP Neil Pappalardo

i am  install the IRISHealth on Mac,however,it met below error,can someone help on this issue:

below is the setup when do install,id/group irisusr is create during install setup.

Instance name: IRIS
Destination directory: /Users/xxx/Downloads/IRIS
IRISHealth version to install: 2025.3.0.226.

As applications grow, every database eventually hits scaling limits. Whether it's storage capacity, concurrent users, query throughput, or I/O bandwidth, single-server architectures have inherent constraints. This guide explains fundamental approaches to database scalability and shows how InterSystems IRIS implements these patterns to support enterprise-scale workloads.

We'll explore two complementary scaling strategies: horizontal scaling for user volume (distributing computational load) and sharding for data volume (partitioning datasets). Understanding the general principles behind these approaches will help you make informed decisions about when and how to scale your IRIS applications.

The examples in this guide use InterSystems IRIS in Docker containers.

IPM version 0.10.5 has been released on January 15, 2026. This new version contains a ton of improvements and bug fixes so be sure to check it out either directly from the GitHub page or from the Community Registry!

1-command only required for an entire IRIS instance for Data Science projects, and leveraging this to compare query methods' speed (Dynamic SQL, Pandas Query, and Globals).

Before joining InterSystems, I worked in a team of web developers as a data scientist. Most of my day-to-day work involved training and embedding ML models in Python-based backend applications through microservices, mainly built with the Django framework and using Postgres SQL for sourcing the data.

How I Vibecoded a Backend (and Frontend) on InterSystems IRIS

I wanted to try vibecoding a real backend + frontend setup on InterSystems IRIS, ideally using something realistic rather than a toy example. The goal was simple: take an existing, well-known persistent package in IRIS and quickly build a usable UI and API around it — letting AI handle as much of the boilerplate as possible. Here is the result of the experiments.

Here are the technology bonuses for the InterSystems Full Stack Contest 2026, which will give you extra points in the voting:

• IRIS Vector Search usage -3
• InterSystems Native SDK for Python or Embedded Python usage -3
• Developer Community Idea implemented - 2
• Docker container usage -2 
• IPM Package Deployment - 2
• Online Demo -2 
• Find and report a bug - 2
• Article on Developer Community - 2
• The second article on Developer Community - 1
• Video on YouTube - 3
• YouTube Short - 1
• First Time Contribution - 3

See the details below.

I've modified the class file, but messages still arrive as a single line (e.g., "H|.../rQ|.../rL") instead of separate lines in the ASTM service. The <ENQ>..<EOT> header looks correct, logs show no errors, and the service receives messages fine. Is there an Ensemble 2018.1 engine setting (like line terminator handling or TCP framing) to fix the line splitting? ​