H
HasteHealth/HasteHealth
The Open-Source FHIR Server for AI-Native Health Apps
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"hastehealth-hastehealth": {
"command": "npx",
"args": ["haste-health"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"hastehealth-hastehealth": {
"command": "npx",
"args": ["haste-health"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio hastehealth-hastehealth -- npx haste-health
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 86 ★ · HasteHealth/HasteHealth · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-25 · last seen 2026-11-14 · seen 24× · listed by 1 sources
- Score
- score 103 · 86 ★ · 1 sources · repo
- Install
npx haste-health
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx haste-health. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
HasteHealth/HasteHealth；first catalogued 2026-10-25；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.## Overview
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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.
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.
## Running Locally
The quickest way to get everything running is with the top-level docker-compose.yml, which pulls the published images and starts PostgreSQL, the server, the worker, and the admin app.
bash
curl -O https://raw.githubusercontent.com/HasteHealth/HasteHealth/main/docker-compose.yml
docker compose up
Once the containers are healthy, open http://my-health--system.localhost:3001 and log in with:
username: myuser@health.org
password: testingpassword
This tenant and user are created automatically by the migration step in the compose file.
If you're actively developing on the backend or frontend instead of just running published images, see Running for Development below.
## Running for Development
### 1. Services
bash
docker-compose -f docker-services-compose.yml up
This starts a PostgreSQL database and a migration job for the repository and
search index schema migrations.
### 2. Server
Once the services have finished starting, open a separate terminal and go to
the backend directory:
bash
cd ./backend
then run the server with the following command:
bash
cargo run server start
Configuration for the server can be found here.
### 3. Worker
Finally, the worker is the last service to be launched. It handles search
indexing and FHIR subscription processing in the background.
Open a separate terminal and go to the backend directory:
bash
cd ./backend
then run:
bash
cargo run worker
Configuration for the worker can be found here.
### 4. Frontend
In a separate terminal, run the frontend admin application:
bash
cd /frontend/packages/admin-app
pnpm dev
Then go to http://my-health--system.localhost:3001 and fill in the following credentials:
username: myuser@health.org
password: testingpassword
This tenant and user are created automatically when you run the migration in the earlier docker-compose step.
## Binaries
One haste-health binary runs the server, the worker and the CLI. Install it with npm:
bash
npm install -g haste-health
haste-health --help
Or try it without installing:
bash
npx haste-health --help
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 also has the binaries attached, for machines without Node.js.
Configuration (haste.toml or environment variables) is documented here for the server and here for the worker.
Available commands (server start, worker, admin migrate, admin tenant create, etc.) are documented here.
## Docker Images
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.
## Running Locally
The quickest way to get everything running is with the top-level docker-compose.yml, which pulls the published images and starts PostgreSQL, the server, the worker, and the admin app.
bash
curl -O https://raw.githubusercontent.com/HasteHealth/HasteHealth/main/docker-compose.yml
docker compose up
Once the containers are healthy, open http://my-health--system.localhost:3001 and log in with:
username: myuser@health.org
password: testingpassword
This tenant and user are created automatically by the migration step in the compose file.
If you're actively developing on the backend or frontend instead of just running published images, see Running for Development below.
## Running for Development
### 1. Services
bash
docker-compose -f docker-services-compose.yml up
This starts a PostgreSQL database and a migration job for the repository and
search index schema migrations.
### 2. Server
Once the services have finished starting, open a separate terminal and go to
the backend directory:
bash
cd ./backend
then run the server with the following command:
bash
cargo run server start
Configuration for the server can be found here.
### 3. Worker
Finally, the worker is the last service to be launched. It handles search
indexing and FHIR subscription processing in the background.
Open a separate terminal and go to the backend directory:
bash
cd ./backend
then run:
bash
cargo run worker
Configuration for the worker can be found here.
### 4. Frontend
In a separate terminal, run the frontend admin application:
bash
cd /frontend/packages/admin-app
pnpm dev
Then go to http://my-health--system.localhost:3001 and fill in the following credentials:
username: myuser@health.org
password: testingpassword
This tenant and user are created automatically when you run the migration in the earlier docker-compose step.
## Binaries
One haste-health binary runs the server, the worker and the CLI. Install it with npm:
bash
npm install -g haste-health
haste-health --help
Or try it without installing:
bash
npx haste-health --help
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 also has the binaries attached, for machines without Node.js.
Configuration (haste.toml or environment variables) is documented here for the server and here for the worker.
Available commands (server start, worker, admin migrate, admin tenant create, etc.) are documented here.
## Docker Images
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/hastehealth-hastehealth/)
- Source
- github · https://github.com/HasteHealth/HasteHealth
- Browse by field
- Open source
- Traction
- 86 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.