Specify a file name convention for each lifecycle stage

This procedures describes how to select the clinical model, name a file specification, set the lifecycle stage, and select the submission mode.

Important:

Make sure you have the privileges to load data in the specified lifecycle stage. If not, data loads will fail. When the data load runs, it uses the account that defined or most recently updated the File Specification.

1. Click the Study Configuration icon from the navigation bar. Then click the Clinical Data Models tab.

2. Select Development from the Lifecycle drop-down at the top of the page.

   Tip:

   In the Development lifecycle context you can configure File Watcher for any lifecycle stage.

3. Select the model and click Check Out.

4. In the Watcher Configuration tab, under File Specifications, click the Add icon.

5. Enter a name and description for the File Specification.

   Tip:

   Include the lifecycle stage in the name to make it visible in the Detected Files tab.

6. File Name: Enter a regular expression for the names of files to be loaded in each lifecycle stage.

   File name patterns use the POSIX standard Extended Regular Expression syntax. An asterisk (*) in POSIX syntax matches zero or more occurrences of the preceding character. A dot (.) means "any single character." You can use .* to mean "any character or no characters."

   For example, in a study with file input models for three labs, you could use the following file specifications that allow for a date and the lab name:

   • CentralLab_.*.zip
   • SpecialLab_.*.cport
   • LocalLab_.*.zip

   Tips:

   File names must be unique across all models in the study.

   Be careful about case sensitivity. Include the lab or source name.

   For more information, see https://docs.oracle.com/cd/B28359_01/server.111/b28286/ap_posix001.htm.

7. Lifecycle: Select Development, Quality Control, or Production.

8. Select the Submission Mode:

   • Incremental: The system loads all data in the file, inserting new records, updating records with changes, and refreshing the timestamps of records that are reloaded without change. It does not delete any records.
   • Full: The system inserts, updates, and refreshes reloaded records as in incremental processing and in addition, compares the unique keys of records in the file to existing records and deletes any records that are not included in the file.
   • UOW Load: Within each Unit of Work (subject or subject visit) that has any new or changed records, the system processes all records, inserting new records, updating records with changes, and refreshing the timestamps of records that are reloaded without change. The system does not process records for units of work that have no new or changed records. The system deletes any existing records that are not reloaded within processed units of work. It does not delete records that are not present in the source if no other records from the same unit of work are reloaded.

     Tip:

     Create two File Specifications, one for a frequent incremental or UOW load and another for a less frequent full load. Incremental loads are faster and can be run on a subset of data. Full loads are more time-consuming but they detect when to delete data. Be careful to always load the complete set of current data when you use full processing; see Data processing types and modes.

     Use a different file name for incremental/UOW and full loads.

9. Execution Priority: The priority for loading data with this File Specification relative to others: Low, Normal, or High.

10. Select the Dataload Type:

    • Immediate: The Watcher searches for files continuously.
    • Scheduled: The Watcher searches at the interval you specify.

11. Frequency: If you selected Scheduled, select a frequency for the Watcher to look for a new data file in days, hours, or minutes.

12. Start Date: If you selected Scheduled, enter the date and time for file watching to begin.

13. End Date: Enter the date and time for file watching to end. You can enter a date far in the future and change it at any time.

14. Click OK.

Next: Install a clinical data model or, if the data source is a clinical data capture system other than InForm, Configure the web service location for a source data system.