Menu

Individual skill

ehr-quality-governance

Build normalized EHR quality-governance JSON packets by querying a shared read-only FHIR-style REST API. Use this skill whenever the task involves duplicate-chart merge readiness, referral coordination, care-transition packets, quality-governance case review, or batch referral audits against an EHR environment. Trigger on mentions of EHR, FHIR, duplicate candidates, referral packets, care transitions, quality governance, clinical data reconciliation, ICD-10 validation, provider lookup, or answer_template.json with clinical/administrative keys.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_015/fewshot/cc/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# EHR Quality-Governance Packet Builder

Produce normalized JSON packets for healthcare quality-governance workflows by
querying a shared read-only EHR REST API.  Every task provides a concrete
answer template (often named `answer_template.json` or embedded in the prompt)
and points at a task-environment base URL.  The solver's job is to gather
evidence through the API, reconcile it against the template's controlled
vocabularies, and emit strictly conformant JSON.

## API orientation

The task environment provides these endpoint families at `<TASK_ENV_BASE_URL>`.
All are read-only GETs.  Replace `{id}` placeholders with real identifiers
found in upstream responses.