<?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=949&amp;output=omeka-xml&amp;page=2" accessDate="2026-04-11T13:59:58+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>2</pageNumber>
      <perPage>10</perPage>
      <totalResults>201</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="12915" public="1" featured="1">
    <fileContainer>
      <file fileId="12970">
        <src>https://repository.horizon.ac.id/files/original/8b99ef3e34683f5a26353b90b75c26d5.pdf</src>
        <authentication>b0bd156cd124d64ef72e2479d2077319</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137863">
                <text>Entrustable Professional Activities for Emergency Medicine specialists</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137864">
                <text>Entrustable professional activities, Consensus methods, Competence, Assessment, Emergency medicine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137865">
                <text>Abstract&#13;
Background Various countries have developed competency frameworks for postgraduate training programs.&#13;
Identifying Entrustable Professional Activities (EPAs) that are core clinical activities could bridge the gap between&#13;
competencies and clinical practice. We aim to define core EPAs required for safe independent practice as an&#13;
Emergency Medicine (EM) Specialist, aligned with curricular outcomes from the International Federation for&#13;
Emergency Medicine (IFEM) model curriculum for postgraduate training and existing EPAs from IFEM member&#13;
countries to demonstrate the value such core documents bring to training and practice.&#13;
Methods A nominal group of six members used consensus methodology to generate and rate essential EPAs for&#13;
safe, independent practice as an EM specialist. Using existing literature on EPAs and IFEM curricular documents,&#13;
the nominal group generated and clarified ideas for potential EPAs. Feedback was obtained from the IFEM Core&#13;
Curriculum and Education committee, which comprises representatives from countries across all seven international&#13;
regions, and integrated with iterative revisions. The EQual: Queen’s EPA Quality Rubric were used to rate how essential&#13;
each EPA was for safe practice and the quality of each EPA. This approach is more rigorous as it allows for examination&#13;
of the quality of EPAs generated and how well they align with the key domains of the EPA construct.&#13;
Results A total of five core EPAs were selected and refined from seventeen proposed EPAs. The five EPAs were: EPA&#13;
1 (Patient resuscitation), EPA 2 (Adult and/or paediatric non-resuscitative emergency care), EPA 3 (Managing multiple&#13;
emergency patients), EPA 4 (Maintaining quality emergency care), and EPA 5 (Teaching emergency staff ). All core EPAs&#13;
were directly mapped to the IFEM model curriculum to ensure relevancy and reliability. Rating with the EQual rubrics&#13;
showed all five EPAs faring excellently, achieving overall median scores of more than four.&#13;
Conclusion Five EPAs were identified and evaluated to show their importance as core EPAs required for safe,&#13;
independent practice as an EM specialist. These EPAs can serve as a guide for individual countries to develop EPAs for&#13;
training.&#13;
Keywords Entrustable professional activities, Consensus methods, Competence, Assessment, Emergency medicine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137866">
                <text>David Teng1,2*, Anantharaman Venkataraman3&#13;
&#13;
, Andrew Singer4,5, Simon Chu6&#13;
&#13;
, Arif Alper Cevik7,8, Janis P. Tupesis9&#13;
,&#13;
&#13;
Taj Hassan10 and James Kwan1,2</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="137867">
                <text>https://doi.org/10.1186/s12245-025-01075-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="137868">
                <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="137869">
                <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="137870">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137871">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137872">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15742">
        <name>Entrustable professional activities, Consensus methods, Competence, Assessment, Emergency medicine</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12913" public="1" featured="1">
    <fileContainer>
      <file fileId="12968">
        <src>https://repository.horizon.ac.id/files/original/ee46a4865e9849cba1993e423a555b83.pdf</src>
        <authentication>3cfad9753fe4a4d849a5577ce081e4ac</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137843">
                <text>Emergency surgical conditions in geriatric patients: current research landscape</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137844">
                <text>Geriatric emergency surgery, Acute abdomen, Frailty, Multidisciplinary team, Laparoscopy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137845">
                <text>Abstract&#13;
