Menu

Individual skill

ehr-governance-packet

0upvotes

Generate a normalized EHR quality-governance / referral-coordination packet or audit as JSON from a read-only EHR API. Use when a task supplies a prompt plus an answer_template.json and asks to prepare a duplicate-merge readiness packet, referral coordination packet, care-transition packet, ServiceRequest/duplicate review, or referral-batch audit. Fetches evidence only over the network via environment_access.md, reconciles records, classifies quality signals, cites evidence IDs, excludes distractors, and emits sorted JSON conforming to the template.

experiments/claude_code_glm_5_2_max/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 Governance Packet & Audit Generation

This skill produces a single normalized JSON object for EHR quality-governance and
referral-coordination tasks. A task in this family always provides:

- `prompt.txt` — the packet type and the concrete IDs in scope (candidate / patient /
  referral / batch / provider / service-request).
- `input/payloads/answer_template.json` — the exact output contract: required
  top-level keys, field types, enum `allowed_values`, and per-field ordering rules.
- `environment_access.md` (staged at `/work/environment_access.md`) — the only
  network access path: the base URL and the allowed read-only GET endpoints.

The template is the contract. The environment API is the only source of truth.
Never mix the two: do not invent values, and do not carry values over from any