Review for 10.1186/s12876-020-01420-x (2020)

Reviewer’ s report
Title: Left-sided portal hypertension caused by peripancreatic lymph node tuberculosis
misdiagnosed as pancreatic cancer: a case report and literature review
Version: 0Date: 08 Jun 2020
Reviewer's report:
This is rather interesting case referring to rare but clinically significant condition of pancreatic
tuberculosis, in this particular patient provoking left-sided portal hypertension.Case is clinically relevant and points out an important message that pancreatic TB should be takenin consideration when assessing solid pancreatic lesions.However before publication several issues need to be addressed:1. This is a case of patient how was misdiagnosed with pancreatic cancer 7 years beforepresentation. It is unclear why patient was not assessed with EUS+FNA/FNB prior to surgery. IfEUS was planned but not conducted because of rapid clinical deterioration that urged patient to beoperated please add this information. State if EUS was not available at your institution.2. Please address more detailed in discussion paragraph the important role of EUS+FNA/FNB indifferential diagnosis of pancreatic mass lesions. Discuss if information obtained wit EUS couldaffect a treatment in this particular patient.3. Minor language polishing could be of use.
Are the methods appropriate and well described?
If not, please specify what is required in your comments to the authors.
Yes
Does the work include the necessary controls?
If not, please specify which controls are required in your comments to the authors.
Unable to assessAre the conclusions drawn adequately supported by the data shown?
If not, please explain in your comments to the authors.
YesAre you able to assess any statistics in the manuscript or would you recommend an
additional statistical review?If an additional statistical review is recommended, please specify what aspects require furtherassessment in your comments to the editors.
Not relevant to this manuscript
Quality of written English
Please indicate the quality of language in the manuscript:
Needs some language corrections before being publishedDeclaration of competing interests
Please complete a declaration of competing interests, considering the following questions:
1. Have you in the past five years received reimbursements, fees, funding, or salary from an
organisation that may in any way gain or lose financially from the publication of this
manuscript, either now or in the future?
2. Do you hold any stocks or shares in an organisation that may in any way gain or lose
financially from the publication of this manuscript, either now or in the future?
3. Do you hold or are you currently applying for any patents relating to the content of the
manuscript?
4. Have you received reimbursements, fees, funding, or salary from an organization that holds
or has applied for patents relating to the content of the manuscript?
5. Do you have any other financial competing interests?6. Do you have any non-financial competing interests in relation to this paper?
If you can answer no to all of the above, write 'I declare that I have no competing interests' below.
If your reply is yes to any, please give details below.
I declare that I have no competing interests
Reviewer Publication Consent. I agree for my report to be made available under an Open Access
Creative Commons CC-BY License (http://creativecommons.org/licenses/by/4.0) if this manu-script is accepted for publication. Any comments that I do not wish to be included in the publishedreport have been included as confidential comments to the editor, which will not be published.Ifyou are not happy for us to publish this report, please contact the editorial office before completingthe review.If you wish, you can include your name in your published report. Please note you mustdecide whether to include your name at the start of the process and confirm this decision wheneverprompted. If you change your decision later, we will not be able to publish your name.
I agree to the terms of the CC-BY 4.0 license; please do not publish my name with my report.
(default)