<?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?output=omeka-xml" accessDate="2026-04-26T05:51:00+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>13010</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="13272" public="1" featured="1">
    <fileContainer>
      <file fileId="13326">
        <src>https://repository.horizon.ac.id/files/original/4246823311a6986dfa4c6f3d3e5739bc.pdf</src>
        <authentication>2c3560437352def72501923772afa559</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="141137">
                <text>A unique case of atraumatic splenic haematoma likely caused by increased intra- abdominal pressure: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141138">
                <text>Splenic haematoma, Intra-abdominal pressure, Atraumatic</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141139">
                <text>Abstract&#13;
Background The spleen is a highly vascular organ, and splenic haematoma is a complication most commonly&#13;
due to abdominal trauma. Atraumatic splenic haematoma is much rarer and is often associated with underlying&#13;
pathology such as coagulopathies, malignancies, anatomical abnormalities or use of anticoagulants. This case report&#13;
highlights a unique case of atraumatic splenic haematoma in a young, healthy male, likely precipitated by increased&#13;
intra-abdominal pressure from persistent cough and weightlifting. It presents a rare cause of atraumatic splenic&#13;
haematoma that is not commonly documented in literature.&#13;
Case presentation The patient is a 21-year-old male, with no known chronic disease. He is a smoker and complained&#13;
of a persistent cough for the past three months. He presented the day after a gym session, with sudden left&#13;
hypochondrium tenderness with no history of trauma, vomiting or diarrhoea. Physical exam revealed normal vital&#13;
signs and generalized involuntary guarding over the entire abdomen. Initial point-of-care ultrasound was negative for&#13;
free fluid in the abdomen, but a repeat ultrasound three hours later turned positive. Computed tomography scans of&#13;
the abdomen, pelvis and mesenteric angiogram were then performed. They revealed intraperitoneal blood, a Grade&#13;
III splenic haematoma involving the superior pole of the spleen towards the inferior pole, but no active bleeding. The&#13;
patient was admitted for close monitoring. Initial laboratory evaluation did not show any coagulopathy or infection.&#13;
The patient remained hemodynamically stable throughout his inpatient stay, and was managed conservatively with&#13;
rest, analgesia, and empirical antibiotics. Serial haemoglobin levels remained stable, and his symptoms resolved&#13;
with analgesia. As he remained hemodynamically stable, no repeat imaging was performed inpatient. He was&#13;
subsequently discharged with instructions to avoid strenuous activities for 4 to 6 weeks. An outpatient follow-up was&#13;
arranged for him, to review symptoms and monitor haemoglobin level.&#13;
&#13;
Conclusion This case highlights a rare case of atraumatic splenic haematoma, possibly related to increased intra-&#13;
abdominal pressure from persistent coughing and weightlifting. Atraumatic splenic haematoma is rare and might&#13;
&#13;
be easily overlooked as a diagnosis in the emergency department. Emergency physicians should maintain a high&#13;
index of suspicion for splenic injury in patients presenting with unexplained left hypochondrium pain, and bedside&#13;
ultrasonography can aid in assessment and guide the need for further evaluation.&#13;
Keywords Splenic haematoma, Intra-abdominal pressure, Atraumatic</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141140">
                <text>Yu Xian Wong1,2*, Yi Wen Mathew Yeo1&#13;
&#13;
and Eleazar Ebreo1</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="141141">
                <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="141142">
                <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="141143">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141144">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141145">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16075">
        <name>Splenic haematoma, Intra-abdominal pressure, Atraumatic</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13271" public="1" featured="1">
    <fileContainer>
      <file fileId="13325">
        <src>https://repository.horizon.ac.id/files/original/797f2394ea18318add4e8eb424cdd4bf.pdf</src>
        <authentication>c850734968a9af6317fb2cf7bd2d3d26</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="141128">
                <text>A novel model for early prediction of in- hospital mortality in seawater drowning: the SNOP score</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141129">
                <text>Drowning, Hospital mortality, Seawater, Sodium, Oxygen saturation, Emergency medicine, Prognostic model</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141130">
                <text>Abstract&#13;
