OSCR

Longitudinal changes in coagulation-fibrinolysis in patients with traumatic brain injury within seven days after injury.

Overview

Authors: Xinlong Dong1,2, Nanyu Yao1, Limin Zhang3, Guanghui Zheng3, Yutong Zhao4, Weiming Liu1
  1. Department of Neurosurgery, Beijing Tiantan Hospital, Capital Medical University, Beijing, China
  2. Beijing Key Laboratory of Central Nervous System Injury, Beijing Neurosurgical Institute, Capital Medical University, Beijing, China
  3. Laboratory Diagnosis Center, Beijing Tiantan Hospital, Capital Medical University, Beijing, China
  4. Beijing Neurosurgical Institute, Capital Medical University, Beijing, China
Journal: iScience, volume 29, issue 6, article 115443
Dates: received 10 August 2025; accepted 19 March 2026; published online 24 March 2026
Type: Research article · Language: English
License: CC BY-NC-ND
Identifiers: DOI 10.1016/j.isci.2026.115443 · PMID 42109853 · PMCID PMC13156692 · OpenAlex W7140214651
Open access: gold, a free copy (OpenAlex)
Status: code verified (how the code is found and verified)
Categories: human (organism), traumatic brain injury (population), clinical / translational (subfield)
Methods: Statistics
Keywords: health sciences, medicine, medical specialty, cardiovascular medicine
Topic: Trauma, Hemostasis, Coagulopathy, Resuscitation (Critical Care and Intensive Care Medicine, Medicine), according to OpenAlex
Funding: National Natural Science Foundation of China (82201520); Capital’s Funds for Health Improvement and Research (2024-1-2042)
Citations: not cited yet (Europe PMC); 41 references in the paper
Research resources: RRID:AB_2034024, RRID:AB_2077978, PE anti-human CD42b Antibody RRID:AB_314386

Abstract

The abstract is not reproduced here: the paper's license (CC BY-NC-ND) does not allow it. Read it in the paper, at the publisher or on Europe PMC.

Code

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

datadryad.org/share/link_not_for_publication/sgsfugtaavnujuzck3x9dqoetem4rph0lzoav7grm0g

License: none: the authors keep all their rights
State: the link answers, verified on 30 September 2026
Evidence: the link answers
Software Heritage: not checked
Found in: “Data and code availability”
Not found: README, license file, CITATION.cff, environment file, tests, continuous integration, documentation
Availability: 1 check, the latest on 30 September 2026: the link answers (HTTP 200)
  • 30 September 2026: the link answers (HTTP 200)

The paper's code and data availability statement is in the Data section.

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.

Code and data availability statement

The paper has a code and data availability statement. Its license (CC BY-NC-ND) does not allow reproducing it here; in short, from what the harvester recognized in it:

Read it in the paper: doi.org/10.1016/j.isci.2026.115443.

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 1, 30 September 2026: the first record

Recorded: type, language, journal, volume, issue, pages, dates, 6 authors, 4 keywords, 2 funders, 41 references, 3 RRIDs.

Cite

This paper

Dong, X., Yao, N., Zhang, L., Zheng, G., Zhao, Y., & Liu, W. (2026). Longitudinal changes in coagulation-fibrinolysis in patients with traumatic brain injury within seven days after injury. iScience, 29(6), 115443. https://doi.org/10.1016/j.isci.2026.115443

BibTeX

