Availables Cases

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

This feature provides a public page where prospective or current providers can review available client cases by agency location. It helps recruiting and operations teams share current openings with enough detail for providers to identify a possible match and contact the office.

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

• Public users with the page link: Can view available case information for the location included in the URL.
• Current or prospective providers: Can review case location, schedule, and status before contacting the team.
• Recruiting and operations teams: Can share a location-specific link and use the page as a public reference for current case availability.
• Permission model: This page is in the public module and the API route is public. No authenticated app role is required, but the page needs a valid location_id query parameter to load case data.

3. Business Rules & Enforcements

• Location is required: The available cases API returns an error when location_id is missing. The frontend also waits for location_id before requesting cases or the agency logo.
• Only approved public locations are exposed: The backend returns cases only for allowed location IDs 1, 5, 6, 7, 8, and 9. Other location IDs return an empty successful response.
• Available-case definition: A case is shown when it belongs to the requested location and either:
  • it has no assigned home RBT and its status is not active, inactive, void, onHold, or onDischarge; or
  • its status is activeRbtReplacement.
• Read-only public view: Users can review case information and contact instructions, but this page does not provide create, edit, assign, or reserve actions.
• Paged results: The frontend requests up to 100 cases per page and keeps the active page in the URL query parameters.
• Status display: Status codes are converted into user-friendly labels before they are shown in the table.
• Empty-state handling: When no records are returned, the table displays No data available.

4. UI Placement

1. Public route: /availables-cases.
2. Required query parameter: location_id.
3. Optional query parameter: page.

Inside the page:

1. Cases tab: Shows the agency logo/name when available, the available cases table, and pagination.
2. Contact us tab: Shows application links, contact information, and bilingual guidance about how available cases are offered and communicated.

The cases table displays:

1. Patient identifier.
2. Status.
3. City.
4. Schedule.
5. Summer Schedule, with N/A when no summer schedule is available.

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

Scenario A: Review available cases for one location

1. Open /availables-cases?location_id=<location-id>.
2. Wait for the loading skeleton to finish.
3. Confirm the agency name/logo shown above the table.
4. Review the available cases by patient identifier, status, city, schedule, and summer schedule.
5. Use Previous, page numbers, or Next to move through additional pages when available.

Scenario B: Share a location-specific available cases page

1. Open the available cases page with the correct location_id.
2. Navigate to the page number that should be shared, if needed.
3. Copy the current URL, including query parameters.
4. Send the link to the provider so they land on the same location and page context.

Scenario C: Find contact and application instructions

1. Open the available cases page for the relevant location.
2. Select the Contact us tab.
3. Review the application link and office contact details.
4. Return to the Cases tab to continue checking open availability.

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

• Q: What happens if location_id is missing from the URL?
  • A: The frontend does not request cases or the agency logo. If the API is called directly without location_id, it returns an error that the parameter is required.
• Q: What happens if the location is not approved for the public list?
  • A: The backend returns a successful response with no cases, so the table displays No data available.
• Q: What happens if a case has an assigned RBT?
  • A: It is normally excluded from this public list unless the case status is activeRbtReplacement.