You are here:
Provider Engagement Compliance Glossary
Before you dive into the configurations for Provider Engagement Compliance, familiarize yourself with the feature's nomenclature. Learn about the terms that are commonly used to describe Provider Engagement Compliance, including the terminology used throughout the feature's lifecycle.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package. |
Generic Terms
- EPPV (Early Post-Marketing Phase Vigilance): A mandatory regulatory process in Japan that monitors the safety, effectiveness, and overall performance of newly launched pharmaceutical products for the first six months of sales.
- MID (Medical Information Delivery): A regulatory requirement in Japan mandating pharmaceutical companies to deliver promptly urgent safety documents and information to healthcare institutions where their drugs are prescribed.
- Provider Engagement Compliance: The Agentforce Life Sciences Cloud (AFLS) name for the overall EPPV and MID feature.
- Compliance Template: A reusable template created by using Action Plan Template. This template dictates the structure of the compliance process, including cycle length, number of cycles, and restart and last-cycle behaviors.
- Compliance Program: These records, created by using Care Program, contain the specific details, such as mandatory regulatory dates and associated products (Care Program Product).
- Account Compliance Plan: These records are created by using Action Plan for each HCO participating in a compliance program. Sales representatives use these records to monitor the required compliance activities during visits to those HCOs.
- Provider Engagement Compliance Cycles: The account-specific generated cycles that contain the details of when sales representatives must conduct visits for an HCO.
- Compliance Activity: The actual record of the Provider Engagement Compliance interaction is created by using Assessment Task. A sales representative captures the interaction during a scheduled visit to an HCO.
- Institution Doctor Account: A business account type that links an HCP to an HCO, which serves as the target account for scheduling compliance activities.
Key Configurations
- Compliance Announce Date: The date when the compliance program officially becomes visible to sales representatives.
- Compliance Start Date: The date when a sales representatives officially delivers a pharmaceutical product at an HCO. On this date, you can change the status of an account compliance to In Progress.
- Compliance End Date: The date marking the end of the compliance period beyond which Salesforce doesn't create any cycle.
- Extension Due Date: The latest date that the final compliance cycle can be extended to, allowing users a final window to execute their compliance activity visits.
- Modification End Date: The final date after which sales representatives can’t log new visits or enter or modify reasons for skipped cycles.
- Pre-Cycle Start Date: A compliance template setting that defines the date when sales representatives can begin optional pre-survey visits to HCO before the product is officially launched. A pre-survey visit can begin on the defined pre-cycle start date and conclude one day before the compliance start date.
- Restart Behavior: A compliance template setting that defines the rules to generate new
cycles when sales representatives restart an interrupted compliance plan. There are four
available Restart Behavior options.
- Not Allowed: Sales representatives can’t restart an account compliance. This is the default option.
- Restart: Salesforce deletes the incomplete cycles when you stop an account compliance. When you restart the account compliance, Salesforce deletes the completed cycles.
- Start Over: Salesforce deletes the incomplete cycles when you stop an account compliance. When you restart the account compliance, Salesforce generates a new set of cycles, by using the restart date as the start date for Cycle 1.
- Resume: Salesforce retains the completed cycles and deletes the incomplete ones when you stop an account compliance. When you restart the account compliance, Salesforce generates the incomplete cycles by using the restart date as the start date for the next cycle.
- Last Cycle Behavior: A compliance template setting that determines how Salesforce
handles the final cycle if the cycle approaches the compliance end date. There are three
Last Cycle Behavior options.
- Do Not Create: Salesforce skips generating a cycle and its subsequent ones if the cycle's calculated end date falls after the compliance end date.
- Create With Cycle End Date: Salesforce generates cycles with an end date based on the duration defined in the compliance template. However, if the cycle’s end date exceeds the extension due date, Salesforce adjusts a cycle's end date to match the extension due date. This is the default option.
- Create With Compliance End Date: Salesforce generates cycles ignoring the duration defined in the compliance template and sets a cycle's end date to match the compliance end date.
Did this article solve your issue?
Let us know so we can improve!
