The FY2026 ICD-10-CM update introduced more specific ways to report flank pain and injuries beginning October 1, 2025. For coding leaders, the operational task is to apply those changes consistently across documentation, code assignment and quality review. Confirm that the code set matches the encounter’s applicable date and that the record supports the selected detail. This guide focuses on the flank changes and the controls that help teams put them into practice.
Flank pain coding has long been hampered by a lack of specificity in options. If you input "pain, flank," the ICD-10 index will point you to "pain, abdominal." From there, a slew of possibilities opens up, from R10.9 "unspecified abdominal pain" to R10.11 "right upper quadrant pain." (1)
Adding to the complexity is that pain in the flank, the side of the torso below the ribs, can radiate to the abdomen - and abdominal pain accounts for some 10% of emergency room visits (2). Emergency departments (EDs) are facing ambiguity in coding and symptom presentation, and they're dealing with it regularly and at high volumes.
For health information management (HIM) directors, ED practice managers, and revenue cycle leaders, this ambiguity has represented a persistent challenge: How do you capture reimbursement for services when the coding system doesn't adequately reflect the anatomical specificity of the encounter? The 2026 ICD-10 updates finally offer a solution.
The FY2026 ICD-10-CM release added flank-specific codes effective October 1, 2025. Apply the code set associated with the encounter’s applicable date and verify the record against the relevant coding instructions. The operational requirement is consistent use across documentation, code assignment and quality review.
Flank pain is considered a non-specific symptom, meaning it isn't linked to any one condition but associated with a wide variety of health concerns. A patient reporting flank pain could be experiencing anything from kidney stones to a urinary tract infection, rib injury, musculoskeletal strain, or even referred pain from a gastrointestinal issue (1).
The flank-specific codes distinguish the documented location more precisely. Select the code supported by the record and applicable guidance, including laterality when documented.
The FY2026 release introduced four flank-pain codes effective October 1, 2026:
For flank contusions, use the applicable complete code: S30.13XA for an initial encounter, S30.13XD for a subsequent encounter or S30.13XS for sequela. The X placeholder is required.
Nym ensures prompt compliance with new ICD-10 codes for 2026. When guideline changes are announced, Nym's internal team updates Nym’s autonomous coding engine. This enables medical coding teams at provider organizations to continue operating seamlessly without any need for additional staff training or the inconvenience of operational lag time.
In addition to making life easier for staff, this also protects the bottom line by minimizing the risk of coding errors, which cost healthcare about $36 billion every year (4). In the past, outdated coding systems could contribute to such costly mistakes, but with Nym ensuring immediate alignment with updates, the risk is minimized.
Another key asset of Nym is that it creates fully traceable audit trails, supplemented with supporting documentation and evaluation and management (E/M) level justifications. This is invaluable in the event of audits, which can otherwise leave teams scrambling to find the paperwork needed to explain past coding decisions.
This can become especially problematic in the wake of changes like ICD-10 updates, when people, processes, and systems have not yet fully integrated the new codes, creating confusion and, in some cases, incorrect coding.
Nym’s coding-specific AI applies configured coding guidance consistently across the encounters it codes autonomously. Guideline updates are part of maintaining that capability, alongside validation and customer communication. Each coded encounter includes an audit trail that connects assigned codes to supporting documentation and guidance. Ask Nym how an update is tested, how affected encounters are reviewed and how exceptions are handled. Use those answers to define responsibilities for your organization’s next code-set transition.
If you're interested in learning more about autonomous medical coding, check out Nym's Autonomous Coding Education Hub. With a collection of articles, guides, case studies, and worksheets tailored to your role and stage in your autonomous coding journey, you're guaranteed to find what you need.
The FY2026 release introduced R10.A0 for flank pain of unspecified side, R10.A1 for right-sided pain, R10.A2 for left-sided pain and R10.A3 for bilateral pain. For flank contusions, the complete codes are S30.13XA for an initial encounter, S30.13XD for a subsequent encounter and S30.13XS for sequela. These codes took effect October 1, 2025. Use the code set applicable to the encounter date.
When new guidelines are published, our Compliance and Clinical teams review the changes and translate them into technical updates. These updates are implemented into Nym’s autonomous coding engine, validated for accuracy, and communicated to customers before they ever enter production. Learn more about Nym’s update process here.
Greater specificity helps a claim reflect documented care. Payment still depends on applicable coverage, coding and payer requirements. Monitor coding accuracy and denial reasons to identify whether the change improves your organization’s results.
Sources: