Skip to main content

HealthShare® Health Connect Cloud Upgrade Checklist (2026.1)

This document is meant to help you assess the impact of moving your code to the HealthShare Health Connect Cloud 2026.1.0 cloud maintenance release. It lists the incompatibilities since 2025.1.0. These incompatibilities may require changes to code, configuration, or operation.

To see the incompatibilities between your current version and the current release, use the Upgrade Impact Checklist.

InterSystems News, Alerts, and Advisories

From time to time, InterSystems publishes items of immediate importance to users of our software. These include alerts, mission-critical issues, important updates, fixes, and release announcements. You can obtain the most current list at https://www.intersystems.com/support-learning/support/product-news-alerts/Opens in a new tab. InterSystems recommends that you check this list periodically to obtain the latest information on these issues.

Gateways - IRIS

DP-444395: Change property AllowedIPAddresses to BindToIPAddress

Category: Gateways - IRIS
Platforms: All
Version: 2025.3.0

This change alters the name of a property of External Language Servers. The property previously known as "AllowedIPAddresses" is now "BindToIPAddresses". An alias between this new name and the old one has been added, so if you are modifying an External Language Server definition through the %Net.Remote.ObjectGateway class, your configuration will continue to work. However, if you modify External Language Servers with %DynamicObject, your code must be updated to use the new property name.

Interoperability

DP-439825: Visual Trace does not show all events

Category: Interoperability
Platforms: All
Versions: 2024.1.6, 2025.1.3, 2025.2.0

Previously, when there were more than 1,000 entries in the log table, the visual trace of a session might not have shown all of the events in the session, even if that was the configured behavior. Now, every event is always shown, so previously set values for LimitEvents and EventsMaxRows in ^EnsPortal.Settings are overridden.

DP-440718: [Interoperability] Amend FunctionSet class container identification

Category: Interoperability
Platforms: All
Version: 2025.2.0

If a Custom Utility Function class that mistakenly extends superclasses other than Ens.Rule.FunctionSet (and those super classes themselves do not extend Ens.Rule.FunctionSet) has been created, then any class methods in those superclasses cannot be used in Rules.

Code generated for Rules now uses the class where the class method is defined, not a subclass.

DP-440887: Deprecate EnsLib managed Gateways

Category: Interoperability
Platforms: All
Version: 2025.2.0

The server and port properties of the EnsLib.Gateway.*, EnsLib.JavaGateway.*, and EnsLib.DotNetGateway.* classes are now deprecated, so users should instead migrate to interact with gateway services through an External Language Server.

DP-443153: [Interoperability] Amend resource protecting Export For Deployment in Production Config page

Category: Interoperability
Platforms: All
Version: 2025.3.0

Sites that had granted users who should be able to export for deployment packages from the Production Configuration page will need to grant such users %Ens_DeploymentPkg:USE and may be able to remove %Ens_Deploy:USE. This only concerns the Zen Production Configuration page.

DP-443265: [Interoperability] Ensure Document TimeStamp is empty for non existent Lookup Table

Category: Interoperability
Platforms: All
Version: 2025.3.0

The document TimeStamp value for the projected Lookup Table document for a non existent or no named Lookup Table was previously returned as the current time. This is now corrected, and returns an empty string in line with other Interoperability projected documents. Any manually created workarounds should be reverted.

DP-443464: [Interoperability] Correct error thrown by X12 parser

Category: Interoperability
Platforms: All
Version: 2025.3.0

An issue that could cause the X12 parser to throw an UNDEFINED error when the binary data length field contained a value greater than the actual length of the binary data has been resolved. The parser now returns the error BinaryDataShort instead.

DP-444481: Alter setting in Kafka outbound adaptor

Category: Interoperability
Platforms: All
Version: 2026.1.0

In the Kafka outbound adaptor, the ClientID setting has been renamed to ProducerClientID. If you had previously set ClientID, use the new method in Ens.Director to remove that setting. See [Adding and Removing Settings](https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=EGDV_settings_removeprog) for more details.

DP-445034: Interoperability: Change default value of ^Ens.Configuration setting KeepInQueues to true

Category: Interoperability
Platforms: All
Version: 2026.1.0

This change sets the default value of the ^Ens.Configuration setting KeepInQueues to "true", meaning that when a production is stopped, messages are kept in ^Ens.Queue by default rather than moved to ^Ens.Suspended. If you relied on the previous behavior, you must manually set ^Ens.Configuration("Queues","KeepInQueues") to 0 in each relevant namespace.

