New in HealthShare Health Connect Cloud 2025.3.1

The internal layout of the Approximate Nearest Neighbor (ANN) index used by vector search has been modified to improve duplicate entry management and reduce query-time overhead. Benchmarks show throughput and latency improvements of up to 10% depending on workload characteristics.

The updated format is applied automatically when the index is rebuilt. Rebuilding is not required for continued operation: the runtime is fully backwards compatible and can read and write indices in both the legacy and updated formats.

InterSystems FHIR Server now supports the $expand operation for ValueSet resources, enabling instance-level expansions as well as expansion of ValueSets within the repository using imported CodeSystems and packages. Query chaining has also been enhanced to allow mixing forward and reverse chain syntax within a single parameter: For example, to search for Encounter of patients who are members of Group 102, use the following query:

GET [base]/Encounter?patient._has:Group:member:_id=102

Chaining is also supported through canonical references. For example, to search for all ActivityDefinitions and include any Tasks absed on them via canonical identifiers, use the following query:

GET [base]/ActivityDefinition?_revinclude=Task:instantiatesCanonical

In addition, the Capability Statement now populates the supportedProfile element on each resource type. Configuration options for unauthenticated access have also been removed.

This release introduces several features to improve the user experience of configuring OAuth2.

• OAuth2 is now a native authentication type that can easily be enabled for web applications.

• You can now create resource servers with the new OAuth2.ResourceServer class, which simplifies resource server configuration significantly. Previously, resource servers were configured as an instance of OAuth2.Client.

• The OAuth2.ResourceServer class provides a sample authenticator for determining user permissions which, for simple configurations, requires no custom code (this previously required a custom ZAUTHENTICATE implementation). This simple authenticator can be extended and customized to suit your environment.

• You can now use JDBC and ODBC to authenticate with access tokens.

Health Connect Cloud now supports ECC (ECDSA) certificates for TLS configurations. ECC certificates are smaller and more computationally efficient than RSA and DSA certificates.

In past releases, it was necessary to configure pool sizes of one in order to force sequential message processing in order to maintain first-in-first-out (FIFO) queuing behavior for messages in a message feed. This release introduces customer-calculated message group identifiers, which allows for pool sizes of greater than one while maintaining FIFO. These identifiers also enable parallel processing of messages that had no direct dependency, increasing throughput of a production.

There are two settings provided for Business Processes and Business Operations under the header “FIFO Message Grouping” - Group Calculation (FMGCalculation) and Group Completion Hosts (FMGCompletionHosts) - that allow developers to configure the group identifier and the host that releases the group handle for a given group identifier, respectively. Group identifiers are configured by a Data Transformation (DTL) and is typically set to a value that identifies a FIFO dependency, such as a patient or device id.

This release introduces a significant change in how Health Connect Cloud manages table statistics, a key ingredient for getting high SQL query performance. Health Connect Cloud now distinguishes between fixed statistics, which are stored in the class definition and can be tuned by a developer (as in the pre-existing model), and collected statistics, which are stored with the data and are always based on actual data.

A new system maintenance task is available to automatically collect statistics for tables that do not have any or have stale statistics. This task is currently off by default to stay as close as possible to the pre-existing behavior, but InterSystems recommends switching it on and reviewing whether the additional IO load is reasonable. Fixed statistics always take precedence over collected statistics, so it is worth reviewing your current application to evaluate whether there are any fixed statistics in the class definition that you may want to drop in favor of the collected ones.

This release significantly enhances the foreign table infrastructure, which now also considers functions, aggregates, grouping, and ordering clauses in queries selecting from foreign tables, such that their evaluation can be pushed down to the remote servers. The new capabilities significantly expand upon the number of predicates that were previously eligible for pushdown and therefore can speed up many queries by minimizing the amount of data that needs to be passed back over the connection, a major factor in foreign table query performance.

To address the variance in different vendors’ support for SQL functions, a set of simple tiers is used to captured which set of functions it is safe to assume a foreign server supports. See the foreign tables documentation for more details.

Foreign tables now also use a simplified class structure, meaning it is safe to export and import them simply as a class definition.

Columnar storage for relational tables offers order-of-magnitude faster response times for analytical SQL queries. With this release, InterSystems introduces enhancements to the SQL optimizer’s costing algorithm to accurately estimate the cost of not just the query plans that entirely use columnar indexes, but also the mixed plans that combine columnar and non-columnar index structures. These changes increase the applicability and benefits of columnar stored in mixed transactional-analytical environments.

• When editing host categories, viewing connections are permissible

• A view icon on all rule sets open the specific rule set in the Rule Editor split panel

• Updated icons to open and close a panel

• When selecting the test button, the button is highlighted to indicate that the test panel is open

• Added a legend for Host Statuses in the information icon on a host

• Added drop down icons for all drop-down enabled settings fields

• Host Properties are now searchable, with added “expand all” sections

• IP Address and Port Number are now searchable in the Production Configuration Filter Bar

• Host Connections appear as they are registered by the front end, rather than appearing all at once when connections are fetched

• Pool size quantities are now displayed on each production configuration host.

• You can now create a new category by directly entering the naming convention in the category field of the host.

• There is now support for browser-level control find in Production Configuration.

• Production Host items now feature the Test Host function.

• In the new Settings Panel the X cancel icon also appears on panels to cancel an action.

• Longer class tooltip descriptions are formatted per the class documentation.

• Display of configuration item descriptions is enhanced to honor markup for longer, structured descriptions.

• Action Items are grayed out when not in the context of a host item or production.

• Creating a host enabled the automatic creation of a router and role.

• You now have the option to Update and Recover a production, where supported.

• Productions may not be created through the UI.

• DTL Segment Path copies with both field text and ordinal numbers

• The “hover over” segment icons for copying or adding a mapping are more accessible

• When adding a mapping, hovering over the particular segment now only shows the copy icon

• The DTL Editor split screen header and toolbar both remain in place when scrolling

• The Data Transformation Function drop-down menu is now searchable and limited to functions defined in the subclass.

• The DTL Graphical Editor now includes a button to copy an HL7 field path when hovering over a segment.

• Setting the Ordinal Number or Path Expressions or both will input the same expression setting when setting the DTL statement target and source fields.

• It is no longer possible to rename rules. Previously, that behavior cause confusion about changes to active rules. To create a new rule, use Save As instead.

• There is now support for browser-level control find in Rule Editor.