<?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=25" accessDate="2026-04-22T15:14:41+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>25</pageNumber>
      <perPage>10</perPage>
      <totalResults>255</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="12621" public="1" featured="1">
    <fileContainer>
      <file fileId="12677">
        <src>https://repository.horizon.ac.id/files/original/9b32c52070699eb90f79d0037f219881.pdf</src>
        <authentication>b2ad0c6167f541f705692800396d984d</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="134849">
                <text>Percutaneous closure of a traumatic ventricular septal defect: a case report&#13;
and literature review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134850">
                <text>Penetrating cardiac trauma, Ventricular septal defect, Emergency thoracotomy, Percutaneous closure, Echocardiography</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134851">
                <text>Abstract&#13;
Background Penetrating cardiac trauma is an entity with high pre and intrahospital mortality due to complications&#13;
such as cardiac tamponade and massive hemothorax. A ventricular septal defect (VSD) occurs in 1–5% of cases and&#13;
can present early or late. The management strategy for VSD resulting from penetrating cardiac trauma is uncertain.&#13;
Case presentation A 19-year-old man was admitted in cardiorespiratory arrest after a precordial stab wound.&#13;
Cardiopulmonary resuscitation was initiated achieving return of spontaneous circulation. eFAST evaluation&#13;
revealed cardiac tamponade, he was taken to emergency left thoracotomy finding a perforation of the free wall of&#13;
the left ventricle and a tear of the upper lobe of the left lung that were sutured. The patient was discharged and&#13;
six days later was readmitted with fever and dyspnea. During treatment for a surgical site infection a new-onset&#13;
pansystolic murmur was found: A transthoracic echocardiogram revealed a 13-mm VSD with left-to-right shunt. A&#13;
multidisciplinary team recommended percutaneous closure of the defect which was successfully performed without&#13;
complications.&#13;
Conclusions Traumatic VSD is a rare complication of penetrating cardiac trauma. A thorough clinical and&#13;
echocardiographic evaluation is essential for its diagnosis and characterization. Symptomatic septal defects, those&#13;
10 mm or larger, with Qp: Qs greater than 1.5, or causing complications such as pulmonary hypertension or valvular&#13;
involvement, are usually closed to prevent progression of heart failure. Management of traumatic VSD has traditionally&#13;
been surgical. However, a percutaneous intervention is a viable alternative in selected stable patients. Unlike ischemic&#13;
VSD, early intervention after patient stabilization generally yields favorable outcomes.&#13;
Keywords Penetrating cardiac trauma, Ventricular septal defect, Emergency thoracotomy, Percutaneous closure,&#13;
Echocardiography</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134852">
                <text>Camilo Andres Calderon-Miranda1,2*, Maria Juliana Reyes-Cardona3&#13;
&#13;
, Gabriel Roberto Lopez-Mora2,4,&#13;
Fernando Andrés Guerrero-Pinedo2,5, Jairo Sanchez-Blanco1,2, Carlos Enrique Vesga-Reyes1,2,&#13;
Jorge Alexander Zambrano-Franco1,2 and Pastor Olaya1,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="134853">
                <text>Abstract&#13;
