Skip to main content
PLOS One logoLink to PLOS One
. 2025 Aug 22;20(8):e0330769. doi: 10.1371/journal.pone.0330769

Remimazolam’s clinical application and safety: A signal detection analysis based on FAERS data and literature support

Gang Ye 1, Luqin Ding 2, Qingbo Zhou 2,*
Editor: Anmar Al-Taie3
PMCID: PMC12373250  PMID: 40845004

Abstract

This study aimed to evaluate the adverse event profile of remimazolam, a novel ultra-short-acting benzodiazepine, with a focus on its safety in the respiratory, cardiovascular, and immune systems across diverse patient populations. We analyzed adverse event reports from the FAERS database over a defined period, performing signal detection using the proportional reporting ratio (PRR) and the reporting odds ratio (ROR), and contextualized the findings with a concurrent literature review. Remimazolam demonstrated a strong signal for hypoventilation. In the cardiovascular system, it was associated with serious adverse events, including cardiac and cardiorespiratory arrest, particularly in high-risk patients. Furthermore, we detected significant signals for severe hypersensitivity reactions, such as anaphylactic shock and laryngeal edema, while signals in other systems were less pronounced but remained clinically significant. Given that the study population was predominantly elderly, and considering the serious nature of the identified signals, its potential for adverse events necessitates vigilant monitoring. Future research should focus on clarifying risks within specific high-risk groups to establish optimized safety protocols.

Introduction

Remimazolam, a novel ultra-short-acting benzodiazepine, is distinguished by its rapid onset and swift recovery profile [1]. Compared to traditional sedatives like propofol and midazolam, remimazolam offers greater hemodynamic stability and a lower risk of respiratory depression. These properties make it a valuable agent for procedural sedation, general anesthesia, and other settings requiring rapid patient recovery [2]. Moreover, its distinct metabolic pathway is thought to lower the incidence of adverse reactions, particularly in elderly patients and those with comorbidities [3].

With the expanding clinical use of remimazolam, especially in high-risk populations, a systematic evaluation of its safety profile has become crucial. While pre-market clinical trials provide foundational safety data, their limited sample sizes and short follow-up periods may not detect rare or delayed adverse events in a broad population [4,5]. Therefore, post-marketing surveillance using real-world data is essential for a comprehensive safety assessment. Indeed, pharmacovigilance studies using real-world databases are instrumental for assessing the post-marketing safety profiles of various therapeutics. These studies complement findings from pre-approval clinical trials, as seen in studies on sildenafil [6] and everolimus [7].

This study analyzes data from the FDA Adverse Event Reporting System (FAERS) to investigate potential safety signals associated with remimazolam. FAERS is a global pharmacovigilance database maintained by the U.S. FDA, which contains millions of spontaneous adverse event reports from patients, healthcare professionals, and pharmaceutical companies [8,9]. The utility of FAERS for such pharmacovigilance, and its capacity for signal detection in diverse therapeutic areas, is well-documented in studies concerning topotecan [10], acetylsalicylic acid [11], anastrozole [12], and vinca alkaloids [13].

The extensive coverage of FAERS allows for the identification of infrequent or delayed adverse event signals that might be missed in clinical trials [14]. By systematically analyzing remimazolam-related reports in this database, our study aims to provide a more comprehensive evidence base for its real-world safety. Ultimately, this work seeks to inform safer prescribing strategies, especially for high-risk patient groups.

Methodology

Data source and processing

This study is based on data from the U.S. Food and Drug Administration’s (FDA) Adverse Event Reporting System (FAERS), a public database of spontaneous adverse event reports submitted by patients, healthcare professionals, and pharmaceutical manufacturers. For our analysis, we queried the entire available database, spanning from the first quarter of 2004 to the fourth quarter of 2023, to extract all reports associated with remimazolam. The resulting dataset, which covered reports from the second quarter of 2020 to the first quarter of 2023, formed the basis of our study [9].

Data processing was performed in several stages. First, we removed duplicate reports by retaining only the most recent entry for each unique case ID. Next, data from different tables were linked using the primaryid field. We then standardized drug names using the MedEx-UIMA system and cleaned the dataset by correcting or removing records with abnormal age or weight entries. Finally, we isolated all reports where remimazolam was listed as a suspect drug and extracted key variables, including patient demographics and report details. The complete workflow for data selection and processing is illustrated in Fig 1.

Fig 1. Flow diagram of the selection process for remimazolam-related adverse events.

Fig 1

The diagram illustrates the stepwise filtering of reports from the FAERS database, showing the number of adverse event (AE) records identified and excluded at each stage to arrive at the final analytical dataset.

Signal detection analysis

To identify potential safety signals, we employed a multi-algorithm approach to ensure robust and comprehensive detection. Four distinct signal detection algorithms were used: the Reporting Odds Ratio (ROR), the Proportional Reporting Ratio (PRR), the Bayesian Confidence Propagation Neural Network (BCPNN), and the Multi-Item Gamma Poisson Shrinker (MGPS). This combination allowed for the detection of both common and rare adverse event signals. The specific formulas and criteria for these algorithms are detailed in Fig 2.

Fig 2. Signal detection algorithms and their corresponding criteria.

Fig 2

This figure outlines the formulas and specific thresholds used for the four signal detection algorithms (ROR, PRR, BCPNN, and MGPS) employed in this study.

The criteria for signal detection for each algorithm were as follows:

  • ROR: A signal was defined as the lower limit of the 95% confidence interval (CI) being greater than 1 [15].

  • PRR: A signal required a PRR value ≥ 2 and a corresponding chi-square value ≥ 4 [16].

  • BCPNN: A signal was present if the lower limit of the 95% CI of the Information Component (IC) was greater than 0 [17].

  • MGPS: This empirical Bayesian method was used to detect signals for rare events [18].

All calculations were performed using R software (version 4.1.3). The aggregated results from these algorithms formed the basis for our evaluation of remimazolam’s adverse event profile.

Signal screening and classification

This threshold (N ≥ 3) is a commonly adopted criterion in pharmacovigilance to enhance the stability of disproportionality measures and to reduce the likelihood of spurious signals arising from isolated case reports [19].

All identified signals were coded and classified using the Medical Dictionary for Regulatory Activities (MedDRA). We focused our analysis on Preferred Terms (PT) within each System Organ Class (SOC). This systematic classification allowed us to identify the primary organ systems affected and to provide a clear framework for analyzing remimazolam’s safety risks [15].

Results

Overview of dataset characteristics

A total of 68 adverse event reports associated with remimazolam were analyzed. The number of reports increased annually between 2020 and 2023, peaking in 2022, which accounted for 35.3% of the total reports (Table 1). Reports for male patients (55.9%) were more frequent than for female patients (27.9%), with gender unspecified in 16.2% of cases. The median patient age was 67.5 years and the median weight was 65.5 kg, indicating a predominantly elderly study population. Physicians submitted the majority of reports (79.4%), followed by pharmacists (19.1%). The primary route of administration was intravenous (88.2%). Regarding outcomes, most events were classified as “other serious” (74.7%), while 12.7% were “life-threatening” and 2.8% were fatal. The median time-to-onset was 0 days, suggesting that most adverse events occurred shortly after drug administration.

Table 1. Demographic and report characteristics of the study population.

Variable Category/Value Total n (%)
Year
2020 6 (8.82)
2021 23 (33.82)
2022 24 (35.29)
2023 15 (22.06)
Sex
Female 19 (27.94)
Male 38 (55.88)
Unknown 11 (16.18)
Age (years) Median (IQR) 67.50 (54.50, 75.75)
Weight (kg) Median (IQR) 65.50 (56.50, 69.68)
Reporter
Physician 54 (79.41)
Pharmacist 13 (19.12)
Consumer 1 (1.47)
Reported countries
Other 68 (100.00)
Route of Administration
Intravenous 60 (88.24)
Other 8 (11.76)
Outcomes
Other serious 53 (74.65)
Life-threatening 9 (12.68)
Hospitalization 7 (9.86)
Death 2 (2.82)

