> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rcintell.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Encounter check

> Pre-visit PA + NCCI + payment in one call

Use `POST /v1/encounter/check` when you already know the payer and the CPT/HCPCS list for a visit. It is the same determinations as `GET /v1/prior-auth/check`, NCCI validate, and a payment estimate — one round trip.

Knowledge resolve (`POST /v1/knowledge/resolve`) is the CCN stack. Encounter check is the pre-visit bundle.

## REST

```bash theme={null}
curl -X POST https://api-dev.rcintell.com/v1/encounter/check \
  -H "X-API-Key: kp_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "payer_slug": "uhc",
    "cpt_codes": ["27447", "99213"],
    "ccn": "170001",
    "state": "KS",
    "plan_type": "commercial"
  }'
```

| Field                                      | Required | Notes                            |
| ------------------------------------------ | -------- | -------------------------------- |
| `payer_slug`                               | yes      | Directory slug or alias          |
| `cpt_codes`                                | yes      | 1–25 codes                       |
| `ccn`                                      | no       | Facility — GPCI + PA overrides   |
| `state` / `plan_type` / `place_of_service` | no       | Same meaning as prior-auth check |
| `date_of_service` / `visit_count`          | no       | Threshold PA and payment as-of   |

Response: `pa_results`, `ncci_conflicts`, `payment_estimates`, `warnings`, `encounter_ready`.

Pre-submission (filing deadline + NCCI, no PA): `POST /v1/encounter/claim-check`.

## MCP

Tool name: `check_encounter`. Same body as REST.

```json theme={null}
{
  "name": "check_encounter",
  "arguments": {
    "payer_slug": "uhc",
    "cpt_codes": ["27447"],
    "ccn": "170001",
    "state": "KS"
  }
}
```