Health Cloud Administration
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Health Cloud Data Models
Health Cloud Provider Network and Relationship Management
Health Cloud Sales and Commercial Excellence
Health Cloud Utilization Management
Health Cloud for Insurance
Types of People in Health Cloud
Quick Start List for a Successful Health Cloud Implementation
Use the Health Cloud - Admin App
Flow for Health Cloud
Intelligent Document Reader
Intelligent Form Reader
Document Generation in Health Cloud
OmniStudio Components for the Provider Authorization Request Process
Built-In MuleSoft Integration to Manage Authorization Requests
Set up Integration Definitions for Apex Classes
Configure Statuses for Authorization Requests from Provider Offices
Configure Priorities for Authorization Requests
Configure the Partial Request Outcome for Authorization Requests
Configure Action Buttons for Submitting and Inquiring about Authorization Requests
CRM Analytics for Utilization Management
Artificial Intelligence for Utilization Management
Set up Action Plans
Authorization Request Process Setup for Providers
Help your provider users to easily create and submit authorization requests using
FHIR-aligned, industry-specific APIs, along with a predefined suite of Integration procedures
and DataRaptors. These components retrieve member information, service requests, and other
details required to create an authorization request record and submit the request to the
payer.
|
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions with Health Cloud |
Before you proceed with this process: Set Up Permissions and Data for Utilization Management
-
OmniStudio Components for the Provider Authorization Request Process
Utilization Management provides a set of predefined OmniStudio Integration Procedures and DataRaptors to retrieve member information from the provider’s Electronic Health Record (EHR) system and to submit the authorization request to the payer’s system. -
Built-In MuleSoft Integration to Manage Authorization Requests
Integrate Health Cloud with external Electronic Health Record (EHR) and payer systems by using FHIR Da Vinci Health Record Exchange aligned, industry-specific APIs, and integration applications deployed on MuleSoft. With this Industry Integration Solution, you experience an accelerated and hassle free, end-to-end authorization process. -
Set up Integration Definitions for Apex Classes
Use Integration Definitions to quickly set up integrations with different external endpoints using a low code interface. Create integration definitions for Apex classes used to integrate providers with EHR and payer systems. The integration procedures of the provider process call these integration definitions instead of directly pointing to the Apex classes. -
Configure Statuses for Authorization Requests from Provider Offices
It’s critical to track the real-time status of each authorization request from submission to approval to make quick, informed decisions on the patient's care. To help your users efficiently use Utilization Management’s highly refined technological workflows, define the required case statuses. -
Configure Priorities for Authorization Requests
Authorization requests can have multiple priorities depending on, for example, a patient’s health condition diagnosis or the services requested by the provider. For the end-to-end authorization request process to work effectively, set up the required priorities. -
Configure the Partial Request Outcome for Authorization Requests
The outcomes of authorization requests vary depending on factors such as the patient’s member plans or the payer’s clinical review guidelines. To help your authorization coordinators successfully manage the authorization request process, define a request outcome named Partial. The other required outcomes, Queued, Error, and Complete are available by default. -
Configure Action Buttons for Submitting and Inquiring about Authorization Requests
Help your provider users to launch OmniScripts and handle authorization request submissions and inquiries in an efficient manner by adding FlexCard-based action buttons to pages.