Background The global population is aging rapidly, leading to a significant increase in geriatric patients requiring&#13;
emergency surgical intervention. This demographic presents unique challenges due to high frailty, multisystem&#13;
comorbidities, and atypical disease presentations, which contribute to elevated surgical risks and poorer outcomes&#13;
compared to younger populations.&#13;
Objective This review aims to synthesize the current research landscape regarding emergency general surgical&#13;
conditions in older adults. It focuses on the common disease spectrum, evolving management strategies, and critical&#13;
prognostic determinants to inform and enhance evidence-based clinical practice.&#13;
Methods A comprehensive literature review was conducted to delineate the etiology of acute abdomen in the&#13;
elderly, evaluate the utility of preoperative assessment tools and surgical approaches, and identify key factors&#13;
influencing patient outcomes, including mortality and complication rates.&#13;
Results Acute appendicitis, intestinal obstruction, gastrointestinal perforation, and biliary diseases represent the&#13;
most prevalent conditions. Precise preoperative risk stratification using scoring systems like POSSUM is crucial. For&#13;
hemodynamically stable patients, a laparoscopic-first approach is associated with reduced complications and shorter&#13;
hospital stays. Prognosis is critically influenced not just by age, but more significantly by frailty, multimorbidity, and&#13;
psychosocial factors. The integration of Multidisciplinary Team (MDT) models and rehabilitation medicine principles is&#13;
pivotal for optimizing comprehensive care.&#13;
Conclusions The management of geriatric emergency surgical patients necessitates a tailored, multidimensional&#13;
strategy. Future efforts to improve outcomes should focus on refined preoperative optimization, the promotion&#13;
of minimally invasive techniques, and the systematic implementation of multidisciplinary collaboration and early&#13;
rehabilitation.&#13;
Keywords Geriatric emergency surgery, Acute abdomen, Frailty, Multidisciplinary team, Laparoscopy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137846">
                <text>Dezhuang Li1*</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="137847">
                <text>https://doi.org/10.1186/s12245-025-01074-0</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="137848">
                <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="137849">
                <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="137850">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137851">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137852">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15739">
        <name>Geriatric emergency surgery, Acute abdomen, Frailty, Multidisciplinary team, Laparoscopy</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12912" public="1" featured="1">
    <fileContainer>
      <file fileId="12967">
        <src>https://repository.horizon.ac.id/files/original/f0dd029c6923ef6ff4ef635b4de1839a.pdf</src>
        <authentication>fdc205b42bbe9d0bea3c8c65c4dfc4ee</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137833">
                <text>Prevalence and associated factors&#13;
of hypertensive emergency among&#13;
hypertensive crisis patients admitted to the&#13;
emergency department at Hawassa University&#13;
Comprehensive Specialized Hospital, Ethiopia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137834">
                <text>Hypertensive emergency, Hypertensive urgency, Hypertensive crisis, Target organ damage, Ethiopia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137835">
                <text>Abstract&#13;
Background Hypertension is a major global health problem that affects approximately 1.4 billion people worldwide,&#13;
and 1–2% of this population experience hypertensive crisis. Hypertensive emergency is a subtype of hypertensive&#13;
crisis associated with target organ damage and is linked with increased morbidity and mortality. In our setting,&#13;
the prevalence of hypertensive emergencies and the characteristics of patients with a hypertensive crisis are not&#13;
certainly known yet. This study aimed to assess the prevalence and associated factors of hypertensive emergency&#13;
among hypertensive crisis patients admitted to the emergency department at Hawassa University Comprehensive&#13;
Specialized Hospital, Ethiopia.&#13;
Methods An institution-based cross-sectional study was conducted among 379 randomly selected medical records&#13;
of hypertensive crisis patients admitted at Hawassa University Comprehensive Specialized Hospital from July 2021 to&#13;
July 2024. Data were extracted from September 1 to 30, 2024. A structured checklist was used to collect the data from&#13;
charts through the Kobo toolbox. The descriptive statistics were presented in tables, frequencies, percentages, and&#13;
graphs. Binary logistic regression analysis was used to identify factors associated with hypertensive Emergency. An&#13;
adjusted odds ratio along with a 95% confidence interval was reported. The statistical significance level was declared&#13;
at a p-value≤0.05.&#13;
Results A total of 369 patients with hypertensive crisis were included in the study. The prevalence of hypertensive&#13;
Emergency was 40.7% (95% CI: 36, 46%). In patients with hypertensive emergencies, cerebrovascular injuries&#13;
accounted for 25.7% of the hypertension-mediated organ damage, followed by acute renal failure (22%), and&#13;
cardiovascular emergencies (15.4%). New-onset hypertension [AOR:2.5; 95%CI: 1.52, 4.15] and diabetes mellitus [AOR:&#13;
2.92; 95% CI: 1.63, 5.24] were independently associated with a hypertensive emergency.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137836">
                <text>Teshome Shanko1&#13;
