A coding proposal is easier to evaluate when the request behind it is specific.
“Provide coding support” leaves room for different interpretations. One vendor may include routine quality reviews and management meetings. Another may price production coding alone. Both proposals can appear responsive while covering different work.
When you outsource medical coding services, a clear request for proposals helps establish what your organization needs, what providers must explain, and how the responses will be compared.
Hospitals, physician groups, and public healthcare organizations can use the following framework to prepare a focused request and move toward an agreement with defined responsibilities.
Explore Cooper Thomas’s healthcare services when considering coding support alongside health information management and technology requirements.
What Does It Mean to Outsource Medical Coding Services?
Outsourcing medical coding services means assigning defined coding work to an external provider.
The engagement may cover inpatient facility coding, outpatient encounters, professional services, selected specialties, or a backlog. It may also include audits, reporting, and education when those activities are specified.
The request for proposals, often called an RFP, should explain both the assignment and its operational context. Providers need to understand the records, systems, documentation workflow, and expected deliverables before proposing staffing or pricing.
For a broader explanation of service models, read our medical coding outsourcing guide.
1. Describe the Problem You Want the Engagement to Address
Begin with the operational need.
A backlog project requires a different plan from continuing support for a growing service line. Temporary coverage during recruitment also needs different assumptions from a long-term assignment.
Explain what prompted the request and what your organization will measure.
Examples include:
- Reducing a defined inventory of older encounters.
- Maintaining coverage during vacancies.
- Adding capacity for selected departments.
- Supporting a specialty with recurring delays.
- Reviewing coding quality across several locations.
Use available baseline information. Include current queue age, encounter volume, held records, and relevant quality findings.
These details give providers a basis for developing a practical response.
2. Define the Records and Tasks Included
Describe the scope in enough detail for providers to estimate the work consistently.
| RFP component | Information to include |
|---|---|
| Care settings | Inpatient facility, outpatient facility, professional services, or a defined combination |
| Specialties | Clinical areas included in the assignment |
| Locations | Facilities, departments, or practice sites |
| Volume | Expected monthly encounters and fluctuations |
| Backlog | Starting inventory, dates, and record status |
| Coding tasks | Assignments, reviews, edits, and corrections included |
| Exclusions | Responsibilities retained by internal teams |
| Completion | Conditions that must be met before work is finalized |
If the assignment combines production coding and auditing, describe each component separately.
When you outsource medical coding services, clear boundaries help prevent unfinished records from moving between teams without an owner.
3. Request a Staffing Plan for Your Assignment
Ask providers to identify how they will staff the work.
Request relevant experience, qualifications, supervision, and replacement coverage. Determine whether subcontractors will participate and where assigned personnel will work.
AHIMA describes its Certified Coding Specialist credential as demonstrating coding proficiency and skills in data quality and accuracy. Credentials can support your assessment alongside practical experience and readiness for the assigned records. AHIMA Certified Coding Specialist. AHIMA
Ask each provider to explain:
- How staff are selected.
- How specialty experience is verified.
- How readiness is assessed before production.
- Who reviews complex cases.
- How staff changes are communicated.
- How replacement personnel receive orientation.
Evaluate the proposed delivery team as well as the company’s broader experience.
4. Specify Coding References and Update Responsibilities
The RFP should require providers to explain how they identify and apply relevant coding updates.
CMS publishes ICD-10 code files, guidelines, and effective-date information. Ask how the provider uses the appropriate materials for both current and historical records. CMS ICD-10 resources. CMS
For applicable Medicare services, ask how National Correct Coding Initiative policies and edits enter the coding and review workflow. Medicare NCCI resources. CMS
Request the process for communicating changes, preparing staff, and checking implementation.
Also identify how your organization will share approved local procedures and clarify conflicts or questions.
5. Require an Explainable Quality Method
A quoted accuracy target needs supporting detail.
Ask providers to define what they measure, how they select records, and how they calculate results.
For example, encounter-based accuracy and code-level accuracy can produce different figures. The response should make the methodology understandable.
Request a quality plan covering:
- Review frequency.
- Sampling approach.
- Coding elements assessed.
- Error definitions.
- Scoring calculations.
- Reviewer qualifications.
- Disagreement resolution.
- Corrective action and follow-up.
Ask for a sample report showing how a finding connects to documentation and the reviewer’s rationale.
Cooper Thomas’s medical coding and auditing services provide a starting point for discussing production oversight, reviews, and education.
6. Define Turnaround and Documentation Holds
Turnaround commitments should use the same definitions across proposals.
Specify when measurement begins, what counts as completion, and how incomplete records are handled.
Consider an encounter that lacks a signed report. The coding provider identifies the issue promptly, but the document becomes available several days later. Your reporting requirements should make that delay visible and identify who owns the next action.
Require providers to explain:
- How documentation concerns are recorded.
- Who receives questions.
- Who monitors unresolved items.
- When escalation occurs.
- How records return to coding.
- How held encounters affect reporting and pricing.
A sample exception workflow can reveal more than a general turnaround promise.
7. Document Technology and Access Requirements
Identify the EHR, encoder, work queues, and other systems involved.
Ask each provider to describe its access needs, orientation requirements, and implementation dependencies.
The response should explain how staff will locate documentation, identify amendments, record questions, and mark encounters complete.
Cooper Thomas’s Health IT and EHR support addresses the technology and operational context surrounding healthcare information.
Include a workflow demonstration or testing milestone in the implementation plan. Test both a complete encounter and one requiring clarification.
8. Request Privacy and Security Information
Before records are shared, involve your privacy and security teams in reviewing the proposed relationship.
HHS explains requirements for business associate agreements, including applicable arrangements involving subcontractors. Request the information your organization needs to evaluate those responsibilities. HHS business associate guidance. HHS.gov
Ask about work locations, subcontractor involvement, approved access methods, incident reporting, and information handling.
HHS’s Security Rule summary describes safeguards for electronic protected health information. Your security team can use the relevant requirements when evaluating proposed access and operational arrangements. HHS Security Rule summary. HHS.gov
Specify who approves access, reviews permissions, and removes access when staff leave the assignment.
9. Use a Consistent Pricing Response Format
When you outsource medical coding services, compare proposals using the same workload assumptions.
Ask providers to complete a pricing table that identifies included activities and additional charges.
| Pricing category | Required explanation |
|---|---|
| Implementation | Orientation, access preparation, and workflow testing |
| Production | Billing unit and workload assumptions |
| Quality review | Included reviews and separately priced audits |
| Incomplete records | Treatment of held or unresolved encounters |
| Reporting | Included reports and management meetings |
| Education | Training and follow-up review charges |
| Volume changes | Pricing when workload increases or decreases |
| Transition | Responsibilities and costs at engagement end |
Request an estimate for a representative month. For backlog projects, request a separate estimate tied to the starting inventory and completion criteria.
Account for internal coordination time when reviewing the overall cost.
10. Establish Reporting and Oversight
Define the information managers need to assess performance.
Request reports showing completed encounters, inventory by age, held records by reason, turnaround, quality findings, and open corrective actions.
Specify the reporting frequency and meeting schedule. Identify who will explain results and who can approve changes.
Coordinate recurring findings with the appropriate internal oversight functions. The OIG’s General Compliance Program Guidance offers voluntary guidance on compliance infrastructure and related oversight. OIG General Compliance Program Guidance. oig.hhs.gov
How to Evaluate the Responses
Agree on evaluation criteria before reviewing final proposals.
Compare relevant staffing, workflow, quality methods, implementation, reporting, privacy arrangements, and cost.
Record unanswered questions separately. A proposal can perform well in several areas while leaving an essential requirement unresolved.
A limited pilot may help assess readiness. Define the sample, duration, review method, and acceptance criteria before work begins.
Frequently Asked Questions
Do we need a formal RFP to outsource medical coding services?
The process depends on your organization’s procurement requirements and engagement size. A written scope and consistent proposal questions remain helpful for comparing responses.
What volume information should we provide?
Share available encounter counts, workload fluctuations, backlog age, and complexity information. Explain any limitations in the estimates.
Should auditing be included?
Specify routine production quality checks and any broader audits separately. Define the method and deliverables for each.
Can the engagement start with one department?
Yes. A defined queue or service line can form an initial assignment. Establish ownership, readiness criteria, and reporting.
What should the exit plan address?
Include unfinished encounters, unresolved questions, reports, information handling, access removal, and handoff responsibilities.
Prepare a Coding Request That Providers Can Answer
Bring your encounter types, estimated volume, outstanding inventory, systems, and quality expectations into the proposal process. Identify the exceptions that create the most work for your internal team.
Learn more about Cooper Thomas’s healthcare focus and contact our team to discuss coding, auditing, and training requirements.