Application of a halo-femoral traction system, including subsequent removal, with threaded pins anchored into the femoral bones to apply skeletal traction — used primarily for correction of severe spinal deformities such as scoliosis.
Verified May 8, 2026 · 6 sources ↓
- Medicare
- $464.94
- Work RVU
- 5.6
- Global, days
- 90
- Region
- Spine
Documentation requirements
What must appear in the operative or office note to support the claim.
Source · Editorial brief grounded in 6 cited references ↓
- Diagnosis driving traction — specify the deformity type, Cobb angle if scoliosis, and why staged traction is indicated before definitive surgery
- Operative note identifying femoral pin insertion sites, number of pins placed, and confirmation that halo ring was secured to the cranium
- Documentation distinguishing femoral fixation from pelvic or cranial-only constructs to support 20663 vs. 20661/20662
- If removal is performed at a separate encounter by the same provider, note that removal is included in 20663 and is not separately billable
- For pediatric patients or thin-skull pathology, confirm whether 20664 (6+ cranial pins) is more appropriate and document skull characteristics accordingly
- Record of informed consent and any fluoroscopic or imaging guidance used during pin placement, noting guidance is not separately billable unless performed for an independently documented additional procedure
Applicable modifiers
Modifiers commonly billed with this code.
Source · AMA CPT modifier descriptors · CMS NCCI Policy Manual
What this code covers
Source · Editorial summary grounded in 6 cited references ↓
CPT 20663 covers placement of a halo-femoral traction construct in which a cranial halo ring is fixed to the skull and threaded pins are inserted near the ends of the femoral bones, creating a distraction force across the spine. The code bundles both application and removal into a single reportable unit — don't bill removal separately when the same provider does both. The 90-day global period classifies this as major surgery, so routine follow-up within that window is not separately billable.
The procedure is most commonly used as a staged pre-operative intervention for severe scoliosis or other spinal deformities where gradual correction is required before definitive fusion. Because it often bridges to a separate spinal surgery, understand global-period overlap rules: if the definitive fusion falls within the 90-day global of 20663, modifier 58 is required on the subsequent surgery to signal a staged procedure.
This code sits in the General Introduction or Removal Procedures on the Musculoskeletal System family (20660–20665). Know your neighbors: 20661 is cranial halo, 20662 is pelvic, 20664 is cranial with 6+ pins for thin skull osteology. Billing the wrong variant is a common clean-claim failure.
RVU & reimbursement
Component RVUs and Medicare national rate. Actual payment varies by GPCI locality.
Source · CMS Physician Fee Schedule, RVU26A · January 2026
Work RVU vs. total RVU
The work RVU (5.6) is the surgeon's own effort — the figure physician pay and productivity targets are built on. The total RVU (13.92) adds practice overhead and malpractice, and is what drives the Medicare payment below.
| Work RVU | 5.6 |
| Practice expense RVU | 7.11 |
| Malpractice RVU | 1.21 |
| Total RVU | 13.92 |
| Medicare national rate | $464.94 |
| Global period | 90 days |
Payment by site of service
Medicare pays different rates by setting. HOPD typically pays substantially more than ASC for the same procedure.
Source · CMS OPPS Addendum B·ASC HCPCS payment rates·2026
| Setting | Medicare rate (national) |
|---|---|
Office (PFS non-facility) Procedure performed in physician's office | $464.94 |
HOPD (APC 5113) Hospital outpatient department | $3,342.87 |
ASC (PI R2) Ambulatory surgical center (freestanding) | $1,644.87 |
Common denial reasons
The recurring reasons claims for CPT 20663 get rejected.
Source · Editorial brief grounded in CMS NCCI edits, AAOS coding appeals, and cited references ↓
- Wrong code selected — 20661 (cranial) or 20662 (pelvic) billed instead of 20663 (femoral) when operative note supports femoral pin placement
- Separate removal billed in addition to 20663 by the same provider — removal is bundled into this code
- Definitive spinal fusion billed without modifier 58 when it falls within the 90-day global period of 20663, triggering a global-period denial
- Medical necessity not established — payer requires documented failure or contraindication to less invasive correction methods before approving halo-femoral traction
- Place-of-service mismatch — facility vs. non-facility setting inconsistency between the claim and operative documentation
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 6 cited references ↓
01Is removal of the halo-femoral construct separately billable?
02What modifier do I use when definitive spinal fusion is performed during the 90-day global period of 20663?
03How do I choose between 20661, 20662, and 20663?
04When is 20664 correct instead of 20661 or 20663?
05Can fluoroscopic guidance during pin placement be billed separately?
06Does the 90-day global period affect billing for traction adjustments or follow-up pin care?
Sources & references
Editorial content was developed using the following public sources. Last verified May 8, 2026.
- 01CMS Physician Fee Schedule 2026
- 02fastrvu.comhttps://fastrvu.com/cpt/20663
- 03emedny.orghttps://www.emedny.org/providermanuals/physician/pdfs/physician%20procedure%20codes%20sect5.pdf
- 04cms.govhttps://www.cms.gov/files/document/04-chapter4-ncci-medicare-policy-manual-2025finalcleanpdf.pdf
- 05aapc.comhttps://www.aapc.com/codes/cpt-codes/20663
- 06billrazor.comhttps://billrazor.com/procedures/20663-application-halo-femoral
Mira Scribe
Mira's AI scribe captures the specific traction construct applied (halo-femoral vs. cranial or pelvic), the femoral pin insertion sites and count, the indication with deformity severity, and whether this procedure is staged before a planned definitive spinal surgery. That documentation prevents the two most common denials: wrong-code selection within the halo family and missing modifier 58 when the fusion claim follows within the 90-day global.
See how Mira captures CPT 20663 documentation