Abdominal Pain ICD 10: R10 Codes, Documentation and Billing

ICD-10-CM code R10.9 is given to cases of abdominal pain when no specific location is provided. In such cases, if the exact location is known, a more descriptive code is assigned. For example, R10.31 is assigned for pain in the right lower quadrant, R10.13 is assigned for epigastric pain, R10.84 is assigned for generalized pain, and R10.85 is assigned for pain at multiple distinct sites.

Not having a cause does not mean one assigns an unspecified location code. It is appropriate to assign right lower quadrant pain if that is the case even if the cause is unknown.

This publication puts together the complete R10 code list, along with case examples, reporting rules, and examples to adjudicate issues related to claim denials. One can find quick answers to questions in the tables and locate thorough answers to questions related to tenderness, pregnancy, chronicity, outpatient and inpatient reporting in the detailed sections.

Abdominal pain ICD 10 quick-reference tables

The FY2027 files encompass 42 reportable codes in category R10. The tables below outline each code. Descriptions are truncated to provide easier readability; the last column explains the documented finding which justifies the assignment of the code. Category heading, for instance, R10.1 and R10.81, are not complete codes for submission.

Pain by abdominal region and distribution

Abdominal, flank and suprapubic tenderness

Rebound abdominal tenderness

Accuracy check: R10.818, R10.828, R10.322 and R10.84A are absent from the verified FY2027 R10 list. There are multiple reasons for this. One is code extension. This occurs when a known code is used as the basis for a new code. Another reason is that the R10.A3 means bilateral flank pain and R10.8A3 means suprapubic tenderness. They appear similar, but there are important differences.

Match the code set to the encounter date

There is some overlap between calendar years and ICD-10-CM fiscal years. FY2027 started on October 1, 2026, so an article updated in October 2026 should not describe FY2026 as the current release for new encounters. CMS and CDC publicly list the release periods for the code sets on their official code-file pages.

For outpatient services, use the date of service to determine the code set. For inpatient hospital services, use the release applicable to the discharge date. Sending a claim does not by itself dictate which code set should apply.

This is important when you deal with aged accounts receivable. A claim for a service done a long time ago should be reviewed to see if the code set at the time of the service allows for the use of the code for which the claim was updated. Updating an old claim with a code from a newer code set can create an error even if the new code better reflects the encounter being reported.

Changes introduced in FY2026 that still matter

The expansion in October 2025 improved the R10 category with additional details:

• Pelvic and perineal pain received codes R10.20 to R10.23 to differentiate laterality.
• R10.24 specified suprapubic pain.
• R10.A0 to R10.A3 specified flank pain laterality.
• R10.85 specified abdominal pain of multiple sites.
• R10.8A1 to R10.8A3 and R10.8A9 specified flank or suprapubic tenderness.

These options remain in the FY2027 files reviewed for this article. R10.2 remains a category heading, and it is not a complete, reportable code in that release. Select the appropriate child code, if any, instead of reporting R10.2.

Trade favorites with previous releases. A practice needs to be able to review previous claims for previous releases. This requires the ability to store prior versions in the system. Check subsequent addenda for the effective date of the change.

Start with the clinical record, then verify the code

Codes for abdominal pain are located in Chapter 18 of the ICD-10-CM/PCS. Chapter 18 covers Symptoms, signs and abnormal clinical and laboratory findings, not elsewhere classified. Codes in Chapter 18 are used to document symptoms and laboratory and other clinical findings for which no definitive condition or syndrome is subsequently coded.

ICD-10-CM is the United States modification of the World Health Organization’s (WHO) ICD-10. CDC’s National Center for Health Statistics (NCHS) is the main entity responsible for the U.S. diagnosis classification. CMS and NCHS publish the Official Guidelines for Coding and Reporting with the assisting organizations.

In your routine work, you will use the Alphabetic Index, the Tabular List and the applicable guidelines to code a case. The Index helps you to locate the code and the Tabular List confirms the descriptor, inclusion and exclusions and additional instructions.

Candidates for an ICD-10-CM diagnosis code for abdominal pain are found by answering the following five questions:

• What condition or symptom did the provider establish?
• Is the claim for outpatient care, professional service or hospital inpatient care?
• What is the location of the pain, is it localized, generalized or in multiple distinct sites?
• Does the record describe pain, tenderness, rebound or other reportable findings?
• Are there any special circumstances, exclusions or instructions that change your coding choice?

Consider the entire relevant record. Reconcile conflicting information through an appropriate query. A coder should not turn a suspected diagnosis into a confirmed diagnosis or diagnose what is missing in a case.

R10.9, R10.84 and R10.85 describe different situations

These codes differentiate documentation requirements. The difference relates to the documented spread of the pain, as opposed to the extent of the testing the patient received, or if the cause of the pain is known.

R10.9: The location or pattern remains unspecified

R10.9 is acceptable for abdominal pain when a specific location is not described in the available record. For example, the description may say the patient has abdominal discomfort without saying where in the abdomen the discomfort is located. The rest of the record may not address that uncertainty.