DP-445471: Correct EnsLib.PubSub.Utils AddSubscriber

Category: Interoperability
Platforms: All
Version: 2026.1.0

Previously, the EnsLib.PubSub.Utils:AddSubscriber() method did not correctly use the first parameter for DomainName, so the created Subscriber object did not have its DomainName property set. Any workaround in custom code that adds the DomainName property after this call should be removed.

DP-445779: SAP Operation creates connection file in mgr directory and only uses External Language Server name

Category: Interoperability
Platforms: All
Version: 2026.1.0

This change ensures that the system correctly locates an SAP connection file in the instance’s mgr folder.

Additionally, an SAP operation works with a JavaGateway service only if the service specifies a valid External Language Server name. Specifying server and port is no longer sufficient. The preferred usage for EnsLib.SAP.BootStrap:ImportSAP() is to now use pPort="" and pAddress="".

Networking

DP-435478: %Net.SSH.Session:Connect to use SHA256 for default hostkey hash

Category: Networking
Platforms: All
Version: 2025.2.0

New %Net.SSH.Session objects by default have a SHA256 hostkey. If you need a different size, you must pass "SHA1" or "MD5" as an argument to the Connect() method manually.

Object Library

DP-441221: Export methods should respect /createdirs qualifier

Category: Object Library
Platforms: All
Version: 2025.2.0

This change modifies the behavior of ExportXMLList^%apiOBJ and ExportXMLPackage^%apiOBJ so that they explicitly check for the /createdirs qualifier before calling CreateDirectoryChain() to create a directory. Any usage of these routines that do not use the /createdirs qualifier may have some commands fail.

DP-446764: %Net.URLParser Compose and Decompose bug fixes

Category: Object Library
Platforms: All
Version: 2026.1.0

This change removes support for path segment parameters and non-digit ports in %Net.URLParser.

Additionally, URL queries are no longer decoded automatically; instead, the Decompose() method decodes keys and values into Components("query",i,"key") and Components("query",i,"value"), where i is the position of the key-value pair.

Also, the netloc, username, password, host, port, query, and fragment components no longer treat the empty string as undefined. To properly remove these components, you must issue a kill command.

ODBC

DP-437848: Enforce BufferLength in SQLBindParameter function

Category: ODBC
Platforms: All
Version: 2025.2.0

When binding parameters with the SQLBindParameter function, the system previously ignored the BufferLength parameter. Now that the parameter is enforced, any invocations of the SQLBindParameter function that use the BufferLength parameter will truncate data to the specified length.

DP-443339: ODBC: SQLGetData from binary fills only BufferLength-1 bytes

Category: ODBC
Platforms: All
Version: 2026.1.0

Previously, if the BufferLength was smaller than the fetched data length when requesting characters from binary data using the ODBC SQLGetData function, the entire BufferLength was filled with data. Now, the function fills the buffer with data up to BufferLength-1 bytes and sets the last byte to the null character ('\0'). Code that expected the entire buffer to be filled with data should be modified.

Security

DP-446954: %CSP.REST:DispatchRequest() is final

Category: Security
Platforms: All
Version: 2026.1.0

The %CSP.REST:DispatchRequest() method is now marked as final and can no longer be overridden. Any REST dispatch class that overrides this method will no longer compile.

SQL

DP-422287: Update CREATE FOREIGN TABLE behavior

Category: SQL
Platforms: All
Version: 2025.2.0

The point of failure for some ill-formed foreign tables has been moved from query-time to create-time. As a result, some CREATE FOREIGN TABLE statements that previously succeeded could now fail. However, these failures typically indicate that a SELECT statement against the foreign table would have failed anyway.

To prevent the possibility of these validation runtime errors during a CREATE FOREIGN TABLE statement, use the NOVALIDATE keyword.

This change in behavior only applies to foreign tables that use other database management systems as their external source; schema validation is not performed when creating file-based foreign tables.

DP-434312: inherit the CALCSELECTIVITY parameter from the super field

Category: SQL
Platforms: All
Version: 2025.2.0

If you add CALCSELECTIVITY=0 on a property that is an embedded object, the system no longer calculates statistics both for that property and for the corresponding serial object properties. For example, if you have a class Sample.Person with a field Home, which is of type Sample.Address, and assign the Home field CALCSELECTIVITY=0, then no stats will be collected for Home or any of the serial object properties for Home.

DP-439031: $IsVector(null string) will be True

Category: SQL
Platforms: All
Version: 2025.2.0

