Table of Contents

General information and advice: Within a surveillance system, several surveillance activities can be implemented, which can be separated into surveillance components(Hoinville et al., 2013).

Framework details: Extensive discussions have been carried out within the RISKSUR consortium in order to define the scope of a surveillance component. In practice, the identification of unique surveillance components can vary according to the level of details needed. For instance “serological surveys in poultry” can be seen as a single component if the “target population” is defined simply as “poultry”, but it can appear as multiple components if the target population is detailed based in the target species, breaking it down into, for instance, “serological surveys in domestic chickens” and “serological survey in domestic ducks”. For the purpose of the RISKSUR surveillance design framework, a surveillance component was defined as a surveillance activity which is characterized by:


Within the RISKSUR design framework a surveillance designer is encouraged to first think about all surveillance components that are/will be part of the surveillance system, and list them to have an overview. The next steps of surveillance design then focus on each of these components at a time.
Data collection is generally the most resource consuming step of surveillance implementation, and therefore it is the driver of the surveillance design. Based on this assumption, it is expected that some methods of data collection (such as sample collection) are already in place or planned to be performed, and surveillance will be designed around those methods. This is the motivation behind starting the design process by listing the expected surveillance components, based on a few key characteristics:

2.1. Target species

Animal species (or animal group or even other materials) which will be sampled for active surveillance. On the framework, based on the definition above, users can only add one species per component (each surveillance component should be defined for one species at a time). If multiple species will be targeted in the surveillance, the surveillance designer should add more surveillance components.

2.2. Target sector

From among the species or categories selected above, the designer should consider whether surveillance will focus on a particular sector. Multiple sectors per component, however, the design must be the same for all sectors. If for instance sampling will differ between sectors, one should consider increasing the number of components and designing one component for each sector.

2.3. Geographical area

What is the geographical area covered by this specific activity, in relation to the total area the surveillance system covers (defined at the surveillance system level)? It can be, for instance, “entire region” or specific areas. Designers should at this point consider the entire area covered by the activity. Any differences in sample allocation due to varied risk in different regions will be addressed later in the framework.

2.4. Data collection point

It refers to where your units can be reached, and therefore where samples will be collected. At this stage the designer should consider the availability of an accurate sampling frame. If it is not possible to identify and locate farms/herds/flocks, it should be considered where animals can be located and sampled. In the surveillance framework, the following are listed:

2.5. Study type

There are various criteria that can be used to classify types of surveillance study, these are the options that we have used within the surveillance framework:

2.6. Type of disease indicator

In the surveillance framework, the following are listed:

2.7. Type of sample collected

In the surveillance framework, the following are listed: