0SH338Z
Insertion Lumbosacral Joint to No Qualifier with Spacer, Percutaneous Approach
Procedural Specifications
| Clinical Axis | Detail Definition |
|---|---|
| Section | 0 Medical and Surgical |
| Body System | S Lower Joints |
| Operation | H Insertion |
| Body Part | 3 Lumbosacral Joint |
| Approach | 3 Percutaneous |
| Device | 8 Spacer |
| Qualifier | Z No Qualifier |
Operation Definition
Putting in a nonbiological appliance that monitors, assists, performs, or prevents a physiological function but does not physically take the place of a body part
Procedure Overview
This family covers procedures that place a nonbiological device into a joint of the lower body - the lumbar, sacral, or coccygeal spine, hip, knee, ankle, or a joint of the foot - without removing or replacing any of the joint's own anatomy. The device stays behind to support, stabilize, or monitor the joint rather than to act as a substitute for bone or cartilage that has been taken out. Examples include interspinous process spacers placed between vertebrae to relieve nerve compression, internal fixation hardware such as screws or pins used to stabilize a joint after injury, and leads for neurostimulators placed near a joint to manage chronic pain.
Patients typically undergo these procedures for spinal stenosis, joint instability following trauma, or chronic pain that has not responded to conservative treatment. Because the device is added to existing anatomy rather than replacing it, recovery generally focuses on protecting the joint while it adapts to the new hardware.
Anatomy & Axis Detail
Lumbosacral Joint
The lumbosacral joint is the articulation where the fifth lumbar vertebra meets the sacrum, a transition point that bears substantial mechanical stress as the mobile lumbar spine gives way to the fixed pelvis. Insertion of a device at this junction, such as an interspinous process spacer or supplemental fixation hardware, is generally used to limit excessive motion, relieve nerve compression associated with spondylolisthesis, or reinforce an already-fused segment without performing a new fusion during that encounter. This joint's location near the cauda equina and exiting nerve roots makes accurate device placement important for avoiding neurologic injury. Documentation should distinguish an insertion procedure at the lumbosacral junction from a comparable procedure at a purely lumbar level above it.
Approach: Percutaneous
Percutaneous describes entry by needle or instrument puncture through the skin or mucous membrane to reach the site of the procedure, without cutting the tissue open or using a visualizing scope. It differs from Open in that the site itself is never exposed, and from Percutaneous Endoscopic in that no endoscope is used to see internal structures. Common examples include needle biopsies and injections.
Device: Spacer
In Medical and Surgical procedures, a Spacer is a temporary, non-articulating device left in a joint or space after a component is removed, most often an antibiotic-impregnated cement block placed during a staged joint revision to control infection while preserving space and alignment. It is not intended to move like a real joint. It differs from an Articulating Spacer, which is shaped to permit some motion during the interim period, and from a permanent Synthetic Substitute.
Coding & Documentation
A coder needs operative documentation confirming that a device was placed into the joint and left in place, with no accompanying excision or replacement of joint tissue - if tissue is also being replaced, Replacement rather than Insertion applies. The device type and specific joint (by vertebral level or named lower joint) must be documented to select the correct body part and device value. A frequent error is coding Insertion when a fixation device is actually part of a fusion procedure; if the hardware is placed to achieve fusion, the fusion root operation captures the device and Insertion should not be coded separately. Another common mistake is misidentifying the joint level, especially in multi-level spinal cases where each level may require its own code.