Selecting R10.9 is not automatically incorrect or unacceptable. The official guidelines say that symptom codes and unspecified codes can reflect the encounter accurately. Choosing less specificity to avoid using an unspecified code makes the claim less accurate.

Not knowing the cause and not knowing the location of the pain are separate issues. An episode of epigastric pain could be documented and supported with R10.13 even if the cause and the disease is unknown. It could be gastritis or reflux. The cause may be undetermined, but the location of the pain is documented. The investigation may be ongoing, but that is not the reason to choose R10.9.

The same logic applies to the symptom of pain. If the patient has abdominal pain but the evaluation does not identify any condition to account for the pain, then use a symptom code rather than a disease that is ruled out.

R10.84: The pain is generalized

R10.84 can be used for non-specific abdominal pain. Documentation should support broad distribution of pain within the abdomen. It is not necessary to document the patient has the same level of pain in all regions of the abdomen for the pain to be described as generalized. The clinical judgment of the provider along with the overall assessment and the patient’s description should be considered.

However, if the cause of the abdominal pain is unknown, generalized abdominal pain should not be assigned. For example, pain of unknown origin should not be assigned R10.84 if the only documentation is “abdominal pain, cause unknown.” In the same manner, the absence of specific documentation should not preclude assignment of the code for abdominal pain. For example, abdominal tenderness on examination does not support that the pain is localized if the patient reports pain in all regions of the abdomen.

In the example where a patient states “I have pain all over my abdomen,” and the clinical judgement supports this, assignment of the code for generalized or diffuse abdominal pain is supported. The entire case should be reviewed before assigning the final code including the symptoms, examination and the assessment of the clinician. For the Pain Management Billing Services, detailed description of the pain experienced should be documented to support the code selection, claim submitted and reimbursement.

R10.85: Distinct sites are documented

R10.85 is related to pain at various locations of the abdomen and is useful to specify the individual regions as indicated rather than requiring the coder to infer them from scattered statements. This is different from the clinician’s assessment where pain is described as a single generalized pattern.

Just because pain moves from one location to another, it doesn’t necessarily mean that the pain at both the locations was present at the same time. Migration, radiation and separate concurrent complaints are all different pain patterns. The final assessment should clarify the pattern.

There are specific exclusions provided for R10.85. Coders should not automatically group it along with localized R10.1 through R10.3 or R10.84 for the same pain presentation. The complete tabular instructions should be reviewed for any combination. More diagnosis lines do not necessarily imply the encounter was more complex.

Upper abdominal pain: choose the documented region

The upper abdomen includes a variety of areas. “Upper abdominal pain” and “epigastric pain” are not interchangeable terms, but epigastric pain is in the upper abdomen.

R10.10 for an unspecified upper location

R10.10 is used to represent upper abdominal pain when the location is not otherwise specified, but may lose information represented by R10.9. Use this code when the description supports this level of detail and seek clarification when conflicting information makes the choice uncertain.

An adequate billing system would allow the clinician to select R10.10 when the location is not established rather than choosing right or left. Selecting the correct unspecified location could be better than selecting the wrong precise location.

R10.11 for the right upper quadrant

R10.11 is used to represent right upper quadrant (RUQ) pain. This code cannot be used to represent gallbladder, liver or kidney disease. Nausea, meal related symptoms, and/or a planned ultrasound of the right upper quadrant may be documented; however, the presence of these symptoms does not dictate the diagnosis.

R10.11 may remain appropriate for an outpatient encounter that ends with RUQ pain and a diagnostic workup that is still pending. A diagnostic test should be handled in accordance with the rules and recommendations for the type of encounter in which the test is performed.

R10.12 for the left upper quadrant

R10.12 is used to represent pain in the left upper quadrant. The provider should use his/her best estimate for pain location based on the patient’s description rather than choosing a quadrant based on an assumption of the patient’s diagnosis or the location of the organ in question. Pain in the left upper abdomen may be confused with pain in the left lower abdomen or left flank and may require clarification based on the patient’s description.

Don’t use R10.12 for all pain on the left side of the body. The anatomical area in the record will determine if an abdominal, flank, chest, back or other code is more appropriate.

R10.13 is for epigastric pain

R10.13 describes pain in the upper central abdomen. It can describe burning or aching if the provider explains that location; sensation alone does not make the diagnosis.

The Tabular List defines R10.13 as dyspepsia and excludes functional dyspepsia (K30). It is important to use the provider’s exact wording. Not every time indigestion is mentioned should be considered functional dyspepsia. Likewise, don’t use K30 to report symptoms of dyspepsia.

Lower abdominal pain and pain around the navel

Lower abdominal codes describe a documented region. They should not be assigned to an undocumented condition based on symptoms, age, or sex. Nor should they be assigned based on the reason for an imaging order.

R10.30 for lower abdominal pain

R10.30 is appropriate for lower abdominal pain when the region is specified but the record does not support a more specific location. Before using this code, review the record to see if the clinician documented and coded pelvic, suprapubic, or umbilical pain, for which there are specific codes.

“Lower midline discomfort” does not always correlate to suprapubic pain. If there is uncertainty and the clinical description is vague, it is appropriate to request more clinical information rather than reinterpreting the description.

