<?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=5" accessDate="2026-04-11T15:29:22+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>5</pageNumber>
      <perPage>10</perPage>
      <totalResults>201</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="12877" public="1" featured="1">
    <fileContainer>
      <file fileId="12932">
        <src>https://repository.horizon.ac.id/files/original/11540209a6c58ef5c366cdd94af9b297.pdf</src>
        <authentication>26906966ceef2ce3d6e4c51897903671</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="137483">
                <text>Special care services delivery at disaster&#13;
scenes: a systematic review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137484">
                <text>Disaster, Hazard-induced emergencies, Public health response, Health system resilience, Disaster&#13;
preparedness and coordination, Special care services, Prehospital care, Advanced life support</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137485">
                <text>Abstract&#13;
Background Disasters create strain on health systems and require significant preparedness to reduce mortality&#13;
and morbidity. Special care services; e.g. Advanced Life Support, critical care interventions (intubation; vasopressor&#13;
therapy) and point of care diagnostics (ultrasound) may be provided in disaster-settings, although actual use of&#13;
services is dependent on logistical, operational and contextual issues. This systematic review identifies an important&#13;
gap to understand the effectiveness, feasibility and barriers to, special care services.The overall aim of this systematic&#13;
review is to synthesise global evidence on the evidence-based practices and improve disaster response.&#13;
Methods This systematic review utilized PubMed, Scopus, Web of Science, Embase, and grey literature from the&#13;
time of inception of the different databases to January 2025, from which a total of 4465 records were identified. After&#13;
a thorough, organized review of the identified records based on our exclusion criteria and inclusion criteria, a total&#13;
of 31 articles were retained. The systematic review followed PRISMA 2020, and searched for studies on special care&#13;
services in a pre-hospital disaster setting, and included primary research and review articles that described advanced&#13;
interventions, and which had no time restrictions on date of publication. Articles that were waived from the cost of&#13;
in-app purchasing were excluded due to limited resources and could limit the studies that were included. Quality&#13;
assessment using STROBE, SANRA and checklists, along with the categories of findings using a thematic content&#13;
analysis based on the dimensions of prehospital care.&#13;
Results Thematic analysis revealed six broad themes: Patient Care and Clinical Management, Operational Efficiency&#13;
and Logistics, Personnel and Training, Technology and Equipment, System Coordination and Preparedness, and Ethical&#13;
and Contextual Considerations. Advanced functions like REBOA, ultrasound and AI-related diagnostics improved&#13;
survival and neurological outcomes, However, they were restricted due to limited resources, lack of training, and lack&#13;
of coordination, particularly in low resource contexts.&#13;
Conclusions The reviewed literature demonstrated that critical-care services such as Advanced Life Support (ALS),&#13;
intubation, and ultrasound resulted in improved morbidity and mortality outcomes in disaster settings but were&#13;
&#13;
limited due to resource constraints, lack of training and inadequate coordination all the more pertinent to low-&#13;
resource settings.&#13;
&#13;
Clinical trial number Not applicable.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137486">
                <text>Mohammad Masbi1&#13;
&#13;
, Nader Tavkoli2&#13;
&#13;
, Hamid Payrovi3&#13;
&#13;
and Mohsen Dowlati4*</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="137487">
                <text>https://doi.org/10.1186/s12245-025-01041-9</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="137488">
                <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="137489">
                <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="137490">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137491">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137492">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15700">
        <name>Disaster, Hazard-induced emergencies, Public health response, Health system resilience</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12876" public="1" featured="1">
    <fileContainer>
      <file fileId="12931">
        <src>https://repository.horizon.ac.id/files/original/e9f499efb76ed4e9cda9be2bad14b167.pdf</src>
        <authentication>c5901ed3b70b2284f7a764a753e8d0b6</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="137473">
                <text>Traumatic spigelian hernia in an adolescent&#13;
following a blunt abdominal trauma: a rare&#13;
case report and literature review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137474">
                <text>spigelian hernia, Traumatic abdominal wall hernia, Mesenteric defect, Laparotomy, Blunt trauma</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137475">
                <text>Abstract&#13;
