Menu

Individual skill

ehr-governance-packet

0upvotes

Produce the normalized JSON deliverable for an EHR quality-governance task against a read-only EHR/referral API. Use whenever a prompt gives one or more case objects (patient IDs, a duplicate-candidate ID, a referral ID or batch ID, a ServiceRequest ID, and/or a recipient provider ID), points at an EHR environment base URL, and asks for JSON that conforms to a supplied `answer_template.json`. Covers duplicate-chart merge-readiness packets, referral coordination packets, care-transition handoff packets, duplicate + ServiceRequest quality reviews, and referral-batch audits.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_015/fewshot/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

You are handed a prompt plus a machine-readable output contract
(`input/payloads/answer_template.json`) and a read-only EHR governance API. Your
job is to gather evidence from the API, apply the normalization/reconciliation
rules below, and emit **one JSON object that exactly conforms to the template** —
no prose, no markdown fences, no fields the template does not define.

The task differs run to run, but the machinery is always the same. Do not
hard-code any values you may have seen before: every ID, key, code, provider,
disposition, and count must be re-derived live from the environment for the
current case.

## 0. Orient
Back to top