HealthShare® Health Connect Change Notes (2026.1.1)

DP-448059: Return null axis in %GetBranchesForSlicer

Category: Analytics - MDX Engine
Platforms: All
Version: 2026.1.1

This change fixes the pBranch output of %DeepSee.Query.Engine:GetBranchesForSlicer() for plugins to properly reflect the slicer axis that has produced the null set. The previous output incorrectly signaled that there was no slicer in effect.

DP-448422: Fix check of abandoned KPI plugin cache to prevent execution stall

Category: Analytics - MDX Engine
Platforms: All
Version: 2026.1.1

Previously, there was an issue that could cause a plugin cache entry to be left in an in-process state without any process doing focused work. This change helps each plugin request identify this state when checking the cache to reset it and restart execution, if appropriate.

DP-448902: Update DataMove statistics more often if processing long strings

Category: DataMove
Platforms: All
Version: 2026.1.1

Previously, when attempting a DataMove on a global that only contained long strings, there was an issue that could prevent the system from updating the DataMove statistics or stopping the DataMove altogether. This change resolves these issues.

DP-449040: When DataMove stops with a recoverable error, set higher error level in Messages.log

Category: DataMove
Platforms: All
Version: 2026.1.1

When a DataMove encounters a STORE error while reading journal files, the error stops the DataMove entirely. In most cases, you can restart the DataMove to resume at the place it stopped. However, if you purge the journal file used by the DataMove before restarting it, you cannot restart the DataMove.

This change increases the severity of the error message provided when a DataMove encounters a STORE error to improve system alerting.

The previous error message was: 04/15/26-12:39:17:209 (21644) 0 [DataMove.Event] DataMove STC-ROLLBACK STOP signaled - Signaled by recoverable error

The new error message is: 04/15/26-12:39:17:209 (21644) 2 [DataMove.Event] DataMove STC-ROLLBACK STOP signaled - Signaled by recoverable error

IF-9283: $expand timestamp passes FHIR validation

Category: FHIR Server
Platforms: All
Version: 2026.1.1

Previously, issues with date-time data types caused errors when using $expand. These issues have been corrected.

IF-9364: ##class(HS.HealthConnect.FHIRRepo.Upgrade.V4)."Upgrade-HSSYS-2"() is now async

Category: FHIR Server
Platforms: All
Version: 2026.1.1

Previously, when a system had a massive number of orphaned search table rows, the ##class(HS.HealthConnect.FHIRRepo.Upgrade.V4)."Upgrade-HSSYS-2"() upgrade step took too long to complete, which could result in blocking the upgrade and extending downtime. Furthermore, because the delete was a single atomic SQL statement (and therefore in a transaction), being interrupted would trigger a rollback. This upgrade step is now async, which has corrected these issues.

DP-448527: Resolve issue with management of database buffers

Category: Global Module
Platforms: All
Version: 2026.1.1

This change resolves an issue in the management of database buffers that could lead the system to write to an incorrect image of a block during a write cycle under extremely rare circumstances. The issue had never been observed to occur.

DP-448898: Fix file compaction for $ZU-created empty databases

Category: Global Module
Platforms: All
Version: 2026.1.1

Previously, when file compaction was invoked with a requested free space equal to or greater than that of an empty database, the process could encounter a error due to underflow or, if ExtendedDatabaseSize is enabled, an infinite loop. This update ensures that file compaction stops safely before it reaches the conditions that trigger the error and infinite loop.

This issue is unlikely to occur in typical usage, as it only affects databases created through low-level $ZU calls rather than standard database creation APIs.

DP-449161: allow Manage^JRNROLL to handle rollbacks by NodeNameInPid jobs

Category: Journaling
Platforms: All
Version: 2026.1.1

Previously, if the CPF setting NodeNameInPid=1, Manage^JRNROLL cannot detect when the Mirror Manager process is performing a transaction rollback and so cannot skip this rollback during mirror start up. This issue has been resolved.

DP-449135: Better error message for misconfigured OS authentication

Category: Security
Platforms: All
Version: 2026.1.1

Previously, when OS authentication failed, the error message returned was "User @ is not defined." Now, the error message returned from such a failure is "Multiple domains are not enabled. O/S authentication for non-default domain cannot be used unless multiple domains are enabled."

DP-449534: Prevent Windows username parsing from spamming SYSLOG in non-domain environments