Introduction spigelian hernias are rare anterior abdominal wall hernias, accounting for less than 2% of all hernias.&#13;
Traumatic spigelian hernias are exceptionally rare and typically result from blunt abdominal trauma.&#13;
Case presentation We report a case of a 15-year-old male who presented with right lower quadrant abdominal pain&#13;
following blunt trauma. Imaging revealed a traumatic spigelian hernia with an associated ileal mesenteric defect. The&#13;
patient underwent exploratory laparotomy and hernia repair with excellent postoperative recovery.&#13;
Conclusion This case highlights the importance of early recognition and surgical management of traumatic&#13;
spigelian hernias, particularly when associated with underlying mesenteric defects.&#13;
Keywords spigelian hernia, Traumatic abdominal wall hernia, Mesenteric defect, Laparotomy, Blunt trauma</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137476">
                <text>Mahdi Aljamal1*, Zainah Amjad Issa2&#13;
&#13;
, Ali Shakhshir3&#13;
&#13;
and Omar Abu-Zaydeh4</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="137477">
                <text>https://doi.org/10.1186/s12245-025-01040-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="137478">
                <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="137479">
                <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="137480">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137481">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137482">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15699">
        <name>spigelian hernia, Traumatic abdominal wall hernia, Mesenteric defect, Laparotomy, Blunt trauma</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12875" public="1" featured="1">
    <fileContainer>
      <file fileId="12930">
        <src>https://repository.horizon.ac.id/files/original/b7014ffc6ccab9d44a1207a2a0c8f1f1.pdf</src>
        <authentication>26188fe50108ffe996d586da855ced1d</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="137463">
                <text>Complicated diaphragmatic hernia post laparoscopic Nissen fundoplication: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137464">
                <text>Gastric volvulus, Nissen fundoplication, GERD</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137465">
                <text>Abstract&#13;
Background The definition of gastroesophageal reflux disease is gastroesophageal reflux with associated symptoms&#13;
or complications. Because parents or guardians perceive the disease’s symptoms differently, it is difficult to determine&#13;
how common it is. Although gastric volvulus and wrap migration are well-known complications following Nissen&#13;
fundoplication, the herniation in our case was caused by a defect medial to the hiatus, which could potentially&#13;
compromise the patient’s life in the future.&#13;
Case presentation We present a rare complication post laparoscopic Nissen fundoplication, four years male&#13;
Egyptian child presented to emergency department by shock, rigid abdomen. X-ray and CT scan abdomen showed&#13;
herniated stomach with ischemic volvulus of the stomach and pneumoperitoneum, exploration was done and case&#13;
managed successfully.&#13;
Conclusion Gastric volvulus is a complication with high morbidity and mortality outcomes that could be missed&#13;
or misdiagnosed, especially post laparoscopic fundoplication, high index of suspicion is the key to detect such&#13;
complications. Defects in diaphragm could be present in pediatric patients because of congenital or acquired causes,&#13;
careful inspection of diaphragm during laparoscopic fundoplication is an important step to detect possible defects to&#13;
minimize post operative complications.&#13;
Keywords Gastric volvulus, Nissen fundoplication, GERD</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137466">
                <text>Ahmed Maher1* , Ahmed Tayel1 and Karim Darwesh1</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="137467">
                <text>https://doi.org/10.1186/s12245-025-01039-3</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="137468">
                <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="137469">
                <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="137470">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137471">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137472">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15698">
        <name>Gastric volvulus, Nissen fundoplication, GERD</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12874" public="1" featured="1">
    <fileContainer>
      <file fileId="12929">
        <src>https://repository.horizon.ac.id/files/original/5a40e3863b589eeb6335451421fca970.pdf</src>
        <authentication>de327b51c4decd2da4c21b99aa4fc062</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="137453">
                <text>Rebound warfarin toxicity presenting&#13;
with spontaneous hemopericardium&#13;
in cardiac tamponade: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137454">
                <text>Hemopericardium, Cardiac tamponade, Rebound warfarin toxicity, Half-life</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137455">
                <text>Abstract&#13;