R10.31 and R10.32 for right and left lower quadrant

R10.31 is right lower quadrant pain and R10.32 is left lower quadrant pain. Because reversing these codes would change the documented location, check the final description before submitting a claim or saving the record as a favorite in the EHR.

Reporting rules take precedence over clinical judgment. Right-sided lower quadrant pain with appendicitis under consideration may be coded as a symptom-only outpatient encounter. The same applies to left-sided lower quadrant pain, if the cause is uncertain.

A coder should not be using a ‘cheat sheet’ that pairs abdominal quadrants with assumed or suspected diagnoses. This can lead the coder to assume an unproven diagnosis. The location should be coded correctly, and then, depending on the provider’s judgment, the status of the underlying condition should be captured as well.

R10.33 Periumbilical Pain

R10.33 describes pain located near the umbilicus (navel). Tenderness described in the official documentation may be documented as periumbilical (but not umbilical.)

R10.33 should not be confused with R10.83, which describes colic and bears an age restriction. Cramping near the umbilicus does not mean that the patient should be coded for colic simply because the symptom comes and goes.

Pelvic, perineal and suprapubic pain

The pelvic and perineal family has four laterality options: R10.20 when the side is unspecified, R10.21 (right), R10.22 (left) and R10.23 (bilateral). Choose the option that is supported by the record.

Pelvic and perineal pain, in the absence of laterality, is appropriately coded to R10.20. An unspecified side is different from an incomplete parent heading, R10.2.

Pelvic pain may be attributed to a number of causes, and it may originate from several anatomical structures and organ systems of the body. Pain is complex and frequently has referral patterns to other areas of the body. A complete evaluation is usually beyond the scope of the ICD-10-CM and, therefore, it must be coded to the highest level of specificity described by the documentation.

If the pain is suprapubic, the code would be R10.24. The pubic bone is in the inguinal region. Therefore, pain documented in this region may not be suprapubic. Likewise, pain in the genital region may not be suprapubic.

Pelvic pain has common features with pain in the abdomen and perineum. The rule out is for conditions that have an overlapping nature, and they may be documented as separate entities. If vulvar symptoms are present, R10.2 is an exclusion and a more specific condition should be assigned based on the evidence in the record.

There are special rules for coding conditions related to pregnancy. Code R10.2 (or any other code for a condition related to pregnancy) may not be sequenced until the reason for the current encounter is reviewed in relation to the pregnancy, and the pregnancy is defined based on its trimester. Codes for conditions related to pregnancy should not be sequenced with other non-pregnancy related conditions.

Flank pain and flank tenderness

Flank pain includes codes for laterality. Unspecified flank pain is coded to R10.A0. R10.A1 is coded for pain on the right, R10.A2 for pain on the left, and R10.A3 for pain on both sides. Terms for lateral abdominal and flank pain are included in this category.

A right flank pain diagnosis should not default to R10.9 simply because the old favorites list does not include a flank option in the EHR. Add the appropriate options to the list and allow the user to see the descriptions.

Right flank tenderness is represented by R10.8A1; left flank tenderness is by R10.8A2; and flank tenderness of an unspecified side is by R10.8A9. R10.8A3 indicates tenderness of suprapubic region. This is under the subcategory of flank tenderness.

Tenderness of the costovertebral angle is represented by complete codes of the R39.85 category and includes laterality. This should not be used to substitute every flank complaint. The anatomical finding the provider has actually documented should be used. Verify the full reportable code when the costovertebral angle is involved.

Flank tenderness and flank pain do not automatically denote the presence of a stone or infection or renal colic. If renal colic is diagnosed then the Excludes 1 note of the R10 category becomes applicable. Code only when the diagnosis is certain and in accordance with the classification instructions.

Tenderness and rebound need their own documentation

Phenomenon X describes a symptom. Phenomenon Y describes an examination response. Phenomenon Z describes a documented examination response whereby tenderness is released. While the two may occur together, the terms should not be used interchangeably for coding purposes.

Use the R10.81 family for abdominal tenderness, the R10.82 family for rebound tenderness and the R10.8A family for the specified flank or suprapubic findings. Each complete code in the tables represents the documented location.

Not observing rebound tenderness does not support a diagnosis. Likewise, an examination stating the abdomen is nontender does not negate the presence of pain. A patient may be experiencing pain and it may be documented, but that does not always mean tenderness will be elicited at the examination.

Use judgment to determine when to report additional symptom and sign codes. Pain and tenderness may both be documented in the same place, but it does not mean every finding should be reported as a diagnosis. Consider context, other diagnoses and instructions when reporting additional codes.

If an examination identifies focal tenderness when generalized pain is described in the history, it does not mean the pain should always be reclassified as localized pain. Seek additional information when an assessment leaves the relationship to be interpreted.

Acute abdomen, severe pain and colic

R10.0 does not apply to every emergent situation

R10.0 covers acute abdomen and includes severe generalized abdominal pain and rigidity. Abdominal rigidity NOS, generalized abdominal pain NOS and localized abdominal pain are excluded by the Tabular List.

