| Tests |
|
| Infra |
|
| Quality |
|
| Security |
|
| Stack |
|
OpenEMR on Amazon ECS with Fargate: automatic scaling, encryption, backups, and monitoring, deployed with one command.
Important
HIPAA notice. This project uses HIPAA-eligible AWS services and is checked against HIPAA security rules, but deploying it does not make you HIPAA compliant. Compliance also requires a signed Business Associate Addendum (BAA) with AWS for each account, your own policies and procedures, staff training and access controls, and regular risk assessments. See Security and compliance.
OpenEMR is free, open-source software for electronic health records and medical practice management. This repository sets up a complete, production-style OpenEMR installation in your own AWS account, using infrastructure-as-code written with the AWS Cloud Development Kit (CDK). You edit a short settings file, run one command, and roughly 40 minutes later you have OpenEMR running behind HTTPS.
Who it's for:
- Clinics, IT teams, and consultants who want OpenEMR on AWS without managing servers.
- People evaluating OpenEMR who want a realistic, secure test environment they can delete afterwards.
- Developers who want to extend or contribute to an OpenEMR-on-AWS reference architecture.
You don't need to be an AWS expert. The Get Started guide explains every step, and the glossary defines the jargon.
You pay AWS directly for what the deployment uses. The project's baseline estimate is about $320 per month (roughly $10–11 per day) for the default settings in us-west-2 with light usage. Most of that is the two always-on application containers, the database's minimum capacity, and two NAT gateways. Costs go up as traffic grows and the system scales out, and they vary by AWS Region. Charges continue until you delete the deployment. See Costs for the full breakdown and ways to reduce it. If you only need a small installation, OpenEMR's AWS Marketplace offerings may be cheaper.
- Your users reach OpenEMR over HTTPS through an Application Load Balancer, which is protected by a web application firewall (AWS WAF) and only accepts the IP addresses you allow.
- OpenEMR runs in containers on AWS Fargate, so there are no servers to patch. At least two copies run at all times, and more start automatically when traffic grows.
- Patient data lives in an Aurora MySQL Serverless v2 database that grows and shrinks its capacity on demand.
- Shared files (documents, images, site configuration) live on Amazon EFS, a network drive every container can use. A Valkey cache (ElastiCache Serverless) stores user sessions.
- Everything is encrypted with keys in AWS KMS, passwords are generated and stored in Secrets Manager, and AWS Backup takes automatic daily, weekly, and monthly backups.
- Everything runs in a private network (VPC) spread across two data centers (Availability Zones) for resilience.
For the full tour, see Architecture.
| I want to... | Start here |
|---|---|
| Deploy it. Get OpenEMR running in my AWS account. | Get Started guide |
| Understand it. Learn how the pieces fit together before I commit. | Architecture |
| Contribute or maintain it. Change the code, run tests, cut releases. | CONTRIBUTING.md and the Maintainer guide |
Not sure? The documentation home routes you by goal.
| Section | Pages |
|---|---|
| Get started | Step-by-step deployment · Glossary |
| Guides | Configuration · HTTPS and DNS · Backup and restore · Importing an existing OpenEMR · Database access · REST and FHIR APIs · Analytics environment · Optional features · Credential rotation · Load testing · Local testing |
| Reference | Architecture · Costs · Security and compliance · cdk-nag suppressions · Troubleshooting |
| Maintainers | Overview · CI workflows · Live end-to-end tests · Floci emulator · Knowledge MCP server · Deployment timing |
| Design decisions | ADR 0001: Guarded OpenEMR import |
Day-to-day backups can also be browsed and restored from an interactive terminal app, the Backup Manager TUI. See Backup and restore.
- Something broken? Check Troubleshooting first.
- Found a bug or have a feature idea? Open an issue on GitHub.
- Questions about OpenEMR itself? Ask the OpenEMR community forum.
- Security issue? Don't open a public issue. Follow the process in CONTRIBUTING.md.
This repository is released under the MIT No Attribution License. OpenEMR itself is licensed under GPL-3.0 and is downloaded as a container image at deploy time. This project depends on other third-party open-source packages, each under its own license; review them against your organization's open-source policy before use.
This is sample infrastructure code provided as-is. You are responsible for testing, securing, and operating it, and for making sure your use complies with the laws and regulations that apply to you (for example, HIPAA). See Security and compliance.
