# AWS HealthLake releases
Releases\$1bulk-member-match operation

AWS HealthLake now supports the `$bulk-member-match` operation for processing multiple member match requests asynchronously. This operation enables healthcare organizations to efficiently match hundreds of members' unique identifiers across different healthcare systems using demographic and coverage information in a single bulk request.
+ Handles up to 500 members per request with up to 5 concurrent operations per data store
+ Results categorized into MatchedMembers, NonMatchedMembers, and ConsentConstrainedMembers groups
+ Integrates with `$davinci-data-export` for end-to-end bulk data workflows

For more information, see [`$bulk-member-match` operation for HealthLake](reference-fhir-operations-bulk-member-match.md).Asynchronous bundle transactions

AWS HealthLake now supports asynchronous `Bundle` type `transaction`, allowing you to submit transactions with up to 500 resources. HealthLake queues the transaction for processing and immediately returns a polling URL to check status and retrieve results. For more information, see [Asynchronous bundle transactions](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-bundle.html#managing-fhir-resources-async-transactions).DaVinci PDex Export Types for \$1davinci-data-export

The `$davinci-data-export` operation now supports PDex export types for Provider Access, Payer-to-Payer, and Member Access APIs.
+ Profile-based inclusion logic for ExplanationOfBenefit resources
+ Financial data transformation with the `_includeEOB2xWoFinancial` parameter
+ 5-year temporal filter on clinical and claims data\$1inquire Operation

The `$inquire` operation enables you to check the status of a previously submitted prior authorization request.\$1questionnaire-package Operation

The `$questionnaire-package` operation retrieves a comprehensive bundle containing a FHIR Questionnaire and all its dependencies needed to render and process the questionnaire.\$1submit Operation

The `$submit` operation enables you to electronically submit prior authorization requests to payers for approval.CMS interoperability endpoints

This feature enable you to track API usage by CMS category and subsequently report usage metrics for compliance purposes.Bundle Message Type Support

Limited support for FHIR Bundle resources with Message typeAdded support for new IGs

AWS HealthLake has expanded its FHIR Implementation Guides (IGs) support for CMS 0057F:
+ Support for CARIN Blue Button 2.0.0 & 2.1.0
+ Support for Da Vinci Payer Data Exchange 2.0.0 & 2.1.0
+ Support for DaVinci Payer Data Exchange (PDex) US Drug Formulary 2.0.1 & 2.1.0
+ Support for Da Vinci Clinical Data Exchange (CDex) 2.1.0
+ Support for Da Vinci Prior Authorization Support (PAS) FHIR IG 2.1.0\$1include Search Parameter

HealthLake now supports include:\$1 and include:iterate\$1until Parameter in \$1export & \$1davinci-data-export

Temporal filtering parameter for export operations\$1davinci-data-export Operation

The \$1davinci-data-export operation is an asynchronous FHIR operation that enables the export of Member Attribution List data from AWS HealthLake.\$1confirm-attribution-list Operation

Indicates to a Producer that the Consumer has no more changes to make to the Attribution List, finalizing the attribution list by removing inactive members and changing the status to "final".\$1attribution-status Operation

Retrieves the attribution status for a specific member, returning a Bundle containing all attribution resources related to the Patient.\$1member-remove Operation

The \$1member-remove operation allows you to remove members from a FHIR Member Attribution List (Group resource) in AWS HealthLake.\$1member-add Operation

The FHIR \$1member-add operation adds a member (patient) to a Group resource, specifically a Member Attribution List.\$1member-match Operation

AWS HealthLake now supports the \$1member-match operation for Patient resources, enabling healthcare organizations to find a member's unique identifier across different healthcare systems using demographic and coverage information.FHIR Subscriptions

HealthLake supports FHIR Subscriptions, allowing you to receive real-time notifications when specific healthcare data changes occur and build event-driven workflows.Region expansion to Montreal Canada

HealthLake is available in the Canada (Montreal) region. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html).Added support for new IGs

AWS HealthLake has expanded its FHIR Implementation Guides (IGs) support for the following Canadian market:
+ CA Core\$1Canadian baseline FHIR profile defining core data elements and constraints for interoperability across Canadian healthcare systems.
+ CA:eReC Pan-Canadian eReferral-eConsultStandardized FHIR specification for electronic referrals and consults between healthcare providers across Canada.
+ Patient Summary Canadian Edition (PS-CA)Canadian adaptation of the International Patient Summary (IPS) for sharing essential patient health information across care settings.
+ Ontario Digital Health Drug RepositoryOntario-specific FHIR profile for standardized medication and prescription data exchange within the provincial health system.Region specific IG support

HealthLake now supports region specific IGs. For more information, see [profile validations](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-profile-validations.html).\$1expand Operation

HealthLake now allows expanding ValueSet resources to retrieve the complete list of codes contained within customer-ingested ValueSets.\$1document Operation

HealthLake supports generating complete clinical documents by bundling a Composition resource with all its referenced resources into a single document Bundle.\$1validate Operation

HealthLake enables validating FHIR resources against the specification and profiles without performing storage operations, returning detailed validation results.\$1lookup Operation

HealthLake provides the ability to retrieve detailed information about a specific concept in a CodeSystem by providing the code and system identifier.Patch Operation

HealthLake allows modifying specific elements of FHIR resources using JSON Patch operations without updating the entire resource.\$1erase Operation

HealthLake now offers permanently deletion of a specific resource and all its historical versions from the datastore.\$1purge Operation

HealthLake includes functionality to permanently delete all resources within a patient's compartment from the datastore.:below Search Modifier

HealthLake introduces searching for URI values that are hierarchically below the specified URI in a terminology system.Conditional Delete

HealthLake now supports FHIR Conditional Delete, allowing healthcare organizations to delete an existing resource based on search criteria rather than by logical FHIR ID. See [Deleting FHIR resources based on conditions](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-delete.html#conditional-delete-fhir) for more information.Added support for new IGs

AWS HealthLake has expanded its FHIR Implementation Guides (IGs) support for the following:
+ US Core 7.0.0 which specifies how to use FHIR to implement the USCDI 4.0 standard
+ UK Core 2.0.1 Implementation Guide to provide UK wide FHIR implementation guidanceRegion expansion to Dublin Ireland

HealthLake is available in the EU (Dublin) region. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html).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.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.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.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.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.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.FHIR \$1export with GET

HealthLake supports FHIR `$export` with `GET`. For more information, see [Exporting HealthLake data with FHIR `$export`](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-operations.html#export-operation).SMART on FHIR V2 scopes

HealthLake supports SMART on FHIR V2 scopes for creating, reading, updating, deleting, and searching FHIR resources. For more information, see [SMART on FHIR resource scopes for HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-smart-on-fhir-oauth-scopes.html#smart-on-fhir-scopes-rest).
+ SMART on FHIR V2 scopes are available to all HealthLake data stores created after 01/22/2025. If your data store was created before this date, you can submit a support ticket to have SMART on FHIR V2 scopes enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.FHIR US Core Profile, version 6.1.0

HealthLake supports version 6.1.0 of the FHIR US Core Profile. For more information, see [FHIR profile validations for HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-profile-validations.html).Refactored Developer Guide with tested code examples

HealthLake introduces a refactored Developer Guide with tested code examples for native AWS CLI and AWS SDK actions. In addition, procedures are now available for all supported FHIR API interactions. For more information, see [Code examples](https://docs.aws.amazon.com/healthlake/latest/devguide/service_code_examples.html) and [Managing FHIR resources](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources.html).FHIR `history` and `vread` interactions

HealthLake supports the FHIR `history` interaction for retrieving the history of a particular resource and the `vread` interaction for performing a version-specific read of a resource. For more information, see [Reading FHIR resource history](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-read-history.html).
+ FHIR resource `history` is enabled by default to all HealthLake data stores created after 10/25/2024. If your data store was created before this date, you can submit a support ticket to have FHIR `history` interaction enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.FHIR `Patient/$everything` operation

HealthLake supports the FHIR `Patient/$everything` operation for searching a `Patient` resource and all its related resources. Using this operation, you can access a patient's entire record or download `Patient` data in bulk. For more information, see [Getting patient data with `Patient/$everything`](https://docs.aws.amazon.com/healthlake/latest/devguide/patient-everything-operation.html).
+ FHIR `Patient/$everything` is enabled by default to all HealthLake data stores created after 02/27/2024. If your data store was created before this date, you can submit a support ticket to have the `Patient/$everything` operation enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.FHIR `VerificationResult` resource

HealthLake supports the FHIR `VerificationResult` resource type for describing validation requirements, sources, status, and dates for one or more elements. For more information, see [FHIR R4 resource types for HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-resource-types.html).SMART on FHIR support

HealthLake adds support for SMART on FHIR authorization. For more information, see [SMART on FHIR support for AWS HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-smart-on-fhir.html).FHIR profile validations

HealthLake supports FHIR profile validations for defining specific resource type definitions using constraints and/or extensions on base resource types. For more information, see [Profile validations](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-profile-validations.html).FHIR `$export` operation

HealthLake supports the FHIR `$export` operation for exporting health data in bulk from an HealthLake data store. For more information, see [Exporting HealthLake data with FHIR `$export`](https://docs.aws.amazon.com/healthlake/latest/devguide/export-operation.html).
+ FHIR `$export` is enabled by default to all HealthLake data stores created after June 1, 2023. If your data store was created before this date, you can submit a support ticket to have the `$export` operation enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.
+ HealthLake data stores created prior to 06/01/23 support only `$export` job requests for system-wide exports.
+ HealthLake data stores created prior to 06/01/23 do not support getting the status of an FHIR `$export` using a `GET` request on the data store's endpoint.Asia Pacific (Mumbai) region

HealthLake is available in the Asia Pacific (Mumbai) region. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-endpoints.html).Natural language processing turned off by default

HealthLake turned off integrated natural language processing (NLP) on all data stores as of February 20, 2023. You can submit a support ticket to have integrated NLP functionality turned on. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**. To learn more about integrated NLP, see [Integrating NLP with HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/integrating-nlp.html).
+ SQL index and query with Amazon Athena

HealthLake supports querying FHIR data with SQL using Amazon Athena. For more information, see [Querying HealthLake data with Amazon Athena](https://docs.aws.amazon.com/healthlake/latest/devguide/integrating-athena.html).
+ SQL query functionality is enabled by default to all HealthLake data stores created after 11/14/2022. If your data store was created before this date, you can submit a support ticket to have SQL query functionality enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.
+ With SQL query functionality, IAM settings to access HealthLake must be updated. To both create HealthLake data stores and grant access to them in Athena, you must have the `AWSLakeFormationDataAdmin` managed policy added to your IAM user, group, or role. You can use the `AWSLakeFormationDataAdmin` policy to create data lake administrators and grant access to data stores in Athena. For more information, see [Configure an IAM user or role](https://docs.aws.amazon.com/healthlake/latest/devguide/getting-started-setting-up.html#gs-configure-iam).Total import job size increased

HealthLake updates the `Total import job size` for a `StartFHIRImportJob` request to 500 GB. For more information, see [Service quotas](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-quotas).FHIR `Bundle` resource

HealthLake supports the FHIR `Bundle` resource type for processing multiple FHIR resources simultaneously. For more information, see [Bundling FHIR resources](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-bundle.html).Quota updates for FHIR interactions

HealthLake updates quotas for FHIR resource management interactions. For more information, see [Service quotas](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-quotas).FHIR `_include` search parameter

HealthLake adds support for the FHIR `_include` search parameter to return additional resources in a `search` request. For more information, see [Advanced search parameters](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-search-parameters.html#search-parameters-advanced).AWS HealthLake is generally available

HealthLake is generally available in all supported regions. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-endpoints.html).

The following table shows when features and updates were released for AWS HealthLake. For more information about a release, see the linked topic.

| Change | Description | Date | 
| --- |--- |--- |
| [\$1bulk-member-match operation](#releases) | AWS HealthLake now supports the `$bulk-member-match` operation for processing multiple member match requests asynchronously. This operation enables healthcare organizations to efficiently match hundreds of members' unique identifiers across different healthcare systems using demographic and coverage information in a single bulk request. Handles up to 500 members per request with up to 5 concurrent operations per data store Results categorized into MatchedMembers, NonMatchedMembers, and ConsentConstrainedMembers groups Integrates with `$davinci-data-export` for end-to-end bulk data workflows For more information, see [`$bulk-member-match` operation for HealthLake](reference-fhir-operations-bulk-member-match.md). | April 1, 2026 | 
| [Asynchronous bundle transactions](#releases) | AWS HealthLake now supports asynchronous `Bundle` type `transaction`, allowing you to submit transactions with up to 500 resources. HealthLake queues the transaction for processing and immediately returns a polling URL to check status and retrieve results. For more information, see [Asynchronous bundle transactions](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-bundle.html#managing-fhir-resources-async-transactions). | March 24, 2026 | 
| [DaVinci PDex Export Types for \$1davinci-data-export](#releases) | The `$davinci-data-export` operation now supports PDex export types for Provider Access, Payer-to-Payer, and Member Access APIs. Profile-based inclusion logic for ExplanationOfBenefit resources Financial data transformation with the `_includeEOB2xWoFinancial` parameter 5-year temporal filter on clinical and claims data  | March 20, 2026 | 
| [\$1until Parameter in \$1export & \$1davinci-data-export](#releases) | Temporal filtering parameter for export operations | February 26, 2026 | 
| [\$1include Search Parameter](#releases) | HealthLake now supports include:\$1 and include:iterate | February 26, 2026 | 
| [CMS interoperability endpoints](#releases) | This feature enable you to track API usage by CMS category and subsequently report usage metrics for compliance purposes. | February 26, 2026 | 
| [Bundle Message Type Support](#releases) | Limited support for FHIR Bundle resources with Message type | February 26, 2026 | 
| [Added support for new IGs](#releases) | AWS HealthLake has expanded its FHIR Implementation Guides (IGs) support for CMS 0057F: Support for CARIN Blue Button 2.0.0 & 2.1.0 Support for Da Vinci Payer Data Exchange 2.0.0 & 2.1.0 Support for DaVinci Payer Data Exchange (PDex) US Drug Formulary 2.0.1 & 2.1.0 Support for Da Vinci Clinical Data Exchange (CDex) 2.1.0 Support for Da Vinci Prior Authorization Support (PAS) FHIR IG 2.1.0  | February 26, 2026 | 
| [\$1submit Operation](#releases) | The `$submit` operation enables you to electronically submit prior authorization requests to payers for approval. | February 26, 2026 | 
| [\$1questionnaire-package Operation](#releases) | The `$questionnaire-package` operation retrieves a comprehensive bundle containing a FHIR Questionnaire and all its dependencies needed to render and process the questionnaire. | February 26, 2026 | 
| [\$1inquire Operation](#releases) | The `$inquire` operation enables you to check the status of a previously submitted prior authorization request. | February 26, 2026 | 
| [\$1member-remove Operation](#releases) | The \$1member-remove operation allows you to remove members from a FHIR Member Attribution List (Group resource) in AWS HealthLake. | November 12, 2025 | 
| [\$1member-match Operation](#releases) | AWS HealthLake now supports the \$1member-match operation for Patient resources, enabling healthcare organizations to find a member's unique identifier across different healthcare systems using demographic and coverage information. | November 12, 2025 | 
| [\$1member-add Operation](#releases) | The FHIR \$1member-add operation adds a member (patient) to a Group resource, specifically a Member Attribution List. | November 12, 2025 | 
| [\$1davinci-data-export Operation](#releases) | The \$1davinci-data-export operation is an asynchronous FHIR operation that enables the export of Member Attribution List data from AWS HealthLake. | November 12, 2025 | 
| [\$1confirm-attribution-list Operation](#releases) | Indicates to a Producer that the Consumer has no more changes to make to the Attribution List, finalizing the attribution list by removing inactive members and changing the status to "final". | November 12, 2025 | 
| [\$1attribution-status Operation](#releases) | Retrieves the attribution status for a specific member, returning a Bundle containing all attribution resources related to the Patient. | November 12, 2025 | 
| [FHIR Subscriptions](#releases) | HealthLake supports FHIR Subscriptions, allowing you to receive real-time notifications when specific healthcare data changes occur and build event-driven workflows. | October 30, 2025 | 
| [Region expansion to Montreal Canada](#releases) | HealthLake is available in the Canada (Montreal) region. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html). | October 17, 2025 | 
| [Added support for new IGs](#releases) | AWS HealthLake has expanded its FHIR Implementation Guides (IGs) support for the following Canadian market: CA Core\$1Canadian baseline FHIR profile defining core data elements and constraints for interoperability across Canadian healthcare systems. CA:eReC Pan-Canadian eReferral-eConsultStandardized FHIR specification for electronic referrals and consults between healthcare providers across Canada. Patient Summary Canadian Edition (PS-CA)Canadian adaptation of the International Patient Summary (IPS) for sharing essential patient health information across care settings. Ontario Digital Health Drug RepositoryOntario-specific FHIR profile for standardized medication and prescription data exchange within the provincial health system.  | October 17, 2025 | 
| [Region specific IG support](#releases) | HealthLake now supports region specific IGs. For more information, see [profile validations](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-profile-validations.html). | October 8, 2025 | 
| [Patch Operation](#releases) | HealthLake allows modifying specific elements of FHIR resources using JSON Patch operations without updating the entire resource. | August 18, 2025 | 
| [\$1validate Operation](#releases) | HealthLake enables validating FHIR resources against the specification and profiles without performing storage operations, returning detailed validation results. | August 18, 2025 | 
| [\$1purge Operation](#releases) | HealthLake includes functionality to permanently delete all resources within a patient's compartment from the datastore. | August 18, 2025 | 
| [\$1lookup Operation](#releases) | HealthLake provides the ability to retrieve detailed information about a specific concept in a CodeSystem by providing the code and system identifier. | August 18, 2025 | 
| [\$1expand Operation](#releases) | HealthLake now allows expanding ValueSet resources to retrieve the complete list of codes contained within customer-ingested ValueSets. | August 18, 2025 | 
| [\$1erase Operation](#releases) | HealthLake now offers permanently deletion of a specific resource and all its historical versions from the datastore. | August 18, 2025 | 
| [\$1document Operation](#releases) | HealthLake supports generating complete clinical documents by bundling a Composition resource with all its referenced resources into a single document Bundle. | August 18, 2025 | 
| [:below Search Modifier](#releases) | HealthLake introduces searching for URI values that are hierarchically below the specified URI in a terminology system. | August 8, 2025 | 
| [Conditional Delete](#releases) | HealthLake now supports FHIR Conditional Delete, allowing healthcare organizations to delete an existing resource based on search criteria rather than by logical FHIR ID. See [Deleting FHIR resources based on conditions](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-delete.html#conditional-delete-fhir) for more information. | July 7, 2025 | 
| [Added support for new IGs](#releases) | AWS HealthLake has expanded its FHIR Implementation Guides (IGs) support for the following: US Core 7.0.0 which specifies how to use FHIR to implement the USCDI 4.0 standard UK Core 2.0.1 Implementation Guide to provide UK wide FHIR implementation guidance  | July 7, 2025 | 
| [Region expansion to Dublin Ireland](#releases) | HealthLake is available in the EU (Dublin) region. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html). | June 9, 2025 | 
| [Bundle Type Transactions](#releases) | 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](#releases) | 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](#releases) | 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](#releases) | 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'](#releases) | 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](#releases) | 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 | 
| [SMART on FHIR V2 scopes](#releases) | HealthLake supports SMART on FHIR V2 scopes for creating, reading, updating, deleting, and searching FHIR resources. For more information, see [SMART on FHIR resource scopes for HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-smart-on-fhir-oauth-scopes.html#smart-on-fhir-scopes-rest).  SMART on FHIR V2 scopes are available to all HealthLake data stores created after 01/22/2025. If your data store was created before this date, you can submit a support ticket to have SMART on FHIR V2 scopes enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.   | January 22, 2025 | 
| [FHIR US Core Profile, version 6.1.0](#releases) | HealthLake supports version 6.1.0 of the FHIR US Core Profile. For more information, see [FHIR profile validations for HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-profile-validations.html). | January 22, 2025 | 
| [FHIR \$1export with GET](#releases) | HealthLake supports FHIR `$export` with `GET`. For more information, see [Exporting HealthLake data with FHIR `$export`](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-operations.html#export-operation). | January 22, 2025 | 
| [Refactored Developer Guide with tested code examples](#releases) | HealthLake introduces a refactored Developer Guide with tested code examples for native AWS CLI and AWS SDK actions. In addition, procedures are now available for all supported FHIR API interactions. For more information, see [Code examples](https://docs.aws.amazon.com/healthlake/latest/devguide/service_code_examples.html) and [Managing FHIR resources](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources.html). | December 18, 2024 | 
| [FHIR `history` and `vread` interactions](#releases) | HealthLake supports the FHIR `history` interaction for retrieving the history of a particular resource and the `vread` interaction for performing a version-specific read of a resource. For more information, see [Reading FHIR resource history](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-read-history.html).  FHIR resource `history` is enabled by default to all HealthLake data stores created after 10/25/2024. If your data store was created before this date, you can submit a support ticket to have FHIR `history` interaction enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.   | October 25, 2024 | 
| [FHIR `Patient/$everything` operation](#releases) | HealthLake supports the FHIR `Patient/$everything` operation for searching a `Patient` resource and all its related resources. Using this operation, you can access a patient's entire record or download `Patient` data in bulk. For more information, see [Getting patient data with `Patient/$everything`](https://docs.aws.amazon.com/healthlake/latest/devguide/patient-everything-operation.html).  FHIR `Patient/$everything` is enabled by default to all HealthLake data stores created after 02/27/2024. If your data store was created before this date, you can submit a support ticket to have the `Patient/$everything` operation enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.   | February 27, 2024 | 
| [FHIR `VerificationResult` resource](#releases) | HealthLake supports the FHIR `VerificationResult` resource type for describing validation requirements, sources, status, and dates for one or more elements. For more information, see [FHIR R4 resource types for HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-resource-types.html). | December 9, 2023 | 
| [FHIR `$export` operation](#releases) | HealthLake supports the FHIR `$export` operation for exporting health data in bulk from an HealthLake data store. For more information, see [Exporting HealthLake data with FHIR `$export`](https://docs.aws.amazon.com/healthlake/latest/devguide/export-operation.html).  FHIR `$export` is enabled by default to all HealthLake data stores created after June 1, 2023. If your data store was created before this date, you can submit a support ticket to have the `$export` operation enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.   HealthLake data stores created prior to 06/01/23 support only `$export` job requests for system-wide exports.   HealthLake data stores created prior to 06/01/23 do not support getting the status of an FHIR `$export` using a `GET` request on the data store's endpoint.   | June 1, 2023 | 
| [SMART on FHIR support](#releases) | HealthLake adds support for SMART on FHIR authorization. For more information, see [SMART on FHIR support for AWS HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-smart-on-fhir.html). | May 31, 2023 | 
| [FHIR profile validations](#releases) | HealthLake supports FHIR profile validations for defining specific resource type definitions using constraints and/or extensions on base resource types. For more information, see [Profile validations](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-profile-validations.html). | May 31, 2023 | 
| [Asia Pacific (Mumbai) region](#releases) | HealthLake is available in the Asia Pacific (Mumbai) region. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-endpoints.html). | April 4, 2023 | 
| [Natural language processing turned off by default](#releases) | HealthLake turned off integrated natural language processing (NLP) on all data stores as of February 20, 2023. You can submit a support ticket to have integrated NLP functionality turned on. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**. To learn more about integrated NLP, see [Integrating NLP with HealthLake](https://docs.aws.amazon.com/healthlake/latest/devguide/integrating-nlp.html).     | February 20, 2023 | 
| [SQL index and query with Amazon Athena](#releases) | HealthLake supports querying FHIR data with SQL using Amazon Athena. For more information, see [Querying HealthLake data with Amazon Athena](https://docs.aws.amazon.com/healthlake/latest/devguide/integrating-athena.html).  SQL query functionality is enabled by default to all HealthLake data stores created after 11/14/2022. If your data store was created before this date, you can submit a support ticket to have SQL query functionality enabled. Create a case using [AWS Support Center Console](https://console.aws.amazon.com/support/home#/). To create your case, log in to your AWS account and choose **Create case**.   With SQL query functionality, IAM settings to access HealthLake must be updated. To both create HealthLake data stores and grant access to them in Athena, you must have the `AWSLakeFormationDataAdmin` managed policy added to your IAM user, group, or role. You can use the `AWSLakeFormationDataAdmin` policy to create data lake administrators and grant access to data stores in Athena. For more information, see [Configure an IAM user or role](https://docs.aws.amazon.com/healthlake/latest/devguide/getting-started-setting-up.html#gs-configure-iam).   | November 14, 2022 | 
| [Total import job size increased](#releases) | HealthLake updates the `Total import job size` for a `StartFHIRImportJob` request to 500 GB. For more information, see [Service quotas](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-quotas). | October 3, 2022 | 
| [FHIR `Bundle` resource](#releases) | HealthLake supports the FHIR `Bundle` resource type for processing multiple FHIR resources simultaneously. For more information, see [Bundling FHIR resources](https://docs.aws.amazon.com/healthlake/latest/devguide/managing-fhir-resources-bundle.html). | August 5, 2022 | 
| [Quota updates for FHIR interactions](#releases) | HealthLake updates quotas for FHIR resource management interactions. For more information, see [Service quotas](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-quotas). | July 16, 2022 | 
| [FHIR `_include` search parameter](#releases) | HealthLake adds support for the FHIR `_include` search parameter to return additional resources in a `search` request. For more information, see [Advanced search parameters](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-fhir-search-parameters.html#search-parameters-advanced). | July 16, 2022 | 
| [AWS HealthLake is generally available](#releases) | HealthLake is generally available in all supported regions. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthlake/latest/devguide/reference-healthlake-endpoints-quotas.html#reference-healthlake-endpoints.html). | July 15, 2021 |