Format

Send to:

Choose Destination
See comment in PubMed Commons below
Calcif Tissue Int. 1993 Mar;52(3):199-204.

Geometric variables from DXA of the radius predict forearm fracture load in vitro.

Author information

  • 1Department of Orthopaedic Surgery, Charles A. Dana Research Institute, Beth Israel Hospital, Boston, Massachusetts 02215.

Abstract

The purpose of this investigation was to determine the cross-sectional geometry of the radius in female and male cadaveric specimens using dual-energy X-ray absorptiometry (DXA), to measure the accuracy of this technique compared with a digitizing procedure, and to measure the correlation between these DXA-based geometric variables and the load required to produce a forearm fracture. Paired intact forearms were scanned at a distal site and at a site approximately 30% of the forearm length from the distal end. The cross-sectional area and the moments of inertia of two sections at 10 and 30% of the forearm length were computed from the X-ray attenuation data. One member of each pair was then sectioned at the 30% location, which is mostly cortical bone, and the section was traced on a digitizing pad. The other forearm was loaded to failure in a servohydraulic materials test system. The DXA-based area and moment of inertia at 30% correlated significantly with the digitized results (r2 = 0.93 for area; r2 = 0.95 for moment; P < 0.001). The conventional bone mineral density from DXA did not associate significantly with failure load, but the minimum moment of inertia and the cross-sectional area at 10% correlated in a strong and significant manner with the forearm fracture force (r2 = 0.67 for area; r2 = 0.66 for moment; P < 0.001). The determination of radial bone cross-sectional geometry, therefore, should have better discriminatory capabilities than bone mineral density in studies of bone fragility and fracture risk.

PMID:
8481832
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Loading ...
    Write to the Help Desk