<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="899" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="http://socictopen.socict.org/items/show/899?output=omeka-xml" accessDate="2026-06-10T19:53:50+00:00">
  <fileContainer>
    <file fileId="899">
      <src>http://socictopen.socict.org/files/original/0854dc139d9680dff0860fac394f4fb5.pdf</src>
      <authentication>e210981be8e90eda6a47a6e4dc1fceae</authentication>
    </file>
  </fileContainer>
  <collection collectionId="1">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1">
                <text>Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2">
                <text>Dominio científico: Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="8511">
              <text>Calculating the potential for within-flight transmission of influenza A (H1N1)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="8512">
              <text>Blower Sally, Coburn Brian J, Wagner Bradley G</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="8513">
              <text>Abstract Background Clearly air travel, by transporting infectious individuals from one geographic location to another, significantly affects the rate of spread of influenza A (H1N1). However, the possibility of within-flight transmission of H1N1 has not been evaluated; although it is known that smallpox, measles, tuberculosis, SARS and seasonal influenza can be transmitted during commercial flights. Here we present the first quantitative risk assessment to assess the potential for within-flight transmission of H1N1. Methods We model airborne transmission of infectious viral particles of H1N1 within a Boeing 747 using methodology from the field of quantitative microbial risk assessment. Results The risk of catching H1N1 will essentially be confined to passengers travelling in the same cabin as the source case. Not surprisingly, we find that the longer the flight the greater the number of infections that can be expected. We calculate that H1N1, even during long flights, poses a low to moderate within-flight transmission risk if the source case travels First Class. Specifically, 0-1 infections could occur during a 5 hour flight, 1-3 during an 11 hour flight and 2-5 during a 17 hour flight. However, within-flight transmission could be significant, particularly during long flights, if the source case travels in Economy Class. Specifically, two to five infections could occur during a 5 hour flight, 5-10 during an 11 hour flight and 7-17 during a 17 hour flight. If the aircraft is only partially loaded, under certain conditions more infections could occur in First Class than in Economy Class. During a 17 hour flight, a greater number of infections would occur in First Class than in Economy if the First Class Cabin is fully occupied, but Economy class is less than 30% full. Conclusions Our results provide insights into the potential utility of air travel restrictions on controlling influenza pandemics in the winter of 2009/2010. They show travel by one infectious individual, rather than causing a single outbreak of H1N1, could cause several simultaneous outbreaks. These results imply that, during a pandemic, quarantining passengers who travel in Economy on long-haul flights could potentially be an important control strategy. Notably, our results show that quarantining passengers who travel First Class would be unlikely to be an effective control strategy.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="8514">
              <text>2009</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="8515">
              <text>DOI: 10.1186/1741-7015-7-81</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="8516">
              <text>BMC Medicine</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="8517">
              <text>BMC</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="8518">
              <text>Medicine</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="8519">
              <text>EN</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
