You are here:
Considerations for Provider Search
Understand how to effectively set up provider search.
Required Editions
| View supported product editions. |
- If you clone the Criteria-Based Search and Filter permission set, make sure to enable the Use Criteria-Based Search and Filter system permission in the copy.
- To enable the Data Processing Engine definition to run successfully, make sure that your
source objects don’t have duplicate conditions. The Data Processing Engine definition for
provider search returns failed writeback records when:
- Two or more benefit specialty records are associated with the same pair of benefit and care specialty records
- Two or more healthcare practitioner facility records are associated with the same pair of healthcare provider and healthcare facility records
- Two or more healthcare provider specialty records are associated with the same pair of healthcare provider and care specialty records
- Two or more healthcare provider NPI records are associated with the same healthcare provider record
- If you delete records from the Benefit, Benefit Specialty, Healthcare Facility, Healthcare Practitioner Facility, Healthcare Provider, Care Provider Facility Specialty, or Care Specialty source object, then the Data Processing Engine definition deletes the corresponding Benefit Provider Searchable Field record the next time it runs. If you delete records from other source objects, then the Data Processing Engine definition updates the corresponding Benefit Provider Searchable Field record the next time it runs. In the updated record, the field from the deleted source record is set to empty.
- Provider search supports these field data types.
Configuration Supported Data Types Search Criteria - Boolean
- Lookup Relationship
- Numeric
- Picklist
- Text
Search Results - Boolean
- Date/Time
- Picklist
- Text
Search Results Grouping and Aggregation Text type fields Provider search doesn’t support composite, formula, or encrypted fields.
- Criteria field mappings and result Field mappings are applied to all configurations that use the same searchable object configuration. So if you create field mappings for the Benefit Provider Searchable Field searchable object configuration, the mappings are applied to all configurations created for Benefit Provider Searchable Field. If you delete the mappings for one configuration record, the mappings are deleted for all other searchable object configurations that use the same object.
- Provider search uses the SOSL
FINDclause. When you select search criteria fields, make sure you select text-indexed fields that yield only up to 4,000 records when used in a combination.
Did this article solve your issue?
Let us know so we can improve!