Abbreviations: N, Number of reports; IQR, Interquartile Range.

SOC-level analysis

Table 2 presents the signal detection results at the System Organ Class (SOC) level. A signal was considered significant if it met the predefined criteria: a Reporting Odds Ratio (ROR) with a 95% CI lower bound > 1, or a Proportional Reporting Ratio (PRR) ≥ 2 with a chi-square (χ²) value ≥ 4. All analyzed signals were based on at least three case reports.

Table 2. Signal detection results at the System Organ Class (SOC) level.

SOC Case Reports ROR (95% CI) PRR (95% CI) chisq IC (IC025) EBGM (EBGM05)
Immune system disorders 17 10.02(6.07, 16.56) 9.09(5.79, 14.27) 123.75 3.18(2.48) 9.09(5.97)
Cardiac disorders 22 7.56(4.83, 11.85) 6.68(4.51, 9.89) 108.45 2.74(2.11) 6.68(4.59)
Vascular disorders 13 4.41(2.5, 7.78) 4.14(2.44, 7.03) 31.6 2.05(1.26) 4.14(2.58)
Respiratory, thoracic and mediastinal disorders 27 4.08(2.7, 6.16) 3.57(2.51, 5.08) 52.41 1.84(1.26) 3.57(2.53)
Investigations 28 3.16(2.11, 4.75) 2.79(2, 3.89) 34.32 1.48(0.91) 2.79(1.99)
Injury, poisoning and procedural complications 26 1.27(0.84, 1.93) 1.23(0.86, 1.75) 1.26 0.3(−0.29) 1.23(0.86)
Skin and subcutaneous tissue disorders 7 0.81(0.38, 1.73) 0.82(0.4, 1.69) 0.29 −0.28(−1.31) 0.82(0.44)
Nervous system disorders 5 0.39(0.16, 0.95) 0.41(0.17, 0.97) 4.6 −1.29(−2.46) 0.41(0.19)
General disorders and administration site conditions 11 0.32(0.17, 0.59) 0.36(0.2, 0.64) 15 −1.46(−2.3) 0.36(0.22)
Gastrointestinal disorders 4 0.29(0.11, 0.78) 0.31(0.12, 0.81) 6.88 −1.71(−3) 0.31(0.13)

Abbreviations: SOC, System Organ Class; Case Reports, Number of individual adverse event reports; ROR, Reporting Odds Ratio; CI, Confidence Interval; PRR, Proportional Reporting Ratio; chisq, Chi-square value; IC, Information Component; IC025, Lower limit of the 95% confidence interval for the IC; EBGM, Empirical Bayes Geometric Mean; EBGM05, Lower limit of the 90% confidence interval for the EBGM.

Significant disproportional reporting was identified for several SOCs. The strongest signal was for Immune System Disorders (17 cases), with an ROR of 10.02 (95% CI 6.07, 16.56) and a PRR of 9.09. This suggests a reporting frequency for these events with remimazolam that is approximately 10 times higher than the background rate. This SOC includes critical Preferred Terms (PTs) like anaphylactic shock, which generated an even more pronounced signal at the PT level (Table 3).

Table 3. Signal detection results for specific adverse events at the Preferred Term (PT) level.

SOC PT Case Reports ROR (95% CI) PRR (95% CI) chisq IC (IC025) EBGM (EBGM05)
Investigations blood pressure decreased 8 51.98(25.54, 105.8) 49.49(25.42, 96.37) 380.28 5.63(4.66) 49.47(27.29)
Investigations oxygen saturation decreased 6 33.33(14.75, 75.32) 32.15(14.68, 70.42) 181.21 5.01(3.91) 32.14(16.24)
Investigations heart rate increased 3 12.07(3.85, 37.83) 11.87(3.88, 36.28) 29.9 3.57(2.14) 11.87(4.56)
Cardiac disorders cardio-respiratory arrest 3 42.92(13.7, 134.53) 42.16(13.79, 128.85) 120.54 5.4(3.97) 42.14(16.2)
Cardiac disorders cardiac arrest 4 25.62(9.5, 69.09) 25.01(9.57, 65.34) 92.28 4.64(3.36) 25.01(10.9)
Cardiac disorders tachycardia 3 14.3(4.56, 44.81) 14.06(4.6, 42.97) 36.43 3.81(2.38) 14.06(5.41)
Vascular disorders hypotension 8 16.66(8.19, 33.91) 15.9(8.17, 30.96) 112 3.99(3.02) 15.89(8.77)
Vascular disorders flushing 3 16.1(5.14, 50.46) 15.83(5.18, 48.38) 41.71 3.98(2.55) 15.82(6.08)
Respiratory, thoracic and mediastinal disorders hypoventilation 3 450.81(143.5, 1416.19) 442.58(144.81, 1352.65) 1315.75 8.78(7.35) 440.56(169.06)
Respiratory, thoracic and mediastinal disorders bronchospasm 5 189.02(77.54, 460.76) 183.28(77.37, 434.16) 904.88 7.52(6.34) 182.94(86.8)
Immune system disorders anaphylactic shock 6 105.97(46.88, 239.55) 102.13(46.63, 223.69) 600.41 6.67(5.58) 102.02(51.56)
Immune system disorders anaphylactic reaction 9 68.03(34.73, 133.25) 64.35(34.37, 120.49) 561.43 6.01(5.09) 64.31(36.64)
Skin and subcutaneous tissue disorders erythema 4 8.74(3.24, 23.57) 8.55(3.27, 22.34) 26.74 3.1(1.81) 8.55(3.73)
Injury, poisoning and procedural complications vascular access site occlusion 11 36584.93(18061.01, 74107.53) 34131.13(17528.18, 66460.64) 277096.74 14.62(13.67) 25192.28(13955.91)
General disorders and administration site conditions drug interaction 4 11.19(4.15, 30.18) 10.94(4.19, 28.58) 36.2 3.45(2.17) 10.94(4.77)

Abbreviations: SOC, System Organ Class; PT, Preferred Term; Case Reports, Number of individual adverse event reports; ROR, Reporting Odds Ratio; CI, Confidence Interval; PRR, Proportional Reporting Ratio; chisq, Chi-square value; IC, Information Component; IC025, Lower limit of the 95% confidence interval for the IC; EBGM, Empirical Bayes Geometric Mean; EBGM05, Lower limit of the 90% confidence interval for the EBGM.

Cardiac Disorders (22 cases) also generated a significant signal (ROR 7.56; 95% CI 4.83, 11.85), with a reporting frequency approximately 7.6 times higher than expected. Respiratory, Thoracic and Mediastinal Disorders (27 cases) presented a signal with an ROR of 4.08 (95% CI 2.70, 6.16), indicating a reporting frequency about 4 times higher than expected. This SOC contains crucial events like hypoventilation.

Other SOCs that met the signal criteria included Vascular Disorders (13 cases; ROR 4.41) and Investigations (28 cases; ROR 3.16). These findings highlight specific system organ classes where remimazolam is associated with a disproportionately high frequency of adverse event reports, underscoring the need for targeted clinical monitoring.

Analysis results of specific adverse reactions

At the Preferred Term (PT) level, a detailed analysis revealed strong safety signals for specific adverse events, with full details presented in Table 3. This granular analysis identified critical risks, some of which were not apparent at the broader SOC level.

Investigations.

