Ebola haemorrhagic fever outbreak in Masindi District, Uganda: outbreak description and lessons learned
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
BACKGROUND: Ebola haemorrhagic fever (EHF) is infamous for its high case-fatality proportion (CFP) and the ease with which it spreads among contacts of the diseased. We describe the course of the EHF outbreak in Masindi, Uganda, in the year 2000, and report on response activities. METHODS: We analysed surveillance records, hospital statistics, and our own observations during response activities. We used Fisher's exact tests for differences in proportions, t-tests for differences in means, and logistic regression for multivariable analysis. RESULTS: The response to the outbreak consisted of surveillance, case management, logistics and public mobilisation. Twenty-six EHF cases (24 laboratory confirmed, two probable) occurred between October 21st and December 22nd, 2000. CFP was 69% (18/26). Nosocomial transmission to the index case occurred in Lacor hospital in Gulu, outside the Ebola ward. After returning home to Masindi district the index case became the origin of a transmission chain within her own extended family (18 further cases), from index family members to health care workers (HCWs, 6 cases), and from HCWs to their household contacts (1 case). Five out of six occupational cases of EHF in HCWs occurred after the introduction of barrier nursing, probably due to breaches of barrier nursing principles. CFP was initially very high (76%) but decreased (20%) due to better case management after reinforcing the response team. The mobilisation of the community for the response efforts was challenging at the beginning, when fear, panic and mistrust had to be countered by the response team. CONCLUSIONS: Large scale transmission in the community beyond the index family was prevented by early case identification and isolation as well as quarantine imposed by the community. The high number of occupational EHF after implementing barrier nursing points at the need to strengthen training and supervision of local HCWs. The difference in CFP before and after reinforcing the response team together with observations on the ward suggest a critical role for intensive supportive treatment. Collecting high quality clinical data is a priority for future outbreaks in order to identify the best possible FHF treatment regime under field conditions.
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.
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,001 | 0,001 |
| É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,001 | 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écoule