Identification and containment of an outbreak of SARS in a community hospital.
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: Severe acute respiratory syndrome (SARS) is continuing to spread around the world. All hospitals must be prepared to care for patients with SARS. Thus, it is important to understand the transmission of this disease in hospitals and to evaluate methods for its containment in health care institutions. We describe how we cared for the first 2 patients with SARS admitted to our 419-bed community hospital in Richmond Hill, Ont., and the response to a SARS outbreak within our institution. METHODS: We collected clinical and epidemiological data about patients and health care workers at our institution who during a 13-day period had a potential unprotected exposure to 2 patients whose signs and symptoms were subsequently identified as meeting the case definition for probable SARS. The index case at our hospital was a patient who was transferred to our intensive care unit (ICU) from a referral hospital on Mar. 16, 2003, where he had been in close proximity to the son of the individual with the first reported case of SARS in Toronto. After 13 days in the ICU, a diagnosis of probable SARS was reached for our index case. Immediately upon diagnosis of our index case, respiratory isolation and barrier precautions were instituted throughout our hospital and maintained for a period of 10 days, which is the estimated maximum incubation period reported for this disease. Aggressive surveillance measures among hospital staff, patients and visitors were also maintained during this time. RESULTS: During the surveillance period, 15 individuals (10 hospital staff, 3 patients and 2 visitors) were identified as meeting the case definition for probable or suspected SARS, in addition to our index case. All but 1 individual had had direct contact with a symptomatic patient with SARS during the period of unprotected exposure. No additional cases were identified after infection control precautions had been implemented for 8 days. No cases of secondary transmission were identified in the 21 days following the implementation of these precautions at our institution. INTERPRETATION: SARS can easily be spread by direct personal contact in the hospital setting. We found that the implementation of aggressive infection control measures is effective in preventing further transmission of this disease.
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,001 | 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écoule