Menu

Individual skill

cedar-ridge-intake-reconciliation

0upvotes

Reconcile Cedar Ridge Intake Coordination Portal data into constrained JSON outputs. Use when a task asks Codex to audit or prepare Cedar Ridge patient access rosters, referral batches, dialysis transfers, chronic-care program enrollment panels, referral-to-chart activation, or similar intake workflows using TASK_ENV_BASE_URL and an answer_template.json schema.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_013/fewshot/fewshot_attempt_01/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

# Cedar Ridge Intake Reconciliation

## Core Workflow

1. Read the user prompt and every file under `input/payloads/` before querying the portal. Treat `answer_template.json` as the source of truth for required keys, constants, controlled values, list ordering, nullability, and summary fields.
2. Use the base URL from `environment_access.md`. Use only the listed Cedar Ridge endpoints and the read-only `POST /query` endpoint.
3. Scope records from the prompt/template: roster ID, referral batch ID, transfer batch ID, program code, and any required patient/referral/transfer IDs. Do not reuse IDs, dates, counts, or row outcomes from prior examples.
4. Prefer one `POST /query` SELECT with joins for batch work, then use REST endpoints for spot checks:
   - `patients`, `clinical_history`, `chart_artifacts`
   - `intake_rosters`, `coverage`, `pbm`, `patient_pharmacy`, `pharmacies`, `lifestyle`
   - `referrals`, `icd_codes`, `documents`
   - `transfer_requests`, `facility_capacity`
   - `program_candidates`
5. Build intermediate issue sets per patient/referral/transfer. Derive summaries from the final rows, not from separate assumptions.
Back to top