&#13;
, Desalegn Dawit Assele2* , Zemedkihun Motera1&#13;
&#13;
and Yitayew Ewnetu Mohammed3</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="137837">
                <text>https://doi.org/10.1186/s12245-025-01073-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="137838">
                <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="137839">
                <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="137840">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137841">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137842">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15738">
        <name>Hypertensive emergency, Hypertensive urgency, Hypertensive crisis, Target organ damage, Ethiopia</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12911" public="1" featured="1">
    <fileContainer>
      <file fileId="12966">
        <src>https://repository.horizon.ac.id/files/original/6069b77341b6ce1aa3582476ee50f910.pdf</src>
        <authentication>47f0ab04c05ee5430672c7ae86275a4f</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137823">
                <text>External validation of the STUMBL score&#13;
in a frontline military hospital: predictive&#13;
performance in conflict-injured patients&#13;
with thoracic trauma</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137824">
                <text>Thoracic trauma, Military, STUMBL score, External validation study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137825">
                <text>Abstract&#13;
Purpose Thoracic trauma is a frequent cause of emergency department admission in both civilian and military&#13;
settings however injuries sustained in conflict zones differ in mechanism and severity. The STUMBL Score is a clinical&#13;
prediction tool originally developed for blunt thoracic trauma in civilian populations. This study aimed to externally&#13;
validate the STUMBL Score in a wartime context.&#13;
Methods We conducted a retrospective, single-centre validation study of adult patients with thoracic trauma&#13;
admitted to the ED of a frontline Ukrainian hospital between January 2023 and December 2024. The primary&#13;
composite outcome was defined as in-hospital mortality, pulmonary complications, or ICU admission. Model&#13;
performance was assessed by discrimination (area under the receiver operating characteristic curve) and calibration&#13;
(Hosmer-Lemeshow test and calibration belt).&#13;
Results A total of 374 patients were included (87% male; median age 38 [32–44]). Blast injury was the predominant&#13;
mechanism. The median STUMBL Score was 30 [24–33], and 92% of patients developed the composite outcome. The&#13;
area under the receiver operating characteristic curve (AUC) was 0.96 (95% CI 0.94–0.98), and calibration assessed&#13;
by the Hosmer-Lemeshow test yielded a p-value of 0.812. Using a threshold score of 23, the sensitivity was 0.89 and&#13;
specificity 0.97.&#13;
Conclusion The STUMBL Score demonstrated excellent predictive performance in a military population with&#13;
high-acuity, war-related thoracic trauma. These findings support its potential utility in conflict-zone emergency care,&#13;
although prospective validation in broader military settings is warranted.&#13;
Keywords Thoracic trauma, Military, STUMBL score, External validation study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137826">
                <text>Ceri Battle1,2* , Edward Baker2,3 , Jacopo Davide Giamello4,5 , Remo Melchio6 and Dmytro Dmytriiev7,8</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="137827">
                <text>https://doi.org/10.1186/s12245-025-01072-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="137828">
                <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="137829">
                <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="137830">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137831">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137832">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12909" public="1" featured="1">
    <fileContainer>
      <file fileId="12964">
        <src>https://repository.horizon.ac.id/files/original/da1cac1732785f9814abf485edc5cf16.pdf</src>
        <authentication>f7a6dd7d5f0f64ab2e3a16cb8bb84b3c</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137803">
                <text>Safety and accuracy of AI in triaging patients&#13;
in the emergency department</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137804">
                <text>Emergency department, AI, Triage, ChatGPT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137805">
                <text>Abstract&#13;
