To create a platform event when the case sub status of a care request extension record
is updated, clone the FHIR Subscription: Publish Platform Event flow. Update the InteropTopicId
and RecordTypeName constants in the flow to match your use case. Then, reference the flow in the
Interoperbility Topic Trigger Criteria object.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions
User Permissions Needed
To use Utilization Management:
Health Cloud Utilization permission set
To use FHIR Subscription:
FHIR Subscription permission set
To clone and configure flows:
Health Cloud Admin permission set
Before you clone and configure the flow, create a PreAuthorization record type in the
Case, Care Request, Care Request Extension, Care Request Item, and Care Request Drug
objects.
From Setup, in the Quick Find box, enter Flows and select
Flows.
Find and select the FHIR Subscription: Publish Platform Event flow.
To clone the flow, click Save As New Flow.
Enter the label and API name of the flow.
Save your work.
The newly cloned flow opens in Flow Builder.
To open the toolbox manager, click .
Open InteropTopicId and update the valule to the ID of the
subscribed interoperabilty topic as per your case.
Click Done.
In the toolbox manager, open RecordTypeName and update the value to
the record type name of your triggering record.
Click Done.
Save and activate your flow.
From the App Launcher, find and select Interoperability Topic Trigger
Criterias.
Open the interoperability topic trigger criteria associated with the subscribed
interoperability topic.
In the Interaction Definition Version field, search and select the cloned flow.
Save your changes.
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.