View and Export BCBA Note

1. What does this feature do? (High-Level Overview)

This feature lets authorized staff open a BCBA note from the patient notes flow and review its full clinical and session details in read mode. It also allows eligible users to export that same note as a PDF for audit, billing, or sharing workflows.

2. Who is this for? (Roles & Permissions)

• BCBA/Analyst and clinical staff with notes access: Can open BCBA notes from the patient note list when they have view_notes access in the location context.
• Admin / Owner / Manager / Superadmin (or any role) with manage_notes: Can see the Export PDF button in the BCBA note view screen.
• Users with export_notes: Can successfully call the BCBA PDF export endpoint.
• Users with access_all_locations: Can export notes across locations when the selected note does not match the current X-Location-Id context.

Required permissions and access checks:

• view_notes: Needed to expose the View action in the BCBA notes list workflow.
• manage_notes: Used by the UI to show the BCBA note Export PDF action in the note view screen.
• export_notes: Enforced by backend middleware for /v2/note_bcba/pdf/{id}.
• Location scoping: The backend validates the note location against X-Location-Id, with access_all_locations as override.

3. Business Rules & Enforcements

• Rule 1: Users open a BCBA note view from the BCBA notes list route (/note-bcba/listbyclient/:id) into /note-bcba/view/:id.
• Rule 2: The view page loads note, patient, specialists, and insurance context before rendering full details.
• Rule 3: The screen renders CPT-specific blocks conditionally (97155, 97156, and 97151 subtype views) plus common summary/signature sections.
• Rule 4: Export PDF is shown in the UI only when the current user has manage_notes.
• Rule 5: PDF generation uses the BCBA endpoint /v2/note_bcba/pdf/{id} and opens the resulting file in a new browser tab.
• Rule 6: Backend export is protected by check.permissions:export_notes; requests without that permission are rejected.
• Rule 7: Backend export bypasses tenant scope to find the note, then enforces location access using X-Location-Id; cross-location export is denied unless the user can perform access_all_locations.

4. UI Placement

1. Medical > Notes > BCBA notes by client: /note-bcba/listbyclient/:id shows the patient BCBA notes table.
2. View action and DOS link: Both navigate to /note-bcba/view/:id.
3. BCBA note view page: Displays note details and, when eligible, the Export PDF button.

5. How-To Guide (Step-by-Step)

Scenario A: View a BCBA note from a patient profile note flow

1. Open the patient BCBA notes list.
2. Locate the target note by DOS.
3. Click the DOS link or the View action.
4. Review session metadata, CPT-specific content, summary note, signatures, and timestamps.

Scenario B: Export a BCBA note as PDF

1. Open the BCBA note in view mode.
2. Confirm the Export PDF button is visible.
3. Click Export PDF.
4. Wait for the system to request /v2/note_bcba/pdf/{noteId}.
5. The PDF opens in a new browser tab.

6. What happens if…? (Edge Cases / FAQ)

• Q: What happens if I can view the note but cannot export it? A: The UI may still show export only under manage_notes, but backend export also requires export_notes; without it, the request is rejected.

• Q: What happens if the note belongs to another location? A: The backend blocks export when the note location does not match X-Location-Id, unless the user has access_all_locations.

• Q: What happens if provider or supervisor is no longer in the patient specialist list? A: The view screen fetches the missing user directly and still renders the provider/supervisor name and signature data when available.