Peer Review History

Original SubmissionNovember 11, 2025
Decision Letter - Issa Atoum, Editor

-->PONE-D-25-60609-->-->FairCareNLP: An AI-Driven Patient Review Analyzer for Healthcare-->-->PLOS One

Dear Dr. Dharma,

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.

==============================

Although the manuscript is technically strong, several points should be addressed before it can be considered sufficiently robust for publication. First, the reliance on synthetic demographic attributes constrains ecological validity and reduces confidence in claims about real-world generalizability. Second, the theme extraction stage appears to depend on heuristic LLM prompting. Still, the manuscript does not yet include a structured evaluation of prompt sensitivity, output stability, or hallucination risk, which weakens the interpretability evidence. Third, the current manuscript does not provide adequate end-to-end validation to show how errors may propagate across stages, nor does it demonstrate system robustness under realistic operating conditions. To strengthen the submission, the authors should systematically address the reviewers’ concerns, including, at a minimum, a more transparent and substantive discussion of privacy-preserving design choices and their practical implications.

==============================

Please submit your revised manuscript by Jan 28 2026 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. 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 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 . 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,

Issa Atoum

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

2.Thank you for stating in your Funding Statement:

“This research was supported by the Vector Scholarship in Artificial Intelligence (Vector

Institute) to PM and the Institute for Pandemics (IFP) at the University of Toronto to ZSH. We also acknowledge funding from the Natural Sciences and Engineering Research Council of Canada (NSERC) through the Canada Research Chairs Program and Discovery Grant (RGPIN-2025-07037 to ZSH). The funders had no role in study design,

data collection and analysis, decision to publish, or preparation of the manuscript.”

Please provide an amended statement that declares *all* the funding or sources of support (whether external or internal to your organization) received during this study, as detailed online in our guide for authors at http://journals.plos.org/plosone/s/submit-now. Please also include the statement “There was no additional external funding received for this study.” in your updated Funding Statement.

Please include your amended Funding Statement within your cover letter. We will change the online submission form on your behalf.

3. Thank you for stating the following in the Acknowledgments Section of your manuscript:

“This research was supported by the Vector Scholarship in Artificial Intelligence (Vector Institute) to PM and the Institute for Pandemics (IFP) at the University of Toronto to ZSH. We also acknowledge funding from the Natural Sciences and Engineering Research Council of Canada (NSERC) through the Canada Research Chairs Program and Discovery Grant (RGPIN-2025-07037 to ZSH). The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.”

We note that you have provided funding information that is currently declared in your Funding Statement. However, funding information should not appear in the Acknowledgments section or other areas of your manuscript. We will only publish funding information present in the Funding Statement section of the online submission form.

Please remove any funding-related text from the manuscript and let us know how you would like to update your Funding Statement. Currently, your Funding Statement reads as follows:

“This research was supported by the Vector Scholarship in Artificial Intelligence (Vector

Institute) to PM and the Institute for Pandemics (IFP) at the University of Toronto to ZSH. We also acknowledge funding from the Natural Sciences and Engineering Research Council of Canada (NSERC) through the Canada Research Chairs Program and Discovery Grant (RGPIN-2025-07037 to ZSH). The funders had no role in study design,

data collection and analysis, decision to publish, or preparation of the manuscript.”

Please include your amended statements within your cover letter; we will change the online submission form on your behalf.

4.  Please include captions for your Supporting Information files at the end of your manuscript, and update any in-text citations to match accordingly. Please see our Supporting Information guidelines for more information: http://journals.plos.org/plosone/s/supporting-information.

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

Additional Editor Comments:

The manuscript should align with PLOS ONE expectations for methods and software by demonstrating practical utility through transparent validation and by ensuring availability, including code, model configurations, and documentation sufficient for independent reproduction. Given that the study is based on deidentified, routinely administered patient experience surveys obtained via freedom-of-information requests, the reporting should follow core STROBE principles for observational data, particularly around sample definition, missingness and labeling limitations, and bounds on inference. If the authors intend to frame the dataset as routinely collected health data in the RECORD sense, they should explicitly justify that choice and map the manuscript to relevant RECORD items without over-claiming compliance. In addition, because demographic attributes are synthetically assigned and used only to compute fairness metrics, the manuscript should clearly delimit what fairness conclusions are supported, and it should avoid causal or real-world equity claims that extend beyond the available evidence.

