HealthLake is the managed FHIR transaction and exchange boundary
Amazon HealthLake is not a generic data lake with healthcare branding. It is the managed AWS service for storing, analyzing, and sharing health data using the FHIR R4 specification, with explicit support for import, export, SMART on FHIR, and natural-language enrichment.
That service boundary matters. If your application needs transactional FHIR APIs, patient-centric resource queries, or a durable standards-based representation for downstream apps, HealthLake is the relevant service. If the workload is native DICOM or omics-specific execution, the architecture needs a different primary store.
HealthLake service boundary
Loading diagram...
What is AWS HealthLake?
Official overview of HealthLake features including FHIR R4 storage, SMART on FHIR, bulk export, and NLP enrichment.
Read the service overviewThe application contract still looks like FHIR
Even though HealthLake is a managed AWS service, application teams usually interact with it through familiar FHIR shapes: resource reads, search queries, transactions, and bulk export. That matters because the app model remains healthcare-specific rather than becoming an AWS-only dialect.
Representative HealthLake FHIR interactions
Simplified examples of the FHIR-style requests application teams design around when HealthLake is the clinical datastore.
Request
GETANNOTATIONS
Response
Managed service, standard contract
The more HealthLake can remain your FHIR system boundary, the easier it is to keep application teams aligned to open healthcare contracts.
HealthLake publishes a SMART discovery document and a concrete authentication model so application teams can separate three concerns: where to discover the authorization contract, which OAuth endpoints the app should use, and how the bearer token is validated before FHIR data is released. That matters for app launches because discovery, token acquisition, token validation, and FHIR access become explicit architectural steps rather than hidden configuration.
SMART app launch and token-validation path against HealthLake
Loading diagram...
Fetching the SMART on FHIR discovery document
Official HealthLake guide for SMART discovery documents and authorization-metadata lookup.
Review SMART discoveryToken validation using AWS Lambda
Official HealthLake guide describing the Lambda-based token-validation step in SMART-enabled data stores.
Review token validationImport and export jobs are part of the operating model
HealthLake explicitly documents import and export jobs because migration and egress are not side topics in healthcare. Bulk ingestion from upstream repositories, controlled export to analytics environments, and validation settings are operational decisions with audit and cost implications.
The import API makes the data-quality tradeoff explicit through ValidationLevel. In practice, teams use stricter validation when the HealthLake datastore is expected to be a clean longitudinal contract for apps, and they use looser structure-only paths only when a migration phase cannot yet meet the stricter bar.
HealthLake import and export control flow
Loading diagram...
HealthLake import validation tradeoffs
| Validation level | What it enforces | When it fits |
|---|---|---|
| strict | FHIR validation with stronger quality gating before resources land durably | Production-grade application contracts where downstream consumers depend on cleaner resource semantics |
| structure-only | Primarily structural validation while allowing more migration debt through the ingest path | Transitional migration phases where preserving flow matters but remediation is still planned downstream |
Representative StartFHIRImportJob request
Simplified import request showing the operational fields that shape ingestion traceability, output handling, and validation behavior.
Click on an annotation to highlight it in the JSON
StartFHIRImportJob API reference
Official API reference for HealthLake import jobs, including InputDataConfig, JobOutputDataConfig, and ValidationLevel.
Read the import APIValidationLevel in HealthLake
Official HealthLake documentation explaining the strict and structure-only validation choices for imports.
Review validation levelsStartFHIRExportJob API reference
Official API reference for HealthLake export jobs and their output configuration.
Read the export APIKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.