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.
We have another great initiative for you to sink your teeth into! Following last year's resounding success, we're hosting a new edition of the Demo Games. But with a twist: our North American Sales Engineers have submitted their best demo videos, but this time, you're the ones to take part and win a prize.
Please welcome the North American Demo Showcase! 🎉
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
This demo highlights how HL7 validation logs can be transformed into scalable, actionable data quality insights using a lightweight application built on top of Health Connect.
Batch ingestion and parsing of HL7 validation error logs into structured data
Aggregation of errors by segment, field, and type to reveal systemic issues
Interactive dashboard (Streamlit) for filtering, exploration, and root cause analysis
Rapid identification of top error patterns across entire data feeds
Natural language chatbot for intent-driven data investigation and querying
PDF report generation for sharing clear, evidence-based feedback during data source onboarding
Special thanks to @Henry Wojnicki for his contributions to designing and refining the application workflow.
🗣 Presenter: @Lynn Wu, 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
In this demo, you will see how Gemini works directly with FHIR data, and how it leverages the harmonized dataset provided by InterSystems Unified Care Record. It also showcases multiple AI assistants helping multiple groups of users, e.g. clinicians, patients.
🗣 Presenter: @Simon Sha, Sales Architect 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.
What is the recommended approach for handling upgrades in an InterSystems IRIS Kubernetes environment?
For example, if we deploy version 1.0.0 of our product and subsequently need to upgrade to 1.0.1, and this upgrade requires changes to SQL tables containing customer data.
The quickest solution that comes to mind is creating an 'upgrade method' that runs on startup to check if any data migration actions are required. However, I'm wondering if there are better solutions or established best practices for this.
What is the most efficient, memory-safe way to get the names of the corrupted indexes on very large tables for a rebuild. However, if an index has millions of corrupted rows, the .errors array in %ValidateIndices grows too large and throws a errorerror.
Hi! We are deploying the iris image in a Kubernetes environment and the cluster state is "Hung" , looking the alerts endpoint we get 2 alerts:
[ { "time":"2026-03-24T13:45:44.548Z", "severity":"2", "message":"System appears to have failed over from node a69a9f137593" }, { "time":"2026-03-24T13:46:30.274Z", "severity":"2", "message":"Error: <PROTECT>KillAlive+1^%SYS.CDIRECT in SERVERS" } ] Any idea / help where those are comming from and how to address them?
I recently started using Cursor/VSCode with an IRIS container for development rather than Studio/Terminal. I've noticed that whenever I use %G (so basically all the time), when I exit %G, the terminal window simply closes, rather than returning me to my usual namespace prompt. %G also does not retain the command stack like it does in old school terminal, so I'm forced to constantly retype every global reference. Anyone figured out a solution to this? It's a relatively minor problem in the grand scheme of things, but a time consuming and irritating one.