[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: N/A

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

**********

-->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: I thank the authors for this good paper that presents FairCareNLP, a comprehensive NLP pipeline for analyzing patient reviews with explicit attention to algorithmic fairness, integrating sentiment analysis, key theme extraction, clinical NER, and bias mitigation strategies within a unified framework. The work is ambitious in scope and well-motivated, particularly given the relevance of bias-aware NLP in healthcare settings. The use of multiple debiasing techniques (INLP, Hard Debiasing, adversarial training) and a broad set of evaluation metrics (including WEAT and Equalized Odds) strengthens the empirical analysis, and the authors are transparent about the observed trade-offs between fairness and predictive performance.

However, several methodological limitations weaken the strength of the conclusions. Most notably, demographic attributes are synthetically generated rather than observed , which raises concerns about the validity and ecological realism of the fairness evaluation; although the authors correctly state that these attributes are used only for assessment, the resulting fairness gains may not transfer to real-world settings with complex, correlated demographic signals. In addition, the key theme extraction relies on a large LLM (LLaMA) in a largely heuristic, prompt-based manner, yet issues such as output stability, hallucination, and sensitivity to prompt design are not systematically examined. Finally, while the pipeline is presented as an integrated system, most components are evaluated independently, leaving open questions about error propagation and end-to-end behavior in deployment scenarios. Overall, the paper represents a solid applied contribution and a useful case study on fairness-aware healthcare NLP, but it would benefit from stronger validation, deeper analysis of LLM reliability, and clearer justification of when such a complex multi-module architecture is preferable to simpler alternatives.

The manuscript would be substantially strengthened by addressing the above points.

Reviewer #2: The paper presents an useful attempt toward achieving a more equitable AI in healthcare by showing that bias mitigation techniques (particularly INLP) can improve fairness without substantially sacrificing accuracy, enabling more inclusive patient-centered care. Existing NLP models contain biases based skewing results and causing underrepresentation of certain patient groups, thus perpetuating existing healthcare disparities and compromises patient care. Authors provide sufficient evidence to substantiate the relevance of this issue. In order to mitigate the problem, they propose a comprehensive NLP pipeline that integrates multiple debiasing techniques (adversarial, Hard Debiasing, INLP) rather than using one in isolation, addresses bias at different stages (in-processing and post-processing), applies to multiple demographic attributes simultaneously, and uses propensity scoring to handle self-selection bias. They test their proposed approach using a dataset of anonymized patient reviews together with synthetic hospital-based demographic attributes.

The validation method demonstrates several notable strengths through its comprehensive and systematic approach. The study employs a large-scale real-world dataset of over 120,000 authentic, anonymized, patient reviews from 45 hospitals, providing substantial empirical grounding. The experimental design is rigorous, testing four different BERT models across multiple hyperparameter configurations (three learning rates, three debiasing techniques, varying loss weights), enabling systematic comparison of fairness-performance trade-offs. Critically, the evaluation framework is multi-dimensional, assessing both traditional performance metrics (accuracy, F1, precision, recall, AUC) and fairness metrics (Equalized Odds Difference, Word Embedding Association Test) across multiple protected attributes (gender, ethnicity, socioeconomic status). The study represents a novel integration of three complementary debiasing strategies applied at different pipeline stages, moving beyond prior work that examined single techniques in isolation. Additionally, the propensity scoring module systematically addresses self-selection bias in online reviews with quantitative validation, and the commitment to reproducibility through public data and code sharing strengthens the contribution.

The most critical weakness undermining the validation is the use of synthetically generated demographic attributes rather than actual patient demographics. These attributes were randomly assigned based on population distributions and (may) have no correlation with the actual review content or writing style, meaning the fairness metrics cannot truly validate whether the models exhibit equitable behavior with real demographic patterns. This fundamental limitation prevents verification of whether bias mitigation actually helps real patients or merely optimizes synthetic benchmarks. The study also lacks external validation—testing only Ontario hospitals with English-language reviews—raising questions about generalizability across regions, healthcare systems, and languages. No real-world deployment testing was conducted with healthcare stakeholders (clinicians or patients) to assess practical utility or actual impact on care quality. The validation suffers from incomplete expert labels (21% missing), limited computational exploration due to resource constraints, absence of statistical significance testing (no confidence intervals or p-values), and no cross-institutional or temporal holdout validation that might reveal overfitting to specific institutional patterns.

In considering whether the draft is ready or not for publication, several considerations need to be taken into account. The validation method is methodologically sound for assessing technical performance but fundamentally limited for validating fairness claims due to reliance on synthetic demographics. It successfully demonstrates that certain debiasing techniques (particularly INLP) can maintain model performance while improving fairness metrics on synthetic benchmarks, establishing technical feasibility. However, the disconnect between synthetic demographic labels and actual patient characteristics means the study cannot confirm whether these techniques would produce equitable outcomes for real diverse patient populations. The work represents an important incremental contribution showing how multiple debiasing strategies can be integrated into healthcare NLP pipelines, but it falls short of validating real-world equity impact. To definitely substantiate fairness claims, the research would need either more explicitly acknowledge the limitations, or alternatively, apply additional tests such as requiring validation on datasets with authentic demographic information (using privacy-preserving methods), cross-institutional testing, multilingual evaluation, and prospective studies involving healthcare stakeholders to assess whether the system genuinely supports more inclusive patient-centered care rather than merely optimizing synthetic fairness metrics.

The reviewer fully acknowledges that conducting the alternative tests would necessarily lead to a better substantiated, but also completely different paper. While the research performed is improvable, asking the authors to engage in the work required to better align with the reviewers' perspective before publication would prevent their unquestionable contribution to immediatly contribute to the discipline, providing a solid and rigorous model for other approaches, and allowing peers to continue this promising line of research. It is necessary to understand that Science is an incremental process made of partial steps. Authors provide a sufficiently solid partial step that others can clearly build upon. Therefore, as long as authors 1) enrich the discussion about privacy preservation, including references to the different approaches (see for example Dwork and colleagues at Harvard on Differential Privacy) and limitations of anonymization (see for example work of Sweeney and associates, also at Harvard), explaining why their chosen approach is the more appropriate one for this paper, and 2) more explicitly state the limitations derived from the use of synthetic demographics, 3) asking for the involvement in future work of social scientists trained in statistical causality (most notably Political Science) as this is the discipline better suited to patch the statistical and causality weaknesses of this paper, then the paper should be considered for publication, and even highlighted in the PONE website.

**********

-->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 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 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 ensure your figures meet our technical requirements, please review our figure guidelines: https://journals.plos.org/plosone/s/figures

You may also use PLOS’s free figure tool, NAAS, to help you prepare publication quality figures: https://journals.plos.org/plosone/s/figures#loc-tools-for-figure-preparation.

NAAS will assess whether your figures meet our technical requirements by comparing each figure against our figure specifications.

Revision 1

Please see attached pdf on respond to reviewers for the full response to the reviewer's questions.

Attachments
Attachment
Submitted filename: rebuttal-PONE.pdf
Decision Letter - Issa Atoum, Editor

-->PONE-D-25-60609R1-->-->FairCareNLP: An AI-Driven Patient Review Analyzer for Healthcare-->-->PLOS One

Dear Dr. Dharma,

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.

==============================-->-->Kindly consider the reviewer's comments on sensitive data and provide detailed responses and actions in the manuscript.-->-->==============================

Please submit your revised manuscript by Mar 20 2026 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.. 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 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 . 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,

Issa Atoum

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.

[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: All comments have been addressed

Reviewer #2: (No Response)

**********

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

Reviewer #2: Yes

**********

-->3. Has the statistical analysis been performed appropriately and rigorously? -->

Reviewer #1: Yes

Reviewer #2: No

**********

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

**********

-->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: 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: Thank you for the revised submission. All previously raised concerns have been carefully considered and successfully addressed in the current version of the manuscript.

Reviewer #2: In a prior review, authors have been suggested to appropriately address the sensitive nature of the data. However, in the re-submitted version, this issue remains unaddressed. Provided the sensitive nature of the involved data, and derived high risk, the draft in the current version cannot be considered ready for publication. Authors need to apply effective privacy-preserving techniques capable to ensure that no personal data is leaked. See my prior review with specific details on this issue.

**********

-->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 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 For information about this choice, including consent withdrawal, please see our Privacy Policy..-->

Reviewer #1: Yes: Benabderrahmane, Sid AhmedBenabderrahmane, Sid Ahmed

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 ensure your figures meet our technical requirements, please review our figure guidelines: https://journals.plos.org/plosone/s/figures

You may also use PLOS’s free figure tool, NAAS, to help you prepare publication quality figures: https://journals.plos.org/plosone/s/figures#loc-tools-for-figure-preparation.

NAAS will assess whether your figures meet our technical requirements by comparing each figure against our figure specifications.

Revision 2

We thank the reviewer for clarifying this comment and for the helpful emphasis on privacy protections for unstructured patient narratives. We agree that free-text patient narratives require strong privacy protection and that masking direct identifiers

(e.g., replacing names with ``XXXX\ldots'') does not, by itself, eliminate re-identification risk. In this revision,

we improved the manuscript to (i) explicitly acknowledge residual linkage risk in de-identified narratives,

(ii) clearly describe the layered privacy controls used in our study, and (iii) explain how formal differential

privacy mechanisms would be incorporated in a deployment-oriented next step.

Manuscript changes:

Rewrote Section 4.4 (Privacy Preservation and Synthetic Benchmarks).(Privacy Preservation and Synthetic Benchmarks).

We replaced the prior Section 4.4 with a new discussion including a mock example showing why residualwith a new discussion including a mock example showing why residual

re-identification risk can persist even after ``XXXX\ldots'' masking, and we detail our mitigations, including

provider de-risking via manual review, data minimization (e.g., coarse month/year only and no exact visit dates),

restricted-access processing, and screened reporting examples. We also clarify the role of synthetic demographics

as a fairness benchmarking tool that reduces the need to use true individual-level demographics.

Clarified LLM handling of narrative text (Sections 2.2.1 and 2.3).

Because narrative text is wrapped into the theme-extraction prompt, we explicitly state that LLaMA inference was

performed within our institutional environment and that record-level narrative text was not transmitted to

external LLM APIs. We also clarify that any LLM-assisted unit/type normalization did not involve narrative text.

Revised Data Availability.

We updated Data Availability to remove ambiguity about releasing record-level narratives. The public repository

contains code and non-identifying derived artifacts sufficient to reproduce reported results, while raw narrative

text is not redistributed due to residual re-identification risk inherent to unstructured text.

Formal privacy mechanisms as future deployment work (Section 4.4).).

We added a concise explanation of differential privacy (DP) and an illustrative example (i.e., DP release

of theme counts) to clarify how DP would be applied to derived releases in future deployments. This study does not claim a DP guarantee and suggests DP integration for deployment when releasing aggregates or model checkpoints.

Please find screenshots of the changes in the attached pdf

Attachments
Attachment
Submitted filename: 2026_Pourya_s_Paper__2_AI-rebuttal.pdf
Decision Letter - Issa Atoum, Editor

-->PONE-D-25-60609R2-->-->FairCareNLP: An AI-Driven Patient Review Analyzer for Healthcare-->-->PLOS One

Dear Dr. Dharma,

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.

==============================

The revised manuscript could not be sent for review because the comments from the previous round were not fully addressed. As per your request, the submission has been returned to you so that you may correct the issues identified earlier. Once all previous concerns have been fully resolved, the manuscript may be reconsidered for further evaluation.

==============================

Please submit your revised manuscript by Apr 11 2026 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.. 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 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 . 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,

Issa Atoum

Academic Editor

PLOS One

Journal Requirements:

1. 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.]