Background Penetrating cardiac trauma is an entity with high pre and intrahospital mortality due to complications&#13;
such as cardiac tamponade and massive hemothorax. A ventricular septal defect (VSD) occurs in 1–5% of cases and&#13;
can present early or late. The management strategy for VSD resulting from penetrating cardiac trauma is uncertain.&#13;
Case presentation A 19-year-old man was admitted in cardiorespiratory arrest after a precordial stab wound.&#13;
Cardiopulmonary resuscitation was initiated achieving return of spontaneous circulation. eFAST evaluation&#13;
revealed cardiac tamponade, he was taken to emergency left thoracotomy finding a perforation of the free wall of&#13;
the left ventricle and a tear of the upper lobe of the left lung that were sutured. The patient was discharged and&#13;
six days later was readmitted with fever and dyspnea. During treatment for a surgical site infection a new-onset&#13;
pansystolic murmur was found: A transthoracic echocardiogram revealed a 13-mm VSD with left-to-right shunt. A&#13;
multidisciplinary team recommended percutaneous closure of the defect which was successfully performed without&#13;
complications.&#13;
Conclusions Traumatic VSD is a rare complication of penetrating cardiac trauma. A thorough clinical and&#13;
echocardiographic evaluation is essential for its diagnosis and characterization. Symptomatic septal defects, those&#13;
10 mm or larger, with Qp: Qs greater than 1.5, or causing complications such as pulmonary hypertension or valvular&#13;
involvement, are usually closed to prevent progression of heart failure. Management of traumatic VSD has traditionally&#13;
been surgical. However, a percutaneous intervention is a viable alternative in selected stable patients. Unlike ischemic&#13;
VSD, early intervention after patient stabilization generally yields favorable outcomes.&#13;
Keywords Penetrating cardiac trauma, Ventricular septal defect, Emergency thoracotomy, Percutaneous closure,&#13;
Echocardiography</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="134854">
                <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="134855">
                <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="134856">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134857">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134858">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15479">
        <name>Penetrating cardiac trauma, Ventricular septal defect, Emergency thoracotomy, Percutaneous closure, Echocardiography</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12610" public="1" featured="1">
    <fileContainer>
      <file fileId="12666">
        <src>https://repository.horizon.ac.id/files/original/ba5c6c1d053baffeb2ff480f76fc024f.pdf</src>
        <authentication>ff512aa4832ba5c2a10624dcf52db80b</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="134719">
                <text>Lack of standardization in the nomenclature of dating strokes or the desperate search for a common language</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134720">
                <text>reading radiology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134721">
                <text>Introduction&#13;
When reading radiology reports from various medical&#13;
&#13;
institutions across Europe, a pronounced lack of consen-&#13;
sus emerges regarding the definition of stroke and infarc-&#13;
tion stages. This ambiguity persists despite significant&#13;
&#13;
advancements in stroke management and the develop-&#13;
ment of novel time frames for mechanical thrombectomy&#13;
&#13;
procedures. Terms such as “hyperacute,” “acute”, and&#13;
&#13;
“subacute” are employed in varying and often overlap-&#13;
ping contexts, leading to confusion among practitioners.&#13;
&#13;
Consequently, many thrombectomy research studies&#13;
&#13;
have resorted to using the time of symptom onset in con-&#13;
junction with the Alberta Stroke Program Early CT Score&#13;
&#13;
(ASPECTS) as a proxy to delineate the timing and nature&#13;
of stroke interventions [1].&#13;
&#13;
Methods We have summarized the terminology com-&#13;
monly used in our neuroradiological clinical practice&#13;
&#13;
regarding the state of strokes / infarcts in a graphic. It&#13;
could serve as a proposal for standardization.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134722">
                <text>Eya Khadhraoui1* and Sebastian Johannes Müller1</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="134723">
                <text>https://doi.org/10.1186/s12245-024-00803-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="134724">
                <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="134725">
                <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="134726">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134727">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134728">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15461">
        <name>eading radiology</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12609" public="1" featured="1">
    <fileContainer>
      <file fileId="12665">
        <src>https://repository.horizon.ac.id/files/original/2e8161ec7209dc6cfee38933bc0457af.pdf</src>
        <authentication>08b3eaa9e1aa4706c8798254cf9d76aa</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="134709">
                <text>A novel tool for assessing pediatric emergency care in low- and middle-income countries: a pilot study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134710">
                <text>Pediatric emergency medicine, Pediatric readiness, Low-income countries, Middle-income countries,&#13;
Health resources / supply and distribution</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134711">
                <text>Abstract&#13;
