ICD-10 code R17: Unspecified jaundice

ICD-10 code R17 is the billable ICD-10-CM diagnosis code for unspecified jaundice, valid for claim submission in FY2026 (effective October 1, 2025). Jaundice sits at the intersection of a sign, a symptom, and a lab finding. The yellowing of skin and sclera caused by elevated bilirubin does not always point to a single documented cause. That is precisely when R17 applies. Use this code only when the provider has documented jaundice without identifying an underlying cause. It also applies when the workup is still in progress and no definitive diagnosis has been recorded.

Found our content helpful?

Key takeaways

ICD-10 code R17 is the billable code for unspecified jaundice; it covers adults and patients where no causative diagnosis has been documented.

R17 carries an Excludes1 note for neonatal jaundice (P55, P57-P59), meaning these codes cannot be reported together on the same claim.

Using R17 when a definitive underlying diagnosis is documented is a compliance violation; query the provider before defaulting to unspecified.

Pabau’s EMR gives coders built-in ICD-10 lookup during the encounter, and claims management scrubs and tracks the claim through submission.

ICD-10 code R17: Definition and billable status

ICD-10 code R17 is a billable, specific diagnosis code in the ICD-10-CM classification system. It is valid for FY2026 submissions, with the 2026 edition becoming effective on October 1, 2025. The code is classified under Chapter R00-R99 (Symptoms, signs and abnormal clinical and laboratory findings, not elsewhere classified). It falls within the block R10-R19 (Symptoms and signs involving the digestive system and abdomen).

Verify current billable status against the CDC/NCHS ICD-10-CM web tool for each fiscal year update. Code validity is confirmed annually by CMS and the National Center for Health Statistics (NCHS).

Clinical description of unspecified jaundice

Unspecified jaundice is the visible yellowing of the skin, sclerae (whites of the eyes), and mucous membranes. It is caused by elevated levels of bilirubin in the blood. Bilirubin is a breakdown product of red blood cells. When the liver cannot process or excrete it efficiently, bilirubin accumulates and produces the characteristic yellow discoloration. Per the CMS ICD-10-CM coding guidelines, R17 applies specifically when no underlying etiology has been documented.

Common approximate synonyms recognized under R17 include yellowing of skin, icterus, and jaundice NOS (not otherwise specified). These all map to the same code when no causative diagnosis is present in the medical record.

Hyperbilirubinemia vs jaundice: Coding differences

Hyperbilirubinemia and jaundice are clinically related but coded differently in ICD-10-CM. Hyperbilirubinemia describes an elevated bilirubin lab value without necessarily presenting with the visible yellowing that defines jaundice. The ICD-10-CM tabular list contains separate codes for specific bilirubin disorders, such as E80.4 for Gilbert syndrome, which causes benign unconjugated hyperbilirubinemia. R17 covers the nonspecific jaundice sign instead.

The key distinction for coders: when the provider documents the specific underlying condition causing the elevated bilirubin or visible yellowing, use the etiology code. R17 applies only when that condition is not documented. It is reserved for the clinical situation where jaundice is documented as a finding without an identified cause.

ICD-10-CM code hierarchy and classification for R17

R17 sits within a logical hierarchy that helps coders understand its scope and limits. The parent chapter (R00-R99) captures symptoms, signs, and abnormal clinical and laboratory findings that do not have a more specific diagnosis code to classify them. This is a foundational coding principle: signs-and-symptoms codes apply only when no definitive diagnosis is available.

R17 has no subcategory codes (no R17.0, R17.1, etc.). It is a terminal, billable code on its own. The AAPC ICD-10-CM code lookup confirms there are no child codes beneath R17 in the current tabular list. This pattern holds across Chapter R codes generally: the code is specific to the symptom, not the cause.

Excludes notes for ICD-10 code R17

R17 carries an Excludes1 note, which is the strictest type of exclusion in ICD-10-CM. An Excludes1 note means the excluded codes and R17 cannot be reported together on the same claim encounter because they represent mutually exclusive conditions.

Neonatal jaundice ICD-10 codes (P55, P57-P59)

Neonatal jaundice codes (P55, P57-P59) are excluded from R17 via an Excludes1 note. P-chapter codes apply exclusively to perinatal conditions in newborns. The appropriate code comes from P55 (hemolytic disease of newborn), P57 (kernicterus), P58 (jaundice from excessive hemolysis), or P59 (jaundice from other or unspecified causes).

