.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.
Hi, every one. Again, it's me!!😀😀
Recently I was trying to organize some learning materials for InterSystems IRIS😆, and realized that the resources are actually quite scattered.🤐
So I put together a list here—grouped by categories—for anyone who:
Also adding some of my own experience on what worked (and what didn’t, may be only not work for me🤫🤐).
If you don’t know where to begin, start here:
|
Advisory ID |
Product & Versions Affected |
Risk Category & Score |
Explicit Requirements |
|
IF-9396 |
InterSystems IRIS® for Health InterSystems Health Connect™ versions |
System Stability Concern: 3 |
Deployments with non-default path-prefixes will not serve FHIR Server UIs. |
This past weekend we ran into something odd. When we failed over our mirror from 2022.1.3 to 2025.1.3 the one of the Business Rules that was on what became the Primary (2025.1.3), had a rule within it that was removed back in January. When the Failover occurred, we had to scramble to backup, disable, and remove the Rule that shouldn't have been there.
Both the Data and Code live within the same IRIS.dat that is the main MIRROR database for that Namespace.
If this happened to one Class file, could it happen to others we do not know about?
Hi Community,
In our two preceding articles, we explored the fundamentals of the Interoperability Embedded Python (IoP) framework, including message handling, production setup, and Python-based business components.
In this third piece, we will examine advanced methodologies and practical patterns within the IoP framework that are pivotal for real-world interoperability implementations.
We will explore the following topics:
✅ DTL (Data Transformation Language) in IoP
✅ JSON Schema Support
✅ Effective Debugging Techniques
Collectively, these features help us create maintainable, validated, and easily troubleshootable production-grade interoperability solutions.
Claude Code has a strong understanding of IRIS, but unexpected issues still occur.
The first issue is one that has already happened several times and is likely to continue occurring if not properly addressed.
In IRIS, the collation for string data (%String) is set to SQLUPPER by default. As a result, when data is retrieved via SQL, it may be returned in uppercase (for example, when sorting and aggregating with GROUP BY).
Since I started using Claude Code, my motivation to create things has skyrocketed.
Previously, even if I wanted to build something, actually doing the coding felt like a hassle, so unless there was a very strong need, I rarely went as far as programming. But now, if I just jot down the specifications, Claude Code handles the rest automatically, resulting in a dramatic improvement in productivity.
I come from a generation native to ObjectScript, so I used to feel some hesitation when it came to switching to Python.
Is there a way to delete a message in a routing rule? For example, an HL7 message doesn't qualify for a rule, but instead of the message being passed on to the next rule, you delete the message.