Botulinum toxin (A)-induced bone loss is associated with increased blood velocity and reduced vascular bone porosity
Bibliographic record
Abstract
Disuse-induced bone loss is a common consequence of spaceflight and prolonged bed rest. Intraosseous blood vessel volume and number are decreased in rodents after sciatic nerve resection, and femoral and tibial perfusion and blood flow to the femoral shaft and marrow are reduced after hindlimb unloading. However, it is unclear if alterations in the flow of blood contribute to botulinum toxin (BTX)-induced bone loss. The objective of this study was to assess patterns of tibial bone loss and alterations in blood flow in murine hindlimbs following BTX injection. We hypothesize that flow of blood to the affected hindlimb will diminish along with bone mass and structure. Skeletally mature C57Bl/6J female were injected with BTX (n = 15) or vehicle (n = 14). Paralysis was confirmed using digit abduction, wire hang tests, and activity analysis. In vivo microCT and ex vivo synchrotron tomography were used to assess bone mass, microstructure, (re)modeling, as well as vascular and lacunar porosity. Blood flow in the hindlimbs and cardiac structure/function was monitored by echocardiography. After 3 wk, BTX-injected tibiae had 16% lower cortical thickness and 66% lower trabecular bone volume fraction compared to baseline. MicroCT-based timelapse morphometry showed bone loss was predominantly at endocortical surfaces. Bone loss in the contralateral limb was coincident with reduced rearing capability of BTX-injected mice compared to vehicle controls. Bony vascular canal thickness and surface area were reduced, but there was no change in lacunar properties due to BTX. In vivo ultrasound demonstrated increased velocity time integral for blood flow due to BTX injection in femoral and popliteal but not in saphenous arteries. Thus, BTX led to significant bone loss in hindlimbs, while increasing blood velocity in the femoral popliteal arteries and decreasing vascular porosity. The vascular response to BTX differs from what has been observed in other hindlimb unloading models.
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.000 |
| 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".