InterSystems IRIS globals are one of the platform's core strengths: they store hierarchical data in a direct, ordered, and efficient structure. But when working from Python, manipulating globals can sometimes feel closer to a low-level API than to the natural habits of the language.
The iris-global-reference project provides a Python layer on top of IRIS globals. Its goal is simple: make access to globals more readable, more idiomatic, and easier to integrate into modern Python code, without hiding the underlying hierarchical model.
If one of your packages on OEX receives a review, you get notified by OEX only of YOUR own package. The rating reflects the experience of the reviewer with the status found at the time of review. It is kind of a snapshot and might have changed meanwhile. Reviews by other members of the community are marked by * in the last column.
Over the years, we keep monitoring Orphan Messages, and I have begun to notice the number of ACK/NCK's that do not match the Scheme in which the message was sent so it can't not align or signify that the message was OK. For example, if we send an ADT^A08 HL7 message to the vendor, and they send back a A08 instead of an ACK as the message type.
Currently our default is to have Save Replies on EnsLib.HL7.Operation set to IndexNotOk's.
InterSystems is pleased to announce the general availability of:
InterSystems IRIS Data Platform 2026.1.0.237.3
InterSystems IRIS for Health 2026.1.0.237.3
HealthShare Health Connect 2026.1.0.237.3
This release adds support for the Ubuntu 26.04 operating system. Ubuntu 26.04 includes Linux kernel 7.0, security improvements, along with installer and user interface improvements.
We are only releasing IRIS for Intel/AMD (x86_64) processors at this time. We've seen occasional network problems on ARM servers.
The InterSystems Learning Services Certification Team is pleased to announce the release of our second TrakCare / IntelliCare certification exam - the InterSystems EHR Integration Specialist exam. A big thank you to everyone in the community who helped us beta test!
The exam is now available for purchase and scheduling in the InterSystems exam catalog. Potential candidates can review the exam topics and the practice questions on the exam's homepage.
Currently, my Caché code triggers an email using Basic Authentication. Now Microsoft is going to stop Basic SMTP Authentication. In this case, what is the best approach to trigger an email alert from the database? It seems OAuth 2.0 is the best approach. Do anybody have any sample using Azure Entra ID?
This certification is intended for InterSystems EHR application specialists who use Tier 2 CCRs to manage and deploy configuration changes across environments. The content covers CCR fundamentals through Tier 2–specific topics.
This program turns ideas from the Ideas Portal into real applications published on Open Exchange while rewarding developers with points, badges, visibility, and recognition across the ecosystem 🚀
I’m exploring deployment options for InterSystems IRIS in cloud environments such as AWS or Azure.
What deployment architectures, scaling strategies, or infrastructure best practices are commonly recommended by the community? I’d also appreciate guidance regarding high availability, backups, and monitoring in cloud-based deployments.
What logging and auditing strategies are commonly recommended for InterSystems IRIS environments?
I’m interested in learning about best practices for tracking user activity, troubleshooting issues, monitoring integrations, and maintaining compliance in enterprise or healthcare systems.
Are there built-in tools or external integrations that work especially well for this purpose?
The competition brought together outstanding publications, each showcasing expertise and innovation. With so many high-quality submissions, selecting the best was a true challenge for the judges.
Let's meet the winners and look at their articles:
I’m looking for recommendations to improve interoperability performance in InterSystems IRIS, especially when handling large volumes of HL7 or healthcare-related messages.
What are the best practices for optimizing productions, business services, operations, and message processing performance? I’d also like to know if there are recommended monitoring tools or settings commonly used in production environments.
I’m currently working with REST APIs in InterSystems IRIS and would like to better understand the recommended security practices for production environments.
I’m especially interested in:
Authentication and authorization methods
Token management strategies
Role-based access control
API gateway recommendations
Encryption and secure communication practices
Monitoring and logging for API activity
I would also appreciate learning about common mistakes to avoid when deploying APIs publicly or integrating with external systems.
What approaches or tools have worked best in your environments?
I'm running a shell script and the q isn't exiting the screen. this is RHEL 7.9 I used to issue in VMS just fine but we have found that Linux scripts behave different. after these run I search the file for the status and depending on what it comes back with it will send an email.
I’m looking for practical recommendations to monitor InterSystems IRIS performance in a production environment. What are the most useful built-in tools, metrics, or best practices to track system health, database performance, and possible bottlenecks?
I would also like to know if there are recommended dashboards, logs, or monitoring integrations commonly used by the community.
What's the most straight-forward way to install this on an offline server? I'm trying to set this up on an Azure DevOps server to support our CI/CD pipelines. I've tried using zpm installing the tgz from the local filesystem. I note zpm seems to need a repo configured to install but I can't work out how to setup a bare-bones Filesystem repo (please point me to some documentation on this). I have no idea what I'm doing...
Common Table Expressions (CTEs) provide a structured framework for defining reusable intermediate result sets within SQL statements. InterSystems IRIS implements CTEs via the WITH clause, enabling clearer query composition and modular analytical processing while remaining fully integrated with the IRIS cost-based optimizer.
This article explores the semantics of CTEs in InterSystems IRIS, explains their interaction with query optimization, discusses appropriate deployment scenarios, and presents executable examples illustrating practical patterns for production environments.
ExplantIQ is an intelligent data application that tackles one of healthcare's most overlooked financial and regulatory risks: the management of explanted medical device warranty credits. When an implanted device is removed from a patient (due to failure or recall) hospitals are legally required to pursue manufacturer credits, refund payers if the credit exceeds 50% of the device's cost, and report to CMS. Miss that obligation and you're facing a reverse False Claims Act violation. Industry data shows hospitals miss 81% of eligible credits.
ExplantIQ, built entirely on InterSystems IRIS for Health and DeepSee, solves this by unifying clinical, supply chain, billing, and FDA recall data into a single real-time compliance dashboard, complete with KPI scorecards, trend analytics, and a Text-to-SQL AI Assistant that lets compliance officers query live operational data in plain English. No separate BI tool. No additional architecture. All questions can be answered without leaving your browser tab.
Health Galaxy creates an AI access point on top of any FHIR server, bringing healthcare into the AI future that has become a reality for many other industries.
AI access: Health Galaxy gives AI agents a single gateway into any healthcare system, so they can pull patient data, schedule appointments, and check insurance automatically instead of a human doing it manually.
Ease of use: You point it at an existing FHIR endpoint, click a button, and it generates an MCP endpoint automatically from the capability statement.
FHIR: Since we are using FHIR, we can leverage both the storage and exchange capabilities of InterSystems IRIS.
🗣 Presenter: @Zelong Wang, Sales Engineer at InterSystems
We are using IRIS for Health to develop an agentic AI chatbot workflow that can interact with a patient using voice commands, reach out to an EHR or other system for context, and provide recommendations back.
Presenters: 🗣 @Vic Sun, Sales Engineer at InterSystems 🗣 @Brad Nissenbaum, Sales Engineer at InterSystems 🗣 Danielle Micciantuono, Clinical Solutions Specialist at InterSystems
When building a Production, should I create separate message classes for each integration flow, or is it acceptable to reuse generic request/response classes across different Business Operations? I'm trying to understand how to keep things organized as the number of integrations grows.
What is the recommended way to handle errors inside a Business Process in IRIS? Should I use Try/Catch within the BPL, return error responses to the caller, or rely on the built-in retry mechanism of the Production? Looking for guidance on what's considered good practice.
