FAQ

The questions users most commonly hit while using Taiwan Health MCP.

Browse by category

Usage

Missing data, keyword search techniques, and so on.

LOINC

Questions about LOINC code mapping and reference values.

Quick answers

Q: Why are some tools missing?

A: Module-backed tools are enabled and disabled automatically according to data-load status. If the corresponding module has not been imported (or has not reached the row-count threshold), its tools are not registered. Check each module's status with health_check first (services), or import the module from its page in the admin console. The tool catalogue under Integrations → MCP tools in the admin console also shows whether each tool is currently registered, and why not.

Q: Why do search results look keyword-only rather than semantic?

A: Semantic / hybrid search needs a reachable embedding endpoint (for example Ollama). The endpoint is configured in the admin console under Integrations → Model endpoints (provider accounts + an embedding route, stored in admin.llm_providers / admin.llm_routes and related tables) — not through environment variables. When it is unset or unreachable, search falls back to keyword mode and the response carries a keyword_only signal. Note also that each module's vectors must be backfilled by its *_embed job first; otherwise you get keyword-only results even with a working endpoint.

Q: A FHIR IG tool returns NO_DEFAULT_IG?

A: The call passed no package_id, no canonical argument identified an owning package, and no default IG is set (with more than one manually installed IG). Set a default IG under FHIR → IG packages in the admin console, or pass package_id. The package actually used is reported in the response's provenance.resolved_by.

Q: Installation and deployment questions?

A: See Getting Started and the Deployment Guide.

Q: FHIR format and validation questions?

A: For basic Condition / Medication conversion see FHIR Tools; for profile- and terminology-level authoring and validation see FHIR IG Service.