Within this SOC, Blood Pressure Decreased (8 cases) and Oxygen Saturation Decreased (6 cases) generated substantial signals. The signal for Blood Pressure Decreased was particularly strong (ROR 51.98), indicating a reporting frequency over 50 times higher than expected. Similarly, Oxygen Saturation Decreased was reported over 30 times more frequently than its background rate (ROR 33.33), highlighting remimazolam’s potential to impact these key physiological parameters.

Cardiac disorders.

Serious cardiac events produced prominent signals. Cardio-Respiratory Arrest (3 cases; ROR 42.92) and Cardiac Arrest (4 cases; ROR 25.62) were reported over 40 and 25 times more frequently than expected, respectively. These findings underscore a significant safety concern regarding remimazolam’s impact on cardiac function.

Respiratory, thoracic, and mediastinal disorders.

Hypoventilation (3 cases) produced the most powerful safety signal for an adverse drug reaction in this study, with an ROR of 450.81. This indicates a reporting frequency over 400 times higher than the background rate, identifying a critical safety risk. Additionally, Bronchospasm (5 cases) generated a very strong signal (ROR 189.02). These results necessitate close respiratory monitoring during remimazolam administration.

Immune system disorders.

Severe hypersensitivity reactions were frequently reported. Anaphylactic Shock (6 cases) was reported over 100 times more frequently than expected (ROR 105.97), and Anaphylactic Reaction (9 cases) was also associated with a strong signal (ROR 68.03).

Injury, poisoning and procedural complications.

The most statistically prominent signal in the entire analysis was for Vascular Access Site Occlusion (11 cases), which had an exceptionally high ROR of 36,584.93. While this extraordinary disproportionality highlights a potential issue, its clinical interpretation requires further investigation to rule out confounding factors related to administration procedures or reporting artifacts.

Discussion

Overview of pharmacological properties and study findings on remimazolam

Remimazolam, a novel ultra-short-acting benzodiazepine, was developed to overcome the limitations of traditional sedatives like propofol and midazolam, namely their associated risks of respiratory depression and hemodynamic instability. The rapid metabolism and short half-life of remimazolam are intended to mitigate these risks and preserve hemodynamic stability. However, our analysis of the FAERS database indicates that remimazolam can still elicit significant adverse events affecting the respiratory and cardiovascular systems. Our findings offer new insights into remimazolam’s real-world safety profile. The respiratory and cardiovascular signals we identified are particularly noteworthy. Existing literature suggests that such risks can be more pronounced in high-risk populations, such as elderly patients and individuals with pre-existing comorbidities [3], which underscores the need for heightened caution when administering the drug to these vulnerable patient groups. These findings offer new insights into remimazolam’s real-world safety profile and underscore the need for heightened caution when administering the drug to vulnerable patient groups.

Discussion of multi-system adverse reactions of remimazolam

This pharmacovigilance study systematically evaluated remimazolam’s real-world safety profile using data from the FAERS database. Our analysis identified significant adverse event signals across several key organ systems, most notably the respiratory, cardiovascular, and immune systems [20].

Respiratory adverse reactions

A primary safety concern with any sedative is the potential for respiratory depression. Although remimazolam was designed to have a more favorable respiratory safety profile, our analysis revealed a powerful signal for Hypoventilation. This finding demonstrates that the risk of respiratory depression with remimazolam persists. The clinical implications of this are significant. For context, this risk may be heightened in high-risk groups, such as elderly patients and individuals with pre-existing respiratory disease, as suggested by other clinical studies [21].

This finding has significant clinical implications. Our findings underscore the critical need for vigilant respiratory monitoring during remimazolam administration, particularly in vulnerable populations or during prolonged sedation. Clinicians must be prepared to provide supplemental oxygen or mechanical ventilation if necessary [22,23]. Therefore, future research should aim to establish optimal dosing regimens that maximize sedative efficacy while minimizing respiratory adverse events [24].

Cardiovascular adverse reactions

Our analysis also identified significant safety signals for cardiovascular adverse events. We found a disproportionately high reporting frequency for Cardiac Arrest and Cardio-Respiratory Arrest. While our study could not stratify risk by patient history, these findings are particularly concerning because existing literature suggests that patients with pre-existing conditions like heart failure may be more vulnerable to such events [25].

While remimazolam is often selected for its favorable hemodynamic profile, these findings align with clinical reports that it can still induce hypotension and bradycardia, particularly in vulnerable patients [26]. Therefore, in high-risk settings such as cardiac surgery, a cautious approach is essential. This includes vigilant hemodynamic monitoring, preparedness to manage acute cardiac events, and consideration of a “start low, go slow” dosing strategy to mitigate the risk of serious cardiovascular complications [27].

Immune system adverse reactions

Our analysis revealed strong signals for severe hypersensitivity reactions, most notably Anaphylactic Shock and Anaphylactic Reaction. This finding is consistent with existing case reports which indicate that remimazolam can elicit life-threatening immune responses, including laryngeal edema [28,29].

These results carry significant clinical implications. A thorough evaluation of a patient’s allergy history, particularly regarding sensitivities to other benzodiazepines, is essential prior to administration. Furthermore, clinicians must ensure vigilant monitoring during drug infusion and have emergency medications and equipment, such as epinephrine, immediately available to manage any potential acute allergic event.

Comparative safety profile and other clinically relevant events

While our analysis did not generate strong signals for all adverse events, some still warrant clinical consideration. For instance, events like hypotension, nausea, and postoperative delirium, though not meeting the threshold for a strong signal in our data, are known risks that may be more pronounced in elderly patients or those on concomitant medications [30]. Postoperative delirium, in particular, remains a significant concern in the elderly due to its potential to delay recovery [31].

When contextualized against other sedatives, remimazolam’s safety profile is distinct. Its primary advantage is superior hemodynamic stability, with a lower incidence of hypotension compared to agents like propofol, making it valuable in high-risk surgeries [32]. However, this must be balanced against the specific clinical scenario. For prolonged deep sedation, propofol may offer more predictable control [33]. Conversely, compared to midazolam, remimazolam’s rapid clearance provides a key benefit by facilitating faster recovery and potentially reducing the risk of postoperative delirium, a notable advantage in elderly populations [34].

Ultimately, while remimazolam presents a favorable alternative to traditional sedatives, these findings emphasize that no single agent is universally optimal. The choice of sedative necessitates a careful, individualized risk-benefit assessment, considering both patient-specific factors and procedural demands to ensure safety and efficacy [35].

Study limitations

This study has several inherent limitations. First, its reliance on the FAERS database, a spontaneous reporting system, means it is subject to underreporting and various reporting biases [36]. Second, while disproportionality analysis can identify statistical signals, it cannot establish causality or calculate the true incidence of adverse events [37]. Finally, the relatively small sample size of remimazolam reports in our dataset (N = 68) may limit the statistical power to detect very rare events, a common challenge in post-marketing surveillance for newer drugs [38]. Therefore, the safety signals identified here should be seen as important hypotheses requiring validation in future controlled studies.

Conclusion

By systematically analyzing real-world data from the FAERS database, this study provides a comprehensive post-marketing safety evaluation of remimazolam, filling a critical gap in the existing literature, which has primarily focused on pre-market clinical trials.

Our findings confirm remimazolam’s known benefits but also highlight several significant safety signals that warrant clinical attention. Most notably, we identified powerful signals for respiratory depression (e.g., Hypoventilation), serious cardiac events (e.g., Cardiac Arrest), and severe hypersensitivity reactions (e.g., Anaphylactic Shock). These findings underscore the need for vigilant monitoring and risk mitigation strategies during remimazolam use. Given that such risks may be amplified in vulnerable populations, as suggested by the broader clinical literature, our results highlight the importance of careful patient selection and monitoring, especially when treating elderly patients or those with significant comorbidities.

