<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" 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://repository.horizon.ac.id/items/browse?collection=955&amp;output=omeka-xml&amp;page=1" accessDate="2026-04-27T04:17:21+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>43</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="13257" public="1" featured="1">
    <fileContainer>
      <file fileId="13311">
        <src>https://repository.horizon.ac.id/files/original/73d9fa3c735986238c53d1d47a720cdb.pdf</src>
        <authentication>1c0f0e40bf08e25ee92a03c3c04fe22f</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="141002">
                <text>Adapting a novel emergency triage tool to a resource-limited hospital in Nepal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141003">
                <text>Triage, Emergency department, Quality improvement, Nepal, Global health</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141004">
                <text>Abstract&#13;
Background Effective triage is critical for prioritizing emergency care. However, many low- and middle-income&#13;
countries lack standardized triage systems. Nepal has been working to introduce the WHO’s Interagency Integrated&#13;
Triage Tool (IITT) into emergency departments nationwide. Still, successful implementation requires context-specific&#13;
adaptations to address operational realities and resource constraints.&#13;
Objective This study aimed to collaboratively adapt the IITT for use in the Dhulikhel Hospital Emergency Department&#13;
by incorporating frontline staff insights to develop a feasible, sustainable triage workflow.&#13;
Methods Five focus groups composed of doctors, nurses, and paramedics were conducted. Through semi-structured&#13;
discussions, we explored staff perceptions of areas for improvement in the existing triage processes. Participants then&#13;
generated site-specific workflow models through iterative brainstorming sessions, progressively refining the design&#13;
into a final consensus-based model.&#13;
Results Participants, representing over 80% of clinical staff, identified key barriers to effective triage, including&#13;
inconsistent communication, unclear handoff responsibilities, and insufficient training. The final triage workflow&#13;
addressed many critical challenges raised in discussion sessions, provided a standardized and customized triage&#13;
process, and resulted in high reported confidence in its utility.&#13;
Conclusion This study demonstrates the value of a bottom-up, staff-centered approach to triage system&#13;
development and implementation. Our focus group design offers a practical, replicable framework for low-resource&#13;
emergency departments seeking to implement the IITT or similar protocols into their ED operations. Future efforts&#13;
should focus on validating the workflow’s impact on patient outcomes and triage efficiency and investing in&#13;
thorough and longitudinal training to support sustained adoption.&#13;
Keywords Triage, Emergency department, Quality improvement, Nepal, Global health</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141005">
                <text>Yael Weiner1*, Claire Therriault1*, Tina Duwal2&#13;
&#13;
, Samjhana Basnet2&#13;
&#13;
, Roshana Shrestha2&#13;
&#13;
and Sanu Krishna Shrestha2*</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="141006">
                <text>2025</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141007">
                <text>Peri Irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141008">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141009">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141010">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16065">
        <name>Triage, Emergency department, Quality improvement, Nepal, Global health</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12980" public="1" featured="1">
    <fileContainer>
      <file fileId="13035">
        <src>https://repository.horizon.ac.id/files/original/ec0582f1ff22a7f0cb2d2a01f90d3ca1.pdf</src>
        <authentication>ac5f526d2285c463ab5a98dbae14c24e</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138513">
                <text>A direct qualitative content analysis on the&#13;
design, implementation, and evaluation&#13;
of prehospital earthquake exercises aligned&#13;
with the HSEEP framework</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138514">
                <text>Preparedness, Prehospital, Earthquake, Exercise</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138515">
                <text>Abstract&#13;
