Prescriber Level Formulary

    iPad | Online

The Prescriber Level Formulary control displays as a pie chart icon in the Prescriber Level Formulary in the Online platform and allows end users to select the payer in the iPad platform. The controls display a pop-up window that contains a product breakdown for that payer-account combination. The percentage of the sales figures for each product displays.

Add the Prescriber Level Formulary control to any Account page by using the Formulary_For_Rep_vod S-Control on the page layout. This displays the following information for an account:

  • Top 10 Payers for the account (Online only)
  • Top 5 Products for each payer - displays only the company products with sales data (Online only)
  • Product-level Benefit Design information for each product and payer combination

Veeva CRM Lightning Ready does not support S-controls. Admins for Lightning Ready orgs should instead configure the FormularyForRepLgtnVod Visualforce page.

Selecting the pie chart icon in the Prescriber Level Formulary in the Online platform or selecting the payer in the iPad platform displays a pop-up window that contains a product breakdown for that payer-account combination. The percentage of the sales figures for each product displays.

Configuring the Prescriber Level Formulary

Prerequisites

Configuration

  1. Grant users the following permissions: 

    Object OLS Record Type Fields FLS

    Account_vod

    n/a

    n/a

    ID_vodID2_vod

    read

    Analytic_Markets_vod

    R

    n/a

    n/a

    n/a

    Analytics_File_Market_Map_vod

    R

    n/a

    n/a

    n/a

    Analytics_Files_vod

    R

    n/a

    n/a

    n/a

    Analytics_Layouts_vod

    R

    n/a

    n/a

    n/a

    Analytics_Product_Group_vod

    R

    n/a

    n/a

    n/a

    Benefit_Design_vod

    R

    n/a

    n/a

    n/a

    Benefit_Design_Line_vod

    R

    n/a

    n/a

    n/a

    Formulary_Products_vod

    R

    n/a

    n/a

    n/a

    Product_Group_Map_vod

    R

    n/a

    n/a

    n/a

    Sales_Transaction_vod

    R

    n/a

    n/a

    n/a

Data Requirements

The following setup and data requirements are necessary to populate Prescriber Level Formulary:

  • Creation of Payer Accounts
  • The Prescriber Level Formulary control requires all payers to be represented as account records in the Veeva CRM application. The account records can be of any record type, however, utilization of the Veeva CRM out-of-the-box record types MCO_vod or MCO_Plan_vod is strongly recommended.

    For each payer, a unique identifier must be stored within the Payer Id field. This value corresponds to the value of the Payer Id field in the Payer Level Sales Data file. This Payer Id provides the link between a sales data record and the corresponding payer.

The Formulary Products will then be leveraged by the Benefit Design Line Item records as noted below.

  • The Formulary Products object must be loaded with the various products contained in the Benefit Designs of the payers. The value of the Name field in the Formulary Product record must be an exact literal match to the Display Name of the Analytics Product Group record from the Sales Data file. To support products aligned to two or more products, the Market_vod field on Formulary Product must also match the Market_vod field on Analytics_Product_Group.
  • Formulary Products
  • Primary Benefit Design - The Benefit Design records correspond to the various formularies that a payer maintains. Each Benefit Design should have the Account field set to one of the payer accounts defined in Creation of Payer Accounts.
    The Prescriber Level Formulary control requires only one of the Benefit Designs for a payer is designated as the Benefit Design displayed for that payer. Select the Primary Benefit Design check box on the appropriate Benefit Design record. Only one Benefit Design should have the Primary Benefit Design check box selected per payer account.
  • Benefit Design Line Items - The Prescriber Level Formulary also supports the display of Benefit Design information based on the inheritance model defined by the Formulary Matrix. For a given Benefit Design, a customer can indicate that the Formulary is determined based upon a Parent Benefit Design, such as a national plan. The Prescriber Level Formulary supports this inheritance model and will display formulary information for a given product and payer based upon the defined Parent Benefit Design.
  • Restrictions
  • Status
  • Co-Pay

The name of the Formulary Product in a Benefit Design Line Item must be an exact textual match to the Display Name of the Analytics Product Group from the Sales Data file.

MyInsights Payer-Level Sales Data Load

You must have access to MyInsights to use the Prescriber Level Formulary control. MyInsights provides a mechanism to load sales data for HCPs and Business Accounts, for example, Group Practices. The Prescriber Level Formulary control utilizes the sales data broken down by the payer that has reimbursed the physician for the prescription. If a prescriber does not have the appropriate sales data, a message displays informing the user there is no sales data. The message is customized using the NO_FORMULARY_DATA Veeva Message.

