Use process builder to create care observation triggers when a patient’s care
observations don’t meet the care metric target conditions. You can create a trigger to post on
Chatter or send an email to notify the user about care observations that fall out of
range.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health
Cloud
Define a process for the care observation trigger and give it a name and
description.
From Setup, in the Quick Find box, enter Process Builder, and then
select Process Builder.
Click New.
Enter a name for the process. For example, Care Observation Trigger. The API Name field is
autopopulated. Keep it as is.
Enter a description for your process.
For The process starts when, select A record changes from the
picklist.
In the Object field, select Care Observation from the
picklist.
For Start the process, select only when a record is created.
Save your changes.
Add a Criteria for the Action
Click +Add Criteria and enter a Criteria Name. For example, Value
Outside Range.
For Criteria for Executing Actions, select Conditions are
met.
Set the conditions for the criteria. For Field, select Processing Result
from the picklist.
For Operator, select Equal.
For Type, select Picklist.
For Value, select Record processed. Expected value updated. Observation Numeric
Value or Outcome Positive does not meet Care Metric Target conditions.
For Conditions, select All of the conditions are met (AND).
Save your changes.
Set Up an Immediate Action
To define an immediate action, click +Add Action.
Select an action type to send a notification. For example, Post to Chatter.
Enter an action name.
For Post to, select User.
For User, select Search for a user.
Enter the name of the user and the message you want to send.
To tailor the message for your patient, select a Merge Field.
Save your changes.
Click Activate.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
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.