The signals identified in this pharmacovigilance study provide a critical foundation for future investigation. To advance from signal detection to confirmed risk assessment, it is essential that these findings are validated through large-scale, multicenter prospective studies. Such research is necessary to quantify adverse event incidence more precisely and establish definitive clinical guidelines. Furthermore, long-term follow-up studies utilizing real-world data from electronic health records (EHRs) will be crucial for assessing remimazolam’s long-term safety profile. Ultimately, this study provides a vital evidence base to inform safer clinical practice and guide future research, ensuring that the therapeutic benefits of remimazolam can be maximized while its risks are carefully managed.

Supporting information

S1 File. R script for FAERS data mining and analysis.

This file contains the complete R script used to perform the pharmacovigilance analysis. The script uses the faersR package to filter the FAERS database for adverse event reports associated with Remimazolam and to calculate key disproportionality metrics (e.g., ROR, PRR). The dplyr and openxlsx packages are subsequently used for data manipulation and to export the final result tables.

(R)

pone.0330769.s001.R (4.8KB, R)

Data Availability

All relevant data underlying the results presented in this study are publicly available from the FDA Adverse Event Reporting System (FAERS) database. The data used in this study cover the period from [specific time range, e.g., Q2 2020 to Q1 2023] and can be accessed via the FDA website at https://www.fda.gov/drugs/questions-and-answers-fdas-adverse-event-reporting-system-faers.

Funding Statement

The author(s) received no specific funding for this work.

