A proposal arrives with a competitive coding rate and a promise of additional capacity. Leadership wants to know what the organization will gain, while coding managers need to understand how much coordination the engagement will require.

Outsourcing medical coding services deserves a business case grounded in the work being assigned. That means examining current costs, identifying the operational problem, and defining how results will be measured.

The objective might be maintaining coverage during vacancies, reducing a defined backlog, or supporting a specialty that needs additional expertise. Each objective creates different staffing, implementation, and reporting requirements.

This guide explains how healthcare organizations can evaluate the costs and results of outsourced coding. Explore Cooper Thomas’s healthcare services when considering coding alongside health information management and technology needs.

Define the Objective Before Comparing Costs

Start with the problem your organization expects the engagement to address.

“Improve coding operations” is difficult to assess. A defined objective gives managers a basis for comparing the proposal with actual performance.

Examples include:

  • Completing an identified inventory of older encounters.
  • Providing coverage during a recruitment period.
  • Maintaining turnaround for selected outpatient queues.
  • Adding capacity for a growing service line.
  • Reviewing recurring coding quality concerns.

Specify the records involved, the current condition, and the expected outcome. Identify which dependencies remain with internal teams, such as obtaining missing documentation.

For service-model options, read our medical coding outsourcing guide.

Establish a Baseline for the Assigned Work

A baseline helps your organization understand what changes after implementation.

Use a representative period and separate encounter types where practical. Differences in complexity can make organization-wide averages difficult to interpret.

Baseline measureInformation to capture
Incoming volumeEncounters entering the defined workflow
Completed workRecords finalized during the period
InventoryOutstanding records by age and status
Documentation holdsCounts, reasons, and unresolved time
Quality findingsResults and methodology from available reviews
Staffing effortCoding, supervision, and coordination time
Existing expenditureRelevant staffing, overtime, and service costs

Document limitations in the available data. If the organization cannot reliably distinguish ready-to-code records from documentation holds, establish those definitions before using queue age as a performance measure.

Identify the Costs That Will Change

Outsourcing medical coding services introduces vendor charges and may change internal workload.

Some existing costs may continue. Others may decrease, increase, or move between departments. The business case should explain those assumptions.

Vendor Charges

Request a proposal identifying the billing unit, included tasks, and additional charges.

Ask about production coding, implementation, routine quality review, education, reporting, and work outside the original scope.

Internal Coordination

Estimate the time required for access approval, orientation, documentation questions, performance meetings, and review of findings.

These responsibilities need assigned owners and sufficient capacity.

Transition Effort

Account for workflow testing, preparation of instructions, initial review, and any temporary overlap between teams.

Show one-time implementation costs separately from recurring operating costs.

Compare the Same Workload Across Options

A useful comparison uses consistent encounter types, volume assumptions, quality requirements, and deliverables.

If one proposal includes reviews and another prices them separately, adjust the comparison to reflect the intended scope.

Cost areaWhat to clarify
ProductionIncluded encounters and complexity assumptions
OnboardingOrientation, access preparation, and testing
Quality oversightReview frequency, sampling, and scoring
ExceptionsTreatment of incomplete or complex records
ReportingIncluded reports and management meetings
EducationTraining and follow-up reviews
Volume changesMinimum commitments and adjustment pricing
TransitionResponsibilities for unfinished work at contract end

Request estimates for a representative month and a plausible change in workload. Ask providers to show how the pricing responds.

Assess Staff Readiness Alongside the Rate

The proposed team’s experience should match the assigned work.

Ask who will perform the coding, what comparable records they have handled, and how readiness is assessed.

AHIMA describes its Certified Coding Specialist credential as demonstrating coding proficiency and skills in data quality and accuracy. Evaluate credentials alongside practical experience and supervision. AHIMA Certified Coding Specialist. AHIMA

Also examine replacement coverage. Additional orientation may be needed when personnel change, and your implementation assumptions should account for that process.

Make Quality Part of the Business Case

Completed volume needs to be considered alongside coding quality and correction effort.

Agree on how the provider will select records for review, classify errors, calculate results, and resolve disagreements. Determine who performs corrections and how that work is priced.

Cooper Thomas’s medical coding and auditing services provide a starting point for discussing production oversight, reviews, and education.

