Managing data flow

Aim

To describe how to manage data streams through a database system for projects with complex and/or large-scale data streams.

 

Requirements

  • To test the administrative database on proper functioning;
  • To provide instructions to those who will be working with the database.

 

Documentation

  • A schematic overview of the data logistics;
  • A list of persons who have access to the administrative database (including the Data Management department);
  • A copy of the privacy form of all persons who have access to the database.

 

Responsibilities

Executing researcher: In case of complex and/or large-scale data streams:
  • To create an administrative database in consultation with the Data Management department;
  • To test this database;
  • To provide instructions how to use the database to research assistants/other users.
Project leaders: In case of complex and/or large-scale data streams:
  • To ensure that the executing researcher
    • Creates an administrative database in consultation with the Data Management department;
    • Tests this database;
    • Instructs research assistant(s)/other users how to use the database.
Research assistant: To get instruction of the executing researcher how to use the administrative database.

 

How To

For sending out questionnaires, producing labels, documenting names, addresses etc. it is helpful to create an administrative database. In general, an administrative (Access) database will only be required when data streams are complex and/or large-scale. Otherwise it is just as easy to manage your administration in Word or Excel, as creating a database would proportionately cost too much time. An administrative database is not used to input registration forms and questionnaires.
An administrative database is used to monitor and manage the data flow during the data collection process in a research project. Databases such as these are used, for instance:
  • To send out questionnaires (surveys or e-mail links) at particular points in time to research participants
  • To send out reminders when questionnaires are not returned on time.
  • To generate reminders for invitations for a visit.
Variables will partly need to be entered manually, when something arrives, or automatically by the computer, when something needs to be sent and has been sent. Variables that are often incorporated in an administrative database are, among others:
  • Name,
  • Address,
  • Clinician, like general practitioner or doctor,
  • Calendar dates on which a specific questionnaire or registration form was sent and received or a visit took place.
The administrative database is usually created and programmed by the Data Management department. A “standard” database is used and can be tailored to the projects’ configuration. Costs for this will be outlined in a quote for the work and are charged to the research project (for more information about this process, please refer to the Information Analysis guideline).
Before an administrative database can be created, it is necessary for the researcher to provide a schematic overview of the data logistics. In this overview, the time points and associated conditions for sending out information to the research participants and/or general practitioners (for instance), are described in columns. Furthermore, the overview should also contain information what needs to be imported into the database at that point in time, manually or automatically (for instance questionnaires). Click here for example of such a diagram.
Once the administrative database has been designed, the researcher has to test the database for errors by entering a number of fictional respondents into the administrative database. This is important, for example, to investigate whether respondents will be sent their questionnaires on time. Once the database has passed these tests, the administrative database will be installed on one of the network drives in a project folder to be created by the local ICT department. Support and administrative staff associated with projects and the principal researcher are authorised to add, amend and/or view the data. This may only be undertaken once the confidentiality agreement has been signed (refer to storage of research data and privacy/security aspects). The daily user(s) of the administrative database will receive instructions from the developer on how to use it.

 

Appendices/references/links

 

Audit questions

(Only applicable if an administrative database is used. The guideline Information Analysis describes the potential need for an administrative database).
  1. Has the administrative database been tested by the researcher?
  2. Has the daily user received instructions from the developer in using the administrative database?

 

V4.0: 16 Dec 2016: Text updated
V3.0: 16 July 2015: Revision format and text updated
V 2.1: 1 Jan 2010: English translation
V 2.0: 27 May 2009: Text updated
V 1.0: 29 Nov 2006: Text updated