Claims Generation from Logs Report

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

This feature lets billing users create a claim batch directly from selected rows in the Logs Report. It reduces manual handoff work by turning selected service notes into a ready-to-review claim batch in one action.

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

• Users with access to Logs Report (typically roles with manage_notes): Can open the report, select rows, and trigger Generate Claim.
• Users with manage_claims (for example, Manager/Owner): Can manage the generated batch in the Batches list (send, review, download, delete, and re-create rejected batches).

3. Business Rules & Enforcements

• Rule 1: At least one RBT or BCBA note must be included; generation is rejected when no notes are provided.
• Rule 2: Every patient in the selected notes must have required demographic fields and a parent/guardian assigned; otherwise generation is blocked with patient-level details.
• Rule 3: Providers linked to selected notes must have taxonomy configured; otherwise generation is blocked with provider-level details.
• Rule 4: If one or more selected notes have missing stored charges, generation is blocked until those notes are recalculated.
• Rule 5: If the selected notes cannot produce valid EDI content or normalized claim rows, the batch is not created.
• Rule 6: A successful generation creates a new claim batch with pending status, stores batch totals, and links normalized claims, services, and note references.

4. UI Placement

1. Reports > Billing Collections > Logs Report: User selects note rows for claim creation.
2. Logs Report toolbar: User clicks Generate Claim.
3. Claims > Batches (/claims): User is redirected here after success to review the new pending batch.

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

Scenario A: Generate a new claim batch from Logs Report

1. Open Reports > Billing Collections > Logs Report.
2. Filter the list as needed (date range, client, provider, insurance, status).
3. Select the rows to include in the batch.
4. Click Generate Claim.
5. If validations pass, confirm the success message and continue to the redirected Batches page.
6. In Batches, locate the new pending batch and continue with sending/review workflow as needed.

Scenario B: Handle generation errors before retrying

1. In Logs Report, select rows and click Generate Claim.
2. If an error modal appears, review the grouped issues (patient data, parent assignment, provider taxonomy, or note recalculation requirement).
3. Correct the missing data in the corresponding records.
4. If instructed to recalculate note charges, run recalculation for affected notes.
5. Return to Logs Report, reselect rows, and click Generate Claim again.

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

• Q: What happens if the user clicks Generate Claim without selecting valid notes?
  A: The API rejects the request and no batch is created.
• Q: What happens if some selected patients or providers are missing required claim data?
  A: Generation is blocked and the modal shows detailed patient/provider issues to fix before retrying.
• Q: What happens after a successful generation?
  A: A new batch is created with pending status, and the user is redirected to the Claims Batches list.