Introduction
This document is intended to be a starting point for anyone who is considering doing mobile data collection. A number of colleagues at LSHTM submitted replies to a question about current practice in this area and this is a collation of their responses and opinions. If you have a more specific question about this area of work they are best addressed to the mailing list:
This list should be used by data managers and researchers to find information and share experience with others involved in similar work. To be added to the list click: https://lists.lshtm.ac.uk/sympa/info/mobile-data-collection
There are regulatory and financial considerations as to how data is collected and researchers should consult relevant staff and the regulator or funding body for advice if necessary in these areas. This document will concentrate largely on technical considerations.
Overview
Most data collection solutions require the user to input questions and design a form. The form will often need to be loaded onto each device being used to conduct the interviews. A master database at the ‘backend’ holds all of the data once uploaded and some hold the data in a temporary state on the collection device, or on an intermediate device (such as a pc or laptop) until uploaded to the master. Configuring this setup will probably require someone who is experienced with either the solution you are using or a similar one, if not an experienced programmer, which will have an associated cost.
The choice of solution will depend on the complexity of the questionnaire/survey you wish to use. For example a form of simple yes/no or other fixed response questions could be handled by most solutions; if consequential questions are required to appear dependent on a response this will require more complex solutions and configuration.
Data is collected on a device (PDA/tablet/mobile phone/laptop or netbook) and either held there or sent, via (mobile) internet, to the database. Some software allows the data to be held on the device temporarily and downloaded (perhaps via a PC/laptop) to the database. The choice of device is often dictated by the software solution but the conditions where data collection will occur should also be considered when choosing a solution.
Consideration should be given to how and where the data is held on devices, any intermediate steps and the master database, depending on the
agreements/regulations associated with the project.
Available Solutions/Software
This is an overview of common data collections solutions. All have pros and cons and the nature of the study will dictate the most appropriate choice.
CSPro (free)
Website: http://www.census.gov/population/international/software/cspro/ Comment: A solid, tried and tested but basic tool. Has limited flexibility as
requires Microsoft Windows. Might be suitable if using laptops for data collection. Uses a web browser. Can’t handle multi-level forms
EpiCollect (free)
Website: http://www.epicollect.net/
Comment: Developed by Imperial College this appears to be another good tool. It runs on Android mobiles/IOS devices and can hold data until a connection is available. It has limited handling of multi-level forms. Download as an app.
ODK (free)
Website: http://opendatakit.org/
Comment: Some say this is easier to configure than Epicollect. Again it requires Android mobile phones. It can deal with some multilevel forms and can hold data on the device to download later, though this requires a second (open source) product. Download as an app.
Pendragon Forms (Licence Required) Website: http://pendragonsoftware.com/
Comment: This would appear the most advanced and flexible of the solutions available, hence the cost. It can deal with a variety of devices
(Android/IOS/Palm) and multi-level forms. The data is exported into a number of formats and is held on the device when no connection is available. Uses device’s web browser.
Commcare (License Required)
Website: http://www.commcarehq.org/
Comment: Free to try but license for significant use. Configuration service available and looks to be based on ODK above so highly flexible. Little used at LSHTM currently but could be promising.
Fax (Associated Cost) Website: Unavailable
Comment: This is less used and appears to be an expensive solution that requires completion of data forms and then faxing them via a provider who can digitize the data. Forms need to be good quality and completed accurately to prevent errors in character recognition. There may be regulatory considerations depending on intermediate providers used.
Bespoke Software (Associated Cost)
It is of course possible to pay a developer to design a bespoke data collection system for your project, using whichever database and device you like. This approach may cause issues and is likely to be a costly option as you would need to make your requirements clear to the developer and this would require some technical knowledge. You would also need to consider how the system was supported throughout the life of the project.
Mobile Devices
When considering which device to use to collect data it’s also worth considering the physical aspects of the device (size, resilience, cost) as well as how easily it can handle your preferred collection software. In an ideal world a device that would only allow data entry would be available but this isn’t the case. Can the device be held securely when not is use? Battery life, ability to recharge, will touchscreen or keypad lead to more accurate data entry?
Consideration should also be give to how the device will get to any intermediate steps or directly to the master database. This is likely to involve a physical cable (USB) connection, wireless or 3G/mobile data capability.
A brief overview of the most common devices:
PDA (Personal Data Assistants) Eg. Palm Pilots – these are an attractive
proposition but few are manufactured any more and the technology is dated, no in-built internet connectivity and download would need to be to a PC/laptop. Consider: screen size, access to support, portability. Fairly resilient models available.
Consider: Screen size, portability,
Tablet – Easily available, variety of costs, available as wireless only or with SIM card/3G, good size screen, less portable, less robust, good if wireless is
available.
Laptop/Netbook – variety of models and costs, more cumbersome than other devices but more flexible, battery life tends to be shorter than other devices, possibly easier to damage in transit. 3G/Wireless models now available.
Conclusion
There is no silver bullet that’s going to present a solution for all scenarios though there are a range of options available that should fit most circumstances. Before deciding on a data collection procedure, even when applying for funding, you are strongly advised to contact your IT Partner or the ITS Helpdesk to discuss the options.
Thanks to all those who shared their experience to make this document possible. Overview of Data Collection on Mobile Devices.