Background Artificial Intelligence (AI) has been increasingly explored in healthcare, particularly in emergency&#13;
department (ED) triage. This study aimed to evaluate the effectiveness of the AI chatbot ChatGPT in triaging patients,&#13;
focusing on its accuracy, safety, efficiency, and impact on patient care.&#13;
Methods A prospective observational study was conducted at the ED of King Saud Medical City (KSMC) in Riyadh,&#13;
Saudi Arabia, with a sample size of 138 patients. Patients requiring immediate resuscitation were excluded. ED&#13;
physicians assigned triage scores using the Canadian Triage and Acuity Scale (CTAS), followed by AI-generated scores&#13;
for the same patients. In cases of discrepancy, the final decision by the senior ED consultant was considered the gold&#13;
standard. The study assessed inter-rater reliability between AI and human raters and evaluated the accuracy of each&#13;
compared to the consultant’s assessment.&#13;
Results The results indicated a high agreement rate (85.61%) between ChatGPT and ED physicians, with substantial&#13;
inter-rater reliability (κ=0.780, 95% Confidence Interval [CI] 0.676–0.884, p&lt;0.001). Agreement between ED physicians&#13;
and consultants was at 63.9%, with moderate reliability (κ=0.406, 95% CI 0.006–0.806, p=0.018). Consultants assigned&#13;
lower acuity levels than physicians in most cases. ChatGPT’s accuracy compared to the consultant was 42.86%, with&#13;
slight reliability, showing a tendency to overestimate acuity, particularly in critical cases. However, it performed better&#13;
in mid-range acuity levels.&#13;
Conclusion The findings suggested that AI could support ED triage by aligning closely with human decision-making.&#13;
However, its overestimation of severity could lead to over-triaging and increased resource use. Limitations included a&#13;
small sample size and the use of a general AI model not specifically trained for medical triage. Future research should&#13;
focus on AI models tailored for ED triage to improve reliability and clinical applicability.&#13;
Keywords Emergency department, AI, Triage, ChatGPT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137806">
                <text>Lama Mohammad Alomari1 , Mai Mamdouh Alshammari1 , Asal Osama Arbaeen1 , Raghad Abdullah Alshehri2&#13;
and Hanin Saad Almalki3*</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="137807">
                <text>https://doi.org/10.1186/s12245-025-01069-x</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="137808">
                <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="137809">
                <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="137810">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137811">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137812">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15734">
        <name>Emergency department, AI, Triage, ChatGPT</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12908" public="1" featured="1">
    <fileContainer>
      <file fileId="12963">
        <src>https://repository.horizon.ac.id/files/original/66e74c44e0b69305488a75d9a71fafba.pdf</src>
        <authentication>56d9a5db314e9e30af5412f4859b6a53</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137793">
                <text>Waiting time ambulances in the Emergency&#13;
Department; a Dutch single center study&#13;
(WAITED study)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137794">
                <text>Crowding, Emergency Medical Services, Ambulance Diversion, Ambulance Offload Delay, Emergency&#13;
Department, Hospital</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137795">
                <text>Abstract&#13;
Background Ambulance offload delay (AOD) indicates the persistent and increasingly visible problem of Emergency&#13;
Department (ED) crowding. AOD is defined as the extended time from ambulance arrival at the ED until patient care is&#13;
transferred to ED staff. Despite its negative consequences and international attention, AOD is currently not monitored&#13;
within the Dutch Emergency Care. It is also unknown whether or not AOD is associated with the ambulance diversion&#13;
(AD) status. In the Dutch ED the AD status is monitored by means of the traffic light system. This study aims to&#13;
monitor AOD at the EDs of Franciscus Gasthuis &amp; Vlietland (FGV).&#13;
Methods A 10-week observational study was conducted at both the EDs of FGV. Ambulance personnel was queried&#13;
regarding AOD duration and traffic light statuses by means of paper questionnaires. Descriptive statistics are reported&#13;
as frequencies, medians and interquartile ranges (IQR). Associations between the traffic light status and categorical&#13;
AOD data were analyzed using Chi-square tests.&#13;
Results During the study period, 2967 ambulances arrived at the EDs. In 229 cases (7.7%), the definition of AOD&#13;
was met. The median AOD was 16 min (IQR: 10–25 min). In 95.6% (n=2830) of the cases the handover time was less&#13;
than 15 min. No statistically significant association was found between the traffic light status (green, orange, red) and&#13;
offload delay categories (p=0.109). A non-significant difference remained (p=0.075) when comparing median AOD in&#13;
the absence of an AD with the median AOD during an (impending) AD.&#13;
Conclusion This is the first observational study conducted in the Netherlands collecting data regarding the AOD. The&#13;
limited observation period, the reliance of self-reported data and the single-center design restricts the generalizability&#13;
of the data. Consequently, the authors conclude hypothesis-generating findings which warrant validation through&#13;
planned multicenter research. Nevertheless, besides the existing traffic light system, this unique study provides policy&#13;
makers with a candidate complementary quality indicator for ED-crowding in the Dutch context.&#13;
Keywords Crowding, Emergency Medical Services, Ambulance Diversion, Ambulance Offload Delay, Emergency&#13;
Department, Hospital</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137796">
                <text>S. Mol1*, J. D. G. Hageman-van Wamel1&#13;
