The standard Data Processing Engine (DPE) definition automatically updates the Care
Provider Searchable Field records used for Provider Search one time per day. If you’re testing
your setup and don’t want to wait for the automatic data sync, use the on-demand manual data
sync.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health Cloud
or Life Sciences Cloud
User Permissions
Needed
To use Provider Search:
Health Cloud Provider Search permission set
OR
Health Cloud Provider Relationship Management permission set
To sync data:
Data Pipelines Base User permission set
For Provider Search and Provider Search with Criteria-Based Search and Filter, on-demand
data synchronization and daily sync jobs use the data pipelines recipe run time limit of 30
hours per month.
For Legacy Provider Search, on-demand data synchronization is available only in sandbox
orgs.
From Setup, in the Quick Find box, enter Provider Search
Settings, and then select Provider Search
Settings.
Click Manual Sync Data.
It takes time to sync the data. For Provider Search, only one data pipeline recipe can
run at a time. Use the Jobs Monitor tab of Data Manager to see the status of your sync.
Use the Usage tab to see the current hours of recipe job run time for the month.
After the data is synchronized, run a provider search and check that everything is
working as expected.
For each facility and each practitioner you've created, confirm there’s an equivalent
Care Provider Searchable Field record.
If you don't find the expected Care Provider Searchable Field records, use the error
messages in the Provider Search Sync Logs to troubleshoot. From the App Launcher, find and
select Provider Search Sync Logs. In each log, the Sync Status
field shows whether a provider’s data sync succeeded. If a provider's data didn't sync to
a corresponding Care Provider Searchable Field record, the Message field shows errors.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.