Introduction Disaster exercises are a vital strategy for enhancing Emergency Medical Services (EMS) operational&#13;
preparedness. This study aimed to extract “Golden Keys” for Design, Implementation and Evaluation of earthquake&#13;
exercises aligning these key components with the internationally recognized Homeland Security Exercise and&#13;
Evaluation Program (HSEEP) Framework from the perspective of experienced Iranian prehospital technicians.&#13;
Method A qualitative study was conducted using a directed content analysis. Data were systematically gathered&#13;
through in-depth semi-structured interviews with 11 prehospital technician that purposefully selected based on their&#13;
demonstrated expertise in prehospital exercise management. Data analysis was conducted in five steps following&#13;
Granheim and Lundman’s approach and the study used Lincoln and Guba’s recommendations to assess data&#13;
trustworthiness.&#13;
Result After multiple rounds of data analysis and summarization 386 initial codes, 13 subcategories, and five main&#13;
categories were identified. These main categories included “Exercise Foundation and Program Governance”, “Exercise&#13;
Design, Coordination, and Control”, “Operational Implementation of the Exercise”, “Performance Evaluation and&#13;
Capability Assessment” and “Learning, Workforce Empowerment”, and “System Improvement”.&#13;
Conclusion Earthquake preparedness exercises must be sustained as an ongoing effort to enhance prehospital&#13;
system resilience. The indicators identified in this study provide an actionable, evidence-based framework for EMS&#13;
managers and policymakers to design, implement, and evaluate exercises aligned with system priorities. Translating&#13;
exercise outcomes into actionable evidence facilitates informed decision-making targeted resource allocation and&#13;
evidence-based policy formulation. Future research should focus on contextualizing this framework within localized&#13;
programs and conducting quantitative validation of the proposed indicators.&#13;
Keywords Preparedness, Prehospital, Earthquake, Exercise</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138516">
                <text>Asiye Aminafshar1&#13;
&#13;
, Ali Moradi Chaleshtori2&#13;
&#13;
, Ali Khosravizad3&#13;
&#13;
, Ali Sahebi3* and Hojjat Farahmandnia4*</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="138517">
                <text>https://doi.org/10.1186/s12245-026-01135-y</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="138518">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138519">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138520">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138521">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138522">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15806">
        <name>Preparedness, Prehospital, Earthquake, Exercise</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12979" public="1" featured="1">
    <fileContainer>
      <file fileId="13034">
        <src>https://repository.horizon.ac.id/files/original/68fd0baff56c8609341d63defff010e0.pdf</src>
        <authentication>e53c2ad327398ec9d21d223f9125f12f</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138503">
                <text>Accuracy of ultrasound for intussusception&#13;
in pediatric emergency presentations:&#13;
&#13;
a systematic review and diagnostic meta-&#13;
analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138504">
                <text>Intussusception, Emergency department, Pediatrics, Surgery, Point-of-care ultrasound</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138505">
                <text>Abstract&#13;
Introduction Intussusception is a common cause of acute abdominal emergencies in children. This systematic&#13;
review and diagnostic meta-analysis aimed to determine the diagnostic accuracy of ultrasound for intussusception&#13;
in pediatric emergency presentations, providing pooled estimates for sensitivity, specificity, predictive values, and&#13;
diagnostic odds ratios to inform clinical practice.&#13;
Methods Adhering to PRISMA-DTA guidelines, a comprehensive search was conducted in PubMed, Scopus,&#13;
Cochrane Library, and Web of Science up to July 2025. Bayesian bivariate random-effects meta-analyses were&#13;
performed to estimate pooled sensitivity, specificity, and other measures, with subgroup and meta-regression&#13;
analyses to explore heterogeneity.&#13;
Results A total of 44 studies comprising 4,142 pediatric patients were included in the quantitative synthesis. The&#13;
pooled sensitivity of ultrasound for diagnosing intussusception was 96.3% (95% credible interval [CrI] 94.9–97.5%),&#13;
and the pooled specificity was 95.7% (95% CrI 93.3–97.5%). The area under the hierarchical summary receiver&#13;
operating characteristic curve (AUC) was 0.81–0.82, indicating good discriminative ability. Positive predictive value&#13;
(PPV) ranged from 54.1% at 5% prevalence to 99.8% at 95% prevalence, while negative predictive value (NPV)&#13;
decreased from 99.8% to 57.7% across the same prevalence range. The overall certainty of evidence for sensitivity and&#13;
specificity was rated as high, with moderate certainty for prevalence due to substantial heterogeneity.&#13;
Conclusion Ultrasound demonstrates excellent diagnostic performance for pediatric intussusception in emergency&#13;
settings, with high sensitivity and specificity maintained across patient subgroups and operator backgrounds. These&#13;
findings support the continued use of ultrasound as the first-line diagnostic modality in both high- and low-resource&#13;
environments and highlight the importance of structured training to optimize its accuracy. Future research should&#13;
focus on multicenter prospective studies, standardization of ultrasound protocols, and the integration of artificial&#13;
intelligence to further enhance diagnostic reliability.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138506">
                <text>Mohammed Alsabri1,2* , Shree Rath3 , Mohamed Amr Elkarargy4&#13;