Background Globally, most children seek emergency care at general rather than specialized pediatric emergency&#13;
&#13;
departments. There remains significant variation in the provision of pediatric emergency care, particularly in resource-&#13;
constrained settings. The objective of this study is to pilot a self-assessment tool to evaluate pediatric emergency care&#13;
&#13;
capabilities in low- and middle-income country (LMIC) hospitals on the African Continent.&#13;
Methods This was a prospective cross-sectional descriptive study using a convenience sample of sub-Saharan&#13;
&#13;
African hospitals. The assessment tool was developed by operationalizing the technical contents of existing stand-&#13;
ards and guidelines from international bodies including the World Health Organization and International Federa-&#13;
tion of Emergency Medicine. The pilot was conducted at emergency departments located across different regions&#13;
&#13;
on the African continent. Descriptive statistics were used to evaluate different domains of pediatric emergency care&#13;
capabilities including pediatric triage, protocols, staffing, training, equipment, consumables, and medicines.&#13;
Results Sixteen hospitals with emergency departments completed the assessment tool (participation rate of 76%).&#13;
The hospitals were in nine different countries across four regions of sub-Saharan Africa. National/academic hospitals&#13;
comprised 56.3% of the participating hospitals. The majority, 44%, of these hospitals saw pediatric patient volumes&#13;
of 2,000–4,999 patients per year. Dedicated pediatric triage spaces and resuscitation spaces were available at 37.5%&#13;
and 56.3%, respectively. Formal pediatric resuscitation guidelines were used at 62.5%. Doctors on the self-assessment&#13;
teams came from primarily pediatrics and general practitioner training backgrounds (both 68.8%). Basic respiratory&#13;
and airway support equipment (e.g. oxygen, bag-valve mask devices) were available in all participating hospitals,&#13;
whereas advanced airway equipment (e.g. pediatric intubation equipment) was available in 37.5% of hospitals. Most&#13;
medicines from the World Health Organization Essential Medicines list were available at participating hospitals.&#13;
Conclusions To date, this is the first assessment tool dedicated to the comprehensive evaluation of pediatric&#13;
emergency care in LMICs. This pilot provides a first approach to evaluate pediatric emergency healthcare capabilities&#13;
in the hospital setting with future directions to improve the tool based on qualitative feedback.&#13;
Keywords Pediatric emergency medicine, Pediatric readiness, Low-income countries, Middle-income countries,&#13;
Health resources / supply and distribution</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134712">
                <text>Sonia Y. Jarrett1*, Andrew Redfern2&#13;
, Joyce Li1&#13;
, Camilo E. Gutierrez3&#13;
&#13;
, Priyanka Patel4&#13;
&#13;
, Olurotimi Akinola5 and&#13;
&#13;
Michelle L. Niescierenko1</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="134713">
                <text>https://doi.org/10.1186/s12245-024-00802-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="134714">
                <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="134715">
                <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="134716">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134717">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134718">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15460">
        <name>Pediatric emergency medicine, Pediatric readiness, Low-income countries, Middle-income countries,</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12608" public="1" featured="1">
    <fileContainer>
      <file fileId="12664">
        <src>https://repository.horizon.ac.id/files/original/f48b11627c19ff2e2fc924af1e2bfc6c.pdf</src>
        <authentication>2817cb95cae5ccf66cb77b1c0be60702</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="134699">
                <text>A prospective, longitudinal, comparative analysis of the World Health Organization / International Committee of the Red Cross Basic Emergency Care Course on emergency&#13;
medicine knowledge and confidence&#13;
among recent medical school graduates</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134700">
                <text>Emergency medicine education, Training, Emergency care</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134701">
                <text>Abstract&#13;
