Also: look for tips on when to query the provider. Understanding the distinction between signs and symptoms and primary conditions is vital to accurate diagnosis coding. It can be tricky for new and seasoned coders to know which symptom codes to report and when to query the provider. If you are looking to avoid redundancy and shore up your R-code know-how, keep reading as our panel of experts during the June 2023 Ask & Learn titled “R Codes: Signs, Symptoms and Coding from Documentation” helped us bust common myths about reporting these chapter 18 codes. Remember: According to ICD-10 guideline 1.B.4-6, “Codes that describe symptoms and signs, as opposed to diagnoses, are acceptable for reporting purposes when a related definitive diagnosis has not been established (confirmed) by the provider… Signs and symptoms that are associated routinely with a disease process should not be assigned as additional codes, unless otherwise instructed by the classification. Additional signs and symptoms that may not be associated routinely with a disease process should be coded when present.” Myth 1: I must query my provider whenever they don’t specifically link signs and symptoms with the diagnosis. While it’s true that as coders you shouldn’t make assumptions, the idea that a query is the only way to determine whether a sign or symptom is related to a diagnosis is false. According to the guidelines mentioned above, you don’t code for symptoms that are inherent to the established diagnoses. But the guidelines also say to code for symptoms that are not common or not routinely associated with that condition. Knowing whether a symptom is common or routinely associated with the condition sometimes requires some initiative and self-education. “Many symptoms and conditions are those we see all the time. But when we come across codes that are less familiar to us, it’s important to reference anatomy resources to keep sharp,” said Linda Renner, CPC, CPCO, CPMA, CRC, CDEO, CPC-I, CEMC, CCC, CGSC, population health coding analyst at Saint Luke’s Health System in Kansas City, MO during the Ask & Learn. It’s never a bad idea to query the provider though. For example, maybe a patient came in for smoking cessation counseling. There’s a code for chronic cough, but there is also a code for smoker’s cough. “If the patient presented for smoking cessation counseling, as coders we might assume there is a relationship between that cough and the smoking, but we can’t assume. That is an instance where we’d have to reach out to the provider.” Renner said. Sometimes, a symptom is related but not common. This is another example where a little self-education can go a long way. For example, flu is quite common, and as primary care coders, you’re familiar with most of the symptoms associated with the condition, such as fever, body aches, and cough. Let’s say that the provider also documents that the patient is having febrile seizures. “That is related to flu, but not common. So, per the guidelines, we’d code that in addition to the flu with R56.00 (Simple febrile convulsions),” Renner explained. Coding alert: “For those of you with value-based plans or who are doing risk adjustment, R56.00 is actually a hierarchical condition category (HCC) code that we want to capture. Knowing these codes and the specific rules that come up only in the tabular section is really important. We aren’t coding from the index,” Renner continued. Myth 2: During a patient’s annual wellness exam, my provider documented ataxia with history of stroke. I should capture this as R27.0 and Z86.73. Independently, these codes represent two conditions: Ataxia, coded to R27.0 (Ataxia, unspecified), and history of stroke, coded to Z86.73 (Personal history of transient ischemic attack (TIA), and cerebral infarction without residual deficits). However, this is not likely how you should report the situation. To understand why, first look up “ataxia” in the index. Under that, you will see the sub-entry “following,” which leads to subsequent sub-entries for “cerebrovascular disease” and, finally, “cerebral infarction” (i.e., ischemic stroke). At that point, the index directs you to I69.393 (Ataxia following cerebral infarction). “By saying the patient has ataxia with a history of stroke, the provider is linking these conditions together,” explained Claire Stevenson, COC, CIC, CPC, CPMA, CDEO, coding audit and education coordinator at Northwest Specialty Hospital in Post Falls, ID during the Ask & Learn. “So, in this case, the ataxia is a sequela of the stroke. The stroke is clearly no longer acute. The patient isn’t seeing this provider for acute stroke symptoms if they’re at their annual wellness visit. What they’re left with is this loss of coordination,” said Stevenson. As mentioned in the previous answer, you never want to code solely from the index, but as this question illustrates, it’s important to use the index as a starting point and follow the trail to the correct code. The correct code for this happens to be a combination code, I69.393. Even if you knew from the documentation that the ataxia was sequela of the stroke, you might incorrectly follow typical sequela coding, “which would be whatever your condition is, potentially R27.0 followed by the initial code with the 7th character,” Stevenson said. However, Excludes1 notes following R27.0 and Z86.73 reinforce that I69.393 is the better choice. The Excludes1 note following R27.0 states, “ataxia following cerebrovascular disease (I69. with final characters -93),” and an Excludes1 note following Z86.73 states, “sequelae of cerebrovascular disease (I69.-).” Myth 3: Back pain codes aren’t in chapter 18, so we can’t code back pain as a sign or symptom. We have to code that as a diagnosis. There’s no clear reason why back pain codes aren’t listed in chapter 18, but we can use back pain codes as a sign or symptom even though they’re not R codes. “This is because ICD-10 guidelines give us the option to define our own signs or symptoms. ICD-10 guideline 1.B.4 says, ‘… Chapter 18… (codes R00.0 – R99) contains many, but not all, codes for symptoms,’” said John Piaskowski, CPC-I, CPMA, CUC, CRC, CGSC, CGIC, CCC, CIRCC, CCVTC, COSC, specialty medicine auditor at Capital Health in Trenton, New Jersey and surgical coding consultant at Memorial Care Health System in Huntington Beach, California during the Ask & Learn. However, you’ll likely find yourself back at the first question, wondering whether or not you should report back pain, depending on the diagnosis. For example, back pain is common with a lot of different spinal conditions. “If your provider documents degenerative disc disease and back pain, you are pretty safe to go ahead and remove that back pain as a signs and symptoms code and capture only the disease for your code,” said Stevenson. However, if it looks like it’s possible there is some differential diagnoses that are causing the back pain outside of the degenerative disc, “then it would be appropriate to capture the back pain code in addition to the listed diagnosis,” Stevenson added. Expert tip: “Whether it’s ultimately going to be a sign and symptom or something completely different is likely going to be up to the provider,” said Piaskowski. But don’t be afraid to talk to your provider and come to an agreement about how the provider can differentiate back pain as a symptom of an existing diagnosis or as something separate in the notes. That way, you’re not constantly going back and forth for the same kinds of things, Piaskowski suggested.