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.

Validation Disclaimer

This functionality is released without validation. CDS Validation for Non-Controlled and Schedule-Specific Sampling requires enablement and does not affect other Vault CRM functionality. The functionality was extensively tested by our QA team during the development and release process and will go through validation at a later date.

To configure this feature:

1. Navigate to Admin > Users & Groups > Permission Sets.

2. Select the appropriate permission set.

3. Select the Objects tab.

4. Grant Edit permission for the following fields:

   • cds_schedule__v on the address__v object
   • cds_state_schedule__v on the product__v object
   • cds_for_non_controlled__v on the samples_state_settings__v object

5. Navigate to Admin > Configuration > Objects > address__v > Layouts.

6. Place the cds_schedule__v field on the appropriate address__v layouts.

7. Navigate to Admin > Configuration > Objects > product__v > Layouts.

8. Place the cds_state_schedule__v field on the appropriate product__v layouts.

9. Navigate to Admin > Configuration > Objects > samples_state_settings__v > Layouts.

10. Place the cds_for_non_controlled__v field on the appropriate samples_state_settings__v layouts.

To configure this feature:

1. Navigate to Business Admin > Objects > address__v.
2. Complete the following fields on address__v records, if not already populated:
   • cds__v
   • cds_expiration_date__v
   • cds_status__v
3. Populate the cds_schedule__v field on the appropriate address__v 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.
4. Navigate to Business Admin > Objects > product__v.
5. Populate the cds_state_schedule__v field on product__v 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 field name of the corresponding picklist value in the name__v field on the address__v object, and schedule is the API name of the schedule designated in that state. Only one schedule can be listed per state. HCPs must be licensed for the appropriate schedule in each state in order to receive the product.

     For example, ma__v:V;ca__v:06 indicates a product is categorized as Schedule Five in Massachusetts and Schedule Six in California.
     

   • The values in the cds_state_schedule__v field on the product__v record must be an exact match for the values in the cds_schedule__v field on address__v records.

     For example, if the roman numeral VI is used in the cds_schedule__v field for addresses in Massachusetts, ma__v:VI must be used for that state in the cds_state_schedule__v field on the product__v record.

6. Navigate to Business Admin > Objects > samples_state_settings__v.
7. Create samples_state_settings__v records for states where products are regulated as controlled substances by the state but not scheduled by the DEA, for example, Massachusetts.
8. Select the cds_for_non_controlled__v check box on the newly created samples_state_settings__v records. This step enables CDS validation to run regardless of whether the controlled_substance__v check box is selected on the product__v record.
   • Do not select both the cds_required__v and cds_for_non_controlled__v check boxes on the same record
   • Do not select the controlled_substance__v check box on product__v records for Massachusetts Schedule VI substances. This check box only needs to be selected if the product is a DEA-scheduled controlled substance.
9. Ensure CDS license and schedule information is complete on all appropriate address__v records, and the cds_state_schedule__v field is populated on product__v records. If this information is not complete, users may be prevented from sampling once field permissions are granted to them.
10. Navigate to Admin > Users & Groups > Permission Sets.
11. Select the appropriate permission set.
12. Select the Objects tab.
13. Grant end users Read permission for the following fields:
    • cds_schedule__v on the address__v object
    • cds_state_schedule__v on the product__v object
    • cds_for_non_controlled__v on the samples_state_settings__v object

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