&#13;
Background The Basic Emergency Care (BEC) course was created by the World Health Organization (WHO) in col-&#13;
laboration with the International Committee of the Red Cross (ICRC) and the International Federation for Emergency&#13;
&#13;
Medicine (IFEM) to train frontline providers in low-resource settings. This study aims to evaluate long-term retention&#13;
and maintenance of emergency care knowledge and confidence among University of Nairobi School of Medicine&#13;
graduates after completing the BEC course.&#13;
&#13;
Methods This longitudinal, prospective, comparative study was conducted with recent graduates of the Univer-&#13;
sity of Nairobi School of Medicine from October 2021 to May 2023. Participants’ retention of emergency medicine&#13;
&#13;
knowledge was assessed comparing a pre/post course test and a multiple-choice examination 12 to 18 months&#13;
after completing the BEC course. A survey assessed participants’ confidence in managing patients with emergencies&#13;
12–18 months after completing the BEC course using a 4-point Likert scale. These results were compared to a control&#13;
group of recent University of Nairobi School of Medicine graduates who did not take the BEC course.&#13;
Results The follow-up test scores were lower than the immediate post-course test scores, which suggests some&#13;
&#13;
knowledge loss over time. Compared to the control group, the BEC participants had higher test scores during the fol-&#13;
low-up period although the difference was not significant. There was no difference between most of the immedi-&#13;
ate post-course and follow-up survey responses. On follow-up evaluation, BEC participants reported a significant&#13;
&#13;
decrease in confidence in understanding emergency drugs and managing an obstructed airway and a patient requir-&#13;
ing immobilization. However, compared to the control group, BEC participants had significantly higher self-reported&#13;
&#13;
confidence in most areas assessed by the survey.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134702">
                <text>Nichole Michaeli1&#13;
&#13;
, Andrew Beck2&#13;
&#13;
, Giovanna De Luca2&#13;
&#13;
, Mary Gitau3&#13;
&#13;
, Derek Lubetkin4&#13;
&#13;
, Derick Ochieng5&#13;
,&#13;
&#13;
Grace W. Wanjiku2 and Justin G. Myers6*</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="134703">
                <text>https://doi.org/10.1186/s12245-024-00797-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="134704">
                <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="134705">
                <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="134706">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134707">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134708">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15021">
        <name>Emergency medicine education, Training, Emergency care</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12607" public="1" featured="1">
    <fileContainer>
      <file fileId="12663">
        <src>https://repository.horizon.ac.id/files/original/4ae7b895fc80fd013720926b78b453c3.pdf</src>
        <authentication>1d67dadab1d64a0da3549a65f05d64e8</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="134689">
                <text>Clinical and demographic profiling of snakebite envenomation in a tertiary care centre in northern India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134690">
                <text>Snake bite, Hemotoxic, Neurotoxic, ASV, Plasmapheresis, HBOT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134691">
                <text>Abstract&#13;