• P55 codes: hemolytic disease of newborn (ABO incompatibility, Rh incompatibility, other)
• P57 codes: kernicterus (bilirubin encephalopathy of the newborn)
• P58 codes: jaundice due to excessive hemolysis in newborns (bruising, polycythemia, swallowed blood)
• P59 codes: neonatal jaundice from other causes (breast milk jaundice, hepatocellular damage)

R17 should never appear on a neonatal claim. If a coder sees jaundice documented for a patient in the perinatal period, the P55, P57-P59 range always takes precedence.

Obstructive jaundice ICD-10 codes

Obstructive (post-hepatic) jaundice results from biliary tract obstruction, most commonly choledocholithiasis (bile duct stones) or biliary stricture. When the provider has documented the obstructive cause, the correct code shifts away from R17 to a more specific hepatobiliary code.

• K80.3x: calculus of bile duct with cholangitis (acute or chronic, by subcode)
• K80.4x: calculus of bile duct with cholecystitis
• K83.1: obstruction of bile duct (not elsewhere classified)

These codes require specificity documentation: the coder needs a clear provider statement identifying the obstructive etiology. Absent that, R17 remains the appropriate choice.

Related ICD-10 codes for jaundice and bilirubin disorders

Coding jaundice accurately often requires knowing which more specific code replaces R17 once a definitive diagnosis exists. The table below gives coders the most commonly referenced alternatives alongside R17 as a quick reference tool.

Documentation requirements for the jaundice billing code R17

Sound documentation is the foundation of defensible R17 usage. Because this is a signs-and-symptoms code, payers and auditors expect to see documentation that explains why a more specific code was not assigned. Strong medical billing compliance practices require coders to confirm all of the following before using R17.

• Provider statement of jaundice as the primary finding: the term “jaundice,” “icterus,” or “yellowing of skin/sclera” must appear in the provider’s documentation. It is not enough for the term to appear only in nursing notes or lab results.
• No documented etiology: the assessment, problem list, and discharge summary (where applicable) must not identify a causative diagnosis that has a more specific ICD-10-CM code.
• Outpatient coding rule compliance: ICD-10-CM Official Guidelines Section IV governs this. Signs and symptoms are coded for outpatient encounters when no definitive diagnosis has been established by the end of the visit.
• Inpatient coding rule compliance: for inpatient stays, Section III guidelines require coders to code to the highest degree of certainty. If a provider documents “jaundice, probable hepatitis,” the code would shift to the hepatitis code, not R17.
• Provider query when needed: lab findings or imaging may be consistent with a specific diagnosis the provider has not named. Query the provider before assigning R17 in that situation.

Proper documentation also supports audit readiness. The WHO ICD-10 browser provides additional context on the international classification of jaundice. Aligning clinical documentation with the code’s official descriptor is the simplest way to prevent retrospective denials.

When to use ICD-10 code R17 vs a more specific jaundice code

The decision to use R17 versus a specific etiology code hinges on one question: has the provider documented a definitive underlying diagnosis? The table below summarizes the decision logic that coders and compliance teams apply in practice.

The inpatient versus outpatient distinction is critical. Coders working on inpatient records who see “probable” or “likely” jaundice etiologies should code the probable condition, not R17. Outpatient coders follow the opposite rule: code what is confirmed at the time of the visit.

Billing and reimbursement considerations for the jaundice billing code R17

R17 is a payer-accepted, billable ICD-10-CM code, but reimbursement outcomes vary by payer, setting, and the accompanying CPT procedure codes. There is no single national fee schedule for a diagnosis code alone. Reimbursement depends on what services (CPT codes) are billed alongside R17 and the medical necessity shown in the clinical documentation.

Practices submitting claims with R17 should route them through a clearinghouse to validate the code against payer-specific edits before transmission. Pabau integrates with Claim.MD, its US clearinghouse partner, which supports thousands of payers with real-time eligibility verification and ERA/835 remittance processing. This integration catches code-level errors before claims leave the practice, which is especially useful for signs-and-symptoms codes like R17 that payers scrutinize for medical necessity.

Key billing considerations for R17 submissions:

