The Involvement of Pial Microvessels in Leukocyte Invasion after Mild Traumatic Brain Injury
Bibliographic record
Abstract
The pathophysiological mechanisms underlying mild traumatic brain injury (mTBI) are not well understood, but likely involve neuroinflammation. Here the controlled cortical impact model of mTBI in rats was used to test this hypothesis. Mild TBI caused a rapid (within 6 h post-mTBI) upregulation of synthesis of TNF-α and IL-1β in the cerebral cortex and hippocampus, followed by an increase in production of neutrophil (CXCL1-3) and monocyte (CCL2) chemoattractants. While astrocytes were not a significant source of CXC chemokines, they highly expressed CCL2. An increase in production of CXC chemokines coincided with the influx of neutrophils into the injured brain. At 6 h post-mTBI, we observed a robust influx of CCL2-expressing neutrophils across pial microvessels into the subarachnoid space (SAS) near the injury site. Mild TBI was not accompanied by any significant influx of neutrophils into the brain parenchyma until 24 h after injury. This was associated with an early induction of expression of intercellular adhesion molecule 1 on the endothelium of the ipsilateral pial, but not intraparenchymal, microvessels. At 6 h post-mTBI, we also observed a robust influx of neutrophils into the ipsilateral cistern of velum interpositum (CVI), a slit-shaped cerebrospinal fluid space located above the 3rd ventricle with highly vascularized pia mater. From SAS and CVI, neutrophils appeared to move along the perivascular spaces to enter the brain parenchyma. The monocyte influx was not observed until 24 h post-mTBI, and these inflammatory cells predominantly entered the ipsilateral SAS and CVI, with a limited invasion of brain parenchyma. These observations indicate that the endothelium of pial microvessels responds to injury differently than that of intraparenchymal microvessels, which may be associated with the lack of astrocytic ensheathment of cerebrovascular endothelium in pial microvessels. These findings also suggest that neuroinflammation represents the potential therapeutic target in mTBI.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".