Reduce the time it takes your representatives to connect with payors by using an
electronic benefits verification request. This request automates the verification process
through electronic exchange of coverage information with payors through clearing
houses.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Life
Sciences Cloud or Health Cloud
Use pharmacy benefits verification to integrate your Salesforce org with clearing houses or
payors by using integration with MuleSoft. The integration happens through Patient Services
Benefits Application, a MuleSoft outbound application. When your representative initiates an
electronic verification request, an FHIR (Fast Healthcare Interoperability Resources)
compliant RTPBC (Real-Time Pharmacy Benefit Check) Request is sent to a third-party clearing
house through MuleSoft. Similarly, the clearing house sends the FHIR compliant RTPBC Claim
Response to Salesforce org through MuleSoft.
Built-In MuleSoft Integration for Electronic Verification Integrate Health and Life Sciences Cloud with third-party clearing houses by using FHIR-CARIN and NCPDP aligned verification requests, industry-specific APIs, and integration application deployed on MuleSoft. Use this integration to accelerate the end-to-end benefits verification process.
Set Up Electronic Verification Request Set up electronic verification request for your reps to verify patient's benefits electronically by using External Client app, MuleSoft integration, and Integration Defintions.
Electronic Verification Scenarios Explore the different scenarios that occur when your representative raises an electronic verification request. Also, understand the different scenarios of failure and their resolution.
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.