What problem does it solve? Developers working on the Helios FHIR Server often need both the HFS FHIR server and the HTS terminology server running together so that terminology-backed features like the FHIR search :in modifier and FHIRPath memberOf()/subsumes() functions work locally. This Skill provides the exact startup commands and environment variable wiring to run both servers in a coordinated local setup. ## Core Features & Use Cases - Combined Server Startup: Step-by-step bash and PowerShell commands to launch HTS (seeded from bundled terminology data) followed by HFS wired to it via HFS_TERMINOLOGY_SERVER and FHIRPATH_TERMINOLOGY_SERVER. - Terminology-Backed Features: Enables ValueSet expansion filtering via the search :in modifier, FHIRPath memberOf()/subsumes() delegation, and the crates/ui terminology-proxy handlers. - Sanity Checks: Ready-made curl commands to verify health endpoints, TerminologyCapabilities metadata, and the HTS admin UI. - Use Case: When developing HFS features that delegate terminology operations to HTS, or building UI terminology pages that proxy through HFS, use this Skill to bring up the full local stack in two terminals. ## Quick Start Ask the assistant to start the HTS terminology server seeded with the bundled terminology data and then start the HFS server pointed at it for local development.
