Arkansas APCD Data Submission Tips

The Arkansas APCD team works closely with submitting entities covering all aspects of data submission, and we have noted some commonly asked questions about the data exception process. The following are a few tips that we have found useful with other submitting entities:

1. When the values listed in the DSG for a data element contain the value U for unknown.
   

   When mapping values to DSG data element values:

   1. Map the submitting entity’s value that best represents the meaning described in the DSG to the appropriate DSG data element value.
   2. Map the submitting entity’s value to U if it does not represent any of the values represented in the DSG for that data element.
   3. Do not request an exception if the submitting entity’s value is not an option for the DSG data element and the value U is available for the DSG data element. Map the value to U.
      
      
2. Dependency Not Met Criteria

   When a dependency is in place and values are found on records that don’t meet the dependency, the number of records “failing” the dependency (values present when dependency specifies otherwise) is found in the Failed Dependency column of the Arkansas APCD Data Validation Summary Report. Records failing dependency will not show up in the Detail report that accompanies the summary report. See the example below.
   
   
   
   

3. Exceptions 

   Exceptions must be approved through the online process before they are applied to any subsequent file submission. If files are submitted before the exceptions are approved, the new exceptions will not be applied.
   
   

4. DSA Encryption
   Submitting entities can send multiple DSG keys to verify signatures, enabling the submitting entity to have staff redundancy for APCD data submission if necessary. It is important to remember that only one RSA key is allowed but after the initial set up, RSA keys do not need to be resubmitted.