Testing that the Changes Are Valid

Before you commit your changes to the database, you can test if the changes are valid. Validation is optional. If you proceed directly to applying the changes to the database, the system runs the same validation test as part of the process and does not apply changes that would result in invalid data.

Running validation explicitly, in advance, gives you the opportunity to correct problems before you try to apply the changes.

To validate pending changes, click the Validate button in the Candidate Data Set window. The system displays a message when it completes testing the changes. Close the message box and review the Status field for each record:

• VS. The specified change(s) would result in valid data.

  The next time you apply changes to the database for this CDS, this record will be updated.

• VF. At least one of the record's specified change(s) would result in invalid data. A message is displayed in the Validation Comment field explaining the reason for the failure.

  The next time you apply changes to the database for this CDS, records with a status of VF will not be updated.

For all types of changes except RDCI Soft Delete, the system does not run validation tests on records with a status of either UN or IG (explicitly excluded from change). These records retain the same status after validation. For RDCI Soft Deletes, the system does validate records with a status of UN (see Soft-Deleting RDCIs).

See Applying the Changes to the Database.

Note:

The system gives incorrect error messages under certain circumstances when you attempt to update locked data, whether the data was explicitly locked or locked as part of "freezing" the patient, study, Investigator, or study site. System behavior is correct in terms of what data you are allowed to update, but the error message is incorrect.

If you do not have Privileged Update, you are not allowed to update locked data. The system correctly prevents you from updating data but may give an error message like "No update allowed to the RDCM buffer" or "Visit Name [or some other field] is not updateable."

If you do have Privileged Update, you are allowed to update locked data and soft-delete locked RDCIs. The system correctly allows you to update the data. However, instead of warning you that the data is locked, it may give an error message like "RDCI is not protected because at least one of its RDCMs is locked and you have privileged update."

In addition, if you try to update a record that contains no data (not a null value) you receive an error message that the record has been changed since the CDS was created. The error message is incorrect, but it is true that you cannot update the record using mass changes. Records with no data occur, for example, when a question is added to a DCM question group after data has been collected for the DCM, or when an indicator question response is entered but no data was collected. You must update these records in Data Entry Update.