Background Drowning is a leading cause of preventable mortality worldwide; however, early in-hospital risk&#13;
stratification remains limited. Although tools such as the Szpilman score assist in early severity assessment, they may&#13;
not fully capture the evolving clinical status after admission. This study aimed to develop a simplified and objective&#13;
model based on readily available parameters to predict in-hospital mortality following seawater drowning.&#13;
Methods This retrospective study was conducted at a referral emergency department (ED) in northern Turkey&#13;
between July 1, 2011, and December 31, 2024. Of 190 patients initially included, 166 with complete clinical and&#13;
laboratory data were analyzed. Data were obtained from institutional and national health information systems.&#13;
Clinical, physiological, and biochemical variables were assessed. Predictors of in-hospital mortality were identified&#13;
using receiver operating characteristic (ROC) analysis and multivariable logistic regression. Variables with near-perfect&#13;
discrimination (e.g., GCS, pH, Szpilman score) were excluded to avoid overfitting.&#13;
Results Among the 166 patients, 34 (20.5%) died during hospitalization. CPR and endotracheal intubation rates&#13;
&#13;
were significantly higher among non-survivors (CPR: 97.1% vs. 0%; intubation: 97.1% vs. 2.3%; both p&lt;0.001). Non-&#13;
survivors also presented with lower GCS (median 3 vs. 15), lower arterial pH, and higher Szpilman scores (all p&lt;0.001).&#13;
&#13;
ROC analysis identified four potential predictors with AUC values between 0.90 and 0.95—pCO2, lactate, SpO2, and&#13;
sodium—all showing significant discriminatory capacity (p&lt;0.001). These variables were entered into a binary logistic&#13;
regression model, from which serum sodium (OR=2.110; 95% CI: 1.310–3.401; p=0.002) and SpO2 (OR=0.902; 95%&#13;
CI: 0.847–0.961; p=0.001) emerged as independent predictors. These formed the basis of the SNOP score (Saturation&#13;
and Natremia-based Outcome Predictor), a two-parameter logistic model demonstrating excellent performance:&#13;
AUC=0.996, sensitivity=99.0%, specificity=96.2%, and overall accuracy=98.4%.&#13;
Conclusion: The SNOP score is a simple, ED-specific tool for early prediction of in-hospital mortality in seawater&#13;
drowning. It complements existing assessment systems by incorporating objective, admission-based parameters.&#13;
Prospective multicenter validation is warranted to confirm its clinical applicability and support broader&#13;
implementation.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141131">
                <text>Kıvanç Öncü1* , Özhan Özcan2 , Şeyma Şi̇mşi̇rgi̇l Kara3 , Ayhan Parmaksız4 and Teoman Erşen5</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="141132">
                <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="141133">
                <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="141134">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141135">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141136">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16074">
        <name>Drowning, Hospital mortality, Seawater, Sodium, Oxygen saturation, Emergency medicine, Prognostic model</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13270" public="1" featured="1">
    <fileContainer>
      <file fileId="13324">
        <src>https://repository.horizon.ac.id/files/original/a8a94fe22c03ecb48466ca295d962cc5.pdf</src>
        <authentication>feded735a815f2c3a697a0f1f77bbfbf</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="141119">
                <text>Diagnostic performance of artificial intelligence for dermatological conditions: a systematic review focused on low- and middle-income countries to address resource constraints and improve access to specialist care</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141120">
                <text>Dermatology, Artificial Intelligence, Low- and Middle-Income Countries, Convolutional Neural Networks,&#13;
Diagnosis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141121">
                <text>Abstract&#13;
