Providers and payers in US healthcare
Almost every healthcare IT project sits somewhere between the people who deliver care (providers) and the organisations that pay for it (payers). Understanding who they are, how money and data flow between them, and who the stakeholders are on each side is the foundation for scoping, planning and running healthcare projects well.
Providers deliver care
They diagnose, treat and document care, then bill for it. Their priorities: patient safety, clinician time, throughput and getting paid accurately and fast.
Payers finance care
They enrol members, decide what's covered, authorise services, process claims and pay providers. Their priorities: cost control, accurate payment, member experience and regulatory compliance.
Types of providers
Hospitals & health systems
Inpatient, emergency and surgical care; often own clinics, labs and imaging. Big EHR and revenue-cycle programmes.
Physician practices & medical groups
Primary and specialty care in clinics; smaller IT teams, often reliant on vendors.
Ambulatory surgery & urgent care
Outpatient procedures and walk-in care; fast throughput, tight scheduling.
Post-acute & long-term care
Skilled nursing, rehab, home health and hospice; heavy Medicare dependence.
Ancillary providers
Labs, imaging centres, pharmacies, durable medical equipment suppliers.
Behavioural health & FQHCs
Mental health, substance use and community health centres; extra privacy rules (e.g. 42 CFR Part 2) and grant reporting.
Types of payers
Commercial insurers
Private health plans sold to employers and individuals (e.g. via the ACA marketplace).
Self-funded employer plans
Employers carry the risk and hire a third-party administrator (TPA) to process claims.
Medicare (CMS)
Federal programme for people 65+ and some disabled people; Parts A, B and D, plus Medicare Advantage (Part C) run by private plans.
Medicaid & CHIP
Joint federal–state programmes for low-income people and children; often run through managed care organisations.
Military & veterans
TRICARE and the VA, with their own rules and systems.
Patients (self-pay)
Uninsured patients and anyone paying deductibles, copays and coinsurance.
Provider and payer workflow
The revenue cycle runs from the moment a patient books an appointment to the moment the last dollar is collected. Here is how the two sides hand work back and forth.
The electronic transactions behind the workflow
HIPAA requires standard electronic formats (X12) for these exchanges. Knowing the names helps you talk to revenue-cycle and integration teams.
| Step | Transaction | Question it answers |
|---|---|---|
| Eligibility check | 270 / 271 | Is the patient covered, and what do they owe? |
| Prior authorisation | 278 (and FHIR prior-auth APIs) | Will the payer cover this service in advance? |
| Claim submission | 837P / 837I | Professional or institutional bill for services provided. |
| Claim status | 276 / 277 | Where is my claim in processing? |
| Payment & remittance | 835 | What was paid, adjusted or denied, and why. |
Stakeholders on each side
Provider
- Physicians & nursesEnd users of the EHR; their time and workflow drive adoption.
- CMIO / CNIOClinical informatics leaders who translate between clinicians and IT.
- Revenue cycle (patient access, coding, billing)Register patients, verify eligibility, code and submit claims, work denials.
- CIO, IT & security teamsOwn systems, integrations, infrastructure and HIPAA safeguards.
- Compliance & privacy officersApprove PHI use and regulatory evidence.
- CFO & managed-care contractingNegotiate payer contracts and rates; care about cash flow and denial rates.
Payer
- Member servicesHandle enrolment, ID cards and member questions.
- Utilisation management (UM) nurses & medical directorsReview prior authorisations and medical necessity.
- Claims operationsAdjudicate claims, apply benefits and pricing, issue payments and remittances.
- Provider network & contractingRecruit providers, negotiate rates, maintain provider directories.
- Actuarial & financeSet premiums and manage medical-cost risk.
- Payment integrity & complianceDetect fraud, waste and abuse; meet CMS and state reporting.
Shared / external
- Patients / membersThe same person is a 'patient' to the provider and a 'member' to the payer.
- Employers & brokersChoose and fund plans for employees.
- ClearinghousesRoute and validate electronic transactions between providers and payers.
- Regulators (CMS, state agencies, OCR)Set rules on coverage, interoperability, privacy and payment.
- Technology vendorsEHR, practice management, claims and analytics platforms.
Where they pull in different directions
- Prior authorisation: payers use it to control cost; providers see it as delay and admin burden.
- Denials: payers deny claims that don't meet rules; providers spend significant effort reworking and appealing them.
- Contract rates: each side negotiates hard, and rates drive how much a provider is paid for the same service.
- Data sharing: both are now pushed by federal interoperability rules to exchange data through APIs — a big source of healthcare IT projects.
What this means for healthcare IT project managers
- Map which side of the workflow your project touches — a change to registration or coding ripples into claims and cash.
- Involve revenue cycle early on any EHR or scheduling project; bad front-end data is the top cause of denials.
- Plan clearinghouse and payer testing windows — payers set their own timelines for enrolment and transaction testing.
- Track payer-driven regulation (e.g. CMS interoperability and prior authorisation rules) as fixed deadlines on your schedule.
- Measure success in shared terms: clean-claim rate, denial rate, days in accounts receivable, prior-auth turnaround.
- Remember both sides handle PHI — BAAs, minimum-necessary access and audit trails apply to every integration.
Frequently asked questions
What is the difference between a provider and a payer?
A provider delivers care — hospitals, doctors, clinics, labs. A payer finances care — insurers, Medicare, Medicaid and self-funded employers. Providers bill payers; payers decide what is covered and pay according to contracts and benefits.
What is a payvider?
An organisation that is both a provider and a payer, such as an integrated health system that also runs its own health plan. They share data across both sides, which can simplify some workflows.
What is a clearinghouse in US healthcare?
A company that receives electronic claims and other transactions from providers, checks them for errors, converts formats if needed and forwards them to the right payer.
Why do claims get denied?
Common reasons are wrong patient or insurance details, missing prior authorisation, coding errors, services not covered, and late filing. Many denials start with errors at registration.