Background Snake bites are a major cause of emergency visits in tropical countries like India, with actual mortality&#13;
and morbidity likely higher due to underreporting. The aim of the study was to analyze the clinical and demographic&#13;
profiles of snake bites at the Department of Emergency Medicine, AIIMS Rishikesh, over two years (July 2021 to July&#13;
2023).&#13;
Methods Patients aged over 18 with witnessed or suspected snake bites were included. Data on demographics,&#13;
clinical history, laboratory parameters, treatment, and outcomes were collected.&#13;
Results Most patients were male (68.3%) and aged 31–50 years (35.6%). Farmers made up 57.4% of the cohort.&#13;
Bites occurred mostly in the evening (46.5%) and during the monsoon (71.3%). Symptoms varied: 48.5% were&#13;
asymptomatic, 31.7% had hemotoxic symptoms, and 15.8% experienced neurotoxic symptoms, including ptosis.&#13;
Hemotoxic bites frequently involved bleeding at the bite site (93.8%) and gum bleeding (46.9%). Local complications&#13;
were noted in 7.9% of cases. Neuroparalytic bites required ventilatory support in 62.5%. Blood products were&#13;
administered to 31% of patients with hemotoxic bites, hemodialysis to 19%, and plasmapheresis and hyperbaric&#13;
oxygen therapy to 6.3%. Out of the 69 symptomatic patients (68.3%) who received anti-snake venom (ASV), 28&#13;
(40.6%) patients developed adverse reactions.&#13;
Conclusion This study provides a detailed analysis of suspected snakebites in Uttarakhand and surrounding areas,&#13;
highlighting the importance of early recognition, prompt treatment, and timely referral to prevent fatalities. The&#13;
administration of anti-snake venom (ASV) is identified as the most critical intervention, though lack of awareness in&#13;
rural areas complicates management. The study calls for targeted public health campaigns to educate communities&#13;
about early snakebite recognition and the role of ASV. It also stresses the need for region-specific protocols&#13;
and improved healthcare access, emphasizing the importance of referral systems for advanced interventions&#13;
like hemodialysis and intubation. Overall, the study advocates for enhanced public awareness and healthcare&#13;
infrastructure to reduce snakebite incidence and mortality in rural populations.&#13;
Keywords Snake bite, Hemotoxic, Neurotoxic, ASV, Plasmapheresis, HBOT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134692">
                <text>Parvathy Sasidharan1&#13;
&#13;
, Nidhi Kaeley1*, Prakash Mahala1&#13;
&#13;
, Jewel Rani Jose1&#13;
&#13;
, Takshak Shankar1&#13;
&#13;
, Silpa Santhalingan2&#13;
,&#13;
&#13;
Ankit Sharma1&#13;
&#13;
, Balwant Kumar1&#13;
&#13;
, Mallapu Ajay Kumar1&#13;
&#13;
and Minakshi Dhar1</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="134693">
                <text>https://doi.org/10.1186/s12245-024-00796-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="134694">
                <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="134695">
                <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="134696">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134697">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134698">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15459">
        <name>Snake bite, Hemotoxic, Neurotoxic, ASV, Plasmapheresis, HBOT</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12606" public="1" featured="1">
    <fileContainer>
      <file fileId="12662">
        <src>https://repository.horizon.ac.id/files/original/338b13d953a24f49a0595516b633f798.pdf</src>
        <authentication>5c488a563dc7213271c74da591507415</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="134679">
                <text>From thrombosis to tamponade: unveiling&#13;
severe pericardial effusion in a misdiagnosis&#13;
case</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134680">
                <text>Pericardial effusion, Tamponade, Thromboembolism, Misdiagnosis, Case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134681">
                <text>Abstract&#13;
Background Anticoagulants increase the risk of cardiac tamponade in patients with pericardial effusion (PE).&#13;
Therefore, inappropriate administration of them in the presence of PE can lead to a catastrophic outcome. This study&#13;
presents a patient with a provisional misdiagnosis of venous thromboembolism (VTE).&#13;
Case Presentation An 83-year-old Iranian female was transferred to the emergency department of a tertiary&#13;
cardiology hospital complaining of neck swelling concomitant with chest pain and dyspnea. The patient had been&#13;
diagnosed with jugular vein thrombosis in another local center, and since the chief complaint was neck swelling, she&#13;
underwent Doppler sonography, and the diagnosis was confirmed. Subsequently, the treatment with unfractionated&#13;
heparin was started. After 5 h, considering the worsening of symptoms with the suspicious diagnosis of COVID-19&#13;
based on her symptoms and laboratory data, a chest computed tomography scan was requested, which showed a&#13;
massive PE. Subsequently, transthoracic echocardiography confirmed the diagnosis. The patient was immediately&#13;
transferred to the operating room and underwent pericardiotomy. The post-surgery period was uneventful, and she&#13;
was discharged 5 days later.&#13;
Conclusion Patients with viral infections, specifically COVID-19, are at risk of undiagnosed severe pericardial&#13;
effusions. Venous stasis in the jugular veins due to PE can mimic jugular vein thromboembolism, causing a wrong&#13;
diagnosis. Since treating thrombosis can exacerbate tamponade to hemodynamic instability and collapse, sufficient&#13;
investigation before starting anticoagulants is necessary.&#13;
Clinical key message Distinguishing VTE from PE is not always straightforward. Therefore, it is important to ensure&#13;
physicians have reached an appropriate level of certainty about their diagnosis by performing precise diagnostics&#13;
before using anticoagulants. Mismanagement with anti-thrombotics can result in catastrophic consequences.&#13;
Therefore, taking an accurate history, performing a precise physical examination, and using rapid and available&#13;
diagnostic modalities can avoid delays in definitive management.&#13;
Keywords Pericardial effusion, Tamponade, Thromboembolism, Misdiagnosis, 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="134682">
                <text>Amin Bagheri1,2, Morteza Sheikhi Nooshabadi1,3, Pouya Ebrahimi2&#13;