&#13;
, Amira A. Aboali5&#13;
&#13;
, Khaled Abouelmagd6&#13;
,&#13;
&#13;
Abdelaziz Abdelaziz Abdelftah Ramadan7&#13;
&#13;
, Luis L. Gamboa8&#13;
&#13;
, Patrick Yoo9&#13;
&#13;
and Yisha Cheng9</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="138507">
                <text>https://doi.org/10.1186/s12245-026-01134-z</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="138508">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138509">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138510">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138511">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138512">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15805">
        <name>Intussusception, Emergency department, Pediatrics, Surgery, Point-of-care ultrasound</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12978" public="1" featured="1">
    <fileContainer>
      <file fileId="13033">
        <src>https://repository.horizon.ac.id/files/original/1bb1d009071e1fc89d112b7382021d29.pdf</src>
        <authentication>106b2b3be19f35c86892834ba87f5637</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138493">
                <text>Effectiveness of a flipped classroom model&#13;
for enhancing emergency physicians’ skills&#13;
in diagnosing high-risk pulmonary embolism&#13;
with point-of-care ultrasound: a randomized&#13;
controlled study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138494">
                <text>Flipped classroom, Point of care ultrasound, High-risk pulmonary embolism</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138495">
                <text>Abstract&#13;
Background High-risk pulmonary embolism is a significant cause of morbidity and mortality in the emergency&#13;
department. Point-of-care ultrasonography is a valuable tool for identifying high-risk pulmonary embolism at the&#13;
bedside, but many physicians lack proficiency. A flipped classroom model may enhance point-of-care ultrasound&#13;
training, but its effectiveness compared to standard teaching remains unclear.&#13;
Methods Emergency physicians and residents at a single academic centre were randomized to either a flipped&#13;
classroom or standard teaching after a baseline assessment of their ability to identify high-risk pulmonary embolism&#13;
using a database of ultrasound clips. The flipped classroom group completed an online module, while the standard&#13;
teaching group attended an in-person seminar. Both groups participated in an in-person workshop and subsequently&#13;
underwent post-training testing. The primary outcome was the difference in final test scores. Statistical analysis&#13;
included Student’s t-test for mean comparisons, while Fisher’s exact test and one-way ANOVA were used to assess&#13;
differences between teaching methods, with significance set at p≤0.05.&#13;
Results A total of 30 participants completed the study (15 in the flipped classroom and 15 in the standard teaching&#13;
&#13;
group). Most (80%) reported low baseline confidence in identifying high-risk pulmonary embolism with point-of-&#13;
care ultrasound. There were no significant differences in baseline scores between the groups (65.0% ± 24.7% for&#13;
&#13;
the flipped classroom vs. 64.3% ± 24.9% for standard teaching, p=0.93). Both groups demonstrated significant&#13;
improvement in scores on final testing (standard teaching: 11% increase, p=0.02; flipped classroom: 7.3% increase,&#13;
p=0.03). However, there was no significant difference in final test scores between the two groups (75.3% ± 20.1% for&#13;
standard teaching vs. 72.3% ± 21.4% for the flipped classroom, p=0.65).</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138496">
                <text>Noman Ali1,2*, Alan Tan2&#13;
&#13;
, Salman Muhammad Soomar1,3, Dominick Shelton2&#13;
&#13;
, Rob Simard2&#13;
&#13;
and Jordan Chenkin2</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="138497">
                <text>https://doi.org/10.1186/s12245-026-01129-w</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="138498">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138499">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138500">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138501">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138502">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12977" public="1" featured="1">
    <fileContainer>
      <file fileId="13032">
        <src>https://repository.horizon.ac.id/files/original/e03a6663b84a4b7870b147d07a3661bd.pdf</src>
        <authentication>6a2a117925ccc62929d45be58c53f631</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138483">
                <text>Blunt trauma-induced abdominal wall hernia&#13;
with small bowel incarceration: case report&#13;
and review of the literature</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138484">
                <text>Traumatic abdominal wall hernia, Blunt trauma, Bowel obstruction, Mesh repair, Case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138485">
                <text>Abstract&#13;
