What does Healthpoint Rs do that alternatives don’t?
It is a Rust‑native, read‑only toolchain that preserves raw FHIR while exposing typed domain records, with built‑in provenance tracking and a synthetic‑fixture mode for offline development.

@edithatogo
基本信息
Rust SDK, CLI, and read-only MCP server for licensed Healthpoint HL7 FHIR API access
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"healthpoint": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HEALTHPOINT_API_KEY",
"-e",
"HEALTHPOINT_BASE_URL",
"-e",
"HEALTHPOINT_AUTH_SCHEME",
"ghcr.io/edithatogo/healthpoint-mcp:0.1.0"
],
"env": {
"HEALTHPOINT_API_KEY": "<YOUR_LICENSED_HEALTHPOINT_API_KEY>",
"HEALTHPOINT_BASE_URL": "https://uat.healthpointapi.com/baseR4/",
"HEALTHPOINT_AUTH_SCHEME": "x-api-key"
}
}
}
}Show redacted runtime mode, configuration, and readiness.
Show non-secret endpoint, auth, and documentation notes.
Show the conservative access/export policy before reuse.
Search HealthcareService records by text, codes, region filters, cursor, and limit.
Search HealthcareService records by SNOMED CT code in type, category, or specialty.
Find HealthcareService records near a latitude/longitude point.
Read one HealthcareService by FHIR id.
Read one Location by FHIR id.
Read one Organization by FHIR id.
Read a supported `healthpoint://` resource URI.
Healthpoint Rs is a Rust-first tooling suite for the Healthpoint HL7 FHIR® API, providing a typed client, CLI, read-only MCP server, and a future open‑social‑data adapter. It is designed for developers and researchers who need to query Healthpoint’s directory and service information while bringing their own API key and licence.
Install via cargo install healthpoint-mcp healthpoint-cli (requires Rust), from a source checkout, or through the Smithery marketplace. Configure environment variables such as HEALTHPOINT_MODE (synthetic or live), HEALTHPOINT_API_KEY, and HEALTHPOINT_BASE_URL. Then run the CLI with healthpoint doctor or start the MCP server with cargo run -p healthpoint-mcp.
It is a Rust‑native, read‑only toolchain that preserves raw FHIR while exposing typed domain records, with built‑in provenance tracking and a synthetic‑fixture mode for offline development.
Rust and Cargo. For live mode, a valid Healthpoint API key and licence are required. The MCP server can run in synthetic mode without any API key.
No real Healthpoint API payloads are committed in the repository. Synthetic FHIR fixtures are stored in `crates/healthpoint-testkit/fixtures/`. Local exports are marked with provenance and redistribution status.
The server is read‑only by design: no writes, no scraping fallback, no public proxy mode. It is not a clinical decision‑support system and should preserve Healthpoint attribution, currency, and licensing obligations.
The MCP server uses standard MCP transport (stdio). Authentication is configured via environment variables: `HEALTHPOINT_AUTH_SCHEME` supports `bearer`, `x-api-key`, `header:<name>`, or `none`. Live API calls require `x-api-key` (observed for UAT) and a base URL.
This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,
A curated list of references for MLOps
Painless E2E Automation for Mobile and Web

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
评论