Does Replication of Native Acetabular Anatomy Satisfy Recommended Hip-Spine Targets for Cup Orientation?
Bibliographic record
Abstract
Background: The aim of this study was to assess whether replication of native acetabular anatomy would satisfy cup orientation targets using 3 commonly described hip-spine algorithms. Whether spinopelvic characteristics influence ability to achieve cup orientation targets when replicating native anatomy and the agreement between algorithm recommendations was tested. Methods: A prospective database was queried to identify patients with adverse (n = 70) spinopelvic characteristics. These were matched for age and sex with patients without adverse characteristics (n = 70). Spinopelvic characteristics were obtained from radiographs and computed tomography (CT) scans. CT scans were segmented to determine native acetabular anatomy, particularly anteversion. Three hip-spine planning algorithms were evaluated for each patient (Optimized Positioning System [OPS], Combined-Sagittal Index [CSI], Hip-Spine Classification). Differences between target orientations and native anatomy were determined. Agreement between algorithms was tested. Results: OPS plan had significantly reduced inclination compared with native (39° vs. 52°, p < 0.001). No significant difference between OPS and native anteversions was seen (18° vs. 18°, p = 0.1) for the adverse group. OPS-planned anteversion was greater than native (23° vs. 16°, p < 0.001) in the nonadverse group. Most native orientations met published CSI targets (90% nonadverse, 59% adverse). Most native acetabular orientations (61% adverse and 58% nonadverse) failed to meet Hip-Spine Classification targets. Overall, in 88% of cases, replication of native acetabular version and 40° of inclination satisfied at least one suggested target. Agreement of all 3 algorithms was 31%; greater agreement was seen between Hip-Spine Classification and OPS (64%). Conclusions: Native acetabular anteversion and radiographic inclination of 40° are reliable targets, satisfying at least one hip-spine algorithm and thus justifying such practice, when advanced hip-spine analysis is not performed. The discrepancy between suggested orientations by the various published techniques, despite their validated low dislocation rates, emphasizes that although achieving a target cup orientation is important, the nature of hip stability is multifactorial and merits a holistic approach.
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.007 | 0.039 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 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".