Confirm Applicable Coding Materials

CMS publishes ICD-10 code files, guidelines, and effective-date information. The provider should explain how staff use the appropriate materials for current and historical records. CMS ICD-10 resources. CMS

For applicable Medicare work, ask how relevant National Correct Coding Initiative policies and edits enter the coding and review workflow. Medicare NCCI resources. CMS

These processes should be included in the operational assessment of the proposal.

Separate Capacity Benefits From Financial Savings

An organization may gain value through additional coverage, reduced queue age, or access to relevant specialty experience.

Describe each expected benefit and the evidence needed to assess it.

For example, temporary support may allow a department to maintain its defined workflow while recruiting. A backlog project may reduce older inventory while internal staff manage current encounters.

Record these outcomes separately from confirmed reductions in expenditure. Estimate financial effects only where your organization can support the assumptions.

This approach helps leadership understand what outsourcing medical coding services is expected to accomplish.

Examine Technology and Implementation Dependencies

The provider needs appropriate access and orientation before production begins.

Confirm how staff receive assignments, locate documentation, record questions, and complete handoffs. Test both a complete record and an encounter requiring clarification.

Cooper Thomas’s Health IT and EHR support addresses the technology and operational context surrounding healthcare information.

Assign responsibility for access approval, technical support, workflow changes, and offboarding. Include the corresponding staff effort in implementation planning.

Review Privacy and Security Arrangements

External coding personnel may need access to protected health information.

HHS explains requirements for business associate agreements, including applicable arrangements involving subcontractors. Your privacy team should review the proposed relationship before records are shared. HHS business associate guidance. HHS.gov

Ask where work occurs, whether subcontractors participate, and how information is accessed and handled.

HHS’s Security Rule summary describes safeguards for electronic protected health information. Your security team can use the relevant requirements when evaluating proposed arrangements. HHS Security Rule summary. HHS.gov

Identify any implementation requirements arising from that review.

Use a Pilot to Test the Assumptions

A defined pilot can help assess whether the proposed staffing, workflow, and reporting function as expected.

Agree on the encounter sample, duration, quality method, and acceptance criteria before work begins.

Evaluate:

  • Access and orientation readiness.
  • Completed encounters.
  • Documentation question handling.
  • Quality findings.
  • Turnaround under agreed definitions.
  • Internal coordination effort.
  • Actual charges.

Compare results with the assumptions in the proposal. Record the changes needed before expanding the assignment.

Review Actual Results Consistently

After implementation, use a recurring report that connects workload, quality, and cost.

Changes in volume, complexity, and documentation availability should be visible when interpreting performance.

Review questionEvidence to examine
Is capacity meeting demand?Incoming volume, completions, and queue age
Is the backlog decreasing?Remaining original inventory
Where is work delayed?Held records and unresolved questions
Is quality meeting expectations?Defined review results and repeat findings
Are costs consistent with the proposal?Invoices, workload, and additional charges
What internal effort remains?Coordination and review time
What action is needed?Named owners and due dates

Coordinate recurring findings with the appropriate oversight functions. The OIG’s General Compliance Program Guidance offers voluntary guidance on compliance infrastructure and related responsibilities. OIG General Compliance Program Guidance. oig.hhs.gov

Frequently Asked Questions About Outsourcing Medical Coding Services

Does outsourcing always reduce costs?

The result depends on pricing, workload, implementation, quality, and internal effort. Compare actual expenditure and operational results with the baseline.

What should we include in a cost estimate?

Include vendor charges, implementation, internal coordination, quality review, reporting, and any separately priced activities.

How do we measure a backlog project?

Track the original inventory, completed records, remaining encounters, and documentation holds. Keep new arrivals visible separately.

Should we use one productivity target for all records?

Define expectations around the assigned encounter types and complexity. Review the assumptions supporting any target.

When should we reassess the engagement?

Set a review schedule in advance and reassess when volume, specialties, staffing, systems, or scope change.

Discuss Your Coding Business Case

Prepare your encounter mix, current inventory, staffing needs, costs, and quality expectations. Identify which outcomes your organization wants to measure and which responsibilities will remain internal.

Learn more about Cooper Thomas’s healthcare focus and contact our team to discuss coding, auditing, and training requirements.