Missing Notes

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

This feature shows providers a focused list of completed calendar sessions that still require a clinical note. It helps teams close documentation gaps faster by letting users jump directly from each missing-note item to the correct note form.

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

• Provider roles (for example RBT/BCBA/Analyst): Can view their own missing notes in the location dashboard home and open note creation directly from each row.
• Any authenticated user with access to the location dashboard home: Can view the widget when they can open the UniqueDashboardComponent route.

Permission-related behavior:

• The widget itself does not add an extra frontend permission gate in UniqueDashboardComponent; visibility is driven by access to the location dashboard route and backend response scope.
• The note destination is selected automatically by appointment CPT code (RBT note vs BCBA note flow).

3. Business Rules & Enforcements

• Rule 1: Data is loaded from GET /v2/appointments/note-reminder/:provider_id using the logged-in user id.
• Rule 2: While the request is in progress, the table shows a Loading... state.
• Rule 3: If no missing notes are returned, the table shows No missing notes.
• Rule 4: Clicking Create Note routes by CPT: 97153 opens the RBT note route (/note-rbt/:patientId/:appointmentId), and all other CPT values open the BCBA note route (/note-bcba/:patientId/:appointmentId).
• Rule 5: The Date of Service shown in the table is formatted as MM/DD/YYYY from the appointment session_date.
• Rule 6: Requests are location-scoped by the app interceptor (X-Location-Id), so results follow the currently selected location context.

4. UI Placement

1. Dashboard > Home (location dashboard view).
2. Component: UniqueDashboardComponent.
3. Section title: Missing Notes.
4. Table columns: Patient, CPT Code, DOS, Time In, Time Out, and action column.
5. Primary action per row: Create Note.

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

Scenario A: Create an RBT note from a missing-note reminder

1. Open Dashboard > Home.
2. In the Missing Notes table, find the target session row.
3. Confirm the row has CPT code 97153.
4. Click Create Note.
5. The app opens /note-rbt/:patientId/:appointmentId, where the user completes and submits the note.

Scenario B: Create a BCBA note from a missing-note reminder

1. Open Dashboard > Home.
2. In the Missing Notes table, find the target session row.
3. Confirm the row has a CPT code different from 97153.
4. Click Create Note.
5. The app opens /note-bcba/:patientId/:appointmentId, where the user completes and submits the note.

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

• Q: What happens if there are no missing notes for the current user and location?
  A: The table remains visible and shows No missing notes.

• Q: What happens if the reminder API call fails?
  A: The loading state stops, the error is logged in the browser console, and no rows are displayed.

• Q: What happens if I change location context before opening this page?
  A: The backend query uses the current location header, so the missing-note list reflects the selected location.