Peer Review History
| Original SubmissionJune 6, 2019 |
|---|
|
PONE-D-19-15827 Severe anaemia complicating HIV in Malawi; multiple co-existing aetiologies are associated with high mortality. PLOS ONE Dear mrs Huibers, 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. Among them, particular attention should be given on comparing patients who died early, later or survived, and also on comparing patients on ART or not. We would appreciate receiving your revised manuscript by Aug 31 2019 11:59PM. When you are 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. If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. To enhance the reproducibility of your results, we recommend that if applicable you deposit your laboratory protocols in protocols.io, where a protocol can be assigned its own identifier (DOI) such that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols Please include the following items when submitting your revised manuscript:
Please note while forming your response, if your article is accepted, you may have the opportunity to make the peer review history publicly available. The record will include editor decision letters (with reviews) and your responses to reviewer comments. If eligible, we will contact you to opt in or out. We look forward to receiving your revised manuscript. Kind regards, Kostas Pantopoulos, PhD Academic Editor PLOS ONE Journal Requirements: When submitting your revision, we need you to address these additional requirements. 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 http://www.journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and http://www.journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf 1. Please note that all PLOS journals ask authors to adhere to our policies for sharing of data and materials: https://journals.plos.org/plosone/s/data-availability. According to PLOS ONE’s Data Availability policy, we require that the minimal dataset underlying results reported in the submission must be made immediately and freely available at the time of publication. As such, please remove any instances of 'unpublished data' or 'data not shown' in your manuscript and replace these with either the relevant data (in the form of additional figures, tables or descriptive text, as appropriate), a citation to where the data can be found, or remove altogether any statements supported by data not presented in the manuscript. 2. We note that you have included the phrase “data not shown” in your manuscript. Unfortunately, this does not meet our data sharing requirements. PLOS does not permit references to inaccessible data. We require that authors provide all relevant data within the paper, Supporting Information files, or in an acceptable, public repository. Please add a citation to support this phrase or upload the data that corresponds with these findings to a stable repository (such as Figshare or Dryad) and provide and URLs, DOIs, or accession numbers that may be used to access these data. Or, if the data are not a core part of the research being presented in your study, we ask that you remove the phrase that refers to these data. [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: Partly Reviewer #2: Yes ********** 2. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes Reviewer #2: 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: No Reviewer #2: 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 Reviewer #2: 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: General comments: It is well established that anaemia and anaemia severity are associated with HIV disease stage and mortality. HIV-associated anaemia has many potential causes. In this manuscript, Huibers et al report the prevalence of diverse co-existing morbidities that can be linked to anaemia in a cohort of hospitalised HIV patients presenting with severe anaemia (Hb<7g/dL, N=199 – median 5.3g/dL), many of whom were immunosuppressed. They classified participants as having severe anaemia or very severe anaemia (Hb<5g/dL) and tested, using univariate and multivariate analyses, whether there were differences in risk of co-morbidities according to anaemia severity; they found some evidence of increased risk of CMV-EBV infection in the very severe anaemia group. The cohort had a high mortality rate, presumably reflecting a high prevalence of advanced HIV disease at hospital presentation. Mortality was associated with end-stage renal disease and (more weakly) with folate deficiency; anaemia severity was not associated with mortality risk (bearing in mind all participants had Hb<7g/dL according to enrolment criteria). Similar studies from the same location have previously been published (e.g. Lewis et al, Trans R Soc Trop Med Hyg. 2005) considering multiple-potential aetiologies of anaemia in hospitalised patients. The data in the present study are largely descriptive, focussing purely on HIV-infected patients; they are robust, although the inclusion criterion of Hb<7g/dL does limit evaluation to comparison of severe vs very severe anaemia (as opposed to e.g. no anaemia/mild anaemia). The discussion is long and could be made more concise. In places it seems to infer a causative relationship between anaemia and mortality, but the present analyses do not allow such inferences to be made; HIV pathogenesis is complex, and although anaemia may contribute to morbidity and mortality, the data show that there are many other co-morbidities that could also explain the mortality risk. This manuscript was submitted with a parallel manuscript evaluating markers of iron status in a subset of the above cohort of severely anaemic HIV-infected patients, to be evaluated concurrently. Specific points: 1. Data availability: the authors state that raw data will be available within the manuscript or supplementary information – it’s not clear whether this has been provided yet. It would be helpful to refer to this within the manuscript. 2. Introduction (paragraph 2): it would be useful to include brief consideration of how important anaemia is clinically in relation to other co-morbidities (i.e. how important is correction of anaemia per se). 3. Introduction: The authors should specifically mention inflammation as a potential cause of anaemia (this will likely be present during many of the infections, but may not be restricted to these). 4. Methods: the authors confirm whether blinding was used in bone marrow analyses. 5. Methods/Results/Discussion (line 83): iron deficiency – the parallel manuscript demonstrates that MCV is a poor index of iron status (bone marrow iron staining, considered gold standard). The authors should make this clear in the present study in the text / table footnotes (e.g. by referring to the second manuscript) – it is therefore unclear how useful this part of the analysis is. Could the authors incorporate bone marrow iron status into analysis, for the subset of patients for whom that information is available? 6. Results – Table 2: o % with severe anaemia (in title row) should be corrected. o In the table footer, the authors should clarify that analyses are comparing severe with very severe anaemia. o The methods section states that variables with P<0.1 in univariate are included in multivariate analysis: it appears that variables with P>0.1 are included – this should be clarified / corrected. o Renal function: normal – is it intentional that no statistics are included here? 7. Results: o do particular co-morbidities frequently occur together? o do any particular combinations associate with anaemia severity, haemoglobin concentration or mortality/mortality within first 60 days? 8. Results: Table 1 / Text: there is a discrepancy between the mortality reported in the text and in the Table. This should be corrected. 9. Results: Given the pattern of mortality (approx. 50% within 1 year, approx. 80% of whom died within 60 days): o The analysis could be refined to compare patients who died within 60 days vs those who died later and/or those who survived: was there a difference in anaemia group, haemoglobin concentration, or co-morbidities between these groups? 10. Results: Figure 3 – the position of the “zero” line should be aligned with 0. 11. Discussion: o In general the discussion can be made more concise, e.g. see repetition in lines 10-11 and 20-21. o Lines 14-15: this could be interpreted as anaemia being causal for mortality; it is part of a complex disease state. Figure 3 found no association of anaemia severity with mortality risk (noting that all individuals had at least severe anaemia). However, in concert with much previous literature, the data are consistent with a associations between severe anaemia and mortality in HIV infection given this mortality rate. Suggest revising to “a multi-causal critical condition associated with high mortality”. o Line 26-27: it is a little unclear whether the authors are implying that severe anaemia is itself a prime cause of mortality (that therefore should be addressed per se), or rather whether it is a clear marker of severe disease (line 30) that would likely be improved through addressing co-existing conditions associated with advanced HIV (infections etc). The literature cited regarding anaemia and mortality is correlative, so the latter interpretation is favoured in my view. o Line 34: add “and inflammation”? o Line 36: the lack of effect here could reflect all patients having Hb<7g/dL in the present study. o Line 39-41: the authors could cite relevant data on the impact of ART on anaemia during HIV infection. o Line 49 – refer to point on line 26-27. o Line 83-87: see comment above regarding iron deficiency definition and reference to the second manuscript; the prevalence of BM-ID in the subset of individuals assessed in the second manuscript was higher (48%) and could be cross-referenced here. Should Line 87 use ref 46, not 45? Reference 46 used BM iron rather than MCV as the definition. o Line 92-94: Caution should be employed in making this inference – these patients are still all severely anaemic with multiple co-morbidities, and a high proportion are still immunosuppressed. It is possible the discrepancies are more likely related to assessment of iron status. Formatting / Spelling: • Abstract: repetition of “of anaemia” in Methods paragraph. • Discussion: line 39: “therefore” • Discussion: line 91: “severe” • Discussion: line 92: “anaemia” not “anaemic" • Discussion: line 94: “conditions such as iron deficiency are….” Reviewer #2: i would like to thank the authors for submitting this article for submission. The article highlights the very important problem of severe anemia in HIV infected adults in Malawi and the multiple etiologies associated with this diagnosis. i believe this article contributes something new to the body of evidence already available for decision makers. I would like to recommend this article for publication but first I would like to authors to address a few concerns. Major comments in the methods section on page 10, the authors note that all HIV infected patients over 18 years old admitted to the general medical ward with severe anemia were approached and recruited for the study if they provided informed consent. How was the sample size (n=199) determined? this was not explained in the methods section. How did the authors come about the 15 initial etiological factors that were explored for possible associations with severe anemia in HIV infected adults? some of the factors listed such as malaria, zidovudine use, iron deficiency have long been associated with anemia but others such as EBV, CMV, vitamin B12 not so much. Could the authors expand on this further in the introduction, discussion? More than half of the study population was not on ART with low CD4 counts and high viral loads- thus this study population may not be generalizable to other adult HIV-infected populations in resource poor countries as the majority of the population were not on standard ART treatment and had a higher risk of mortality. the study would be more informative if the outcomes were looked at separately in patients on ART and those not on ART to determine if there was a significant difference in mortality, as well as in the associations with the different etiological factors. Minor comments: Figure 1: the title and explanation of the figure is in the manuscript but not on the figure itself. Similar comment for Figure 2, readers should be able to understand the figures by looking at them without having to refer to the manuscript for detailed explanation. in figure 3, what do the plotted numbers represent and how will the readers interpret them? are they median values with interquartile ranges or hazard ratios with 95% confidence intervals? this was explained in the manuscript but should also be clear from looking at the figure itself. ********** 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 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 to be viewed.] 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 us at figures@plos.org. Please note that Supporting Information files do not need this step. |
| Revision 1 |
|
PONE-D-19-15827R1 Severe anaemia complicating HIV in Malawi; multiple co-existing aetiologies are associated with high mortality. PLOS ONE Dear mrs Huibers, Thank you for submitting your manuscript to PLOS ONE. Both reviewers found that the revised manuscript is improved and has addressed most of their concerns. However, reviewer 1 raised a few remaining minor issues, which require attention. Therefore, we invite you to address them in a revised version of the manuscript. We would appreciate receiving your revised manuscript by Dec 07 2019 11:59PM. When you are 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. If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. To enhance the reproducibility of your results, we recommend that if applicable you deposit your laboratory protocols in protocols.io, where a protocol can be assigned its own identifier (DOI) such that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols Please include the following items when submitting your revised manuscript:
Please note while forming your response, if your article is accepted, you may have the opportunity to make the peer review history publicly available. The record will include editor decision letters (with reviews) and your responses to reviewer comments. If eligible, we will contact you to opt in or out. We look forward to receiving your revised manuscript. Kind regards, Kostas Pantopoulos, PhD Academic Editor PLOS ONE [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author 1. If the authors have adequately addressed your comments raised in a previous round of review and you feel that this manuscript is now acceptable for publication, you may indicate that here to bypass the “Comments to the Author” section, enter your conflict of interest statement in the “Confidential to Editor” section, and submit your "Accept" recommendation. Reviewer #1: (No Response) Reviewer #2: All comments have been addressed ********** 2. 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: Partly Reviewer #2: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes Reviewer #2: Yes ********** 4. 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: Yes ********** 5. 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 ********** 6. 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: Thank you to the authors for their engagement with the reviewer comments. They have made several changes and consequently the manuscript is improved. A few minor points remain. 1. There is a discrepancy between the median days to death reported in the abstract, versus that reported in Table 1 / line 283 – this should be corrected. 2. Point 2 from the previous review (“Introduction (paragraph 2): it would be useful to include brief consideration of how important anaemia is clinically in relation to other co-morbidities (i.e. how important is correction of anaemia per se)”). • The authors have added a sentence referring to reference 1 (Mocroft et al, 1999) stating “Anaemia treatment may even improve survival”. The data presented in the large Mocroft study do not address treatment of anaemia and indeed they conclude (final sentence) that “Further follow-up is needed to determine…. whether an increase in haemoglobin decreases the risk of death”. • This therefore does not seem an appropriate reference to support the claim – this should be revised or toned down, or appropriate support presented from other sources. 3. Iron deficiency based on MCV: • I accept that this is now clarified in the recent manuscript. However, I still feel that classifying these individuals as “iron deficient” when the test performance is so poor (AUC=0.54) could be misleading, even though this is the highest (least low) AUC among the markers tested. • In my opinion, it would therefore be more appropriate to classify explicitly as “low MCV (<83 fL)” or similar (rather than “iron deficiency”), indicating e.g. in the text that this definition is used elsewhere as an index of iron deficiency, but noting that it poorly identified bone marrow iron deficiency in this group (Huibers et al, 2019 – other manuscript). 4. General point: attention needs to be given to manuscript organisation and spelling/grammar in places – a check should be made. For example: • Remove repetition in discussion: see lines 399-402 and lines 411-414. • Table S1 / S2: remove repetition in the figure legends (text is duplicated). • Line 356: sever • Line 173 and elsewhere: ferritine – change to ferritin Reviewer #2: Authors have addressed all my concerns. Minor revisions of spelling and grammar recommended in discussion section: Discussion, line 326: ‘Anaemia in HIV-infected patients is descripted as an independent predictor’ should be corrected to ‘Anaemia in HIV-infected patients is an independent predictor’ Discussion, line 330: ‘reported an estimated one-year mortality of 30 - 55% in severe anaemic vs 3.7%’ should read ‘reported an estimated one-year mortality of 30 - 55% in severely anaemic vs 3.7%’ Discussion, line 344: ‘however our cohort consist with’ should read ‘however our cohort consisted of’ Discussion, line 356: ‘ the complex multifactorial ethology of the severe anaemia might be marker of sever HIV disease’ should read ‘ the complex multifactorial etiology of the severe anaemia might be a marker of severe HIV disease’ Discussion, line 357: 'At last the effect of medication as Zidovudine' should read ‘Lastly, the effects of medications such as Zidovudine’ Discussion, line 358: ‘ However possible due to the bias’ should read ‘however, possibly due to the bias’ Discussion, line 394 and 398- repetition of the statement ‘the prevalence of iron deficiency in our study is higher than…' Discussion, line 408: 'sever immune suppression' should read 'severe immune suppression’ Discussion, line 413: should read ‘peripheral blood markers such as MCV poorly reflect bone-marrow iron deficiency' ********** 7. 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 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 to be viewed.] 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 us at figures@plos.org. Please note that Supporting Information files do not need this step. |
| Revision 2 |
|
Severe anaemia complicating HIV in Malawi; multiple co-existing aetiologies are associated with high mortality PONE-D-19-15827R2 Dear Dr. Huibers, We are pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it complies with all outstanding technical requirements. Within one week, you will receive an e-mail containing information on the amendments required prior to publication. When all required modifications have been addressed, you will receive a formal acceptance letter and your manuscript will proceed to our production department and be scheduled for publication. Shortly after the formal acceptance letter is sent, an invoice for payment will follow. To ensure an efficient production and billing process, please log into Editorial Manager at https://www.editorialmanager.com/pone/, click the "Update My Information" link at the top of the page, and update your user information. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org. If your institution or institutions have a press office, please notify them about your upcoming paper to enable them to help maximize its impact. If they will be preparing press materials for this manuscript, you must inform our press team as soon as possible and 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. With kind regards, Kostas Pantopoulos, PhD Academic Editor PLOS ONE Additional Editor Comments (optional): Reviewers' comments: Reviewer's Responses to Questions Comments to the Author 1. If the authors have adequately addressed your comments raised in a previous round of review and you feel that this manuscript is now acceptable for publication, you may indicate that here to bypass the “Comments to the Author” section, enter your conflict of interest statement in the “Confidential to Editor” section, and submit your "Accept" recommendation. Reviewer #1: All comments have been addressed ********** 2. 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 ********** 3. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes ********** 4. 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 ********** 5. 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 ********** 6. 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: (No Response) ********** 7. 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 |
| Formally Accepted |
|
PONE-D-19-15827R2 Severe anaemia complicating HIV in Malawi; multiple co-existing aetiologies are associated with high mortality Dear Dr. Huibers: I am pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department. If your institution or institutions have a press office, please notify them about your upcoming paper at this point, to enable them to help maximize its impact. If they will be preparing press materials for this manuscript, 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. For any other questions or concerns, please email plosone@plos.org. Thank you for submitting your work to PLOS ONE. With kind regards, PLOS ONE Editorial Office Staff on behalf of Dr. Kostas Pantopoulos 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 .