The Red Flag You Missed Before You Signed
A regional physician group in the Midwest switched coding vendors primarily on price. The new vendor's quote came in 30 percent below their previous partner, and the contract was signed in under two weeks. Six months later, their denial rate had climbed from 4 percent to nearly 11 percent, their DNFB balance had ballooned, and AR days had crept past 50. When they finally audited a sample of charts, they found coders who were not credentialed for the specialties they were coding, no second-level review on complex cases, and a QA process that existed only on the vendor's sales deck.
The painful part? Every one of those problems was visible before the contract was signed. The warning signs were there. Nobody knew what to look for.
This post gives you a specific checklist of medical coding company red flags, what good looks like for each one, and how to run a structured pilot so you test claims before they cost you real revenue.
Red Flag 1: No Measurable Accuracy Standard or Unwillingness to Guarantee One
Any experienced coding company should be able to tell you their accuracy rate, broken down by code type and specialty, and back it with documented QA data. If a vendor gives you a vague answer like "our coders are very experienced" or "we focus on quality," stop the conversation and ask again directly: what is your current first-pass accuracy rate, and what does your QA process look like?
A credible partner will tell you they run ongoing internal audits, that all work passes through a defined QA layer before it leaves the coding team, and that they are willing to contractually commit to an accuracy threshold, typically 95 percent at minimum, with 98 percent or above as the industry standard for a quality operation. If they cannot or will not commit to a number, that tells you everything.
A good partner not only states their accuracy target but documents it in the service agreement, reports against it monthly, and has a clear remediation plan when they miss it.
Red Flag 2: A Price That Is Far Below Market With No Explanation
Medical coding pricing varies by model: per-chart fees, per-RVU fees, and percentage-of-collections each carry different economics. Typical per-chart fees in the market range meaningfully depending on specialty complexity, but there is a floor below which quality is simply not possible. Credentialed coders with specialty experience cost real money to recruit, train, and retain.
When a vendor quotes you a rate that is 30 to 40 percent below every other proposal you received, ask them directly how they achieve that cost. The answers are usually one of three things: uncredentialed coders, very high coder-to-QA ratios with minimal review, or volume-based models where your account is a low-priority batch job. None of those outcomes are good for your denial rate.
The cheapest quote is usually the most expensive. A denial rate that climbs 5 percentage points on a $10 million revenue practice costs far more than the savings on a coding invoice. Run the numbers using the free Coding Outsourcing ROI Calculator before you let price dominate the decision.
Red Flag 3: Vague Answers About Who Actually Does the Coding
This is one of the most underasked questions in vendor evaluation. You are not just buying a service; you are handing over your revenue integrity and your compliance posture to specific human beings with specific credentials and specific training. You have every right to know exactly who those people are.
Ask: Are your coders AAPC or AHIMA certified? What credentials do the coders assigned to my specialties hold? Are they CPC, CCS, CRC, or another designation relevant to my volume mix? How long have they been coding in this specialty? Is there a lead coder or coding supervisor reviewing their work?
A good partner will answer these questions without hesitation and, in many cases, will introduce you to the team lead or provide credential summaries as part of onboarding. If the sales rep deflects, gets defensive, or says the coders are "all highly experienced," that is a red flag. Experience without credentials is not auditable.
Red Flag 4: No BAA or Casual Dismissal of Security Requirements
A Business Associate Agreement is not optional. It is a federal requirement under HIPAA. If a vendor hesitates to sign a BAA, asks you to waive it, or suggests it is just a formality they can get to later, end the conversation.
Beyond the BAA itself, ask how PHI is transmitted, stored, and accessed. Credible vendors operate on encrypted platforms, control access through role-based permissions, conduct regular internal security assessments, and can speak intelligently to frameworks like SOC 2 or HITRUST even if they are not fully certified. Offshore delivery models can be fully HIPAA-compliant when the right technical and administrative safeguards are in place, but the vendor needs to be able to demonstrate that, not just assert it.
If security gets a hand-wave during sales, it will get a hand-wave after the breach.
Red Flag 5: No Defined QA Process or Second-Level Review
Coding errors are not random. They cluster by coder, by payer, by specialty, and by code category. A mature QA process catches those patterns before they become denial trends. A vendor with no second-level review, no documented audit cadence, and no QA reporting is essentially asking you to self-detect their errors through your own denial management workflow.
Ask specifically: what percentage of charts receive a secondary review? How often do you conduct internal audits? What triggers an escalation to a senior coder? What happens when a coder's accuracy drops below threshold?
If you want to pressure-test a vendor's quality claims before signing, consider starting with a coding quality audit on your existing work. The results give you a baseline and a concrete comparison point when you evaluate the vendor's own QA output during a pilot.
Red Flag 6: No Specialty Depth
General coding competency does not transfer cleanly across specialties. Orthopedics, cardiology, behavioral health, oncology, and ED coding each have their own documentation patterns, payer quirks, and high-risk code categories. A vendor who says their coders can handle anything should be pressed on exactly that claim.
Ask them to walk you through how they staff specialty-specific engagements. Do they assign coders by specialty? What is the coder's track record in your specific specialty? Have they worked with your payer mix before?
For practices with complex ProFee volume, this matters even more. Specialty-specific physician coding (ProFee) requires coders who understand the nuances of modifier use, incident-to billing, and place-of-service rules, which are areas where generalists make consistent, costly errors.
Red Flag 7: No References and a Refusal to Run a Pilot
A vendor who cannot produce two or three current client references in a comparable specialty is a vendor who either does not have satisfied clients or has not been doing this long enough. Either way, that is a problem.
Call the references. Ask specifically about denial rates, accuracy rates, reporting quality, and how the vendor handled a problem when one arose. A vendor who handled a problem well is often a stronger reference than one who claims nothing ever went wrong.
The pilot refusal is an even harder red flag. A confident, established coding company will offer a structured pilot, paid or free, on a defined chart sample. They will accept your scrutiny because they know what the results will look like. A vendor who resists piloting, cites operational complexity, or tells you to just trust the contract is signaling that they do not want you to look too closely before you commit.
Red Flag 8: Opaque Reporting and No Denial Accountability
Your coding partner should give you visibility, not just invoices. Ask what reporting comes standard. Can you see coder-level accuracy by chart type? Is denial data tied back to coding root cause? Do you get monthly performance summaries with trend lines?
Denial accountability is the real test. When a claim is denied for a coding-related reason, a good partner owns it, corrects it, and flags the pattern to prevent recurrence. A bad partner will code the rework as additional volume and move on. The difference in AR days between those two approaches is measurable within 60 days of going live.
If you want a structured way to score reporting and accountability criteria before you select a vendor, the coding vendor scorecard gives you a ready-made framework.
Red Flag 9: High Coder Turnover
Coder turnover is one of the most underappreciated quality risks in outsourced coding. Every time a coder leaves, institutional knowledge of your documentation patterns, your payer preferences, and your provider habits leaves with them. The replacement coder's learning curve shows up in your denial rate.
Ask vendors directly: what is your annual coder turnover rate? How do you document coder-specific knowledge during transitions? What is your average coder tenure?
High turnover is often a sign of poor internal culture, low compensation, or production pressure that burns coders out quickly. None of those conditions produce accurate, consistent work on your charts.
What a Structured Pilot Actually Looks Like
A well-run pilot removes most of the guesswork from vendor selection. Here is what to require.
- A defined chart sample of 50 to 150 charts, drawn from your actual recent volume and covering your most complex and highest-revenue code types.
- A parallel run where the vendor codes the same charts your current team has already coded, so you have a direct comparison point.
- A blind QA review of the vendor's output by a neutral third party or your own HIM team.
- A debrief where the vendor walks through any discrepancies and explains their coding rationale.
- Reporting that shows coder-level accuracy, not just aggregate results.
A vendor who performs well on a structured pilot with your actual charts, your actual payer mix, and your actual specialty complexity is a vendor who has earned the contract.
How MedCodex Approaches Each of These Standards
MedCodex is a HIPAA-compliant coding and CDI partner with AAPC and AHIMA certified coders, a documented QA process with 98 percent or above accuracy, and a BAA included as a standard contract term. We specialize by service line, including outpatient coding, ProFee, and CDI, and we assign coders based on specialty match rather than availability. We offer a free pilot, we provide denial-linked reporting, and we will put references in front of you before you sign anything.
We built our model around the assumption that you have been burned before or that you know someone who has. Every process we have is designed to make that fear go away with evidence rather than promises.
If you are actively evaluating coding partners right now, reach out to the MedCodex physician coding team to schedule a pilot scoping call and see exactly how our process holds up against the checklist you just read.