ISCD CCD common mistakes
ISCD CCD · Understand the traps and how to avoid them.
Reporting a T-score computed against the wrong reference population (e.g., using the young-adult female database for a man or for a child) instead of matching the reference database to the patient's sex, ethnicity, and age.
Candidates memorize the T-score threshold of -2.5 but gloss over the rule that the reference database must match the patient; manufacturer defaults or prior technologist settings are often accepted without verification.
What to do instead
Before interpreting, explicitly state which reference database was used and confirm it matches patient sex and ethnicity; for premenopausal women and men under 50 use Z-scores, not T-scores.
Applying the WHO T-score diagnostic thresholds to the wrong skeletal sites (e.g., diagnosing osteoporosis from a forearm, total hip T-score of -2.6 without confirming it is the correct region, or using the wrong region of interest).
Candidates conflate the diagnostic criteria with monitoring sites and forget that the WHO classification is validated for lumbar spine, total hip, femoral neck, and 33% radius (the ISCD-designated diagnostic sites), not for Ward's triangle or trochanter alone.
What to do instead
Memorize the ISCD-approved diagnostic sites and the rule that the lowest T-score among them determines diagnosis; exclude Ward's triangle, greater trochanter, and non-33% radius from diagnostic classification.
Misinterpreting least significant change (LSC) and precision data-claiming a follow-up change is real when it is within the LSC, or comparing scans done on different machines without cross-calibration.
Candidates treat any numeric difference between two DXA reports as a true change and do not recall that LSC is calculated at the 95% confidence level from in-vivo precision and is site- and technologist-specific.
What to do instead
State the LSC for each site and require the observed change to exceed it before calling it significant; require same-scanner, same-technologist precision assessment and cross-calibration when equipment changes.
Failing to recognize artifacts and invalid scan conditions (e.g., degenerative changes, vertebral compression fractures, scoliosis, aortic calcification, or metal hardware) that falsely elevate spine BMD, and reporting the spine value anyway.
Candidates focus on numeric values and do not systematically review the image or the scan validity criteria (e.g., vertebrae that are not evaluable must be excluded per ISCD rules).
What to do instead
Review each vertebral level for artifact and exclude non-evaluable vertebrae (requiring at least two evaluable levels for a spine result); when spine is invalid, rely on hip or radius and document the exclusion.
Confusing the indications for DXA versus other modalities-ordering or interpreting DXA where it is not indicated, or failing to recognize when vertebral fracture assessment (VFA) or trabecular bone score (TBS) is appropriate.
Candidates memorize that DXA measures areal BMD but do not internalize the distinct roles of VFA (fracture detection) and TBS (texture/microarchitecture) versus BMD, nor the ISCD indications for each.
What to do instead
Build a modality-indication table: DXA for areal BMD and diagnosis/monitoring; VFA for vertebral fracture assessment when height loss or glucocorticoid use; TBS as an adjunct that does not change BMD-based diagnosis.
Omitting required quality-control and calibration steps (phantom scanning, technologist precision assessment) and failing to verify that the scanner is calibrated and the technologist is certified.
Candidates study clinical interpretation but treat QC as administrative; they do not recall that ISCD requires a precision assessment and regular phantom QC as part of a valid DXA program.
What to do instead
Memorize the QC requirements: daily/weekly phantom scans per manufacturer, annual precision reassessment, and documentation that the interpreting physician and technologist meet ISCD certification requirements.
Reporting a T-score or Z-score without the required interpretive context-no statement of the reference database, no fracture risk assessment, no mention of secondary causes, and no clinical recommendations.
Candidates focus on getting the number right and neglect the reporting standards that ISCD expects in a complete DXA report (demographics, indication, technique, findings, impression, recommendations).
What to do instead
Use a checklist for every report: patient demographics and indication, scanner and software, sites measured, reference database, T- and Z-scores, fracture risk (e.g., FRAX where appropriate), secondary-cause workup, and recommendations.
Misapplying FRAX-using it in patients already on osteoporosis treatment, in those with prior hip or vertebral fracture, or ignoring that FRAX inputs (e.g., BMD at femoral neck only, secondary osteoporosis) must be entered correctly.
Candidates treat FRAX as a universal risk calculator and forget its validated population (untreated patients) and its limitation to femoral neck BMD and specific clinical risk factors.
What to do instead
Restrict FRAX to untreated patients without prior hip/vertebral fracture; use femoral neck BMD only; recognize that FRAX does not replace clinical judgment and does not apply to children or to monitoring.
Neglecting patient preparation and positioning errors that affect scan validity-failing to remove artifacts, incorrect positioning of the nondominant forearm, or scanning a patient with recent contrast or nuclear medicine studies.
Candidates underestimate how much positioning and preparation affect BMD and do not recall the specific contraindications (e.g., recent barium, contrast, or radionuclide studies) and positioning rules.
What to do instead
Memorize the preparation checklist: remove metal, verify no recent contrast or nuclear medicine, position per manufacturer protocol, scan the nondominant forearm at 33% radius, and document any deviations.
Failing to distinguish monitoring from diagnosis-using T-scores to follow treatment response, or comparing scans performed on different sites or with different software versions.
Candidates carry diagnostic thresholds into the monitoring context and do not recall that monitoring requires the same site, same scanner, and comparison against LSC rather than T-score thresholds.
What to do instead
For monitoring, compare absolute BMD at the same site and scanner against the LSC; do not use T-score change as a monitoring endpoint, and flag any software or hardware change as requiring cross-calibration.