Menu

Individual skill

ehr-governance-packet

0upvotes

Produce the normalized JSON deliverable for an EHR quality-governance task — duplicate-merge readiness packets, specialty referral coordination packets, care-transition handoff packets, duplicate-review + ServiceRequest QA, and referral-batch audits. Use when a prompt gives clinical/governance object IDs (patients, duplicate candidates, referrals, ServiceRequests, batches) plus an `input/payloads/answer_template.json`, and asks for normalized JSON that reconciles a read-only EHR/referral environment against that template. Read this before gathering data or writing the answer.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_015/reflect-3/reflect-3_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 tasks

These tasks share one shape: a prompt names some governance objects (patient IDs,
a duplicate candidate, a referral, a ServiceRequest, a batch) and points to an
`input/payloads/answer_template.json`. A read-only EHR/referral environment is
described in the task's own access file. Your job is to gather evidence from that
environment and emit **JSON that conforms exactly to the answer template** —
right keys, right enum tokens, right ordering, no prose.

The winning approach is evidence-driven and template-driven, not narrative. The
template is the spec; the environment is the source of truth; your output is a
faithful reconciliation of the two.

## Workflow