• HealthShare Unified Care Record Overview – Virtual  May 19-20, 2026
  • Overview of HealthShare Unified Care Record® architecture, data flows, consent, and notifications
  • This 2-day course provides an overview of HealthShare Unified Care Record®. It focuses on architecture, data flows, consent, alerts, user management and terminology.
  • This non-technical course provides an introduction to the product for those who do not need the detail provided in the 5-day HealthShare Unified Care Record Fundamentals class.

Hi everyone,

I’ve been diving into the new IRIS 2026.1 features this week, specifically trying out the opt-in modernized Interoperability UI and the new DTL Explainer, but I’ve recently hit a persistent technical snag where the Management Portal becomes incredibly sluggish and my Terminal sessions start to experience significant input latency.

I am currently using a community setup to handle some automated local logging and script-based data scrubbing for my production archives in the background while I work.

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.

InterSystems has released IAM 3.10.0.9, which is a maintenance release of IAM 3.10 that includes significant fixes, including fixes for security vulnerabilities.

For those of you running older versions of IAM, we encourage you to start planning your upgrade. Customers upgrading from versions of IAM earlier than 3.10 must get a new IRIS license key to use IAM 3.10.  

IAM is an API gateway between your InterSystems IRIS servers and applications, providing tools to effectively monitor, control, and govern HTTP-based traffic at scale.

We are very excited to launch a new AI powered CCR feature which should help our users save time and prevent calls to Support.  Today we are introducing the new CCR Transport Log Analyst (or CTLA) AI-Generated summary.  The goal of CTLA is to provide an analysis of errors that have occurred in the Transport Log for a specific CCR, and advise the user as to what steps could be taken to correct the situation, as well as what might have been done to prevent it in the first place. When there is an issue with integrating or deploying a CCR, all of the details are captured in the Transport Log.

. . . you are not alone. 

Help is available.

This took me a while to figure out, and I assume there may be others struggling too. I made my way through all the Entra stuff to set up a client credentials workflow to send email through a Microsoft 365 account. I was able to successfully retrieve my token, but I couldn't ever get it to authenticate with the SMTP server using the %Net.SMTP class. There were two parts to fixing this.

First, the authenticator's access token needs to be more than JUST the access token. It has to be formatted as:

set smtp.authenticator.AccessToken = "user="_emailaddress_$C(1)_"auth=Bearer "_token_$C(1,1)

I am working on setting up OAUTH with FHIR and Microsoft Entra.  I have configured the Client and configured it in the FHIR Server successfully. However, I get 401 when authenticating with a token.   Looking at ^ISCLOG I see:
^ISCLOG("Data",9,0)="accessToken=<jwt token>, scope=, aud="
^ISCLOG("Data",10)=$lb(3,"OAuth2","[OAuth2.ServerDefinition:ValidateJWT]","171430","%SYS","2026-04-28 17:41:25.305549397","OAuth2.ServerDefinition.1","","zwKKakZZZx2")
^ISCLOG("Data",10,0)="JWT valid? sc=1"
^ISCLOG("Data",11)=$lb(3,"HSFHIRServer","[HS.FHIRServer.