R10.0 should not be assigned to all patients solely because the visit occurred in an emergency department, the pain was recent onset, or the pain was described as high. Review the documented diagnosis and supportive statements. If the documentation is unclear, a clarification should be documented. Building a diagnosis of acute abdomen with scattered criteria should be avoided.

The same approach should be applied to a diagnosis of acute appendicitis. There are no absolutes, and it is likely that in some of these cases the clinician has established the diagnosis of appendicitis. A code list should not be used in lieu of a diagnostic checklist.

Exclusion of age-related documentation for R10.83

R10.83 contains both Colic NOS and infantile colic. The current Tabular List excludes colic in adults and children above the age of 12 months and for these instances, it directs to R10.84. This instruction is often times missed on abbreviated online lists.

Therefore, in the case of an adult where intermittent cramps is reported, this is not an automatic indication to select R10.83. Colic can manifest at other age groups, and hence, one needs to review the patient’s age, the documented diagnosis and the Index.

Renal colic is a reported condition, and if documented as such, is to be coded to its most relevant classification, and not under R10.83.

Vomiting in children may be a sign of multiple conditions. When there is a documentation of infantile colic, often, one can see crying. Do not automatically assume this, and do not misinterpret a caregiver’s statement to mean a confirmed diagnosis unless validated by the provider.

A confirmed diagnosis changes the coding decision

When a provider establishes a cause, determine if the abdominal symptom is typically associated with that condition. As per the official guidelines, symptoms integral to a disease are generally not separately reported, unless instructed to do so in the classification.

For example, if abdominal pain that is associated with confirmed appendicitis does not warrant reporting of an additional R10 code. The claim should reflect the documented appendicitis at the appropriate level of specificity. Codes for appendicitis subtypes should not be assigned in the absence of relevant clinical information.

This principle is more broad and applies to any symptom that is integral to the disease and was given diagnostic and/or therapeutic attention. Additional reporting is dependent on the classification and the rules that apply to the setting, rather than whether medication was administered for the symptom.

Abdominal symptoms that are not typically associated with a condition established by the provider, and are clinically pertinent and reported, may warrant additional reporting. Read the entire assessment and determine if there are other abdominal symptoms for which the provider established a diagnosis and treated.

A practical way to validate this would be to compare the presenting complaint with the final assessment. An imported assessment may remain on the billing screen after the clinician has established a more definitive diagnosis. This should be reviewed. Consider other fields on the claim to be instructions to bill only if the field truly represents an instruction to bill.

Outpatient, emergency and inpatient rules differ

Office visits, emergency care and observation

Coders must report the diagnostic information that is supported by the greatest level of medical certainty. They should not code documentation of uncertain or suspected diagnoses. Uncertain or suspected diagnoses include conditions documented as “rule out,” “probable,” “suspected,” or any other similar terms.

This applies to all levels of medical care in the emergency department, but especially to cases in which the medical care was extensive, but the patient was not admitted. ED and observation services are outpatient services, and, therefore, the diagnosis coding should reflect the outpatient coding criteria.

Accurate Emergency Medical Billing Services assist the hospitals and health systems in capturing accurate documentation and minimizing coding and billing errors. For example, a physician may document right lower quadrant abdominal pain and suspect appendicitis, and document the diagnosis as such. However, if testing or other assessment does not confirm appendicitis, the documentation, coding, and billing should reflect abdominal pain, not appendicitis. Employing such procedures would help minimize risks associated with inaccurate coding, billing, and reporting.

Hospital inpatient discharge reporting

In the case of qualifying hospital inpatient stays, the exception to the uncertain diagnosis is different. A diagnosis that is documented as probable, suspected, or similar at discharge permits the code to be considered established, based on the inpatient rules.

This exception, however, applies to the inpatient setting and discharge documentation only. This should not encourage reporting all conditions that are part of an early differential diagnosis. It is important to understand the differences between the rules that apply to various settings and levels of care.

The primary diagnosis is chosen after studying the circumstances at admission and any applicable instructions. If an associated definitive condition is established, an undefined code for presenting abdominal pain does not replace that associated condition as the primary diagnosis.

There are exceptions for diagnostic services.

For outpatient diagnostic services, the presence of a confirmed final physician’s interpretation may impact the assignment of the code. The official guidelines of outpatient diagnostic services address this situation and the coder has to follow the guidelines instead of either disregarding the final interpretation or interpreting the test results on his/her own.

It is often helpful to label each work queue by setting to be able to have different rules applicable to different settings. Having separate accounts for the office, ED, observation, professional, and inpatient services helps avoid the situation where a rule that is applicable and should be followed for one service gets carried over and followed for the other service.

Excludes1 and Excludes2 notes that affect R10 coding

Exclusion notes show the relationships between classifications. Read them at the code, subcategory and category levels because an instruction higher in the hierarchy may apply to a selected child code.

Excludes1 generally prevents reporting the excluded condition together

At category R10, an Excludes1 note for renal colic states N23. If renal colic accounts for the same pain presentation, you should not add an R10 code to reiterate its location.

