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

605 is a legacy ICD-9-CM diagnosis code for redundant prepuce and phimosis. 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 5 ICD-10-CM candidates: N47.0, N47.1, N47.2, N47.5, and N47.8. While the code set was active, the Medicare Code Editor limited this diagnosis to male patients.

Code Identity

ICD-9-CM Code
605
Valid for Submission
No — Legacy Code
Code Describes
Redundant prepuce and phimosis
Short Description
Redun prepuce & phimosis
Parent Block
605 Redundant prepuce and phimosis
ICD-10-CM Replacement
5 candidates — see Crosswalk

Convert 605 to ICD-10-CM

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

ICD-10-CM
N47.0 Adherent prepuce, newborn
Approximate The match is approximate rather than exact.
ICD-10-CM
N47.1 Phimosis
Approximate The match is approximate rather than exact.
ICD-10-CM
N47.2 Paraphimosis
Approximate The match is approximate rather than exact.
ICD-10-CM
N47.5 Adhesions of prepuce and glans penis
Approximate The match is approximate rather than exact.
ICD-10-CM
N47.8 Other disorders of prepuce
Approximate The match is approximate rather than exact.

Medicare Code Edits

Medicare Code Editor checks that applied to 605 while ICD-9-CM was in use.

Diagnoses for males only
Medicare Code Editor detects inconsistencies between a patient’s sex and any diagnosis on the patient’s record, this code applies to MALES only.

Index of Diseases References

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

  • Accessory congenital
    • foreskin 605
    • prepuce 605
  • Adherent
    • prepuce 605
  • Adhesion s adhesive postinfectional postoperative
    • preputial prepuce 605
  • Concretion SEE ALSO Calculus
    • prepuce male 605
  • Constriction
    • prepuce congenital 605
  • Excess excessive excessively
    • foreskin 605
  • Hypertrophy hypertrophic
    • prepuce congenital 605
  • Paraphimosis congenital 605
  • Phimosis congenital 605
    • due to infection 605
  • Redundant redundancy
    • foreskin congenital 605
    • prepuce congenital 605
  • Spanish collar 605
  • Tight tightness
    • foreskin congenital 605

Information for Patients

Penis Disorders

Problems with the penis can cause pain and affect a man's sexual function and fertility. Penis disorders include:

Read the full article at MedlinePlus

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

Questions About 605

Is 605 (redundant prepuce and phimosis) 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 N47.0, N47.1, and N47.2.

What is the ICD-10 replacement for 605?

The General Equivalence Mappings list 5 ICD-10-CM candidates for this code: N47.0 (Adherent prepuce, newborn), N47.1 (Phimosis), N47.2 (Paraphimosis), N47.5 (Adhesions of prepuce and glans penis), and N47.8 (Other disorders of prepuce). Each match is approximate, so the right choice depends on what the documentation supports.

What did 605 mean?

In the final ICD-9-CM release, this code described redundant prepuce and phimosis. It sat in block 605 Redundant prepuce and phimosis under Diseases of the genitourinary system (580–629).

Who could 605 be reported for?

Male patients only. The Medicare Code Editor treated this diagnosis as a males-only code and flagged claims where the patient record listed a different sex as inconsistent.

Why does 605 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 N47.0, N47.1, N47.2, N47.5, and N47.8, so the General Equivalence Mappings list every candidate rather than forcing one. The correct target is the one the documentation supports.