Before you use Pharmacy Benefits Verification, you must prepare your org by completing
tasks such as assigning permission sets to your users, configuring setup entities, enabling
history tracking, and adding picklist values to certain objects.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health Cloud
or Life Sciences Cloud, and Einstein GPT Platform and Einstein GPT Prompt Builder
Add-On licenses
Configure Care Limit Type To use Pharmacy Benefits Verification, you must define care limit types such as co-pay, co-insurance, and many more to determine the pharmacy benefits that are available to a patient.
Configure Units of Measure Configure the units of measure for the medications that a healthcare practitioner prescribes to a patient.
Configure a Code Set In pharmacy benefits verification, code sets define the metrics that explain the patients’ pharmacy benefits coverage status code. For example, covered, not covered, or covered with restrictions.
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.
