Ignore Time Limits for RBT Notes

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

This feature allows authorized users to create or update RBT notes even when standard time-based restrictions would normally block the save. It supports operational exceptions while keeping core scheduling and data-quality validations in place.

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

• Users with ignore_time_limits in the current location: Can save RBT notes without daily/weekly hour limits, backdating limits, and CPT-per-day limits.
• Superadmin: Has the same bypass behavior through global role logic.
• RBT/Analyst and other users without ignore_time_limits: Must follow standard time, backdating, and CPT constraints.

Required permission:

• ignore_time_limits (location-scoped permission).

Related permission context:

• manage_notes does not replace ignore_time_limits for all validations, but it can bypass backdating validation in edit/create workflows.

3. Business Rules & Enforcements

• Rule 1: With ignore_time_limits, RBT note requests skip daily and weekly time-limit validation.
• Rule 2: With ignore_time_limits, RBT note requests skip backdating-limit validation.
• Rule 3: With ignore_time_limits, RBT note requests skip CPT daily unit-limit validation.
• Rule 4: Time-overlap validation for patient/provider sessions is still enforced (including same-CPT overlap and provider overlap).
• Rule 5: Buffer-time validation between sessions is skipped when ignore_time_limits is granted.
• Rule 6: Standard field-level and chronology validations remain enforced (required fields, date/time formats, future date/time restrictions, and time order checks).

4. UI Placement

1. Medical > Patients > Patient actions > Create RBT Note.
2. Create route: /note-rbt/:patient_id (or appointment flow /note-rbt/:patient_id/:appointment_id).
3. Edit route: /note-rbt/edit/:patient_id/:id.
4. Role/permission assignment area: Admin role-permission screens where ignore_time_limits is assigned for the active location.

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

Scenario A: Authorized user creates an RBT note outside configured limits

1. Confirm the user has ignore_time_limits in the active location.
2. Open Create RBT Note for the patient.
3. Complete required session and clinical fields.
4. Save the note, even if normal daily/weekly/backdating/CPT limits would otherwise reject the request.
5. Verify the note appears in the patient RBT notes list.

Scenario B: Authorized user updates an older RBT note that would normally fail time/backdating/CPT checks

1. Open the existing RBT note in edit mode.
2. Confirm the user has ignore_time_limits in the active location.
3. Apply required changes (date, time blocks, CPT, and clinical content).
4. Save the note.
5. Confirm the update succeeds as long as overlap and base validation rules are satisfied.

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

• Q: What happens if a user has ignore_time_limits but creates an overlapping RBT session? A: The save is still rejected by overlap validation.

• Q: What happens if a user has ignore_time_limits but enters invalid chronology (for example time_out before time_in)? A: The request is rejected. Core date/time and field validations are still enforced.

• Q: What happens if a user does not have ignore_time_limits and exceeds configured limits? A: The request is rejected with validation errors for time limits, backdating limits, or CPT limits, depending on what was exceeded.