Menu

Individual skill

cedar-ridge-intake-reconciliation

0upvotes

Reconcile Cedar Ridge intake portal data into strict JSON templates for patient access verification, specialty referral readiness, dialysis transfer packets, chronic-care program panels, and referral-to-chart activation. Use when a task provides Cedar Ridge portal data plus an answer template and asks for controlled-value intake, referral, transfer, program enrollment, or chart activation output.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_013/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
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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 prompt and answer template first. Treat the template as the contract for required keys, allowed values, ordering, and count fields.
2. Identify the target cohort from the prompt and template: roster, referral batch, transfer batch, program code, or explicit patient/referral/transfer IDs.
3. Pull structured portal data for only that cohort. Prefer database or JSON joins over screen scraping or manual transcription.
4. Join the cohort to all relevant support tables before deciding statuses:
   - Patient demographics and contact availability.
   - Coverage, PBM, pharmacy preference, lifestyle, and clinical history for access verification.
   - ICD metadata, referral flags, duplicate indicators, authorization fields, and chart artifacts for referrals.
   - Transfer request rows, finalized packet documents, transportation, and capacity for dialysis transfer work.
   - Program candidates, chart artifacts, and clinical history for chronic-care enrollment.
5. Derive controlled values from source records, then build the exact JSON shape. Sort rows and nested lists as the template specifies. Treat reason-code arrays as sets unless the template says otherwise.
Back to top