run-hts-server

Run and configure the HTS FHIR terminology server with bundled seed data.

51|19|Updated Jan 4, 2025
One-click install
npx skills add https://github.com/HeliosSoftware/hfs --skill run-hts-server-heliossoftware
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-hts-server
Source: https://github.com/HeliosSoftware/hfs/tree/main/.claude/skills/run-hts-server
Command: npx skills add https://github.com/HeliosSoftware/hfs --skill run-hts-server-heliossoftware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers need a running HTS terminology server for local FHIR development, but configuring ports, database paths, and seeding terminology data requires knowing the right environment variables and startup commands. ## Core Features & Use Cases - Server Startup: Launch the hts binary with defaults (SQLite, port 8090) or override with HTS_* environment variables on Bash or PowerShell. - Terminology Seeding: Point HTS_BOOTSTRAP_DIR at the bundled terminology-data directory to auto-import ICD-10-CM, ICD-9-CM, NCI Thesaurus, MeSH, NDC, HL7 THO, UCUM, and NUCC on startup, with SHA-256 hashing to skip unchanged files. - Admin UI Control: Access the built-in dashboard at /ui/hts or disable it with HTS_UI_ENABLED=false for gateway deployments. - Use Case: A developer building a FHIR application needs local code lookup; they set HTS_BOOTSTRAP_DIR to the bundled seed set, run cargo run --bin hts, and verify with a TerminologyCapabilities metadata call. ## Quick Start Start the HTS terminology server locally with the bundled terminology seed data and confirm it responds on the health and metadata endpoints.

Frequently Asked Questions about run-hts-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the HTS terminology server locally?▼

Run cargo run --bin hts to start the server with defaults: SQLite storage, port 8090, and no seed data. Override settings with environment variables like HTS_SERVER_PORT and HTS_DATABASE_URL before launching.

How do I seed terminology data into HTS on startup?▼

Set HTS_BOOTSTRAP_DIR to ./crates/hts/terminology-data before starting the server. HTS auto-imports the bundled files and records SHA-256 hashes in a bootstrap_imports ledger, so unchanged files are skipped on restart.

Which terminologies are included in the HTS bundled seed set?▼

The bundled set includes ICD-10-CM, ICD-9-CM, NCI Thesaurus, MeSH via NCI Thesaurus FLAT, NDC, HL7 THO, HL7 v2 tables, UCUM, and NUCC. SNOMED CT, LOINC, RxNorm, CPT, and MedDRA require separate licenses and manual import via hts import.

Does HTS support PostgreSQL instead of SQLite?▼

Yes, HTS_DATABASE_URL accepts either a SQLite file path or a PostgreSQL connection URL. The default is ./data/hts.db for local SQLite storage.

How do I disable the HTS admin UI?▼

Set HTS_UI_ENABLED=false before starting the server. The UI is on by default at /ui/hts, with the root path redirecting there, but operators behind an API gateway can opt out entirely.

How do I verify the HTS server started correctly?▼

Call curl http://localhost:8090/health for a liveness check, then curl http://localhost:8090/metadata?mode=terminology. The second call returns a TerminologyCapabilities resource once terminology data is seeded.