Last updated: 2026-09-26

Deciding between a healthcare BPO and in-house operations starts with what the term covers, because business process outsourcing means handing a whole non-clinical function to an outside team rather than staffing seats you still manage. The first honest move is naming what never leaves the building, since clinical care and any duty needing a person on-site stay with in-house operations no matter what the budget says. From there the practical questions stack up. Which back-office functions a healthcare BPO takes on first, what those same functions cost when an in-house team runs them, and what a BPO charges once the work moves are the three that reshape the math. Volume is the next axis, because a healthcare BPO and an in-house team scale in different ways when claim and call counts jump. Then comes the decision itself, meaning how a health organization sorts what to send out and what to keep, and when it makes sense to run a BPO alongside an in-house team rather than pick one. Governance closes the loop, since moving functions to a vendor changes how you control data and vendor risk. Where every cost figure here comes from is set out at the end.

What does healthcare BPO mean, and how does it differ from in-house operations?

Healthcare BPO, short for business process outsourcing, is the practice of handing an entire non-clinical function to an outside vendor whose team runs it. Instead of hiring, training, and supervising staff for medical billing, coding, claims processing, scheduling, call handling, data entry, or prior authorization, the organization contracts the outcome and the vendor staffs and manages it. In-house operations do the reverse, keeping those functions under the roof with employees the organization pays, trains, and directs. The line that matters is ownership. With a BPO the vendor owns the process and, in many arrangements, the result, while with in-house operations the practice owns both. Outsourcing isn't a single purchase, though. It spans firms that price per transaction or as a percentage of collections, enterprise operators that run a contracted scope for hospitals, and staffing models that place people who work inside your systems while you keep control of the work. Honest Taskers sits in that last group. It places dedicated, healthcare-trained remote professionals the practice directs day to day, which is one staffed model within the outsourcing spectrum rather than a vendor that runs the whole function itself. Naming the tier before comparing anything else keeps a solo practice from measuring itself against a vendor built for a 40-hospital system.

Which functions should never move to a healthcare BPO?

Clinical care, clinical decisions, and any task needing a person physically in the building should never move to a healthcare BPO. That boundary sits before any cost discussion, because putting price first and burying the limits is how these decisions go wrong. The following stay with in-house operations.

• Anything clinical, such as diagnosis, treatment decisions, triage judgments, and orders, which stay with licensed providers wherever they sit.
• Hands-on patient work, such as rooming, taking vitals, drawing blood, and assisting with a procedure.
• The physical front desk, such as greeting patients, collecting a cash co-pay, and handing over forms.
• Physical materials, such as paper charts, specimens, mail, and anything arriving on paper or in person.
• Anything the practice cannot govern or audit, because work you can't see is work you can't control.

That last item is the one buyers skip. A function can be non-clinical and still be a poor candidate for outsourcing if you can't monitor access, review the output, or pull the plug cleanly. Data entry into a system nobody logs is the common example. Where most of the open work sits on this list, in-house operations are the answer and the comparison is already settled, so the rest of this page matters only where a meaningful share of the work lives in software.

Which back-office functions does a healthcare BPO absorb first?

A healthcare BPO absorbs the high-volume, rules-driven back-office functions first, because those move cleanly and show results fast. The usual first wave covers medical billing and payment posting, medical coding, claims processing and denial follow-up, insurance eligibility and benefits verification, prior authorization, patient scheduling and rescheduling, inbound and outbound call handling, and data entry. Each shares one trait, which is that it lives entirely in software, follows documented rules, and creates a measurable backlog when it slips. That combination is what makes a function safe to move. Billing and coding usually go first in a revenue-focused practice, since a claims backlog carries a direct dollar cost a vendor can attack immediately. Call handling and scheduling go first where the phone is the bottleneck and patients feel the wait. Prior authorization is a common early candidate too, because it is labor-heavy, deadline-driven, and rarely staffed to volume. What all of these share is that none of them needs the building. A remote team with the right access can work the same queues your on-site staff work, on the same shift, which is why the back office is where outsourcing starts rather than the exception it has to justify.