Category: Security
Platforms: All
Version: 2026.1.1

This change prevents the system from spamming to SYSLOG when trying to obtain the OS name of the current process. Previously, in such cases, the system would continually write unnecessary warnings to the SYSLOG in FAST environments, which are domainless, clashing with the expected formatting but causing no system issues. The issue is now resolved.

DP-446836: Fix ORDER BY processing in UNION queries for Sybase TSQL

Category: SQL
Platforms: All
Version: 2026.1.1

Previously, there was an issue that caused the system to incorrectly parse UNION queries that included ORDER BY clauses in Sybase TSQL, resulting in wrong results. This issue has been resolved.

DP-448681: Fix FRAMESTACK and MAXSTRING errors in queries with many WHERE conditions

Category: SQL
Platforms: All
Version: 2026.1.1

Previously, a FRAMESTACK or MAXSTRING error could arise when executing queries with thousands of WHERE conditions. This issue has been resolved.

DP-449056: Do not allow literal for target database in ALTER TABLE t MOVE PARTITION

Category: SQL
Platforms: All
Version: 2026.1.1

This change fixes a problem in which the target database name in the ALTER TABLE t MOVE PARTITION command was mistakenly allowed to be either an identifier (no quotes) or a literal (single quotes). With this change, the target database name is only allowed to be an identifier. If it is specified with single quotes, an error "IDENTIFIER expected, LITERAL ('TargetDatabaseName') found" is returned.

DP-449068: Verify the existence of RTPC condition to prevent UNDEFINED error

Category: SQL
Platforms: All
Version: 2026.1.1

Previously, there was an issue that would return an UNDEFINED error when compiling a SQL query when table statistics were present. In particular, the UNDEFINED error could arise when the system would check for a selectivity value for an equality condition in a JOIN field.

DP-449170: Correct parsing of stored procedures

Category: SQL
Platforms: All
Version: 2026.1.1

Previously, there was an issue that caused statements that created stored procedures to fail by incorrectly parsing the defined procedure. The issue has been resolved.

DP-449345: Adjust query plan cost calculation to select most efficient plans

Category: SQL
Platforms: All
Version: 2026.1.1

This change resolves an issue that caused queries, such as those with TOP, ORDER BY ID, and ASC/DESC clauses, to default to using a query plan that employed table scans, rather than more targeted map scans.

DP-449412: Fix ALTER TABLE t CONVERT PARTITION BY for partition key fields with names not all lower case

Category: SQL
Platforms: All
Version: 2026.1.1

This change resolves an issue that caused ALTER TABLE t CONVERT PARTITION BY partition-key-field would fail if the partition key field's actual name was not all lower case (regardless of what case was used to specify the field's name in the ALTER TABLE command).

DP-448526: Fix unprotected pointer reference in event message allocation

Category: System
Platforms: All
Version: 2026.1.1

This change corrects a issue where $SYSTEM.Event.Signal(pid, message) could crash (with a segmentation fault or access violation) if it was passed a message within a certain size range and the shared memory heap did not have sufficient memory for the message. Now, this case correctly fails with a <STORE> error.

DP-449487: Completely validate BPL using schema prior to save

Category: UI - BPL Editor
Platforms: All
Version: 2026.1.1

When attempting to save a BPL, the system performs validation by using the Ens.BPL.Process class's Validate() method. Previously, this method did not fully validate that the BPL adheres to the schema specification in Ens.Schema.BPL, allowing a user to save an invalid schema and causing failures when trying to open this BPL later. This issue has been resolved by perfoming a full validation when the BPL is saved.

DP-449352: Fix issue with code used in VS Code debugger

Category: VS Code
Platforms: All
Version: 2026.1.1

Previously, running the VS Code debugger on a .int file would execute lines of .int code after translating them to the corresponding .cls code. Since this conversion is not always available, the debugger could occasionally highlight uselines of .cls code in the UI. Now, if there is no .cls code that corresponds with .int code, the debugger uses the .int code.

DP-449444: Admin APIs Request Body Validation Fixes

Category: Web Services - REST
Platforms: All
Version: 2026.1.1

This change updates the endpoints PUT /v1/security/audit/event, PUT /v1/els, and POST /v1/security/encryption/key/deactivate to correctly return a 400 HTTP response when the request body does not contain an acceptable set of fields.