<?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=23" accessDate="2026-04-22T12:13:58+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>23</pageNumber>
      <perPage>10</perPage>
      <totalResults>255</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="12659" public="1" featured="1">
    <fileContainer>
      <file fileId="12715">
        <src>https://repository.horizon.ac.id/files/original/57d45a9fc7be17534c4880045dd792f5.pdf</src>
        <authentication>31603a8bc59af9ae1b3cfb7e48d520f0</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="135257">
                <text>The association between anion gap and prognosis in patients myocardial&#13;
infarction with congestive heart failure: a retrospective analysis of the MIMIC-IV database</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135258">
                <text>Anion gap, Heart failure post myocardial infarction, Prognosis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135259">
                <text>Abstract&#13;
Background Elevated serum anion gap at hospital admission is often linked to a poor prognosis in critically ill&#13;
patients, but there is insufficient data on this correlation in patients with acute myocardial infarction accompanied&#13;
by heart failure. In this study, we aimed to determine the relationship between serum admission AG and all-cause&#13;
mortality in patients with acute myocardial infarction accompanied by heart failure.&#13;
Methods We conducted a retrospective analysis of data within the MIMIC-IV database. Serum AG was collected at&#13;
ICU admission, and all-cause mortality after discharge was analyzed. Multivariable Cox proportional hazards regression&#13;
models and Kaplan-Meier survival curve analyses were used to assess the relationship between serum AG and&#13;
myocardial infarction accompanied by heart failure as well as all-cause mortality.&#13;
Results A total of 943 patients with acute myocardial infarction complicated by heart failure were included in the&#13;
study. The all-cause mortality rate after discharge was 24.7% and 18.9%. Multivariable analysis, adjusted for potential&#13;
confounders, indicated that compared to low serum AG levels (&lt;12 mmol/L), high serum AG levels (&gt;17 mmol/L)&#13;
were associated with an increased risk of all-cause mortality. Similarly, Kaplan-Meier survival curves also indicated that&#13;
patients with higher serum AG levels had lower survival rates. Stratified analysis further showed that the association&#13;
between higher serum AG levels and in-hospital all-cause mortality was observed across different subgroups based&#13;
on stratification variables.&#13;
Conclusions In patients with acute myocardial infarction complicated by heart failure, elevated serum AG levels at&#13;
ICU admission are associated with an increased risk of all-cause mortality.&#13;
Keywords Anion gap, Heart failure post myocardial infarction, Prognosis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135260">
                <text>Muzheng Li1†, Chenyang Li2†, Jihua Wang1&#13;
&#13;
and Qinghua Yuan1*</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="135261">
                <text>https://doi.org/10.1186/s12245-025-00828-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="135262">
                <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="135263">
                <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="135264">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135265">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135266">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15514">
        <name>Anion gap, Heart failure post myocardial infarction, Prognosis</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12657" public="1" featured="1">
    <fileContainer>
      <file fileId="12713">
        <src>https://repository.horizon.ac.id/files/original/fca2a0b6e535ff1e8fa5bd7568fe2ff2.pdf</src>
        <authentication>c0857844dc37d15e60b09a3b7cf0bb2a</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="135235">
                <text>Primary diagnosis of atrioventricular pseudo‐block in a neonate with definitive diagnosis of long QT syndrome: diagnostic considerations and therapeutic approaches</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135236">
                <text>Atrioventricular block, Arrhythmias, Case report, Long QT syndrome, Sudden cardiac death</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135237">
                <text>Abstract&#13;