@article{dong2026longitudinal,
author = {Dong, Xinlong and Yao, Nanyu and Zhang, Limin and Zheng, Guanghui and Zhao, Yutong and Liu, Weiming},
title = {{Longitudinal changes in coagulation-fibrinolysis in patients with traumatic brain injury within seven days after injury}},
journal = {iScience},
year = {2026},
month = mar,
volume = {29},
number = {6},
pages = {115443},
publisher = {Elsevier},
issn = {2589-0042},
doi = {10.1016/j.isci.2026.115443},
url = {https://doi.org/10.1016/j.isci.2026.115443},
pmid = {42109853},
pmcid = {PMC13156692}
}

RIS

TY - JOUR
AU - Dong, Xinlong
AU - Yao, Nanyu
AU - Zhang, Limin
AU - Zheng, Guanghui
AU - Zhao, Yutong
AU - Liu, Weiming
TI - Longitudinal changes in coagulation-fibrinolysis in patients with traumatic brain injury within seven days after injury
T2 - iScience
J2 - iScience
PY - 2026
DA - 2026/03/24
VL - 29
IS - 6
SP - 115443
SN - 2589-0042
PB - Elsevier
DO - 10.1016/j.isci.2026.115443
UR - https://doi.org/10.1016/j.isci.2026.115443
LA - en
ER -

CSL-JSON

{
"id": "10.1016/j.isci.2026.115443",
"type": "article-journal",
"title": "Longitudinal changes in coagulation-fibrinolysis in patients with traumatic brain injury within seven days after injury",
"container-title": "iScience",
"author": [
{
"family": "Dong",
"given": "Xinlong"
},
{
"family": "Yao",
"given": "Nanyu"
},
{
"family": "Zhang",
"given": "Limin"
},
{
"family": "Zheng",
"given": "Guanghui"
},
{
"family": "Zhao",
"given": "Yutong"
},
{
"family": "Liu",
"given": "Weiming"
}
],
"container-title-short": "iScience",
"volume": "29",
"issue": "6",
"page": "115443",
"DOI": "10.1016/j.isci.2026.115443",
"PMID": "42109853",
"PMCID": "PMC13156692",
"ISSN": "2589-0042",
"publisher": "Elsevier",
"URL": "https://doi.org/10.1016/j.isci.2026.115443",
"language": "en",
"issued": {
"date-parts": [
[
2026,
3,
24
]
]
}
}

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.3389/fneur.2024.1407107
Association between early coagulation disorders and the risk of severe acute kidney injury in traumatic brain injury patients: a retrospective cohort study using the MIMIC-IV database.
Journal: Frontiers in neurology
In common: traumatic brain injury, 4 references
[2] doi:10.1186/s12964-026-02871-7
Hematopoietic cell kinase regulates microglial/macrophage activation to drive neuroinflammation after traumatic brain injury.
Journal: Cell communication and signaling : CCS
In common: traumatic brain injury, 4 references
[3] doi:10.1177/2689288x261469553
Fibrin Degradation Products Regulate Endothelial Barrier Function in Traumatic Brain Injury via the Actin Cytoskeleton.
Journal: Neurotrauma reports
In common: traumatic brain injury, 3 references
[4] doi:10.3389/fneur.2022.839784 [code]
Radiomics Features on Computed Tomography Combined With Clinical-Radiological Factors Predicting Progressive Hemorrhage of Cerebral Contusion.
Journal: Frontiers in neurology
In common: traumatic brain injury, clinical / translational, 2 references
[5] doi:10.1016/j.xcrm.2025.102022 [code]
High-dimensional analysis of injured patients reveals distinct circulating proteomic profiles in plasma vs. whole blood resuscitation.
Journal: Cell reports. Medicine
In common: traumatic brain injury, clinical / translational, 2 references
[6] doi:10.3389/fimmu.2022.1095657
Integrated single-cell multiomics reveals novel immune candidate markers for post-traumatic coagulopathy.
Journal: Frontiers in immunology
In common: traumatic brain injury, 2 references
[7] doi:10.1038/s41746-023-00895-8 [code]
Mining the contribution of intensive care clinical course to outcome after traumatic brain injury.
Journal: NPJ digital medicine
In common: traumatic brain injury, clinical / translational, 2 references
[8] doi:10.1186/s13195-026-02086-5
Examining the additive risk of TBI and comorbid conditions on dementia in military veterans: a retrospective cohort study.
Journal: Alzheimer's research & therapy
In common: traumatic brain injury, clinical / translational, 2 references
[9] doi:10.1177/2689288x261446294
Proteomic Changes of Neurodegenerative and Inflammatory Plasma Biomarkers Following Traumatic Brain Injury.
Journal: Neurotrauma reports
In common: traumatic brain injury, clinical / translational, 2 references
[10] doi:10.1186/s40001-025-03540-0 [code]
The association between white blood cell-to-hemoglobin ratio and mortality risk in critical traumatic brain injury: insights from MIMIC-IV retrospective analysis.
Journal: European journal of medical research
In common: traumatic brain injury, clinical / translational, 2 references

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.1016/j.isci.2026.115443.svg)](https://openscicode.org/badge/doi/10.1016/j.isci.2026.115443)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.1016/j.isci.2026.115443.svg
   :target: https://openscicode.org/badge/doi/10.1016/j.isci.2026.115443
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1016/j.isci.2026.115443"><img src="https://openscicode.org/badge/doi/10.1016/j.isci.2026.115443.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.