[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 ensure your figures meet our technical requirements, please review our figure guidelines: https://journals.plos.org/plosone/s/figures

You may also use PLOS’s free figure tool, NAAS, to help you prepare publication quality figures: https://journals.plos.org/plosone/s/figures#loc-tools-for-figure-preparation.

NAAS will assess whether your figures meet our technical requirements by comparing each figure against our figure specifications.

Revision 3

Response To Reviewer #2

Reviewer # 2-1: In a prior review, authors have been suggested to appropriately

address the sensitive nature of the data. However, in the re-submitted version, this

issue remains unaddressed. Provided the sensitive nature of the involved data, and

derived high risk, the draft in the current version cannot be considered ready for

publication. Authors need to apply effective privacy-preserving techniques capable

to ensure that no personal data is leaked. See my prior review with specific details

on this issue.

We thank the reviewer for clarifying this comment and for the helpful emphasis on privacy

protections for unstructured patient narratives. We agree that free-text patient narratives re-

quire strong privacy protection and that masking direct identifiers (e.g., replacing names with

“XXXX. . . ”) does not, by itself, eliminate re-identification risk. In this revision, we improved the

manuscript to (i) explicitly acknowledge residual linkage risk in de-identified narratives, (ii) clearly

describe the layered privacy controls used in our study, and (iii) explain how formal differential

privacy mechanisms would be incorporated in a deployment-oriented next step.

Manuscript changes: (1) Rewrote Section 4.4 (Privacy Preservation and Synthetic(Privacy Preservation and Synthetic

Benchmarks). We replaced the prior Section 4.4 with a new discussion including a mock examplewith a new discussion including a mock example

showing why residual re-identification risk can persist even after “XXXX. . . ” masking, and we detail

our mitigations, including provider de-risking via manual review, data minimization (e.g., coarse

month/year only and no exact visit dates), restricted-access processing, and screened reporting

examples. We also clarify the role of synthetic demographics as a fairness benchmarking tool that

reduces the need to use true individual-level demographics.

(2) Clarified LLM handling of narrative text (Sections 2.2.1 and 2.3). Because narra-

tive text is wrapped into the theme-extraction prompt, we explicitly state that LLaMA inference

was performed within our institutional environment and that record-level narrative text was not

transmitted to external LLM APIs. We also clarify that any LLM-assisted unit/type normalization

did not involve narrative text.

(3) Revised Data Availability. We updated Data Availability to remove ambiguity about

releasing record-level narratives. The public repository contains code and non-identifying derived

artifacts sufficient to reproduce reported results, while raw narrative text is not redistributed due

to residual re-identification risk inherent to unstructured text.

(4) Formal privacy mechanisms as future deployment work (). We added(). We added

a concise explanation of differential privacy (DP) and an illustrative example (i.e., DP release of

theme counts) to clarify how DP would be applied to derived releases in future deployments. This

study does not claim a DP guarantee and suggests DP integration for deployment when releasing

aggregates or model checkpoints.

Attachments
Attachment
Submitted filename: 2026_Pourya_s_Paper__2_AI-rebuttal_auresp_3.pdf
Decision Letter - Issa Atoum, Editor

FairCareNLP: An AI-Driven Patient Review Analyzer for Healthcare

PONE-D-25-60609R3

Dear Dr. Dharma,

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

Issa Atoum

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 #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 #2: Yes

**********

-->3. Has the statistical analysis been performed appropriately and rigorously? -->

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.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 #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 #2: 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 #2: Authors have explicitly addressed the identified issues regarding privacy. While re-identification risk have not been completely removed, authors have put in place necessary safeguards, including local LLM deployment. Authors have included notes about potential improvements, allowing the research community to build on their basis. Everything together, included acknoweledged limitations, this paper may be considered ready for publication.

**********

-->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 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 For information about this choice, including consent withdrawal, please see our Privacy Policy..-->

Reviewer #2: No

**********

Formally Accepted
Acceptance Letter - Issa Atoum, Editor

PONE-D-25-60609R3

PLOS One

Dear Dr. Dharma,

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. Issa Atoum

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 .