Introduction Long QT syndrome (LQTS) is a potentially lethal medical condition that might never be diagnosed&#13;
&#13;
and cause sudden cardiac death. It is mainly caused by mutation in electrolyte transporter genes. Due to the sig-&#13;
nificant difference in the treatment approach of heart block and other rhythm disorders that mimic this condition,&#13;
&#13;
it is necessary to discriminate these conditions. The occurrence of pseudo-block in electrocardiography features&#13;
&#13;
but without disturbance in the function of the conduction system can mask the definite diagnosis of the real underly-&#13;
ing disorder, and this issue leads to the selection of an unfavorable treatment protocol and sometimes the sudden&#13;
&#13;
death of the patient.&#13;
&#13;
Case presentation We described an infant who showed evidence of atrioventricular (AV) block in initial electrocar-&#13;
diography (ECG) on his first day, but in further evaluations, the final diagnosis of LQTS was raised. The patient recov-&#13;
ered after performing the treatment protocol, which included Mexiletine and beta-blockers. After the genetic test&#13;
&#13;
of the parents and the patient, it was determined that a defective allele of the gene had caused the condition.&#13;
Conclusion Our report shows the importance of timely differentiation between heart block and LQTS in neonates&#13;
and choosing the correct treatment approach to faster patient recovery and prevent sudden death.&#13;
&#13;
Clinical key message Primary diagnosis of LQTS in neonates might not be a straightforward process due to resem-&#13;
bling AV pseudo-block and can cause misleading diagnosis and treatment. Long QT syndrome has several nonspecific&#13;
&#13;
presentations. They might be asymptomatic until adulthood and be diagnosed after sudden cardiac death. Preventive&#13;
measures such as timely initiation of medications, ICD or PPM implantation, and continuous observation by caregivers&#13;
are the mainstay of survival and quality of life improvement.&#13;
Keywords Atrioventricular block, Arrhythmias, Case report, Long QT syndrome, Sudden cardiac death</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135238">
                <text>Mohammadrafie Khorgami1&#13;
&#13;
, Fatemeh Naderi2* and Samira Kalayinia3</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="135239">
                <text>https://doi.org/10.1186/s12245-025-00827-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="135240">
                <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="135241">
                <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="135242">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135243">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135244">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15511">
        <name>Atrioventricular block, Arrhythmias, Case report, Long QT syndrome, Sudden cardiac death</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12656" public="1" featured="1">
    <fileContainer>
      <file fileId="12712">
        <src>https://repository.horizon.ac.id/files/original/bb0fdfb6ae428d5c8990c562536c095c.pdf</src>
        <authentication>6422f07a9301ea83a0be286a57b6ed91</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="135225">
                <text>Characteristics, outcomes, and prognostic factors in patients with penetrating and blunt traumatic diaphragmatic injury: a nationwide retrospective cohort study in Japan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135226">
                <text>Traumatic diaphragmatic injury (TDI), Penetrating TDI (PTDI), Blunt TDI (BTDI), Japan Trauma Data Bank&#13;
(JTDB), Associated injury, Severe concomitant injury, Independent predictor of mortality, Epidemiology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135227">
                <text>Abstract&#13;
Background Traumatic diaphragmatic injury (TDI) is well-known worldwide as rare and life-threatening. However,&#13;
&#13;
because no nationwide cohort study of penetrating and blunt TDI has been conducted in Japan and other coun-&#13;
tries where penetrating trauma is relatively uncommon, the clinical characteristics of all TDI are unknown. We aimed&#13;
&#13;
to describe the characteristics of TDI patients, compare penetrating TDI with blunt TDI, and identify mortality risk&#13;
factors in Japan.&#13;
Methods We retrospectively identified TDI patients between 2004 and 2019 using data from the Japan Trauma Data&#13;
Bank. We extracted data on patient demographics, type of trauma, cause of trauma, physiological parameters, region&#13;
of concomitant injury, associated injury, and management. We compared penetrating and blunt TDI for each variable.&#13;
The primary outcome was mortality. Multivariable logistic regression was performed to identify mortality risk factors.&#13;
Results Of the 338,744 patients, 1,147 (0.3%) had TDI, of which 771 were eligible for analysis (excluding 308 in cardiac&#13;
arrest on arrival). Penetrating TDI represented 29.8% and blunt TDI 70.2%, and comparing penetrating and blunt TDI,&#13;
the most common cause was self-inflicted (48.7%) vs. accident (85.6%), males were 68.7% vs. 66.0% of the patients&#13;
(P=0.50), and the mortality rate was 8.3% vs. 26.4% (P&lt;0.001). Multivariable analysis found that age (odds ratio [OR]&#13;
1.03, 95% confidence interval [CI] 1.01–1.04), Injury Severity Score (OR 1.03, 95%CI 1.006–1.06), Revised Trauma Score&#13;
(OR 0.55, 95%CI 0.45–0.67), severe concomitant abdominal injury (OR 2.45, 95%CI 1.32–4.56), severe concomitant&#13;
&#13;
upper extremity injury (OR 3.38, 95%CI 1.24–9.17) were independent predictors of mortality, and computed tomogra-&#13;
phy (CT) (OR 0.32, 95%CI 0.15–0.69) and diaphragm repair (OR 0.44, 95%CI 0.25–0.78) were protective factors.&#13;
&#13;
Conclusions In Japan, we found that penetrating TDI was mainly caused by self-injury and the male–female ratio&#13;
was the same as for blunt TDI, although blunt TDI was much more frequent. TDI was considered highly lethal,&#13;
with over 25% of patients in cardiac arrest on arrival. Our unique independent predictors were CT, severe concomitant&#13;
abdominal injury, and severe concomitant upper extremity injury. These findings may help in the management of TDI&#13;
in countries with less common penetrating trauma.&#13;
Keywords Traumatic diaphragmatic injury (TDI), Penetrating TDI (PTDI), Blunt TDI (BTDI), Japan Trauma Data Bank&#13;
(JTDB), Associated injury, Severe concomitant injury, Independent predictor of mortality, Epidemiology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135228">
                <text>Takafumi Shinjo1*, Yoshimitsu Izawa1&#13;
