#Health Connect

#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.

• 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

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

• July 2026: first maintenance release for IRIS 2026.1 (planned version: 2026.1.4)
• October 2026: next maintenance release (planned version: 2026.1.5)
• February 2027: following maintenance release (planned version: 2026.1.6)

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.

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.

The 2026.1 release of InterSystems IRIS® data platform, InterSystems IRIS^® for Health, and InterSystems Health Connect™ is now Generally Available (GA). This is an Extended Maintenance (EM) release.

Hi Community,

Take a look at these new videos in online learning, and get familiar with new features and interfaces in the latest release of InterSystems® products. All videos are also available in the Learning Services YouTube channel.

Plus, check out a video for new ObjectScript developers, and a guide for HealthShare® users upgrading their deployments.

• Goal: Learn about enhancements to the interoperability UI in version 2026.1 of InterSystems products.

The 2025.1.4 and 2024.1.6 maintenance releases of InterSystems IRIS^® data platform, InterSystems IRIS^® for Health, and InterSystemsHealth Connect™ are now Generally Available (GA). These releases include the fixes for a number of recently issued alerts and advisories, including the following: 

• April 15, 2026 – Alert: Removal of InterSystems IRIS for Health and Health Connect 2024.1.4 and 2024.1.5 Due to Health Interoperability Issues | IDC

Summary

Issue

• The impacted versions of InterSystems IRIS for Health and Health Connect are being removed from WRC distribution sites due to issues identified in several FHIR and healthcare interoperability features.

Summary

Issue

• Deployments do not serve FHIR Server, bulk FHIR, FHIR SQL, or associated security user interfaces when using a non-default path prefix. For example, when using logical path configurations with Windows IIS, Apache, or other web servers.

This past weekend we ran into something odd. When we failed over our mirror from 2022.1.3 to 2025.1.3 the one of the Business Rules that was on what became the Primary (2025.1.3), had a rule within it that was removed back in January. When the Failover occurred, we had to scramble to backup, disable, and remove the Rule that shouldn't have been there. 

Both the Data and Code live within the same IRIS.dat that is the main MIRROR database for that Namespace. 

If this happened to one Class file, could it happen to others we do not know about?

We are working on Disk Consolidation and looking at Class/Globals that are rather large and not being cleaned up by the nightly Purge process. We have implemented DeleteHelper - A Class to Help with Deleting Referenced Persistent Classes | IDC on any Custom Data Classes, and Business Processes (BPL).

We have a bunch of Data Classes, BPL's, and Operations that connect to external MS SQL Server using JDBC to query or write data to using Stored Procedures and Queries. All that Query external tables are using EnsLib.SQL.Snapshot, and this is being written to ^Ens.AppData which is not cleaned up.

Summary

Issue

An issue has been identified in the HL7-to-SDA3 transformation logic that can cause an infinite loop when processing certain medication-related HL7 messages.

Our Pharmacy team would like us to convert...

¼ test character and ½ test character and ¾ test character and

to more like 

1/4 test character and 1/2 test character and 3/4 test character and

Is this possible?

v2026.1 was just released as GA, and one of the features I'm looking forward to using is the DTL Explainer feature.

This allows you to take a Data Transformation, and with a click of a button get a human-readable description of the transformation (which you can also use as the basis for the DTL Description).

For complex DTLs, especially ones you didn't write yourself, or you did but a long time ago, this will allow you to get a clear quick understanding of what it's doing.

The 2023.1.7 maintenance releases of InterSystems IRIS^® data platform, InterSystems IRIS^® for Health, and InterSystems Health Connect™ are now Generally Available (GA). 

Please share your feedback through the Ideas Portal using the category Post-Release Feedback so we can build a better product together.

Documentation

You can find the detailed change lists & upgrade checklists on these pages:

• InterSystems IRIS
• InterSystems IRIS for Health
• HealthShare Health Connect

Early Access Programs (EAPs)

There are many EAPs available now. Check out this page and register to those you are interested.

The Interoperability user interface project has continued from 2025.1 and has incorporated many of the items that you – our customers and partners – have suggested and observed.  We are continuing to invest in feedback and updating this important user experience.  In the latest release, 2026.1 for IRIS, IRIS for Health, Health Connect and Health Connect Cloud, the BPL Editor and Message Viewer/Visual Trace applications are now available for opt-in!
NOTE:

• Existing users can switch between the modernized and standard experiences.

As you all probably know, Health Connect / IRIS for Health natively supports DICOM messaging, and many of you will have used it daily. Well, I recently discovered a rather insidious little issue that our beloved @Alberto Fuentes gave me the solution.

We (I) will call this phenomenon the Creosote effect (those of you who know Monty Python will understand the reference, for the rest you can see the sketch here )

Mr.

Hello Community!

We're pleased to invite you to the upcoming webinar in Hebrew:

👉Getting Started with OAuth 2.0 on InterSystems👈

📅 Date & time: March 25th, 3:00 PM IDT

While reviewing our Orphan messages, we noticed that there are some Orphans that look like they are the start of an HL7 message.

MSH|^~\&

Since this does not link to any Message Header, and most of the information in EnsLib_HL7.Message is NULL, is there a way to track down what Object maybe creating these so we can nip it in the bud.

Only way that I know of is to go through each of our Schema's and make both the MSH and Encoding Characters optional.

Issue

In the versions specified above, an instance may fail to start or may hang during operation if the database cache is greater than or equal to 2,097,152 MB (2 TB).

I have an issue and can't seem to find the problem.

Issue

 In some namespaces i get a 403 Page not Found error for healthconnect/csp/healthshare/[NAMESPACE]/%25ZEN.Dialog.namespaceSelect.cls ; healthconnect/csp/healthshare/[NAMESPACE]/%25ZEN.Dialog.finderDialog.zen  && healthconnect/csp/healthshare/[NAMESPACE]/_CSP.UI.Portal.About.zen

Iris setup

It is currently configured in a mirror group and on the other mirror-member i don't encounter the issue. (I have checked if it was because of the member-type Primary and Backup). 

The user that I am using has the %All role.

As part of the new Interoperability UI wave (see what was new in 2025.1, and 2025.3 by @Aya Heshmat), v2026.1 which is available already as a Developer Preview, and this could be a reason for you to give it a ride - will be shipping the new UI for the Message viewing and searching, including Visual Trace (and other UI goodies).

He's a quick teaser: