AWS HealthLake releases

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
Patch Operation	HealthLake allows modifying specific elements of FHIR resources using JSON Patch operations without updating the entire resource.	August 18, 2025
$validate Operation	HealthLake enables validating FHIR resources against the specification and profiles without performing storage operations, returning detailed validation results.	August 18, 2025
$purge Operation	HealthLake includes functionality to permanently delete all resources within a patient's compartment from the datastore.	August 18, 2025
$lookup Operation	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
$expand Operation	HealthLake now allows expanding ValueSet resources to retrieve the complete list of codes contained within customer-ingested ValueSets.	August 18, 2025
$erase Operation	HealthLake now offers permanently deletion of a specific resource and all its historical versions from the datastore.	August 18, 2025
$document Operation	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	HealthLake introduces searching for URI values that are hierarchically below the specified URI in a terminology system.	August 8, 2025
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 for more information.	July 7, 2025
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 guidance	July 7, 2025
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 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 for more information.	April 18, 2025
FHIR history consistency	HealthLake now supports strong consistency for history-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 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 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 for more information.	April 18, 2025
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. 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. 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	HealthLake supports version 6.1.0 of the FHIR US Core Profile. For more information, see FHIR profile validations for HealthLake.	January 22, 2025
FHIR $export with GET	HealthLake supports FHIR $export with GET. For more information, see Exporting HealthLake data with FHIR $export.	January 22, 2025
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 and Managing FHIR resources.	December 18, 2024
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. 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. To create your case, log in to your AWS account and choose Create case.	October 25, 2024
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. 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. To create your case, log in to your AWS account and choose Create case.	February 27, 2024
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.	December 9, 2023
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. 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. 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	HealthLake adds support for SMART on FHIR authorization. For more information, see SMART on FHIR support for AWS HealthLake.	May 31, 2023
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.	May 31, 2023
Asia Pacific (Mumbai) region	HealthLake is available in the Asia Pacific (Mumbai) region. For more information, see Service endpoints.	April 4, 2023
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. 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.	February 20, 2023
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. 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. 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.	November 14, 2022
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.	October 3, 2022
FHIR Bundle resource	HealthLake supports the FHIR Bundle resource type for processing multiple FHIR resources simultaneously. For more information, see Bundling FHIR resources.	August 5, 2022
Quota updates for FHIR interactions	HealthLake updates quotas for FHIR resource management interactions. For more information, see Service quotas.	July 16, 2022
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.	July 16, 2022
AWS HealthLake is generally available	HealthLake is generally available in all supported regions. For more information, see Service endpoints.	July 15, 2021