Background Traumatic abdominal wall hernia (TAWH) is a rare sequela of blunt abdominal trauma, characterized&#13;
by disruption of the abdominal musculature and fascia without skin penetration. Diagnosis may be challenging and&#13;
delayed, with complications such as bowel incarceration or strangulation requiring urgent intervention. This report&#13;
describes a TAWH complicated by bowel obstruction, followed by a narrative review of relevant literature.&#13;
Case presentation A 69-year-old male presented with acute abdominal pain, vomiting, and a right flank mass,&#13;
three days after a road traffic accident. Physical examination revealed a tender, irreducible swelling with overlying&#13;
abrasions and ecchymosis. Laboratory results were unremarkable. Contrast-enhanced computed tomography (CT)&#13;
demonstrated an anterior abdominal wall defect containing dilated small bowel loops with features of obstruction&#13;
and possible strangulation. Emergency exploratory laparotomy revealed incarcerated but viable bowel loops within&#13;
a traumatic defect. The loops were reduced, and a preperitoneal mesh repair was performed. Postoperative recovery&#13;
was uneventful, and the patient was discharged on postoperative day 3.&#13;
Conclusion TAWH, though rare, should be suspected in patients with localized swelling after blunt trauma. Prompt&#13;
imaging and timely surgical repair are essential to prevent life-threatening complications.&#13;
Keywords Traumatic abdominal wall hernia, Blunt trauma, Bowel obstruction, Mesh repair, Case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138486">
                <text>Imen Ben Ismail1*, Marwen Sghaier1&#13;
&#13;
, Hakim Zenaidi1&#13;
&#13;
, Houssem Messoudi2&#13;
&#13;
, Saber Rebii1&#13;
&#13;
and Ayoub Zoghlami1</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="138487">
                <text>https://doi.org/10.1186/s12245-026-01127-y</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="138488">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138489">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138490">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138491">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138492">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15804">
        <name>Traumatic abdominal wall hernia, Blunt trauma, Bowel obstruction, Mesh repair, Case report</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12976" public="1" featured="1">
    <fileContainer>
      <file fileId="13031">
        <src>https://repository.horizon.ac.id/files/original/dcbf068a5fe60b266d24fced404f1245.pdf</src>
        <authentication>6f82e5d7e44e5d1c5f872a6cfd494a5d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138473">
                <text>Acute management of spontaneous&#13;
intracerebral hemorrhage (ICH) in the&#13;
emergency department</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138474">
                <text>Acute intracerebral hemorrhage, Blood pressure management, Anticoagulation reversal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138475">
                <text>Background Spontaneous intracerebral hemorrhage (ICH) is a catastrophic form of stroke affecting more than 3.3&#13;
million individuals worldwide each year and accounting for approximately 10–20% of all strokes globally. Although&#13;
less common than acute ischemic stroke, ICH carries a disproportionate burden of morbidity and mortality, with&#13;
30-day case fatality rates approaching 40–50%. Therapeutic advances for ICH have progressed more slowly than&#13;
for ischemic stroke, and management remains largely supportive. Patients frequently present to the emergency&#13;
department (ED) in critical condition, making early recognition and rapid, guideline-concordant intervention essential&#13;
to improving outcomes.&#13;
Review This narrative review summarizes the most recent American Heart Association/American Stroke Association&#13;
(AHA/ASA) guidelines for the acute management of spontaneous ICH, with emphasis on practical ED application.&#13;
Hypertension remains the most important modifiable risk factor, particularly in younger patients, while cerebral&#13;
amyloid angiopathy predominates in older adults. Additional risk factors include anticoagulant and antiplatelet&#13;
therapy, alcohol and illicit drug use, smoking, advanced age, and genetic predisposition. Primary brain injury results&#13;
from hematoma mass effect and elevated intracranial pressure, followed by secondary injury driven by edema,&#13;
inflammation, and oxidative stress. Because hematoma expansion commonly occurs within the first hours after&#13;
symptom onset and strongly predicts mortality, early ED management prioritizes rapid neuroimaging, controlled&#13;
blood pressure reduction, timely anticoagulation reversal, seizure management, metabolic and temperature control,&#13;
and prompt neurosurgical consultation when indicated. Emerging evidence supports bundled, time-sensitive care&#13;
pathways to reduce delays and optimize outcomes.&#13;
Conclusion Optimal ICH outcomes depend on rapid, structured, guideline-concordant ED care focused on limiting&#13;
hematoma expansion and secondary injury. Standardized workflows and bundled interventions represent effective&#13;
strategies for improving survival and functional outcomes while avoiding premature prognostication in the acute&#13;
phase.&#13;
Keywords Acute intracerebral hemorrhage, Blood pressure management, Anticoagulation reversal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138476">
                <text>Madeleine Puissant1 and Latha Ganti2*</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="138477">
                <text>https://doi.org/10.1186/s12245-026-01126-z</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="138478">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138479">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138480">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138481">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138482">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15803">
        <name>Acute intracerebral hemorrhage, Blood pressure management, Anticoagulation reversal</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12975" public="1" featured="1">
    <fileContainer>
      <file fileId="13030">
        <src>https://repository.horizon.ac.id/files/original/f3a16924a291ab58c262d5923e472796.pdf</src>
        <authentication>6f82e5d7e44e5d1c5f872a6cfd494a5d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138463">
                <text>Acute management of spontaneous&#13;
