.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.
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:
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.
Hey Community,
We're pleased to invite everyone to the upcoming Kick-off Webinar for InterSystems Programming Contest: AI Agents for FHIR!
Date & Time: Tuesday, May 26 – 12 pm EDT | 6 pm CEST
Hi Community,
Do you build and manage applications with InterSystems IRIS SQL?
🎓Two tiers of certifications—specialist and professional (new!)—are now available!
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.
Hi Community,
Stay ahead with content relevant to your role and goals with the InterSystems Learning Services newsletter!
See how to customize your journey! 👇
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.
Thanks in advance!
Hello Community!
We’re excited to invite you to our upcoming Hebrew webinar, presented by @Keren Skubach, an InterSystems Senior Sales Engineer:
👉A Practical Guide to Leveraging AWS Adapters and APIs 👈
📅 Date & time: June 2nd, 3:00 PM IDT
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.