&#13;
, Chikara Yonekawa1&#13;
&#13;
, Tomohiro Matsumura1 and Takashi Mato1</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="135229">
                <text>https://doi.org/10.1186/s12245-025-00826-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="135230">
                <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="135231">
                <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="135232">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135233">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135234">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15510">
        <name>Traumatic diaphragmatic injury (TDI), Penetrating TDI (PTDI), Blunt TDI (BTDI), Japan Trauma Data Bank</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12651" public="1" featured="1">
    <fileContainer>
      <file fileId="12707">
        <src>https://repository.horizon.ac.id/files/original/24cd4adece5db10d7f1cc210c9a0a39f.pdf</src>
        <authentication>5e7846577d348d02af5b015550019c62</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="135170">
                <text>Development of an emergency department triage tool to predict admission or discharge for older adults</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135171">
                <text>Hospitalization, Emergency department, Risk score, Older adults</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135172">
                <text>Abstract&#13;
Background Older adults present to Emergency Departments (ED) with complex conditions, requiring triage models&#13;
that support effective disposition decisions. While existing models perform well in the general population, they&#13;
often fall short for older patients. This study introduces a triage model aimed at improving early risk stratification and&#13;
disposition planning in this population.&#13;
Methods We analyzed the National Hospital Ambulatory Medical Care Survey data (2015–2019) for ED patients&#13;
aged≥60 years, excluding those who died in the ED or left against medical advice. Key predictors were identified&#13;
using a two-step process combining LASSO and backward stepwise selection. Model performance was evaluated&#13;
using AUC and calibration plots, while clinical utility was assessed through decision curve analysis. Risk thresholds&#13;
(&lt;0.1, 0.1–0.5, &gt;0.5) stratified patients into low, moderate, and high-risk groups, optimizing the balance between&#13;
sensitivity and specificity.&#13;
Results Of 13,431 patients, 3,180 (23.7%) were admitted. Key predictors for admission included ambulance arrival,&#13;
chronic conditions, gastrointestinal bleeding, and abnormal vital signs. The model showed strong discrimination (AUC&#13;
0.73) and good calibration, validated by 10-fold cross-validation (mean AUC 0.73, SD 0.02). Decision curve analysis&#13;
highlighted net benefit across clinically relevant thresholds. At thresholds of 0.1 and 0.5, the model identified 18.9% as&#13;
low-risk (91.2% accuracy) and 7.9% as high-risk (57.7%). Adjusting thresholds to 0.2 and 0.4 expanded low-risk (55.4%,&#13;
87.9% accuracy) and high-risk (14.1%, 53.7% accuracy) groups.&#13;
Conclusions This older adult–focused risk score uses readily available data to enhance early discharge, prioritize&#13;
admissions for high-risk patients, and enhance ED care delivery.&#13;
Highlights&#13;
• Readily available triage data predict hospital admission in older adult ED patients.&#13;
• Key predictors include chief complaint, ambulance arrival, comorbidities, and vital signs.&#13;
• The Hospital Admission Model effectively stratifies patients into low- and high-risk groups.&#13;
• At a 0.2 threshold, 55% of patients were classified as low risk with 88% accuracy.&#13;
• At a 0.5 threshold, 8% of patients were classified as high risk with 58% accuracy.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135173">
                <text>Ashraf Abugroun1*, Saria Awadalla2&#13;
