Medical Coding Outsourcing: 12 Questions to Ask Before You Sign

Medical coding outsourcing works when the vendor can prove accuracy, keep up with code changes and flag documentation gaps instead of guessing. Before you sign, ask about coder credentials, audit methods, turnaround, query handling, pay incentives and data security. The practice stays responsible for every claim filed under its providers' numbers, so the contract has to spell out how errors are found and fixed.

Why coding is worth getting right

Code sets change every year. For 2026, the AMA added 288 new CPT codes, deleted 84 and revised 46, effective January 1. ICD-10-CM updates take effect each October 1; the FY 2026 guideline changes went into effect Oct. 1, 2025. A coder who isn't trained on these changes produces denials in January and October.

Payers also look closely at documentation. CMS estimated the Medicare fee-for-service improper payment rate for FY 2025 at 6.55%, or $28.83 billion, and said most improper payments occurred where a reviewer could not determine whether a payment was proper, which CMS ties to documentation gaps. Coding can't fix weak notes, but a good coder flags them before the claim goes out.

Staffing is the third pressure. The Bureau of Labor Statistics reports a 2025 median pay of $51,140 for medical records specialists, an occupation whose BLS profile describes medical coders, and projects 8% employment growth from 2025 to 2035, much faster than average. Hiring and keeping experienced specialty coders is hard for a small practice.

12 questions to ask a coding vendor

Credentials and fit

1. What credentials do your coders hold, and in which specialties? Ask for the credential mix (for example, AAPC or AHIMA certifications) of the specific coders who will work your account, not the company average.
2. Have you coded for practices like ours? Cardiology, orthopedics, behavioral health and primary care each have their own patterns. Ask for the volume they handle in your specialty.
3. Are coders dedicated to our account? Dedicated coders learn your providers' documentation habits. Pooled coders rotate, and accuracy often suffers.

Accuracy and audits

4. How do you measure accuracy? Ask for the audit method: sample size, frequency, who audits and how errors are scored. The OIG's compliance guidance for billing companies recommends annual review of a valid statistical sample of claims by a qualified coding expert, plus periodic spot-checks of coding staff.
5. Will you share audit results with us? Monthly or quarterly reports by coder and by error type. If they won't share them, assume the numbers aren't good.
6. How are coders paid? The same OIG guidance warns against compensation that creates a financial incentive to upcode. Avoid vendors whose pay is a percentage of collections without safeguards.

Process

7. What is your turnaround time from documentation to coded claim? Agree on a standard in business days and how it is measured.
8. How do you handle documentation queries? Coders should send unclear notes back to the provider, as the OIG guidance recommends, not guess. Ask how queries are sent, tracked and escalated.
9. How do you train on code updates? Ask what happens before January 1 and October 1 each year, and how payer-specific policies are tracked.
10. What happens when a claim is denied for a coding reason? Denials should feed back to the coder, with a fix and a pattern review. Our guide to denial management services covers how that loop should work.

Security and contract

11. Do you sign a BAA, and where does our data live? The vendor should work inside your EHR or practice management system with role-based access, sign a Business Associate Agreement and tell you in writing where any data is stored.
12. What are the exit terms? Ask about notice periods, transfer of work in progress and return or destruction of data at the end.

Red flags in a coding proposal

How to start without risking cash flow

1. Run a parallel test. Have the vendor code a sample of recent encounters that your team has already coded, then compare results.
2. Start with one provider or one visit type. Expand once accuracy and turnaround meet the agreed standard.
3. Set a 30-day review. Look at accuracy, turnaround, query volume, coding-related denials and days to bill.
4. Keep a person in-house who owns the relationship. Someone needs to answer queries, review audit reports and raise issues.

When to keep coding in-house

Keep it in-house if your volume is small and a single experienced coder knows your providers well, if your specialty is so narrow that few vendors have experience in it, or if your providers' documentation needs a lot of in-person education first. Outsourcing makes more sense when coder turnover is high, backlogs delay billing, you need coverage across several specialties, or code-change season brings a spike in denials. For the cost side of the decision, see the real cost of an in-house medical biller.

Key takeaways

• Code sets change every January and October. Ask how the vendor trains for both.
• Demand an audit method and regular audit reports by coder and error type.
• Avoid pay structures that reward upcoding and any promise of guaranteed revenue gains.
• Coders should query providers, never rewrite documentation.
• Start with a parallel test and one provider before moving everything.

Telemed provides billing and coding support for U.S. medical practices, with dedicated teams working inside your systems under a BAA.