intracerebral hemorrhage (ICH) in the&#13;
emergency department</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138464">
                <text>Acute intracerebral hemorrhage, Blood pressure management, Anticoagulation reversal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138465">
                <text>Background Spontaneous intracerebral hemorrhage (ICH) is a catastrophic form of stroke affecting more than 3.3&#13;
million individuals worldwide each year and accounting for approximately 10–20% of all strokes globally. Although&#13;
less common than acute ischemic stroke, ICH carries a disproportionate burden of morbidity and mortality, with&#13;
30-day case fatality rates approaching 40–50%. Therapeutic advances for ICH have progressed more slowly than&#13;
for ischemic stroke, and management remains largely supportive. Patients frequently present to the emergency&#13;
department (ED) in critical condition, making early recognition and rapid, guideline-concordant intervention essential&#13;
to improving outcomes.&#13;
Review This narrative review summarizes the most recent American Heart Association/American Stroke Association&#13;
(AHA/ASA) guidelines for the acute management of spontaneous ICH, with emphasis on practical ED application.&#13;
Hypertension remains the most important modifiable risk factor, particularly in younger patients, while cerebral&#13;
amyloid angiopathy predominates in older adults. Additional risk factors include anticoagulant and antiplatelet&#13;
therapy, alcohol and illicit drug use, smoking, advanced age, and genetic predisposition. Primary brain injury results&#13;
from hematoma mass effect and elevated intracranial pressure, followed by secondary injury driven by edema,&#13;
inflammation, and oxidative stress. Because hematoma expansion commonly occurs within the first hours after&#13;
symptom onset and strongly predicts mortality, early ED management prioritizes rapid neuroimaging, controlled&#13;
blood pressure reduction, timely anticoagulation reversal, seizure management, metabolic and temperature control,&#13;
and prompt neurosurgical consultation when indicated. Emerging evidence supports bundled, time-sensitive care&#13;
pathways to reduce delays and optimize outcomes.&#13;
Conclusion Optimal ICH outcomes depend on rapid, structured, guideline-concordant ED care focused on limiting&#13;
hematoma expansion and secondary injury. Standardized workflows and bundled interventions represent effective&#13;
strategies for improving survival and functional outcomes while avoiding premature prognostication in the acute&#13;
phase.&#13;
Keywords Acute intracerebral hemorrhage, Blood pressure management, Anticoagulation reversal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138466">
                <text>Madeleine Puissant1 and Latha Ganti2*</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="138467">
                <text>https://doi.org/10.1186/s12245-026-01126-z</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="138468">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138469">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138470">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138471">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138472">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15803">
        <name>Acute intracerebral hemorrhage, Blood pressure management, Anticoagulation reversal</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12974" public="1" featured="1">
    <fileContainer>
      <file fileId="13029">
        <src>https://repository.horizon.ac.id/files/original/f5bc0f7ac4dedca371e2082dabc31fa9.pdf</src>
        <authentication>0ef8fc857b64bd741cebab508a1c6fe1</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138453">
                <text>Designing a model for hospital preparedness&#13;
against chemical weapons of mass&#13;
&#13;
destruction terrorist incidents: a mixed-&#13;
method study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138454">
                <text>Preparedness model, Hospital, Preparedness, Terrorist incidents, Chemical, Weapons of mass destruction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138455">
                <text>Abstract&#13;