&#13;
, Sanjay Singh3&#13;
&#13;
and Margaret C. Fang1</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="135174">
                <text>https://doi.org/10.1186/s12245-025-00825-3</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135175">
                <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="135176">
                <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="135177">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135178">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135179">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="12650" public="1" featured="1">
    <fileContainer>
      <file fileId="12706">
        <src>https://repository.horizon.ac.id/files/original/a1f5a885d0954769a05cb730bf93dba8.pdf</src>
        <authentication>60e33eee978e2d0dad7d62c4011c17ee</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="135160">
                <text>Successful outcome following intralipid emulsion and plasmapheresis in a patient with profound neurologic and cardiovascular manifestations due to nortriptyline poisoning: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135161">
                <text>TCA, Plasmapheresis, Intralipid</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135162">
                <text>Abstract&#13;
Objective Tricyclic antidepressants (TCAs) are used to treat depression, but if abused or misused, they can cause&#13;
poisoning, which can be fatal. The main treatment for TCA poisoning is administering sodium bicarbonate.&#13;
Methods We report a 16-year-old girl diagnosed with nortriptyline poisoning with a profound neurologic and&#13;
cardiovascular manifestations, successfully treated using sodium bicarbonate, intralipid emulsion, and plasmapheresis.&#13;
Conclusions Plasmapheresis can be a good treatment modality for patients with TCA poisoning who do not respond&#13;
well to classic treatments.&#13;
Keywords TCA, Plasmapheresis, Intralipid</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135163">
                <text>Asma Ahmadinejad1&#13;
&#13;
, Amir Saeed2&#13;
&#13;
and Marzieh Davoodi3*</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="135164">
                <text>https://doi.org/10.1186/s12245-025-00824-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="135165">
                <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="135166">
                <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="135167">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135168">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135169">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15508">
        <name>TCA, Plasmapheresis, Intralipid</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12648" public="1" featured="1">
    <fileContainer>
      <file fileId="12704">
        <src>https://repository.horizon.ac.id/files/original/24046d2f9c1fb2b2d0a757ad61332b26.pdf</src>
        <authentication>26b229c8b0b382c664fd7f3773b7448d</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="135139">
                <text>Point of care ultrasound in rapid diagnosis of acute cholangitis and emphysematous cholecystitis: a case report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135140">
                <text>Emphysematous cholecystitis, Champagne sign, Point of care ultrasound, Cholangitis, Gas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135141">
                <text>Abstract&#13;