&#13;
, Roozbeh Nazari1&#13;
&#13;
, Pedram Ramezani4&#13;
and&#13;
&#13;
Toktam Alirezaei5*</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="134683">
                <text>https://doi.org/10.1186/s12245-024-00794-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="134684">
                <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="134685">
                <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="134686">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134687">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134688">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15458">
        <name>Pericardial effusion, Tamponade, Thromboembolism, Misdiagnosis, Case report</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12604" public="1" featured="1">
    <fileContainer>
      <file fileId="12660">
        <src>https://repository.horizon.ac.id/files/original/18528c7424ef9ea4247d71be5cd034ea.pdf</src>
        <authentication>62b60c5a93f9078e9dd98eaea7c13dc8</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="134659">
                <text>Seizure aggravation by ampicillin/sulbactam in an elderly patient with status epilepticus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134660">
                <text>Seizure aggravation, Antibiotic-associated encephalopathy, Ampicillin/sulbactam, Status epilepticus,&#13;
Continuous electroencephalogram monitoring, Critical care EEG, Density spectral array</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134661">
                <text>Abstract&#13;
Background Ampicillin/sulbactam (ABPC/ SBT) is one of the most common β-lactam antibiotics for patients with&#13;
status epilepticus complicated with aspiration pneumonia. It is known that β-lactam antibiotics such as penicillin&#13;
aggravate epileptic seizures or status epilepticus. Here, we investigated whether ABPC/SBT aggravates seizures using&#13;
electroencephalography (EEG) monitoring.&#13;
Case presentation An 84-year-old male with status epilepticus who presented with a new onset of clonic seizures&#13;
mainly of his left side and underwent continuous video EEG was analyzed. He had been suffering from severe&#13;
ulcerative colitis and infectious enteritis, delirium, atrial fibrillation and deep venous thrombosis. His cerebrospinal&#13;
fluid analysis was unremarkable. Four days after starting levetiracetam, he had a cluster of seizures with impaired&#13;
consciousness, consistent with status epilepticus. We started fosphenytoin and phenobarbital. We also administered&#13;
ABPC/SBT twice a day, ten times in total, for aspiration pneumonia while monitoring the patient. He died twelve&#13;
days after the seizure onset. We analyzed the number and duration of seizures in two hours before and after starting&#13;
ABPC/SBT for each administration using EEG with trendgraph. After administration of ABPC/SBT, number of seizures&#13;
significantly increased from 3.2±4.7 to 7.3±9.7 (mean±SD, p=0.047, Wilcoxson’s signed-rank test) per 2 h. Duration&#13;
of seizures showed a tendency of increase from 199±275 to 406±536 s (p=0.079).&#13;
Conclusions In this elderly male patient with status epilepticus, administration of ABPC/SBT aggravated his seizures.&#13;
EEG monitoring using a trendgraph is useful for evaluation of seizure severity and for analysis of causative factors.&#13;
Keywords Seizure aggravation, Antibiotic-associated encephalopathy, Ampicillin/sulbactam, Status epilepticus,&#13;
Continuous electroencephalogram monitoring, Critical care EEG, Density spectral array</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134662">
                <text>Kaoru Obata1,2, Masako Kinoshita3* , Akiyo Shinde1&#13;
