Menu

Individual skill

synthetic-clinic-protocol-json

0upvotes

Build strict JSON answers for protocol-bound synthetic clinic tasks that require retrieving a target case, patient-linked clinical records, observations, registry/SDoH facts, and protocol rules; applying controlled enums, time windows, status filters, safety checks, and evidence provenance exactly as requested by an answer template.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_016/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

# Synthetic Clinic Protocol JSON

Use this skill for synthetic clinic decision-support tasks where the user provides a prompt, an answer template, and runtime access to case, patient, observation, medication, allergy, problem, registry, SDoH, imaging, or protocol records. The goal is a single schema-conformant JSON object, not a narrative.

## Workflow

1. Read the prompt and answer template first. Treat the template as the contract: required keys, enum values, object shapes, precision, ordering rules, nullable fields, and extra-key restrictions override normal prose instincts.
2. Identify the target case id, task id, expected case type, target patient id if supplied, clinical review time, target observation codes, and any time windows.
3. Retrieve the target case first, then use its patient id to gather only patient-linked records needed by the template and the applicable protocol. Keep distractors separate from qualifying evidence.
4. Read the relevant protocol material before deciding any assessment, disposition, routing, replacement plan, observation gate, follow-up timing, or medication strategy.
5. Build the JSON from the template outward. Fill identifiers and raw anchors first, then derived protocol decisions, then provenance and safety checks.
6. Validate the final object against the template before answering: no markdown, no comments, no extra top-level keys unless the template explicitly permits them, and no prose where an enum is required.

## Evidence Rules