Field Usage in Provider-Match

provider-match-opensearch-field-usage-audit.md

Field	In OpenSearch Index	Used in App Code?	Where Used
has_ein	✅	✅ Yes	ranker.service.ts — pushed as a tag for SC_EIN ranking criterion
has_low_voltage_license	✅	✅ Yes	f_lvc.ts — explicit filter
last_top5_at	✅	❌ No	Type definition only (data-attributes.ts:633)
field_experience	✅	❌ No	Type definition only (data-attributes.ts:634)
block_ratio	✅	✅ Yes	Ranker via SC_BLOCK_RATIO → block_pct formula in convert-custom-selection-rule.service.ts
is_tier1	✅	✅ Yes	f_service_company.ts — filter
is_tier2	✅	❌ No	Type definition only (data-attributes.ts:637)
num_service_company_providers	❌ (not in index)	❌ No	Not found anywhere in src
is_active	✅	✅ Yes	filters.ts — exclusion filter (is_active: false)
skills	✅	✅ Yes	provider-search.service.ts — segment filter
project_types	✅	✅ Yes	ranker.controller.ts — passed to ranking engine
skillsets	✅	✅ Yes	provider-search.service.ts:291 — segment filter + ranker
talent_pools	✅	❌ No	Type def only — talent_pools_v2 (nested) is used instead
talent_pools_v2	✅	✅ Yes	filters.ts — nested query; f_talent_pools.ts
project_ids	✅	✅ Yes	f_worked_with_on_this_project.ts
company_ids	✅	✅ Yes	f_worked_with.ts
blocked_by	✅	✅ Yes	filters.ts — exclusion filter
blocked	✅	✅ Yes	filters.ts — exclusion filter
blocked_service_companies	❌ (not in index)	❌ No	Not found in src
blocked_locations	✅	✅ Yes	filters.ts — exclusion filter
blocked_clients	✅	✅ Yes	filters.ts — exclusion filter
blocked_projects	✅	✅ Yes	filters.ts — exclusion filter
network_ids	✅	✅ Yes	filters.ts — must match work order networks
select_network_ids	✅	✅ Yes	f_select_networks.ts
license_ids	✅	✅ Yes	f_licenses_certs.ts
certification_ids	✅	✅ Yes	f_licenses_certs.ts
active_with	✅	✅ Yes	f_active_job_at_my_company.ts
service_company_id	✅	✅ Yes	f_service_company.ts + filters.ts
service_company name/phone/thumbnail/is_ghost	✅	❌ No	Not used in queries — only service_company_id is
cbsa_code / cbsa_name	✅	❌ No	Type defs and mocks only — not used in filter or ranking logic
latitude / longitude	✅ (as separate fields)	❌ No	The coordinates geo_point field is used instead via l_geo.ts

---

Summary: Truly Unused Fields (only in OpenSearch, not queried)

These are in the OpenSearch index but never referenced in any filter, ranker, or query logic:

• last_top5_at
• field_experience
• is_tier2
• num_service_company_providers (not even in the index)
• blocked_service_companies (not even in the index)
• talent_pools (superseded by talent_pools_v2)
• cbsa_code / cbsa_name
• latitude / longitude (stored as separate fields but geo queries use the coordinates geo_point)
• service_company name, phone, thumbnail, is_ghost