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

# GPRA→SUPRT Grant Profile Configuration — Admin Guide

> No-code path for configuring a SUPRT grant profile (SOR, CCBHC-E) via jurisdiction settings.

## Overview

A **grant profile** is a PF-96 jurisdiction configuration record that tells the SUPRT capture engine which instrument item set to use, how frequently to reassess clients, and the minimum client age for the SUPRT-C self-report instrument. Each grant type (SOR, CCBHC-E, etc.) has its own profile; switching profiles is a configuration change with **zero schema migrations**.

Grant profiles are managed in the Jurisdiction section of your organization's admin settings.

> **AHCCCS cadence note (C3 gate):** The Arizona-specific PF-96 profile for AHCCCS AMPM 320-O cadence values has not yet been activated. Before enabling the AZ profile, your clinical compliance officer must extract the verbatim cadence requirements from the official AHCCCS AMPM 320-O PDF and verify they do not conflict with SUPRT collection windows. See [CL-69 Compliance Sign-Off](../../specs/cl/reviews/CL-69-COMPLIANCE-SIGNOFF.md) Condition C3.

***

## Step 1: Navigate to Admin > Settings > Jurisdiction

1. Log in with an account that has the **Admin** or **Platform Admin** role.
2. From the main navigation, go to **Admin → Settings → Jurisdiction**.
3. The Jurisdiction settings page shows the current active profile and any configured grant profiles.

***

## Step 2: Select or Create a Grant Profile

* To **configure an existing profile**, click the profile name (SOR or CCBHC-E) in the list.
* To **create a new profile**, click **Add Grant Profile** and enter the grant type and a display name.

***

## Step 3: Configure the `clinical.suprt` Rule Pack

Each grant profile has a `clinical.suprt` rule pack with three configurable values:

| Setting                             | Description                                                                             | Example        |
| ----------------------------------- | --------------------------------------------------------------------------------------- | -------------- |
| **Instrument Set ID**               | References a row in `cl_assessment_instruments` — the SUPRT-A/C item set for this grant | `suprt-sor-v1` |
| **Reassessment Cadence**            | Number of months between required follow-up assessments (6-month and annual timepoints) | `[6, 12]`      |
| **Client Instrument Age Threshold** | Minimum client age (in years) for the SUPRT-C self-report instrument                    | `11`           |

Enter or update the values for each setting. The instrument set ID must match a row that is already loaded in `cl_assessment_instruments` (seeded via `supabase/seeds/system-defaults/cl69_suprt_instruments.sql` during database initialization).

***

## Step 4: Save

Click **Save** to apply the profile. Changes take effect for the **next intake session** — active open episodes are not retroactively changed. No database migration is required; the values are read at runtime from the PF-96 profile.

To verify the change, open a client chart, click the **Outcomes** tab, and confirm that the SUPRT dialog shows the expected item set when you click **Start SUPRT**.

***

## Notes and Caveats

* **Instrument set must be seeded.** If the instrument set ID you enter does not exist in `cl_assessment_instruments`, the SUPRT dialog will open with an empty item list and show a warning. Coordinate with your implementation team to run the system-defaults seed.
* **SUPRT codebook validation (C1/C2).** Before publishing SUPRT-A/C instrument definitions to production, your grant manager must validate the item set against the SAMHSA published codebook (available from SPARS). The NOMs domain list in the seed must also be reconciled against the official SAMHSA NOMs PDF. These are human-gate conditions tracked in the compliance sign-off.
* **AHCCCS AMPM 320-O (C3).** The AZ jurisdiction PF-96 profile for AHCCCS cadence coexistence must NOT be activated until clinical compliance has extracted and verified the verbatim cadence values from the official PDF. Using incorrect cadence values could result in AHCCCS non-compliance.
* **Profile isolation.** SUPRT cadences and item sets for one grant type (e.g., SOR) never affect another grant type (e.g., CCBHC-E). Each profile is independently configured.