Loading
Intermittent Errors with Salesforce Trial Org Registration Read More
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Understand the Reverification Request Generation

          Understand the Reverification Request Generation

          Pharmacy Benefits Reverification uses two flows and one data processing engine to generate a new copy of Care Benefits Verify Request records.

          Required Editions

          Available in: Lightning Experience
          Available in: Enterprise and Unlimited Editions with the Health Cloud or Life Sciences Cloud license. It's also available with these add-on licenses: Agentforce for Life Sciences Cloud or Agentforce for Health Cloud, Flex Credits Metering, Agentforce Employee Agent, Einstein GPT Platform, Einstein GPT Copilot, Einstein GPT Trust, Genie Data Platform Starter, and Einstein GPT Prompt Builder.

          Before your program leads can use the Initiate Benefit Reverification flow in your org, you must clone the existing Data Processing Engine definition and activate it. The flow uses the cloned definition to copy Care Benefit Verify Request records for benefits reverification. To clone the existing flows, refer Clone and Activate the Care Benefit Verify Requests Data Processing Engine Definition and Clone, Activate, and Configure Benefit Reverification Flows.

          Here’s an overview of how your cloned Data Processing Engine definition and the flows work together.

          Step Outcome
          A program lead runs the Initiate Benefit Reverification flow. The flow initiates a benefit reverification request based on data provided by the flow user. The user enters the date range and status of the Care Benefit Verify Requests to reverify.
          The Initiate Benefit Reverification flow triggers the Care Benefit Verify Requests Data Processing Engine definition.

          The definition identifies existing care benefit verify request records within the date range and with the status specified by the Initiate Benefit Reverification flow user. The definition creates a copy of a care benefit verify request if the record isn’t referenced as a parent request in any other record.

          The definition assigns a Copy status to the new record. The Copy status triggers the Copy Care Benefit Verify Request Fields flow.

          Records copied by the Data Processing Engine definition trigger the Copy Care Benefit Verify Request Fields flow.

          The flow verifies that the care benefit verify requests to copy have a status of Copy, have a Related Care Benefit Verify Request value, and have no Authorized Prescription, Original Prescription, or Coverage Benefit values. For each record that meets these conditions, the flow creates copies of the original record’s medication requests, coverage benefit, coverage benefit items, and coverage benefit item limits. It then populates the Authorized Prescription, Original Prescription, and Coverage Benefit fields in the copied record.

          • If the flow succeeds, it updates the status of the new care benefit verify request records to Pending.
          • If the flow fails, for example because of a network connection issue, it updates the status of the new care benefit verify request records to Error. The error status indicates that the copy process is incomplete because the flow didn’t create any records or update the Authorized Prescription, Original Prescription, and Coverage Benefit fields in the copied record.
          A program lead passes copied care benefit verify request records along to patient services reps for processing. If any records don't get copied, the program lead manually triggers the Copy Care Benefit Verify Request Fields flow for those records.

          Program leads can share a list view of the pending care benefit verify request records with patient services reps, or they can assign pending requests directly to patient services reps. To reverify the benefits, patient services reps access the shared list or the pending records assigned to them. Patient services reps can update the pharmacy benefits coverage details for each of these records.

          To trigger the copy flow manually for care benefit verify request records with a status of Error, change the status from Error to Copy.

           
          Loading
          Salesforce Help | Article