R10.0 excludes abdominal rigidity, NOS, and generalized abdominal pain, NOS, and the specified localized abdominal pain, categories. R10.84 excludes generalized pain associated with the acute abdomen. These exclusions help to avoid reporting the same presentation in an inconsistent and overlapping way.

R10.85 excludes abdominal rigidity, NOS, generalized pain associated with the acute abdomen, and generalized abdominal pain, NOS and localized abdominal pain in categories R10.1 to R10.3. It is not appropriate to combine a multiple-site code with all of its component location codes in order to describe a single episode in the routine case.

There is an official exception when the excluded conditions are totally unrelated. This exception is valid only when a distinguished relationship can be documented. If the relationship is not clear, query the documenter. This exception can not be used as a blanket reason to bypass an exclusion edit.

Excludes2 permits both conditions to be reported

At category R10, Excludes2 notes describe costovertebral angle tenderness, and some dorsalgia conditions and conditions related to flatulence. An Excludes2 note means the excluded condition is outside of the scope of the code description and may be reported with that code when both are present.

“Permission to report both” should not be read as an instruction to report everything. The record must show the existence of a condition. Only then should the reporting of that condition be allowed if it is also appropriate based on the reporting criteria. An Excludes2 note does not create a reason to add a condition if it is not already shown to exist.

Check notes outside of R10 as well

R52 unspecified pain excludes abdominal pain. Do not add R52 to abdominal pain to show that abdominal pain is of a high severity. Review the more specific pain classification and/or G89 guidance.

An exclusion conflicts and payer response are two separate questions. A coding error may be caught by a local edit, a clearinghouse or later review, but there is no basis to say every excluded combination will trigger an immediate rejection by every payer.

Chronic, recurrent and postoperative abdominal pain

R10 Codes for Abdominal Pain

There is no individual R10 code for “chronic abdominal pain.” Where the pain is located remains important, and a G89 code may provide supplementary information if the documented condition and reporting regulations so support.

The official guidelines do not specify a particular number of days after which the coders are to assign pain as chronic on their own. Therefore, if a provider documents abdominal pain as chronic, the coders are to rely on the provider’s documentation. There are other factors to consider that can provide context, but are not to be considered a substitute for the diagnosis.

G89 is used to denote the presence of chronic pain. If the focus of the visit is for the management or control of pain, then the G89 code may be first-listed and paired with the appropriate site code. If the focus of the visit is not for pain management or control, then the site-specific code may be first-listed and paired with the G89 code.

If the purpose of the visit is to address pain that is associated with a known condition, then the coders are to refer to the specific guidelines of that condition. G89.29 should not be added to every chronic condition, Pain associated with a known condition is to be captured under that condition.

Chronic pain syndrome is a separate diagnosis

G89.4 is the only IC-10-CM code for chronic pain syndrome; however, simply documenting pain in a general manner or using adjectives to describe pain, such as severe, high-level, intractable or difficult to manage pain, will not justify assigning this code. Chronic pain syndrome must be specifically documented in order to assign this code.

Regarding a patient documented to have intractable abdominal pain, if abdominal pain is coded as “intractable,” it is referencing the level of difficulty in managing the pain. R10 codes are specific to pain. Resistant pain is not chronic pain syndrome, unless the documenting provider has indicated it to be the case. The same is true for all chronic conditions for which the patient is receiving Chronic Care Management Services. Ongoing follow up and relevant documentation are necessary in order to reflect the chronic conditions of the patient and to ensure that the care plan and services and procedures related to the plan are appropriately assessed and coded.

Post-Operative Pain requires a Documented Relationship

Pain immediately following surgery is expected. Routine pain is not separately coded. If the postoperative pain is documented, G89 category would be appropriate.

G89.18 indicates other acute post-procedural pain and G89.28 indicates other chronic post-procedural pain.

It is important to remember, pain occurring after surgery is not always related to the surgery. Relationships must be documented. If pain is related to a complication, pain should be coded according to the complication and not using a two-code formula.

It is important to document the date and time of the post-surgical pain, nature and extent of the pain, expected duration of the pain, clinical assessment, course and complication. All these documents help in differentiating between an expected part of recovery, a different abdominal condition and post-operative pain.

Abdominal pain during pregnancy

Expectations of pregnancy can alter code selection and sequencing. Chapter 15 codes take precedence in sequencing over codes from other chapters when a condition related to pregnancy is present.

R10 should not be used when abdominal pain is the main complaint. Other chapter codes should be assigned and R10 should be added as appropriate.

Gestational age and assessed condition should be documented along with pertinent symptoms and whether the condition is affecting the pregnancy. Using the index, tabular list, and obstetric guidelines, the coder selects the complete code and accompanying detail.

Not all conditions which are not directly related to a pregnancy are Z33.1. A pregnant patient with a non-reproductive system condition, such as a gastrointestinal condition, is not always Z33.1.

Z33.1, pregnant state incidental, is applicable when the provider indicates that the pregnancy is incidental and not pertinent to the encounter. It should not be selected when the coder makes that determination on her/his own.