References

  • 1.Keam SJ. Remimazolam: First Approval. Drugs. 2020;80(6):625–33. doi: 10.1007/s40265-020-01299-8 [DOI] [PubMed] [Google Scholar]
  • 2.Zhu H, Su Z, Huai X, Chen C, Zhang X, Zhou J, et al. Efficacy and safety of remimazolam tosylate for sedation during upper gastrointestinal endoscopy: study protocol for a multicenter randomized controlled trial. Trials. 2022;23(1):995. doi: 10.1186/s13063-022-06935-0 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 3.Kilpatrick GJ. Remimazolam: Non-Clinical and Clinical Profile of a New Sedative/Anesthetic Agent. Front Pharmacol. 2021;12:690875. doi: 10.3389/fphar.2021.690875 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 4.Zhang H, Li H, Zhao S, Bao F. Remimazolam in General Anesthesia: A Comprehensive Review of Its Applications and Clinical Efficacy. Drug Des Devel Ther. 2024;18:3487–98. doi: 10.2147/dddt.s474854 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 5.Yao Z, Liao Z, Li G, Wang L, Zhan L, Xia W. Remimazolam tosylate’s long-term sedative properties in ICU patients on mechanical ventilation: effectiveness and safety. Eur J Med Res. 2023;28(1):452. doi: 10.1186/s40001-023-01440-9 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 6.Wang Y, Zhao B, Yang H, Wan Z. A real-world pharmacovigilance study of FDA adverse event reporting system events for sildenafil. Andrology. 2024;12(4):785–92. doi: 10.1111/andr.13533 [DOI] [PubMed] [Google Scholar]
  • 7.Zhao B, Fu Y, Cui S, Chen X, Liu S, Luo L. A real-world disproportionality analysis of Everolimus: data mining of the public version of FDA adverse event reporting system. Front Pharmacol. 2024;15:1333662. doi: 10.3389/fphar.2024.1333662 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 8.Dhodapkar MM, Shi X, Ramachandran R, Chen EM, Wallach JD, Ross JS. Characterization and corroboration of safety signals identified from the US Food and Drug Administration Adverse Event Reporting System, 2008-19: cross sectional study. BMJ. 2022;379:e071752. doi: 10.1136/bmj-2022-071752 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 9.Giunchi V, Fusaroli M, Hauben M, Raschi E, Poluzzi E. Challenges and Opportunities in Accessing and Analysing FAERS Data: A Call Towards a Collaborative Approach. Drug Saf. 2023;46(10):921–6. doi: 10.1007/s40264-023-01345-w [DOI] [PubMed] [Google Scholar]
  • 10.Yang H, Wan Z, Chen M, Zhang X, Cui W, Zhao B. A real-world data analysis of topotecan in the FDA Adverse Event Reporting System (FAERS) database. Expert Opin Drug Metab Toxicol. 2023;19(4):217–23. doi: 10.1080/17425255.2023.2219390 [DOI] [PubMed] [Google Scholar]
  • 11.Zhao B, Zhang X, Chen M, Wang Y. A real-world data analysis of acetylsalicylic acid in FDA Adverse Event Reporting System (FAERS) database. Expert Opin Drug Metab Toxicol. 2023;19(6):381–7. doi: 10.1080/17425255.2023.2235267 [DOI] [PubMed] [Google Scholar]
  • 12.Li J, Zhao B, Zhu Y, Wu J. Vitreoretinal Traction Syndrome, Nitrituria and Human Epidermal Growth Factor Receptor Negative Might Occur in the Aromatase-Inhibitor Anastrozole Treatment. Int J Clin Pract. 2024;2024:1–9. doi: 10.1155/2024/5132916 [DOI] [Google Scholar]
  • 13.Zhong C, Zheng Q, Zhao B, Ren T. A real-world pharmacovigilance study using disproportionality analysis of United States Food and Drug Administration Adverse Event Reporting System events for vinca alkaloids: comparing vinorelbine and Vincristine. Expert Opin Drug Saf. 2024;23(11):1427–37. doi: 10.1080/14740338.2024.2410436 [DOI] [PubMed] [Google Scholar]
  • 14.Huang F, San X, Liu Q, Zhu H, Xu W. Signal mining and risk analysis of Alprazolam adverse events based on the FAERS database. Sci Rep. 2024;14(1):7489. doi: 10.1038/s41598-024-57909-y [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 15.Pan Y, Wang Y, Zheng Y, Chen J, Li J. A disproportionality analysis of FDA adverse event reporting system (FAERS) events for ticagrelor. Front Pharmacol. 2024;15:1251961. doi: 10.3389/fphar.2024.1251961 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 16.Jung D, Jung I. A simulation-based comparison of drug-drug interaction signal detection methods. PLoS ONE. 2024;19(4):e0300268. doi: 10.1371/journal.pone.0300268 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 17.Hauben M, Zhou X. Quantitative methods in pharmacovigilance: focus on signal detection. Drug Saf. 2003;26(3):159–86. doi: 10.2165/00002018-200326030-00003 [DOI] [PubMed] [Google Scholar]
  • 18.Ahlmann-Eltze C, Huber W. glmGamPoi: fitting Gamma-Poisson generalized linear models on single cell count data. Bioinformatics. 2020;36(24):5701–2. doi: 10.1093/bioinformatics/btaa1009 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 19.Lerch M, Nowicki P, Manlik K, Wirsching G. Statistical Signal Detection as a Routine Pharmacovigilance Practice: Effects of Periodicity and Resignalling Criteria on Quality and Workload. Drug Saf. 2015;38(12):1219–31. doi: 10.1007/s40264-015-0345-1 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 20.Lee A, Shirley M. Remimazolam: A Review in Procedural Sedation. Drugs. 2021;81(10):1193–201. doi: 10.1007/s40265-021-01544-8 [DOI] [PubMed] [Google Scholar]
  • 21.Hu Q, Liu X, Wen C, Li D, Lei X. Remimazolam: An Updated Review of a New Sedative and Anaesthetic. Drug Des Devel Ther. 2022;16:3957–74. doi: 10.2147/DDDT.S384155 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 22.Tang Y, Gao X, Xu J, Ren L, Qi H, Li R, et al. Remimazolam besylate versus propofol for deep sedation in critically ill patients: a randomized pilot study. Crit Care. 2023;27(1):474. doi: 10.1186/s13054-023-04760-8 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 23.Garrett A, Flowers J, Ng V, Tobias JD. Remimazolam for Sedation During Upper Gastrointestinal Endoscopy in an Adolescent. J Med Cases. 2022;13(10):495–8. doi: 10.14740/jmc4013 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 24.Heo HJ, Kim G, Kim YY, Park J. Can remimazolam be safely used in cardiac tamponade?: A case report. Medicine (Baltimore). 2023;102(32):e34822. doi: 10.1097/MD.0000000000034822 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 25.Qiu Y, Gu W, Zhao M, Zhang Y, Wu J. The hemodynamic stability of remimazolam compared with propofol in patients undergoing endoscopic submucosal dissection: A randomized trial. Front Med. 2022;9:938940. doi: 10.3389/fmed.2022.938940 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 26.Kitaura A, Sakamoto H, Hamasaki S, Tsukimoto S, Nakajima Y. Remimazolam-Based Anesthesia in Patients with Heart Failure Due to Mitral Regurgitation and Low Left Ventricular Function: A Case Series. Medicina. 2023;59(12):2136. doi: 10.3390/medicina59122136 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 27.Oka S, Satomi H, Sekino R, Taguchi K, Kajiwara M, Oi Y, et al. Sedation outcomes for remimazolam, a new benzodiazepine. J Oral Sci. 2021;63(3):209–11. doi: 10.2334/josnusd.21-0051 [DOI] [PubMed] [Google Scholar]
  • 28.Kempenaers S, Hansen TG, Van de Velde M. Remimazolam and serious adverse events: A scoping review. Eur J Anaesthesiol. 2023;40(11):841–53. doi: 10.1097/EJA.0000000000001902 [DOI] [PubMed] [Google Scholar]
  • 29.Hu K, Xiang Q, Wang Z, Sheng X, Li L, Liang Y, et al. Effects of Vitamin D Receptor, Cytochrome P450 3A, and Cytochrome P450 Oxidoreductase Genetic Polymorphisms on the Pharmacokinetics of Remimazolam in Healthy Chinese Volunteers. Clin Pharmacol Drug Dev. 2021;10(1):22–9. doi: 10.1002/cpdd.797 [DOI] [PubMed] [Google Scholar]
  • 30.Nakayama J, Ogihara T, Yajima R, Innami Y, Ouchi T. Anesthetic management of super-elderly patients with remimazolam: a report of two cases. JA Clin Rep. 2021;7(1):71. doi: 10.1186/s40981-021-00474-4 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 31.Liu T, Zhao H, Zhao X, Qu M. Comparison of Remimazolam and Propofol on Postoperative Delirium in Elderly Patients Undergoing Radical Resection of Colon Cancer: A Single-Center Prospective Randomized Controlled Study. Med Sci Monit. 2024;30:e943784. doi: 10.12659/MSM.943784 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 32.Xu Q, Wu J, Shan W, Duan G, Lan H. Effects of remimazolam combined with sufentanil on hemodynamics during anesthetic induction in elderly patients with mild hypertension undergoing orthopedic surgery of the lower limbs: a randomized controlled trial. BMC Anesthesiol. 2023;23(1):311. doi: 10.1186/s12871-023-02249-z [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 33.Mao Y, Guo J, Yuan J, Zhao E, Yang J. Quality of Recovery After General Anesthesia with Remimazolam in Patients’ Undergoing Urologic Surgery: A Randomized Controlled Trial Comparing Remimazolam with Propofol. Drug Des Devel Ther. 2022;16:1199–209. doi: 10.2147/DDDT.S359496 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 34.Sekiguchi R, Kinoshita M, Kawanishi R, Kakuta N, Sakai Y, Tanaka K. Comparison of hemodynamics during induction of general anesthesia with remimazolam and target-controlled propofol in middle-aged and elderly patients: a single-center, randomized, controlled trial. BMC Anesthesiol. 2023;23(1):14. doi: 10.1186/s12871-023-01974-9 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 35.Wang M, Zhao X, Yin P, Bao X, Tang H, Kang X. Profile of Remimazolam in Anesthesiology: A Narrative Review of Clinical Research Progress. Drug Des Devel Ther. 2022;16:3431–44. doi: 10.2147/DDDT.S375957 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 36.García-Abeijon P, Costa C, Taracido M, Herdeiro MT, Torre C, Figueiras A. Factors Associated with Underreporting of Adverse Drug Reactions by Health Care Professionals: A Systematic Review Update. Drug Saf. 2023;46(7):625–36. doi: 10.1007/s40264-023-01302-7 [DOI] [PMC free article] [PubMed] [Google Scholar]
  • 37.Scosyrev E, Behr S, Jain D, Ponnuru A, Michel C. Disproportionality Analysis and Causal Inference in Drug Safety. Pharmaceut Med. 2025;39(2):97–107. doi: 10.1007/s40290-024-00549-4 [DOI] [PubMed] [Google Scholar]
  • 38.Shi Y, Zhang L, Diao Y, Zhao M. The effect of toluene sulfonic acid remimazolam on postoperative delirium in elderly patients undergoing painless bronchoscopy. Sci Rep. 2024;14(1):31239. doi: 10.1038/s41598-024-82582-6 [DOI] [PMC free article] [PubMed] [Google Scholar]

Decision Letter 0

Anmar Al-Taie

28 Apr 2025

PONE-D-24-58735Remimazolam’s Clinical Application and Safety: A Signal Detection Analysis Based on FAERS Data and Literature SupportPLOS ONE

Dear Dr.  Zhou,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

Please submit your revised manuscript by Jun 12 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.

  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.

  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

  If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols .

We look forward to receiving your revised manuscript.

Kind regards,

Anmar Al-Taie, Ph.D.

Academic Editor

PLOS ONE

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1.Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at

https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. Please note that PLOS ONE has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, we expect all author-generated code to be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse.

3. Please ensure that you refer to Figure 1 and 2 in your text as, if accepted, production will need this reference to link the reader to the figure.

4. Please include your tables as part of your main manuscript and remove the individual files. Please note that supplementary tables (should remain/ be uploaded) as separate "supporting information" files.

5. Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice.

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

**********

2. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

**********

3. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

**********

4. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

**********

5. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: Zhou et al entitle “Remimazolam’s Clinical Application and Safety: A Signal Detection Analysis Based on FAERS Data and Literature Support ” clearly reported that Remimazolam could be adverse drug for procedures requiring quick recovery, procedural sedation, and general anesthesia.

Why are you using the FAERS database to study this drug, it should be that someone else has done this with this similar database similar methodology, so you can write cite in the INTRODUCTION section about some specific other similar studies, such as recommending a few (It is equivalent to saying that someone else has done this type of research using the FAERS database, and you can use this database to do research related to Remimazolam as well):【1】Wang Y, Zhao B, Yang H, Wan Z. A real-world pharmacovigilance study of FDA adverse event reporting system events for sildenafil. Andrology. 2024 May;12(4):785-792. doi: 10.1111/andr.13533. Epub 2023 Sep 19. PMID: 37724699.

【2】Zhao B, Fu Y, Cui S, Chen X, Liu S, Luo L. A real-world disproportionality analysis of Everolimus: data mining of the public version of FDA adverse event reporting system. Front Pharmacol. 2024 Mar 12;15:1333662. doi: 10.3389/fphar.2024.1333662. PMID: 38533254; PMCID: PMC10964017.【3】Yang H, Wan Z, Chen M, Zhang X, Cui W, Zhao B. A real-world data analysis of topotecan in the FDA Adverse Event Reporting System (FAERS) database. Expert Opin Drug Metab Toxicol. 2023 Apr;19(4):217-223. doi: 10.1080/17425255.2023.2219390. Epub 2023 May 30. PMID: 37243615.【4】Zhao B, Zhang X, Chen M, Wang Y. A real-world data analysis of acetylsalicylic acid in FDA Adverse Event Reporting System (FAERS) database. Expert Opin Drug Metab Toxicol. 2023 Jan-Jun;19(6):381-387. doi: 10.1080/17425255.2023.2235267. Epub 2023 Jul 12. PMID: 37421631.【5】Li, Jie, Zhao, Bin, Zhu, YongQing, Wu, Jibiao, Vitreoretinal Traction Syndrome, Nitrituria and Human Epidermal Growth Factor Receptor Negative Might Occur in the Aromatase-Inhibitor Anastrozole Treatment, International Journal of Clinical Practice, 2024, 5132916, 9 pages, 2024. https://doi.org/10.1155/2024/5132916【6】Zhong, C., Zheng, Q., Zhao, B., & Ren, T. (2024). A real-world pharmacovigilance study using disproportionality analysis of United States Food and Drug Administration Adverse Event Reporting System events for vinca alkaloids: comparing vinorelbine and Vincristine. Expert Opinion on Drug Safety, 23(11), 1427–1437. https://doi.org/10.1080/14740338.2024.2410436

Besides,

Minior Issues:

1)Simplify complex sentences to improve readability. For example, revise "particularly focusing on its safety in the respiratory, cardiovascular, and immune systems" to "with a focus on its safety in major organ systems, including respiratory, cardiovascular, and immune systems."

2)Clarify the time frame covered by the FAERS data (e.g., specific months or quarters) to enhance transparency.

