<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>DSpace Collection:</title>
    <link>http://localhost:8080/xmlui/handle/123456789/8793</link>
    <description />
    <pubDate>Tue, 14 Apr 2026 20:45:16 GMT</pubDate>
    <dc:date>2026-04-14T20:45:16Z</dc:date>
    <item>
      <title>Unusual Lifespan of Edwards' Syndrome in COVID-19 Era</title>
      <link>http://localhost:8080/xmlui/handle/123456789/8817</link>
      <description>Title: Unusual Lifespan of Edwards' Syndrome in COVID-19 Era
Authors: Suryaningrat, Filla Reviyani; Hudayari, Devatri; Amalda, Natasha; Mardhiya, Wan Rita; Kadi, Fiva Aprilia; Primadi, Aris; Yuniati, Tetty
Abstract: Edwards' syndrome is caused by an extra chromosome on the 18th chromosome. Patients with this diagnosis have median survival of only 3–14.5 days, with the majority of infants with full trisomy 18 type die before or shortly after they are born. There is only supportive treatment available for Edwards’ syndrome. During the COVID-19 pandemic, providing health services was challenging, leading to less than optimum treatments added by patients’ reluctance to visit healthcare facilities due to the fear of COVID-19 transmission. This case study presented an infant with Edwards’ syndrome with major malformation. The patient had several organ problems, was admitted to the NICU, and continued with home care for monitoring for 6 months. Patient then died at 9 months of age. Maintaining the best quality of life for this patient was very challenging for parents and healthcare providers. Since the management for this type of sydnome is more palliative, good education, information, and psychosocial supports for the parents are needed to prepare them with the worst conditions, which was especially more challenging during the COVID-19 pandemic</description>
      <pubDate>Sun, 01 Sep 2024 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://localhost:8080/xmlui/handle/123456789/8817</guid>
      <dc:date>2024-09-01T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Management of Stage-4 HIV with Cerebral Toxoplasmosis Coinfection and SIADH Complication</title>
      <link>http://localhost:8080/xmlui/handle/123456789/8816</link>
      <description>Title: Management of Stage-4 HIV with Cerebral Toxoplasmosis Coinfection and SIADH Complication
Authors: Laksono, Pandu; Oktavia, Erlin; Putri, Hidayati Adi; Herawati, Fauna
Abstract: HIV/AIDS stage 4 is the stage where the HIV/AIDS patients have low immunity protection against infections, which can led to coinfections and complications. This case report presented an evaluation of the diagnosis and treatment of an HIV/AIDS stage 4 patient with cerebral toxoplasmosis coinfection and SIADH complications. A man (47 years, 35 kg), married with two children, complaining of weakness, nausea, vomiting, weight loss, and low appetite. Sodium level were measured, showing a 117 mg/dL level that continued to decrease throughout the patient's treatment. Five days later, the patient lost his consciousness with a GCS score of 224, indicating severe brain injury, and was diagnosed with cerebral toxoplasmosis based on the result of head CT-SCAN with contrast. On day 6, the patient was tested positive for HIV and diagnosed with stage 4 with an absolute CD4 count of 4 cells/μl. Therapy was provided by giving pyrimethamine-clindamycin therapy for cerebral toxoplasmosis, followed by Tenofovir, Lamivudine, and Evafirenz as antiretroviral therapy. Treatment for hyponatremia was done by administration of 3% NaCl and tolvaptan. The patient started experiencing an improvement in consciousness after the 10th day of medication, and sodium levels fluctuated throughout the treatments. Patient was discharged after 15 days with clinical improvements.</description>
      <pubDate>Sun, 01 Sep 2024 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://localhost:8080/xmlui/handle/123456789/8816</guid>
      <dc:date>2024-09-01T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Comparison of Different Cycloplegic Refraction Regimens for Children</title>
      <link>http://localhost:8080/xmlui/handle/123456789/8815</link>
      <description>Title: Comparison of Different Cycloplegic Refraction Regimens for Children
Authors: Irfani, Irawati; Gunawan, Fany; Satari, Karmelita; Sari, Maya; Oktarima, Primawita; Caesarya, Sesy
Abstract: In the process of a pediatric eye exam, cycloplegic refraction is a crucial step. Since no single cycloplegic drug is ideal, a combination regimen is employed. This study compares the ocular (refractive power and pupil diameter) and systemic (blood pressure and heart rate) effects of administering a combination of 1% cyclopentolate and 2.5% phenylephrine, with or without 1% tropicamide, to children with refractive errors. This study aimed to discover a more feasible regimen for children. This was a single-blind study, a randomized clinical trial conducted from November–December 2020 in children with mild to moderate refractive errors. Group A received 1% cyclopentolate, 2.5% phenylephrine, and 1% tropicamide (SFT), whereas group B received 1% cyclopentolate and 2.5% phenylephrine (SF). The outcomes were measured using an auto refractometer and IOL Master® 700. Before and 60 minutes after medication was administered, blood pressure and heart rate were measured. There were 54 participants (108 eyes) with an average age of 12.85±2.84 years. Although the SFT group's refractive power and pupil width were greater than those of the SF group, the differences were not statistically significant (p=0.271 and p=0.088). Heart rate (p=0.521) and blood pressure (systolic p=0.201; diastolic p=0.950) did not significantly differ between the two groups. Despite mydriasis manifested more rapidly in the SFT group, there was no discernible difference in the cycloplegic effects between those groups. SF might be a more feasible regimen for cycloplegic refraction in children with refractive errors.</description>
      <pubDate>Sun, 01 Sep 2024 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://localhost:8080/xmlui/handle/123456789/8815</guid>
      <dc:date>2024-09-01T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Prostate Specific Antigen Level and Gleason Score in Indonesian Prostate Cancer Patients</title>
      <link>http://localhost:8080/xmlui/handle/123456789/8814</link>
      <description>Title: Prostate Specific Antigen Level and Gleason Score in Indonesian Prostate Cancer Patients
Authors: Herawan, Muhammad Imam Al Kautsar; Adriansjah, Ricky
Abstract: In Indonesia, the number of prostate cancer continues to increase and even becomes the most common malignancy in men in 2015. Delayed early detection of prostate cancer is a significant concern. Prostatespecific antigen (PSA) level is found to be elevated in various conditions of prostate tissue damage, including prostate cancer. The extent of tissue damage in prostate cancer, represented by the Gleason score, is suspected to be related to the increase in the PSA level in the bloodstream. To investigate the relationship between the PSA level and Gleason scores in prostate cancer patients, a cross-sectional observational study was conducted. The study population consisted of 83 prostate cancer patients treated in Dr. Hasan Sadikin General Hospital Bandung, Indonesia, from 2017 to 2021. Data collected were analyzed using Spearman correlation test was used with an alpha value of 5%. Results indicated that 37.3% patients had a PSA level above 200 ng/dL, and 25.3% had a PSA level between 10-50 ng/dL. The majority of patients (48.1%) had a Gleason score of 9-10 (ISUP 5), while 24.1% had a score of 8 (ISUP 4). Bivariate analysis showed no significant relationship between the PSA level and Gleason score (p-value=0.445). Further studies are needed to determine the sensitivity and specificity of PSA in diagnosing prostate cancer.</description>
      <pubDate>Sun, 01 Sep 2024 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://localhost:8080/xmlui/handle/123456789/8814</guid>
      <dc:date>2024-09-01T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

