Update BCBA Note

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

This feature allows authorized users to update an existing BCBA note when corrections or clinical adjustments are needed after creation. It keeps clinical documentation accurate while enforcing location, ownership, billing, and validation controls.

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

• Original note provider (BCBA/Analyst): Can update their own BCBA note when they have the create_note_bcba permission and access to the note’s location.
• Admin / Owner / Manager / Superadmin with manage_notes: Can update BCBA notes in the authorized location, including notes created by other providers.
• Users without ownership or manage_notes: Cannot update another provider’s BCBA note.

Required permission logic:

• create_note_bcba: Required by the V2 update route.
• manage_notes: Allows editing notes not owned by the current user and allows protected clinical field editing when a note is billed.
• Location access is always required for the existing note and for any changed location.

3. Business Rules & Enforcements

• Rule 1: The update is blocked if the user is not authorized for the note’s current location.
• Rule 2: The update is rejected when the user is neither the assigned provider nor a user with manage_notes.
• Rule 3: If the note location changes, the backend also verifies access to the new location.
• Rule 4: Required note fields still apply on full update, including patient, date of service, supervisor, provider, CPT/service, POS, and summary note.
• Rule 5: Date and time validations still apply. The session date cannot be in the future, and time fields must remain chronological.
• Rule 6: Time overlap, time limits, backdated constraints, CPT limits, and weekly PA service units are re-validated unless the user has the applicable override permission.
• Rule 7: The same CPT-specific requirements used during creation still apply when updating the note.
• Rule 8: If a note is already billed, protected clinical inputs are restricted in the UI for users without manage_notes.
• Rule 9: If billed_blocked is already active, billing status cannot be changed in later updates.
• Rule 10: If a note is marked billed during update, the backend sets it as blocked for future billing-state edits.
• Rule 11: The partial update endpoint can modify only provided fields, but voided notes can only be restored by a user with both manage_notes and manage_claims.

4. UI Placement

1. Notes > BCBA Notes > Client list: Open a patient’s BCBA note list and select an existing note to edit.
2. Edit route: The edit screen is loaded in the BCBA notes module at /note-bcba/edit/:patient_id/:id.
3. Shared BCBA note form: The same form is reused for create and edit mode, with edit-specific messaging, preloaded note data, and an Update action.

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

Scenario A: Provider updates their own BCBA note

1. Go to the patient BCBA notes list.
2. Open the target note in edit mode.
3. Review the preloaded session details, CPT-specific fields, participants, signatures, and summary.
4. Update required fields while keeping valid time order and required clinical inputs.
5. Click Update.
6. Confirm the success message and return to the notes list.

Scenario B: Manager or admin updates another provider’s BCBA note

1. Open the note through the BCBA notes list.
2. Confirm the current location context matches the note and that you have manage_notes.
3. Apply the needed corrections, such as provider/supervisor context, session details, or clinical content.
4. If the note is billed, confirm that your permissions allow the protected clinical fields to be changed.
5. Click Update and verify the note saves successfully.

Scenario C: Update a billed note

1. Open the billed BCBA note in edit mode.
2. Review which clinical fields are editable for your permission level.
3. Make only the allowed corrections.
4. Click Update.
5. If billing status is already blocked, leave billing state unchanged and update only the permitted fields.

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

• Q: What happens if a user tries to edit a BCBA note they do not own and they do not have manage_notes?
  A: The backend returns a forbidden response and the update is blocked.

• Q: What happens if a note is billed and a user without manage_notes tries to change clinical fields?
  A: The form disables protected clinical fields in the UI and the user cannot apply those changes.

• Q: What happens if the edited session date or time is invalid?
  A: Validation fails and the note is not updated until the date/time values comply with the rules.