Smile CDR 2025.05.R01 and HAPI FHIR 8.1.0 (Code Name: Fortification)

- The SMART discovery document will now include the `grant_types_supported` and `code_challenge_methods_supported` elements which are required by the SMART 2.0 specification.

- SMART 2.1-style "*.cruds" scopes are now supported by the SMART outbound and inbound modules.

- The SMART discovery document will now automatically include details from any linked SMART Inbound Security module (previously only linked SMART Outbound Security modules were used).

- Gateway searches can now handle OperationOutcome resources appearing in target server search responses.

- Instance-level history operations are now supported through the gateway.

- Bulk export is now supported through the Gateway.

- An issue preventing SASL-based Kafka authentication has been resolved.

- Sending to Kafka (from Smile) is now a synchronous operation and will throw an exception if the send times out (previously messages were logged and dropped in the event of a timeout from an unresponsive broker).

- Javascript-based storage interceptors prevented the use of Mass Ingestion Mode
Connections in the database connection pool are now tested while idle to ensure that they are still valid.

- A new partition mode has been added which allows the request partition to be specified using an HTTP Request Header.

- New feature to the FHIR Repository called Tokenization. This feature is a new building block that can be used to encrypt individual data elements within FHIR resources in order to satisfy security directives for record-level encryption, etc.

- The CDAx+ module now provides built-in mappings between C-CDA 2.1 and FHIR US Core 6.1.0.

- Observation FHIR resources generated by CDAx+ have been modified to more closely follow current guidance in the FHIR specification.

- The default ingestion mode has changed from "Transaction Bundle" to "Document Bundle".

- The resource de-duplication algorithm has been improved to better avoid duplicate resource creation when multiple elements within a CDA document map to the same logical target resource.

- The camel module will now validate route definitions and fail to start if they contain any errors.

- A new built-in processor has been added which converts a string into a DocumentReference.

- A new built-in processor has been added which persists (i.e. create/update) a single raw FHIR resource.

- FHIRPath expressions can now be evaluated on resources via Javascript Execution Environment scripts.

- XPath selection on XML documents failed if an `xmlns=` declaration was found anywhere except the root of the document.

- XPath evaluation performance has been significantly improved from Javascript calls.

- The CDAx+ module now provides built-in mappings between C-CDA 2.1 and FHIR US Core 6.1.0.

- Observation FHIR resources generated by CDAx+ have been modified to more closely follow current guidance in the FHIR specification.

- The default ingestion mode has changed from “Transaction Bundle” to “Document Bundle”.

- The resource de-duplication algorithm has been improved to avoid creating duplicate resources when multiple elements in a CDA document map to the same logical target.

- The camel module will now validate route definitions and fail to start if they contain any errors.

- A new built-in processor has been added which converts a string into a DocumentReference.

- A new built-in processor has been added which persists (i.e. create/update) a single raw FHIR resource.

- FHIRPath expressions can now be evaluated on resources via Javascript Execution Environment scripts.

- XPath selection on XML documents failed if an xmlns= declaration was found anywhere except the root of the document.

- XPath evaluation performance has been significantly improved from Javascript calls.

- The Consent Module API introduced in 2025.02.R01 has been simplified based on initial feedback. Existing configuration may require changes, see the release notes for more information.
Consent directives can now be applied to Bulk Export ($export).

- When using Infinispan-based query cache, some data was previously still stored in the database. Now all cached data will be stored in Infinispan, meaning the database is not written to at all by the query cache in this mode.

- Fixed an issue preventing the use of Safari browser to manage modules in the Web Admin Console.

- When viewing a module on the same node as the WAC, the list of currently registered interceptors is shown on the display (WHAT ABOUT OTHER NODES?).

- The support bundle which can be requested from the WAC includes a list of registered interceptors (WHAT ABOUT OTHER NODES).

- The audit log viewer will now view logs from registered Audit Log Persistence modules (previously only events stored directly in the cluster manager database were shown).

- It is now possible to archive and view archived OIDC clients from the WAC.

- Transaction log entries generated during HL7v2 message processing now contain more complete details of all validation failures occurring during processing.

- Mapping OBX segments previously failed if OBX-5 (value) was not populated.

- A bug prevented accessing data in unknown HL7v2 fields (i.e fields beyond the known list) if the field contained only one component.

- A new tutorial has been added showing how to add custom $operations to a FHIR Storage-based repository endpoint.

- Broken in-page navigation has been fixed when the user selects a page from the left-side navigation/search bars.

- The query timeout configuration property was not applied to Mongo client connections.

- The built-in AWS SDK has been upgraded from 1.0 to 2.0. This allows new security features for authenticating to AWS database and other resources.

- A new partition selection troubleshooting log is now available.

- Remote terminology services clients can now be configured for request and connection timeouts and pool sizes.

- It is now possible to select which version of the CDS Hooks specification you wish to support in the CDS Hooks module. Options are: 1.1, 2.0.

- The R4 backport of R5 SubscriptionTopic (using a Basic resource as prescribed in the backport IG) is now fully supported in R4 FHIR Storage modules.

- The SubscriptionTopic notificationShape element is now respected, meaning subscriptions can define additional resource inclusions and exclusions for delivery messages.

- New search methods have been added to the NPM endpoint which can be used to search for packages containing specific artifacts by canonical URI, and optionally fetch these artifacts.