AWS healthlake medium security documentation change
Summary
Added documentation for new features: Bundle Transactions, Implementation Guides support, Idempotency Keys, FHIR history consistency, ETag/If-Match, and Conditional PUTs in Bundles
Security assessment
Added idempotency keys and ETag/If-Match support which explicitly address data integrity and prevent accidental overwrites during concurrent updates. These changes directly mitigate potential race conditions and data corruption scenarios in healthcare data systems.
Diff
diff --git a/healthlake/latest/devguide/releases.md b/healthlake/latest/devguide/releases.md index 31d40ec66..3113d4d2d 100644 --- a//healthlake/latest/devguide/releases.md +++ b//healthlake/latest/devguide/releases.md @@ -10,0 +11,13 @@ Change| Description| Date +Bundle Type Transactions| HealthLake now supports FHIR Bundle type ‘Transaction’, allowing healthcare organizations to submit multiple resources as a single atomic operation. This enables more efficient data exchange and integration workflows. For example, a healthcare provider can now update a patient record, medication list, and appointment in a single transaction, reducing complexity and potential errors. See [Bundling FHIR Resources](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-bundle.html) for more information.| April 28, 2025 +Added support for new IGs| AWS HealthLake AWS HealthLake has expanded its FHIR Implementation Guides (IGs) support for the following: + + * NCQA HEDIS® Implementation Guide (0.3.1): Supports quality measurement and reporting for the Healthcare Effectiveness Data and Information Set (HEDIS). + * International Patient Summary (IPS) (2.0.0): Enables the exchange of essential health information to support continuity of care for patients. + * Quality Measure (5.0.0): Supports the representation and exchange of quality measure definitions and data. + * Genomics Reporting (3.0.0): Facilitates the exchange of genomic data and reports. + +| April 28, 2025 +Idempotency Keys| HealthLake now supports idempotency keys for FHIR POST operations, providing a robust mechanism to ensure data integrity during resource creation. See [Idempotency and Concurrency](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-idempotency.html) for more information.| April 18, 2025 +FHIR history consistency| HealthLake now supports strong consistency for [history](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-read-history.html)-enabled data stores via the new `x-amz-fhir-history-consistency-level` header. When set to 'strong', FHIR search results include all indexed records regardless of update status. See [FHIR Search Consistency Levels](https://docs.aws.amazon.com/healthlake/latest/devguide/searching-fhir-consistency-levels.html) for more information.| April 18, 2025 +Etag and 'if-match'| HealthLake now provides eTag support, allowing clients to use the 'If-Match' header to ensure idempotent updates. This helps maintain data integrity by preventing accidental overwrites during concurrent updates. This is particularly valuable in high-volume healthcare environments where multiple systems might attempt to update the same record simultaneously. See [ETag in AWS HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-idempotency.html#healthlake-etag) for more information.| April 18, 2025 +Conditional PUTs in Bundles| HealthLake now supports conditional updates for FHIR Bundles, giving healthcare organizations more flexibility to manage and update their data. Clients can now specify criteria to conditionally create, update, or delete resources as part of a Bundle transaction. This simplifies data synchronization processes between systems and reduces the need for complex client-side logic. See [Conditional PUTs in Bundles](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-bundle.html#bundle-conditional-PUTs) for more information.| April 18, 2025