Introduction Health systems play a pivotal role in managing chemical weapons of mass destruction (WMD) terrorist&#13;
incidents, particularly in reducing casualties and facilitating crisis management. The growing recognition of the need&#13;
for precise and effective preparedness in these sectors underscores the importance of this research. The present study&#13;
aimed to identify the essential components of hospital preparedness and to develop and validate a comprehensive&#13;
model for hospital readiness in response to chemical WMD terrorist incidents.&#13;
Methods This study was conducted in 2025 using a three-phase exploratory sequential mixed-methods approach.&#13;
First, a scoping review was conducted in accordance with Arksey and O’Malley’s methodological framework and&#13;
the PRISMA guideline to identify key components of hospital preparedness for chemical WMD terrorist incidents.&#13;
Second, a qualitative study was conducted using semi-structured interviews, and the data were analyzed through a&#13;
conventional content analysis approach to further identify preparedness components. Third, the components derived&#13;
from the previous two phases were integrated and validated through two rounds of the Delphi technique. Ultimately,&#13;
a comprehensive hospital preparedness model was developed.&#13;
Results Following integration of the scoping review and qualitative findings by an expert panel, 88 preparedness&#13;
components were identified. After two rounds of the Delphi technique, 82 preparedness components were&#13;
finalized and classified into 16 subcategories and seven main categories: specialized training and empowerment;&#13;
psychological support and ethical considerations; security measures; specialized clinical and therapeutic processes;&#13;
optimal management of surge capacity; integrated information and communication management; and contingency&#13;
strategic management and planning. Finally, based on the Delphi assessment, the proposed preparedness model was&#13;
approved by the expert panel.&#13;
Conclusions Hospitals facing chemical terrorism require a comprehensive preparedness strategy encompassing&#13;
specialized training, psychological support, and robust clinical systems. Effective management, intersectoral</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138456">
                <text>Zoha Dorri1&#13;
, Leila Mohammadinia2,3, Azadeh Fatehpanah1,4, Farzan Madadizadeh5&#13;
&#13;
, AbbasAli Dehghani Tafti1&#13;
and&#13;
&#13;
Samaneh Mirzaei1,6*</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="138457">
                <text>https://doi.org/10.1186/s12245-026-01124-1</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="138458">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138459">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138460">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138461">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138462">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15802">
        <name>Preparedness model, Hospital, Preparedness, Terrorist incidents, Chemical, Weapons of mass destruction</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12973" public="1" featured="1">
    <fileContainer>
      <file fileId="13028">
        <src>https://repository.horizon.ac.id/files/original/25ad5b65c6e4ad16d0d888a28cb8c295.pdf</src>
        <authentication>3685009b49a648f55da7c8346e0ccb5d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138443">
                <text>Severe anaphylaxis following off-label rectal&#13;
use of injectable diazepam in a febrile seizure:&#13;
a case report and clinical implications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138444">
                <text>Febrile seizure, Rectal diazepam, Propylene glycol, Pediatric anaphylaxis, Off-label use, Excipient&#13;
hypersensitivity, Emergency medicine,</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138445">
                <text>Abstract&#13;
Background Off-label rectal administration of intravenous diazepam is commonly practiced for acute seizure&#13;
management in children when FDA-approved rectal gels (e.g., Diastat® AcuDial) are inaccessible—particularly in&#13;
low-resource settings like Vietnam. However, such injectable formulations often contain excipients not validated for&#13;
mucosal use, including propylene glycol and sodium benzoate, which may induce hypersensitivity reactions. Reports&#13;
of anaphylaxis in this context remain exceedingly rare.&#13;
Case presentation We describe a case of suspected grade III anaphylaxis in a 14-month-old girl with complex&#13;
febrile seizure who received 2 mg rectal diazepam (injectable formulation, Vidipha, Vietnam). Within five minutes of&#13;
administration, she developed generalized urticaria, apnea, cyanosis, and hypotonia. Emergency treatment included&#13;
intramuscular epinephrine, corticosteroids, antihistamines, and mechanical ventilation. She made a full recovery. The&#13;
diazepam preparation used contained approximately 40% propylene glycol and also included sodium benzoate—&#13;
both of which have been reported as potential triggers of non–IgE-mediated hypersensitivity reactions, particularly&#13;
when delivered via mucosal routes.&#13;
Conclusion This case underscores the potential for life-threatening adverse events following off-label rectal use of&#13;
injectable diazepam. Emergency clinicians should be aware of excipient-related risks and prioritize safer alternatives&#13;
such as intranasal midazolam. There is an urgent need for regulatory efforts to improve access to mucosal-safe,&#13;
pediatric-appropriate benzodiazepine preparations in resource-limited healthcare systems.&#13;
Keywords Febrile seizure, Rectal diazepam, Propylene glycol, Pediatric anaphylaxis, Off-label use, Excipient&#13;
hypersensitivity, Emergency medicine, Case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138446">
                <text>Ninh Xuan Nguyen1*, Ngoc Tien Pham1&#13;