Background Artificial Intelligence (AI) has emerged as a transformative tool in dermatology, particularly in Low- and&#13;
Middle-Income Countries (LMICs), where healthcare systems face challenges such as a shortage of dermatologists&#13;
and limited resources. AI technologies, including deep learning models like Convolutional Neural Networks (CNNs),&#13;
have demonstrated potential in improving diagnostic accuracy for skin diseases, which contribute significantly to&#13;
the global disease burden. However, most research has focused on High-Income Countries (HICs), leaving gaps in&#13;
understanding AI's applicability and effectiveness in LMICs.&#13;
Aim/Objective This systematic review critically evaluates the application of AI in dermatological practice within&#13;
LMICs, assessing the performance of AI technologies across diverse geographic regions.&#13;
Methodology The review adhered to the Preferred Reporting Items for Systematic Reviews and Meta-Analyses&#13;
(PRISMA) guidelines and included 19 studies from databases including PubMed, Embase, and Cochrane. Eligible&#13;
studies evaluated AI applications in dermatology within LMICs, reporting metrics like sensitivity, specificity, precision,&#13;
and accuracy. Data extraction and quality assessment were performed independently by several reviewers using tools&#13;
like PROBAST and QUADAS-2. A qualitative synthesis as per SWiM guidelines was conducted due to heterogeneity in&#13;
study designs and outcomes.&#13;
Conclusion AI shows significant promise in enhancing dermatological diagnostics and expanding access to&#13;
dermatologic care in LMICs, with models achieving high accuracy (up to 99%) in tasks like skin cancer and infectious&#13;
disease detection. However, challenges such as underrepresented skin tones in datasets, limited clinical validation,</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141122">
                <text>Olivier Uwishema1* , Malak Ghezzawi1,2, Nicole Charbel1,3,4, Shireen Alawieh1,3,4, Subham Roy1,5, Magda Wojtara1,6,&#13;
Clyde Moono Hakayuwa1,7, Ibrahim Khalil Ja’afar1,8, Gerard Nkurunziza9&#13;
&#13;
and Manya Prasad10</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="141123">
                <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="141124">
                <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="141125">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141126">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141127">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16073">
        <name>Dermatology, Artificial Intelligence, Low- and Middle-Income Countries, Convolutional Neural Networks, Diagnosis</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13269" public="1" featured="1">
    <fileContainer>
      <file fileId="13323">
        <src>https://repository.horizon.ac.id/files/original/7967d4c922e6110814710d16819f22a4.pdf</src>
        <authentication>e5c5c32a6411ba21ce16e2d63127be1e</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="141110">
                <text>Characteristics of patients with ruptured abdominal aortic aneurysm who contacted out-of-hours primary care: a case-control study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141111">
                <text>Ruptured abdominal aortic aneurysm, Triage, Primary care, Out-of-hours primary care services, Emergency medicine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141112">
                <text>Abstract&#13;
Background Ruptured abdominal aortic aneurysm (rAAA) is rare but it is the second most frequently missed&#13;
diagnosis reported as sentinel adverse event (‘calamity’) at out-of-hours services in primary care (OHS-PC).&#13;
We aimed to identify characteristics that could be useful for telephone triage of suspected rAAA at the OHS-PC.&#13;
Methods In a matched case-control study (1:4 ratio), we compared patients with a missed rAAA (cases) to patients&#13;
with the same age and sex, and with similar entrance complaint (controls). Data were collected from OHS-PC triage&#13;
call recordings that were re-assessed by researchers blinded to the case-control status. Patient and call characteristics&#13;
were univariably assessed with conditional logistic regression analysis.&#13;
Results Twenty cases of missed rAAA between 2013 and 2023 were matched to 80 controls. 40% of the cases&#13;
presented with abdominal pain, and 35% with back pain. Cases compared to controls more often had a pain&#13;
onset&lt;12 h (odds ratio (OR) 15.2; 95%CI 1.9-123.8), reported more sweating (OR 10.1; 95% CI 1.2–86.9, p=0.035), more&#13;
often verbally expressed their concern (OR 13.6; 95%CI 3.0-61.3, p=0.001), and more often called during the night (OR&#13;
3.8; 95% CI 1.1–12.7, p=0.029).&#13;
Conclusions Recognition of rAAA at the OHS-PC remains challenging given its rare occurrence and lack of specific&#13;
symptoms. Nevertheless, this case-control study identified factors that could be useful in triage of patients calling the&#13;
OHS-PC with symptoms possibly indicating rAAA.&#13;
Keywords Ruptured abdominal aortic aneurysm, Triage, Primary care, Out-of-hours primary care services, Emergency&#13;
medicine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141113">
                <text>Carline J. van den Dries1*, Dave A. Dongelmans2&#13;
