Potential Zika virus spread within and beyond India
Notice bibliographique
Résumé
As of 28 October 2018, 147 cases of Zika virus disease (ZVD) have been reported in Jaipur, the capital of Rajasthan state, India.1 Subsequently, as of 2 November 2018, a single case was reported in the neighbouring state of Gujarat and three additional cases were reported in the state of Madhya Pradesh, demonstrating national spread of ZVD and marking the largest reported outbreak of ZVD in Indian history.1 State health departments in India have mobilised hundreds of medical personnel to perform emergency screenings for ZVD.1 As a major tourist attraction for domestic and foreign visitors, the outbreak in Jaipur presents a high risk of Zika virus exportation. To anticipate the potential spread of ZVD in the face of an ongoing outbreak in Jaipur, we determined temporally explicit air travel connectivity with Jaipur and the corresponding seasonal environmental suitability for Zika virus transmission in domestic and international destination cities. We ranked destination cities based on their arriving volume of travellers on commercial flights from Rajasthan for November, December and January using passenger-level, full-route, flight itinerary data from the International Air Transport Association (IATA) for the year 2017. We delineated suitability for transmission of Zika virus in India and Southeast Asia using distribution models of the virus’s primary mosquito vector Aedes aegypti and secondary vector Aedes albopictus limited by the well-characterised temperature thresholds for the genetically similar dengue virus for November, December and January.2 Each month, top ranking domestic and international cities were subsequently filtered by connectivity to include only those cities located within 200 km of areas suitable for Zika virus transmission. Over this 3-month period, 326 cities that were within 200 km of areas suitable for Zika virus transmission received a total of 740,232 passengers from Rajasthan (summarised for December in Figure 1). Of these passengers, approximately 94% travelled to cities within India (n = 696,753). Mumbai received the most passengers (>24%), with Delhi, Bengaluru and Kolkata ranking second, third and fourth, respectively, across all 3 months. Bangkok, Muscat and Singapore were the only international cities ranked in the top 20 destinations. Number of passengers arriving from Rajasthan state (highlighted in red) by air for cities within 200 km of any Zika suitable area estimated for December. Proportion of total outbound passengers from Rajasthan provided in parentheses. Case counts for Jaipur are reported as of 2 November 2018.1 Given the abundance of regions that are predicted to support Zika virus transmission and have large populations with limited previous exposure, and thus limited immunity, to Zika virus, Indian cities and countries with close international connections to Jaipur should prepare for potential importations of Zika virus. Our results suggest a greater risk of domestic spread from Jaipur within India in the upcoming months but relatively lower potential for international exportation and spread. Notably, the city of Chennai may be especially vulnerable given relatively high connectivity to Rajasthan, a large urban population (>7 million), and conditions conducive to year-round transmission of Zika virus via Ae. aegypti. If not controlled, the ZVD outbreak in Jaipur could have far-reaching consequences,3,4 and public health and clinical personnel in domestic and global areas connected to the current epidemic should remain vigilant for possible importation of ZVD cases. We thank Kieran Petrasek, Hernan Acosta, Deepit Bhatia, Andrea Thomas-Bachli, Mariana Torres, and Ashleigh Tuite for their contributions to the study design and data collection for this work. Centers for Disease Control and Prevention (Grant no. USG CK000433-01).
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 machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,005 |
| 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,003 | 0,001 |
| Communication savante | 0,002 | 0,003 |
| Science ouverte | 0,001 | 0,001 |
| Intégrité de la recherche | 0,017 | 0,014 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,008 | 0,002 |
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 source (Gemma direct ou Codex distillé), 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 ».