Individual Rationale
1. What does this feature do? (High-Level Overview)
Section titled “1. What does this feature do? (High-Level Overview)”This feature captures the individualized clinical rationale of the BIP so clinicians can document the client-specific medical necessity narrative in one focused section, linking case formulation to why this specific intervention plan is appropriate for this client, and supporting consistency for care planning, payer-facing documentation, and multidisciplinary communication.
2. Who is this for? (Roles & Permissions)
Section titled “2. Who is this for? (Roles & Permissions)”- Superadmin/Admin/Owner/Manager (or any role granted
manage_bips): Primary users of editable tabbed BIP flow; can write or refine individualized rationale content. - RBT/Analyst without
manage_bips: Usually redirected to full BIP read-only flow (/bip/show/patient/:id) instead of tabbed editing flow. - Users without BIP access permissions (
view_bips/manage_bips): Cannot access BIP actions from normal client workflows.
Required permissions used by this feature path:
manage_bips: Required to remain in editable tabbed BIP route.view_bips: Used in non-tabbed BIP viewing entry points.
3. Business Rules & Enforcements
Section titled “3. Business Rules & Enforcements”- Rule 1: This tab is defined as
individual_rationalewith titleIndividual Rationale. - Rule 2: The tab is feature-flagged and only appears when
insurance-statements-fieldsis enabled. - Rule 3: If no BIP exists yet, tab interaction is blocked globally and users must first create a BIP.
- Rule 4: Any text change emits
bipUpdated, which triggers parent debounced autosave. - Rule 5: Tab completion state is true when
individualized_rationalehas non-empty trimmed text. - Rule 6: The tab includes a
Regenerate with AIaction that requests backend field regeneration (regenerateFieldwith keyindividualized-rationale). - Rule 7: AI regeneration is blocked when BIP has no ID (unsaved/not ready) and user receives feedback message.
- Rule 8: While regeneration is running, the UI enters loading/disabled state to avoid conflicting edits.
4. UI Placement
Section titled “4. UI Placement”- Medical > clients list > client actions >
BIP View / Update. - Inside BIP tabbed view: tab
Individual Rationale(tab idindividual_rationale) when feature flag is enabled.
5. How-To Guide (Step-by-Step)
Section titled “5. How-To Guide (Step-by-Step)”Scenario A: Write individualized rationale manually
Section titled “Scenario A: Write individualized rationale manually”- Go to Medical and open the clients list.
- Open client actions and click
BIP View / Update. - Open tab
Individual Rationale. - Enter or refine the client-specific rationale text in the editor.
- Wait for autosave confirmation/toast after edits.
Scenario B: Regenerate rationale with AI
Section titled “Scenario B: Regenerate rationale with AI”- Open
Individual Rationaletab. - Click
Regenerate with AI. - Wait for regeneration to complete (loading spinner shown).
- Review generated text and make manual clinical edits if needed.
- Save is triggered through standard tab update flow.
Scenario C: Regeneration when BIP is not ready
Section titled “Scenario C: Regeneration when BIP is not ready”- Open tab before BIP has persisted ID.
- Click
Regenerate with AI. - System blocks operation and displays guidance to create/load BIP first.
6. What happens if…? (Edge Cases / FAQ)
Section titled “6. What happens if…? (Edge Cases / FAQ)”-
Q: What if AI regeneration returns no content?
-
A: The system shows a feedback message (
No content returned by AI regeneration) and keeps existing content unchanged. -
Q: What if AI regeneration fails?
-
A: The system displays backend error message (or fallback failure text) and exits loading state.
-
Q: Why don’t I see this tab in some environments?
-
A: The tab depends on
insurance-statements-fieldsfeature flag; if disabled, it is intentionally hidden.