PHIN Preparedness: Outbreak Management
Notice bibliographique
Résumé
As a result of the response to 9/11 and the subsequent anthrax attacks, CDC and its partners needed to collect a huge amount of case and specimen data. At that time CDC was faced with this requirement but had no standardized tools available to aid with these investigations. Outbreak Management (OM) is the PHIN functional area intended to support the needs of investigation, monitoring, management, analysis, and reporting of a public health event or act of bioterrorism. This presentation will give an overview of requirements for outbreak management systems that have been defined by the CDC and reviewed and refined with input from local and state public health subject matter experts, as well as demonstrate an application, the Outbreak Management System, that was developed for use in public health investigations that support these requirements. OM aids in the collection and analysis of data to support identifying and containing the outbreak. OM systems should be configurable to meet the needs of different types of outbreaks, and capture data related to cases, contacts, investigations, exposures, relationships, clinical and environmental specimens, laboratory results, vaccinations and treatments, travel history, and conveyance information. One clearly stated need is to have an application that allows for the definition and creation of new objects during the course of an investigation. Central to the functionality of a system supporting OM is the ability to collect data related to possible cases and exposures and to create traceable links between all appropriate entities. By tracing the mechanism of transmission and identifying the source of the outbreak, the appropriate outbreak response staff can more effectively contain the event. Systems supporting OM should also be integrated with early event detection, countermeasure administration, laboratory, and surveillance systems to achieve the primary goal of managing the response to and mitigating the effects of an outbreak. Unless standardized data can be exchanged and linked with other appropriate data (i.e., laboratory data) across public health during public health investigations, public health will not be able to adequately assess the source, methods of transmission, agents, and intervention strategies required for management of outbreaks. Without these data, delays will result in determining the affected and potentially exposed population. The SARS outbreak in Toronto and the MonkeyPox response in the U.S. illustrated the distinct needs to have systems with the ability to trace people possibly exposed to a person ill with a communicable disease, trace exposures to a disease vector including physical locale, or follow theoretical paths of conveyance via specific plane flights. These contact tracing capabilities can be efficiently tracked by systems such as the CDC’s Outbreak Management System (OMS). OMS manages complex relationships tracks linkages and provides public health officials with the ability to know who to investigate, manage and either prophylax or treat. As with all preparedness systems, outbreak management systems must be implemented and regularly used before an event, and be adaptable to handle emergency situations when they occur.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».