&#13;
, Maarten J. van der Laan3&#13;
&#13;
, Sonja Oomkens4&#13;
&#13;
, Eva Ouwendijk5&#13;
,&#13;
&#13;
Annelies Visser6&#13;
&#13;
, Frans H. Rutten1&#13;
&#13;
and Dorien L. M. Zwart1</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="141114">
                <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="141115">
                <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="141116">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141117">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141118">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16072">
        <name>Ruptured abdominal aortic aneurysm, Triage, Primary care, Out-of-hours primary care services, Emergency medicine</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13268" public="1" featured="1">
    <fileContainer>
      <file fileId="13322">
        <src>https://repository.horizon.ac.id/files/original/00ca79e87933fe358765daea09d0da37.pdf</src>
        <authentication>e64d269936eab2f19eb6e58bea3418f1</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="141101">
                <text>Does TXA reduce total volume of 24-hour blood products transfused in post-traumatic hemorrhage in a resource-constrained setting:Secondary analysis of a prospective cohort trauma study in South Africa.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141102">
                <text>Trauma, Injury, Hemorrhage, Shock, Tranexamic acid, TXA, Blood products, LMIC, South Africa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141103">
                <text>Abstract&#13;
Background Low- and middle-income countries bear a disproportionately large share of the global burden of&#13;
trauma, with hemorrhage as a leading cause of preventable mortality. Tranexamic acid has been shown to reduce&#13;
mortality in trauma, but no studies have investigated tranexamic acid’s effect on blood product consumption in&#13;
resource-constrained settings.&#13;
Methods A prospective secondary analysis was performed from data collected from ‘The Epidemiology and&#13;
Outcomes of Prolonged Trauma Care (EpiC)’ study, a multicenter observational study of major trauma patients within&#13;
the Western Cape of South Africa. Adult trauma patients with major hemorrhage who arrived at an EpiC study site&#13;
within 24 h of injury between March 2021 and December 2024 were included. The primary outcome was total blood&#13;
product administration within 24 h of injury. Treatment groups included patients who received tranexamic acid&#13;
within 3 h compared to those who did not. Multiple regression with inverse probability weighting was performed&#13;
to mitigate confounding. Subgroup analyses included patients with penetrating injuries, severe shock, presence of&#13;
intracranial hemorrhage and patients without head injury who received large-volume blood products.&#13;
Results A total of 1630 patients were included. Median total blood product volume was 760 mL. There was no&#13;
difference in blood volume between the two groups. There was no significant difference in blood product volumes&#13;
observed in all subgroup analysis.&#13;
Conclusion In a cohort of adult trauma patients with major hemorrhage, there was no difference in total blood&#13;
volume transfused within the first 24 h between patients who received tranexamic acid compared to those who did&#13;
not.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141104">
                <text>Chelsea Dymond1&#13;
