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 end-to-end authorization process.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health
Cloud
Set up and use Integrations to implement digital workflows and create seamless user
experiences. Health Cloud’s comprehensive solution gives you:
Predefined integration procedures, Omnistudio Data Mappers, and Apex classes that help you retrieve
member information from EHR and submit authorization requests to payers.
Pre-built integration applications, built using the FHIR standards, that enable Health
Cloud to interact with external EHR and payer systems. These out-of-the-box integration
applications help providers by reducing the time and cost to go live. These apps are
available to users who have the MulesSoft add-on product called MuleSoft Direct for
Health cloud.
Prior Authorization EMR Retrieval API helps provider systems to automatically
retrieve all the relevant datasets from the EMR to prepare a Da Vinci (an HL7 FHIR
accelerator) aligned prior authorization request.
Prior Authorization Claim Submission API helps provider systems to send a Da
Vinci (an HL7 FHIR accelerator) aligned prior authorization request to a clearing
house or a payer endpoint. It handles the submission of the request and inquiry
about the request status.
Use the EHR connector MuleSoft Direct for Health Cloud to directly pull patient and
clinical information, greatly simplifying the information gathering process. MuleSoft
Direct for Health Cloud allows providers to easily pull patient and clinical information
to quickly create authorization requests. Then, providers can submit the request
electronically in a Da Vinci FHIR API format where it can be sent to the payer’s FHIR
endpoint via Mule Connector.
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.