Oracle® Clinical Administrator's Guide Release 5.1 E53556-02 |
|
|
PDF · Mobi · ePub |
Setting up the Mass Change Utility (MCU), which is described in Oracle Clinical Conducting a Study, requires performing the following general steps, each described in the following sections:
Oracle Clinical supplies two default database roles for the Mass Changes Utility:
RXC_MC
RXC_MC_TEST
RXC_MC has access to all production mass change options and RXC_MC_TEST has access to the test mass change options only. Your organization can also choose to create your own roles.
Assign these roles to the users that work with the Mass Changes Utility.
The Mass Changes Utility uses the local reference codelists described in the following table. You can modify them to suit your organization's needs. The affected tablename.columnname column indicates the database columns that are affected by or use each reference codelist. From the Admin menu, select Reference Codelists, then select Local Codelists and query the codelists named in the following table.
Table 4-1 Mass Changes Utility Reference Codelists
Name | Description | Affected Tablename.Columnname |
---|---|---|
|
Default sort order for viewing and applying the candidate data set (CDS); the columns you can order. |
|
|
The list of columns that can be used in LHS or RHS of criteria, such as RDCI.SITE |
|
Columns available for the LHS and RHS of the CDS Criteria form, regardless of the discrepancy type specified, such as |
|
|
Columns available for the LHS and RHS of the CDS Criteria form, where the discrepancy type specified is UNIVARIATE, such as DE.DISCREPANCY_TYPE_CODE |
|
|
Columns available for the LHS and RHS of the CDS Criteria form, where the discrepancy type specified is INDICATOR |
|
|
Columns available for the LHS and RHS of the CDS Criteria form, where the discrepancy type specified is MULTIVARIATE, such as PROCEDURES.NAME |
|
|
Columns available for the LHS and RHS of the CDS Criteria form, where the discrepancy type specified is MANUAL HEADER |
|
|
Candidate Data Set fields to be displayed on the Candidate Data Set form when called for RDCI KEY changes, their order of display, width, and prompt. |
N/A |
|
Candidate Data Set fields to be displayed on the Candidate Data Set form when called for RDCM KEY changes, their order of display, width, and prompt |
N/A |
|
Candidate Data Set fields to be displayed on the Candidate Data Set form when called for RDCI DELETE changes, their order of display, width, and prompt |
N/A |
|
Candidate Data Set fields to be displayed on the Candidate Data Set form when called for Responses changes, their order of display, width, and prompt |
N/A |
|
|
Sets the default maximum number of records to change in a Candidate Data Set. Its initial long value is 1000. |
|
Footnote 1 Only the display sequence and whether the field should be sorted in ascending or descending order should be changed. New fields should not be added and existing ones should not be removed.
Footnote 2 The values in this reference codelist determine the contents of the list of values for mass change criteria. Additional values may be added to the reference codelist but they must be from one of the existing tables already defined for values, and they must use the alias provided for the table. No validation occurs against the values in this codelist. If a value is not in the list of values it can still be added as a criterion for specifying the candidate data set.
Footnote 3 OCL MC PREFS currently has one value, MAX_CDS_RECORDS, which controls the default maximum number of records to include in a Candidate Data Set.
These local codelists control the display of fields on the Candidate Data Set form for the four Mass Changes Utility change types:
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:
Where:
If all fields are non-scrolling, you must still use the For Response data and data comment fields, the prompt is the default prompt for the DCM question concatenated with |
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. Table 4-4, "Candidate Data Set Form Codelist Values" 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 Table 4-4, "Candidate Data Set Form Codelist Values".
Table 4-3 Legend for Table 4-4, "Candidate Data Set Form Codelist Values"
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 |
† |
Responses and associated old and new values are required and present by default, if they exist. |
‡ |
An list of values is present for |
Ñ |
An list of values is present for |
½ |
There is an list of values for the |
Table 4-4 Candidate Data Set Form Codelist Values
Column Value | Short Name | Display Settings by Mass Changes Utility Change Type | ||||
---|---|---|---|---|---|---|
Recom- mended |
Set by Default | Can be Set | List of Values | Update-able | ||
|
|
All |
All |
|||
|
|
All |
All |
|||
(Must be valid in codelist) |
|
All |
All |
All |
All |
|
|
|
All |
All |
All |
||
|
|
I, M, R |
I, M, R |
|||
|
|
All |
||||
|
|
All |
All |
|||
|
|
I |
I |
I |
||
|
|
I |
All |
|||
|
|
I |
I |
I |
I |
|
|
|
I |
All |
~ |
~ |
~ |
|
|
I |
I |
~ |
I |
I |
|
|
I |
All |
~ |
~ |
~ |
|
|
I |
I |
~ |
I |
I |
|
|
I |
All |
~ |
~ |
~ |
|
|
I |
I |
~ |
I |
I |
|
|
I |
All |
~ |
~ |
~ |
|
|
I |
I, M |
~ |
I, M** |
I, M |
|
|
I |
All |
~ |
~ |
~ |
|
|
I |
All |
~ |
~ |
~ |
|
|
I |
All |
~ |
I, M |
I, M |
|
|
I |
I, D, M |
R |
~ |
~ |
|
|
I |
I |
~ |
~ |
I |
|
|
I |
I, D, M |
R |
~ |
~ |
|
|
I |
I |
~ |
~ |
I |
|
|
I, M |
I, D, M |
R |
~ |
~ |
|
|
I, M |
I, M |
~ |
~ |
I, M |
|
|
I, M |
I, D, M |
R |
~ |
~ |
|
|
I, M |
I, M |
I, M |
I, M |
|
|
|
~ |
~ |
M, R |
~ |
~ |
|
|
~ |
~ |
M, R |
~ |
~ |
|
|
~ |
~ |
M, R |
~ |
~ |
|
|
~ |
~ |
M, R |
~ |
~ |
|
|
~ |
~ |
M, R |
~ |
~ |
|
|
~ |
~ |
M, R |
~ |
~ |
|
|
M |
M, R |
~ |
~ |
~ |
|
|
~ |
M |
R |
~ |
~ |
|
|
~ |
M |
R |
~ |
~ |
|
|
M |
M |
R |
~ |
~ |
|
|
M |
M |
~ |
~ |
M |
|
|
M |
M |
R |
~ |
~ |
|
|
M |
M |
~ |
~ |
M |
|
|
M |
M, R |
~ |
~ |
~ |
|
|
M |
M |
~ |
M |
M |
|
|
M |
M |
R |
~ |
~ |
|
|
M |
M |
R |
~ |
M |
|
|
R |
R |
~ |
~ |
~ |
|
|
~ |
~ |
R |
~ |
~ |
|
|
~ |
R |
~ |
~ |
~ |
|
|
~ |
~ |
R |
R‡ |
~ |
|
|
~ |
~ |
R |
RÑ |
~ |
|
|
R |
R |
~ |
R½ |
~ |
|
|
R |
R |
~ |
R½ |
R |
|
|
R |
R |
~ |
~ |
~ |
|
|
R |
R |
~ |
~ |
R |
|
|
~ |
~ |
R |
~ |
~ |
|
|
~ |
R |
~ |
~ |
~ |
|
|
~ |
~ |
R |
R‡ |
~ |
|
|
~ |
~ |
R |
RÑ |
~ |
|
|
R† |
R† |
~ |
R½ |
~ |
|
|
R† |
R† |
~ |
R½, as per data entry |
R |
|
|
R† |
R† |
~ |
~ |
~ |
|
|
R† |
R† |
~ |
~ |
R |
|
|
~ |
~ |
R |
~ |
~ |
|
|
~ |
R |
~ |
~ |
~ |
|
|
~ |
~ |
R |
R‡ |
~ |
|
|
~ |
~ |
R |
RÑ |
~ |
|
|
R† |
R† |
~ |
R½ |
~ |
|
|
R† |
R† |
~ |
R½, as per data entry |
R |
|
|
R† |
R† |
~ |
~ |
~ |
|
|
R† |
R† |
~ |
~ |
R |
|
|
~ |
~ |
R |
~ |
~ |
|
|
~ |
R |
~ |
~ |
~ |
|
|
~ |
~ |
R |
R‡ |
~ |
|
|
~ |
~ |
R |
RÑ |
~ |
|
|
R† |
R† |
~ |
R½ |
~ |
|
|
R† |
R† |
~ |
R½, as per data entry |
R |
|
|
R† |
R† |
~ |
~ |
~ |
|
|
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.