FHIR Search Consistency Levels in AWS HealthLake
FHIR Search Consistency Levels - AWS HealthLake AWS Documentation Set
AWS documented the use of FHIR Search Consistency Levels within AWS HealthLake.
Summary
AWS HealthLake now allows developers to select between 'Eventual Consistency' and 'Strong Consistency' for search results when resources are updated. This enables reliable handling of the latest resource information at critical times.
Key Players
Details
This document details the operational specifications for FHIR resource searching within AWS HealthLake. By default, GET/POST SEARCH operations operate under an 'Eventual Consistency' model; if a search index update is pending, results may only include version N-1 until the index completes its update. However, AWS HealthLake now offers the option of 'Strong Consistency'. When strong consistency is set, resources with pending search index updates—meaning the latest versions—are included in the search results. This feature is crucial for use cases requiring immediate data verification after an update. Developers control this behavior using the `x-amz-fhir-history-consistency-level` request header. While enabling strong consistency allows for immediate visibility of updated resources, it increases write capacity consumption per resource. The choice between eventual and strong consistency involves a trade-off between immediate data availability and potential performance impact.
Technology Note
FHIR（Fast Healthcare Interoperability Resources）は医療データ交換の国際標準。このエントリの関連技術: FHIR
Original content copyright by respective publishers