What problem does it solve? Working with the HFS Terminology Server requires knowing its runtime configuration, environment variables, terminology import formats, and FHIR terminology API endpoints, which are scattered across the codebase. ## Core Features & Use Cases - Runtime Configuration: Set up the hts binary with environment variables for port, host, database URL, storage backend, CORS, and bootstrap directory sync. - Terminology Import: Bulk import HL7 FHIR NPM packages, SNOMED CT RF2, LOINC, ICD-10-CM, and RxNorm RRF files with format auto-detection and batch controls. - Terminology APIs: Use FHIR operations like $lookup, $expand, $validate-code, $subsumes, $translate, and $closure on CodeSystem, ValueSet, and ConceptMap resources. - Use Case: Import a SNOMED CT RF2 release into a local SQLite terminology database, then validate codes against a ValueSet through the HTS REST API while HFS delegates memberOf() checks to it. ## Quick Start Start the HTS terminology server with cargo run --bin hts and import my terminology package into it.