Background Emphysematous cholecystitis is a rare and rapidly progressive disease that requires prompt diagnosis&#13;
and intervention. Point of care ultrasound (POCUS) is a useful diagnostic imaging tool in the emergency department&#13;
that can help expedite diagnosis and management of biliary etiology.&#13;
Case presentation In our case, we describe an 85 year old female with a history of diabetes mellitus with a&#13;
presentation consistent with undifferentiated cholecystitis. Point of care ultrasound performed in the emergency&#13;
department showed a characteristic “champagne sign”, along with other findings including dilated common bile&#13;
duct and pericholecystic fluid. These findings ultimately led to the diagnosis of emphysematous cholecystitis and&#13;
acute cholangitis. The use of ultrasound expedited the patient’s cholecystostomy tube placement and subsequent&#13;
endoscopic retrograde cholangiopancreatography, proving to be a life-saving tool in the management of this patient.&#13;
Conclusion POCUS can be an important tool for the diagnosis of undifferentiated biliary etiology, expediting the&#13;
management of these patients.&#13;
Keywords Emphysematous cholecystitis, Champagne sign, Point of care ultrasound, Cholangitis, Gas</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135142">
                <text>Min Seok Chae1* and Olga A. Kravchuk1</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="135143">
                <text>https://doi.org/10.1186/s12245-025-00823-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="135144">
                <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="135145">
                <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="135146">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135147">
                <text>englsih</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135148">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15507">
        <name>Emphysematous cholecystitis, Champagne sign, Point of care ultrasound, Cholangitis, Gas</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12646" public="1" featured="1">
    <fileContainer>
      <file fileId="12702">
        <src>https://repository.horizon.ac.id/files/original/a0291dc43da738b94a4faea7df986ec1.pdf</src>
        <authentication>f8156fbc57b36d74a201d1f2bc6c46ab</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="135118">
                <text>Impact of physician group practice in the operations, quality of care, and service satisfaction in the non-urgent section of an emergency department in a tertiary hospital in the Philippines: a mixed methods study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135119">
                <text>Emergency department, Group practice, Independent consultancy, Non-urgent, Quality of care, Service&#13;
satisfaction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135120">
                <text>Abstract&#13;
&#13;
Background The Emergency Department (ED) is a primary source of healthcare services for patients with non-&#13;
urgent conditions in the Philippines. The adaptation of physician group practice (GP) in the ED has gained popularity&#13;
&#13;
in the country due to its potential advantage to patient management and physicians compared to independent&#13;
consultancy (IC). This study aimed to determine the impacts of GP in a non-urgent ED setting in terms of operations,&#13;
quality of care, and service satisfaction compared to IC.&#13;
Methods Historical data collection focusing on operations, service costs, patient outcomes, and satisfaction was&#13;
performed between 2021 and 2022 at a tertiary for-profit private hospital in Metro Manila, Philippines. In addition,&#13;
patient surveys on demographics, perception, ED accessibility, and descriptive satisfaction ratings were also&#13;
administered in 2023 (n=310). These aspects were compared between patients managed by GP and IC quantitatively&#13;
using univariate descriptive statistics, Mann-Whitney U tests, and ANCOVA to compare operational metrics, financial&#13;
data, and patient outcomes. Qualitative data from patient surveys were analyzed using a sequential-explanatory&#13;
approach.&#13;
Results Our analysis of the historical data showed high rates of positive outcomes for non-urgent ED patients in both&#13;
GP and IC. Total (PhP587,812 vs. PhP379,699; p&lt;0.001) and per patient (PhP1,801 vs. PhP554; p&lt;0.001) operational&#13;
costs were higher for the GPs. However, GPs incurred shorter mean length of stay (165.5 vs. 214.2 min; p&lt;0.001). There&#13;
appears to be no difference in service satisfaction and overall patient outcomes between patients managed by GP&#13;
or IC, although patients of GP physicians assessed the level of care of the ED to be higher (5 vs. 4; p-value=0.019). In&#13;
the quantitative and qualitative ratings, most patients provided positive citations on ED service quality, staff, structure,&#13;
system, physician competency and compassion.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135121">
                <text>Ma. Lourdes Concepcion D. Jimenez1,2*, Mark B. Carascal3&#13;
&#13;
, Marlouie D. Figueras4&#13;
&#13;
, John Q. Wong5&#13;
, Roemer&#13;
&#13;
D. Tanghal1,2, Veincent Christian F. Pepito1&#13;
&#13;
and Rafael Manzanera6</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="135122">
                <text>https://doi.org/10.1186/s12245-025-00822-6</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="135123">
                <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="135124">
                <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="135125">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135126">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135127">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15506">
        <name>Emergency department, Group practice, Independent consultancy, Non-urgent, Quality of care, Service satisfaction</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12644" public="1" featured="1">
    <fileContainer>
      <file fileId="12700">
        <src>https://repository.horizon.ac.id/files/original/601b432308930e4a844d881442cc86fa.pdf</src>
        <authentication>269037348cd38f6204cef4656f1c25f3</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="135097">
                <text>Artificial intelligence in gynecologic and obstetric emergencies</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135098">
                <text>Artificial intelligence, Gynecology, Obstetrics, Emergency</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135099">
                <text>Abstract&#13;