&#13;
, Mengli Xiao2&#13;
, Lani Finck3&#13;
, Hendrick Lategan4&#13;
&#13;
, George Oosthuizen4&#13;
&#13;
, Shaheem de Vries5&#13;
,&#13;
&#13;
Janette Verster6&#13;
&#13;
, Craig Wylie7&#13;
&#13;
, EpiC Study Site Collaborators8&#13;
&#13;
, Willem Stassen9&#13;
&#13;
, Joseph Maddry10, Steven Schauer11,&#13;
&#13;
Julia Dixon3&#13;
and Nee-Kofi Mould-Millman3*</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="141105">
                <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="141106">
                <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="141107">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141108">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141109">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16071">
        <name>Trauma, Injury, Hemorrhage, Shock, Tranexamic acid, TXA, Blood products, LMIC, South Africa</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13267" public="1" featured="1">
    <fileContainer>
      <file fileId="13321">
        <src>https://repository.horizon.ac.id/files/original/93b7dae4ddc4ed2a9e88975a3463e39f.pdf</src>
        <authentication>a69eff6cf454668d57c9fffe7c8ecca8</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="141092">
                <text>Delayed diagnosis of aortic dissection: the overlooked clues on chest X-ray</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141093">
                <text>Acute chest pain, Acute aortic dissection, Chest radiography, Pleuritis, Differential diagnosis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141094">
                <text>Abstract&#13;
Background Acute aortic dissection (AD) is a life-threatening vascular emergency requiring immediate intervention,&#13;
with mortality rates increasing by 1–2% per hour post-onset. The pathophysiology involves an intimal tear that&#13;
permits blood to enter the medial layer, forming a false lumen that may expand and compromise branch vessels&#13;
and end-organ perfusion. Current guidelines from the European Society of Cardiology (ESC), American College of&#13;
Cardiology (ACC), and American Heart Association (AHA) highlight the necessity of risk stratification based on clinical&#13;
features (e.g., tearing pain, pulse deficits), predisposing factors (e.g., hypertension), and D-dimer levels, followed by&#13;
confirmatory imaging with transthoracic echocardiography (TTE) or computed tomography angiography (CTA).&#13;
Despite advancements in imaging, chest radiography (CXR) remains underutilized; however, key findings—such as&#13;
mediastinal widening (≥5 cm at the aortic knob), abnormal aortic contour, and displaced intimal calcifications—can&#13;
offer critical diagnostic information.&#13;
Case report A young male patient presented with acute chest pain following strenuous exertion. Initial outpatient&#13;
evaluation, including complete blood count (CBC), liver function tests (LFTs), renal function tests (RFTs), cardiac&#13;
enzymes, and chest X-ray (CXR), yielded nondiagnostic results, leading to his discharge with analgesics. Three&#13;
days later, during a national holiday when outpatient clinics were closed, the patient returned to the emergency&#13;
department (ED) with persistent chest pain. A meticulous review of the initial CXR by the emergency physician&#13;
revealed mediastinal widening (measuring 8.5 cm) and an abnormal contour of the aorta. Subsequent emergency&#13;
computed tomography angiography (CTA) confirmed the diagnosis of a Stanford type B aortic dissection.&#13;
Conclusions This case underscores two critical learning points: (1) the diagnostic pitfalls associated with atypical&#13;
early presentations of aortic dissection, and (2) the often underappreciated value of meticulous interpretation of chest&#13;
&#13;
X-rays in the evaluation of acute chest pain, particularly when initial studies yield unremarkable results. The three-&#13;
day diagnostic delay emphasizes the necessity of maintaining a high index of suspicion for aortic dissection, even in&#13;
&#13;
young patients lacking classic risk factors.&#13;
Keywords Acute chest pain, Acute aortic dissection, Chest radiography, Pleuritis, Differential diagnosis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141095">
                <text>Yao Chen1&#13;