&#13;
, Huong Thi Thanh Le1&#13;
&#13;
, Quoc Viet Tran1&#13;
&#13;
, Hang Ngoc Thuy Tran1&#13;
,&#13;
&#13;
Thi Kim Thanh Vo1&#13;
&#13;
and Chuong Thi Ngoc Dang2</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="138447">
                <text>https://doi.org/10.1186/s12245-026-01123-2</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="138448">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138449">
                <text>peri </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138450">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138451">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138452">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15801">
        <name>Febrile seizure, Rectal diazepam, Propylene glycol, Pediatric anaphylaxis, Off-label use, Excipient hypersensitivity, Emergency medicine,</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12972" public="1" featured="1">
    <fileContainer>
      <file fileId="13027">
        <src>https://repository.horizon.ac.id/files/original/73ffd661e9ef7c1b22af690d67cdd546.pdf</src>
        <authentication>0ffdc432109e833757985135f7dfe584</authentication>
      </file>
    </fileContainer>
    <collection collectionId="955">
      <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="138073">
                  <text>Volume 19 Issue 1 2026</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="37">
              <name>Contributor</name>
              <description>An entity responsible for making contributions to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="138074">
                  <text>PERI IRAWAN</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="138433">
                <text>Evaluation of immunochromatography-&#13;
based urine drug screening and blood drug&#13;
&#13;
concentrations in suspected acute poisoning:&#13;
insights into negative urine drug screening&#13;
results</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138434">
                <text>Antipsychotic agents, Benzodiazepines, Drug evaluation, Chromatography</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138435">
                <text>Abstract&#13;
Background Immunochromatography-based urine drug screening (UDS) can have false-positive or false-negative&#13;
results; thus, interpretation of results requires careful evaluation. A UDS-negative result simply indicates that target&#13;
drugs were not detected in urine and does not rule out acute poisoning. This study aimed to determine the presence&#13;
of drugs in the blood and blood drug concentrations in suspected cases of acute poisoning with UDS-negative&#13;
results.&#13;
Methods In this single-center, retrospective, observational study, we included 501 patients who attended Tokai&#13;
University Hospital Advanced Emergency Medical Center, Japan, between January 1, 2014 and December 31, 2023&#13;
and were diagnosed with acute poisoning with negative UDS results. The primary outcome included the detection&#13;
rate of UDS items and non-UDS items in blood samples. The secondary outcome included the classification of blood&#13;
drug concentrations (below therapeutic range, within therapeutic range, above therapeutic range). Blood drug&#13;
concentrations were measured using a gas chromatography–mass spectrometer and liquid chromatography–tandem&#13;
mass spectrometer.&#13;
Results Blood drug concentrations were detected in 498 (99.4%) of the 501 participants. Despite negative UDS&#13;
results in urine, UDS items were detected in blood samples of 239 patients (58.8%). Non-UDS items were detected in&#13;
430 participants (86.3%). Benzodiazepines were the most commonly detected UDS items, with many cases exhibiting&#13;
blood drug concentrations above the therapeutic range. In non-UDS items, non-benzodiazepine hypnotics,&#13;
antipsychotics, and over-the-counter (OTC) medications were often detected.&#13;
Conclusion This study demonstrates that negative UDS results do not rule out the presence of drugs in acute&#13;
poisoning cases. Moreover, a comprehensive evaluation, including physical and laboratory findings, is essential for&#13;
accurate diagnosis and treatment.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138436">
                <text>Rie Yamamoto1*, Yukari Maki1&#13;
&#13;
, Yuri Iketani1&#13;
&#13;
, Tomoatsu Tsuji1&#13;
&#13;
, Takeshi Saito1&#13;
&#13;
and Seiji Morita1</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="138437">
                <text>https://doi.org/10.1186/s12245-026-01119-y</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="138438">
                <text>2026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138439">
                <text>peri irawan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138440">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138441">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138442">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15800">
        <name>Antipsychotic agents, Benzodiazepines, Drug evaluation, Chromatography</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
