ReleaseMicrosoftMicrosoftpublished Feb 9, 2026seen Jun 26

microsoft/fhir-server release/4.0.654

microsoft/fhir-server

Open original ↗

Captured source

source ↗
published Feb 9, 2026seen Jun 26captured 21hhttp 200method plain

4.0.654

Repository: microsoft/fhir-server

Tag: release/4.0.654

Published: 2026-02-09T02:08:23Z

Prerelease: no

Release notes:

What's Changed

Azure API for FHIR (Cosmos)

  • Improve SqlServer project test coverage - part 2 by @rbans96 in https://github.com/microsoft/fhir-server/pull/5360: Improve SqlServer project test coverage.

Azure Health Data Services (SQL)

  • Allow meta history in transaction bundles by @LTA-Thinking in https://github.com/microsoft/fhir-server/pull/5351: There was a limitation where _meta-history parameter was not working in transaction bundles. This issue has been fixed, and _meta-history parameter can now be used in transaction bundles.
  • DeletionService - IFhirDataStore scoped handling by @fhibf in https://github.com/microsoft/fhir-server/pull/5363: For a transaction bundle, all interactions or operations either succeed or fail together. When a transaction bundle fails, the FHIR service returns a single OperationOutcome. Previously, there was an issue where soft delete operations were not being considered for the transaction bundle scope, which could cause a discrepancy in the all-or-nothing behavior of the transaction bundle. This issue has been fixed, and all interactions or operations, including soft deletes, will now correctly either succeed or fail together.
  • Improve test coverage for SqlServer project by @rbans96 in https://github.com/microsoft/fhir-server/pull/5335
  • Push code coverage data to 1es telemetry by @rbans96 in https://github.com/microsoft/fhir-server/pull/5368
  • Support meta history in bulk update by @LTA-Thinking in https://github.com/microsoft/fhir-server/pull/5370: Metadata-only updates and versioning configuration with $bulk-update: Introduced new query parameter "_meta-history" for bulk update when versioning policy is set to either "versioned" or "version-update." The new query is used to configure whether or not the old version is saved as a historical record. "_meta-history = true" is the default. By default, the resource version is incremented, a new version is created, and the old version is saved as a historical record. "_meta-history=false" can be configured so that the resource version is incremented, a new version is created, but the old version isn't saved as a historical record.

Other Changes

  • Code coverage improvement for Shared API. by @v-isyamauchi-gh in https://github.com/microsoft/fhir-server/pull/5343
  • Use Microsoft Testing Platform & Auto-Retry Tests by @mikaelweave in https://github.com/microsoft/fhir-server/pull/5365

Full Changelog: https://github.com/microsoft/fhir-server/compare/release/4.0.646...release/4.0.654