To run the Score Synchronization API, you have to map score categories to their
corresponding calculated insights in Data 360. This step isn’t required if you don’t use Data
360 or the Score Synchronization API.
Required Editions
Available in: Enterprise and Unlimited Editions with Health
Cloud
User Permissions
Needed
To define a unified health profile
Health Cloud Admin Permission Set
From Setup, enter Unified Health Scoring Settings in the Quick Find
box, and then select Unified Health Scoring Settings.
Select the score category you have to map a calculated insight for.
You can only see top-level score categories on this screen. To map a subcategory, open its
parent category and navigate to the subcategory.
Click Map Calculated Insights.
Tip Now’s a good time to pull up the API names you noted down as part of the Set Up Calculated Insights instructions.
In the Insight Name field, enter the API name of the corresponding
calculated insight.
In the Insight Score Field Name field, enter the API name of the
score field you created as the measure of the calculated insight.
In the Insight Subject Field Name field, enter the API name of the
patient lookup you created as the dimension of the calculated insight.
If you created a field in your calculated insight to capture score dates, enter that
field’s API name in the Insight Date Field Name field.
Click Done.
Repeat these steps for each score category you’ve defined.
And that’s it! Your score categories are now compatible with Data 360 and the Score
Synchronization API.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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.