HealthRecordCommunity
FHIR🌏 International🏛 AWSEnriched

SMART on FHIR Support for AWS HealthLake: Enabling Secure Data Access

SMART on FHIR support for AWS HealthLake AWS Documentation Learn

AWS announced support for SMART on FHIR within AWS HealthLake.

December 18, 2024AWS

Summary

AWS HealthLake has implemented SMART on FHIR support, enabling secure and standardized access to medical data from applications. This system utilizes industry-standard authorization servers for authentication and authorization, replacing traditional ID management methods.

Key Players

SMART on FHIRAWS HealthLake

Details

This documentation details the implementation of SMART on FHIR support within AWS HealthLake. By adopting this standard, HealthLake provides an environment where medical applications can securely access the data store. Technically, authentication (AuthN) is handled via OpenID, while authorization (AuthZ)—defining read/write permissions for specific resources—is managed using OAuth 2.0 scopes. This approach significantly simplifies credential management by allowing developers to bypass complex AWS Identity and Access Management (IAM) processes and instead rely on industry-standard authorization servers. HealthLake supports both SMART on FHIR versions 1.0 and 2.0. Developers can create the data store using AWS CLI or SDKs, and subsequently update its configuration—including the authorization server metadata, token validation Lambda function, and authorization strategy—using tools like UpdateFHIRDatastore. This enhances interoperability and security for medical IT systems, offering a robust technical foundation applicable to advanced Japanese electronic health record (EHR) integration. The documentation covers various topics, including utilizing OAuth 2.0 scopes, detailed token validation using AWS Lambda, and implementing fine-grained authorization, serving as a comprehensive reference guide for developers.

Technology Note

FHIR(Fast Healthcare Interoperability Resources)は医療データ交換の国際標準。このエントリの関連技術: SMART ON FHIR

📰
Read Original Article
docs.aws.amazon.com

Original content copyright by respective publishers