3)Explain why a threshold of three cases was chosen for signal analysis in "Signal Screening and Classification."

4)For Table 2, provide a brief interpretation of the ROR and PRR values in the text, especially for high-risk signals like hypoventilation and anaphylactic shock, to aid readers unfamiliar with these metrics.

5)Improve Figure 1's clarity by enlarging text and refining the labels for better visualization.

6)Correct minor grammatical issues, such as replacing "remimazolam may trigger serious immune responses during clinical use" with "remimazolam may elicit serious immune responses in clinical settings."

7)Include a forward-looking statement emphasizing the need for multicenter prospective studies to validate these findings.

**********

6. PLOS authors have the option to publish the peer review history of their article (what does this mean? ). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy .

Reviewer #1: No

**********

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org . Please note that Supporting Information files do not need this step.

PLoS One. 2025 Aug 22;20(8):e0330769. doi: 10.1371/journal.pone.0330769.r002

Author response to Decision Letter 1


13 Jun 2025

We sincerely thank Reviewer #1 for their positive evaluation and insightful suggestions, which have helped us improve the quality of our manuscript.

Point-by-point response

Reviewer #1:

Comment

Zhou et al entitle “Remimazolam’s Clinical Application and Safety: A Signal Detection Analysis Based on FAERS Data and Literature Support ” clearly reported that Remimazolam could be adverse drug for procedures requiring quick recovery, procedural sedation, and general anesthesia.

Why are you using the FAERS database to study this drug, it should be that someone else has done this with this similar database similar methodology, so you can write cite in the INTRODUCTION section about some specific other similar studies, such as recommending a few (It is equivalent to saying that someone else has done this type of research using the FAERS database, and you can use this database to do research related to Remimazolam as well):

【1】Wang Y, Zhao B, Yang H, Wan Z. A real-world pharmacovigilance study of FDA adverse event reporting system events for sildenafil. Andrology. 2024 May;12(4):785-792. doi: 10.1111/andr.13533. Epub 2023 Sep 19. PMID: 37724699.

【2】Zhao B, Fu Y, Cui S, Chen X, Liu S, Luo L. A real-world disproportionality analysis of Everolimus: data mining of the public version of FDA adverse event reporting system. Front Pharmacol. 2024 Mar 12;15:1333662. doi: 10.3389/fphar.2024.1333662. PMID: 38533254; PMCID: PMC10964017.

【3】Yang H, Wan Z, Chen M, Zhang X, Cui W, Zhao B. A real-world data analysis of topotecan in the FDA Adverse Event Reporting System (FAERS) database. Expert Opin Drug Metab Toxicol. 2023 Apr;19(4):217-223. doi: 10.1080/17425255.2023.2219390. Epub 2023 May 30. PMID: 37243615.

【4】Zhao B, Zhang X, Chen M, Wang Y. A real-world data analysis of acetylsalicylic acid in FDA Adverse Event Reporting System (FAERS) database. Expert Opin Drug Metab Toxicol. 2023 Jan-Jun;19(6):381-387. doi: 10.1080/17425255.2023.2235267. Epub 2023 Jul 12. PMID: 37421631.

【5】Li, Jie, Zhao, Bin, Zhu, YongQing, Wu, Jibiao, Vitreoretinal Traction Syndrome, Nitrituria and Human Epidermal Growth Factor Receptor Negative Might Occur in the Aromatase-Inhibitor Anastrozole Treatment, International Journal of Clinical Practice, 2024, 5132916, 9 pages, 2024. https://doi.org/10.1155/2024/5132916

【6】Zhong, C., Zheng, Q., Zhao, B., & Ren, T. (2024). A real-world pharmacovigilance study using disproportionality analysis of United States Food and Drug Administration Adverse Event Reporting System events for vinca alkaloids: comparing vinorelbine and Vincristine. Expert Opinion on Drug Safety, 23(11), 1427–1437. https://doi.org/10.1080/14740338.2024.2410436

Response: We sincerely thank the reviewer for this insightful comment and for providing a valuable list of relevant literature. We agree that highlighting previous studies employing similar methodologies with the FAERS database strengthens the rationale for our approach.

In response to this suggestion, we have revised the Introduction section to explicitly state why the FAERS database is a suitable and established tool for pharmacovigilance studies like ours. We have now incorporated citations to several studies, including those kindly recommended by the reviewer, that have successfully utilized the FAERS database for signal detection and real-world safety assessments of various drugs.

Specifically, the following paragraph has been added to the Introduction:

"Indeed, pharmacovigilance studies using real-world databases are instrumental for assessing the post-marketing safety profiles of various therapeutics. These studies complement findings from pre-approval clinical trials, as seen in studies on sildenafil [6] and everolimus [7]. The utility of FAERS for such pharmacovigilance, and its capacity for signal detection in diverse therapeutic areas, is well-documented in studies concerning topotecan [10], acetylsalicylic acid [11], anastrozole [12], and vinca alkaloids [13]."

We believe these additions clearly demonstrate the precedent and justification for using the FAERS database for our investigation of remimazolam and appropriately acknowledge the utility of this approach as established by prior research. We are grateful for the reviewer's guidance in enhancing this aspect of our manuscript.

Minior Issues:

Question1: Simplify complex sentences to improve readability. For example, revise "particularly focusing on its safety in the respiratory, cardiovascular, and immune systems" to "with a focus on its safety in major organ systems, including respiratory, cardiovascular, and immune systems.

Response: Thank you for this essential feedback. We are sincerely grateful for your specific guidance on improving the manuscript's clarity, as this is a point of utmost importance to us.

We would also like to transparently explain our revision process in response to your invaluable feedback. Upon receiving your comments, we first addressed this specific point by performing a thorough revision of the entire manuscript based on the principle you outlined.

Subsequently, your other linguistic feedback (particularly in Point 6) inspired us to undertake an even deeper, more holistic overhaul of the paper's language. This second-stage revision was so comprehensive that many sections, including the one containing the original example sentence, were completely rewritten to improve flow and impact.

