<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="4284" 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/4284?output=omeka-xml" accessDate="2026-04-17T04:26:04+00:00">
  <fileContainer>
    <file fileId="4284">
      <src>https://www.socictopen.socict.org/files/original/7f5288b8fe3024bb361f7b1208470fd5.pdf</src>
      <authentication>a150bbddc11296c487022a2e1b8d8187</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="39076">
              <text>Assisting beginners in root cause analysis operations: analysis and recommendations regarding the spread of COVID-19 in nursing facilities for the elderly</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="39077">
              <text>Hitoshi Tsuchiya</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="39078">
              <text>Background To analyse a medical accident, much time and experience are needed. However, people without experience in analysis have difficulty understanding its conditions and methods, and as a result it takes longer to establish countermeasures. It must be noted that understanding conditions by simply aligning occurrences in the accident in a chronological order is difficult.Purpose A workflow chart that considers time was proposed so that individuals without adequate experience in analysis could easily carry out root cause analysis.Methods In the ‘workflow chart (WFC)’, the time sequence was described horizontally. On the vertical axis, the business manual, the occurrence of the accident, and the time of the occurrence are displayed. In the bottom column of patient event, information regarding damage to patients was written in accordance with time axis. Regarding the degree of damage, the time of error until the accident was identified was connected using a straight line (when the patient was not affected, a dotted line was used) in order to show the overall picture of the accident.Results According to the time flow chart, hints to identify potential risks were proposed. Focus was placed not only on the error event, but also on keywords such as manual inadequacy, time gap, degree of error and so on to easily lead to the question ‘why?’ To visualise this, I proposed an operation flow chart. By using time-WFC, even beginners can easily develop accident countermeasure strategies.Conclusion Using a WFC that considers time, time of error and the occurrence of accident could be visualised. As a result, even individuals without experience in analysis could easily perform an analysis.</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="39079">
              <text>2020</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="39080">
              <text>10.1136/bmjoq-2020-000960</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="39081">
              <text>Epidemiology and Health</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="39082">
              <text>Korean Society of Epidemiology</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="39083">
              <text>Medicine (General)</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
