ICD code K21.9 – GERD without esophagitis

Key takeaways

K21.9 covers diagnosed GERD with no endoscopic or histologic evidence of esophagitis, and it is a billable primary diagnosis code for FY2027.

When esophagitis is documented, the correct code is K21.00 (without bleeding) or K21.01 (with bleeding), not K21.9.

Do not report symptom code R12 (heartburn) alongside K21.9 once the clinical note establishes the GERD diagnosis.

Documentation must state the confirmed GERD diagnosis, the symptom pattern, and the treatment history, such as diet changes and a PPI trial.

Pabau’s claims management, part of the practice software we build, sends US claims through Claim.MD and tracks status, eligibility and remittances.

ICD-10 Code K21.9: Definition, descriptor, and code hierarchy

ICD-10 Code K21.9 is the billable ICD-10-CM diagnosis code for gastroesophageal reflux disease without esophagitis. The code is unchanged in CMS’s FY2027 ICD-10-CM files, which apply to encounters from October 1, 2026 through September 30, 2027. It sits in category K21 within Chapter 11, Diseases of the digestive system (K00-K95), and is valid for inpatient and outpatient claims.

The official descriptor turns on the qualifier “without esophagitis.” That phrase carries the whole coding decision. It means the record holds no endoscopic or histologic confirmation of esophageal mucosal damage. When in doubt, ask whether the physician’s note or scope report documents esophageal injury. If it does, K21.9 is the wrong code.

What K21.9 covers: Conditions and clinical scope

K21.9 applies when a physician has diagnosed GERD from the clinical presentation, symptom pattern, or response to empirical treatment. No endoscopic finding of esophageal mucosal damage is on file. The lower esophageal sphincter (LES) dysfunction behind reflux produces a wide range of symptoms that map correctly to this code.

Conditions and presentations that correctly use ICD-10 Code K21.9 include:

• Symptomatic GERD with heartburn and/or regurgitation, confirmed as GERD in the clinical note, with no scope performed or scope showing no mucosal damage
• Acid reflux disease documented by symptom diary and PPI response, without esophageal lesions
• GERD managed in primary care or gastroenterology with ongoing PPI or H2 blocker therapy, non-erosive form
• Laryngopharyngeal reflux (LPR) attributed to GERD without documented esophagitis
• GERD-related chronic cough or asthma exacerbation, where GERD is identified as the contributing diagnosis and no esophagitis is confirmed

Mucosal integrity is the clinical threshold. A patient can have severe symptoms, such as frequent heartburn, nocturnal regurgitation and chest discomfort, and still code to K21.9. That holds while any available scope shows intact mucosa, or when no scope was done and the note does not mention esophagitis.

What K21.9 does not cover: Excludes note and related code boundaries

Category K21 carries one Excludes1 note, for newborn esophageal reflux (P78.83). The other rows below are code-selection boundaries rather than Excludes notes. Each one still decides whether K21.9 is the right code for the encounter.

The R12 boundary matters most in daily coding. Under ICD-10-CM guidelines, sign and symptom codes are not assigned once the definitive diagnosis is established. When the note documents GERD as the diagnosis, R12 is not coded alongside it.

Billing R12 in place of K21.9 when the note clearly states GERD invites denials. Payers expect the established diagnosis code rather than the symptom.

K21.0 vs K21.9: Choosing the right GERD code

K21.9 is used when esophagitis is absent. When esophagitis is confirmed, the code moves to K21.00 or K21.01 under the non-billable parent K21.0. The decision turns on one finding. Does the clinical record contain endoscopic or histologic evidence of esophageal mucosal damage?

A frequent error is assigning K21.9 when the EGD report mentions “mild erythema” or “friable mucosa.” If the gastroenterologist reads those findings as esophagitis in the assessment, the code moves to K21.00. If the EGD impression says “normal mucosa” or “no esophagitis,” K21.9 is correct whatever symptom severity the patient described.

Key rule: Follow the physician’s documented diagnosis, not the symptom description. The coder translates the documented assessment and never infers a diagnosis from symptom lists. The decision path below runs the same checks in order, from diagnosis to bleeding.

Related codes to know when coding GERD

Several codes appear alongside or instead of K21.9, depending on what the clinical record documents. This reference prevents the two common mismatches: R12 when GERD is established, and K21.9 when esophagitis is confirmed.

Documentation requirements for medical necessity

A K21.9 claim stands on the physician’s clinical note. For clean claim submission, the note must demonstrate that GERD was an established diagnosis driving the encounter, not an incidental mention. CMS Local Coverage Determinations for anti-reflux procedures often include documentation checklists, and commercial payers typically require similar elements for medical necessity review.

The physician’s note must contain at minimum:

• Explicit GERD diagnosis: The assessment or impression section must state “GERD” or “gastroesophageal reflux disease” as a confirmed diagnosis, not merely a differential or rule-out
• Symptom pattern: Frequency, timing relative to meals and body position (recumbency triggers), and duration. For chronic GERD, payers may require a symptom history of eight weeks or more
• Absence of esophagitis: Either a scope report confirming no mucosal damage, or a clear note that no scope was performed. In that case the diagnosis rests on clinical presentation and treatment response
• Treatment history: Documentation of dietary modifications attempted and PPI or H2 blocker trial, including the medication, dose, and patient response
• Indication for the service billed: The CPT code on the claim must link logically to the documented K21.9 diagnosis (see CPT pairings below)

