Use the FHIR subscription framework to send subscribers timely notifications of event
changes. Publish the topics or events that are available for subscription so that clients can
subscribe by providing their endpoints.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions
Publishers can use the FHIR Subscription data model to store subscription topics, subscriber
details, the filters and parameters applied to a subscription, and other subscription details.
When the event change occurs, it triggers a notification and a platform event is created as an
Interoperability Topic Subscription Event record. Then, Mulesoft sends the notification to the
subscriber’s endpoint. To learn more about the Mulesoft integration, see FHIR Subscription for Utilization Management.
Utilization Management has the prebuilt FHIR Subscription: Publish Platform Event flow which
can be cloned and configured for your use case. With this flow, payer organizations can notify
providers when the status of their submitted care request is updated from Pending Review to
More Information Required. The provider receives notifications of the update in real time,
enabling them to take timely actions to deliver patient care.
You can configure your own implementation to trigger the platform event and send
notifications to subscribers as per your business needs.
Clone and Configure the FHIR Subscription Flow 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.
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.