Background The spontaneous hemopericardium due to warfarin toxicity is uncommon but can be fatal if it leads to&#13;
cardiac tamponade and timely interventions are not administered.&#13;
Case presentation An 80-year-old male with a medical history of hypertension, chronic obstructive pulmonary&#13;
disease (COPD), and atrial fibrillation presented with chest pain and shortness of breath. On examination, he had&#13;
tachycardia, hypotension, and muffled heart sounds. The 2-D echocardiogram confirmed pericardial effusion&#13;
with cardiac tamponade. An emergent pericardiocentesis was performed in the emergency department (ED),&#13;
following which the patient hemodynamically improved. The past medical history was significant for recurrent&#13;
ED visit with warfarin toxicity in the form of calf hematoma. His most recent ED visit was three days ago, where&#13;
he received fresh frozen plasma (FFP) for a supra-therapeutic International Normalized Ratio (INR) of 8.66 without&#13;
bleeding manifestations and was discharged with an INR value of 2.27. During the current ED presentation, the&#13;
hemopericardium was likely due to rebound warfarin toxicity, as the INR reported was found to be 6.38 despite&#13;
having previously corrected to 2.27 and discontinuing warfarin after the recent ED discharge. In the current ED&#13;
presentation, coagulopathy was corrected with FFP and vitamin K. The patient was admitted to the ward for&#13;
evaluation. The pericardial fluid analysis showed no evidence of tuberculosis or other infections, and his recovery was&#13;
uneventful. On follow-up after 3 months, he was doing well on dabigatran for stroke prevention.&#13;
Conclusion The treatment of warfarin toxicity requires consideration of the half-life of the offending agent, warfarin,&#13;
as well as the antidotes (FFP and vitamin k) widely practiced in low-middle income countries to prevent rebound&#13;
warfarin toxicity.&#13;
Keywords Hemopericardium, Cardiac tamponade, Rebound warfarin toxicity, Half-life</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137456">
                <text>Ugyen Rinzin1* and Mahesh Gurung2</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="137457">
                <text>https://doi.org/10.1186/s12245-025-01037-5</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="137458">
                <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="137459">
                <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="137460">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137461">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137462">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15697">
        <name>Hemopericardium, Cardiac tamponade, Rebound warfarin toxicity, Half-life</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12873" public="1" featured="1">
    <fileContainer>
      <file fileId="12928">
        <src>https://repository.horizon.ac.id/files/original/4d6ba5801834698cd805e6364aed30a8.pdf</src>
        <authentication>93e7740e39fd4b6f5a1b02fef24dd2a5</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="137443">
                <text>Unusual presentation of complicated&#13;
relapsing fever with spontaneous&#13;
hemoperitoneum mimicking surgical acute&#13;
abdomen: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137444">
                <text>Unusual presentation, Relapsing fever, Hemoperitoneum, Acute abdomen, Case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137445">
                <text>Abstract&#13;
Background: Louse-borne relapsing fever (LBRF) is a prevalent disease in Ethiopia, affecting malnourished and&#13;
impoverished populations. Historically fatal, mortality has decreased to less than 5% with antibiotics. Symptoms&#13;
include high fever, rigors, myalgia, hepatosplenomegaly, jaundice, and petechial rash. Diagnosis is challenging due to&#13;
Giemsa-stained blood films and PCR in resource-limited settings.&#13;
Case Presentation: A 29-year-old Ethiopian patient experienced abdominal pain, vomiting, diarrhea, and high fever&#13;
for 3 days. Physical examination revealed low blood pressure, oxygen saturation, tachycardia, decreased air entry, and&#13;
a tender abdomen. A bedside ultrasound revealed bilateral pleural collection, dense B lines, an air bronchogram, and&#13;
abdominal collection. The patient had thrombocytopenia, leukocytosis, acute kidney injury, elevated transaminase&#13;
levels, and Borrelia spirochetes in her blood. The patient recovered fully within 8 days after respiratory failure.&#13;
Discussion: This case highlights the importance of recognizing relapsing fever (RF) as a critical mimic of surgical&#13;
abdomen, preventing unnecessary surgical interventions in hemorrhagic abdominal emergencies.&#13;
Conclusion: A life-threatening Borrelia-induced hemoperitoneum in Ethiopia was successfully managed, despite&#13;
complications of surgical acute abdomen with hemoperitoneum, severe thrombocytopenia, and multiorgan&#13;
involvement, highlighting the importance of infectious consideration in acute abdomen.&#13;
Keywords Unusual presentation, Relapsing fever, Hemoperitoneum, Acute abdomen, 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="137446">
                <text>Yemane Gebremedhin Tesfay1*, Habtamu Kebede Adera2&#13;
&#13;
, Zelalem Getahun Demissie3&#13;
&#13;
, Dirijit Mamo Alemu1&#13;
,&#13;
&#13;
Menbeu Sultan Mohammed1,3, Getaw Worku Hassen4&#13;
&#13;
and Mohammed Kalifa Nuguse1</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="137447">
                <text>https://doi.org/10.1186/s12245-025-01035-7</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="137448">
                <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="137449">
                <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="137450">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137451">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137452">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15696">
        <name>Unusual presentation, Relapsing fever, Hemoperitoneum, Acute abdomen, Case report</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12872" public="1" featured="1">
    <fileContainer>
      <file fileId="12927">
        <src>https://repository.horizon.ac.id/files/original/bab4c24650cc7c44b4e948b17f7a95b7.pdf</src>
        <authentication>aec3ae002fce14af590236ed29bdf094</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="137433">
                <text>Conductive heat loss in simulated outdoor settings: a preliminary experimental human study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137434">
                <text>Hypothermia, accidental, Body temperature regulation, Heat loss, Cold exposure, Wilderness</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137435">
                <text>Abstract&#13;
