Surface Replacement of the Hip Can Result in Decreased Acetabular Bone Stock
Bibliographic record
Abstract
BACKGROUND: The recent interest in hip resurfacing arthroplasty is motivated by its potential advantages over THA. One advantage of hip resurfacing arthroplasty is that it conserves bone on the femoral side; however, it is unclear whether it does so on the acetabular side. QUESTIONS/PURPOSES: We determined whether the amount of acetabular reaming and acetabular bone removal required for hip resurfacing arthroplasty is equal to, less than, or greater than that for THA. PATIENTS AND METHODS: We prospectively evaluated the femoral neck size of 180 hips at the time of primary THA in an identical manner to when carrying out a hip resurfacing arthroplasty. Based on the femoral neck measurement, we determined the minimum cup size that would be used and reamer size required if the hip was undergoing a resurfacing. We compared this to the reamer size actually required to prepare the acetabulum for the THA cup. We calculated the difference between the predicted reaming size for resurfacing and the actual reaming size to determine the effect of resurfacing on acetabular bone stock. RESULTS: Overall, 71%, 57%, and 41% of THAs would have had extra acetabular bone removed to implant a hip resurfacing arthroplasty cup with a line-to-line (0-mm), 1-mm, or 2-mm press fit, respectively. CONCLUSIONS: When compared to THA, hip resurfacing arthroplasty commonly results in additional acetabular bone resection.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 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.003 | 0.001 |
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".