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

If you work with Productions, highlighting connections between Business Hosts is a very convenient feature, allowing developers to get a visual representation of a data flow.

This feature works by default with all system Business Hosts. If a user writes their own Business Services, Processes, or Operations, they must implement the OnGetConnections method for this functionality to work with their custom Business Hosts (or use Ens.DataType.ConfigName properties for connections).
That said, the SMP shows only the first layer of connections of the selected Business Host. Sometimes, we need to get connections of connections recursively to build a complete data flow graph. Or we might need this connection information to check which downstream systems might be affected by a change upstream.

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.

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

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.

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.

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

Hi everyone,

Does anyone know how to export projects via VSC?

I opened the project through the "InterSystems Tools" plugin (command is "Edit Code in Project") and I can correctly work on it.

However, when I try using the "ObjectScript" plugin to export the project (right click on the project -> "Export Project Contents")

This message appears and it is not possible to export the project:

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.

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.

When using InterSystems IRIS as an interoperability engine, we all know and love how easy it is to use the Message Viewer to review message traces and see exactly what's going on in your production. When a system is handling millions of messages per day, you may not know exactly where to begin your investigation though.

Over my years supporting IRIS productions, I often find myself investigating things like...

Introduction

Hello! In this article, I will be discussing database degrade, a type of data integrity issue one can face when using IRIS. First, I will be going over a review of the structure of IRIS databases. I'll then discuss how database degrade can manifest and common causes of degrade issues. I'll then conclude with general tips we give our customers about how to prevent or prepare for database degrade issues.