Background Artificial intelligence (AI) uses a process by which machines perform human-like functions such as&#13;
automated clinical decisions. This may operate efficiently in gynecologic and obstetric emergencies. We aimed to&#13;
review the role and applications of AI in gynecologic and obstetric emergencies.&#13;
Methods A literature search was carried out in November 2023 in PubMed, Cochrane Library and Google Scholar&#13;
using the keywords combination of “artificial intelligence, gynecology and obstetrics”. Relevant articles were selected&#13;
and read. Reference lists of the selected articles were also searched.&#13;
Results The literature demonstrated the role of AI to improve healthcare in emergency settings in several aspects&#13;
such as diagnostic imaging, improving predictions in emergencies, and improving planning and resource allocation&#13;
for emergency services. AI works objectively, overcoming human biases in decision-making. Creating interconnected&#13;
data registries for AI will likely enhance its performance. Validation research in emergency settings has shown that&#13;
AI-prediction tools perform more accurately compared with the estimation of risk and outcomes by gynecologists&#13;
and obstetricians in emergency situations including endometriosis and acute abdominal pain. There was acceptance&#13;
of AI and its potential benefits. Ethical dilemmas of using AI include data governance, responsibility for errors, and&#13;
security issues. Providing training on AI to healthcare professionals working in emergency departments is needed.&#13;
Conclusions Healthcare professionals should educate themselves about the anticipated role of AI in gynecologic&#13;
and obstetric emergencies, its indications, limitations, and ethical considerations so that they can take steps towards&#13;
its application in their future practice using defined guidelines.&#13;
Key message&#13;
Why is this review is important? The use of AI in healthcare has created polarized thoughts among emergency&#13;
medicine professionals. This review is an effort to compare the pros and cons of using AI in gynecologic and obstetric&#13;
emergencies so that AI can be properly applied in these specialities.&#13;
What does this review show? This review shows that there are several research studies in gynecology and&#13;
obstetrics emergencies with positive points in favor of using AI in emergencies like acute abdominal and pelvic pain,&#13;
and endometriosis. There are some reservations from the practitioners to use it due to lack of understanding of its&#13;
nature, advantages and limitations. By narrating the findings of AI-related publications in gynecology and obstetrics&#13;
emergency, we propose their applications and their limitations.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135100">
                <text>Hassan M. Elbiss1* and Fikri M. Abu-Zidan2</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="135101">
                <text>https://doi.org/10.1186/s12245-025-00820-8</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135102">
                <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="135103">
                <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="135104">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135105">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135106">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15505">
        <name>Artificial intelligence, Gynecology, Obstetrics, Emergency</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12641" public="1" featured="1">
    <fileContainer>
      <file fileId="12697">
        <src>https://repository.horizon.ac.id/files/original/2c50127e73785380e8085d90791e528e.pdf</src>
        <authentication>b9350100c002ff8883a60edf9c8e150e</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="135064">
                <text>Precision education – a call to action to transform medical education</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135065">
                <text>Artificial intelligence, Precision education, Competency based medical education, Master adaptive learner,&#13;
Medical education, Health professions education</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135066">
                <text>Abstract&#13;
