Menu

Individual skill

ehr-governance-json-packets

Build normalized JSON packets and audits from a read-only EHR quality/referral API. Use when Codex must prepare duplicate-chart merge readiness packets, referral coordination packets, care transition summaries, ServiceRequest quality reviews, or referral batch audits from prompt IDs, environment_access.md, and answer_template.json.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_015/self/self_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 JSON Packets

## Core Workflow

1. Read the user prompt and the referenced `answer_template.json` before querying data.
2. Read `environment_access.md` for the base URL and allowed endpoints. Use only those endpoints and the supplied files.
3. Extract all concrete IDs from the prompt and payloads: patient IDs, duplicate candidate IDs, referral IDs, batch IDs, provider IDs, and service request IDs.
4. Fetch direct records by ID first, then fetch related patient chart endpoints as needed: conditions, medications, allergies, encounters, immunizations, documents, disclosures, service requests, duplicate candidates, referrals, ICD-10 records, service-code records, and providers.
5. Treat list/search endpoints as broad result sets. Filter client-side by exact `batch_id`, `referral_id`, `candidate_id`, `patient_id`, or provider ID.
6. Build an evidence map before writing JSON. Record which source supplied each ID, status, code validation result, provider contact, active-list key, document, encounter, disclosure, and audit entry.
7. Return JSON only, matching the template's exact top-level keys, field types, enum strings, nullability, and ordering instructions.

## Normalization Rules