Selecting Batch Data Format as the output type will result in the creation of a single comma delimited file, as shown below.
Batch Data files can be imported into a MACRO database using the Batch Data Loading Module. When saving in Batch Data format the Query Module used to save dates in the format of the regional settings of the machine on which you are running the software, not the format of the originating questions. This has been changed, so date responses are now saved in their original format. This means that response data exported by the Query Module in Batch Data format can now be fully imported by the Batch Data Loading module.
When saving the output in the OUTPUT section, you are prompted to enter the name of the Batch Data file.
The default name is StudyName_YYYYMMDDBatchData.csv
|
Field Name |
Field Type |
Mandatory/Optional |
|
Clinical Trial Name |
Text 15 |
Mandatory |
|
Site |
Text 8 |
Mandatory |
|
Subject Id |
Long |
Optional with Subject Label |
|
Subject Label |
Text 50 |
Optional with Subject Id |
|
Visit Code |
Text 15 |
Mandatory |
|
Visit Cycle Number |
Integer |
Optional with Visit Cycle Date |
|
Visit Cycle Date |
Text 10 |
Optional with Visit Cycle Number |
|
eForm Code |
Text 15 |
Mandatory |
|
eForm Cycle Number |
Integer |
Optional with eForm Cycle Date |
|
eForm Cycle Date |
Text 10 |
Optional with eForm Cycle Number |
|
Question Code |
Text 15 |
Mandatory |
|
RepeatNumber |
Integer |
Mandatory |
|
Response |
Text 255 |
Mandatory |
|
User Name |
Text 20 |
Optional (this field can be missing) |
Each CR/LF terminated row within a Batch Data File is a single Batch Response.
Note that when a Batch Response File is imported into Batch Data Loading’s Response Buffer, the following changes are made:
Clinical Trial Name is converted to ClinicalTrialId
Visit Code is converted to VisitId
eForm Code is converted to CRFPageId
Question Code is converted to DataItemId
And an additional field UploadMessage Text 255 is added