$IsVector("") now returns 1, rather than 0. The new behavior better conforms to expectations set by other $vector functions, which treat "" as a valid vector.

DP-441931: Changes to JSON Path Language expressions to align with standards

Category: SQL
Platforms: All
Version: 2025.3.0

This change resolves discrepancies between the implementation of the JSON Path Language (used in the JSON_TABLE SQL function) and the ISO SQL Standard. In particular, it corrects the results returned when applying the member wildcard to the context value. Array accessor expressions are also affected. Any JSON Path Language expressions that use these elements may need to be modified accordingly. See the documentation for more information.

DP-443617: Change in when ROWLEVELSCURITY parameter defines the %RLI index

Category: SQL
Platforms: All
Version: 2025.3.0

The %RLI index is generated automatically only when the ROWLEVELSECURITY class parameter is set to 1. If this parameters is set to any other value, the index is no longer generated automatically, which may affect performance. To ensure the %RLI index is defined in this version, set the ROWLEVELSECURITY class parameter to 1.

DP-447884: Recompilation required to correct concurrency issue inserting into child tables

Category: SQL
Platforms: All
Version: 2026.1.0

This change corrects a concurrency issue in which two or more processes attempting to insert a row into a child table encountered lock timeouts and failed to insert the row.

As a result of this change, you must recompile all of your classes. Failure to do so may result in errors due to a change in the signature of an internal method.

System

DP-434146: Operational considerations for upgrade to Extended Database Sizes

Category: System
Platforms: All
Version: 2026.1.0

This version introduces the capability to expand databases beyond the old size limits (which were approximately 32TB for 8KB blocks, 64TB for 16KB blocks, 128TB for 32KB blocks, and 256TB for 64KB blocks). No data conversion is necessary. When this capability is enabled, existing databases can simply expand beyond the old size limit.

This capability is enabled by a new systemwide setting (ExtendedDatabaseSize), which is off by default. Before turning it on for a given system, you must first:

1. Upgrade any older-version ECP application servers, mirror members, or other systems that may need to mount a copy of the system's databases to at least version 2026.1. Once the new setting is enabled, individual databases may be marked as having an "extended format" when they approach the old size limit. Such databases would not be mountable on older versions of InterSystems IRIS, neither locally nor remotely via ECP. 2. Run an integrity check on all databases (perhaps as part of a standard system task) and check that there are no errors. This ensures that there is no corruption (previously benign) which could become problematic in the extended format. Use version 2026.1 or later to perform this check.

Read more about using this new parameter, including new Integrity Check errors and a new runtime safeguard warning, at [Extended Database Size](https://docs.intersystems.com/iris20261/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_extend_db).

DP-440592: Object could be closed with incorrect roles

Category: System
Platforms: All
Version: 2025.2.0

Previously, if an object in a REST application went out of scope while I/O redirection was active, its %OnClose method could be run with different roles than when it was created. That issue has been resolved, but the fix may cause an application with very deep nesting (large $STACK value) to encounter a error. If necessary, the frame stack size can be increased by getting the current size with $SYSTEM.Util.GetFrameStackSize() and setting a larger value with $SYSTEM.Util.SetFrameStackSize(). The new value will be in effect for all new processes, not just the current one.

DP-441122: Correct $THIS value in a class method

Category: System
Platforms: All
Version: 2025.2.0

Previously, the $THIS value in a class method could sometimes be an object reference, instead of the class name. If you wrote any class methods that used $THIS to refer to an object reference, you must change your code to access the object reference a different way.

Web Services

DP-437099: Correct inconsistency in CORS handling configuration

Category: Web Services
Platforms: All
Versions: 2024.1.4, 2025.1.1, 2025.2.0

Previously, CORS handling was inconsistent if a web application used map forwarding. In previous versions, the value of the HandleCorsRequest parameter in the dispatch class defined in the web application determined CORS handling, unless the route had Cors="true", in which case the HandleCorsRequest parameter in the final dispatch class (that is, the one that handles the request) would determine CORS handling.

With this change, the HandleCorsRequest parameter in the final dispatch class always determines CORS handling.

This change also requires that you recompile all existing REST web services upon upgrade.

For Additional Help

If you need assistance with evaluating how upgrading to this extended maintenance (EM) release will affect your applications, systems, or related plans, please contact the InterSystems Worldwide Support Center:

  • Phone:  +1.617.621.0700
  • Fax:  +1.617.734.9391
  • Email:  support@intersystems.com

Current release notes (and complete product documentation) can be found online at https://docs.intersystems.com.

FeedbackOpens in a new tab