Hip Resurfacing Femoral Neck Fracture Influenced by Valgus Placement
Bibliographic record
Abstract
Femoral neck fracture is the most common short-term concern after hip resurfacing arthroplasty. Currently, there is little basis to decide between neutral and valgus placement. We loaded 10 notched cadaveric femur pairs to failure; one side was implanted at 0 degrees relative to the femoral neck and the other at 10 degrees valgus. All 20 were dual-energy X-ray absorptiometry-scanned. Failure load correlated with bone mineral density. Valgus placement increased the fracture load by an average of 28% over neutral for specimens with normal bone mineral density but had no effect on fracture load in specimens with low bone mineral density. For specimens with normal bone mineral density (typical of patients undergoing resurfacing arthroplasty), neutral-valgus placement had a greater effect than bone mineral density, explaining 54% of the fracture load variance. Component placement greater than 10 degrees valgus is likely undesirable because this can lead to an increase in component size and a greater likelihood of notching. To reduce fracture risk, we recommend placing the femoral component in valgus and selecting patients with higher bone mineral density.
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.001 | 0.002 |
| 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.001 |
| 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.002 | 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".