Northstar Payer Operations
Core Workflow
- Read the user prompt,
input/payloads/task_context.json, andinput/payloads/answer_template.jsonbefore querying. Treat the template as the output contract. - Get the target ID, reporting date or period, base URL, SQL endpoint, and bearer token from the prompt/context. Use only the exposed business endpoints and SQL endpoint; do not inspect environment source, database, generated data, manifests, or setup files.
- Discover records from the live environment, not from local examples. Start with
/api/tableswhen schema is uncertain. For SQL, use scripts/query_northstar.py. - Pull every record family that can affect the requested disposition: case, member, plan, request lines, policy, criteria, documents, facts, authorizations, appeals, assistance screens, drug trials, claims, claim lines, payment benchmarks, P2P events, or service margin rows as applicable.
- Resolve the business result using the source-precedence rule implied by the work type and answer template. See references/northstar_operations.md for task-specific checklists.
- Build only the JSON object requested by the template. Match required keys, enum values, null handling, ordering rules, date formats, and numeric precision exactly. Do not add prose or markdown.
Basis Audit
Every observed task requires basis_audit. Populate it from the records that actually decide the answer:
source_precedence: choose the template enum matching the decisive rule, such as current clinical records over stale exports, payer appeal before manufacturer assistance, effective benchmark by plan/modifier/date, new patient-specific P2P information, margin threshold before charge sensitivity, or appeal deadline before clinical/payment-integrity routing.controlling_record_ids: IDs for records that directly establish the result, in operational evidence order.exception_record_ids: IDs or criterion/gap identifiers explaining exclusions, missing information, denial reasons, stale sources, or route priority.precedence_record_order: controlling and exception records in precedence order, highest priority first.
Validation Before Final
Before returning, compare the draft JSON against answer_template.json field by field. Recompute arithmetic independently, sort lists as specified by the template, use JSON null for absent nullable values, and omit fields that the template does not allow.