What does running these functions with in-house operations cost?

Running these functions with in-house operations costs far more than the salary line shows, roughly $68,252 a year for a single representative back-office role once the employer load is added. US medical secretaries and administrative assistants earned a median $45,930 a year (Source: Bureau of Labor Statistics, "Occupational Employment and Wage Statistics", May 2025). The employer load on top is broken out separately in the table below so nothing gets counted twice (Source: Bureau of Labor Statistics, "Employer Costs for Employee Compensation", March 2026).

That table prices one seat, and a full in-house back office is several such roles across functions. A billing and posting clerk (SOC 43-3021, $48,500 median) runs about $72,072 all-in on the same load, so a practice keeping billing, coding, scheduling, and calls in-house is stacking several of these seats, plus the cost to fill each one and the coverage gap when any of them is out. Two costs sit outside that recurring number as well. Filling each seat carries a one-time recruiting cost that repeats on every departure, and a single administrative person is a single point of failure, so when they take leave or resign the work stops or lands on clinical staff. That stacked figure is what the outsourcing question is weighed against, not one salary line.

What does a healthcare BPO charge, and how is the fee structured?

A healthcare BPO charges in one of three ways, and the number depends on the model. Percentage-of-collections pricing is common for revenue cycle work billed as a whole function, a single-digit share of what the vendor collects each month. Per-transaction pricing attaches a set fee to each claim, chart, or call handled. Hourly pricing bills for the time worked with no employer load on top. Honest Taskers uses the hourly model at $10.00 to $12.65 an hour, billed by the hour, which at 40 hours a week runs about $20,800 to $26,312 a year and at 20 hours a week about $10,400 to $13,156. None of the employer load in the table above applies, because you're buying hours rather than employing a person. Enterprise BPO contracts, by contrast, are usually priced on request against a defined scope and rarely publish a rate. Fees vary widely by function and by vendor, so the honest move is to price your own volume against each structure rather than trust a headline number. Read the model against your own numbers, since a percentage that looks small can exceed an hourly rate at high collections, and a per-transaction fee can beat both at steady volume. For a fee-heavy function like billing, comparing published models is where a shortlist starts, and our roundup of the best medical billing outsourcing companies shows how those structures differ in practice.

Which model scales faster when claim and call volume jumps?

A healthcare BPO scales faster than in-house operations when claim and call volume jumps, because adding capacity is the vendor's job rather than yours. When a payer rule change floods the denial queue or a new location doubles inbound calls, an in-house team has to post, recruit, hire, and train before the backlog clears, and the seat sits empty for weeks while the work piles up. A BPO adds trained staff from an existing pool, often within days, and pulls them back when the surge passes. Most Honest Taskers placements complete within one to three weeks of a signed agreement, so a practice can stand up the remote half quickly rather than wait out a full hiring cycle. In-house operations scale in whole employees, so a 30% volume increase either overloads the current team or forces a full-time hire the practice may not need once the spike passes. Hourly and per-transaction models flex with the volume directly, since you pay for the surge and stop paying when it ends. The trade is control, because scaling fast through a vendor means trusting their bench and their quality at the new volume. For voice work, where volume swings hardest, our list of the best healthcare call center outsourcing companies covers who answers and how coverage is staffed.

How should a health organization decide what to send to a healthcare BPO?

A health organization should decide what to send to a healthcare BPO by sorting every function into two columns before pricing anything. In the first column go tasks needing a person on-site or a clinical license. The second column holds tasks living entirely in software that follow documented rules. Only the second column is a candidate, and then four tests run on it, in order, because each one can settle the question on its own.

• How large and rules-driven is the function? High-volume, repetitive work moves best and shows results first.
• Can you measure the outcome? A function with a clear metric, such as days in AR or call abandonment, is one you can hold a vendor to.
• Can you govern the access it needs? Where you can't scope, log, and revoke access, keep it in-house.
• Is the volume steady or spiky? Spiky work suits hourly or per-transaction pricing, while steady work may be cheaper to staff.