Background Little is known about the nature and magnitude of conductive heat loss in outdoor environments.&#13;
Although manikin studies provide reproducible and consistent data, they may not fully reflect all aspects of human&#13;
physiological responses. This preliminary study assessed heat loss in volunteers under simulated outdoor conditions,&#13;
with a focus on heat flux toward the ground, which primarily represents heat conduction.&#13;
Methods An experimental study was conducted with seven healthy volunteers in a thermoclimatic chamber. A&#13;
two-phase rescue scenario was employed in which a person immobilized on a spineboard was placed directly on&#13;
the ground (Phase 1) and then lifted upwards under windy conditions (Phase 2). Heat flux was measured via heat&#13;
flow sensors placed on the volunteers’ skin. The driving force for conductive heat loss was determined on the basis of&#13;
the temperature difference between the skin and the spineboard. A linear regression model was used to analyse the&#13;
relationship between heat flux and temperature difference.&#13;
Results The mean skin-spineboard temperature difference was 23,6±2,9 °C and increased over time. The mean heat&#13;
flux through the contact area was 467±97 W/m2. A significant increase in heat flux to 560±45 W/m2 was recorded&#13;
in Phase 2 of the experiment. Multiplication of the heat flux per area times the contact area resulted in a mean heat&#13;
loss of 159 Watts. In both phases, a strong linear relationship was found between back skin temperature and heat&#13;
flux. In Phase 1, the relationship was positive (β=+31 W/m2 per 1 °C decrease in skin temperature; R2=0.986; p&lt;0.001),&#13;
whereas in Phase 2, it was negative (β=−20 W/m2 per 1 °C decrease; R2=0.946; p&lt;0.001).&#13;
Conclusions The heat flux through the skin-to-spineboard interface, which is mainly conductive loss, is one-fourth&#13;
greater than the heat flux through the skin of anterior body. Heat conduction towards the ground accounts for&#13;
approximately one-fifth of the total heat loss. The heat flux through the skin-to-spineboard contact surface may&#13;
increase when the spineboard is lifted from the ground in windy conditions.&#13;
Keywords Hypothermia, accidental, Body temperature regulation, Heat loss, Cold exposure, Wilderness</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137436">
                <text>Tomasz Sanak1*, Mateusz Putowski2&#13;
&#13;
, Stanisław Krzeptowski-Sabała3&#13;
&#13;
, Janusz Pobędza4&#13;
&#13;
, Paweł Walczak4&#13;
,&#13;
&#13;
Konrad Mendrala5&#13;
&#13;
, Tomasz Darocha5&#13;
&#13;
and Sylweriusz Kosiński3,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="137437">
                <text>https://doi.org/10.1186/s12245-025-01034-8</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="137438">
                <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="137439">
                <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="137440">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137441">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137442">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15695">
        <name>Hypothermia, accidental, Body temperature regulation, Heat loss, Cold exposure, Wilderness</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12871" public="1" featured="1">
    <fileContainer>
      <file fileId="12926">
        <src>https://repository.horizon.ac.id/files/original/f2f101c3b055e812d3f70b943f839b8e.pdf</src>
        <authentication>fc2ea3baa22700c53418ea48dd91d970</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="137423">
                <text>The utility of computed tomography-derived inferior vena cava parameters in predicting outcomes in patients with active bleeding undergoing transarterial embolization</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137424">
                <text>Inferior vena cava volume, Inferior vena cava diameter, CT, Active bleeding, Transarterial embolization,&#13;
Massive transfusion, Mortality</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137425">
                <text>Abstract&#13;