Configure the following MyInsights components to utilize Prescriber Level Formulary:

  • Analytics Product Group Records
  • You must load the Analytics Product Group records to map the product values within the sales data file to a human readable format. As mentioned above, the Display Name of the Analytics Product Group record must be an exact literal match to the Name of the corresponding Formulary Product record.
  • You must load the Analytics Product Group records to map the product values within the sales data file to a human readable format. As mentioned above, the Display Name of the Analytics Product Group record must be an exact literal match to the Name of the corresponding Formulary Product record.
  • Display in Reports? - This check box drives whether the Analytics Product Group is displayed in both MyInsights and in the Prescriber Level Formulary control
  • Product Group Map Records
  • The Product Group Map records provide a relationship from Analytics Product Group records to Product Catalog records. You can view the relationship and the markets a user will have access to by navigating to Analytics Markets:
    1. Navigate to the user’s My Setup Products.
    2. Click Product Catalog.
    3. Click Product Group Map.
    4. Click Analytics Product Group.
    5. Click Analytics Markets.
  • The Prescriber Level Formulary control only displays the markets the user is aligned to in Analytic Markets. If the Product Group Map records do not exist, then no markets are available for selection from within the Prescriber Level Formulary control.
  • Payer Sales Data File
  • The Payer Sales Data file requires several key components in order to be used by the Prescriber Level Formulary. The following fields must exist in the Payer Sales Data file and mapped using the file’s corresponding Data Map Template:
  • Id_vod__c – Prescriber identifier that is mapped to ID_vod__c or ID2_vod__c on the prescriber account record
  • Product_Group_vod__c – Product code mapped to the Name field on Analytics Product Group
  • Payer_Plan_vod__c – Textual name of the payer. This is the name that displays in the Prescriber Level Formulary Control
  • Payer_Id_vod__c – Payer identifier that maps to the Payer Id field in the payer account record
  • Sales Data Buckets – Buckets of sales data B1_vod__c to BX_vod__c, where X is equal to the number of historical data points (either weekly or monthly)

Only one Payer Sales Data file should have a selected value for the Formulary_For_Rep_Label_vod__c field. In addition to the Formulary for Rep Label picklist, the Data Map Template must have the Payer/Plan Mapped? Check box checked.

  • Data Map Template
  • A customer can determine which Payer Sales Data file metric to use by selecting a value for the Formulary_For_Rep_Label_vod__c picklist field in the Data Map Template associated to a Payer Sales Data file. When selecting a value, the option First_Column_Label_vod will indicate that the metric stored in the Column Label field will be utilized when performing calculations. If the Second_Column_Label_vod value is selected in the picklist for the Data Map Template, then the Second Column Label field is used.
  • Data Map Templates provide the meta-data that loads the sales data. Since there can be multiple Payer Sales Data files, the Prescriber Level Formulary requires a customer to select one metric in a Payer Sales Data file to determine which data will drive the calculations performed in the Prescriber Level Formulary.

After processing, the Sales Data file with the associated Data Map Template, the Formulary_For_Rep_Label_vod__c value is copied to the Analytics File record for processing by the Prescriber Level Formulary control.

Prescriber Level Formulary in Veeva CRM for iPad

The Prescriber Level Formulary report is available offline on Veeva CRM for iPad.

iPad takes advantage of a local data cache for runtime performance. The cache loads the first time the Formulary page is accessed and results in a delay of several seconds when the page is loading. Once loaded, subsequent page displays takes advantage of the local cache.

Select the analytics market you want to view using the Market picklist. The payers who have reimbursed products prescribed by this account display.

The products section of the display is scrollable as indicated by the right arrow.

Tapping a status button highlights cells containing that status. Tapping a restriction on the right highlights those cells.

Tapping a payer roll displays the details for that payer. You can pull out a slice from the pie chart by tapping either the slice or a product row in the accompanying table.

The required configuration for enabling offline MyInsights is:

  • Visibility to the sales_transaction_vod object
  • Setting the Veeva setting ENABLE_OFFLINE_VINSIGHTS to true
  • Active VMOC records for iPad for:
  • Analytics_Files_vod__c
  • Analytics_File_Market_Map_vod__c
  • Analytics_Layouts_vod__c
  • Analytics_Markets_vod__c
  • Analytics_Product_Group_vod__c
  • Data_Map_Template_vod__c
  • Data_Map_Template_Field_vod__c
  • Product_Group_vod__c
  • Product_Group_Map_vod__c
  • Sales_Transaction_vod__c

In addition, to configure offline Prescriber Level Formulary:

  • Ensure there are active VMOC records for iPad for:
  • Benefit_Design_vod
  • Benefit_Design_Line_vod
  • Formulary_Products_vod
  • Ensure the Formulary_For_Rep_vod S-Control is on the Account page layout.

The value of the Payer_Id_vod field in the payer Account records must be identical to the value of the corresponding Payer_Id_vod field in the payer sales data file. These accounts must be downloaded to the mobile device.

For offline VInsights, payer sales data is limited to one year of data.

Alternative Prescriber Formulary Report Configuration

The iPad platform retrieves results that match the Online platform without the user assigning territories to payer accounts for the Prescriber Formulary Report. When Benefit Design data is available for a product, the following items display in the iPad environment for each cell in the report whether or not the payer account is assigned to the user’s territory:

  • Status_vod
  • Restrictions_vod
  • Copay_vod

To ensure consistency in the order in which the report information displays in the Online and iPad platforms, the Payer column information displays based on the total sales amount. If the total sales amount is identical for multiple payers, the payers display in alphabetical order.

The report is functional with the original configuration; however, you must follow the steps in this procedure if you want the iPad version of the report display the formulary information without assigning payer accounts to the user's territory.

To enable this alternative configuration:

  1. Deactivate the Benefit_Design_vod VMOC object by deselecting the Active check box associated with the object.
  2. Modify the Benefit_Design_Line_vod VMOC with the following settings:
  • Type - Child and Parent Row
  • Parent Object Name field - Benefit Design
  • Relationship Name - Benefit_Design_Line_vod__r
  • Where Clause - WHERE Product_vod__c in (select Id from Formulary_Products_vod__c)
  • Active check box - selected
  1. Grant the user FLS visibility to the Competitor_vod field on the Benefit_Design_Line_vod__c object. 
Data Date

The Data Date now displays on the main page of the report. This is the date the payer sales data was loaded. If multiple files are used for calculations, the most recent date displays.