NIMH Data Archive Post-Submission QA/QC

The NDA ensures all data are harmonized to a common definition prior to submission. This validation ensures that all data conforms.  Post submission, Quality Assurance and Quality Control (QA/QC) checks are run across records ensuring basic information is accurate. Results of these checks are then collated by NDA Collection and sent to those that submitted the data, typically data managers, so that any issues found may be fixed prior to the next scheduled submission.  The email provides a link to a report containing Summary and Detailed QA/QC issues.  This page provides information on what checks are made and when found, how labs submitting those data may interpret and resolve the issues found.  

In addition to the QA/QC reports, those with Admin access to the collection, may also download records identified with errors by navigating to their Collection, clicking on the Submissions tab, and then selecting the "Submissions with QA Errors" radio button to see if any submissions contain errors (authentication is required).  Then, by adding specific error types to your filter cart and downloading them, you can more easily see the records in error by viewing only the affected submissions.  You'll have to review all data structures to see where that error is discrepant with other data previously submitted.

Downloads of submissions with potential QA issues through this method will automatically include a QA_into.txt file with a report on these issues.

The goal is to resolve these issues as soon as possible helping ensure that accurate data are shared in a timely manner. Feel free to contact us if you require additional information or assistance in resolving these outstanding issues (NDAHelp@mail.nih.gov). 

Summary Discrepancy Issue Resolutions

The following summary discrepancies are provided in the NDA QA Report.  

MISSING SUBJECTS FOR DATA STRUCTURE PROVIDED: Clinical data are expected to be submitted cumulatively. This error is returned when the percentage of submitted subjects are not included in subsequent submissions.  Please note, this rule checks subjectkey, age, date combinations and forgives resubmissions that are off by +/-2 months. Therefore it is possible that a subject was resubmitted but was flagged in the QA process because that subject was not resubmitted for that age date combination within the data structure of interest.

 

  • Suggested Action: Review the submission to confirm all subjects collected so far were included in your cumulative submission. If not, reupload your cumulative submission. Note that neurosignaling and omics subject data are excluded from this report as those data are only expected to be submitted once. 

 

MISSING DATA STRUCTURE: Clinical data are expected to be submitted cumulatively. This error indicates a structure submitted previously is not found in subsequent submissions. You will be provided with the shortname of the structure in question.

 

  • Suggested Action: Confirm all cumulative data was submitted. Upload missing structures or confirm with NDA to resolve. 

 

Detailed QA/QC Issue Resolutions

The following errors are available in the QA/QC report provided.  However, these issues may also be added to your filter cart and downloaded helping you identify and resolve the issue.  To download, go to your collection, the submission tab (authentication is required to see the submission tab) and select "QA Submissions with errors" radio button and then add the submission(s) to the NDA filter cart.  

MISCALCULATED AGE - INTERVIEW DATE INCONSISTENT WITH AGE: This error indicates that multiple ages (in months) are listed for a given subject for the same relative interview_date. It is very important that age be consistent across measures.

  • Suggested Action: Review the ages (in months) recorded for the subjects across the data structures noted on the error report. Ensure that the correct age in recorded. Age in months should be determined using the following rule: If <=15 days into the next month, round the age down in months. If >15 days into the next month, round the age up to the next month. Once records have been corrected, resubmit the data.

 

MISCALCULATED AGE - INTERVIEW AGE INCONSISTENT WITH DATE: This error indicates that mutiple dates are listed for a given subject for the same relative interview_age. It is very important that age is consistent across measures.

  • Suggested Action: Review the ages (in months) recorded for the subjects across the data structures noted on the error report. Ensure that the correct age is recorded. Age in months should be determined using the following rule: If <=15 days into the next month, round the age down in months. If >15 days into the next month, round the age up to the next month. Once records have been corrected, resubmit the data.

 

INCONSISTENT SEX PROVIDED: This error indicates that a given subject has existing records with the sex labeled with more than one valid sex value (e.g., male (M) in one instance and female (F) in another).

  • Suggested Action: Review the source documents for the correct sex. Record the appropriate code (male (M), female (F) ) on all subject records locally and resubmit. If the change in sex is a valid change, note this information in the Supporting Documentation section of the Collection.

 

INCONSISTENT GUID FOR SAME SRC_SUBJECT_ID: This error indicates that a src_subject_id (locally used ID) within a data set is ascribed to multiple GUIDs. A SRC_SUBJECT_ID and a GUID should refer to a unique individual consistently across measures.

 

  • Suggested Action: Review the source documents for the subject’s correct GUID. If necessary, use the GUID Tool to validate the GUID. Correct data locally and resubmit.


INCONSISTENT SRC_SUBJECT_ID FOR SAME GUID: This error indicates that a given GUID has multiple src_subject_ids (locally used IDs) within a single data set. A SRC_SUBJECT_ID and a GUID should refer to a unique individual consistently across measures.

 

  • Suggested Action: Review the source documents for the subject’s correct src_subject_id (locally used ID). Correct data locally and resubmit. This change in the data should be documented and uploaded to the Supporting Documentation in the Collection.