AWS HealthLake
A HIPAA-eligible service to store, transform, query, and share health data in the FHIR R4 standard: data stores, import and export, integrated medical NLP, SQL queries with Athena, SMART on FHIR, and security.
2 min read · Last reviewed · MLA-C02
Sign in to bookmark tutorials and track what you have read.
On this page
Already know this topic?
Try the AWS HealthLake quiz: 5 questions on AWS HealthLake.
What it is
AWS HealthLake is a HIPAA (Health Insurance Portability and Accountability Act)A US law that protects health information. AWS customers can process protected health information on HIPAA-eligible services after accepting a Business Associate Addendum (BAA) with AWS, which is available in AWS Artifact.Glossary entry-eligible service for storing, analyzing, and sharing health data in the FHIR R4 standard (Fast Healthcare Interoperability Resources). A data store indexes records such as patients, observations, conditions, and clinical notes, gives a chronological view of each patient's history, and serves them through standard FHIR API (Application programming interface)A defined way for one program to ask another for data or actions, such as a set of HTTPS requests and responses. Every AWS service is controlled through its API, which the console, the CLI, and the SDKs call for you.Glossary entry. Integrated medical NLP extracts entities and PHI from unstructured notes, and Amazon Athena queries the data with SQL (Structured Query Language)The standard language for querying and changing data in relational databases. Analytics services such as Amazon Athena and Amazon Redshift also use SQL.Glossary entry for analytics and ML (Machine learning)Software that learns patterns from example data to make predictions or decisions, instead of following rules written by hand. A model is first trained on data, then used to make predictions on new data, which is called inference.Glossary entry.
Choose HealthLake when a question asks for a managed FHIR data store, interoperability with healthcare systems, or a single place to analyze structured and unstructured patient data for ML (MLA-C02 task 1.1.8).
Concepts and features
- Import FHIR R4 data from Amazon S3, and export in bulk (FHIR Bulk Data) for analytics.
- Transformation: convert legacy formats such as C-CDA and CSV into FHIR R4 (a data transformation agent is in preview).
- Integrated NLP: medical entities, relationships, traits, and PHI from clinical text, stored as FHIR resources.
- Analytics: query with Athena (SQL); govern access with AWS Lake Formation; build training datasets for SageMaker AI.
- Standards: FHIR R4 APIs, SMART on FHIR authorization with OAuth 2.0 and OIDC (OpenID Connect)A sign-in standard built on OAuth 2.0 that lets an application learn who a user is from a trusted identity provider, through a signed ID token. IAM accepts OIDC providers, so that, for example, a GitHub Actions workflow can assume an IAM role.Glossary entry, US Core.
Security, resilience, performance, and cost
Security
HIPAA eligible; connections use TLS (Transport Layer Security)The protocol that encrypts traffic between a client and a server and lets the server prove its identity with a certificate. It replaced SSL, though the older name is still common; HTTPS is HTTP over TLS.Glossary entry; data is encrypted at rest (with an AWS owned or customer managed KMS key); access through IAM and SMART on FHIR; AWS PrivateLink keeps traffic off the internet; CloudTrail logs activity. Results that inform clinical decisions need review by medical professionals.
Resilience
A managed data store with durable primary storage and an always-updated index.
Performance
The index scales with the data; use bulk export and Athena for large analytical queries instead of many API calls.
Cost
Pay for data storage, queries, and NLP processing; see HealthLake pricing.
Monitoring
CloudWatch metrics, CloudTrail logs, and EventBridge events for data store operations.
Comparisons
| Need | Choose |
|---|---|
| A managed FHIR R4 data store with search, analytics, and NLP | AWS HealthLake |
| Extract entities and PHI from clinical text through an API | Amazon Comprehend Medical |
| Store and analyze medical images or genomics data | AWS HealthImaging or AWS HealthOmics (out of scope for MLA-C02) |
| A general Data lakeA central store for large amounts of structured and unstructured data kept in its original form, usually in Amazon S3, which many tools can analyze. AWS Lake Formation helps build and secure one.Glossary entry | Amazon S3 with Lake Formation and Athena |
Reverse mindmap: when the question points here
- Points to HealthLake
- Managed FHIR R4 data store leads to HealthLake data store
- Query patient records with SQL leads to HealthLake with Athena
- Apps authorize with SMART on FHIR leads to HealthLake FHIR APIs
- Points elsewhere
- Just extract entities from a note leads to Comprehend Medical
Key takeaways
- HealthLake stores and serves health data in FHIR R4, with import, bulk export, and SMART on FHIR.
- Integrated medical NLP turns clinical notes into structured FHIR resources.
- Athena and Lake Formation make the data available for analytics and ML.
- HIPAA eligible, encrypted, with PrivateLink and CloudTrail.