Background Institutions, departments, and individuals are increasingly facing challenges to determine how to&#13;
enable their learners to acquire and curate rapidly changing knowledge and to foster the creation of lifelong learners&#13;
in this information-rich digital era.&#13;
Methods Much like the Precision Medicine initiative of 2015, in which diagnostic, treatment, and preventive care&#13;
target individual patients based on their genetic and environmental profiles, educators can use the same principles to&#13;
create a model of “Precision Education.”&#13;
Results In this model, future facing individualizable educational infrastructure can consider innate qualities, learning&#13;
style, behavior, environment, prior experience, expertise, and assessments.&#13;
Conclusion Educators can utilize Artificial Intelligence, the Master Adaptive Learner model, and key components&#13;
of Competency Based Medical Education to transform the evolution of Health Professions Education to meet the&#13;
individual and systemic needs of tomorrow’s learners, educators, and institutions to improve educational and clinical&#13;
outcomes.&#13;
Keywords Artificial intelligence, Precision education, Competency based medical education, Master adaptive learner,&#13;
Medical education, Health professions education</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135067">
                <text>Wendy C. Coates1,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="135068">
                <text>https://doi.org/10.1186/s12245-025-00819-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="135069">
                <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="135070">
                <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="135071">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135072">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135073">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15502">
        <name>Artificial intelligence, Precision education</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="12640" public="1" featured="1">
    <fileContainer>
      <file fileId="12696">
        <src>https://repository.horizon.ac.id/files/original/db8b02a33d4143c31efe60be58fb8b44.pdf</src>
        <authentication>9e115f8cdb3201be7a32c4744490ce44</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="135054">
                <text>The impact of a targeted Arab Board of Emergency Medicine examination&#13;
preparation course on resident success rates</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135055">
                <text>Emergency medicine residents (EMRs), Examination preparation, Board certification, Arab board&#13;
emergency medicine (ABEM), Objective structured clinical examination (OSCE)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135056">
                <text>Abstract&#13;
Background The Arab Board of Emergency Medicine (ABEM) examination is a critical milestone for emergency&#13;
medicine residents (EMRs) aiming to transition to independent practice. Prior to this study, no structured course had&#13;
been administered to prepare EMRs for the ABEM examination. To address this gap, a five-day evening preparatory&#13;
course was developed, designed to align with ABEM requirements and deliver updated, essential knowledge. This&#13;
study aims to evaluate the impact of this newly introduced preparatory course on EMRs’ success rates on the ABEM&#13;
examination from 2017 to 2021.&#13;
Methods The five-day in-person course was conducted annually in the evenings to accommodate both EMRs&#13;
and faculty, scheduled approximately six weeks before the ABEM examination. The course content was specifically&#13;
aligned with ABEM standards, focusing on relevant and contemporary knowledge. EMRs participated in assessments&#13;
modeled after the ABEM examination, using standardized rubrics. Pass rates were compared to historical data, and&#13;
demographic variables were thoroughly analyzed. Feedback was collected from both EMRs and faculty after each&#13;
course to continuously refine and improve course content and delivery.&#13;
Results Data were collected over a five-year period (2017–2021), with 49 emergency medicine residents (EMRs)&#13;
(100%) participating in the course. The majority of participants were male (69.4%), and the cohort included graduates&#13;
from diverse regions, including Sudan (22.4%) and Pakistan (18.4%). The overall pass rate for the Arab Board of&#13;
Emergency Medicine (ABEM) examination significantly increased to 91.8%, compared to a pre-course pass rate of&#13;
60%. No significant impact on outcomes was observed based on factors such as gender, country of graduation, year&#13;
of participation, or initial confidence levels. Feedback from both participants and faculty indicated high levels of&#13;
satisfaction with the course, with recommendations for further content refinement and the inclusion of additional&#13;
Objective Structured Clinical Examination (OSCE) stations.&#13;
Conclusion The findings demonstrate the significant impact of the newly introduced, face-to-face, five-day ABEM&#13;
preparatory course on EMR pass rates, potentially serving as a model for similar programs in other specialties. The&#13;
results highlight the importance of targeted, up-to-date instruction in improving the confidence and success of EMRs&#13;
on the ABEM examination. Furthermore, the course’s development and the incorporation of ongoing feedback played&#13;
key roles in further enhancing the quality and effectiveness of the training program.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135057">
                <text>Shahzad Anjum1,2, Khalid Bashir1,2*, Haris Iftikhar1&#13;
&#13;
, Biju Gafoor1&#13;
&#13;
and Aftab Mohammad Umar1,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="135058">
                <text>https://doi.org/10.1186/s12245-025-00818-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="135059">
                <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="135060">
                <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="135061">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135062">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135063">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="15501">
        <name>Emergency medicine residents (EMRs), Examination preparation, Board certification, Arab board</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
