#InterSystems IRIS for Health

10 Followers · 2.5K Posts

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.

New
InterSystems Official Daniel Palevski · 6 hr ago

Summary

Alert Id Product & Versions Affected Risk Category & Score Explicit Requirements
DP-449126 InterSystems IRIS® data platform 
InterSystems IRIS® for Health 
InterSystems Health Connect™ 
versions 2024.1.0 – 2024.1.5, 2024.2.0, 2024.3.0, 2025.1.0 – 2025.1.3, 2025.2.0, 2025.3.0
Data Integrity: Low Risk  Database updates executed as part of custom logic for CSP session events may not be journaled.

 

Issue

An issue has been corrected that prevented global sets and kills in custom logic from being journaled.

0
1 13
New
Question Oliver Wilms · Mar 15

I created a new repo called ipm-module-budget from https://github.com/intersystems-community/intersystems-iris-dev-template template.

I cloned the repo to an EC2 instance in AWS. When I try to build image, I see this error:

#8 22.09 [IRISAPP|ipm-module-budget] Reload START (/home/irisowner/dev/)Segmentation fault (core dumped) #8 ERROR: process "/bin/sh -c pip3 install -r requirements.txt && iris start IRIS && \tiris session IRIS < iris.scri pt && iris stop IRIS quietly" did not complete successfully: exit code: 139

9
0 77
New
InterSystems Official Daniel Palevski · Mar 17

Summary

Alert Id Product & Versions Affected Risk Category & Score Explicit Requirements
DP-448888

Products:
· InterSystems IRIS® data platform
· InterSystems IRIS® for Health
· InterSystems Health Connect™

Versions:
· 2024.3.0
· 2025.1.0 – 2025.1.3
· 2025.2.0
· 2025.3.0

Operational: High Risk ≥ 2 TB of database cache is used

Issue

In the versions specified above, an instance may fail to start or may hang during operation if the database cache is greater than or equal to 2,097,152 MB (2 TB).

0
0 38
New
Announcement KC Lu · Mar 16

Since our previous announcement, we have introduced several incremental improvements to the client‑side editing experience in VS Code. These updates focus on preserving developer‑authored formatting when synchronizing with the server.

What Changed

Client‑side *.cls files previously lost certain formatting details during compilation, including keyword casing (e.g., classmethod → ClassMethod), normalization of blank lines between class members, and removal of line breaks within parameter lists.

1
0 41
New
Article Robert Barbiaux · Mar 16 12m read

There are lessons we learned from developing and maintaining code for interoperability components within a healthcare institutional environment.

The plane is already flying

Be prepared to rebuild, improve, extend, and fix the plane mid-flight.
 

Maintenance windows for hospital systems are often very limited, with some required to be operational 24/7. While the critical health systems such as imaging modalities or registration kiosks — or at least their critical functions — must operate autonomously, efficiency and usability may be compromised when interoperability components malfunction.

0
0 32
New
Discussion Raef Youssef · Mar 14

Hi community,

I've been working on a side project that I'd love to get some eyes on: a ground-up rebuild of the classic IRIS Production Monitor using a modern web stack. The existing ZEN/CSP-based portal does the job, but I wanted to explore what a contemporary, real-time version of it could look like.


What it is

A standalone Angular web application that connects to any Interoperability-enabled IRIS namespace and gives you a live view of your production — services, processes, operations, queues, event log, and message traffic — all in one screen.


3
0 133
New
Article Tani Frankel · Mar 15 1m read

As part of the new Interoperability UI wave (see what was new in 2025.1, and 2025.3 by @Aya Heshmat), v2026.1 which is available already as a Developer Preview, and this could be a reason for you to give it a ride - will be shipping the new UI for the Message viewing and searching, including Visual Trace (and other UI goodies).

He's a quick teaser:

0
0 63
New
Article Tani Frankel · Mar 15 1m read

As part of the new Interoperability UI wave (see what was new in 2025.1, and 2025.3 by @Aya Heshmat), v2026.1 which is available already as a Developer Preview, and this could be a reason for you to give it a ride - will be shipping the new UI for the BPL editor (and other UI goodies).

He's a quick teaser:

0
0 65
New
Article Andrew Sklyarov · Mar 14 6m read

I may have mentioned this before: I believe the Visual Traces, these sequence diagrams with full content of each step, are a fantastic feature of the IRIS Data platform! Detailed information about how the API works internally, as a visual trace, can be very useful for projects on the IRIS platform. Of course, this applies when we are not developing a high-load solution, in which case we simply don't have time for saving/reading messages. For all other cases, welcome to this tutorial!

0
0 62
New
Question Scott Roth · Mar 12

We are trying to track down significant growth within our Namespaces, one big culprit is Ens.AppData (EnsLib.SQL.Snapshot). 

Within many of our BPL's we use EnsLib.SQL.Snapshot to return Results from External SQL Stored Procedures or Query's. The same EnsLib.SQL.Snapshot context variable is used for many of these calls within a BPL. 

Is there something we should be doing at the end of the BPL to ensure that EnsLib.SQL.Snapshot gets cleaned up and purged from Ens.AppData?

1
0 25