OSCR

The effect of intracranial pressure monitoring on severe traumatic brain injury patients who undergo subdural hematoma evacuation.

Overview

Authors: Cade McGarvey1, Aditya Acharya1, Gang Ren1, Jason Schroeder2, Alastair Hoyt2
  1. University of Toledo College of Medicine and Life Sciences,3000 Arlington Ave., Toledo, OH 43614 USA
  2. Department of Neurosurgery, University of Toledo Medical Center,3000 Arlington Ave., Toledo, OH 43614 USA
Institutions: University of Toledo (United States); University of Toledo Medical Center (United States)
Journal: Neurosurgical review, volume 49, issue 1, article 419
Dates: received 21 January 2026; accepted 18 May 2026; published online 23 May 2026; in print 2026
Type: Research article · Language: English
License: CC BY
Identifiers: DOI 10.1007/s10143-026-04341-7 · PMID 42176125 · PMCID PMC13198487 · OpenAlex W7162194541
Open access: hybrid, a free copy (OpenAlex)
Status: code verified (how the code is found and verified)
Categories: human (organism), other condition (population), traumatic brain injury (population), clinical / translational (subfield)
Methods: Statistics
Keywords: Trauma, Intracranial pressure, Traumatic brain injury, Subdural hematoma, Monitor
MeSH: Brain Injuries, Traumatic*, Hematoma, Subdural*, Intracranial Pressure*, Adult, Aged, Female, Glasgow Coma Scale, Hospital Mortality, Humans, Length of Stay, Male, Middle Aged, Monitoring, Physiologic, Retrospective Studies (* major topic)
Topic: Traumatic Brain Injury and Neurovascular Disturbances (Clinical Neurology, Medicine), according to OpenAlex
Citations: not cited yet (Europe PMC); 23 references in the paper

Abstract

Intracranial pressure (ICP) monitoring is frequently employed for patients with severe traumatic brain injury. The effect of intracranial pressure monitoring on patient outcomes has been studied little, and results often fail to account for confounding variables. We sought to focus on the impact of ICP monitoring on patients with severe traumatic brain injury and subdural hematoma (SDH) that underwent surgical intervention. Using the National Trauma Data Bank, we identified patients between 2021 and 2024 who had SDH and a presenting Glasgow Coma Score (GCS) of 3–8 who underwent an SDH evacuation. Of the patients whose ICP monitoring status was known, we compared the in-hospital mortality rate and length of stay (LOS) of patients who had ICP monitoring and those who did not. 3932 patients met the inclusion criteria, with 1481 patients undergoing ICP monitoring and 2451 not undergoing ICP monitoring. After propensity score matching to control for confounding variables, 1271 patients from each cohort were selected for further analysis. In-hospital mortality rate of the patients with monitoring did not show a significant difference from the cohort without ICP monitoring, in either matched (41.6% vs. 41.9%, p = 0.9) or without matching scenario (40.2% vs. 42.6%, p = 0.15). However, patients with ICP monitoring showed a longer hospital stay compared to the cohort without ICP monitoring (median 19 days vs. 13 days, p < 0.001). While ICP monitoring is recommended in brain injury treatment guidelines, it did not show a significant impact on the in-hospital mortality rate of patients with SDH and GCS 3–8 who had undergone SDH evacuation. Patients with ICP monitoring had significantly longer LOS and a higher rate of complications, including ventilator-associated pneumonia, deep venous thrombosis, and acute respiratory distress syndrome. Additional study is needed to determine if ICP monitoring improves outcomes in various populations of traumatic brain injury patients. Clinical trial number: not applicable.

Supplementary Information: The online version contains supplementary material available at 10.1007/s10143-026-04341-7.

Reproduced under the paper's license (CC BY), from the paper cited above.

Code

No file of the authors' code could be read here: it is described below, and read at its source.

cran.r-project.org/web/packages

License: none: the authors keep all their rights
State: the link answers, verified on 29 October 2026
Evidence: the link answers
Software Heritage: not checked
Found in: the text, “Statistical analysis”
Not found: README, license file, CITATION.cff, environment file, tests, continuous integration, documentation
Availability: 2 checks, the latest on 29 October 2026: the link answers (HTTP 200)
  • 29 October 2026: the link answers (HTTP 200)
  • 28 September 2026: the link answers (HTTP 200)

Tracing map

Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.

What the map holds:

  • 1 repository of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
  • 0 scripts, each with its path and the digest of its content;
  • no match between paragraphs and code yet;
  • neither the text of the paper nor the code itself.

Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.

Data

No dataset and no data link were found in the paper.

Data availability

All data is available in the manuscript.

Reproduced under the paper's license (CC BY), from the paper cited above.

Versions

The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.

Version 2, 28 September 2026

  • Publisher: n/a → Springer Science+Business Media

Version 1, 28 September 2026: the first record

Recorded: type, language, journal, volume, issue, pages, dates, 5 authors, 5 keywords, 14 MeSH terms, 22 references.

Cite

This paper

McGarvey, C., Acharya, A., Ren, G., Schroeder, J., & Hoyt, A. (2026). The effect of intracranial pressure monitoring on severe traumatic brain injury patients who undergo subdural hematoma evacuation. Neurosurgical review, 49(1), 419. https://doi.org/10.1007/s10143-026-04341-7