Background The inferior vena cava (IVC) parameters are associated with prognostic significance in emergency&#13;
patients, but there is a lack of data using this parameter in patients with active bleeding.&#13;
Objectives To investigate the prognostic relevance of IVC parameters in patients with active bleeding.&#13;
Patients and methods A retrospective analysis was conducted on consecutive patients who underwent&#13;
transarterial embolization due to bleeding from different anatomical sites following computed tomography (CT)&#13;
imaging at a university medical center over a five-year period (2018–2022). The initial CT scan was used to determine&#13;
the IVC volume and IVC flatness index, which were then incorporated into multivariable regression analyses that&#13;
included demographic, hemodynamic, and laboratory data.&#13;
Results The analysis included 188 patients (75.3% male) with a median age of 50 years, and a massive transfusion rate&#13;
and an all-cause 30-day mortality rate of 26.6% each. Compared with female patients, male patients had a significantly&#13;
higher median IVC volume (25.45 vs. 15.8 cm3, p&lt;0.001), whereas the median IVC flatness index was similar for&#13;
both sexes (14 vs. 14, p=0.414). Median IVC volumes were similar between 30-day survivors and nonsurvivors (21.6&#13;
vs. 20.2 cm3, p=0.382) and between patients who underwent massive transfusion and those who did not (21.2 vs.&#13;
21.5 cm3, p=0.567). A multivariable Cox proportional hazards model revealed a statistically significant association&#13;
between the IVC flatness index and 30-day mortality (hazard ratio, 1.27; 95% confidence interval, 1.01–1.59; p=0.038).&#13;
Additionally, logistic regression analysis revealed no significant association between the IVC flatness index and&#13;
massive transfusion (univariable odds ratio, 1.01; 95% confidence interval, 0.75–1.34; p=0.972).&#13;
Conclusions A higher IVC flatness index was associated with 30-day mortality in patients undergoing transarterial&#13;
embolization for active bleeding. Further studies are needed to determine the prognostic value of CT-derived IVC&#13;
parameters.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137426">
                <text>Hans-Jonas Meyer1* , Veronika Sotikova1&#13;
&#13;
, Simon Riegelbauer1&#13;
&#13;
, Sebastian Ebel1&#13;
&#13;
, Holger Gößmann1&#13;
,&#13;
&#13;
Matthias Mehdorn2&#13;
&#13;
, Uwe Scheuermann2&#13;
&#13;
, Hans-Michael Tautenhahn2&#13;
&#13;
, Christian Kleber3&#13;
&#13;
, Timm Denecke1&#13;
and&#13;
&#13;
Manuel F. Struck4</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="137427">
                <text>https://doi.org/10.1186/s12245-025-01033-9</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="137428">
                <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="137429">
                <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="137430">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137431">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137432">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15694">
        <name>Inferior vena cava volume, Inferior vena cava diameter,</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12870" public="1" featured="1">
    <fileContainer>
      <file fileId="12925">
        <src>https://repository.horizon.ac.id/files/original/c13178c55bc24e26c54184ccba352e0b.pdf</src>
        <authentication>1ff3bd403ba79106c9fa4d718c45e0ef</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="137413">
                <text>Cardiopulmonary resuscitation-inducedn consciousness in an elderly patient: a case report in the prehospital setting</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137414">
                <text>Cardiopulmonary resuscitation (CPR) aims to limit hypoxic injury</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137415">
                <text>Abstract&#13;
Cardiopulmonary resuscitation (CPR) aims to limit hypoxic injury by providing oxygen to brain and heart tissues&#13;
during cardiac arrest. There has been an increase in reports of patients exhibiting signs such as eye opening, limb&#13;
movement, agitation, or even interference with resuscitation maneuvers while receiving CPR. These manifestations&#13;
cease when chest compressions are stopped, even without achieving return of spontaneous circulation (ROSC).&#13;
This phenomenon is termed CPR-induced consciousness (CPRIC). CPRIC cases are typically associated with cardiac&#13;
arrest of cardiac origin, shockable rhythms, and witnessed arrests with timely CPR. Here, we present the case of&#13;
an 80-year-old man who collapsed in a public setting. During resuscitation by Bystanders, the patient showed&#13;
purposeful movements and vocalizations, leading to incorrect interruptions of compressions due to presumed&#13;
ROSC. Once CPRIC was recognized, chest compressions and defibrillation continued, achieving ROSC. This case&#13;
highlights the importance of training prehospital providers to recognize and manage CPRIC, including the&#13;
potential use of sedatives—such as ketamine—to control movements that interfere with resuscitation. The case&#13;
also underscores the need for effective communication strategies with bystanders, given the social and ethical&#13;
implications of CPRIC manifestations. Further research is necessary to establish clear international guidelines and&#13;
improve clinical outcomes for patients experiencing CPRIC.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137416">
                <text>Jose Daniel Yusty-Prada1,2 , Nelson Esteban Portuguez-Jaramillo3 and Jose Luis Piñeros-Alvarez4,5*</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="137417">
                <text>https://doi.org/10.1186/s12245-025-01032-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="137418">
                <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="137419">
                <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="137420">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137421">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137422">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15693">
        <name>Cardiopulmonary resuscitation (CPR) aims to limit hypoxic injury</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12869" public="1" featured="1">
    <fileContainer>
      <file fileId="12924">
        <src>https://repository.horizon.ac.id/files/original/decec07dacaca8b484b8158a81d69f7f.pdf</src>
        <authentication>6dec3aeb2af9ae0eee99260ccc43a036</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="137403">
                <text>Spontaneous spinal epidural hematoma – an&#13;