When there is a request for the pregnancy-related code to include information on the pregnancy trimester, use the documented pregnancy trimester. Include an additional weeks-of-gestation code if appropriate in the classification. Do not leave an O-code category open-ended as a finished diagnosis.

Most symptoms in and of themselves do not warrant the diagnosis of an obstetric complication. Symptoms such as bleeding, accompanied by pain, do not automatically justify the presence of threatened abortion, ectopic pregnancy, etc. Use the documented diagnosis and follow the reporting rules pertinent to the case and the setting.

For practices involved in obstetric care, a brief documentation frame can be helpful: record the clinical condition, the relationship to the pregnancy, and the gestational age in the assessment. This allows the coding staff to have a basis for sequencing, without having to make an inference as to the clinical causation.

Associated symptoms and additional diagnosis codes

Abdominal pain may be reported in the presence of nausea, vomiting, diarrhea, bloating, or with changes in the frequency of urination. Fever may also be reported in conjunction with abdominal pain. An unifying diagnosis may be established; however, other associated symptoms may be reported if they affect care and are allowable according to the setting.

Examples of associated symptoms may include R11.0 for nausea, R11.2 for nausea and vomiting, R19.7 for unspecified diarrhea, and R14.0 for gaseous abdominal distention. Codes associated with abdominal pain should be reported only when supportive of the condition described.

Vomiting does not always indicate the presence of nausea. Symptoms which resolved prior to the encounter do not always warrant reporting. Classification should be reviewed prior to selecting the first available associated code.

If the clinician diagnosed an underlying condition or determined that the symptoms were attributed to a different condition, these would warrant separate reporting. Symptoms reported at the initial encounter should be reviewed, and only those that support the final assessment and ruling-in or ruling-out of a diagnosis should be included in the final diagnosis list.

Clinical context and signs that need medical attention

Abdominal pain can come from many structures and for many reasons. Possibilities include constipation, infections, food intolerance or irritable bowel syndrome. Other possibilities include serious conditions like appendicitis or other obstructions, gallbladder issues, and other pathology.

Location can give the clinician an idea of what is wrong, but location usually doesn’t help pin point the diagnosis. Some pain is referred to other areas. A patient should not use a coding table to determine their diagnosis.

The same is true for pain severity. Pain can vary in intensity based on the condition. Sometimes a condition can be serious but the pain can be minimal. Based on the information from MedlinePlus, pain intensity does not always correlate to the severity of the condition.

Seek medical attention for any sharp or severe abdominal pain. Other reasons to seek medical attention include if you have a rigid, hard abdomen, you have bloody or black stool or vomit, you are having difficulty breathing, or you have any pain with chest symptoms. If you have any of the above symptoms or you are feeling very sick or in distress, you should call 911.

Call a doctor or go to the emergency room if you have the sudden onset of pain and bleeding during pregnancy, especially if you are feeling sick or having other symptoms. Call a doctor for any worsening or persistent pain, vomiting, fever, or symptoms of a urinary tract infection (UTI). These symptoms require medical evaluation and you shouldn’t rely on a code to determine if you need to see a doctor.

Documentation that helps the provider and coder

The objective is a clear and accurate clinical record. You do not need paragraphs filled with coding terminology, but you must provide enough detail for the reviewers to capture the reasoning of the clinician.

Be consistent with description of symptoms

When describing symptoms, you may need to capture attributes such as location, side, onset, duration, pattern and associated symptoms. When reporting a symptom as being “general,” “widely scattered” or “diffuse,” identify the various sites if they can be separated. Indicate if the pain is migrating or radiating if that information is important to establishing the diagnosis.

Avoid conflicting locations in a note. Discrepancies in history vs. assessment are common and not unexpected. If the history states that the pain is in the right lower quadrant and the assessment states that the pain is in the left lower quadrant, don’t expect coders to decide which one is correct.

Severity, triggers and the functional impact of the pain, when documented, enhance the clinical record and explain the reason for the encounter. If these do not affect the code, consider them background and reflective of the encounters. Document the history of the trauma including the mechanism of injury. Document findings of the physical examination.

Distinguish history and physical examination findings

Rigidity and rebound tenderness can best be documented under examination. Tenderness can best be documented as part of the history. If these are intermixed, coders may interpret the statement as meaning that pain was in a location that was not reported. For example, “patient states there is RUQ pain” and “RUQ exam is +T,” should not be interchanged with “RUQ pain and exam is +T.”

Assessment should also draw the conclusions for which findings are being captured. For example, “Patient states there is lower abdominal pain. Exam is +T over RLQ,” may also draw the conclusion “Diffuse abdominal pain. Etiology undetermined.”

Make the final assessment usable

Provide the agreed upon diagnosis/symptom at the end of the evaluation. If possible alternatives have not been ruled out, say so, rather than providing a list of differential diagnoses.

When a patient returns for a follow up visit, note what is known, not what was previously documented. A prior diagnosis may still be pertinent, but should not be copied and pasted as documented in previous visits, especially if a new symptom or problem is being addressed.

Ask focused, neutral, clarification questions.

A clarification request which is focused and relevant to the discrepancy helps the clinician eliminate the difference.