BibTeX

@article{mcgarvey2026effect,
author = {McGarvey, Cade and Acharya, Aditya and Ren, Gang and Schroeder, Jason and Hoyt, Alastair},
title = {{The effect of intracranial pressure monitoring on severe traumatic brain injury patients who undergo subdural hematoma evacuation}},
journal = {Neurosurgical review},
year = {2026},
month = may,
volume = {49},
number = {1},
pages = {419},
publisher = {Springer Science+Business Media},
issn = {0344-5607},
doi = {10.1007/s10143-026-04341-7},
url = {https://doi.org/10.1007/s10143-026-04341-7},
pmid = {42176125},
pmcid = {PMC13198487}
}

RIS

TY - JOUR
AU - McGarvey, Cade
AU - Acharya, Aditya
AU - Ren, Gang
AU - Schroeder, Jason
AU - Hoyt, Alastair
TI - The effect of intracranial pressure monitoring on severe traumatic brain injury patients who undergo subdural hematoma evacuation
T2 - Neurosurgical review
J2 - Neurosurg Rev
PY - 2026
DA - 2026/05/23
VL - 49
IS - 1
SP - 419
SN - 0344-5607
PB - Springer Science+Business Media
DO - 10.1007/s10143-026-04341-7
UR - https://doi.org/10.1007/s10143-026-04341-7
LA - en
ER -

CSL-JSON

{
"id": "10.1007/s10143-026-04341-7",
"type": "article-journal",
"title": "The effect of intracranial pressure monitoring on severe traumatic brain injury patients who undergo subdural hematoma evacuation",
"container-title": "Neurosurgical review",
"author": [
{
"family": "McGarvey",
"given": "Cade"
},
{
"family": "Acharya",
"given": "Aditya"
},
{
"family": "Ren",
"given": "Gang"
},
{
"family": "Schroeder",
"given": "Jason"
},
{
"family": "Hoyt",
"given": "Alastair"
}
],
"container-title-short": "Neurosurg Rev",
"volume": "49",
"issue": "1",
"page": "419",
"DOI": "10.1007/s10143-026-04341-7",
"PMID": "42176125",
"PMCID": "PMC13198487",
"ISSN": "0344-5607",
"publisher": "Springer Science+Business Media",
"URL": "https://doi.org/10.1007/s10143-026-04341-7",
"language": "en",
"issued": {
"date-parts": [
[
2026,
5,
23
]
]
}
}

The tracing map gets a citation of its own once an author has validated it and it has a DOI.

Similar papers

The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.

[1] doi:10.1016/j.lana.2024.100915
Clinical profile of patients with acute traumatic brain injury undergoing cranial surgery in the United States: report from the 18-centre TRACK-TBI cohort study.
Journal: Lancet regional health. Americas
In common: traumatic brain injury, clinical / translational, 2 references
[2] doi:10.1117/1.jbo.30.s2.s23912 [code]
Diffuse optical tomography system for acute traumatic brain injury in the intensive care unit: a prospective study on healthy volunteers.
Journal: Journal of biomedical optics
In common: traumatic brain injury, clinical / translational, 1 reference
[3] doi:10.1111/cns.13854
Group-based trajectory modeling of intracranial pressure in patients with acute brain injury: Results from multi-center ICUs, 2008-2019.
Journal: CNS neuroscience & therapeutics
In common: traumatic brain injury, clinical / translational, 1 reference
[4] doi:10.3389/fneur.2026.1783194 [code]
Assessment of cerebral hemodynamics in patients with acute brain injury: a group-based multivariate trajectory approach.
Journal: Frontiers in neurology
In common: clinical / translational, 1 reference
[5] doi:10.1038/s41598-025-04793-9
Latent class growth analysis of dynamic PaCo&lt;sub&gt;2&lt;/sub&gt; patterns and clinical outcomes in acute brain injury.
Journal: Scientific reports
In common: clinical / translational, 1 reference
[6] doi:10.1038/s41746-024-01227-0
Derivation, external and clinical validation of a deep learning approach for detecting intracranial hypertension.
Journal: NPJ digital medicine
In common: clinical / translational, 1 reference

Contribute

The authors of this paper can claim it, correct its record and validate its tracing map, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to OSCR's own machine, which answers it; your account page follows them.

Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.

Add the badge to the code's README

OSCR: the badge of this paper

If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.

Markdown
<!-- oscr-badge:start -->
[![OSCR](https://openscicode.org/badge/doi/10.1007/s10143-026-04341-7.svg)](https://openscicode.org/badge/doi/10.1007/s10143-026-04341-7)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.1007/s10143-026-04341-7.svg
   :target: https://openscicode.org/badge/doi/10.1007/s10143-026-04341-7
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1007/s10143-026-04341-7"><img src="https://openscicode.org/badge/doi/10.1007/s10143-026-04341-7.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->

If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.

Request its removal

To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).

Discussion, reproductions, activity

Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.

Report a mismatch between the code and the paper · Report a code error (signed in)

Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.

Report a reproduction failure (signed in)

Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.