Therefore, while the exact sentence you highlighted may no longer exist in its revised form, please be assured that the core principle of your suggestion was the guiding force behind our entire linguistic refinement. To demonstrate our commitment to your advice, here is the methodology we applied systematically across the whole manuscript:

We broke down long, complex sentences into shorter, more direct statements.

We rephrased complex clauses and participial phrases to make logical connections explicit and unambiguous.

We used simpler conjunctions and clearer transitions to guide the reader smoothly through our arguments.

We hope this explanation clarifies our dedicated approach. Your combined feedback prompted a level of revision that we believe has elevated the entire manuscript. We are truly appreciative of the opportunity you gave us to so thoroughly improve our work.

Question2: Clarify the time frame covered by the FAERS data (e.g., specific months or quarters) to enhance transparency.

Response: Thank you for highlighting the need for greater transparency on this point. To address this comprehensively, we have revised the "Data Source and Preprocessing" subsection in our Methods. We now explicitly state that our search encompassed the full database period from 2004 to 2023, and clarify that the resulting reports for our drug of interest, Remimazolam, were found to span from 2020 to 2023. This detail is crucial for accurately describing our dataset. The revised text in the manuscript now reads:

" This study is based on data from the U.S. Food and Drug Administration's (FDA) Adverse Event Reporting System (FAERS), a public database of spontaneous adverse event reports submitted by patients, healthcare professionals, and pharmaceutical manufacturers. For our analysis, we queried the entire available database, spanning from the first quarter of 2004 to the fourth quarter of 2023, to extract all reports associated with Remimazolam. The resulting dataset of relevant reports for this drug covered the period from the second quarter of 2020 to the first quarter of 2023, and this forms the basis of our study."

Question3: Explain why a threshold of three cases was chosen for signal analysis in "Signal Screening and Classification.".

Response: Thank you for this insightful question and the opportunity to elaborate on this key methodological choice.

Our selection of a minimum of three reports (N ≥ 3) is a standard pharmacovigilance practice designed to ensure the statistical robustness of our findings. This threshold serves two primary functions:

1. Enhancing Statistical Stability: It provides a more stable foundation for disproportionality calculations (like ROR), reducing the risk of spurious signals that can arise from one or two isolated reports.

2. Reducing Analytical Noise: It helps filter out coincidental or isolated case reports common in spontaneous reporting systems, thereby improving the specificity of the detected signals.

This approach is well-supported in the literature. For instance, a study by Lerch et al. (2015) in the journal Drug Safety employed this exact criterion (N ≥ 3) for signal detection in the FAERS database.

To make this rationale clear in the manuscript, we have now added the following explanation to the Methodology section, under the Signal Screening and Classification subsection, and have included the supporting citation:

"This threshold (N ≥ 3) is a commonly adopted criterion in pharmacovigilance to enhance the stability of disproportionality measures and to reduce the likelihood of spurious signals arising from isolated case reports [14]."

We thank you for prompting this important clarification.

Question4: For Table 2, provide a brief interpretation of the ROR and PRR values in the text, especially for high-risk signals like hypoventilation and anaphylactic shock, to aid readers unfamiliar with these metrics..

Response: Thank you for this excellent suggestion. We agree that providing a clear interpretation of the ROR values is essential for making our findings accessible to a broader audience.

To address this, we have substantially revised the Results section. Within the main text, for each of the key adverse events discussed, we have now added a plain-language interpretation of its corresponding ROR value from Table 2.

For instance, for the high-risk signals you highlighted:

• For Hypoventilation, which has an ROR of approximately 450, we now explain in the text that this means the event was reported over 400 times more frequently than expected.

• For Anaphylactic shock, with an ROR of about 106, we clarify in the text that reports were more than 100 times more frequent than expected.

This interpretive approach has been applied systematically throughout the text to other significant signals, such as Cardio-respiratory arrest and Blood pressure decreased, to give readers a clear sense of the signal strength.

We are confident that these additions make the clinical implications of our quantitative findings much clearer, and we appreciate your guidance on improving the paper's accessibility.

Question5: Improve Figure 1's clarity by enlarging text and refining the labels for better visualization.

Response: Thank you very much for your thoughtful comment. I have made sincere efforts to improve the clarity of Figure 1, including enlarging the text and refining the labels as suggested. However, due to limitations in PDF rendering, some loss of resolution may still occur in the final compiled version.

To address this, I have re-inserted a high-resolution version of the figure directly into the main manuscript, following the editorial office's instruction to embed all figures within the text. While the clarity has been improved, the figure might still appear slightly different compared to earlier versions.

The revised figure is placed below for your kind review. Should you still find the clarity unsatisfactory, please kindly indicate it in your response, and I will make further revisions accordingly.

Question6: Correct minor grammatical issues, such as replacing "remimazolam may trigger serious immune responses in clinical use" with "remimazolam may elicit serious immune responses in clinical settings."

Response:

Thank you for your invaluable guidance. The phrasing you suggested is indeed far more precise and professional.

Following your expert advice, we have not only incorporated this specific change but have also taken this opportunity to conduct a comprehensive review of the entire manuscript. We have meticulously polished the language throughout the paper to enhance its overall clarity, precision, and scholarly tone.

We are sincerely grateful for the chance to improve our work under your direction. Your keen insights have been instrumental in elevating the quality of our manuscript to meet the high standards of PLOS ONE.

Question7: Include a forward-looking statement emphasizing the need for multicenter prospective studies to validate these findings.

Response:

Thank you for this important suggestion. We agree that adding this forward-looking statement strengthens the manuscript's conclusion.

Following your advice, we have revised the final paragraph of our Conclusion section to explicitly emphasize the need for future validation. The revised text now includes the statement: "To advance from signal detection to confirmed risk assessment, it is essential that these findings are validated through large-scale, multicenter prospective studies."

We believe this revision improves the paper, and we thank you again for your valuable input.

We thank you and the reviewer once again for your valuable time and guidance. We have uploaded a clean version of the manuscript and a version with tracked changes for your convenience. We hope that the revised manuscript is now suitable for publication in PLOS ONE.

Sincerely,

Qingbo Zhou, on behalf of all authors.

Attachment

Submitted filename: PONE-D-24-58735_Response_to_Reviewers.docx

pone.0330769.s003.docx (124.1KB, docx)

Decision Letter 1

Anmar Al-Taie

25 Jul 2025

PONE-D-24-58735R1Remimazolam’s Clinical Application and Safety: A Signal Detection Analysis Based on FAERS Data and Literature SupportPLOS ONE

Dear Dr. Zhou,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

Please submit your revised manuscript by Sep 08 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.

  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.

  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols .

We look forward to receiving your revised manuscript.

Kind regards,

Anmar AL-TAIE, Ph.D.

Academic Editor

PLOS ONE

Journal Requirements:

If the reviewer comments include a recommendation to cite specific previously published works, please review and evaluate these publications to determine whether they are relevant and should be cited. There is no requirement to cite these works unless the editor has indicated otherwise. 

Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice.

Additional Editor Comments:

Editor comments

• There are some minor grammatical issues that need to be corrected.

• What are the authors trying to say by this incomplete sentence’ reduce the probability of spurious signals from isolated case reports (e.g.,[19]).’’

• The text for some responses is not available within the main paper body. Try to be committed to the responses.

• The authors mention several times ‘such as elderly patients and individuals with pre-existing comorbidities’’ We could not recognize these comorbidities with this small sample size. In addition, there are no results that show such an association with these variables. Consider addressing this concern while providing more details and a table for the common comorbidities.

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org . Please note that Supporting Information files do not need this step.

