0SHK45Z
Insertion Tarsometatarsal Joint, Right to No Qualifier with External Fixation Device, Percutaneous Endoscopic Approach
Procedural Specifications
| Clinical Axis | Detail Definition |
|---|---|
| Section | 0 Medical and Surgical |
| Body System | S Lower Joints |
| Operation | H Insertion |
| Body Part | K Tarsometatarsal Joint, Right |
| Approach | 4 Percutaneous Endoscopic |
| Device | 5 External Fixation Device |
| 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
Tarsometatarsal Joint, Right
The tarsometatarsal joints, also known as the Lisfranc joint complex, connect the cuneiforms and cuboid to the bases of the metatarsals and are critical to maintaining the transverse arch of the foot. On the right side, insertion procedures commonly involve placing fixation devices, such as pins used temporarily to stabilize the joint after a Lisfranc injury, without permanently altering the joint surfaces. This joint complex is prone to subtle instability that can be easily missed on imaging, so any inserted device is typically documented alongside careful assessment of alignment. Because Lisfranc injuries are frequently unilateral, correctly specifying the right side supports accurate tracking of this often under-recognized injury.
Approach: Percutaneous Endoscopic
Percutaneous Endoscopic combines a puncture through skin or mucous membrane with insertion of an endoscope to visualize the procedure internally, as in laparoscopic cholecystectomy. It is distinguished from plain Percutaneous by the presence of scope-guided visualization, and from Via Natural or Artificial Opening Endoscopic by its route being a new puncture rather than an existing orifice or stoma.
Device: External Fixation Device
This is the general external fixation device value, used when pins or wires anchored in bone are connected to a stabilizing frame outside the body to hold a fracture or joint in position, without specifying a more particular frame configuration. It contrasts with the more specific External Fixation Device subtypes - Monoplanar, Ring, Hybrid, and Limb Lengthening - which describe the frame's geometry or added lengthening function.
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.