Customizing the Field Display on the Candidate Data Set Form

These local codelists control the display of fields on the Candidate Data Set form for the four Mass Changes Utility change types:

• FLD RXCMCMCD RDCI KEY

• FLD RXCMCMCD RDCM KEY

• FLD RXCMCMCD RDCI DELETE

• FLD RXCMCMCD RESPONSE

From the Admin menu, select Reference Codelists, then select  Local Codelists, and query FLD% in the Name field. The following table describes how the codelist values control all four codelists:

Table 4-2 CDS Display Codelist Fields

Codelist Field Name	Description
Seq	Sequence number: Orders each value's column position in either the fixed (the lowest numbers), or scrolling sections of the Mass Changes Utility form. (See Description, below)
Short Value	The name of the field in the form. You must not change these values.
Long Value	The display length for the field on the Candidate Data Set form.
Active box	Check a value's Active box to display to include its field on the Mass Changes Utility form.
Default box	N/A
Description	The value's assignment to the non-scrolling or scrolling sections of the Mass Changes Utility form, and its prompt label. The description field has the following syntax: F:promptlabel or S:promptlabel Where: F: locates the field in the left-side, non-scrolling section of the Candidate Data Set form. S: locates the field on the scrolling, right-side section of the Candidate Data Set form. promptlabel The field label on the Candidate Data Set form. If all fields are non-scrolling, you must still use the F:promptlabel syntax. For Response data and data comment fields, the prompt is the default prompt for the DCM question concatenated with promptlabel.

Oracle Clinical has default values for these codelists that reflect the most likely scenario for displaying the Candidate Data Set. You can modify the default values. customizing-field-display-candidate-data-set-form.html#GUID-30E464A0-3163-437C-BD8C-9B3501470345__CHDJGAAG lists all possible column values. You can add, remove, modify, or rearrange the display fields. Footnotes follow that table.

The following table is a legend for the values in customizing-field-display-candidate-data-set-form.html#GUID-30E464A0-3163-437C-BD8C-9B3501470345__CHDJGAAG.

Table 4-3 Legend for customizing-field-display-candidate-data-set-form.html#GUID-30E464A0-3163-437C-BD8C-9B3501470345__CHDJGAAG

Symbol	Description
~	A tilde (~) indicates that the value does not qualify for any of the change types. RDCI KEY change type
D	RDCI DELETE change type
M	RDCM KEY change type
R	RESPONSE change type
All	Applies to all change type codes: RDCI KEY, RDCI DELETE, RDCM KEY, RESPONSE The system does not display this field. Instead a display field is used as with the Data Entry Log-in form. This field displays the data retrieved into the base table field in the appropriate format and translates the information entered into the new fields to the format needed by the base table fields. This field contains an list of values, or is update-able, pertains to the display field, with the update of the base table fields by the system. It is necessary for the reference codelist to have the display fields rather than the base table field. For these fields, the labels, Column value refers to the base table field and short name refers to the display field. The clin_plan_eve_name_new field list of values contains the visit number as well, for reference purposes only.
†	Responses and associated old and new values are required and present by default, if they exist.
‡	An list of values is present for exception_value_text if an alpha data code discrete value group exists for the DCM question, and values from this group are part of the list of values. An list of values is present for value_text if a discrete value group exists for the DCM question, and values from this group will appear in the list of values There is an list of values for the full_value_text if any discrete value group exists for the DCM question, and values from these groups appear in the list of values.

Table 4-4 Candidate Data Set Form Codelist Values with Display Settings by Mass Changes Utility Change Type