Coders reviewing notes for medical billing compliance should flag encounters where the note documents “acid reflux” in the HPI but the assessment only says “dyspepsia.” A mismatch between the history and the assessment is a common pre-authorization denial hook and an audit red flag.

Common CPT codes billed with ICD-10 Code K21.9

The table below lists the CPT codes most often paired with K21.9 in GI and primary care practice. Each pairing holds only when the note supports both the service and the GERD diagnosis.

Pairing 43239 with K21.9 when the EGD report documents esophagitis is a mismatch auditors look for. The diagnosis code must reflect the final post-procedure impression, not the pre-procedure working diagnosis.

Top reasons K21.9 claims are denied and how to fix them

K21.9 rejections fall into five categories, and each one surfaces as standard medical billing denial codes on the remittance. Each has a specific root cause and a fix that prevents a repeat.

Good denial management workflows catch most of these before submission. A pre-claim step that checks the EGD report against the diagnosis code removes the wrong-esophagitis-code category almost entirely.

Payer requirements and prior authorization for GERD billing

ICD-10 Code K21.9 as a standalone diagnosis code does not typically trigger prior authorization with Medicare, Medicaid, or most commercial payers. Prior authorization requirements in GERD billing attach to the procedure CPT codes, not to the diagnosis.

Procedures that commonly require prior authorization when billed alongside K21.9 include:

• Laparoscopic Nissen fundoplication (CPT 43280): Most commercial payers and Medicare Advantage plans require prior auth. Documentation must show failed conservative management, such as a PPI trial of at least 8 weeks and dietary modification
• LINX reflux management system placement: Prior auth required by virtually all payers; some payers exclude LINX coverage entirely under their technology assessment policies
• STRETTA procedure: Commercial payer coverage varies significantly; some plans consider it investigational. Confirm with the specific payer before scheduling
• Transoral incisionless fundoplication (TIF): Coverage and auth requirements differ by plan; check payer-specific medical policies annually as coverage has expanded in recent years

Medicare fee-for-service does not require prior authorization for most diagnostic procedures paired with K21.9, such as 43239 or 91035. Medicare Advantage plans run on individual plan rules, so verify each one separately.

Payer policies for GERD-related surgery change every year. Build a payer-specific prior auth matrix into the scheduling workflow rather than relying on last year’s experience.

How to code GERD correctly in your practice management system

Accurate GERD coding depends on a consistent workflow that ties the physician’s documentation to the submitted diagnosis before the claim leaves the practice. A clinical record that captures the assessment separately from the HPI reduces coder interpretation errors and leaves a clear audit trail.

Follow these steps for each GERD encounter:

1. Confirm the physician documented GERD explicitly. The assessment must say “GERD” or “gastroesophageal reflux disease,” not “acid reflux symptoms” or “probable GERD.” Coders cannot infer a confirmed diagnosis from symptom descriptions alone.
2. Check for esophagitis documentation. Review any EGD or biopsy reports linked to the encounter. If esophagitis is documented, escalate to K21.00 (without bleeding) or K21.01 (with bleeding). Do not assign K21.9.
3. Verify no Excludes1 conflict. Confirm the encounter does not involve newborn esophageal reflux (P78.83), which cannot be coded with K21.9.
4. Link K21.9 to the correct CPT code. The diagnosis must crosswalk to the procedure or E&M service billed. Run a crosswalk validation for any CPT outside the standard E&M range (99213-99215) before submission.
5. Submit with supporting documentation attached where required. For surgical procedures or payer medical necessity reviews, attach the clinical note, any EGD report, and the prior auth number. Pabau sends US claims through its Claim.MD clearinghouse integration and tracks status, eligibility and remittances.

How Pabau keeps GERD claims traceable from note to payment

Many K21.9 errors begin when the EGD report, the physician’s assessment and the claim live in separate systems. The coder then reconciles them by hand before every submission.

Pabau keeps the clinical note, an uploaded scope report and the invoice on the same patient record. Its claims management software sends US claims through Claim.MD as CMS-1500/837P submissions. It also tracks claim status, eligibility checks and electronic remittances.

The coder still chooses between K21.9 and K21.00, with the evidence for that choice on the same record. When a remittance comes back denied, the team sees the reason code against that patient and corrects the claim from there.

Keep every GERD claim traceable after submission

Pabau keeps the clinical note and scope report on one patient record, sends US claims through Claim.MD, and tracks status, eligibility and remittances. Your team can follow each K21.9 claim from note to payment.

Book a demo

Conclusion

GERD coding turns on one documented finding: whether the record shows esophagitis. Make the EGD impression the last check before K21.9 goes on a claim, and the most common correction becomes rare.

The trade-off is timing. Holding a claim for a pending scope report delays submission by days, but it saves a full rework cycle when the report shows esophagitis.

Book a demo to see how Pabau keeps the note, the scope report and the claim on one record for GI billing teams.

Continue your research

Need to understand how clearinghouse submission works for GI claims? Medical claims clearinghouse guide explains how EDI claims flow from the practice to payers. It also covers what happens when the clearinghouse rejects a claim.

Trying to reduce your overall denial rate across all diagnosis codes? Revenue cycle management guide covers the end-to-end billing workflow from eligibility check through final payment posting.

Looking for a reference on electronic remittance advice and 835 files? Electronic remittance advice explains how ERA files carry denial reason codes and how to action them in your billing workflow.

Frequently asked questions