Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
2-surveillance-components [2018/07/31 16:11] thorsten |
2-surveillance-components [2018/08/01 16:04] (current) thorsten |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{/file/view/info.png/549117566/42x42/info.png|info.png}}**__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).\\ \\ {{/file/view/risksur.jpg/549117584/66x31/risksur.jpg|risksur.jpg}}**__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:\\ \\ | + | {{:files:info.png?nolink&50 |}}**__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).\\ \\ {{:files:risksur.jpg?nolink&50 |}}**__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:\\ \\ |
| - | * Being directed against __one specific hazard__. While it is recognized that some surveillance activities support the detection of multiple hazards (for example clinical surveillance, post-mortem and abattoir inspections), the framework supports the design of surveillance one hazard at a time. Activities that support multiple hazards should be listed, and can then be “reused” when designing surveillance systems targeting other hazards. Please refer to section [[/Multi-hazard%20surveillance|Multi-hazard surveillance]] for a multiple hazard surveillance description. | + | * Being directed against __one specific hazard__. While it is recognized that some surveillance activities support the detection of multiple hazards (for example clinical surveillance, post-mortem and abattoir inspections), the framework supports the design of surveillance one hazard at a time. Activities that support multiple hazards should be listed, and can then be “reused” when designing surveillance systems targeting other hazards. Please refer to section [[/Multi-hazard-surveillance|Multi-hazard surveillance]] for a multiple hazard surveillance description. |
| * Targeting __one specific animal population__, which can be defined at the species level (for example chickens) or target sector (p.e. layers), as long as all characteristics listed below to define a component are the same. | * Targeting __one specific animal population__, which can be defined at the species level (for example chickens) or target sector (p.e. layers), as long as all characteristics listed below to define a component are the same. | ||
| * __A specific data source__ (sampling point and case definition). | * __A specific data source__ (sampling point and case definition). | ||
| Line 9: | Line 9: | ||
| \\ 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:\\ \\ | \\ 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 ===== | ===== 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.\\ \\ | + | 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 ===== | ===== 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.\\ \\ | + | 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 ===== | ===== 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.\\ \\ | + | 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 ===== | ===== 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:\\ | 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:\\ | ||
| Line 25: | Line 25: | ||
| * markets | * markets | ||
| * others | * others | ||
| - | \\ | ||
| ===== 2.5. Study type ===== | ===== 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:\\ | 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:\\ | ||
| Line 37: | Line 36: | ||
| * **Syndromic surveillance:** Surveillance that uses health-related information (clinical signs or other data) that might precede or substitute for formal diagnosis. This information may be used to indicate a sufficient probability of a change in the health of the population to deserve further investigation or to enable a timely assessment of the impact of health threats which may require action. This type of surveillance is not usually focused on a particular hazard so can be used to detect a variety of diseases or pathogens including new (emerging) diseases. Syndromic surveillance has been used for early detection and also for case detection during outbreaks | * **Syndromic surveillance:** Surveillance that uses health-related information (clinical signs or other data) that might precede or substitute for formal diagnosis. This information may be used to indicate a sufficient probability of a change in the health of the population to deserve further investigation or to enable a timely assessment of the impact of health threats which may require action. This type of surveillance is not usually focused on a particular hazard so can be used to detect a variety of diseases or pathogens including new (emerging) diseases. Syndromic surveillance has been used for early detection and also for case detection during outbreaks | ||
| * **Other** | * **Other** | ||
| - | \\ | ||
| ===== 2.6. Type of disease indicator ===== | ===== 2.6. Type of disease indicator ===== | ||
| In the surveillance framework, the following are listed:\\ | In the surveillance framework, the following are listed:\\ | ||
| Line 47: | Line 45: | ||
| * indirect indicators | * indirect indicators | ||
| * other | * other | ||
| - | \\ | ||
| ===== 2.7. Type of sample collected ===== | ===== 2.7. Type of sample collected ===== | ||
| In the surveillance framework, the following are listed:\\ | In the surveillance framework, the following are listed:\\ | ||
| Line 63: | Line 60: | ||
| * meat juice | * meat juice | ||
| * environmental sample | * environmental sample | ||
| - | * other swab (not fecal) | + | * other swab (not fecal)\\ \\ |
| - | \\ | + | |
| - | | [[/home|{{ :files:home.png?nolink&200 |}}]]\\ | [[/Design-surveillance|{{ :files:survDESIGN.png?nolink&200 |}}]]\\ | [[/RE-design-surveillance|{{ :files:SurvREdesign.png?nolink&200 |}}]]\\ | [[/Multi-hazard-surveillance|{{ :files:multihazard.png?nolink&200 |}}]]\\ | [[/RISKSUR-project-information-and-files|{{ :files:risksur.jpg?nolink&200 |}}]]\\ | [[{{ :files:RISKSUR_SurvDesFramework_PublicDRAFT.xlsm|{{ :files:ExcelTool.png?nolink&200 |}}]]\\ | [[/Examples|{{ :files:examples.png?nolink&200 |}}]]\\ | [[/Guided-tour-surveillance-objective-specific-road-maps|{{ :files:guidedTours.png?nolink&200 |}}]]\\ | [[/Glossary|{{ :files:glossary.png?nolink&200 |}}]]\\ | [[/References|{{ :files:references.png?nolink&200 |}}]]\\ | | + | | [[/start|{{ :files:home.png?nolink&200 |}}]]\\ | [[/Design-surveillance|{{ :files:survDESIGN.png?nolink&200 |}}]]\\ | [[/RE-design-surveillance|{{ :files:SurvREdesign.png?nolink&200 |}}]]\\ | [[/Multi-hazard-surveillance|{{ :files:multihazard.png?nolink&200 |}}]]\\ | [[/RISKSUR-project-information-and-files|{{ :files:risksur.jpg?nolink&200 |}}]]\\ | [[{{ :files:RISKSUR_SurvDesFramework_PublicDRAFT.xlsm|{{ :files:ExcelTool.png?nolink&200 |}}]]\\ | [[/Examples|{{ :files:examples.png?nolink&200 |}}]]\\ | [[/Guided-tour-surveillance-objective-specific-road-maps|{{ :files:guidedTours.png?nolink&200 |}}]]\\ | [[/Glossary|{{ :files:glossary.png?nolink&200 |}}]]\\ | [[/References|{{ :files:references.png?nolink&200 |}}]]\\ | |
| \\ | \\ | ||
| | [[/1-Surveillance-system|{{ :files:previous.png?nolink&200 |}}]]\\ | [[/3-Target-population|{{ :files:next.png?nolink&200 |}}]]\\ | | | [[/1-Surveillance-system|{{ :files:previous.png?nolink&200 |}}]]\\ | [[/3-Target-population|{{ :files:next.png?nolink&200 |}}]]\\ | | ||