fhir-validationlisted

# Records FHIR Validation Validate FHIR resources with Records and local project tooling. Prefer local or already configured execution. Do not send clinical data, patient data, FHIR server URLs, or full patient resources to external services unless the user explicitly consents for this task. ## Arguments Treat the user request as a file, directory, JSON resource, OperationOutcome, FHIR URL, or validation goal. If no target is inferable, ask one concise question. ## Bundled Paths Resolve `<skill-root>` to the absolute directory containing this `SKILL.md`. Resolve `<plugin-root>` two directories above `<skill-root>`. In Claude Code `${CLAUDE_PLUGIN_ROOT}` is also the plugin root; in Codex derive it from the installed skill path. Never resolve bundled scripts relative to the user's workspace. ## Fast Start For file or directory validation, first run the deterministic detector and runtime planner when available: ```bash node "<skill-root>/scripts/detect-fhir-project.mjs" <target-or-repo> node "<skill-root>/scripts/plan-runtime.mjs" <target-or-repo> ``` Use their output to pick source directories, generated directories, available runtimes, privacy gates, and validation order. Then choose the first suitable mode: 1. Records MCP tools, when available. 2. Records API, only when `RECORDS_API_URL` is configured and the privacy boundary is acceptable. 3. Records CLI, using `records validate-file <target>`. 4. Existing local profile-aware validators such as SUSHI, IG Publisher