Northstar Payer Ops
Use this skill to produce a single JSON answer for Northstar payer-operations tasks. The task prompt, input/payloads/task_context.json, and input/payloads/answer_template.json are the output contract.
Core Workflow
- Read the prompt, task context, and answer template before querying the environment.
- Identify the target business object: case ID, appeal ID, claim ID, P2P case, or queue row IDs.
- Use only the network environment named in the task. If the prompt shows a placeholder base URL, resolve it from the task's environment access note. Use the task-provided bearer token for SQL.
- Query narrowly. Prefer target-specific business endpoints such as
GET /api/cases/{case_id}. Use POST /sql/query with JSON body {"sql": "..."} only for tables and IDs needed by the target.
- Do not list unrelated records, inspect task-environment source files, or infer from records outside the requested target and its linked records.
- Fill exactly the keys required by the answer template. Respect enum choices, list ordering, null handling, date formats, and numeric precision from the template.
- Return JSON only, with no markdown or narrative.
For field derivations, table relationships, formulas, and audit rules, read references/northstar-payer-ops.md.
Output Discipline
- Treat
answer_template.json as authoritative when field names, enum values, ordering, or precision differ from intuition.
- Use environment records over local memo wording when the environment supplies structured facts, statuses, criteria, lines, rates, or finance rows.
- Use the task context for scope limits such as queue row IDs, reporting period, threshold definitions, and requested as-of date.
- Derive values from current target records; do not reuse values from examples or from unrelated cases.
- When a required value is absent, use the template's allowed null, empty list, status, or route rather than adding explanatory fields.
1---2name: northstar-payer-ops-123description: Resolve Northstar Health Plan payer-operations tasks against the shared task environment and return exact JSON outputs. Use for prior authorization, pharmacy appeal, peer-to-peer, claim repricing, payment-integrity, rate-schedule, and therapy margin queue prompts that provide an answer_template.json and Northstar environment access.4metadata:5 source: https://skillmd.com/skills/prism-shadow/northstar-payer-ops-126---78# Northstar Payer Ops910Use this skill to produce a single JSON answer for Northstar payer-operations tasks. The task prompt, `input/payloads/task_context.json`, and `input/payloads/answer_template.json` are the output contract.1112## Core Workflow13141. Read the prompt, task context, and answer template before querying the environment.152. Identify the target business object: case ID, appeal ID, claim ID, P2P case, or queue row IDs.163. Use only the network environment named in the task. If the prompt shows a placeholder base URL, resolve it from the task's environment access note. Use the task-provided bearer token for SQL.174. Query narrowly. Prefer target-specific business endpoints such as `GET /api/cases/{case_id}`. Use `POST /sql/query` with JSON body `{"sql": "..."}` only for tables and IDs needed by the target.185. Do not list unrelated records, inspect task-environment source files, or infer from records outside the requested target and its linked records.196. Fill exactly the keys required by the answer template. Respect enum choices, list ordering, null handling, date formats, and numeric precision from the template.207. Return JSON only, with no markdown or narrative.2122For field derivations, table relationships, formulas, and audit rules, read [references/northstar-payer-ops.md](references/northstar-payer-ops.md).2324## Output Discipline2526- Treat `answer_template.json` as authoritative when field names, enum values, ordering, or precision differ from intuition.27- Use environment records over local memo wording when the environment supplies structured facts, statuses, criteria, lines, rates, or finance rows.28- Use the task context for scope limits such as queue row IDs, reporting period, threshold definitions, and requested as-of date.29- Derive values from current target records; do not reuse values from examples or from unrelated cases.30- When a required value is absent, use the template's allowed null, empty list, status, or route rather than adding explanatory fields.