How to Compare Payer Administration Vendors

Vendors selling payer-facing administration describe themselves in different vocabularies: staffing, outsourcing, software, managed service. Nine questions, put to each of them in the same words, cut through the vocabulary.

Start with the work, not the vendor category

Before comparing vendors, write down the work: which workflows, for which payers, at what monthly volume, in which systems, and what finished looks like for each. Then notice that the market offers three broadly different things. One vendor places a person with you and you direct the work. Another takes the work into its own process and system and returns results. A third performs a defined scope inside your systems and is accountable for the scope. Each answers the questions below differently, and the differences are the comparison.

Nine questions

Ask each vendor the same nine questions and ask for the answers in writing.

• What exactly is in scope, and what is excluded? Services, payers, volumes, the definition of a case, and the exclusions: appeals, projects, complex cases, clinical questions, and work outside the written scope.
• Where is the work performed, and in whose systems? Inside your practice-management system, electronic health record, and payer portals, or in the vendor’s own system. Where the record of each action lives, and whether patient information is copied outside your systems to do the work.
• How is access granted, controlled, and revoked? The security rules require authorization and supervision of the people who work with electronic protected health information, confirmation that each person’s access is appropriate, documented establishment, review, and modification of access, and termination of access when the arrangement ends, with access limited to the minimum necessary. Ask who provisions the accounts and who can revoke them.
• Is there a business associate agreement, and what does it cover? The rules require one before protected health information is disclosed, with defined contents: permitted uses, safeguards, breach reporting, flow-down to subcontractors, return or destruction at termination, and your right to terminate for a material violation. Ask to see it before onboarding, not after.
• Who performs the work, where are they, and are they dedicated? Employees or subcontractors, in the United States or elsewhere, assigned to your practice or drawn from a pool, trained on your payers and systems, and backed up when absent. Subcontractors carry the same contract obligations, so ask how they are met.
• Who is accountable for the outcome of the process? Under a seat model you supervise and you own the result. Under a managed scope the vendor is accountable for delivering the scope. Under any model, payer decisions belong to the payer.
• What is reported, how often, and at what level? Case status, last payer action, next follow-up, deadlines, determinations, unresolved issues and escalations, and recurring barriers by payer and service; whether the report is aggregate or contains patient information; and how often it arrives.
• Where are the clinical boundaries? Medical-necessity determinations, clinical answers to payer questions, the peer-to-peer discussion itself, attestations, and coding decisions stay with the practice and its clinicians. Ask how the vendor routes those questions and how quickly.
• How does it end? Notice periods, transition of open cases, return or destruction of protected health information, and termination of access. A vendor that has a clear answer has thought about the whole engagement.

Reading claims and promises

Vendors can commit to what they control: completeness of submissions, follow-up cadence, documentation, escalation, and reporting. They cannot control the payer. For the payers covered by the federal interoperability and prior authorization rule, decisions are due within 72 hours for expedited requests and seven calendar days for standard requests beginning January 1, 2026, with a specific reason required for a denial; other plans follow their own timeframes and state law. When a vendor quotes an approval rate or a turnaround, ask how it is defined, what the denominator is, whether it is measured across clients like yours, and what the agreement says when the payer is the cause of delay.

The pricing model is a signal

How a vendor prices tells you what it thinks it is selling. A price per case sells transactions. A price per seat sells time, and leaves supervision, training, coverage, and the follow-up tail with you unless the agreement says otherwise. A flat monthly price sells capacity within a band. A share of recovery sells a project. A managed scope sells accountability for a defined body of work. None is wrong; each should match the work you wrote down at the start, and each should arrive as a written scope rather than a rate card.

A comparison sheet

One row per vendor, one column per item, filled in from written answers rather than from a sales conversation.

• Scope and exclusions
• Systems in which the work is performed, and where the record lives
• Access provisioning, review, and revocation
• Business associate agreement provided before onboarding
• Workforce: employees or subcontractors, location, dedicated or pooled, backup
• Accountability: seat, vendor process, or managed scope
• Reporting: content, level, frequency
• Clinical routing and boundaries
• Exit and transition terms
• Pricing model and what it includes

What this is not

A comparison sheet does not choose for you. It makes sure that when two quotes look different, the difference is in what is being bought and not in what was left unsaid.

Ellery Health Partners is a managed payer-administration service: work is performed inside the practice’s authorized systems by a U.S.-based team under a written scope, with practice-controlled access, a business associate agreement before any access to protected health information, aggregate reporting, and clinical decisions retained by the practice and its clinicians.

Related services

• Prior Authorization
• Credentialing & Payer Enrollment
• Denials & Appeals
• Claims & A/R Administration

Sources

• 45 CFR § 164.308, Administrative safeguards, via Cornell Legal Information Institute. Workforce security and information access management require procedures for authorizing and supervising workforce members who work with electronic protected health information, confirming that access is appropriate, establishing, documenting, reviewing, and modifying each user’s right of access, and terminating access when the arrangement ends; a covered entity must obtain satisfactory assurances from a business associate through a written contract.
• 45 CFR § 164.502, Uses and disclosures of protected health information: general rules, via Cornell Legal Information Institute. Disclosure to a business associate requires satisfactory assurance documented in a written contract; a covered entity or business associate must limit protected health information to the minimum necessary for the purpose.
• 45 CFR § 164.504(e), Business associate contracts, via Cornell Legal Information Institute. The contract must establish permitted uses and disclosures, safeguards, reporting of breaches, flow-down to subcontractors, return or destruction of protected health information at termination, and the covered entity’s right to terminate for a material violation.
• CMS, CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) fact sheet. Beginning January 1, 2026, impacted payers must send prior authorization decisions within 72 hours for expedited requests and seven calendar days for standard requests, and must provide a specific reason for denials.

Sources are cited for the substantive factual statements above. Payer-specific rules vary by plan, product, contract, and state.

Last updated September 2026. Educational reference, not legal or clinical advice.