• Medical necessity: payers expect the documentation to support why the provider could not assign a more specific diagnosis code. A note that simply says “jaundice” without clinical context is a denial risk.
• Principal vs. secondary diagnosis: R17 can serve as the principal diagnosis for an outpatient visit focused on evaluating jaundice. It can also serve as a secondary code when jaundice is an associated finding alongside a primary condition.
• Sequencing rules: when R17 is coded alongside a condition that caused the jaundice, follow the sequencing guidelines in the ICD-10-CM Official Guidelines. The underlying condition (if documented) codes first for most scenarios.
• Payer-specific policies: some payers may require additional documentation or query letters when signs-and-symptoms codes are used as the principal diagnosis on higher-acuity claims. Verify with individual payer policies before submission.

Understanding the broader context of medical billing workflows and revenue cycle management helps billing teams see where R17 fits in the claim lifecycle. That lifecycle runs from documentation through payment posting. A complete superbill process ensures all relevant CPT codes and diagnosis codes, including R17, are captured before submission.

Common coding errors with the jaundice ICD-10 code R17

R17 generates predictable denial patterns. Recognizing these errors before submission is more efficient than working through a denial queue after the fact. Good denial management strategies start at the coding step, not the appeals step.

• Using R17 when a definitive diagnosis is documented: the most common compliance error. If the provider documented “jaundice due to hepatitis C,” the correct code is B18.2, not R17. Using the symptom code instead of the etiology code is an upcoding/downcoding risk and an audit trigger.
• Ignoring the Excludes1 note for neonatal jaundice: billing R17 on a neonatal claim when a P55, P57-P59 code applies will generate an edit rejection. The payer’s claim editing system will flag this as a mutually exclusive code pair.
• Inpatient coding with outpatient logic: coding R17 on an inpatient claim when the discharge summary documents a probable or likely etiology violates inpatient coding guidelines. Inpatient rules require coding the stated probable condition as if confirmed.
• Missing a provider query when documentation is ambiguous: markedly elevated bilirubin, liver function abnormalities (transaminitis), or imaging consistent with biliary obstruction all warrant a query. Query the provider whenever the record lacks a documented etiology. Coders who skip the query and assign R17 risk inaccurate reporting.
• Failing to verify code validity for the current FY: ICD-10-CM codes are updated annually on October 1. Always confirm R17 validity against the current CMS tabular list before the new fiscal year.

How practice management software supports ICD-10 R17 coding accuracy

Coding accuracy for signs-and-symptoms codes like ICD-10 code R17 depends on two things: clean clinical documentation and a reliable code-lookup workflow. Pabau’s EMR gives coders built-in ICD-10 code search directly inside the encounter record. A coder can look up R17, confirm the excludes notes, and attach the code without leaving the patient’s chart.

Once the code is attached, Pabau’s claims management software takes over the submission side. It scrubs the claim against payer edits, submits it through the Claim.MD clearinghouse integration, and tracks its status until payment posts. Keeping documentation, coding, and claim tracking inside one system simplifies retrospective audits and supports medical necessity review.

For practices submitting US insurance claims, Pabau’s Claim.MD integration validates codes against payer edits in real time. Claims carrying R17 as the principal diagnosis on higher-acuity encounters are flagged before transmission. This gives billing staff the chance to review documentation or query the provider before the claim leaves the practice. Additional guidance on interpreting denial codes in billing pairs well with the R17 workflow for practices managing sign-and-symptom denials.

Take the guesswork out of ICD-10 coding

Pabau’s EMR puts ICD-10 code lookup right in the encounter. Its claims management software then scrubs and submits the claim, so billing teams catch errors before they reach the payer.

Book a demo

Conclusion

ICD-10 code R17 is the correct and billable code for unspecified jaundice when no underlying etiology has been documented. The code is straightforward in theory, but it generates consistent errors in practice. Three failure points show up most often: using R17 when a definitive diagnosis exists, and ignoring the neonatal Excludes1 note. A third is applying outpatient logic to inpatient records.

Practices that pair strong provider documentation habits with an integrated coding and claims workflow reduce the risk of R17-related denials substantially. Pabau’s EMR-based ICD-10 lookup and claims management software give billing teams the tools to code R17 correctly and get the claim paid the first time. Book a demo to see how Pabau supports accurate R17 coding and claims for your practice.

Continue your research

Need to understand how clearinghouse submissions work? Claim.MD clearinghouse guide explains how electronic claim routing and real-time eligibility verification reduce denial rates for diagnosis codes.

Handling insurance denials on symptom-coded claims? Electronic remittance advice covers how to read ERA files to identify denial reason codes and initiate the right corrective action.

Looking to strengthen your broader billing compliance posture? Clean claim submission checklist outlines the documentation and code-level requirements that reduce edits before claims reach the payer.

Frequently Asked Questions