uncommon cause of acute neurologic deficit&#13;
in the emergency department: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137404">
                <text>Spontaneous spinal epidural hematoma, Antiplatelet therapy, Emergency department</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137405">
                <text>Abstract&#13;
Background We present here an uncommon case of spontaneous spinal epidural hematoma (SSEH) likely secondary&#13;
to antiplatelet use. Its early recognition in the Emergency Department (ED) proves to be a challenge as presentation&#13;
mimics more common causes of acute neurological deficit leading to diagnostic delays and suboptimal treatment&#13;
outcomes.&#13;
Case Presentation A 63-year-old Chinese man with significant comorbidities including end stage renal failure on&#13;
haemodialysis, hypertension, diabetes mellitus and recent myocardial infarction treated with percutaneous coronary&#13;
intervention and dual antiplatelet therapy (DAPT) presented to the ED, complaining of acute onset non-traumatic&#13;
neck and upper thoracic pain with quadriparesis. Magnetic Resonance Imaging (MRI) of the cervical and thoracic&#13;
spine revealed an acute-subacute posterior epidural hematoma extending from the level of C5 to the level of T7&#13;
compressing the cord up to the level of T5. Despite decompression surgery, the patient remained paraplegic at&#13;
30-day follow-up.&#13;
Conclusion SSEH is a time critical neurosurgical emergency that should be suspected in patients with acute&#13;
onset axial neck or back pain and rapidly progressive myelopathic signs. Emergency physicians should use bedside&#13;
discriminators like axial pain, sensory level, sphincter involvement and cranial nerve sparing to trigger urgent spine&#13;
MRI and early surgical consultation when SSEH is suspected. This recognition is central to optimizing prognosis and&#13;
guiding realistic counselling.&#13;
Keywords Spontaneous spinal epidural hematoma, Antiplatelet therapy, Emergency department</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137406">
                <text>Arjun Thompson1*, Alston Guan Jie Ong2&#13;
&#13;
and Yuan Helen Zhang1</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="137407">
                <text>https://doi.org/10.1186/s12245-025-01031-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="137408">
                <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="137409">
                <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="137410">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137411">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137412">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15692">
        <name>Spontaneous spinal epidural hematoma, Antiplatelet therapy, Emergency department</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12868" public="1" featured="1">
    <fileContainer>
      <file fileId="12923">
        <src>https://repository.horizon.ac.id/files/original/1390244c2d1251e89d4442d6fd9ac952.pdf</src>
        <authentication>cb87d12a84f396d4c5e532932a4a47a6</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="137393">
                <text>Implementation of an AI-assisted tele-stroke&#13;
robot to optimize acute stroke care: a case&#13;
series from the SEHA Healthcare Network, UAE</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137394">
                <text>Timely access to a neurologist is essential for optimal management of acute stroke.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137395">
                <text>Timely access to a neurologist is essential for optimal management of acute stroke.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137396">
                <text>Ali Hassan1&#13;
, Tiago Moreira1&#13;
&#13;
, Ahmed Hassan1&#13;
&#13;
, Ahmed Samir Farw1&#13;
&#13;
, Muneer Al Marzooqi1&#13;
&#13;
, Neema Francis1&#13;
,&#13;
&#13;
Roxanne Roby1&#13;
&#13;
, Sonia Lamichhane1&#13;
&#13;
, Bita Lyons2&#13;
&#13;
, Keyvan Zeynali2&#13;
&#13;
and Thiagarajan Jaiganesh1*</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="137397">
                <text>https://doi.org/10.1186/s12245-025-01030-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="137398">
                <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="137399">
                <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="137400">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137401">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137402">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15691">
        <name>Timely access to a neurologist is essential for optimal management of acute stroke.</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
