Guide to Building Multi-Tenant FHIR Servers with AWS HealthLake
Building a multi-tenant FHIR server with AWS HealthLake AWS FHIR
AWS is building a multi-tenant FHIR server utilizing AWS HealthLake.
Summary
This article technically explains the implementation of multi-tenant FHIR servers using AWS HealthLake. It provides architectural design guidelines for multiple organizations (tenants) to share and utilize data while ensuring high levels of security and scalability in data management.
Key Players
Details
The article addresses the challenge of securely and efficiently managing patient data in healthcare technology. It focuses on how to achieve high levels of data isolation and access control using AWS HealthLake, a FHIR-native, fully managed service, allowing multiple tenants (organizations or hospitals) to share data. Multi-tenancy design requires considering whether to use physical or logical separation. AWS HealthLake supports FHIR R4 transactions. A key decision is whether to manage all tenants in a single data store or to provision separate data stores for each tenant. Regarding authentication, two methods are discussed: SMART on FHIR (based on OAuth 2.0) and SigV4 (AWS's proprietary signing process). While SMART on FHIR is optimal for resource-level permission management in clinical applications, SigV4 is better suited for tight AWS service integration and programmatic access patterns. The article provides design guidelines by comprehensively considering these technical aspects (data isolation, authentication methods, cost) to build a scalable and compliant multi-tenant solution.
Technology Note
FHIR（Fast Healthcare Interoperability Resources）は医療データ交換の国際標準。このエントリの関連技術: FHIR
Original content copyright by respective publishers