&#13;
and Toshihiko Suenaga1</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="134663">
                <text>https://doi.org/10.1186/s12245-024-00793-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="134664">
                <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="134665">
                <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="134666">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134667">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134668">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15457">
        <name>Seizure aggravation, Antibiotic-associated encephalopathy, Ampicillin/sulbactam, Status epilepticus,</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12603" public="1" featured="1">
    <fileContainer>
      <file fileId="12659">
        <src>https://repository.horizon.ac.id/files/original/256ea8b2dead13d9b5b3595199f04475.pdf</src>
        <authentication>14f7ae385a32a450e0a52469113f6077</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="134649">
                <text>Coexistence of adenomyomatosis in a left- sided gallbladder: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134650">
                <text>Left-sided gallbladder, Adenomyomatosis, Congenital anomaly, Cholecystectomy, Hepatocellular&#13;
carcinoma</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134651">
                <text>Abstract&#13;
Introduction The coexistence of gallbladder (LSG) and adenomyomatosis (ADM) is extremely uncommon&#13;
presenting a novel clinical dilemma that has not been previously documented. LSG refers to a anomaly where the&#13;
gallbladder is situated to the left of the round ligament deviating from its usual position. This anomaly is rare, with&#13;
reported occurrences ranging between 0.04% and 1.1%. Identifying LSG before surgery poses challenges. It is often&#13;
discovered incidentally during procedures necessitating surgical expertise to safely manage anatomical variations.&#13;
Case presentation We report an old man with a history of hepatitis C, carcinoma and liver cirrhosis complained&#13;
of sudden epigastric pain. A CT scan revealed the presence of an LSG, which’s a congenital anomaly. During the&#13;
cholecystectomy procedure surgeons encountered variations and observed the existence of ADM complicating the&#13;
operation. The patient recovered smoothly post surgery.&#13;
Discussion This case shows how complicated it can be to diagnose and treat the combination of LSG and ADM.&#13;
Identifying these conditions before surgery is tough so surgeons often have to adjust their approach during the&#13;
operation. Although laparoscopic cholecystectomy for LSG is usually safe it requires care to avoid problems like&#13;
bile duct injuries. For patients at risk a conservative treatment approach might be better. In cases where surgery is&#13;
necessary surgeons need to adapt their techniques to address the unique anatomical issues.&#13;
Conclusion The combination of LSG and ADM in a setting poses an intricate challenge. Surgeons need to be ready&#13;
to recognize and address these abnormalities effectively for the well being of the patient and favorable results. This&#13;
particular case highlights the importance of staying alert and flexible during surgery when dealing with gallbladder&#13;
variations.&#13;
Keywords Left-sided gallbladder, Adenomyomatosis, Congenital anomaly, Cholecystectomy, Hepatocellular&#13;
carcinoma</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134652">
                <text>Mohamed Tolba1&#13;
&#13;
, Hadeer Hafez2* and John Adel3</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="134653">
                <text>https://doi.org/10.1186/s12245-024-00785-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="134654">
                <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="134655">
                <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="134656">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134657">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134658">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15456">
        <name>Left-sided gallbladder, Adenomyomatosis, Congenital anomaly, Cholecystectomy, Hepatocellular carcinoma</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12602" public="1" featured="1">
    <fileContainer>
      <file fileId="12658">
        <src>https://repository.horizon.ac.id/files/original/c26685388a2290886c3622fdd6528c8c.pdf</src>
        <authentication>c843988ffd042dace87f665a4640e76e</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="134639">
                <text>Emergency department crowding in the Netherlands; evaluation of a real-time ambulance diversion dashboard</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134640">
                <text>Crowding, Emergency Service, Ambulance diversions, Emergency department, Emergency room,&#13;
