As a CHO, I want to search for beneficiaries based on my mapped work location so that I can easily find beneficiaries within my assigned area without needing to enter mandatory location details every time.

Description

The system should automatically filter search results based on the CHO’s mapped work location (facility/village/sub-center/PHC, etc.).
The CHO should not be required to manually select or enter location details.
All search results should only include beneficiaries under the CHO’s assigned catchment area.

This location-based filtering must apply to all supported search parameters and integrate with Elasticsearch.

Acceptance Criteria:

Automatic Location Filtering

• The system must automatically filter beneficiary search results based on the CHO’s mapped work location.
• The CHO should only see beneficiaries within their assigned area.

No Manual Location Input Required

• The CHO should not be required to enter any location details (facility, village, sub-center, etc.) while performing the search.
• Location filtering should be applied internally by the system.

Support for All Search Parameters

• Search must work using:
  • Beneficiary name
  • Phone number
  • ABHA number
  • ABHA address
  • Single-word or partial text
• Only beneficiaries within the CHO’s mapped location should be included in the results.

Facility-Level Search Restrictions

• Search results should include only:
  • Beneficiaries registered under the CHO’s mapped work facility/location.
  • Beneficiaries who have visited the mapped facility.

Availability Across Modules

• The search option must be available in both the Nurse section and Registration section.
• Search behavior must be consistent across both modules.
• Advanced search will be there for global search

Mobile App Support

• The same search logic and location filtering must be applied when the mobile app uses the search API.
• Mobile and web must return identical filtered results.

Performance Requirement

Search results, even with auto-filters, must be returned within 1second  for typical search loads.

Technical Notes

• The CHO’s mapped location must be fetched from the user-role mapping table.
• The backend should apply a mandatory filter (facilityId / locationCode / areaCode) internally, not configurable by user.
• Elasticsearch query must include a must-filter clause for location mapping.
• API must support web and mobile with the same behavior.