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.