1. Creating Data Entry Screens in Epi Info
Module 2 Sessions 3 & 4

2. Double Data Entry Why use Double Data Entry? Data Compare Utility
Data Quality Assurance
Easy method of checking data entry
Data Compare Utility
Easy to use
Free with Epi-Info
In small groups spend 20 mins. discussing pros and cons of DDE

3. Overview
In this session we demonstrate how to create data entry screens
Data types
Field size
Required fields
Field names
Legal values
Ranges
Titles and Labels

4. Learning Objectives To design data capture screens
To recognise the type of each variable in a dataset
To create controls for entry of each variable in the dataset
To add code for automatic skips
To test the data entry screens by entering a simple dataset

5. Make View Programme Use Make View from the main Epi Info screen
First make a new project File -> New
Name the view – a table is created within the project file to match the view
Blank screen to work on – with or without a grid

6. Labels and Titles Right-click on the screen – goes to Field Definition
Enter the text for the title or label
Change the field type to Label/Title
Change the font (size or style) as required
The label can be dragged around the screen using the mouse

7. Defining Variables/fields
Right click on the screen in the desired location (as with labels, fields can be moved afterwards)
Type the prompt – e.g. Household ID
Select the field type – e.g. Text or Number
A field name is automatically generated – this can be changed by typing in the Field Name box (recommended)

8. Field Size
For Number fields define the Pattern – default is ## (i.e. 2 digits). Define pattern according to the expected data – are you expecting decimals?
For text fields specify the maximum number of characters allowed in the field

9. Validation Options
Required – Checking this option will prevent the user from leaving the field blank – this is recommended for the unique identifier
Repeat Last – This option will automatically bring the contents of the field from the previous record into the current one – not generally recommended
Read Only – This option prevents data entry into the field – only generally used for calculated fields

10. Code Tables
Legal Values – Allows a table of possible values to be created, e.g. “Yes”, “No” – data is saved as text
Comment Legal – Similar to Legal values but allows a code to be stored. E.g. 1-Yes, 2-No – Data saved will be the digits but as text, e.g. “1”, “2”
Codes – Allows you to use the same code table that was used for a previous field

11. Entering Coded Data
Comment legal – appears on screen as pull-down list – data as text – “1”, “2”, etc.
Option groups – data stored as text – “Male”, “Female”
Number with a range check – data stored as number – range not shown on screen – options added as labels

12. Variable and Value labels
The variable label is often the question
In Epi-Info this will be the text entered as the Prompt during design
Value labels are labels attached to numeric codes in coded questions
No easy method of adding value labels in Epi-info – implications when transferring to another package
Covered in more detail in Session 6

13. Tab Order
Tab Order controls the sequence in which the cursor moves between fields on the screen
The default order is determined by the vertical position of the field on the screen
To change the Tab Order go to Edit -> Order of field entry – select the field and use the Up and Down buttons to change the order
Default order will reset if you add extra fields so set the order once the page is complete

14. Creating Skip Patterns
Skips are created by using programming code
Code can be set to run before or after entering data into a field
Programs are produced using View -> Check Code

15. Example Skip Code For example the code
IF S1AQ1=5 THEN
GOTO SPS1AQ1
ELSE
GOTO S1AQ2
END
Set to run after data is entered into the field S1AQ1 causes the cursor to move to SPS1AQ1 if 5 is entered or to S1AQ2 otherwise

16. Building the IF statement

17. Activity 3 & 4
Demonstration of building the data capture screen for data at the individual level
Participants then try this for themselves in the practical session

18. Activity 6 Good Principles of data entry Steps in Data entry
General discussion