A serverless framework for deploying customizable FHIR-compliant healthcare data servers on AWS.
FHIR Works on AWS is a serverless framework that deploys a Fast Healthcare Interoperability Resources (FHIR) server on AWS. It provides a customizable, standards-compliant solution for managing and exchanging healthcare data, enabling organizations to implement FHIR APIs without building infrastructure from scratch. The framework handles core FHIR operations, search, authentication, and data persistence using AWS services.
Healthcare technology developers, health IT teams, and organizations needing to implement FHIR-compliant data servers for interoperability, clinical data exchange, or digital health applications.
It offers a production-ready, scalable FHIR server on AWS with built-in compliance, reducing development time and infrastructure management. Its modular design allows customization of authentication, persistence, and search components to fit specific regulatory or business requirements.
A serverless implementation of the FHIR standard that enables users to focus more on their business needs/uniqueness rather than the FHIR specification
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports CRUD operations, search, and versioned reads for R4 and STU3 resources, ensuring interoperability with healthcare systems as per HL7 specifications.
Built on AWS Lambda, API Gateway, and DynamoDB, providing automatic scaling and managed infrastructure, reducing operational overhead for healthcare data loads.
Offers both Cognito RBAC for simplicity and SMART-on-FHIR for granular, standards-based access, allowing customization based on security needs.
Uses single-function components for routing, auth, persistence, and search that can be swapped or extended, enabling tailored implementations for specific use cases.
The history component is explicitly not implemented, limiting audit trails and version searching capabilities that are part of the FHIR standard.
Only supports transaction bundles of 25 entries or fewer, which may hinder bulk data operations compared to other FHIR servers with higher limits.
Requires deploying and configuring multiple AWS services, with steps like retrieving variables from logs and handling security updates, adding steep learning curves.