Two further choices sit on top of the columns. Whether to sign a single-function contract or bundle several functions with one vendor, and whether to consolidate work already scattered across multiple vendors. Bundling can lower coordination cost but raises the stakes if the vendor underperforms, and scope creep, meaning work drifting to the vendor without a matching agreement, is the risk to watch. A deadline-driven function like prior authorization is a frequent first move, and our roundup of the best prior authorization outsourcing companies shows what that market looks like.

When does a practice run a healthcare BPO alongside an in-house team?

A practice runs a healthcare BPO alongside an in-house team whenever part of the work needs the building and part of it doesn't, which is most of the time. The pattern that holds keeps in-house staff on the front desk, clinical support, and anything physical, then moves the phone, verification, billing, and follow-up queues to an outside team. That's augmentation rather than replacement, and it usually shows up first as on-site staff getting their clinical and patient-facing hours back. Nobody is displaced, and the queue simply stops landing on people hired to do something else. The split also works as a hedge during a transition, since a practice can move one function to a vendor, keep the in-house version running until the metrics hold, then decide. Running both is the honest answer, too, when volume is steady enough to justify a core in-house team but spiky enough to need surge capacity a vendor provides on demand. Where practices get this wrong is moving a whole role instead of a queue, then finding the on-site half of that role has nobody covering it. Split the work rather than the person, and keep the on-site column staffed no matter how much of the software column moves out. The signal to watch is simple, since an in-house employee spending hours a day on work that never needed the building is a loaded employee rate paid for output an hourly remote seat could deliver, while that same person stays unavailable for the on-site work only they can do. Where the split runs across several functions at once, our roundup of the best healthcare outsourcing companies maps how staffing, outsourced functions, and enterprise operators differ.

How do you govern data and vendor risk once functions move to a BPO?

You govern data and vendor risk with a signed agreement and access controls that stay under your control rather than the vendor's. The foundation is a Business Associate Agreement, which is what makes a vendor's access to protected health information HIPAA-compliant, and no credential a vendor or person can hold removes that requirement. On top of the BAA sit four practices that carry the risk day to day.

• Minimum-necessary access, scoped to exactly what the function needs and nothing more, granted in your own systems.
• Audit logging, so every action on PHI is recorded and reviewable by the practice, not just the vendor.
• Defined performance metrics and reporting, so you can see the work rather than assume it.
• Revocation on exit, so access ends the day the engagement does, cleanly and verifiably.

Vendor risk is broader than data. Continuity matters, so ask what happens when a vendor's staff member leaves and who carries replacement. Offshoring adds two more questions. Time zone, since work should run on your patients' hours rather than the vendor's, and data residency, since where PHI is processed and stored belongs in the agreement. Honest Taskers signs a BAA when a professional will access PHI, keeps access under practice control, describes its environment as SOC 2 audit ready, and staffs professionals who work the client's US time zone. Whatever the model, the rule holds the same, in that you can outsource the work but the accountability for the data stays with you.

Where do these healthcare BPO cost figures come from?

Wages come from the Bureau of Labor Statistics "Occupational Employment and Wage Statistics" program for May 2025, occupation code 43-6013, medical secretaries and administrative assistants, with billing and posting clerks under code 43-3021 for the second illustrative role. Employer load percentages come from the same agency's "Employer Costs for Employee Compensation" series for March 2026, applied as separate components so paid leave and legally required benefits aren't counted twice. Honest Taskers rates come from the company's own published rate card rather than a third-party estimate. BPO fee structures are described in general terms because they vary by function and vendor, so no single vendor fee is stated here as a fixed figure. Every wage figure is a national median, so all of them move with your local wage band, which is why the right final step is to run the same math on the wages you pay.

For a ranked view of the vendors in the enterprise BPO tier, see our list of the best healthcare BPO companies.

Talk to Honest Taskers about which functions can move and which stay in-house.