Setting Up Test Study Design

When you create a live clinical study version, Oracle Clinical automatically assigns test sites, Investigators, and ten patient positions to it. This provides the framework you need to test your definitions. You can use Test mode layouts and forms as you would their Production mode counterparts, ensuring that they correctly represent the study's requirements.

When you enter data into a CRF, you specify or select Investigator, Site, Patient, Clinical Planned Events (CPEs), and Visits. Oracle Clinical uses Test mode data for Investigator, Site, and Patient information. However, Oracle Clinical uses the same CPE and Visit information for both Production and Test mode. (The data comes from the same tables.)

The test sites, Investigators, and patient position names that are included with the installation have a leading X to distinguish them from production data. If you need additional cases you can modify or add to this data. For example, you can modify the generated details in a patient position where you need procedures requiring different sexes or dates of birth.

If you modify or supplement these test objects, Oracle recommends adhering to a naming convention that avoids confusion with production data. Oracle Clinical prevents using test data in Production mode, but hard copy reports or SAS data sets with test data that have similar names to production data could cause confusion.

The Design Test mode systems are identical to their production counterparts. For instructions for using these utilities, refer to the references included in this list:

For more information , see:

About Test Mode Synonyms

Oracle Clinical creates the following private synonyms that point to the test tables or to the views in Test mode. When you access a Test mode option, Oracle Clinical creates synonyms for you that point to the test tables. Oracle Clinical drops the synonyms for Production mode.

Table 17-1 Synonyms

Test Synonym Production Mode Table or View

ACTUAL_EVENTST

ACTUAL_EVENTS

ACTUAL_EVENTS1T

ACTUAL_EVENTS1

ACTUAL_EVENTSVT

ACTUAL_EVENTSV

DISCREPANCY_ENTRIEST

DISCREPANCY_ENTRIES

DISCREPANCY_ENTRY_REVIEW_HISTT

DISCREPANCY_ENTRY_REVIEW_HIST

DISCREPANCY_MANAGEMENTT

DISCREPANCY_MANAGEMENT

INVESTIGATORST

INVESTIGATORS

INVESTIGATORST

OCL_INVESTIGATORS

SITEST

OCL_SITES

RXC_STUDY_SITEST

OCL_STUDY_SITES

STUDY_SITE_ROLEST

OCL_STUDY_SITE_ROLES

OPA_LEVEL_PRIVST

OPA_LEVEL_PRIVS

PATIENT_POSITIONST

PATIENT_POSITIONS

PATIENT_POSITIONS_VT

PATIENT_POSITIONS_V

RDC_AUDIT_VIEWT

RDC_AUDIT_VIEW

RDC_DISCREPANCIEST

RDC_DISCREPANCIES

RDC_PDF_VRVST

RDC_PDF_VRVS

RDC_VRVST

RDC_VRVS

RDCI_HISTORYT

RDCI_HISTORY

RECEIVED_DCIST

RECEIVED_DCIS

RECEIVED_DCIS_VT

RECEIVED_DCIS_V

RECEIVED_DCMST

RECEIVED_DCMS

RECEIVED_DCMS_VT

RECEIVED_DCMS_V

RECEIVED_PAGE_HISTORYT

RECEIVED_PAGE_HISTORY

RECEIVED_PAGEST

RECEIVED_PAGES

RESPONSEST

RESPONSES

RXC_STUDY_SITEST

RXC_STUDY_SITES

SITEST

SITES

STUDY_SITE_PATIENT_POST

STUDY_SITE_PATIENT_POSITIONS

STUDY_SITE_ROLEST

STUDY_SITE_ROLES

VALIDATION_REPORTED_VALUEST

VALIDATION_REPORTED_VALUES

VALIDATION_REPORTED_VALUES_VT

VALIDATION_REPORTED_VALUES_V

Until you move a study to production, all of your Oracle Clinical sessions for that study are in Test mode. When you are in Test mode, your Oracle account points to test tables. This condition applies even after you log out and log back in. You can check whether you are pointing to test or production tables by looking in the User Synonyms table in a SQL session.