PLoS One. 2025 Aug 22;20(8):e0330769. doi: 10.1371/journal.pone.0330769.r004

Author response to Decision Letter 2


31 Jul 2025

July 30, 2025

Dr. Anmar AL-TAIE

Academic Editor

PLOS ONE

Subject: Submission of Revised Manuscript (ID: PONE-D-24-58735R1)

Dear Dr. AL-TAIE,

Thank you for your email and for the opportunity to revise our manuscript, “Remimazolam’s Clinical Application and Safety: A Signal Detection Analysis Based on FAERS Data and Literature Support” (ID: PONE-D-24-58735R1). We sincerely appreciate the time and effort you have dedicated to providing feedback on our work.

We have carefully considered all the comments and have revised the manuscript accordingly. We believe the manuscript has been significantly improved as a result. Below is a point-by-point response to the comments.

________________________________________

Response to Editor's Comments:

Comment 1: "There are some minor grammatical issues that need to be corrected."

Our Response: We thank you for this valuable feedback. We have thoroughly proofread the entire manuscript to correct all grammatical and stylistic issues. We have carefully revised sentence structures, ensured consistent use of verb tenses, improved punctuation, and enhanced the overall clarity and readability of the text. We are confident that the revised manuscript now meets the journal's standards for language.

Comment 2: "What are the authors trying to say by this incomplete sentence’ reduce the probability of spurious signals from isolated case reports (e.g.,[19]).’’”

Our Response: We sincerely apologize for this unclear sentence structure and thank you for pointing it out. The original phrasing was awkward. We intended to explain the rationale for setting a minimum threshold for adverse event reports.

We have now revised this sentence in the “Signal Screening and Classification” section to be clear and complete. The sentence now reads:

"This threshold is a standard practice in pharmacovigilance to increase the stability of the analysis and reduce the probability of spurious signals from isolated case reports [19]."

Comment 3: "The text for some responses is not available within the main paper body. Try to be committed to the responses."

Our Response: We would like to offer our sincerest apologies for this critical oversight and the inconsistency between our previous rebuttal letter and the revised manuscript. This was our mistake, and we deeply appreciate you bringing it to our attention.

We have now taken corrective action to ensure all promised changes are implemented. The sentence regarding the methodological justification for the N ≥ 3 threshold, which we had previously promised to include, has now been correctly inserted into the “Signal Screening and Classification” section of the manuscript.

To ensure full compliance, we have conducted an additional, thorough review of the entire manuscript against our previous rebuttal letter to confirm that all promised changes have been implemented accurately. We apologize again for the inconvenience this has caused.

Comment 4: "The authors mention several times ‘such as elderly patients and individuals with pre-existing comorbidities’’ We could not recognize these comorbidities with this small sample size. In addition, there are no results that show such an association with these variables. Consider addressing this concern while providing more details and a table for the common comorbidities."

Our Response: We are exceptionally grateful for this insightful and critical comment. We agree completely that our previous statements regarding high-risk populations were not supported by our own data. This was a significant oversight, and we sincerely apologize. Your feedback has been invaluable in helping us correct this, thereby greatly enhancing the scientific integrity and credibility of our manuscript.

As you suggested, we initially considered creating a table for comorbidities. However, upon careful re-evaluation of our small dataset (N=68), we concluded that the available comorbidity data was not sufficiently detailed or robust for a meaningful analysis. We believe that presenting a table based on such limited information could be potentially misleading to readers.

Therefore, to address your concern in the most scientifically rigorous manner, we have undertaken a comprehensive revision of the Abstract, Discussion, and Conclusion sections. We have meticulously rephrased every statement that linked adverse event risks to specific populations (such as the elderly or those with comorbidities). These statements now clearly and explicitly attribute such information to the existing body of literature, using it as context for our findings, rather than presenting it as a conclusion from our analysis.

For example, a statement in the Discussion section was revised from:

• Original: "These risks appear to be most pronounced in high-risk populations, such as elderly patients and individuals with pre-existing comorbidities[3]."

• Revised: "Existing literature suggests that such risks can be more pronounced in high-risk populations, such as elderly patients and individuals with pre-existing comorbidities [3], which underscores the need for heightened caution..."

We believe these thorough revisions have fully resolved the issue by ensuring our conclusions are strictly aligned with our data. We are truly thankful for your guidance, which has prevented us from making a serious error and has significantly improved the quality of our paper.

________________________________________

We hope that the revised manuscript is now suitable for publication in PLOS ONE. We look forward to hearing from you.

Sincerely,

Dr. Qingbo Zhou

Corresponding Author

Department of Internal Medicine, Shaoxing Yuecheng People's Hospital, Shaoxing, China

E-mail: zhouqingbo@zcmu.edu.cn

Attachment

Submitted filename: Response to Editor.docx

pone.0330769.s004.docx (18.5KB, docx)

Decision Letter 2

Anmar Al-Taie

6 Aug 2025

Remimazolam’s Clinical Application and Safety: A Signal Detection Analysis Based on FAERS Data and Literature Support

PONE-D-24-58735R2

Dear Qingbo Zhou,

We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements.

Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication.

An invoice will be generated when your article is formally accepted. Please note, if your institution has a publishing partnership with PLOS and your article meets the relevant criteria, all or part of your publication costs will be covered. Please make sure your user information is up-to-date by logging into Editorial Manager at Editorial Manager®  and clicking the ‘Update My Information' link at the top of the page. For questions related to billing, please contact billing support .

If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

Kind regards,

Dr. Anmar Al-Taie

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Acceptance letter

Anmar Al-Taie

PONE-D-24-58735R2

PLOS ONE

Dear Dr. Zhou,

I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now being handed over to our production team.

At this stage, our production department will prepare your paper for publication. This includes ensuring the following:

* All references, tables, and figures are properly cited

* All relevant supporting information is included in the manuscript submission,

* There are no issues that prevent the paper from being properly typeset

You will receive further instructions from the production team, including instructions on how to review your proof when it is ready. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few days to review your paper and let you know the next and final steps.

Lastly, if your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

You will receive an invoice from PLOS for your publication fee after your manuscript has reached the completed accept phase. If you receive an email requesting payment before acceptance or for any other service, this may be a phishing scheme. Learn how to identify phishing emails and protect your accounts at https://explore.plos.org/phishing.

If we can help with anything else, please email us at customercare@plos.org.

Thank you for submitting your work to PLOS ONE and supporting open access.

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr. Anmar Al-Taie

Academic Editor

PLOS ONE

Associated Data

    This section collects any data citations, data availability statements, or supplementary materials included in this article.

    Supplementary Materials

    S1 File. R script for FAERS data mining and analysis.

    This file contains the complete R script used to perform the pharmacovigilance analysis. The script uses the faersR package to filter the FAERS database for adverse event reports associated with Remimazolam and to calculate key disproportionality metrics (e.g., ROR, PRR). The dplyr and openxlsx packages are subsequently used for data manipulation and to export the final result tables.

    (R)

    pone.0330769.s001.R (4.8KB, R)
    Attachment

    Submitted filename: PONE-D-24-58735_Response_to_Reviewers.docx

    pone.0330769.s003.docx (124.1KB, docx)
    Attachment

    Submitted filename: Response to Editor.docx

    pone.0330769.s004.docx (18.5KB, docx)

    Data Availability Statement

    All relevant data underlying the results presented in this study are publicly available from the FDA Adverse Event Reporting System (FAERS) database. The data used in this study cover the period from [specific time range, e.g., Q2 2020 to Q1 2023] and can be accessed via the FDA website at https://www.fda.gov/drugs/questions-and-answers-fdas-adverse-event-reporting-system-faers.


    Articles from PLOS One are provided here courtesy of PLOS

    RESOURCES