InterSystems HealthShare Health Connect is a healthcare integration engine that delivers high-volume transaction support, process management, and monitoring to support mission-critical applications.
At the heart of Health Connect is a high-performance, multi-model data engine that seamlessly handles multiple forms of data at high speed. Health Connect easily scales from serving small clinics to handling the transaction volumes of the largest and most complex healthcare delivery systems in the world. Capabilities include:
In the upcoming 2026.2 release (now available as a preview) we are adding support for a specific case of a FHIR Read.
This is for the Binary Resource - when GETting a Binary Resource that has some MIME type, and the request Accept header also has the same MIME type, the content returned will not be the FHIR Resource (JSON) itself, but rather the actual binary content. See from the FHIR docs.
Hi Community,
Stay ahead with content relevant to your role and goals with the InterSystems Learning Services newsletter!
See how to customize your journey! 👇
One of the latest features I'm really looking forward to in v2026.2 (now available as preview) is the "FHIR Explorer".
This new capability, part of InterSystems' FHIR Server, allows users to explore FHIR data via a friendly and intuitive UI, that builds (possibly complex) FHIR Search URLs, runs it against your FHIR Server (actually any FHIR server...), and displays the results.
Here's a simple flow:
As part of a focus we are putting on improving the speed of ingestion of FHIR payloads, in v2026.2 (available as of now as a Developer Preview), we are introducing an option to skip structure validation of resources. This could save for example 25% of the time, which in large scale ingestions, could be significant.
Hi,
Just thought I'd share quite a handy hook that has helped me out when developing on Health Connect Cloud with VS Code and GitBash. When developing on Health Connect Cloud, if changes are made directly on the server such as routing rules or component deployments, they aren't automatically included in source control, therefore you must export from the server into your local files and push to your remote repo. I'm sure there are easier methods to deal with that which I'm in the process of testing, but as a quick solution I thought it would be handy have a pre-commit hook which triggers a reminder in GitBash - see below.
.png)
<UNDEFINED>ServerLoop+1^%SYS.DBSRV *%qlogging,ERROR <Ens>ErrOutConnectFailed: 'jdbc:opengauss://host:15400/healthcare_data' / 'NHIPProd' 的 JDBC 连接失败,出现错误 ERROR #5023: Remote Gateway Error: JDBC Gateway connection failed for jdbc:opengauss://172.17.211.39:15400/healthcare_data error: -1
Hey All!
I wanted to reach out and get some advice on the best way to interact with a external SQL database, as I'm finding the documentation quite confusing to follow. I'm new to using SQL within InterSystem, and I want to make sure I'm following the best practices.
In essence, what I am trying to achieve, is extracting certain values from a HL7 message and then insert those message field values into an external database. The ODBC, DSN and Credentials details are all setup and working correctly.
Using the SOAP wizard many moons ago, I had setup a process to get Patient Demographics, and the current Visit Location from Epic for processing HL7 DFT Charge Messages.
Within the past week we have had two cases where the Outbound SOAP Adapter has been throwing Errors (Exceptions) where in this case
NO-PATIENT-FOUND details: No patient found with the provided ID and ID type.
The error is not being sent back in the Response to the Business Process that sent the call. The Response comes back blank.
Hi all,
I'm looking for some advice on a DTL issue.
I'm working on an HL7 DTL where I need to populate MSH-6 / Receiving Facility using a combination of literal text and values from the PD1 Patient Primary Care Provider field.
The required MSH-6 value needs to be something like:
MCNIMCNumber.PracticeID
Where:
For the IMC number, the direct source path that works is:
source.{PIDgrpgrp().PIDgrp.PD1(3).assigningauthority.namespaceID}
If I assign this direct path straight into MSH-6, the value populates.
Amazon SQS (Simple Queue Service) is a managed message queue service that provides a simple, durable, and scalable mechanism for exchanging messages between applications. It is particularly well suited for event-driven integration patterns and loosely coupled architectures.
Bear in mind that the AWS SQS adapter is based on InterSystems PEX Network and requires the Java External Server to be enabled.
When using Amazon SQS you can either take the role of a Consumer or a Publisher.
I'm pleased to share that FHIR Agent Studio is now running as a live, hosted demo on the InterSystems Developer Cloud — no install, no setup, just open it in a browser.
FHIR Agent Studio is a developer portal for building, running, and inspecting AI agents for FHIR workflows on a single InterSystems IRIS for Health backend.
AI is going to change healthcare, but only if clinicians can trust it and developers can build it without reinventing the plumbing every time. FHIR Agent Studio is my attempt at both: a place to build AI agents for FHIR workflows from reusable building blocks, run them on a real InterSystems IRIS for Health backend, and inspect exactly what each one did at every step.
It is my entry in the InterSystems AI Agents for FHIR contest, and it ships with twelve working agents over a synthetic FHIR repository of around 1,000 patients and 20,000 resources.
We released the x64_64 Ubuntu 26.04 build back on May 21st. At the time we said that we were holding off on releasing ARM support due to come occasional network problems we found in testing. We've worked with Ubuntu to resolve those issues - a bug in a vendor's network driver - and are pleased to say...
InterSystems announces the general availability of:
This release adds support for the Ubuntu 26.04 operating system for both ARM and x86_64 processors
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.
I’m pleased to share a demo of FHIR Agent Studio, now available on YouTube.
FHIR Agent Studio Demo
https://www.youtube.com/watch?v=vktfq_kvNnk
FHIR Agent Studio brings AI agents together with FHIR, InterSystems IRIS, Vector Search, and large language models to demonstrate how developers can explore, build, and test agent-driven healthcare workflows.
You can also find more information here:
Introduction article: https://community.intersystems.com/post/introducing-fhir-agent-studio-ai-agents-fhir-intersystems-iris
GitHub repository: https://github.com/SeanConnelly/ai-studio-for-fhir
Hey everyone.
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.
Hi Community,
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.
%NOINDEX)?Thank you!
Hi Community,
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?
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.
#North American Demo Showcase entry.
>> Answer the question below to be entered in the raffle!
⏯️ HL7 Validation Error Profiler: Rapid Insights into Batch HL7 Data Quality Issues
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.
Special thanks to @Henry Wojnicki for his contributions to designing and refining the application workflow.
🗣 Presenter: @Lynn Wu, Sales Engineer at InterSystems
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.
1. vscode extensions : intersystems.language-server-2.8.0@linux-arm64.vsix
2. api/atelier web application is enabled
3. vscode connect failed.
The third developer previews of InterSystems IRIS® data platform, InterSystems IRIS® for Health, and InterSystemsHealth Connect™ 2026.1 have been posted to the WRC developer preview site. Containers can be found on our container registry and are tagged latest-preview.
These developer previews includes the dropping of Mac Intel support starting from 2026.1.0, and the adding back of Windows Server 2019 support to 2026.1.0.
Initial documentation can be found at these links below:
Was wondering if anyone had a Dynamic way to see if a Global is still being used by a Class File.
We have been monitoring our Global Size recently, and I am trying to find problematic Class files that are not being cleaned up or used appropriately. I have come across some globals that do not seem to have a Class attached to them anymore, and instead of deleting globals 1 by 1, I was looking for a way that we could dynamically do this since the globals have data that is stale in them.
Thanks
Scott
Below is an update to the IRIS release calendar for 2026 and an early look at the planned changes for 2027. The key takeaway for 2026 is that maintenance release numbering will differ slightly from prior years.
2026: IRIS 2026.1 maintenance release numbering
This numbering change prepares us for the expanded maintenance cadence planned for 2027.
In v2026.2 (currently available as a Developer Preview), we are adding a feature that can help in a FHIR Endpoint SMART/OAuth authorization - more out-of-the-box flexibility in audience value validation.
One of the recommendations when deploying InterSystems Technologies for production is to set up High Availability. The recommended API Manager for these InterSystems Technologies is the InterSystems API Manager (IAM). IAM (essentially Kong Gateway) has multiple deployment topologies.
If you are looking for high availability you could use:
a) Kong Traditional Mode: Multiple Node Clusters
b) Hybrid Mode
c) DB-less Mode
Before we break them down let's first understand the out of the box deployment that is provided by InterSystems: Installing IAM Version 3.10.
The Interoperability user interface now includes modernized user experiences for the DTL Editor and Production Configuration applications that are available for opt-in in all interoperability products. You can switch between the modernized and standard views. All other Interoperability screens remain in the Standard user interface. Please note that changes are limited to these two applications and we identify below the functionality that is currently available.
To try out the new screens prior to upgrading, you can download the 2025.
A very important feature for HL7 FHIR has been introduced with the release of v2026.1 - the support for SMART on FHIR v2 fine-grained granular Scopes.
This enables you to be much stricter and more accurate in the access you provide to the data in your FHIR repository.
Part of this new support is to refuse requests that don't match the scopes, but an even more interesting ability is to filter the results according to the provided scopes.