, Wenjin Wang2&#13;
, Lian Lin3&#13;
and Zhankai Tang2*</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="141096">
                <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="141097">
                <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="141098">
                <text>PDF</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141099">
                <text>ENGLISH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141100">
                <text>TEXT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16070">
        <name>Acute chest pain, Acute aortic dissection, Chest radiography, Pleuritis, Differential diagnosis</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13266" public="1" featured="1">
    <fileContainer>
      <file fileId="13320">
        <src>https://repository.horizon.ac.id/files/original/6ea14fa03122d26d21e5275515857062.pdf</src>
        <authentication>24ed759caa40185756dbcb2e922a9624</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="141083">
                <text>Knowledge and experience of local emergency care staff on stroke recognition and acute care in the United Arab Emirates</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141084">
                <text>Acute stroke, Emergency department staff, Stroke symptoms, Risk factors, And knowledge assessment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141085">
                <text>Introduction Cerebrovascular diseases are among the top three causes of death in the United Arab Emirates. The&#13;
acute stroke care survey among emergency care personnel in Alain City aims to assess the experience, knowledge&#13;
and attitude of emergency department staff about acute stroke care to identify areas for educational and training&#13;
interventions.&#13;
Method This is an observational cross-sectional Face-to-Face electronic survey of the Emergency care doctors and&#13;
nurses across four emergency/urgent care centres in Alain, the United Arab Emirates. The survey was completed&#13;
between 4th August 2023 to 15th October 2024 using a locally validated survey questionnaire.&#13;
Results Of the 215 participants in the study, 178 (83%) completed the survey of which 56% were Physicians.&#13;
Two-thirds (66.1%) of the responders work in a tertiary care centre and about a third 49 (35.4%) of the responders&#13;
personally cared for more than ten stroke or TIA patients in the past three months. Over 75% of the responders&#13;
identified facial droop, unilateral arm or leg weakness and slurred speech as symptoms of acute stroke. Only 61%&#13;
of the responders recognised atrial fibrillation as a risk factor. The overall mean (SD) knowledge score was 59.76&#13;
(23.74) for physicians compared with 52.9 (21.35) for nurses (P=0.054). There was a significant difference in the&#13;
overall mean (SD) knowledge score between responders from tertiary and secondary centres. (59.9 (21.8) versus 51.8&#13;
(21.9) respectively, P=0.019. Responders with &lt;2 years of experience achieved a significantly lower mean (SD) score&#13;
compared with responders with &gt;2 years of experience in all domains (47.1 (27.34) compared with 60.54 (20.1) for&#13;
those with &gt;10 years of experience, P=0.008).&#13;
Conclusions This study identified significant knowledge gaps among staff working in our stroke care system. These&#13;
can be addressed by regular stroke update training for all front-line staff including those working at secondary centres&#13;
with limited experience of daily stroke care.&#13;
Keywords Acute stroke, Emergency department staff, Stroke symptoms, Risk factors, And knowledge assessment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141086">
                <text>Mohammed Alkuwaiti1,2, Azhar Talal3&#13;
&#13;
, Emad Masuadi3&#13;
&#13;
, Ghada Albluwi1&#13;
&#13;
, Abdulla Alkuwaiti2&#13;
and&#13;
&#13;
David Olukolade Alao1,4*</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="141087">
                <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="141088">
                <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="141089">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141090">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141091">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16069">
        <name>Acute stroke, Emergency department staff, Stroke symptoms, Risk factors, And knowledge assessment</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13265" public="1" featured="1">
    <fileContainer>
      <file fileId="13319">
        <src>https://repository.horizon.ac.id/files/original/1e0781b26d4b4fc071835b33729d47bd.pdf</src>
        <authentication>be132e745069cf1c9708e0e7982f9b75</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="141074">
                <text>When methylene blue fails: a case of methemoglobinemia induced&#13;
by azoxystrobin and propiconazole managed by exchange transfusion</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141075">
                <text>(MeSH): azoxystrobin, Exchange transfusion, whole blood, Methemoglobinemia, Methylene blue,&#13;
Propiconazole</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141076">
                <text>Abstract&#13;
Background Methemoglobinemia is a potentially life-threatening condition resulting from the oxidation of&#13;
hemoglobin’s iron moiety from ferrous (Fe2+) to ferric (Fe3+). Clinical features include cyanosis unresponsive to oxygen&#13;
therapy, chocolate-colored blood, and a marked saturation gap between pulse oximetry and arterial blood gas.&#13;
Methylene blue remains the cornerstone of treatment; however, in rare instances, patients may exhibit refractory&#13;
responses necessitating advanced interventions. Literature documenting methemoglobinemia due to fungicides like&#13;
azoxystrobin and propiconazole remains scarce.&#13;
Case presentation A young female presented with altered sensorium, shock, and hypoxia following the ingestion of&#13;
a fungicide containing azoxystrobin and propiconazole. Despite a PaO2 of 400 mmHg on ABG, pulse oximetry showed&#13;
83% oxygen saturation, raising suspicion of dyshemoglobinemia. Methemoglobin levels were elevated at 80.7%. She&#13;
was treated with intravenous methylene blue. While an initial decline in methemoglobin levels to 4% was observed,&#13;
relapse occurred within 12 h. On day three, therapeutic red blood cell exchange transfusion was performed resulting&#13;
in a reduction of methemoglobin levels to 14.2%. Despite aggressive measures, she succumbed to refractory shock&#13;
on day five of admission.&#13;
Conclusion This report presents likely the first documented case of fatal methemoglobinemia due to ingestion&#13;
of azoxystrobin and propiconazole—a combination fungicide widely used in agriculture. The case highlights&#13;
the limitations of standard therapies like methylene blue in severe poisoning and underscores the need for early&#13;
consideration of exchange transfusion. With the increasing use of such agents in rural communities, clinicians must&#13;
maintain vigilance for unusual toxicities and ensure timely escalation in refractory cases.&#13;
Keywords (MeSH): azoxystrobin, Exchange transfusion, whole blood, Methemoglobinemia, Methylene blue,&#13;
Propiconazole</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141077">
                <text>Rajat Goyal1*, Rushabh Bora1&#13;
&#13;
, Anand Jain1&#13;
&#13;
and Gopal Krishana Bohra1,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="141078">
                <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="141079">
                <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="141080">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141081">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141082">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13264" public="1" featured="1">
    <fileContainer>
      <file fileId="13318">
        <src>https://repository.horizon.ac.id/files/original/7005f0f05bf4f4a1dc67fe98866ea42c.pdf</src>
        <authentication>20001edd47333cce29f58b31b01e5ed9</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="141065">
                <text>Impact of telemedicine on mortality, hospital admissions, and length of stay in pediatric emergencies: a systematic review and meta- analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141066">
                <text>Telemedicine, Pediatric, Emergency, Admission, Mortality, Meta-analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141067">
                <text>Abstract&#13;
Background Pediatric emergencies pose significant challenges in healthcare. Telemedicine offers a promising&#13;
solution by enabling remote assessments, improving specialist access, reducing unnecessary ER visits and admissions,&#13;
optimizing resources, and enhancing patient satisfaction. This systematic review and meta-analysis uniquely aimed to&#13;
quantify the effect of telemedicine on key outcomes in pediatric emergency and post-emergency care.&#13;
Methods We searched PubMed, Scopus, the Cochrane Library, and Web of Science to identify studies focusing on&#13;
the impact of telemedicine in pediatric emergency settings. Both single- and double-arm studies were included.&#13;
Statistical analysis was performed using RevMan and CMA software, with a random-effects model applied to all&#13;
analyses. We assessed differences in admissions, hospital length of stay (LOS), and mortality. Event rates were&#13;
calculated for single-arm analyses, and risk ratios and mean differences were used for dichotomous and continuous&#13;
outcomes in double-arm analyses.&#13;
Results A total of 23 studies were included. Telemedicine significantly reduced hospital LOS (MD = -1.01, 95% CI:&#13;
-1.3 to -0.71) and overall mortality (RR=0.17, 95% CI: 0.13 to 0.24). The admission rates to the emergency department,&#13;
hospital ward, and pediatric intensive care unit (PICU) were comparable between both groups. Single-arm analysis&#13;
revealed that telemedicine was associated with an ED admission rate of 18% (95% CI: 5.2–47%), a hospital ward&#13;
admission rate of 16.7% (95% CI: 4.6–45.7%), and a pooled mortality rate of 1.8% (95% CI: 1–3.3%).&#13;
Conclusions Telemedicine appears to be an effective tool in pediatric emergency care. While our analysis suggests&#13;
reductions in hospital length of stay and mortality, these findings should be interpreted with caution due to variability&#13;
and potential confounding across studies. The impact on admission rates remains inconclusive. Nonetheless,&#13;
telemedicine offers a promising approach to enhancing healthcare delivery and optimizing resource use in pediatric&#13;
emergency and early post-emergency settings.&#13;
Keywords Telemedicine, Pediatric, Emergency, Admission, Mortality, Meta-analysis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141068">
                <text>Amani N. Alansari1* , Mohamed Sayed Zaazouee2 , Marwa Messaoud3,4,5 , Salma Mani3 ,&#13;
Alaa Ahmed Elshanbary6 and Hanan Youssif Mohamed7</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="141069">
                <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="141070">
                <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="141071">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141072">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141073">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13263" public="1" featured="1">
    <fileContainer>
      <file fileId="13317">
        <src>https://repository.horizon.ac.id/files/original/30e193827a65ad136147ea6507493452.pdf</src>
        <authentication>4c5e00be397d4517b88f3434d836c294</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="141056">
                <text>Review of current knowledge regarding usage of pre-hospital heart rate variability and complexity in triage and added value for predicting the need for life-saving interventions</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141057">
                <text>Analysis of heart rate variability metrics has shown added accuracy in pre-hospital trauma triage.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141058">
                <text>Abstract&#13;
Background &amp; aim Analysis of heart rate variability metrics has shown added accuracy in pre-hospital trauma triage.&#13;
These metrics include heart rate variability (HRV), meaning oscillations in the time interval between heartbeats, and&#13;
heart rate complexity (HRC), which assesses intricate patterns of heart rate over time. This review article evaluates&#13;
current knowledge regarding HRV and HRC and prediction of a subsequent life-saving intervention (LSI), an&#13;
&#13;
intervention executed by trained medical personnel to prolong the life of the patient. Our primary focus was on pre-&#13;
hospital patients and the utility of HRV and HRC when added to existing trauma triage scores or vital signs such as&#13;
&#13;
heart rate (HR).&#13;
Methode A literature search was carried out by searching the MEDLINE database via the PubMed website for original&#13;
research published in English from 2008 to 2023. The combinations of search terms applied yielded 18 original studies&#13;
of which only six met our criteria. We included another study as it contributed original research beneficial to our&#13;
article.&#13;
Results The studies showed a statistically significant increase in the ∆Area Under Curve (AUC) between 0.14 and&#13;
0.40 for predicting risk of LSI when adding the two heart rate variability metrics to existing trauma triage scores or&#13;
vital signs such as HR. Calculation of HRV and/or HRC could be conducted using ECG recording hardware already&#13;
accessible in most emergency pre-hospital settings with less ECG noise and therefore higher quality ECG data over&#13;
time.&#13;
Conclusion Both HRV and HRC showed potential for increasing ∆AUC in predicting risk of LSI when added to existing&#13;
risk triage scores. Calculation of HRV and HRC could potentially be conducted using a preexisting hardware in most&#13;
emergency pre-hospital settings.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141059">
                <text>Christoffer B. Hedegaard1*, Kasper Iversen1,2,3, Fredrik Folke1,3,4, Morten Lock-Hansen6&#13;
&#13;
, Carolina Malta Hansen1,3,4 and&#13;
&#13;
Jannik Pallisgaard5</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="141060">
                <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="141061">
                <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="141062">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141063">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141064">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="16068">
        <name>Analysis of heart rate variability metrics has shown added accuracy in pre-hospital trauma triage.</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
