.png)
InterSystems IRIS for Health™ is the world’s first and only data platform engineered specifically for the rapid development of healthcare applications to manage the world’s most critical data. It includes powerful out-of-the-box features: transaction processing and analytics, an extensible healthcare data model, FHIR-based solution development, support for healthcare interoperability standards, and more. All enabling developers to realize value and build breakthrough applications, fast. Learn more.
If you're running IRIS behind IIS and get this error when trying to open the Lite Terminal in the vscode-objectscript extension:
WebSocket error: Error: Unexpected server response: 101
check your IRIS Web Gateway log. If you see:
level=SEVERE event=WebGateway.WebSocketError
This Web Server does not support WebSockets
the fix is to enable the WebSocket Protocol IIS feature, which is not installed by default.
Hi Community,
Enjoy the new video on InterSystems Developers YouTube:
IRIS Health (Community) 2026.1.0.235.2 failing to start - any tips on how to reset things without doing a full reinstall?
We use Ensemble 2018 for our production servers, and have local instances for developers running fine. We are gearing up for the move to Iris, and are using the Community edition of Iris Health to check that our existing productions all work OK.
I installed IRIS Health in mid-May alongside my existing Ensemble instance, and have it configured to auto-start when my laptop boots.
One of the latest features I'm really looking forward to in v2026.2 (now available as preview) is the "FHIR Explorer".
This new capability, part of InterSystems' FHIR Server, allows users to explore FHIR data via a friendly and intuitive UI, that builds (possibly complex) FHIR Search URLs, runs it against your FHIR Server (actually any FHIR server...), and displays the results.
Here's a simple flow:
Healthcare is a system that pays claims first and asks questions later.
It's called "pay and chase." You write the check. Then you hire people to chase the fraud.
Chase works about 3% of the time.
We decided to build something that doesn't chase. Something that stops the payment before it leaves the door.
That was the easy part.
InterSystems IRIS for Health processes FHIR claims in real time. Every hospital, every clinic, every transaction passes through it.
We built a hook. A piece of software that doesn't block the claim — but reads it. Analyzes it. Decides if it should wait.
Hi Guys,
I've export Production from live namespace and trying to import it to TEST namespace from Management portal and I've updated Test from Live issue is I'm unable to deploy top test because some queries using legacy tables that they don't exits anymore even in our Live system, so is there a way to copy the production between the systems and skipping the compiling process on Deployment ?
Thanks
InterSystems Reports version 25.3 is now available from the InterSystems Software Distribution site in the Components section. The software is labeled InterSystems Reports Designer and InterSystems Reports Server and is available for Mac OSX, Windows and Linux operating systems.
Don't let the minor release number fool you - there is a lot packed in this release. It includes a refreshed user interface - cleaner lines and fresher colors in "Light mode" and the ability to go back to "Classic mode" in your User Profile.
As part of a focus we are putting on improving the speed of ingestion of FHIR payloads, in v2026.2 (available as of now as a Developer Preview), we are introducing an option to skip structure validation of resources. This could save for example 25% of the time, which in large scale ingestions, could be significant.
Hi,
Just thought I'd share quite a handy hook that has helped me out when developing on Health Connect Cloud with VS Code and GitBash. When developing on Health Connect Cloud, if changes are made directly on the server such as routing rules or component deployments, they aren't automatically included in source control, therefore you must export from the server into your local files and push to your remote repo. I'm sure there are easier methods to deal with that which I'm in the process of testing, but as a quick solution I thought it would be handy have a pre-commit hook which triggers a reminder in GitBash - see below.
.png)
If you start with InterSystems ObjectScript, you will meet the XECUTE command.
And beginners may ask: Where and Why may I need to use this ?
The official documentation has a rich collection of code snippets. No practical case.
Just recently, I met a use case that I'd like to share with you.
When you build an IRIS container with Docker, then, in most cases,
you run the initialization script
iris session iris < iris.script
This means you open a terminal session and feed your input line-by-line from the script.
And that's fine and easy if you call methods, or functions, or commands.
Hi all,
I've been researching the capability within IRIS for Health OAuth2 machine-to-machine authentication. IRIS is the client in this case.
Specifically, the idea is to build JWT claims, sign with a private key and then send a POST request as a client assertion to receive a bearer token. The bearer token would then be used in a subsequent request.
I've learnt one way to do this (described below) . Leaving out any concern about attaching the client_assertion, token caching etc. and focusing on just creating a signed-JWT.
Hi Community,
It's time to announce the winners of the InterSystems Programming Contest: AI Agents for FHIR!
A big thank you to our 18 fellow members who built
This competition received impressive submissions, each reflecting innovation and creative thinking. With so many strong entries, selecting the best was a true challenge.
Let's meet the winners and look at their projects:
Hi Community,
We're excited to invite you to the upcoming webinar in German:
👉 InterSystems TechTalk #17 | ChatFHIR: FHIR Access with MCP and AI Hub 👈
🗓️ Date & Time: Wednesday, June 17th, 11 am CEST
Every clinic visit starts the same way: a patient sits in a waiting room holding a clipboard, answering the same questions they'll be asked again ten minutes later — while the clinician walks in cold, with no idea whether the next case is a sore throat or a heart attack in progress.
That gap: between what the patient knows and what the clinician sees — is what Triage Park closes. It's our entry for the InterSystems Programming Contest: AI Agents for FHIR.
Using the SOAP wizard many moons ago, I had setup a process to get Patient Demographics, and the current Visit Location from Epic for processing HL7 DFT Charge Messages.
Within the past week we have had two cases where the Outbound SOAP Adapter has been throwing Errors (Exceptions) where in this case
NO-PATIENT-FOUND details: No patient found with the provided ID and ID type.
The error is not being sent back in the Response to the Business Process that sent the call. The Response comes back blank.
A vector-search knowledge base of past clinical assessments, running on InterSystems IRIS, gives the LLM a deterministic calibration signal — making its triage reasoning faster, more structured, and clinically defensible.
The LLM answered correctly. But would it answer the same way for the next patient with the same profile? Same conditions, same medications, same symptoms — would the risk score drift? Would the priority shift from "emergency" to "urgent"? Would the follow-up tasks be different?
When installing InterSystems IRIS on Windows, you may see the following option in the installer wizard if IIS has already been installed and enabled (Enable IIS).
Note: Depending on your installation type, you may not see this exact installer screen. In that case, proceed with installation as normal, and then configure the IIS settings on the server where the Web Gateway is installed.
If you choose to configure the local IIS web server for the instance, the installer wires IIS and the InterSystems Web Gateway together for you.
Amazon SQS (Simple Queue Service) is a managed message queue service that provides a simple, durable, and scalable mechanism for exchanging messages between applications. It is particularly well suited for event-driven integration patterns and loosely coupled architectures.
Bear in mind that the AWS SQS adapter is based on InterSystems PEX Network and requires the Java External Server to be enabled.
When using Amazon SQS you can either take the role of a Consumer or a Publisher.
In my first article, I described the baseline version of the FHIR Patient Snapshot Agent: a Streamlit and Python application that retrieves FHIR resources from InterSystems IRIS for Health and uses an LLM to generate a concise patient summary.
This follow-up article explains how I extended the project with two additional InterSystems-focused features:
The goal was to make the project more useful as a clinical summarisation prototype while keeping the design small enough to understand and reproduce.
FHIR Patient Snapshot Agent is a small open-source application built for the InterSystems AI Agents and FHIR Programming Contest.
The project implements the suggested Smart Patient Summary Generator idea: it retrieves structured FHIR resources for a selected patient and generates a concise, role-specific patient summary.
The goal is not to diagnose or recommend treatment.
Hi Community,
It's voting time! Cast your votes for the best applications in our InterSystems Programming Contest: AI Agents for FHIR:
Voting period: June 8 to June 14, 2026
How to vote? Details below.
InterSystems Programming Contest: AI Agents for FHIR at https://openexchange.intersystems.com/contest/46 .
Code: https://github.com/eungi-hong/central-park
Demo: https://triagepark.78-47-167-98.sslip.io/
The first ten minutes of a visit are always the same: take the history, pull the record, cross-check the medications, decide how urgent it is. Triage Park does that first pass as a team of AI agents running entirely inside InterSystems IRIS for Health, and hands the clinician a cited, explainable handoff. The part most "AI triage" demos skip is the part we cared about most: safety
On save the ClassMethod:
ClassMethod create() [ Language = python ] {
print("python")
}
it has received the error :
Compilation started on 06/03/2026 02:15:21 with qualifiers 'cuk /multicompile=0'
ERROR #7802: Worker job/s '1078:17' unexpectedly shut down in group '#Default:(9119826733444):0'.
ERROR #7802: Worker job/s '1078:17' unexpectedly shut down in group '#Default:(9119826733444):0'.
with the compileFlags "cuk" the return is:
ERROR #7802: Worker job/s '1160:34' unexpectedly shut down in group '#Default:(6933525859080):0'.
At 4:57 PM on a Friday, a routine laboratory order failed.
The patient's sample was already in transit. The external reference laboratory rejected the request — it could not uniquely identify the patient. The insurance operator rejected authorization for a different reason. Neither system spoke the same language, neither exposed compatible error messages, and the only integration layer in the middle simply forwarded requests.
A laboratory technician spent the next 25 minutes navigating portals, copying identifiers, and manually reconciling data between systems.
Smart Patient Summary Generator is an AI-powered FHIR demo application built for InterSystems IRIS for Health. It reads FHIR R4 patient data, extracts key clinical information, and generates concise summaries for four different roles:
By consolidating fragmented FHIR records into role-specific summaries, the application helps clinicians quickly understand a patient’s current condition, recent changes, and follow-up risks. For patients and family caregivers, it presents the same clinical context in a more accessible format.
Hi Community,
In this article, I will introduce my application iris-fhir-agents A multi-agent clinical AI platform powered by InterSystems IRIS for Health. Features agents for triage, specialist consultation, pharmacy safety, and FHIR server exploration — all grounded by IRIS Vector Search RAG. Includes a no-code Agent Builder that lets you design and deploy custom clinical agents without writing a single line of code.
For decades, healthcare payers have been trapped in a reactive cycle known as "pay-and-chase." Traditional payment integrity relies on retrospective audits—reviewing claims months after disbursement to claw back overpayments. This inefficiency costs the industry billions in unrecovered fraud, waste, and abuse.
ClaimAuditAI introduces a fundamental paradigm shift by moving the audit to the point of submission.
Most "AI agent + FHIR" projects end up with the same shape: a FHIR server over here, a vector database over there, and a Python service in the middle whose job is to call an embedding API, marshal float arrays back and forth, and keep two datastores in sync. Three moving parts, two network hops, and an embedding client you now own forever.
Triage Park: our entry for the InterSystems Programming Contest: AI Agents for FHIR, doesn't have any of that. The agent never computes an embedding. It never imports an OpenAI embeddings client. There is no vector database.
Hi All,
There is a steady increase in the amount of metadata that I need to build in the message flow (across BPs & DTLs) and I am interested on a good pattern to follow that allows for a mix of metadata types (e.g. json, xml list, etc) and is accessible quickly either within DTLs or BP.
One example for this would be adding various localised codesets to metadata during DTLs which would later be used to submit a FHIR translate request to a terminology server. Providing visibility in the DTL to which codesets are to be translated while batching up the translate request for performance.
Hi Developers,
We are happy to announce the new InterSystems online programming contest:
🏆 InterSystems Programming Contest: AI Agents for FHIR🏆
Duration: May 25 - June 14, 2026
Prize pool: $12,000
