Menu

Individual skill

ehr-governance-packets

0upvotes

Produce normalized JSON for EHR quality-governance / care-coordination packet tasks against a read-only EHR "quality API": duplicate-chart merge-readiness packets, specialty referral coordination letters, care-transition/handoff packets, duplicate-review + service-request validation, and referral-batch audits. Use whenever a prompt hands you case objects (patient IDs, a duplicate candidate ID, a referral or referral-batch ID, a service-request ID, a recipient provider) plus an answer_template JSON schema and asks for a single normalized JSON object reconciling the chart, coding, evidence, provider contacts, and readiness/disposition. Triggers: "merge readiness", "referral coordination packet", "care transition packet", "duplicate review", "ServiceRequest quality", "referral audit", "normalized JSON conforming to answer_template".

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_015/reflect-3/reflect-3_attempt_03/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 governance / coordination packets

These tasks all share one shape: read a **read-only EHR quality API**, reconcile
the evidence, and emit **one normalized JSON object that conforms exactly to the
provided `answer_template`**. The template — not your prose — is the contract.
Getting these right is mostly about (a) obeying the template's keys/enums/
ordering literally and (b) applying a small set of reconciliation rules
consistently, while ignoring planted distractors.

## Procedure

1. **Read the answer template first.** It lists every required top-level key,
   the enum vocabulary for each field, ordering rules, and which arrays are
   "sets". Build your output to match its keys and types one-for-one. If it
Back to top