Defining the Resolution Reasons for Discrepancies
In RDC, 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.
To define the possible set of resolution reasons, you use the DISCREPANCY RESOLU TYPE CODE installation reference codelist.
You enter information into the Description field and the Short Value field. RDC uses the text string that you specify in the Description field to display the list of resolution reasons to the user. Oracle Clinical stores the corresponding short value in the database.
Note:
RDC 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 or use this value in the DISCREPANCY RESOLU TYPE CODE codelist.The following table lists the entries in the DISCREPANCY RESOLU TYPE CODE codelist following the initial installation of Oracle Clinical.
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 |
SUPERSEDED |
Data value changed. Disc no longer applicable. |
OVERRULED |
NON DISCREPANT |
Disc not considered a validation error. |
DATA MODIFIED |
SUPERSEDED |
Data value changed. Disc no longer applicable. |
INV-NO INFO |
IRRESOLVEABLE |
Investigator queried. No further information available. |
Parent topic: Configuring Discrepancy Management