Individual skill

ehr-governance-packet

Build the normalized JSON deliverable for an EHR quality-governance task — duplicate-merge readiness packet, referral coordination packet, care-transition packet, ServiceRequest/duplicate quality review, or referral-batch audit — by reading the case from input/prompt.txt, treating input/payloads/answer_template.json as the exact output contract, and pulling every value from the read-only EHR API described in environment_access.md. Use whenever a task references that API, an answer_template.json, patients/referrals/duplicates/service-requests, ICD-10 or provider directories, and asks for normalized JSON only.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_015/fewshot/fewshot_attempt_02/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 & audit builder

You produce one normalized JSON object for an EHR quality-governance case. Every
answer value comes from a live, read-only EHR API. The task ships an
`answer_template.json` that is the **exact schema contract** for your output.

## Two rules that override everything else

1. **The environment is the only source of truth.** Never invent, guess, or carry
   over a value from an example, a previous case, or these instructions. If a field
   is not derivable from the API, it does not go in the answer. Re-fetch rather than
   assume.
2. **The template is the contract, not a suggestion.** Match its top-level keys,
   nesting, field names, value types, and `enum:` vocabularies exactly. Emit **JSON