&#13;
, M. C. Van Der Linden2&#13;
&#13;
, M. I. Gaakeer3&#13;
&#13;
and V. A. De Ridder4</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="137797">
                <text>https://doi.org/10.1186/s12245-025-01068-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="137798">
                <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="137799">
                <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="137800">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137801">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137802">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15733">
        <name>Crowding, Emergency Medical Services, Ambulance Diversion, Ambulance Offload Delay, Emergency Department, Hospital</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12907" public="1" featured="1">
    <fileContainer>
      <file fileId="12962">
        <src>https://repository.horizon.ac.id/files/original/cd85b6d931b6b4cee6df609ba05dea53.pdf</src>
        <authentication>3befc19c958ec485b8bf20d67d4bbdbb</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137783">
                <text>A dramatic case: fatal air embolism due to intraosseous puncture</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137784">
                <text>Emergency vascular access, Intraosseous puncture, Air embolism</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137785">
                <text>Abstract&#13;
Background Intraosseous access is a commonly used method for establishing vascular access in preclinical&#13;
emergency care. It is often used when peripheral access cannot be established due to shock. Pressure infusions are&#13;
used to overcome the resistance provided by the medullary cavity in order to achieve high flow rates needed for&#13;
effective resuscitation. However, the literature to date does not seem to adequately describe the potential risks. In&#13;
particular, air embolism is a potentially rare short-term fatal complication.&#13;
The case We report on an elderly woman who lay comatose on the floor for at least six hours before she was found&#13;
and given medical attention. In the emergency room, a CT scan showed large amounts of air in her venous system.&#13;
This air came from an intraosseous line in her left tibia and entered the left pelvic vein, the ventral hepatic veins, the&#13;
right ventricle and the pulmonary arteries. Despite all conservative measures, the patient died 18hours later as a&#13;
result of the air embolism.&#13;
Discussion To date, there is no meaningful data in the literature on the use of pressure infusions via intraosseous&#13;
access. The case described here highlights the risk of serious complications, which are probably underrepresented&#13;
in the literature. There is an urgent need for self-reflection when dealing with this type of access and a necessity to&#13;
develop clear guidelines regarding the inspection of connected systems and immediate emergency therapeutic&#13;
measures.&#13;
Conclusion This case highlights the critical importance of careful use of intraosseous access, especially in situations&#13;
with numerous other challenges that can cause distractions. Wherever possible, connection to the pressure device&#13;
should be avoided rather than prescribed as an absolute requirement.&#13;
Keywords Emergency vascular access, Intraosseous puncture, Air embolism</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137786">
                <text>Maximilian Muench1&#13;
&#13;
, Luisa Schonhart1&#13;
&#13;
, Konrad Steinestel2 , Daniel Gagiannis1 and Josefine Christine Baudrexl1*</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="137787">
                <text>https://doi.org/10.1186/s12245-025-01066-0</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="137788">
                <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="137789">
                <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="137790">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137791">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137792">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15732">
        <name>Emergency vascular access, Intraosseous puncture, Air embolism</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12906" public="1" featured="1">
    <fileContainer>
      <file fileId="12961">
        <src>https://repository.horizon.ac.id/files/original/615312723f2492a434b474628b3f22ec.pdf</src>
        <authentication>3befc19c958ec485b8bf20d67d4bbdbb</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137773">
                <text>A dramatic case: fatal air embolism due to intraosseous puncture</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137774">
                <text>Emergency vascular access, Intraosseous puncture, Air embolism</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137775">
                <text>Abstract&#13;
