Exit/Autosequence Behavior

Oracle Clinical behaves in different ways when you have finished data entry on a particular form and selected Save. First, it preserves your changes and returns you to the header. If entry on the RDCM is complete, your changes are saved, and you exit the form. However, if the system determines that the form is not complete—for instance, if mandatory fields have not been filled out, or if fields entered in first pass were not entered in second pass, a message specifies what must be completed, and the cursor is placed in the first incomplete field.

To exit without saving changes, select Exit. If you have pending changes, the Changes Pending dialog box gives you the following choices. If you have made changes, the Changes Pending dialog box offers the options:

Cancel—Places you back in Data Entry and allows you to continue data entry.

Discard—Exits the form and discards all pending changes.

Save Incomplete—Saves pending changes, and exits the form with the RDCM in an incomplete state with a status of pass 2 started.

If you are not in First-Pass Data Entry and have not made any changes, clicking Exit exits the form without confirmation. If you are in First-Pass Data Entry and the RDCM has a status of Received, you can choose Discard or Save as Blank. The Save as Blank option sets the Blank flag to Y.

Note:

You can set the Blank flag to Y in the Initial Login, Initial Login and First-Pass Data Entry, and First-Pass Data Entry modes. If a DCI or DCM has the Blank flag set to Y, it means that this CRF is logged in but the form is blank. Blank RDCIs and RDCMs are not accessible.

To go directly to the next form when you leave the last field on the current form, set the user preference Autosequence. If this preference is enabled, Oracle Clinical silently saves your work before proceeding to the next form. If you prefer an audible signal, enable the preference End of Form Beep. Depending on your current entry mode, the cursor returns to the entry header if Log-In cannot be completed or goes to the first enterable data entry field of the next form in sequence.

Table 2-2 Autosequence Impact on RDCIs from Last Enterable Field with Autosequence Enabled

Action	RDCM info Required	Result in Log-In or Key Changes	Result in Log-In and First-Pass Entry
[Next Field]	Y	Cursor moves to RDCM window, then to Data Entry.	Cursor moves to RDCM window, then to Data Entry.
-	N	RDCI/RDCM saved; status set to RECEIVED; RDCI cleared for next RDCI.	Cursor moves to Data Entry.
[Save]	Y	Cursor moves to RDCM window, then to Data Entry.	Cursor moves to RDCM window, then to Data Entry.
-	N	RDCI/RDCM saved; status set to RECEIVED; RDCI cleared for next RDCI.	Cursor moves to Data Entry.
[Next Block]	Y	Cursor moves to RDCM window, then to Data Entry.	Cursor moves to RDCM window, then to Data Entry.
-	N	RDCI/RDCM saved; status set to RECEIVED; RDCI cleared for next RDCI.	Cursor moves to Data Entry.

Table 2-3 Autosequence Impact on RDCIs from Last Enterable Field with Autosequence Disabled

Action	RDCM info Required	Result in Log-In or Key Changes	Result in Log-In and First-Pass Entry
[Next Field]	Y	Cursor cycles through RDCI fields.	Cursor cycles through RDCI fields.
-	N	Cursor cycles through RDCI fields.	Cursor cycles through RDCI fields.
[Save]	Y	RDCI validated; RDCM displayed to collect RDCM-level information.	Cursor moves to RDCM window, then to Data Entry.
-	N	RDCI/RDCM saved; status set to RECEIVED; RDCI cleared for next RDCI.	RDCI/RDCM saved; status set to Received; RDCI continues to display.
[Next Block]	Y	RDCI validated; RDCM displayed to collect RDCM-level information.	Cursor moves to Data Entry.
-	N	Completed RDCM window displays; press second time— a message informs you that RDCM is complete.	Cursor moves to Data Entry.