Building a multi-tenant FHIR server with AWS HealthLake
Industries Blog
This article provides a comprehensive guide to building multi-tenant FHIR servers using AWS HealthLake, focusing on two primary implementation approaches:
- Option A: Full tenant separation using unique AWS HealthLake data stores with different KMS keys
- Option B: Single data store with logical tenant separation using FHIR tags and security labels
Key considerations include:
- Authentication methods: SMART on FHIR vs AWS SigV4
- Data isolation requirements
- Cost and performance implications
- Use of routers (Lambda or API Gateway) for request management
The article emphasizes balancing security, cost, and scalability when designing multi-tenant healthcare applications with AWS HealthLake.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
May 20
2026
2026
FHIR-powered Care Continuum on AWS HealthLake
Jun 9
2025
2025
AWS HealthLake launches in the EU: Unlocking the future of interoperability and FHIR-based innovation
Oct 20
2025
2025
AWS HealthLake Launches in Canada: Healthcare Data Innovation with FHIR
Aug 5
2025
2025
Build a multi-tenant healthcare system with Amazon OpenSearch Service
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.