Background Intraosseous access is a commonly used method for establishing vascular access in preclinical&#13;
emergency care. It is often used when peripheral access cannot be established due to shock. Pressure infusions are&#13;
used to overcome the resistance provided by the medullary cavity in order to achieve high flow rates needed for&#13;
effective resuscitation. However, the literature to date does not seem to adequately describe the potential risks. In&#13;
particular, air embolism is a potentially rare short-term fatal complication.&#13;
The case We report on an elderly woman who lay comatose on the floor for at least six hours before she was found&#13;
and given medical attention. In the emergency room, a CT scan showed large amounts of air in her venous system.&#13;
This air came from an intraosseous line in her left tibia and entered the left pelvic vein, the ventral hepatic veins, the&#13;
right ventricle and the pulmonary arteries. Despite all conservative measures, the patient died 18hours later as a&#13;
result of the air embolism.&#13;
Discussion To date, there is no meaningful data in the literature on the use of pressure infusions via intraosseous&#13;
access. The case described here highlights the risk of serious complications, which are probably underrepresented&#13;
in the literature. There is an urgent need for self-reflection when dealing with this type of access and a necessity to&#13;
develop clear guidelines regarding the inspection of connected systems and immediate emergency therapeutic&#13;
measures.&#13;
Conclusion This case highlights the critical importance of careful use of intraosseous access, especially in situations&#13;
with numerous other challenges that can cause distractions. Wherever possible, connection to the pressure device&#13;
should be avoided rather than prescribed as an absolute requirement.&#13;
Keywords Emergency vascular access, Intraosseous puncture, Air embolism</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137776">
                <text>Maximilian Muench1&#13;
&#13;
, Luisa Schonhart1&#13;
&#13;
, Konrad Steinestel2 , Daniel Gagiannis1 and Josefine Christine Baudrexl1*</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="137777">
                <text>https://doi.org/10.1186/s12245-025-01066-0</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="137778">
                <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="137779">
                <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="137780">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137781">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137782">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15732">
        <name>Emergency vascular access, Intraosseous puncture, Air embolism</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12904" public="1" featured="1">
    <fileContainer>
      <file fileId="12959">
        <src>https://repository.horizon.ac.id/files/original/964752edf815d6ac646621af946d229e.pdf</src>
        <authentication>9447449d147049eb2d36013ed3c845d9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137753">
                <text>Machine learning-based classification of carotid plaques via ultrasound: a systematic review and meta-analysis of diagnostic performance</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137754">
                <text>Machine learning, Artificial intelligence, Ultrasound, Carotid artery plaque, Carotid atherosclerosis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137755">
                <text>Abstract&#13;
Background Machine learning (ML) models have gained traction for classifying carotid artery plaques via ultrasound&#13;
imaging to differentiate high-risk (unstable) from low-risk (stable) plaques, a critical step for stroke risk prediction&#13;
and guiding clinical interventions such as endarterectomy. However, prior studies report inconsistent diagnostic&#13;
performance attributed to variations in algorithms, cohort diversity, and imaging protocols. This systematic review&#13;
and meta-analysis aim to evaluate the pooled diagnostic accuracy of ML models for carotid plaque classification,&#13;
addressing these inconsistencies to inform standardized clinical applications.&#13;
Methods Five electronic databases were systematically searched up to February 28, 2025, for studies reporting&#13;
diagnostic performance metrics of ML-based models in carotid plaque classification. Pooled performance metrics&#13;
were analyzed using STATA, and the risk of bias was assessed using the PROBAST+AI tool.&#13;
Results A total of 20 studies met the inclusion criteria, of which 13 provided sufficient data for quantitative synthesis.&#13;
Sample sizes ranged from 15 to 413 patients, with 115– 81,000 images per study. Mean ages ranged from 27.5 to&#13;
75 years, mostly 60–70, and male representation ranged from 47% to 81%, except for one all-female cohort. The&#13;
pooled sensitivity was 0.84 (95% CI: 0.74–0.90) and specificity was 0.96 (95% CI: 0.89–0.98), with a pooled AUC of&#13;
0.95 (95% CI: 0.93–0.97). Substantial heterogeneity was observed (I2=88.8% for sensitivity, 64.1% for specificity, and&#13;
&#13;
68.1% overall). Meta-regression identified sample size and model architecture as significant sources of between-&#13;
study heterogeneity. No evidence of publication bias was detected (p=0.36). Quality assessment using PROBAST+AI&#13;
&#13;
indicated a low overall risk of bias in 70% of studies, moderate in 20%, and high in 10%. The GRADE approach rated&#13;
the certainty of evidence as moderate, primarily due to inconsistency and study-level bias.&#13;
Conclusion Machine learning models demonstrate promising diagnostic accuracy for carotid plaque classification,&#13;
showing high pooled sensitivity and specificity. However, substantial heterogeneity and only moderate certainty of&#13;
evidence suggest that these findings should be interpreted with caution.&#13;
Keywords Machine learning, Artificial intelligence, Ultrasound, Carotid artery plaque, Carotid atherosclerosis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137756">
                <text>Pooya Eini1* , Peyman Eini2&#13;