Humans, The Netherlands</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134641">
                <text>Abstract&#13;
Background Emergency department (ED) crowding is a growing concern worldwide and associated with negative&#13;
effects. In 2013, 68% of Dutch ED-managers experienced crowding on several days of the week. This resulted into the&#13;
introduction in phases of an ambulance diversion dashboard, in order to influence ED input. Increasing numbers of&#13;
Dutch EDs have implemented this dashboard, visualizing regional ambulance diversions by means of a traffic light.&#13;
Methods This is a descriptive study of a nationwide online survey of Dutch EDs, conducted between January and&#13;
October 2023. It included both qualitative and quantitative questions. The outcomes and analysis are derived from&#13;
descriptive data of respondents’ experience of crowding as well as their usage and perceived effectiveness of the&#13;
ambulance diversions dashboard.&#13;
Results At the time of the survey, 62 of 82 Dutch EDs (75.6%) actually used the dashboard, of which 56 EDs&#13;
responded (90.3% response rate). 69.7% Of ED managers experienced ED crowding more than three times a week.&#13;
Of the respondents using the dashboard, 52.8% reported it only occasionally alleviates ED inflow. The purported&#13;
reasons are the limited number of patients affected by the red light (ambulance diversion) and the presence of&#13;
regional crowding. The effects of the orange light (impending ambulance diversion) on ED input differ greatly&#13;
among hospitals, mostly due to their own internal agreements. In accordance, many respondents (53.6%) expressed&#13;
dissatisfaction with the resources available to them to alleviate crowding.&#13;
Conclusion After conducting a national survey, ED crowding is reported as a persisting nationwide problem with its&#13;
prevalence largely unchanged since the introduction of the ambulance diversion dashboard. Most hospitals reported&#13;
having insufficient resources to alleviate it. The effects of the ambulance diversion dashboard to decrease crowding&#13;
are apparently limited because it affects a small portion of total ED presentations and because of the influence&#13;
of regional crowding. The main function of the orange light is to increase ED throughput and output rather than&#13;
reducing ED input.&#13;
Keywords Crowding, Emergency Service, Ambulance diversions, Emergency department, Emergency room,&#13;
Humans, The Netherlands</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134642">
                <text>E. C. M. Baan-Kooman1*, S. Mol1&#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="134643">
                <text>https://doi.org/10.1186/s12245-024-00784-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="134644">
                <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="134645">
                <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="134646">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134647">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134648">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12601" public="1" featured="1">
    <fileContainer>
      <file fileId="12657">
        <src>https://repository.horizon.ac.id/files/original/c7355f2a7556ccd339abc6a53bf4e97b.pdf</src>
        <authentication>31b9ba42d8d5e1b10b66d206e50d9118</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="134629">
                <text>Management of acute ischemic stroke in the emergency department: optimizing the brain</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134630">
                <text>Acute ischemic stroke, Blood pressure management, Thrombolysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134631">
                <text>Abstract&#13;
Acute ischemic stroke is a devastating condition that afflicts more than 12 million people every year. Globally, stroke&#13;
&#13;
is the 2nd leading cause of death and 3rd leading cause of disability worldwide. While not all patients can avail them-&#13;
selves of existing acute therapies, all patients can benefit from brain optimization measures. This paper details the 12&#13;
&#13;
steps in the management of acute ischemic stroke in the emergency department.&#13;
Keywords Acute ischemic stroke, Blood pressure management, Thrombolysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134632">
                <text>Latha Ganti1,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="134633">
                <text>https://doi.org/10.1186/s12245-024-00780-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="134634">
                <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="134635">
                <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="134636">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134637">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134638">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15455">
        <name>Acute ischemic stroke, Blood pressure management, Thrombolysis</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
