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.
I'm approaching the need to send notifications through a Microsoft Exchange or Gmail servers. however my last foray into this, I was blocked due to an issue inside my SSL certificate is what I thought after the attempt.
So my attention will be on trying to match the cryptography in the SSL certificate I produce compared to the mail server I'm trying to use.
Has anyone else had an issue with this approach? My other option is Amazon SNS potentially. I do have a functional MS Teams channel for alerts, and can make different notification channels as well.
My team and I have a rare opportunity to start from scratch, and I am keen to know what things others that have gone through a similar process did differently. Obviously there's the immediate benefit of losing any technical debt that has built up over 10+ years of an ever changing environment along with many organisational changes and merges, but I'm thinking about the things that we can do to make life a lot easier for the next 10+ years.
We have a long running InterSystems Engine with an Interface Development Team. We have implemented basic interface and code development processes using mostly manually created helper tasks and functions. We are looking to upgrade these processes by installing and starting to use Embedded GIT in our DEV spaces first. We will not use it to deploy changes to PRODUCTION at first, keeping our same current process that the team is very comfortable with. We plan to start by using the BASIC mode in GIT, to avoid confusion over multiple branches and other version control functions.
Welcome back to a series of introductory articles on AI Hub, the new product feature currently in an early access program! (links: EAP Site for download, documentation)
In the last article, we covered how to create agents and agent tools directly in ObjectScript using the new %AI classes. However, sometimes, instead of creating a new agent, you just want to add some custom tools to an existing agent so you can ask your local claude code, codex, copilot or other agent of choice to query your data directly. This is where MCP Servers might come in.
In traditional InterSystems SQL, I can use the %NOINDEX keyword during a bulk INSERT to improve performance and then run BUILD INDEX %ALL afterward to populate the indices.
I am looking to implement a similar strategy for an InterSystems FHIR Server.
Is there a way to import/save FHIR resources while skipping the search table extraction (the FHIR version of %NOINDEX)?
Once the data is loaded, what is the correct programmatic way to "rebuild" the search tables?
Interoperability metrics were enabled for a production using ##class(Ens.Util.Statistics).EnableSAMForNamespace(). However, after running DisableSAMForNamespace() and DisableStatsForProduction(), the metrics continue to appear in the endpoint output.
Is there a way to completely stop these interoperability metrics from displaying in the API metrics stream? Is there an additional step or cache clear required?
I made a custom application metric, imported it to the USER namespace and used:
set status = ##class(SYS.Monitor.SAM.Config).Add.ApplicationClass("historymonitor.errorSensor", "USER")
to add it. When I do 'w status' it returns 1 so it is added but I still can't see the custom metric in the api/monitor/metrics endpoint. Even though I added %DB_USER in the application roles for api/monitor.
Does anyone know where the problem might be that the metrics endpoint still doesn't show my metric?
We have a task that runs objectscript code to load data into a linked external table. After upgrading from 2024.1 to 2025.1, the load is throwing an error, with error code -400, and no error message. The data DOES get loaded into the external table in its entirety, so with no meaningful error message, its hard to determine what the issue is. The result is the same with and without the USING clause, so don't let that confuse you.
The external is requesting me to send messages with the following structure (using the auto-generated SOAP Bussiness Operation from the WSDL), as you see they need a custom http header titled "Appian-API-Key", as the following:
You may notice when upgrading to IRIS For Health from 2024.1 to 2024.2+ (2025.1, 2026.1, etc.) that where you were previously accessing your FHIR Portal you are now receiving Not Found.
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.
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.
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.
UPDATE: since version 0.0.4 of the extension was published on 2025-11-23 it is now possible to use gj :: configExplorer directly in VS Code on Windows.
In my previous article introducing gj :: configExplorer I flagged up how an apparent bug in the Windows elements of the Native API for Node.js means it's not currently available to run in VS Code on a Windows desktop. In a comment on that article I offered a workaround, but this requires a Docker-equipped Linux host you can SSH to.
If you don't have a suitable target it's now possible to leverage your local Windows Docker Desktop.
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.
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
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
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.
I’m thrilled to share that after several years of deep diving into the InterSystems IRIS data platform, I have finally summarized my project experiences into a new book IRIS (Data Platform) Programming Technical Guide. It is published by Beihang University Press, a prestigious central-level comprehensive publisher renowned for its leading role in aerospace, science, and technology publishing.
Writing this book was a significant engineering challenge for me. My goal was to bridge the gap between "understanding the syntax" and "building a production-ready project.
Create an operational data store using the data flowing through your production. Create user-defined analytics tables based on fields and paths to their data from incoming documents with varying standards (FHIR, CDA, HL7v2, etc.).
Discover how to accelerate cloud-based integration with InterSystems' native AWS adapters for S3, SQS, SNS, and CloudWatch.
This session provides a practical look at building modern interoperability workflows — from secure file ingestion and asynchronous messaging to automated notifications and centralized monitoring.
.png)
