Defining Resolution Reasons for Discrepancies
Users can manually resolve discrepancies. When doing so, the user must also provide an explanation — a reason — for resolving the discrepancy. The user must select a resolution reason from the list that you define in the DISCREPANCY RESOLU TYPE CODE installation reference codelist.
Enter values in the Description field and the Short Value field. The system displays the text string that you specify in the Description field to display the list of resolution reasons to the user. The corresponding short value is stored in the database.
Note:
Oracle reserves the CND BLK DELETED value as the resolution for a manual discrepancy associated with a conditional block that was deleted. The value is hard-coded. Do not add this value to the DISCREPANCY RESOLU TYPE CODE codelist.
The following table lists the default entries in the DISCREPANCY RESOLU TYPE CODE codelist.
Table 3-13 Values for the DISCREPANCY RESOLU TYPE CODE
Short Value | Long Value | Description |
---|---|---|
CRA VERIFY |
CONFIRMED |
CRA Correction |
CRA VERIFY-INV |
CONFIRMED |
CRA Correction, Investigator consulted |
CRA VERIFY-SRC |
CONFIRMED |
CRA Correction, Source Data consulted |
INV VERIFY |
CONFIRMED |
Investigator Correction |
STUDY ASSUMP |
CONFIRMED |
Study Assumption |
NO ACTION REQD |
CONFIRMED |
No Action Required |
ELIMINATED |
IRRESOLVABLE |
Data value changed. Disc no longer applicable. |
OVERRULED |
NON DISCREPANT |
Disc not considered a validation error. |
DATA MODIFIED |
IRRESOLVABLE |
Data value changed. Disc no longer applicable. |
INV-NO INFO |
IRRESOLVEABLE |
Investigator queried. No more information available. |
If you add a value, select a long value from the following:
-
NULL: No value entered.
-
CONFIRMED
-
IRRESOLVABLE: Used for values which correspond to manually closed discepancies. This makes the RESOLUTIONTYPE CODE and COMMENT available when user selects an IRRESOLVABLE status.
-
NOT DISCREPANT. Used for manual discrepancies only; indicates that the discrepancy was raised for a comment, not because there was a problem with the data.
Parent topic: Configuring Discrepancy Management