Column Value	Short Name	Recom- mended	Set by Default	Can be Set	List of Values	Update-able
cdr_status_code	cdr_status_code	All	All
validate_comment	val_comment	All	All
change_reason_codeFoot 1 (Must be valid in codelist)	c_reason_code	All	All		All	All
audit_comment	audit_comment	All	All			All
how_updated	how_updated	I, M, R	I, M, R
received_dci_id	received_dci_id			All
document_number	doc_number	All	All
document_number_new	doc_number_new	I	I			I
investigator	investig	I	All
investigator_new	investig_new	I	I		I	I
site	site	I	All	~	~	~
site_new	site_new	I	I	~	I	I
patient	patient	I	All	~	~	~
patient_new	patient_new	I	I	~	I	I
dci_short_name	dci_sh_name	I	All	~	~	~
dci_short_name_new	dci_sh_name_new	I	I	~	I	I
clin_plan_eve_name	cpe_name	I	All	~	~	~
clin_plan_eve_name_new	cpe_name_new	I	I, M	~	I, M	I, M
visit_number	vis_number	I	All	~	~	~
subevent_number	sub_number	I	All	~	~	~
subevent_number_new	sub_number_new	I	All	~	I, M	I, M
dci_date	dci_dt	I	I, D, M	R	~	~
dci_date_new	dci_dt_new	I	I	~	~	I
dci_time	dci_tm	I	I, D, M	R	~	~
dci_time_new	dci_tm_new	I	I	~	~	I
comment_text	cm_txt	I, M	I, D, M	R	~	~
comment_text_new	cm_txt_new	I, M	I, M	~	~	I, M
blank_flag	blank_flag	I, M	I, D, M	R	~	~
blank_flag_new	blank_flag_new	I, M	I, M		I, M	I, M
received_dcm_id	received_dcm_id	~	~	M, R	~	~
rdci_clin_plan_eve_name	rdci_cpe_name	~	~	M, R	~	~
rdci_visit_number	rdci_vis_number	~	~	M, R	~	~
rdci_subevent_number	rdci_sub_number	~	~	M, R	~	~
rdci_comment_text	rdci_cm_txt	~	~	M, R	~	~
rdci_blank_flag	rdci_blank_flag	~	~	M, R	~	~
dcm_name	dcm_name	M	M, R	~	~	~
dcm_subset_name	dcm_subset_name	~	M	R	~	~
dcm_layout_sn	dcm_layout_sn	~	M	R	~	~
dcm_date*	dcm_dt	M	M	R	~	~
dcm_date_new*	dcm_dt_new	M	M	~	~	M
dcm_time*	dcm_tm	M	M	R	~	~
dcm_time_new*	dcm_tm_new	M	M	~	~	M
qualifying_value	qual_value	M	M, R	~	~	~
qualifying_value_new	qual_value_new	M	M	~	M	M
data_comment_text	dta_cm_txt	M	M	R	~	~
data_comment_text_new	dta_cm_txt_new	M	M	R	~	M
repeat_sn	repeat_sn	R	R	~	~	~
response_id1	response_id1	~	~	R	~	~
validation_status1	valid_status1	~	R	~	~	~
exception_value_text1	e_val_txt1	~	~	R	R‡	~
value_text1	val_txt1	~	~	R	R	~
full_value_text1	f_val_txt1	R	R	~	R	~
full_value_text1_newFoot 2	f_val_txt1_new	R	R	~	R	R
data_comment_text1	dta_cm_txt1	R	R	~	~	~
data_comment_text1_new	dta_cm_txt1_new	R	R	~	~	R
response_id2	response_id2	~	~	R	~	~
validation_status2	valid_status2	~	R	~	~	~
exception_value_text2	e_val_txt2	~	~	R	R‡	~
value_text2	val_txt2	~	~	R	R	~
full_value_text2	f_val_txt2	R†	R†	~	R	~
full_value_text2_new2	f_val_txt2_new	R†	R†	~	R, as per data entry	R
data_comment_text2	dta_cm_txt2	R†	R†	~	~	~
data_comment_text2_new	dta_cm_txt2_new	R†	R†	~	~	R
response_id3	response_id3	~	~	R	~	~
validation_status3	valid_status3	~	R	~	~	~
exception_value_text3	e_val_txt3	~	~	R	R‡	~
value_text3	val_txt3	~	~	R	R	~
full_value_text3	f_val_txt3	R†	R†	~	R	~
full_value_text3_new	f_val_txt3_new	R†	R†	~	R, as per data entry	R
data_comment_text3	dta_cm_txt3	R†	R†	~	~	~
data_comment_text3_new	dta_cm_txt3_new	R†	R†	~	~	R
response_id4	response_id4	~	~	R	~	~
validation_status4	valid_status4	~	R	~	~	~
exception_value_text4	e_val_txt4	~	~	R	R‡	~
value_text4	val_txt4	~	~	R	R	~
full_value_text4	f_val_txt4	R†	R†	~	R	~
full_value_text4_new	f_val_txt4_new	R†	R†	~	R, as per data entry	R
data_comment_text4	dta_cm_txt4	R†	R†	~	~	~
data_comment_text4_new	dta_cm_txt4_new	R†	R†	~	~	R

^Footnote 1

Validation issue: Value must be valid in the reference code list.

^Footnote 2

Validation issue: Must pass field validation in data entry.