Don’t write a question which is a cover request for a more payable diagnosis. Let the clinician document a different, yet pertinent, diagnosis. The goal is to ensure an accurate documentation of the clinician visit, including the case when the appropriate diagnosis is an unspecified code.

Billing, medical necessity and payment are separate checks

Abdominal pain ICD 10 codes indicate the diagnosis or reason for the visit, and do not dictate the level of office visit, determine authorization for an imaging service or establish payment. CPT and HCPCS codes are used to identify outpatient services.

For evaluation and management services, consult the guidelines for the relevant code family and setting. Consider medical decision making or time where applicable. Do not raise the service level to the next higher category simply because R10.0 is on the claim, or because the patient described or documented abdominal pain of a level beyond what was documented.

The reason for ordering an imaging service is evaluated to determine if the service is medically necessary. A diagnosis does not always dictate the imaging service. The imaging service requested must be considered adequate and appropriate to answer the clinical question, and be supported by the medical policy.

There is no universal rate for abdominal pain. Payment for a service is dependent on a number of factors such as the type of service, the contract, the member’s benefits, the setting, and other details on the claim. Similarly, an inpatient diagnosis related group (DRG) cannot be assigned based on an abdominal pain code (R10) alone, without considering the entire member admission and other applicable groupers.

In order to determine why a claim was denied, the actual reason must be identified. Various issues require different solutions. For example, raising an abdominal pain code (R10.9) from a lower code to a more specific code will not resolve an eligibility denial, and is not appropriate, unless the documentation justifies the code level change.

Common abdominal pain coding mistakes and their fixes

There are a few key mistakes that happen due to old shortcuts rather than lack of clinical detail. Look at the code description in the EHR, the value in the claim, and the version of the code set the billing system uses. It is possible to have the right selection on one screen and have it be changed to a wrong mapping downstream.

Twelve practical coding scenarios

The following examples illustrate common coding scenarios and assist in interpreting the guidance for each scenario. Each scenario assumes the described assessment is supported, the appropriate revision to the code is selected and no undocumented omitted diagnosis would change the coding decision.

1. Epigastric Pain, Cause Unknown

The history takes epigastric pain. The clinician adds no diagnosis and performs further testing.

Guidance: Coding is to R10.13 as the unknown cause does not mean the location is unspecified. Check for other symptoms to determine if they are reportable.

2. Unspecified Abdominal Pain

Pain is only mentioned in the final assessment and history is equally unhelpful.

Guidance: Coding to R10.9 may be appropriate to the record, and a request for further information is warranted. Do not add a location code to remove an unspecified code.

3. Generalized Complaint

The patient reports generalized abdominal pain and no region predominates. No definitive diagnosis is established during the outpatient visit.

Guidance: Coding is to R10.84 to reflect the generalized abdominal pain. R10.9 is not appropriate to substitute the code.

4. Two Distinct Abdominal Sites

In the final assessment, pain is reported in the right upper and left lower abdomen.

Guidance: See R10.85 and exclusions. Do not append component location codes for the same pain. Confirmation the location is not describing migrating or radiating pain is warranted.

5. Right flank pain with no confirmed urinary diagnosis

A patient is evaluated for outpatient right flank pain and a diagnosis of renal colic, stone, or infection has not been made.

Coding direction: Symptoms will be coded to the body region documented. In this case R10.A1. Do not code a urinary disease just because a test was ordered to rule out that diagnosis.

6. Persistent suprapubic pain

Patient has pain above the pubic bone and the documentation states that no cause is established.

Coding direction: R10.24 is the code to assign. A generic abdominal code would not appropriately represent the documented region. Any other symptoms should be coded as well.

7. Rebound tenderness documented

A patient is evaluated for right lower quadrant pain and right lower quadrant rebound tenderness. There is no definitive diagnosis made.

Coding direction: R10.31 is coded for the pain. Rebound tenderness is documented, and would be coded as R10.823 in addition to the pain code. Do not substitute ordinary tenderness for documented rebound tenderness, or combine the codes.

8. Right lower quadrant pain with appendicitis considered at ED discharge

The ED record shows consideration of appendicitis with right lower quadrant pain, and the patient has not been admitted.

Coding direction: The uncertainty rule for the outpatient setting can be applied. R10.31 can be assigned to code the right lower quadrant pain. Coding the differential of appendicitis will not support it is confirmed.

9. Probable condition at qualifying inpatient discharge

The discharge summary of the hospital inpatient states that probable diverticulitis is documented after an evaluation. The case meets the setting requirements for the inpatient uncertain diagnosis rule.

Coding direction: Apply the rule and select a supported disease classification. Determine the principal diagnosis based on the admission and discharge situations, and not the original triage reason alone.

10. Chronic pain management is the visit’s purpose

The provider evaluates and manages chronic abdominal pain in the absence of a documented cause. The provider supports the site is involved.

Coding direction: G89.29 can be first, and a site-specific code can be assigned secondarily, if the site is involved. Do not use G89.4 unless chronic pain syndrome is documented.

11. Abdominal pain affects pregnancy care

