Prognostic value of NT-proBNP in patients with severe COVID-19
This article has been Reviewed by the following groups
Listed in
- Evaluated articles (ScreenIT)
Abstract
Background
The outbreak of coronavirus disease 2019 (COVID-19) caused by severe acute respiratory syndrome coronavirus 2 (SARS-CoV-2) in China has been declared a public health emergency of international concern. The cardiac injury is a common condition among the hospitalized patients with COVID-19. However, whether N terminal pro B type natriuretic peptide (NT-proBNP) predicted outcome of severe COVID-19 patients was unknown.
Methods
The study initially enrolled 102 patients with severe COVID-19 from a continuous sample. After screening out the ineligible cases, 54 patients were analyzed in this study. The primary outcome was in-hospital death defined as the case fatality rate. Research information and following-up data were obtained from their medical records.
Results
The best cut-off value of NT-proBNP for predicting in-hospital death was 88.64 pg/mL with the sensitivity for 100% and the specificity for 66.67%. Patients with high NT-proBNP values (> 88.64 pg/mL) had a significantly increased risk of death during the days of following-up compared with those with low values (≤88.64 pg/mL). After adjustment for potential risk factors, NT-proBNP was independently correlated with in-hospital death.
Conclusion
NT-proBNP might be an independent risk factor for in-hospital death in patients with severe COVID-19.
Trial registration
ClinicalTrials, NCT04292964. Registered 03 March 2020,
Article activity feed
-
SciScore for 10.1101/2020.03.07.20031575: (What is this?)
Please note, not all rigor criteria are appropriate for all manuscripts.
Table 1: Rigor
Institutional Review Board Statement IRB: All procedures were followed the instructions of local ethic committee (approval NO. 20200701). Randomization not detected. Blinding not detected. Power Analysis not detected. Sex as a biological variable not detected. Table 2: Resources
Software and Algorithms Sentences Resources Statistical analyses were performed by SPSS 22.0 (SPSS, Chicago, IL, USA) and a two-sided P<0.05 was considered statistically significant. SPSSsuggested: (SPSS, RRID:SCR_002865)Results from OddPub: We did not detect open data. We also did not detect open code. Researchers are encouraged to share open data when possible (see Nature blog).
Results from LimitationRecognizer: An explicit section …SciScore for 10.1101/2020.03.07.20031575: (What is this?)
Please note, not all rigor criteria are appropriate for all manuscripts.
Table 1: Rigor
Institutional Review Board Statement IRB: All procedures were followed the instructions of local ethic committee (approval NO. 20200701). Randomization not detected. Blinding not detected. Power Analysis not detected. Sex as a biological variable not detected. Table 2: Resources
Software and Algorithms Sentences Resources Statistical analyses were performed by SPSS 22.0 (SPSS, Chicago, IL, USA) and a two-sided P<0.05 was considered statistically significant. SPSSsuggested: (SPSS, RRID:SCR_002865)Results from OddPub: We did not detect open data. We also did not detect open code. Researchers are encouraged to share open data when possible (see Nature blog).
Results from LimitationRecognizer: An explicit section about the limitations of the techniques employed in this study was not found. We encourage authors to address study limitations.Results from TrialIdentifier: We found the following clinical trial numbers in your paper:
Identifier Status Title NCT04292964 Completed Prognostic Factors of Patients With COVID-19 Results from Barzooka: We did not find any issues relating to the usage of bar graphs.
Results from JetFighter: We did not find any issues relating to colormaps.
Results from rtransparent:- Thank you for including a conflict of interest statement. Authors are encouraged to include this statement when submitting to a journal.
- Thank you for including a funding statement. Authors are encouraged to include this statement when submitting to a journal.
- No protocol registration statement was detected.
-
-