<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="2328" 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="https://www.socictopen.socict.org/items/show/2328?output=omeka-xml" accessDate="2026-04-18T17:00:57+00:00">
  <fileContainer>
    <file fileId="2328">
      <src>https://www.socictopen.socict.org/files/original/a6ba61647fbf3386e08e2137bdce517a.pdf</src>
      <authentication>68e4dee71ca482a338ea2cf43000e0d7</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="22383">
              <text>An analysis of hospital preparedness capacity for public health emergency in four regions of China: Beijing, Shandong, Guangxi, and Hainan</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="22384">
              <text>Huang Jianshi, Li Xingming, Zhang Hui</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="22385">
              <text>Abstract Background Hospital preparedness is critical for the early detection and management of public health emergency (PHE). Understanding the current status of PHE preparedness is the first step in planning to enhance hospitals' capacities for emergency response. The objective of this study is to understand the current status of hospital PHE preparedness in China. Methods Four hundred hospitals in four city and provinces of China were surveyed using a standardized questionnaire. Data related to hospital demographic data; PHE preparation; response to PHE in community; stockpiles of drugs and materials; detection and identification of PHE; procedures for medical treatment; laboratory diagnosis and management; staff training; and risk communication were collected and analyzed. Results Valid responses were received from 318 (79.5%) of the 400 hospitals surveyed. Of the valid responses, 264 (85.2%) hospitals had emergency plans; 93.3% had command centres and personnel for PHE; 22.9% included community organisations during the training for PHE; 97.4% could transport needed medical staff to a PHE; 53.1% had evaluated stockpiles of drugs; 61.5% had evaluated their supply systems; 55.5% had developed surveillance systems; and 74.6% could monitor the abnormity(See in appendix). Physicians in 80.2% of the analyzed hospitals reported up-to-date knowledge of their institution's PHE protocol. Of the 318 respondents, 97.4% followed strict laboratory regulations, however, only about 33.5% had protocols for suspected samples. Furthermore, only 59.0% could isolate and identify salmonella and staphylococcus and less than 5% could isolate and identify human H5N1 avian flu and SARS. Staff training or drill programs were reported in 94.5% of the institutions; 50.3% periodically assessed the efficacy of staff training; 45% had experts to provide psychological counselling; 12.1% had provided training for their medical staff to assess PHE-related stress. All of the above capacities related to the demographic characteristics of hospitals and will be discussed in-depth in this paper. Conclusion Our survey suggested that, at the time of the survey, hospital preparedness for PHE in China was at an early stage of development. Comprehensive measures should be taken to enhance hospital capacity in the prevention and management of PHE.</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="22386">
              <text>2008</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="22387">
              <text>DOI: 10.1186/1471-2458-8-319</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="22388">
              <text>BMC Public Health</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="22389">
              <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="22390">
              <text>Public aspects of medicine</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="22391">
              <text>EN</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