&#13;
, Homa Serpoush3&#13;
&#13;
, Mohammad Rezayee4&#13;
&#13;
and Jason Tremblay4</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="137757">
                <text>https://doi.org/10.1186/s12245-025-01065-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="137758">
                <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="137759">
                <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="137760">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137761">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137762">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15731">
        <name>Machine learning, Artificial intelligence, Ultrasound, Carotid artery plaque, Carotid atherosclerosis</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12902" public="1" featured="1">
    <fileContainer>
      <file fileId="12957">
        <src>https://repository.horizon.ac.id/files/original/8610eddf08d4f807e72d90537175e3f1.pdf</src>
        <authentication>6985aabf2bfa61e2e8bfe99b1323f6c5</authentication>
      </file>
    </fileContainer>
    <collection collectionId="949">
      <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="134588">
                  <text>Volume 18 Issue 1 2025</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="137733">
                <text>Visualizing the prognostic value of neuron-&#13;
specific enolase in acute ischemic stroke:&#13;
&#13;
a bibliometric analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137734">
                <text>Acute ischemic stroke, Neuron specific enolase, Biomarkers, Bibliometric analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137735">
                <text>Abstract&#13;
Introduction In recent years, neuron-specific enolase (NSE) has been explored as a suitable biomarker for cerebral&#13;
damage, specifically following ischemic stroke. This bibliometric analysis sought to illuminate patterns in research&#13;
published on NSE’s value as a biomarker for ischemic stroke by examining prominent authors, keywords, countries,&#13;
and organizations in this field.&#13;
Methods We conducted a bibliometric analysis using the Web of Science Core Collection. Publications were&#13;
retrieved using the search string “ischemic stroke (Topic) AND enolase (Topic)” without language restriction,&#13;
from database inception to June 2025. Extracted metadata were analyzed using VOSviewer (v1.6.20) to generate&#13;
co-authorship, co-citation, and keyword maps. Analyses characterized key authors, institutions, and countries;&#13;
mapped keyword co-occurrence; and described temporal trends. Bibliometric analysis was used to contextualize&#13;
NSE’s prognostic value in ischemic stroke.&#13;
Results A total of 465 documents were retrieved. China, the United States, and Germany were the most productive&#13;
countries, with the U.S. having the highest citation impact. The University of Florida, Capital Medical University, and&#13;
Central India Institute of Medical Sciences led institutional output. Ronald L. Hayes, Hatim F. Daginawala, and Robert S.&#13;
B. Clark emerged as leading authors, with Clark having the highest citations. Frequently occurring keywords included&#13;
“neuron-specific enolase,” “acute ischemic stroke,” and “cerebrospinal fluid.” Publication activity accelerated after 2016,&#13;
with a notable rise from 2023 onward.&#13;
Conclusion This bibliometric mapping reveals global but fragmented research on NSE as a biomarker for ischemic&#13;
stroke. While NSE shows promise, clinical studies remain inconsistent regarding its predictive value, highlighting the&#13;
need for large-scale, multicenter investigations. Bibliometric analysis helps identify gaps and collaborations critical to&#13;
advancing NSE’s translation into clinical practice.&#13;
Keywords Acute ischemic stroke, Neuron specific enolase, Biomarkers, Bibliometric analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137736">
                <text>Sofia Malik1&#13;
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="137737">
                <text>https://doi.org/10.1186/s12245-025-01064-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="137738">
                <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="137739">
                <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="137740">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137741">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137742">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15727">
        <name>Acute ischemic stroke, Neuron specific enolase, Biomarkers, Bibliometric analysis</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
