Controlled and Dangerous Substances (CDS) license validation can be customized for varying product schedules and CDS license requirements across states, to ensure users distribute samples and BRCs to HCPs with the appropriate credentials. CDS license information is validated when sampling to accounts in states which require CDS licenses for controlled substances. In some states, HCPs must have a CDS license for every address where they stock or store samples that are controlled by the state but not by the DEA, for example, Massachusetts Schedule VI substances.

Configuring CDS Validation for Non-Controlled and Schedule Specific Sampling (MCSR)

CDS validation can be customized to handle states with unique schedule categories and CDS requirements, for example, MCSR (Massachusetts Controlled Substance Registration). The following configuration extends the basic CDS validation functionality to accommodate states with varying CDS regulations.

This functionality is not supported on CRM Desktop (Mac (Sandbox Beta)).

To customize CDS license validation for states where schedule categories and CDS requirements differ from DEA requirements, complete the following additional configuration:

1. Grant admins Edit FLS for the following fields:

• CDS_Schedule_vod on the Address_vod object
• CDS_State_Schedule_vod on the Product_vod object
• CDS_for_Non_Controlled_vod on the Samples_State_Settings_vod object

2. Add the CDS_Schedule_vod field to the appropriate Address_vod page layouts.
3. Add the CDS_State_Schedule_vod field to the appropriate Product_vod page layouts.
4. Add the CDS_for_Non_Controlled_vod field to the appropriate Samples_State_Settings_vod page layouts.
5. Complete the following fields on Address_vod records, if not already populated:

• CDS_vod
• CDS_Expiration_Date_vod
• CDS_Status_vod

6. Populate the CDS_Schedule_vod field on the appropriate Address_vod records with a comma-delimited list of the schedules for which the HCP is licensed in the address’s state. For example: IV, V, VI. This step is for addresses in states where schedules are listed on CDS licenses.
7. Populate the CDS_State_Schedule_vod field on Product_vod records where CDS schedule restrictions apply, with a list of states and the schedule assigned to the product in each state. This step is for products with a schedule assigned by the state.

   Use the format state:schedule;state:schedule, where state is the API name of the corresponding picklist value in the State_vod field on the Address_vod object, and schedule is the text value of the schedule designated in that state. For example, MA:V;CA:06 indicates a product is categorized as Schedule Five in Massachusetts and Schedule Six in California. HCPs must be licensed for the appropriate schedule in each state in order to receive the product.

   The values in the CDS_State_Schedule_vod field on the Product_vod record must be an exact match for the values in the CDS_Schedule_vod field on Address_vod records. For example, if the roman numeral VI is used in the CDS_Schedule_vod field for addresses in Massachusetts, MA:VI must be used for that state in the CDS_State_Schedule_vod field on the Product_vod record.

   On a Product_vod record, only one schedule can be listed per state.

8. Create Samples_State_Settings_vod records for states where products are regulated as controlled substances by the state but not scheduled by the DEA, for example, Massachusetts. Select the CDS_for_Non_Controlled_vod check box on these records. This step enables CDS validation to run regardless of whether the Controlled_Substance_vod check box is selected on the sample or BRC Product_vod record.

   The Controlled_Substance_vod check box only needs to be selected on Product_vod records if the product is a DEA-scheduled controlled substance. For example, Schedule VI substances in Massachusetts do not need to be marked as controlled substances.

Before granting FLS to users, ensure CDS license and schedule information is complete on all appropriate Address_vod records, and the CDS_State_Schedule_vod field is populated on Product_vod records. If this information is not complete, users may be prevented from sampling.

9. Grant end users Read FLS for the following fields:
   • CDS_Schedule_vod on the Address_vod object
   • CDS_State_Schedule_vod on the Product_vod object
   • CDS_for_Non_Controlled_vod on the Samples_State_Settings_vod object

For more information on MCSR, see Ensuring Sampling Meets MCSR Requirements on the Veeva Flightpath site.