Skip to content
Back to search

HasteHealth

The Open-Source FHIR Server for AI-Native Health Apps

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/HasteHealth/HasteHealth with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/HasteHealth/HasteHealth'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hastehealth--hastehealth/badge.svg)](/listings/hastehealth--hastehealth)

HTML

<a href="/listings/hastehealth--hastehealth"><img src="/api/listings/hastehealth--hastehealth/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 148 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. <img src="https://raw.githubusercontent.com/HasteHealth/HasteHealth/refs/heads/main/markdown_assets/banner.svg" style="height: 350px; width: 500px;" />
  3. </div>
  4. ## Overview
  5. Haste Health is the open-source FHIR server for AI-native health apps. It stores clinical data as FHIR R4 and serves it to your applications, analytics and AI agents through one API, with OAuth2, SMART on FHIR and MCP built in.
  6. Epic, Oracle Health and HL7v2 in. FHIR, SQL-on-FHIR and MCP out. Written in Rust, licensed Apache-2.0, and yours to self-host, or [hosted with a signed BAA](https://haste.health/pricing).
  7. ## Running Locally
  8. The quickest way to get everything running is with the top-level [docker-compose.yml](./docker-compose.yml), which pulls the published images and starts PostgreSQL, the server, the worker, and the admin app.
  9. ```bash
  10. curl -O https://raw.githubusercontent.com/HasteHealth/HasteHealth/main/docker-compose.yml
  11. docker compose up
  12. ```
  13. Once the containers are healthy, open `http://my-health--system.localhost:3001` and log in with:
  14. - username: `myuser@health.org`
  15. - password: `testing_password`
  16. This tenant and user are created automatically by the migration step in the compose file.
  17. If you're actively developing on the backend or frontend instead of just running published images, see [Running for Development](#running-for-development) below.
  18. ## Running for Development
  19. ### 1. Services
  20. ```bash
  21. docker-compose -f docker-services-compose.yml up
  22. ```
  23. This starts a PostgreSQL database and a migration job for the repository and
  24. search index schema migrations.
  25. ### 2. Server
  26. Once the services have finished starting, open a **separate terminal** and go to
  27. the `backend` directory:
  28. ```bash
  29. cd ./backend
  30. ```
  31. then run the server with the following command:
  32. ```bash
  33. cargo run server start
  34. ```
  35. Configuration for the server can be found [here](./backend/documentation/server_configuration.md).
  36. ### 3. Worker
  37. Finally, the worker is the last service to be launched. It handles search
  38. indexing and FHIR subscription processing in the background.
  39. Open a **separate terminal** and go to the `backend` directory:
  40. ```bash
  41. cd ./backend
  42. ```
  43. then run:
  44. ```bash
  45. cargo run worker
  46. ```
  47. Configuration for the worker can be found [here](./backend/documentation/worker_configuration.md).
  48. ### 4. Frontend
  49. In a **separate terminal**, run the frontend admin application:
  50. ```bash
  51. cd <repo-root>/frontend/packages/admin-app
  52. pnpm dev
  53. ```
  54. Then go to `http://my-health--system.localhost:3001` and fill in the following credentials:
  55. - username: `myuser@health.org`
  56. - password: `testing_password`
  57. This tenant and user are created automatically when you run the migration in the earlier docker-compose step.
  58. ## Binaries
  59. One `haste-health` binary runs the server, the worker and the CLI. Install it with npm:
  60. ```bash
  61. npm install -g haste-health
  62. haste-health --help
  63. ```
  64. Or try it without installing:
  65. ```bash
  66. npx haste-health --help
  67. ```
  68. Builds exist for Linux (x64 and arm64) and macOS on Apple Silicon. The Linux builds are static and run on any distribution. On Windows, use it inside WSL. Each [GitHub release](https://github.com/HasteHealth/HasteHealth/releases/latest) also has the binaries attached, for machines without Node.js.
  69. Configuration (`haste.toml` or environment variables) is documented [here for the server](./backend/documentation/server_configuration.md) and [here for the worker](./backend/documentation/worker_configuration.md).
  70. Available commands (`server start`, `worker`, `admin migrate`, `admin tenant create`, etc.) are documented [here](./backend/documentation/cli_commands.md).
  71. ## Docker Images
  72. - [Server](https://github.com/HasteHealth/HasteHealth/pkgs/container/hastehealth%2Fhastehealth)
  73. - [Admin App](https://github.com/HasteHealth/HasteHealth/pkgs/container/hastehealth%2Fadmin-app)
  74. Configuration (`haste.toml` or environment variables) is documented [here for the server](./backend/documentation/server_configuration.md) and [here for the worker](./backend/documentation/worker_configuration.md). See [docker-compose.yml](./docker-compose.yml) for a full working setup.
  75. Available commands (`server start`, `worker`, `admin migrate`, `admin tenant create`, etc.) are documented [here](./backend/documentation/cli_commands.md).
  76. ## RFCs (Request for Comments)
  77. For large feature requests submit RFCS the following is a guide for viewing/submitting RFCs:
  78. RFCs can be written [here](https://github.com/HasteHealth/HasteHealth/tree/main/frontend/packages/website/docs/rfc/proposals).
  79. They should follow the format specified [here](https://github.com/HasteHealth/HasteHealth/blob/main/frontend/packages/website/docs/rfc/format.mdx).
  80. RFCs can be read [here](https://haste.health/docs/category/rfcs)
  81. ## Performance
  82. Using `wrk` for performance testing.
  83. ### Example
  84. ```bash
  85. wrk --latency -s crates/server/benchmarks/transaction.lua -t10 -c10 -d10s http://localhost:3000/w/ohio-health/zb154qm9/api/v1/fhir
  86. ```
  87. #### M3 Macbook Air Local 10 threads Postgres 18
  88. | Latency (percentile:time) | Requests per Second | Concurrent connections | Benchmark |
  89. | --------------------------------------------------- | -------------------------------------------------------- | ---------------------- | ----------------------------------------------------------- |
  90. | 50%:1.2ms, 90%:1.8ms, 99%:3.38 | 10344 | 10 | backend/crates/server/benchmarks/observation.lua |
  91. | 50%:60ms, 90%:73ms, 99%:288.6ms | 251 (100 resources per transaction) (25100 total writes) | 10 | backend/crates/server/benchmarks/transaction.lua |
  92. | 50%:116.73ms 75%:118.39ms 90%:121.45ms 99%:246.90ms | 325 (100 reads per batch) (32500 total reads) | 10 | backend/crates/server/benchmarks/observation_batch_read.lua |

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.