ICD-9-CM 932
CMS Source: final ICD-9-CM release (version date October 1, 2014). Retired from U.S. claims after September 30, 2015.FacebookXLinkedInPrint

932 is a legacy ICD-9-CM diagnosis code for foreign body in nose. It was valid on U.S. claims through September 30, 2015 and cannot be reported for services on or after October 1, 2015, when ICD-10-CM replaced the ICD-9 code set. Under the CMS General Equivalence Mappings, it maps to 2 ICD-10-CM candidates: T17.0XXA and T17.1XXA.

Code Identity

ICD-9-CM Code
932
Valid for Submission
No — Legacy Code
Code Describes
Foreign body in nose
Short Description
Foreign body in nose
Same as the full description in the CMS dataset.
Parent Block
932 Foreign body in nose
ICD-10-CM Replacement
2 candidates — see Crosswalk

Convert 932 to ICD-10-CM

Based on the final CMS General Equivalence Mappings (GEMs), 932 crosswalks to the following ICD-10-CM codes. When more than one candidate is listed, pick the code the documentation supports.

ICD-10-CM
T17.0XXA Foreign body in nasal sinus, initial encounter
Approximate The match is approximate rather than exact.
ICD-10-CM
T17.1XXA Foreign body in nostril, initial encounter
Approximate The match is approximate rather than exact.

Index of Diseases References

Entries in the final ICD-9-CM Index to Diseases and Injuries that point to 932. Tap the icons for the official index conventions.

  • Adenomyoma M8932 0 SEE ALSO Neoplasm by site benign
  • Asphyxia asphyxiation by 799.01
    • food or foreign body in larynx 933.1
      • nose nasal passages 932
    • mucus 933.1
      • nasal passages 932
  • Fibroma M8810 0 SEE ALSO Neoplasm conNEC tive tissue benign
  • Foreign body
    • entering through orifice current old
      • accessory sinus 932
      • antrum Highmore 932
      • frontal sinus 932
      • Highmore s antrum 932
      • maxillary sinus 932
      • nasal sinus 932
      • nose passage 932
      • nostril 932
      • sinus 932
        • accessory 932
        • frontal 932
        • maxillary 932
        • nasal 932
  • Hamartoma 759.6
    • epithelial gingival odontogenic central or peripheral M9321 0 213.1
  • Myxofibroma M8811 0 SEE ALSO Neoplasm conNEC tive tissue benign
  • Myxoma M8840 0 SEE ALSO Neoplasm conNEC tive tissue benign

Information for Patients

Foreign Bodies

If you've ever gotten a splinter or had sand in your eye, you've had experience with a foreign body. A foreign body is something that is stuck inside you but isn't supposed to be there. You may inhale or swallow a foreign body, or you may get one from an injury to almost any part of your body.

Read the full article at MedlinePlus

Nose Injuries and Disorders

Your nose is important to your health. It filters the air you breathe, removing dust, germs, and irritants. It warms and moistens the air to keep your lungs and tubes that lead to them from drying out. Your nose also contains the nerve cells that help your sense of smell.

Read the full article at MedlinePlus

Courtesy of MedlinePlus, a service of the U.S. National Library of Medicine.

Questions About 932

Is 932 (foreign body in nose) still a valid code?

No. This code belonged to ICD-9-CM, which the United States retired after September 30, 2015. Claims with dates of service on or after October 1, 2015 must use ICD-10-CM codes, such as T17.0XXA and T17.1XXA.

What is the ICD-10 replacement for 932?

The General Equivalence Mappings list 2 ICD-10-CM candidates for this code: T17.0XXA (Foreign body in nasal sinus, initial encounter) and T17.1XXA (Foreign body in nostril, initial encounter). Each match is approximate, so the right choice depends on what the documentation supports.

What did 932 mean?

In the final ICD-9-CM release, this code described foreign body in nose. It sat in block 932 Foreign body in nose under Injury and poisoning (800–999).

Why does 932 map to more than one ICD-10 code?

ICD-10-CM is more specific than ICD-9-CM. The detail packed into this single legacy code was split across T17.0XXA and T17.1XXA, so the General Equivalence Mappings list every candidate rather than forcing one. The correct target is the one the documentation supports.