Healthpoint Rs

What is Healthpoint Rs?

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.

How to use Healthpoint Rs?

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.

Key features of Healthpoint Rs

• Read‑only MCP server and CLI for Healthpoint FHIR data.
• Search, nearby, and get operations on Services, Locations, and Organizations.
• Supports synthetic fixture mode for offline testing.
• Bring‑your‑own‑key: code does not bundle access or data rights.
• Provenance metadata on all exports (retrieval time, licence, tool version).
• MCP server exposes 10 tools, 3 resources, 4 resource templates, and 2 prompts.

Use cases of Healthpoint Rs

• Query healthcare services by text, SNOMED CT code, or geographic proximity.
• Export search results as JSON, JSONL, or CSV for offline analysis.
• Validate and inspect Healthpoint API behaviour before live integration.
• Build MCP‑enabled AI assistants that can retrieve Healthpoint directory data.
• Set up a synthetic testing environment without requiring a live API key.

FAQ from Healthpoint Rs

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.

What are the runtime requirements?

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.

Where does data live?

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.

What are the known limitations?

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.

What transports and authentication are supported?

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.