Peer Review History

Original SubmissionJune 19, 2025
Decision Letter - Nestor Oliva Damaso, Editor

PONE-D-25-32339Safety assessment of obinutuzumab: Real-world adverse event analysis based on the FAERS and JADER databases from 2013 to 2025PLOS ONE

Dear Dr. Cao,

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 15 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,

Nestor Oliva Damaso

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. We note that your Data Availability Statement is currently as follows: [All relevant data are within the manuscript and its Supporting Information files]

Please confirm at this time whether or not your submission contains all raw data required to replicate the results of your study. Authors must share the “minimal data set” for their submission. PLOS defines the minimal data set to consist of the data required to replicate all study findings reported in the article, as well as related metadata and methods (https://journals.plos.org/plosone/s/data-availability#loc-minimal-data-set-definition).

For example, authors should submit the following data:

- The values behind the means, standard deviations and other measures reported;

- The values used to build graphs;

- The points extracted from images for analysis.

Authors do not need to submit their entire data set if only a portion of the data was used in the reported study.

If your submission does not contain these data, please either upload them as Supporting Information files or deposit them to a stable, public repository and provide us with the relevant URLs, DOIs, or accession numbers. For a list of recommended repositories, please see https://journals.plos.org/plosone/s/recommended-repositories.

If there are ethical or legal restrictions on sharing a de-identified data set, please explain them in detail (e.g., data contain potentially sensitive information, data are owned by a third-party organization, etc.) and who has imposed them (e.g., an ethics committee). Please also provide contact information for a data access committee, ethics committee, or other institutional body to which data requests may be sent. If data are owned by a third party, please indicate how others may request data access.

4. 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. 

[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

Reviewer #2: Partly

**********

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

Reviewer #1: Yes

Reviewer #2: No

**********

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

Reviewer #2: No

**********

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

Reviewer #2: No

**********

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: The authors have systematically and rigorously analyzed the adverse effects (AE)caused by obinutuzumab using two large (FAERS and JADER) databases.

The paper provides an interesting compilation of the drug's main AE. Considering the increasingly widespread use of this drug, it will be useful for the reader.

To enhance the interest of the paper, I suggest the following points:

1. AE may have a greater or lesser incidence and severity depending on the pathology being treated. This last aspect (indications) is poorly developed in the manuscript. They are only briefly discussed in the section about baseline characteristics, and the 5 main indications (CLL, follicular lymphoma, B-cell lymphoma, etc.) are presented in Table 3. However, these 5 top indications include “prescriptions for unknown causes” and "Other." It would be helpful to show the most common indications within the group “Other”.

2. Among the indications for obinutuzumab, its use in rheumatologic and systemic diseases will become increasingly important, given its greater efficacy than rituximab (e.g., lupus nephritis). It would be interesting to compare the frequency, characteristics, and severity of AE in hematologic malignancies (CLL, follicular or B-cell lymphomas, etc.) with non-tumoral indications.

3. In relation to the two previous points, the interest of this paper would be enhanced by analyzing AE of a recently published large trial of obinutuzumab in lupus nephritis (REGENCY; NEJM 2025; 392: 1471-83), using the same methodology applied in this paper and comparing them with the AE observed in other pathologies.

Reviewer #2: The authors conduct a large-scale, real-world pharmacovigilance analysis of adverse events (AEs) associated with obinutuzumab by analyzing the FAERS and JADER databases. They apply multiple signal detection algorithms (ROR, PRR, BCPNN, EBGM) to identify risk signals that are not currently documented in the product label. The study addresses a relevant clinical issue, post-marketing surveillance of monoclonal antibody therapies, and provides real-world evidence. However, the current manuscript lacks critical depth in interpretation, reproducibility, and clarity of English language, which limits its impact.

Main comments:

In my opinion, the study demonstrates insufficient depth in the interpretation of the data:

The authors mainly report signal values without providing a clinical context for many of the findings.

A more in-depth discussion is needed on how these adverse events may arise from a mechanistic point of view and how they compare with similar monoclonal antibodies (rituximab).

I recommend including a meta-analysis or comparative safety analysis with the existing literature to strengthen the conclusions, which appear to be only comments or opinions without scientific rigor.

Language and grammar require revision

The manuscript contains multiple grammatical and structural errors and variations that affect readability. A thorough review by a native English speaker is recommended.

Lack of methodological transparency

The search criteria and exact filters used for FAERS and JADER are not clearly described. Without this information, the analysis is not reproducible. I recommend including a flow chart showing the number of reports included/excluded.

Does not control for confounding or bias in spontaneous reports:

The study should better acknowledge and discuss the limitations of spontaneous reports, including under-reporting, duplicate reports, and lack of denominator data. Consider incorporating a refined risk signal strategy or validating signals with external databases.

Clarify statistical methods:

Formulas and thresholds are included, but justification for the choice of methods is lacking. Statistical corrections are also missing.

Weak conclusions and no meaningful clinical recommendations: The current conclusion merely repeats the results. Provide clinical recommendations (follow-up needs, high-risk patient profiles) and discuss implications for prescribing.

Consider moving the technical descriptions of the algorithms (i.e., BCPNN formulas) to the supplementary material to improve the flow of the manuscript.

Tables 4 and 5 are dense and difficult to interpret. Highlight their content more clearly.

Abbreviations (NHL, ... see text) should be defined consistently the first time they are used.

There are several repeated references to “not registered in the specification”; clearly define what “specification” refers to.

**********

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: Yes:  Manuel Praga

Reviewer #2: 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.

Revision 1

Respond to academic editor

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.

Answer: Thank you very much for your valuable comments. We have revised the manuscript format as per the requirements.

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.

Answer: The code has been uploaded as a supplementary information file (S1_File).

3. We note that your Data Availability Statement is currently as follows: [All relevant data are within the manuscript and its Supporting Information files]

Please confirm at this time whether or not your submission contains all raw data required to replicate the results of your study. Authors must share the “minimal data set” for their submission. PLOS defines the minimal data set to consist of the data required to replicate all study findings reported in the article, as well as related metadata and methods (https://journals.plos.org/plosone/s/data-availability#loc-minimal-data-set-definition).

For example, authors should submit the following data:

- The values behind the means, standard deviations and other measures reported;

- The values used to build graphs;

- The points extracted from images for analysis.

Authors do not need to submit their entire data set if only a portion of the data was used in the reported study.

If your submission does not contain these data, please either upload them as Supporting Information files or deposit them to a stable, public repository and provide us with the relevant URLs, DOIs, or accession numbers. For a list of recommended repositories, please see https://journals.plos.org/plosone/s/recommended-repositories.

If there are ethical or legal restrictions on sharing a de-identified data set, please explain them in detail (e.g., data contain potentially sensitive information, data are owned by a third-party organization, etc.) and who has imposed them (e.g., an ethics committee). Please also provide contact information for a data access committee, ethics committee, or other institutional body to which data requests may be sent. If data are owned by a third party, please indicate how others may request data access.

Answer: The original data have been supplied as separate files within the Supporting Information files.

Respond to Reviewer 1

Reviewer #1: The authors have systematically and rigorously analyzed the adverse effects (AE)caused by obinutuzumab using two large (FAERS and JADER) databases.

The paper provides an interesting compilation of the drug's main AE. Considering the increasingly widespread use of this drug, it will be useful for the reader.

To enhance the interest of the paper, I suggest the following points:

1.AE may have a greater or lesser incidence and severity depending on the pathology being treated. This last aspect (indications) is poorly developed in the manuscript. They are only briefly discussed in the section about baseline characteristics, and the 5 main indications (CLL, follicular lymphoma, B-cell lymphoma, etc.) are presented in Table 3. However, these 5 top indications include “prescriptions for unknown causes” and "Other." It would be helpful to show the most common indications within the group “Other”.

Answer: Thank you very much for your valuable comments. We have raised the number of indications to 20.

2.Among the indications for obinutuzumab, its use in rheumatologic and systemic diseases will become increasingly important, given its greater efficacy than rituximab (e.g., lupus nephritis). It would be interesting to compare the frequency, characteristics, and severity of AE in hematologic malignancies (CLL, follicular or B-cell lymphomas, etc.) with non-tumoral indications.

Answer: As depicted in Figures 4 and 5, we supplemented the disparities in AEs induced by obinutuzumab in tumor and non-tumor indications.

3. In relation to the two previous points, the interest of this paper would be enhanced by analyzing AE of a recently published large trial of obinutuzumab in lupus nephritis (REGENCY; NEJM 2025; 392: 1471-83), using the same methodology applied in this paper and comparing them with the AE observed in other pathologies.

Answer: As the method employed in this article is not applicable to the large trial (REGENCY; NEJM 2025; 392: 1471-83), in Section 4.7, we have supplemented the relevant content regarding the efficacy and safety of obinutuzumab in lupus nephritis.

Reviewer #2: The authors conduct a large-scale, real-world pharmacovigilance analysis of adverse events (AEs) associated with obinutuzumab by analyzing the FAERS and JADER databases. They apply multiple signal detection algorithms (ROR, PRR, BCPNN, EBGM) to identify risk signals that are not currently documented in the product label. The study addresses a relevant clinical issue, post-marketing surveillance of monoclonal antibody therapies, and provides real-world evidence. However, the current manuscript lacks critical depth in interpretation, reproducibility, and clarity of English language, which limits its impact.

Main comments:

In my opinion, the study demonstrates insufficient depth in the interpretation of the data:

The authors mainly report signal values without providing a clinical context for many of the findings.

A more in-depth discussion is needed on how these adverse events may arise from a mechanistic point of view and how they compare with similar monoclonal antibodies (rituximab).

I recommend including a meta-analysis or comparative safety analysis with the existing literature to strengthen the conclusions, which appear to be only comments or opinions without scientific rigor.

Answer: Thank you very much for your valuable comments. In the discussion section, we explored the mechanisms underlying various AEs induced by obinutuzumab. Moreover, in sections 4.2 and 4.3, a meta-analysis was cited to compare the efficacy and safety differences between obinutuzumab and rituximab.

Language and grammar require revision

The manuscript contains multiple grammatical and structural errors and variations that affect readability. A thorough review by a native English speaker is recommended.

Answer: We have revised the language and grammar throughout the manuscript.

Lack of methodological transparency

The search criteria and exact filters used for FAERS and JADER are not clearly described. Without this information, the analysis is not reproducible. I recommend including a flow chart showing the number of reports included/excluded.

Answer: We have added a flow chart (Fig 1).

Does not control for confounding or bias in spontaneous reports:

The study should better acknowledge and discuss the limitations of spontaneous reports, including under-reporting, duplicate reports, and lack of denominator data. Consider incorporating a refined risk signal strategy or validating signals with external databases.

Answer: In section 4.8, we conducted a more in-depth analysis of the limitations of spontaneous reporting and data statistics.

Clarify statistical methods:

Formulas and thresholds are included, but justification for the choice of methods is lacking. Statistical corrections are also missing.

Answer: We have provided the rationale for the selection of methods in section 2.2. The reported statistics of adverse events from the FAERS and JADER databases are not appropriate for statistical corrections.

Weak conclusions and no meaningful clinical recommendations: The current conclusion merely repeats the results. Provide clinical recommendations (follow-up needs, high-risk patient profiles) and discuss implications for prescribing.

Answer: We have incorporated clinical recommendations and deliberated on the implications for prescribing within the conclusion.

Consider moving the technical descriptions of the algorithms (i.e., BCPNN formulas) to the supplementary material to improve the flow of the manuscript.

Answer: We have moved the technical descriptions of the algorithms to the supplementary material.

Tables 4 and 5 are dense and difficult to interpret. Highlight their content more clearly.

Answer: We have made revisions and improvements to Tables 4 and 5 to enhance comprehensibility.

Abbreviations (NHL, ... see text) should be defined consistently the first time they are used.

Answer: These problems have been rectified.

There are several repeated references to “not registered in the specification”; clearly define what “specification” refers to.

Answer: We have revised the “specification” to “drug instruction”.

Attachments
Attachment
Submitted filename: Response to the academic editor and reviewers.docx
Decision Letter - Nestor Oliva Damaso, Editor

Safety assessment of obinutuzumab: Real-world adverse event analysis based on the FAERS and JADER databases from 2013 to 2025

PONE-D-25-32339R1

Dear Dr. Cao,

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,

Nestor Oliva Damaso

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Thank you so much for your valuable study and for submitting to PloS One.

In my opinion this is an important paper helpful for clinicians that its interest will even rise with new indications of Obi in for example nephrology.

Best.

Nestor

Reviewers' comments:

Formally Accepted
Acceptance Letter - Nestor Oliva Damaso, Editor

PONE-D-25-32339R1

PLOS ONE

Dear Dr. Cao,

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. Nestor Oliva Damaso

Academic Editor

PLOS ONE

Open letter on the publication of peer review reports

PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.

We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.

Learn more at ASAPbio .