A pregnant patient is evaluated for abdominal pain and the provider documents the condition affects care and puts it in the context of the pregnancy. The trimester and gestational age are also documented.

Coding direction: Follow selection and sequencing for chapter 15, and include additional information as necessary. Do not default to R10 plus Z33.1 when pregnancy is not incidental.

12. A later visit establishes the cause

There is a history of an earlier outpatient visit for abdominal pain of unknown cause. At a later visit, the cause of the pain is determined, and the plan is changed.

Coding direction: Code each visit using the documentation and certainty applicable to the visit. Review any necessary correction through the proper process; do not automatically overwrite every historic symptom-coded claim.

Build a useful pre-submission review

An abdominal pain ICD 10 review works best when it’s routine. Provide the coding team with a consistent structure instead of a long list of random warnings.

First, determine whether the encounter occurred. Check the patient, service date, care setting, relevant provider’s note and released code-sets. These will assist in determining which set of directives control the evaluation of the diagnosis combination before any other review.

Second, analyze the assessment and the code. Explain discrepancies between the symptom and/or disease, body location, laterality, and whether the finding was assessed as pain or an examination sign. Resolve differences through the query process.

Third, evaluate the overall diagnosis list. This includes looking for body system symptoms, duplicate concepts, exclusions, and unsupported carry over from previous visits. Consider the special rules for inpatient discharge and pain management.

Fourth, determine the adequacy of service and coverage. Ensure the diagnosis adequately describes the service provided and relevant authorization, eligibility and/or order are provided. Coverage and adequacy of service should be determined separately.

Last, learn from submitted claims. Identify the reason for the denial and/or the specific template affected. Describe the correction made to the template. System errors should be addressed by the systems group and unresolved clinical issues should be addressed in a documentation discussion. Reviewing these patterns will be more helpful than telling staff to refrain from using unspecified codes.

Frequently asked questions

Which abdominal pain ICD 10 code should I use first?

Begin with the documented diagnosis and care setting. R10.9 applies to unspecified abdominal pain, but a specific region or distribution may support another R10 code. A confirmed disease, pregnancy-related condition or pain-management encounter can change selection and sequencing. There is no universal first code for every patient.

Is R10.9 acceptable when testing does not find a cause?

Yes, when unspecified abdominal pain accurately reflects the record. However, an unknown cause does not require R10.9 if the pain’s location is established. Use the supported site-specific code when appropriate. Do not order unnecessary tests or invent specificity simply to avoid an unspecified diagnosis code.

What separates generalized pain from multiple-site pain?

R10.84 describes generalized or diffuse abdominal pain. R10.85 describes multiple distinct sites. The provider’s assessment should identify the pattern. Do not infer multiple sites from radiation alone, and review R10.85 exclusions before adding localized or generalized abdominal pain codes for the same presentation.

Is R10.2 still a complete code for pelvic pain?

No, not in the FY2027 code set. R10.2 is a heading with more specific child codes. Use R10.20 through R10.23 for the documented pelvic or perineal laterality, or R10.24 for suprapubic pain when supported. Historical encounters must use their applicable code release.

Does abdominal cramping always use R10.83?

No. R10.83 describes colic NOS or infantile colic and excludes colic in adults and children over 12 months, directing that circumstance to R10.84. Cramping alone does not establish infantile colic. Follow the provider’s diagnosis, location, patient age and the Alphabetic Index.

Can pain and tenderness appear on the same claim?

They may both be reportable when separately documented and supported by the setting’s rules and tabular instructions. They should not be added as an automatic pair. Review whether a confirmed diagnosis explains them and whether the additional finding meets reporting requirements for the encounter.

Does a more specific diagnosis guarantee payment?

No. Accurate specificity helps the claim reflect the record, but payment also depends on the service, coverage, benefits, authorization and other requirements. A diagnosis must never be changed solely to fit a payer’s preferred list. Investigate the actual denial reason before deciding on a correction.

Which code year applies to services in October 2026?

FY2027 ICD-10-CM applies beginning October 1, 2026. Use the appropriate release for the outpatient service date or inpatient discharge date, and check official updates. A claim submitted in October for an earlier encounter may still require an earlier code set.

Situate the documented encounter at the core of your coding process

A clear assessment regarding the symptom or disease, where the symptom is situated, relevant findings of the physical examination, and what is documented at the encounter is the foundation of Abdominal pain ICD-10 coding. The codes assigned should represent the above mentioned assessments in a thorough and precise manner without the inclusion of unsubstantiated diagnoses or losing relevant details.

The current coding tables are your starting point. Confirm the selections in the official classification and apply the rules of the environment (context) in which coding is done. Pay special attention to pregnancy, chronic and acute pain, the Acute Abdomen, and the difference between an uncertain outpatient diagnosis, and a qualifying inpatient discharge diagnosis.

If your office continues to see abdominal pain claim denials, have your clinical and coding teams review a sample of your encounters where abdominal pain is documented. Have them consider what is documented in the encounter, how the EHR was coded, and the reason for denial. Next steps can include template adjustments or addressing specific documentation concerns to enable accurate claims and lessen needless and unnecessary work.