Bridging the Communication Gap Between Coders and Providers
Article Reference Code: NAMAS.07.24.2026
Written by: Dawson Ballard Jr, RHIA, CCS-P, CEMA, CPC, CPMA, RCMS, CPCD, CUC, CRC, CPC-P, AAPC Fellow
In healthcare, coders and providers are a bit like roommates sharing the same kitchen. They both want things to run smoothly, and they both care about accuracy, but they often label things very differently.
Because of that, communication can sometimes feel less like collaboration and more like a long-running sitcom full of miscommunication and misunderstanding, just without the laugh track.
Providers spend their days diagnosing, treating, and heroically surviving back-to-back appointments while wondering if lunch is a myth. Coders, meanwhile, take those notes and attempt to translate them into a highly regulated language that pleases payers, auditors, and the Coding Gods. So when a coder asks, “Can you clarify laterality, acuity, and whether this condition is acute on chronic?” the provider hears, “I, personally, would like you to re-open this chart and contemplate your life choices.”
The root of the issue? Different languages. Providers speak fluent medicine. Coders speak fluent compliance. The EHR acts as a translator who technically knows both languages but insists on autocorrecting everything at the worst possible moment. The result is a chart that makes perfect sense clinically but leaves coders whispering, “This needs… more words.”
Education helps—and no, that doesn’t mean handing providers a 300-slide coding deck and hoping for the best. Bite-sized, specialty-specific tips work far better. Explaining why documentation matters (risk adjustment, medical necessity, fewer denials, fewer angry emails) makes it feel less like busywork and more like self-preservation. Coders benefit too when they understand that providers are not withholding documentation out of spite, but because they are, in fact, human.
Then we have the provider query: infamous, misunderstood, and deeply emotional. A good query is collaborative and neutral. A bad query reads like it was written by a very disappointed toaster. Tone matters. “Can you help clarify?” invites cooperation. “Documentation insufficient” invites a sigh so deep it echoes down the hallway. Clear templates and standardized processes can turn queries from chart horror stories into mildly inconvenient speed bumps.
Relationships make everything better. When coders and providers actually meet—yes, face-to-face or at least camera-to-camera—everyone remembers there’s a real person on the other end of the message. Regular huddles help both sides vent productively, review trends, and bond over shared frustrations like payer logic that defies physics.
Technology can help—but only if it’s used wisely. Templates, smart phrases, and prompts are wonderful tools when they support clinical thought instead of turning notes into copy-and-paste novels. No one needs a three-page progress note that says absolutely nothing new. The goal isn’t “more documentation,” it’s “the right documentation,” which saves coders from detective work and
providers from repeat queries that feel suspiciously familiar. When tech supports clarity instead of clutter, everyone’s blood pressure drops slightly.
Leadership also sets the tone. When documentation integrity is framed as a team sport instead of a post-game penalty, communication improves. Recognition helps too. Nothing builds goodwill like hearing, “Hey, documentation improved and denials went down,” instead of “Please see attached list of everything wrong.” Investing time for education, collaboration, and feedback sends a strong message that this work matters—and that no one is fighting this battle alone.
At the end of the day, coders and providers aren’t opposing forces— they are teammates trying to navigate a highly regulated escape room called healthcare. With better communication, clearer expectations, smarter tools, and a solid sense of humor, they can stop talking past each other, start working together, and maybe—just maybe—close a chart without anyone muttering under their breath.
Contact Dawson LinkedIn by Clicking his Name Below:
Dawson Ballard Jr, RHIA, CCS-P, CEMA, CPC, CPMA, RCMS, CPCD, CUC, CRC, CPC-P, AAPC Fellow
Dawson Ballard, Jr. has an unquenchable passion for medical coding, so much so that many affectionately call him a true “coding nerd.” With more than 20 years of experience in CPT, ICD-10-CM, and HCPCS coding, he has built his career as a respected consultant, auditor, and educator. His consulting work focuses on Evaluation and Management (E/M), risk adjustment, and ICD-10-CM coding, with expertise spanning multiple specialties, including OB/GYN, Family Practice, and Internal Medicine.
Actively engaged in the medical coding community, Dawson is a proud member of both AAPC and AHIMA. His involvement includes publishing professional articles, serving as a local AAPC chapter officer, and contributing as a board member for his AHIMA State Component Association. He has also delivered numerous educational presentations for local chapters and his state association, sharing his knowledge and advancing the profession. In recognition of his contributions and years of service, Dawson has been honored as a Fellow of AAPC, a distinction that reflects both his expertise and his enduring commitment to the medical coding profession.
NAMAS BLOG Disclaimer:
The NAMAS Blog features content written by both NAMAS staff and guest contributors. Guest contributors may present opinions or perspectives that differ from those officially instructed or encouraged by NAMAS. We believe in providing space for a range of informed viewpoints to foster dialogue, reflection, and deeper understanding within the auditing and compliance community.
Some contributors may use artificial intelligence (AI) tools in the development of their content. The decision to incorporate AI is left to the discretion of the author and does not reflect an endorsement or directive from NAMAS.
If you have questions, comments, or concerns about a specific blog post, we encourage you to contact the individual author directly. Their name and contact information are provided at the end of each post.
