DOFR questions, answered.

DOFR stands for Division of Financial Responsibility. It is a contractual exhibit that defines which organization is financially responsible for each category of healthcare services within a delegated risk arrangement. The term is used both to refer to the document itself ("check the DOFR") and to the concept of financial responsibility allocation ("that's a DOFR issue").

A Division of Financial Responsibility (DOFR) is a contractual matrix that assigns financial responsibility for defined categories of healthcare services among the organizations participating in a delegated-risk arrangement.

A DOFR is commonly attached to a delegation agreement between a health plan and a medical group, independent practice association (IPA), or another risk-bearing entity. For each service category, it identifies which party is financially responsible. Depending on the contract, responsibility may be assigned to:

• The medical group or IPA under capitation
• The health plan as plan risk
• A specialty organization through a carve-out or other delegated arrangement

Common DOFR categories include inpatient and outpatient facility services, professional services, emergency care, behavioral health, pharmacy, injectable medications, durable medical equipment, skilled nursing, home health, and transportation. The categories and assignments are contract-specific; no organization should assume that one payer’s DOFR applies to another payer or agreement.

Operationally, the signed DOFR must be translated into rules within a claims-adjudication system. Those rules may consider procedure codes, revenue codes, place of service, provider type, dates of service, exceptions, amendments, and payer-issued crosswalks. If the system configuration does not match the governing contract, a claim may process successfully while assigning its cost to the wrong organization.

A DOFR is therefore more than a contract exhibit. It is the operational source of truth for determining who should pay for covered services under a delegated-risk arrangement.

Sources:

• Centers for Medicare & Medicaid Services, “Risk-Based Arrangements in Health Care”: https://www.cms.gov/priorities/innovation/key-concepts/risk-based-arrangements-health-care
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 17, 2026

This material is educational and describes common industry practices. Financial responsibility ultimately depends on the governing contract, amendments, applicable regulations, and current system configuration.

Delegated risk in healthcare is a contractual arrangement in which a health plan transfers financial and operational responsibility for defined healthcare services to another organization, commonly a medical group, independent practice association (IPA), or risk-bearing organization (RBO).

The delegated organization typically receives a fixed payment, often a per-member-per-month capitated payment, to manage and pay for the services assigned to it. Depending on the agreement, delegated responsibilities may include:

• Paying claims for defined service categories
• Managing provider networks
• Performing utilization management
• Coordinating patient care
• Meeting quality and reporting requirements
• Managing the financial performance of a defined member population

Delegated risk does not mean that the health plan transfers responsibility for every healthcare service. Some services may remain the financial responsibility of the health plan, while others may be carved out to specialty organizations such as pharmacy benefit managers, behavioral health organizations, dental plans, or vision plans.

The Division of Financial Responsibility (DOFR) defines these boundaries. It identifies which services are the responsibility of the delegated organization, which remain plan risk, and which are assigned to another party.

For example, a medical group may receive capitation for professional services while the health plan retains responsibility for inpatient facility services and a separate vendor manages behavioral health. The specific allocation depends on the governing contract and DOFR.

Delegated risk is related to, but not identical to, value-based care. Value-based care is a broad approach that emphasizes quality, patient outcomes, coordination, and cost. Delegated risk is one financial and operational structure that may be used to support those goals.

Accurate delegated-risk administration requires the governing contracts, DOFRs, amendments, benefit grids, crosswalks, and claims-system configuration to agree. If they do not, a claim may process successfully while assigning its cost to the wrong organization.

Sources:

• Centers for Medicare & Medicaid Services, “Risk-Based Arrangements in Health Care”: https://www.cms.gov/priorities/innovation/key-concepts/risk-based-arrangements-health-care
• California Department of Managed Health Care, “Risk Bearing Organization Frequently Asked Questions”: https://www.dmhc.ca.gov/LicensingReporting/RiskBearingOrganizations/RBOFrequentlyAskedQuestions.aspx
• California Department of Managed Health Care, “Useful Terms”: https://www.dmhc.ca.gov/HealthCareinCalifornia/UsefulTerms.aspx

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

This material is educational and describes common industry practices. Delegated responsibilities and financial risk ultimately depend on the governing contract, DOFR, amendments, applicable regulations, and current system configuration.

DOFRs are used by health plans, independent practice associations (IPAs), medical groups, and management services organizations (MSOs) that participate in delegated risk arrangements. The people who work with DOFRs most directly include claims examiners who configure responsibility rules in claims systems, finance directors who reconcile capitated payments, operations leaders who manage payer relationships, and delegation oversight teams at health plans. Hospital CFOs and revenue cycle teams are also affected when DOFR disputes cause payment delays.

Value-based care is an approach to healthcare delivery and payment that emphasizes quality, patient outcomes, care coordination, provider performance, and responsible management of healthcare costs rather than rewarding only the volume of services delivered.

Value-based care can take many forms. Examples include:

• Quality incentive programs
• Shared-savings arrangements
• Bundled payments
• Accountable care organizations
• Population-based payments
• Capitated and other risk-based arrangements
• Models containing upside and downside financial risk

Delegated risk is one structure that may be used within value-based care. In a delegated-risk arrangement, a health plan transfers responsibility for defined services to a medical group, IPA, or other risk-bearing organization. The delegated organization may receive a capitated payment and become financially responsible for managing the cost and delivery of the services assigned to it.

Not every value-based care arrangement involves delegated risk, and not every risk arrangement delegates the same responsibilities. Some models reward quality without transferring responsibility for paying claims. Others place organizations at financial risk for the total cost of care or for specific categories of services.

When financial responsibility is delegated, the Division of Financial Responsibility (DOFR) provides the contractual boundary between the participating organizations. It identifies which services are:

• The responsibility of the medical group or IPA
• Retained by the health plan as plan risk
• Assigned to a specialty vendor through a carve-out
• Subject to shared-risk, split-capitation, or exception provisions

This allocation matters because the financial incentives of value-based care can work only when each organization knows which services and costs it is responsible for managing.

If a DOFR assigns responsibility correctly but the claims system is configured differently, the intended value-based care arrangement can break down operationally. The wrong organization may pay a claim, risk-pool performance may be distorted, reconciliation may become unreliable, and leaders may make decisions using inaccurate financial information.

DOFR accuracy does not create value-based care by itself. It provides part of the financial and operational infrastructure required to administer certain delegated and capitated value-based care arrangements as intended.

Sources:

• Centers for Medicare & Medicaid Services, “Value-Based Care”: https://www.cms.gov/priorities/innovation/key-concepts/value-based-care
• Centers for Medicare & Medicaid Services, “Risk-Based Arrangements in Health Care”: https://www.cms.gov/priorities/innovation/key-concepts/risk-based-arrangements-health-care
• Centers for Medicare & Medicaid Services, “Value-Based Programs”: https://www.cms.gov/Medicare/Quality/Value-Based-Programs
• California Department of Managed Health Care, “Risk Bearing Organization Frequently Asked Questions”: https://www.dmhc.ca.gov/LicensingReporting/RiskBearingOrganizations/RBOFrequentlyAskedQuestions.aspx

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

This material is educational. Value-based care and delegated-risk arrangements vary by program, payer, contract, jurisdiction, and organizational structure.

A DOFR is typically attached as an exhibit, schedule, or appendix to a delegation agreement, provider participation agreement, or other contract governing delegated financial risk between a health plan and a medical group or IPA. The title and exhibit number vary by contract. The underlying agreement defines the authority and responsibilities being delegated, while the DOFR provides the detailed service-by-service allocation of financial responsibility. Other downstream contracts may reference or be affected by these assignments, even when the DOFR itself is not attached to them.

The three-way model describes how financial responsibility is divided among three parties, not two. The first party is the medical group or IPA, which bears financial risk for capitated services and receives a per-member-per-month (PMPM) payment to cover those costs. The second party is the health plan, which retains financial responsibility for plan-risk services it chose not to delegate. The third party is a specialty vendor, such as a pharmacy benefit manager or managed behavioral health organization, which manages carved-out services removed from the group's capitation. Each service category in the DOFR matrix is assigned to one of these three.

Capitated responsibility means the medical group or IPA bears financial risk for a category of services. The health plan pays the group a fixed per-member-per-month (PMPM) amount, and the group is responsible for covering the cost of those services from that payment. If actual costs come in below the capitation amount, the group keeps the surplus. If costs exceed capitation, the group absorbs the loss. Common capitated services include primary care visits, specialist office visits, and outpatient facility services. The specific services assigned to capitation vary by payer contract.

Plan risk means the health plan retains financial responsibility for a service category rather than delegating it to the medical group. The plan pays claims for those services directly. Plan risk is not the same as a carve-out. No third party is involved. The plan simply chose not to transfer financial responsibility for certain services. Common plan-risk categories include out-of-area emergency services, certain high-cost procedures, and transplant services. When a service is classified as plan risk, the medical group's PMPM capitation rate does not include the expected cost of those services.

A carve-out is a service category that has been removed from the medical group's capitation and assigned to a separate specialty vendor. The vendor manages those services under its own payment arrangement. Common carve-outs include behavioral health (managed by organizations like MHN or Beacon Health), pharmacy benefits (managed by PBMs like CVS Caremark or Express Scripts), dental (Delta Dental), and vision (VSP). When a service is carved out, the medical group's PMPM capitation rate decreases to reflect the reduced scope of risk the group is covering.

A DOFR matrix is the detailed table within the DOFR exhibit that maps every service category to a financially responsible party. Rows represent service categories such as inpatient hospital, outpatient facility, physician office visits, behavioral health, pharmacy, DME, SNF, emergency, and injectable medications. Columns represent the responsible parties. A basic matrix has three columns for the medical group, the health plan, and carved-out vendors. More complex arrangements may include additional columns for split capitation, subcapitation to specialty groups, or multiple carve-out vendors.

DOFRs and their supporting code mappings may be updated on different schedules. Contractual DOFR exhibits are commonly revised during renewals, amendments, benefit changes, or changes in delegated scope. Supporting crosswalks—especially those involving injectable medications, new HCPCS codes, biologics, and biosimilars—may be issued quarterly. Each update should be evaluated to determine whether corresponding claims-system configuration or capitation changes are required.

A DOFR crosswalk is a mapping document published by a health plan that links specific procedure codes, drug codes, or service codes to DOFR service categories. The most common example is the Injectable Medication HCPCS/DOFR Crosswalk, which maps HCPCS J-codes for injectable drugs to the appropriate DOFR category. When a new biologic or biosimilar launches, the crosswalk determines which party bears financial responsibility for that drug. Crosswalks are updated quarterly and require corresponding configuration changes in the claims adjudication system.

Crosswalk update frequency varies by payer and service category. When a payer issues a new or revised crosswalk, the affected code mappings should be reviewed against the DOFR and reflected in the claims adjudication system.

A Division of Financial Responsibility (DOFR) begins as contractual language. To use it during claims adjudication, an organization must translate that language into structured rules that its claims-administration system can apply consistently.

The implementation process commonly includes five stages:

1. Identify the governing documents

The organization identifies the signed DOFR, delegation agreement, amendments, effective dates, service definitions, exception tables, and applicable payer-issued crosswalks. These materials must be evaluated together because an amendment or exception may override the general DOFR matrix.

2. Translate service categories into claim-level logic

A DOFR may assign responsibility using broad categories such as outpatient facility services, injectable medications, durable medical equipment, or emergency care. Claims systems operate on more detailed data.

Depending on the contract and platform, configuration logic may consider:

• CPT and HCPCS codes
• Revenue codes
• Place of service
• Provider type or specialty
• Diagnosis codes
• Bill type
• Member product or benefit plan
• Network status
• Dates of service
• Contract-specific exceptions

Not every DOFR uses every data element. The governing agreement determines which distinctions are relevant.

3. Configure financial-responsibility rules

The translated logic is implemented in the organization’s claims-adjudication or core administration platform. The exact method varies by system. Responsibility may be represented through a dedicated DOFR function, benefit configuration, service-category mappings, contract rules, custom tables, or a combination of components.

The important outcome is that each applicable claim can be evaluated against the correct contract version and assigned to the appropriate financially responsible party.

4. Test the configuration

Before implementation, organizations should test representative claims across routine, high-cost, ambiguous, and exception-based scenarios.

Testing should confirm that:

• The correct contract and effective date are applied
• Services map to the intended DOFR category
• Exceptions override general rules when required
• Carve-outs route to the appropriate party
• Contract amendments produce the expected result
• Claims at category boundaries are handled consistently

Testing should include negative and edge cases—not only straightforward claims expected to pass.

5. Govern ongoing changes

DOFR configuration is not a one-time task. Contract amendments, annual code changes, quarterly HCPCS updates, new drugs, revised crosswalks, benefit changes, and system migrations can cause the configured rules to diverge from current contractual terms.

Each change should have a documented owner, effective date, approval, test evidence, and production-validation process. Organizations should also periodically compare current contracts with current system rules to identify configuration drift.

A claims system can apply its configured logic consistently while still producing the wrong financial outcome if that logic no longer reflects the governing contract. Accurate DOFR administration therefore requires both correct initial translation and disciplined change control.

Sources:

• California Department of Managed Health Care, “Claims Technical Assistance Guidance,” January 2026: https://www.dmhc.ca.gov/Portals/0/Docs/OFR/Claims%20TAG_Accessible%20January%202026%20-%20Accessible.pdf
• Centers for Medicare & Medicaid Services, “HCPCS Quarterly Update”: https://www.cms.gov/medicare/coding-billing/healthcare-common-procedure-system/quarterly-update
• Centers for Medicare & Medicaid Services, “Place of Service Codes”: https://www.cms.gov/medicare/coding-billing/place-of-service-codes
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 17, 2026

The implementation details described here represent common operational practices. Actual configuration depends on the governing contract, applicable requirements, organizational policies, and claims-administration platform.

DOFR responsibility rules may be implemented in claims adjudication and core administration platforms including QNXT, Facets, HealthEdge, EZ-CAP, and other payer or delegated-entity systems. QNXT offers a dedicated DOFR Module designed to configure contractual responsibility relationships and apply them during claims adjudication. In other platforms, DOFR logic may be implemented through benefit configuration, provider contract rules, service-category mappings, custom tables, or related adjudication logic. The implementation varies by organization, but the operational challenge is consistent: translating a signed contractual exhibit into accurate, maintainable system rules.

The most common service categories found in DOFR matrices include inpatient hospital services, outpatient facility services, physician office visits (primary care and specialty), emergency services, behavioral health, pharmacy (retail and specialty), injectable medications, infusion therapy, chemotherapy, diagnostic testing, laboratory services, radiology and imaging, durable medical equipment (DME), skilled nursing facility (SNF), home health, ambulance and transportation, and rehabilitation services. The exact categories and their boundaries vary by contract.

Provider abrasion is the friction that providers experience when DOFR responsibility is assigned incorrectly. When a medical group or IPA bears costs it should not be covering, or when payment is delayed due to responsibility disputes between the plan and the group, the downstream providers in the group's network feel the impact through delayed payments, disputed claims, and administrative burden. Reducing DOFR configuration errors reduces provider abrasion by ensuring that financial responsibility is assigned correctly at the point of claims adjudication.

In a traditional fee-for-service arrangement, providers are generally reimbursed for individual covered services based on submitted claims, contracted rates, and applicable benefit rules. In a delegated risk arrangement, a health plan transfers financial responsibility for defined categories of services to a medical group or IPA, commonly through a per-member-per-month capitated payment. The group then bears financial risk for the services assigned to it. The DOFR defines which services are included in that delegated responsibility and which remain the responsibility of the health plan or another entity.

DOFRs matter more now because delegated and value-based payment arrangements continue to expand, while the operational environment supporting them is becoming more complex. Organizations may manage dozens of payer relationships, each with different responsibility assignments, carve-outs, amendments, crosswalks, and configuration rules. At the same time, experienced claims examiners and delegated-risk specialists are retiring or changing roles, taking institutional knowledge with them. The combination of greater contractual complexity, frequent code changes, and limited specialized expertise makes accurate DOFR interpretation and configuration increasingly important.

The financial impact depends on the scope of the error, the volume and cost of affected claims, the number of members involved, and how long the error persists before detection. Because DOFR errors often do not generate denials or other operational alerts, they can compound for months before being discovered through reconciliation or contract review. A single incorrectly mapped service category may affect hundreds or thousands of claims. A capitation mismatch of only a few dollars per member per month can also create substantial annual exposure across a large membership population.

The DOFR Resource Center at gabeo.ai/dofr provides practitioner-level articles, original benchmark research, and educational content on DOFRs and delegated risk operations. Key starting points include "What Is a DOFR? The Complete Guide to Division of Financial Responsibility" for a comprehensive overview, and "Why DOFR Errors Don't Generate Denials" for a deep dive into the invisible failure mode. The DOFR Benchmark Report series publishes original research on DOFR configuration accuracy across the industry.

A Division of Financial Responsibility (commonly referred to as a DOFR) affects how healthcare claims are routed, adjudicated, paid, and reconciled under a delegated-risk arrangement.

The DOFR identifies which organization is financially responsible for each category of service. The responsible party may be the health plan, a medical group or independent practice association (IPA), or another delegated organization such as a specialty vendor.

When a claim is received, the claims-adjudication system applies configured responsibility rules based on information that may include:

• The member and health plan
• The applicable contract and effective date
• The provider and place of service
• Procedure, revenue, and diagnosis codes
• Service-category definitions
• Carve-outs, exceptions, and contract amendments
• Payer-issued code or drug crosswalks

If the contract and system configuration agree, the claim can be assigned to the appropriate financially responsible party.

If they do not agree, the claim may still process without generating a denial or obvious error. The wrong organization may absorb the cost, payment may be delayed, or the parties may need to investigate and reconcile the discrepancy after adjudication.

For providers, inaccurate responsibility assignment can contribute to payment delays, avoidable administrative work, and disputes between organizations. For health plans and delegated entities, it can create financial leakage, reporting discrepancies, and uncertainty about the performance of a risk arrangement.

Patients generally do not interact with a DOFR directly. However, accurate financial-responsibility administration can help reduce avoidable payment friction and administrative burden across the organizations responsible for delivering and financing their care. The DOFR does not determine medical necessity, covered benefits, or the care a patient should receive; those matters are governed by other contract terms, benefit rules, and applicable requirements.

Because DOFR terms vary by agreement, financial responsibility should always be determined using the governing contract, applicable amendments, current crosswalks, and validated system configuration.

Sources:

• Centers for Medicare & Medicaid Services, “Risk-Based Arrangements in Health Care”: https://www.cms.gov/priorities/innovation/key-concepts/risk-based-arrangements-health-care
• California Department of Managed Health Care, “Guidance Regarding AB 72 Delegated Entity Report”: https://dmhc.ca.gov/Portals/0/Docs/OPL/APL%2018-008%20%28OFR%29%20-%20AB%2072%20Delegated%20Entity%20Report%20%2803-23-2018%29_1.pdf
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 17, 2026

DOFR classification is the process of determining which financial responsibility category a healthcare service belongs to based on the DOFR matrix, the service details on the claim, and any applicable exception rules. When a claim arrives, the claims adjudication system evaluates the procedure codes (CPT and HCPCS), revenue codes, place of service, diagnosis codes, and other claim attributes against the configured DOFR rules to assign the claim to the correct financially responsible party.

In straightforward cases, classification is simple: a primary care office visit maps to physician services, which is typically capitated to the medical group. The complexity arises in high-ambiguity service categories where the same procedure code can map to different DOFR categories depending on context. For example, an injectable medication (HCPCS J-code) may be classified as chemotherapy, infusion therapy, or a general injectable depending on the specific drug, the clinical setting, and the contractual definitions in that particular DOFR.

Exception tables add another layer. These are negotiated overrides that route specific CPT or HCPCS codes differently from the general classification rules. A service that would normally fall under one category may be explicitly assigned to another based on contractual provisions. Exception tables are updated regularly and must be maintained alongside the general classification rules.

Accurate DOFR classification depends on three things: a correctly configured DOFR matrix in the claims system, current exception tables reflecting the latest contract amendments, and sufficient detail in the claim data to distinguish between overlapping service categories.

A health plan may delegate financial responsibility for defined healthcare costs, specified administrative functions, or both. The permitted scope and retained responsibilities depend on the contract, product, line of business, and applicable requirements.

Delegated functions can include:

• Claims processing and adjudication
• Utilization management
• Credentialing and provider-network activities
• Quality management and reporting
• Specified member-service, grievance, appeal, or referral functions
• Financial responsibility for defined professional, institutional, ancillary, pharmacy, behavioral health, or other healthcare costs

These responsibilities do not have to move together. An organization may bear financial risk without administering every related claim, or process claims without bearing the costs being adjudicated.

Applicable programs also preserve responsibilities at the health-plan level. Under 42 CFR § 422.504, a Medicare Advantage organization maintains ultimate responsibility for complying with its CMS contract notwithstanding its relationships with first-tier, downstream, and related entities. Medicaid managed-care entities have a parallel responsibility to comply with their state contracts under 42 CFR § 438.230.

Read the complete guide to delegated responsibilities.

DOFR configuration drift is the progressive divergence between a DOFR's current contract terms and the system configuration rules that implement those terms in a claims adjudication platform. In healthcare delegated risk operations, configuration drift occurs when yearly contract amendments, drug table updates, exception table changes, and new code releases accumulate faster than operations teams can update the corresponding system configuration.

Configuration drift does not announce itself. Claims continue to adjudicate successfully, providers are paid, and no denials or alerts are generated. The divergence becomes visible only when financial reconciliation reveals that the wrong party has been absorbing costs, sometimes for months. This makes configuration drift one of the most financially dangerous failure modes in delegated risk, because the errors compound silently over time.

The root causes include the volume of yearly amendments across multiple payer contracts, the complexity of drug table crosswalks and exception table overrides, staff turnover that erodes institutional configuration knowledge, and the absence of automated verification between contract documents and system rules. Organizations managing many payer relationships face an ever-growing Configuration Surface Area that makes drift increasingly likely.

DOFR errors can be difficult to detect because a claim may complete adjudication without producing an obvious exception, even when financial responsibility has been assigned incorrectly.

Many visible claims problems create an operational signal. A claim may deny, suspend for review, reject because required information is missing, or appear on an exception report. Those outcomes give an organization an opportunity to investigate the issue.

A DOFR configuration error may behave differently.

If the claims system contains a valid but incorrect responsibility rule, it may apply that rule consistently. The claim can move through the expected workflow while assigning its cost to the wrong organization. From the system’s perspective, the configured instruction was followed.

For example:

• The governing contract assigns a service to plan risk.
• The claims system is configured to treat that service as capitated responsibility.
• An applicable claim is received.
• The system applies the configured rule and assigns the cost to the delegated entity.
• No exception is generated because the rule itself is technically valid.

The error may remain undetected until someone compares claim outcomes against the governing contract or notices an unexpected financial pattern.

Several factors can make these errors especially difficult to identify:

• Responsibility rules may be distributed across multiple system components.
• Contract amendments may not be reflected in production configuration.
• Code and drug crosswalks may change after the original setup.
• The same service may have different responsibility assignments under different contracts.
• Exceptions may override general service-category rules.
• The affected claims may be financially material in aggregate but individually unremarkable.
• Reconciliation may identify a discrepancy without revealing the configuration rule that caused it.

Detection therefore requires more than monitoring denials. Organizations may need to compare contract terms, configuration rules, and actual claim outcomes.

Useful controls can include:

• Contract-to-configuration validation
• Representative and edge-case claim testing
• Monitoring by service category and responsible party
• Review of high-cost and high-ambiguity services
• Version control for contracts, crosswalks, and configuration
• Post-implementation validation after material changes
• Periodic sampling of successfully adjudicated claims

The key distinction is that successful claim processing does not necessarily prove correct financial-responsibility assignment. It proves that the claim was processed according to the rules available to the system.

Sources:

• California Department of Managed Health Care, “Claims Technical Assistance Guidance,” January 2026: https://www.dmhc.ca.gov/Portals/0/Docs/OFR/Claims%20TAG_Accessible%20January%202026%20-%20Accessible.pdf
• Centers for Medicare & Medicaid Services, “HCPCS Quarterly Update”: https://www.cms.gov/medicare/coding-billing/healthcare-common-procedure-system/quarterly-update
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 17, 2026

The behavior of a particular claim depends on the governing contract, system configuration, claim data, and organizational workflow.

A risk-bearing organization (RBO) is a healthcare organization that accepts financial responsibility for defined healthcare services, commonly in exchange for a fixed or capitated payment.

The specific legal definition varies by jurisdiction. In California, an RBO is generally a physician-controlled organization, medical partnership, medical foundation, or other organized physician group that:

• Contracts directly with a health plan or arranges healthcare services for the plan’s members
• Receives compensation on a capitated or other fixed periodic basis
• Processes and pays provider claims for services covered by that payment

California’s statutory definition does not include an individual provider or the health plan itself.

Independent practice associations (IPAs) and medical groups commonly operate as RBOs. A management services organization (MSO) may provide administrative, claims, contracting, financial, or technology services to an RBO, but an MSO is not automatically an RBO merely because it supports one.

An RBO assumes responsibility only for the services included in its agreement. The Division of Financial Responsibility (DOFR) identifies which service categories are delegated to the RBO, which remain the responsibility of the health plan, and which are assigned to specialty vendors or other parties.

For example, an RBO may accept capitation for professional services while inpatient facility services remain plan risk and behavioral health is carved out to another organization.

The RBO’s claims system must translate those contractual assignments into operational rules. If the configured rules do not match the governing DOFR, the RBO may pay claims that were not included in its assumed risk or fail to pay claims that were.

Accurate DOFR administration is therefore central to an RBO’s financial performance, claims operations, provider relationships, and regulatory responsibilities.

Sources:

• California Department of Managed Health Care, “RBO Frequently Asked Questions”: https://www.dmhc.ca.gov/LicensingReporting/RiskBearingOrganizations/RBOFrequentlyAskedQuestions.aspx
• California Department of Managed Health Care, “Useful Terms”: https://www.dmhc.ca.gov/HealthCareinCalifornia/UsefulTerms.aspx
• Centers for Medicare & Medicaid Services, “Risk-Based Arrangements in Health Care”: https://www.cms.gov/priorities/innovation/key-concepts/risk-based-arrangements-health-care

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

This material is educational. Whether an organization meets a particular legal or regulatory definition depends on the jurisdiction, organizational structure, contracts, and applicable requirements.

Delegated risk and capitation are related, but they describe different parts of a healthcare arrangement.

Delegated risk describes the transfer of responsibility. A health plan assigns defined financial or operational responsibilities to a medical group, IPA, RBO, or another organization.

Capitation describes a payment method. Under capitation, a healthcare provider or organization receives a predictable, upfront amount to cover some or all healthcare services for a defined patient population during a specified period.

In many delegated-risk arrangements, the delegated organization receives a per-member-per-month (PMPM) capitated payment. In return, it becomes financially responsible for the services included within the agreed scope.

The two terms are not interchangeable:

• An organization can receive capitation for a limited group of services without receiving every operational function that a plan could delegate.
• A health plan can delegate an administrative function without transferring financial risk through capitation.
• Different categories of services can be subject to different payment and responsibility arrangements within the same contract.

The Division of Financial Responsibility (DOFR) connects the two concepts. It defines the services that the delegated organization is expected to fund from its capitated payment and distinguishes them from services retained by the health plan or assigned to another party.

For example, a medical group may receive professional-services capitation. Its DOFR may assign primary care and specialist professional services to the group, inpatient facility services to the health plan, and pharmacy services to a pharmacy benefit manager.

Capitation determines how the group is paid. Delegated risk determines what responsibility the group assumes. The DOFR defines the contractual boundary of that responsibility.

If the DOFR, capitation assumptions, and claims-system configuration do not agree, the organization may absorb costs that were not priced into its capitation or avoid costs that it contractually agreed to bear.

Sources:

• Centers for Medicare & Medicaid Services, “Capitation and Pre-Payment”: https://www.cms.gov/priorities/innovation/key-concepts/capitation-and-pre-payment
• Centers for Medicare & Medicaid Services, “Risk-Based Arrangements in Health Care”: https://www.cms.gov/priorities/innovation/key-concepts/risk-based-arrangements-health-care
• California Department of Managed Health Care, “Useful Terms”: https://www.dmhc.ca.gov/HealthCareinCalifornia/UsefulTerms.aspx

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

This material is educational. Actual payment methods and delegated responsibilities depend on the governing contract, DOFR, amendments, benefit documents, and applicable requirements.

Capitation reconciliation is the process of comparing expected capitated payments and financial responsibility against the payments, enrollment records, claims, and contractual terms actually applied during a defined period.

The term can describe two related forms of reconciliation.

Membership and payment reconciliation

Organizations compare member eligibility and enrollment records against the capitation payments received or issued. This process may identify:

• Missing or duplicate members
• Incorrect effective or termination dates
• Retroactive enrollment changes
• Incorrect PMPM rates
• Product or benefit-plan mismatches
• Payments assigned to the wrong provider organization

Standard enrollment and payment transactions, including the HIPAA 834 enrollment transaction and 820 premium-payment transaction, can support this process.

Claims and financial-responsibility reconciliation

Organizations compare paid claims against the contractual responsibility defined by the applicable DOFR, amendments, crosswalks, and benefit arrangements.

This process asks a different question:

Did the organization that absorbed the cost of each claim actually bear financial responsibility for it?

A claim may have been processed and paid correctly according to the system’s configured rules while still being assigned to the wrong organization under the governing contract.

Effective reconciliation may compare:

• Member eligibility
• Capitation payments
• Claims paid by each organization
• DOFR service categories
• Plan-risk and capitated assignments
• Carve-outs and specialty-vendor responsibility
• Contract versions and effective dates
• Configuration rules applied during adjudication

Reconciliation can identify a financial discrepancy, but it does not always identify the configuration rule that caused it. Determining root cause may require tracing the affected claims back through the DOFR, contract amendments, code mappings, and production configuration.

For delegated-risk organizations, capitation reconciliation is both a financial control and a method for identifying potential responsibility leakage.

Sources:

• California Department of Health Care Services, “Capitation Payment Management System 820/834”: https://www.dhcs.ca.gov/forms-laws-publications/laws-and-regulations/health-insurance-portability-accountability-act-default/capitation-payment-management-system-820-834/
• Centers for Medicare & Medicaid Services, “Capitation and Pre-Payment”: https://www.cms.gov/priorities/innovation/key-concepts/capitation-and-pre-payment
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

This material describes common reconciliation practices. Actual reconciliation procedures depend on the contract, payment model, enrollment data, claims workflow, and organizational policies.

Delegation oversight is the process a health plan uses to evaluate and monitor organizations performing healthcare functions on its behalf.

A health plan may delegate functions such as:

• Claims processing
• Utilization management
• Provider credentialing
• Network management
• Care management
• Quality improvement
• Appeals and grievances
• Certain member-service activities

Delegation does not necessarily eliminate the health plan’s accountability for the delegated function. The applicable contract and regulatory requirements commonly require the plan to monitor performance, maintain appropriate oversight, and take corrective action when a delegated entity does not meet required standards.

A delegation oversight program may include:

• Pre-delegation assessments
• Written delegation agreements
• Policies and procedure reviews
• Performance standards and reporting
• Periodic audits
• Corrective action plans
• Claims timeliness and accuracy testing
• Monitoring of member complaints and provider disputes
• Review of financial solvency and administrative capacity

For delegated claims operations, oversight should also consider whether production configuration reflects current contractual financial responsibility.

The Division of Financial Responsibility (DOFR) may accurately define which organization should pay for each service category. However, reviewing the signed DOFR alone does not prove that the delegated entity’s claims system applies those rules correctly.

A complete configuration-control process may include:

• Contract-to-configuration validation
• Testing representative and high-ambiguity claims
• Verification of amendments and effective dates
• Review of code and drug crosswalks
• Post-implementation production validation
• Periodic comparison of configured rules against current contracts
• Documentation of approvals, testing, and accountable owners

Without these controls, claims may continue to adjudicate successfully even when the financial responsibility applied by the system no longer matches the contract.

DOFR configuration accuracy is therefore an important component of delegated claims oversight, especially for health plans managing multiple delegated entities, contracts, products, and lines of business.

Sources:

• Electronic Code of Federal Regulations, 42 CFR § 422.504, Medicare Advantage contract requirements: https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-B/part-422/subpart-K/section-422.504
• California Department of Managed Health Care, “Claims Technical Assistance Guidance,” January 2026: https://www.dmhc.ca.gov/Portals/0/Docs/OFR/Claims%20TAG_Accessible%20January%202026%20-%20Accessible.pdf
• California Department of Managed Health Care, “Risk Bearing Organizations”: https://www.dmhc.ca.gov/LicensingReporting/RiskBearingOrganizations.aspx

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

This material is educational and does not describe every oversight obligation. Applicable requirements depend on plan type, jurisdiction, delegated function, contract, and regulatory program.

No single job title universally owns DOFR configuration accuracy. The accountable role varies by organization, but responsibility should be explicitly assigned to one business owner with authority across contracting, claims, configuration, finance, and delegated operations.

DOFR configuration accuracy requires several functions to work together:

• Contracting maintains the governing agreement, DOFR, amendments, and effective dates.
• Operations interprets the business meaning of service categories, carve-outs, and exceptions.
• Configuration or information technology implements the rules in the claims system.
• Claims operations validates how representative claims adjudicate.
• Finance and reconciliation monitor whether financial outcomes align with the contract.
• Compliance and audit independently evaluate whether required controls are operating.
• Cybersecurity protects access, change authorization, and system integrity.

These functions share responsibility, but shared participation should not mean fragmented accountability.

A strong governance model names one operational owner who is accountable for confirming that:

1. The correct governing documents were used.
2. Every applicable service category was translated into claims logic.
3. Amendments and crosswalks were implemented by their effective dates.
4. Representative, high-cost, and edge-case claims were tested.
5. Approvals and test evidence were documented.
6. Production behavior was validated after implementation.
7. Current system rules are periodically compared with current contracts.

Cybersecurity can verify that a change was authorized and traceable. IT can verify that a rule was deployed. Neither function can independently determine whether the rule accurately represents the contract.

Likewise, a claims examiner can confirm that a claim followed the configured rule but may never see the DOFR language that should have governed it.

The central accountability question is therefore not simply, “Who maintains the claims system?”

It is:

“Who is responsible for proving that the financial-responsibility rules in production match the current contract?”

Related Gabeo resource:

https://www.gabeo.ai/dofr/articles/delegation-oversight-blind-spot-dofr-configuration-accuracy

Sources:

• California Department of Managed Health Care, “Claims Technical Assistance Guidance,” January 2026: https://www.dmhc.ca.gov/Portals/0/Docs/OFR/Claims%20TAG_Accessible%20January%202026%20-%20Accessible.pdf
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

The ownership model described here represents a recommended operational-control structure. Actual responsibilities depend on the organization, contract, claims platform, delegated functions, and applicable requirements.

DOFRs are Divisions of Financial Responsibility used in many delegated healthcare arrangements to define which organization is financially responsible for particular categories of covered services. A DOFR may allocate responsibility among a health plan, delegated medical group or IPA, and one or more specialty organizations, depending on the governing agreement.

Organizations commonly maintain multiple DOFRs because responsibility can vary by health plan, product, line of business, delegated entity, service category, effective date, and contractual amendment. Those differences must be translated into current claims-system rules so each claim is assigned to the appropriate financially responsible party.

Although “DOFR” refers to one Division of Financial Responsibility, “DOFRs” refers to multiple schedules, exhibits, or contractual arrangements. The exact structure and terminology vary by organization and agreement.

Read the complete guide to DOFRs in healthcare.

Financial responsibility leakage in delegated risk occurs when the cost of a healthcare service is absorbed by an organization that was not contractually responsible for it.

The term describes a financial outcome rather than a specific claim status or denial category.

For example:

• A medical group pays a claim that the DOFR assigns to the health plan.
• A health plan pays a claim that should have been covered by the medical group’s capitation.
• A plan or medical group pays for a service assigned to a specialty carve-out vendor.
• A shared-risk or subcapitation rule is applied incorrectly.
• An outdated contract version assigns responsibility for claims with a later date of service.
• A capitation payment does not reflect the service categories actually delegated.

Financial responsibility leakage can be difficult to detect because the underlying claim may process successfully. The provider may be paid, the claim may close, and no denial or exception may be generated.

From the claims system’s perspective, the configured instruction was followed. The problem is that the instruction did not match the governing contract.

Leakage can originate from:

• Incorrect initial DOFR configuration
• Contract amendments not implemented in production
• Outdated code or drug crosswalks
• Conflicting benefit and responsibility rules
• Missing carve-out logic
• Incorrect effective dates
• Configuration copied from another payer or product
• Manual overrides that became permanent
• Incomplete reconciliation across responsible parties

The financial impact may accumulate across individually ordinary claims. A single incorrectly configured service category can affect hundreds or thousands of claims before someone identifies the pattern.

Financial responsibility leakage is distinct from fraud, waste, abuse, or unnecessary utilization. The service may have been appropriate, covered, and correctly priced. The error concerns which organization was contractually responsible for its cost.

Detecting this type of leakage requires comparing contract terms, DOFR rules, production configuration, and actual claim outcomes.

Related Gabeo resource:

https://www.gabeo.ai/dofr/articles/the-three-way-model-financial-responsibility-in-delegated-risk

Sources:

• Centers for Medicare & Medicaid Services, “Risk-Based Arrangements in Health Care”: https://www.cms.gov/priorities/innovation/key-concepts/risk-based-arrangements-health-care
• California Department of Managed Health Care, “RBO Frequently Asked Questions”: https://www.dmhc.ca.gov/LicensingReporting/RiskBearingOrganizations/RBOFrequentlyAskedQuestions.aspx
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

“Financial responsibility leakage” is used here as an operational term for costs assigned to a party other than the party identified by the governing agreement. It is not presented as a standardized regulatory or accounting definition.

A DOFR configuration audit compares the governing contract with the financial-responsibility rules implemented in the claims system and tests whether those rules produce the intended claim outcomes.

A complete audit generally includes seven stages.

1. Identify the governing documents

Collect the signed DOFR, delegation agreement, amendments, effective dates, benefit grids, exception tables, payer-issued crosswalks, and related contractual materials.

The audit should determine which document controls when two sources conflict.

2. Establish the contract version by date

DOFR assignments can change over time. Claims should be evaluated against the version in effect on the claim’s date of service, not simply the most recent document available.

3. Extract the contractual responsibility rules

Document each service category and its assigned party, including:

• Medical group or IPA responsibility
• Health-plan responsibility
• Specialty-vendor carve-outs
• Shared-risk arrangements
• Split capitation
• Subcapitation
• Exceptions and overrides

4. Map the contract to system logic

Identify the configuration components that implement each responsibility assignment.

Depending on the platform, this may include:

• CPT and HCPCS codes
• Revenue codes
• Place-of-service rules
• Provider types or specialties
• Diagnosis codes
• Bill types
• Member products
• Network status
• Effective dates
• Custom responsibility tables
• Drug and injectable crosswalks

5. Compare contract rules with configuration

For every material service category, determine whether the production rule is complete, accurate, current, and traceable to the governing contract.

6. Test representative claims

Testing should include:

• Routine claims
• High-cost services
• High-volume categories
• Ambiguous category boundaries
• Contractual exceptions
• Carved-out services
• Claims immediately before and after effective-date changes
• Negative and edge cases

A successful test should confirm both the adjudication result and the financially responsible party.

7. Validate actual paid claims

Review a sample or population of historical claims to determine whether production outcomes matched the contract in force on each date of service.

Any variance should be traced to its root cause, affected claims, financial exposure, responsible owner, and corrective action.

An audit should produce more than an error list. It should create an evidence trail from the governing contract clause to the configured rule and from the configured rule to the claim outcome.

Related Gabeo resource:

https://www.gabeo.ai/dofr/articles/why-static-dofr-configuration-eventually-fails

Sources:

• California Department of Managed Health Care, “Claims Technical Assistance Guidance,” January 2026: https://www.dmhc.ca.gov/Portals/0/Docs/OFR/Claims%20TAG_Accessible%20January%202026%20-%20Accessible.pdf
• Centers for Medicare & Medicaid Services, “HCPCS Quarterly Update”: https://www.cms.gov/medicare/coding-billing/healthcare-common-procedure-system/quarterly-update
• Centers for Medicare & Medicaid Services, “Place of Service Codes”: https://www.cms.gov/medicare/coding-billing/place-of-service-codes
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

The appropriate audit scope depends on the governing agreements, claims platform, available data, organizational policies, and applicable requirements.

An IPA, MSO, and RBO perform different roles in healthcare, although one organization or affiliated group may operate in more than one of these capacities.

Independent practice association

An independent practice association (IPA) is an organization through which independent physicians participate in health-plan contracts while generally remaining part of their separate medical practices.

An IPA may:

• Contract with health plans
• Organize a physician network
• Coordinate referrals and utilization
• Receive capitated payments
• Assume financial responsibility for defined services
• Process or arrange payment of provider claims

An IPA may qualify as a risk-bearing organization when it satisfies the applicable legal and operational requirements.

Management services organization

A management services organization (MSO) provides administrative and operational services to medical groups, IPAs, health plans, or other healthcare organizations.

Services may include:

• Claims administration
• Contracting support
• Provider-network administration
• Information technology
• Finance and accounting
• Credentialing
• Utilization-management support
• Data analytics
• Compliance support

An MSO is not automatically financially responsible for healthcare services. Its responsibility depends on its contracts, organizational structure, and role in the arrangement.

Risk-bearing organization

A risk-bearing organization (RBO) is an organization that accepts defined financial responsibility for healthcare services, typically in exchange for capitation or another fixed periodic payment.

In California, an RBO generally contracts with a health plan, receives capitated or fixed periodic compensation, and processes and pays provider claims for services covered by that payment.

The three terms therefore describe different characteristics:

• IPA describes a physician-network and contracting structure.
• MSO describes an administrative-services role.
• RBO describes the assumption of financial risk and related claims responsibility.

A healthcare enterprise may include an IPA that assumes risk and qualifies as an RBO while using an affiliated MSO to perform its administrative functions.

Names alone do not determine responsibility. The governing agreements, corporate structure, delegated functions, and DOFR determine which entity performs each role and which organization bears the cost of each service category.

Sources:

• California Department of Managed Health Care, “RBO Frequently Asked Questions”: https://www.dmhc.ca.gov/LicensingReporting/RiskBearingOrganizations/RBOFrequentlyAskedQuestions.aspx
• California Department of Managed Health Care, “Risk Bearing Organizations”: https://www.dmhc.ca.gov/LicensingReporting/RiskBearingOrganizations.aspx
• California Department of Managed Health Care, “Useful Terms”: https://www.dmhc.ca.gov/HealthCareinCalifornia/UsefulTerms.aspx

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

These terms may be used differently across jurisdictions and organizations. An entity’s legal and financial responsibilities depend on its structure, licenses, contracts, delegated functions, and applicable law.

Delegated risk can support value-based care by giving provider organizations financial responsibility for the cost and coordination of care across a defined population.

Fee-for-service generally rewards additional billable services. A well-designed risk arrangement can instead create incentives to prevent avoidable complications, coordinate care, manage chronic conditions proactively, reduce duplicative services, and invest in population-health capabilities.

Delegated risk does not automatically produce better outcomes. Capitation rates must be adequate, quality and access must be measured, members need appropriate protections, and organizations need the clinical and operational capability to manage care. Poorly designed incentives can create pressure to reduce necessary as well as unnecessary utilization.

Delegation is also not the only form of value-based care. Bundled payments, quality incentives, shared-savings programs, shared-loss arrangements, and accountable-care models can create value-based incentives without a health plan delegating financial responsibility to an IPA or medical group.

Delegated risk is therefore best understood as one important operating model within the broader value-based-care landscape.

Read how delegated risk can support value-based care.

In a Medicare Advantage arrangement involving delegated financial risk, the Division of Financial Responsibility (DOFR) helps determine whether the Medicare Advantage health plan, a delegated medical group or IPA, or another contracted organization is financially responsible for a covered service.

A DOFR does not determine whether Medicare covers a service. It also does not replace the member’s Evidence of Coverage, establish medical necessity, or independently determine member cost-sharing.

Instead, the DOFR operates within the contractual relationship among the organizations administering and financing care.

For example, a Medicare Advantage plan may delegate financial responsibility for defined professional services to a medical group through capitation while retaining responsibility for inpatient facility services. Pharmacy, behavioral health, dental, vision, or other benefits may be administered under separate arrangements.

When a Medicare Advantage claim is received, responsibility may depend on:

• The member’s plan and product
• The delegated medical group or IPA
• The applicable contract and DOFR
• The claim’s date of service
• Procedure and revenue codes
• Place of service
• Provider type and network status
• Benefit-specific rules
• Carve-outs and specialty vendors
• Contract amendments and exceptions

The claims system translates these terms into adjudication rules. If the configuration matches the governing agreement, the claim can be assigned to the appropriate financially responsible organization.

If the configuration is wrong or outdated, the claim may still process successfully while assigning its cost to the wrong party.

That can create:

• Plan overpayments
• Costs incorrectly absorbed by the delegated organization
• Provider-payment delays
• Disputes between the plan and medical group
• Inaccurate risk-pool reporting
• Reconciliation adjustments
• Member confusion when organizations provide conflicting answers

Medicare Advantage organizations may contract with other entities to perform certain functions, but federal requirements generally preserve the Medicare Advantage organization’s responsibility for fulfilling its CMS contract.

DOFR accuracy is therefore relevant to both delegated claims administration and health-plan oversight. It helps establish who should bear the financial cost of a covered service after applicable Medicare Advantage coverage and benefit rules have been determined.

Sources:

• Electronic Code of Federal Regulations, 42 CFR § 422.504, Medicare Advantage contract requirements: https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-B/part-422/subpart-K/section-422.504
• Centers for Medicare & Medicaid Services, “Organization Determinations”: https://www.cms.gov/medicare/appeals-grievances/managed-care/organization-determinations
• Centers for Medicare & Medicaid Services, “Electronic Health Care Claims”: https://www.cms.gov/medicare/coding-billing/electronic-billing/electronic-healthcare-claims
• Alameda County Health, example Division of Financial Responsibility: https://health.alamedacountyca.gov/wp-content/uploads/2024/03/AppendixA-DOFR.pdf

Written by: Michael Riley, Co-Founder & Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with 20+ years of DOFR experience.

Last substantively reviewed: August 26, 2026

This material is educational. Medicare Advantage coverage, payment, delegation, and financial responsibility depend on CMS requirements, the member’s benefits, the governing contracts, and current system configuration.

An IPA is an organization through which independent physicians or practices can participate collectively in health-plan contracting and coordinated activities. Some IPAs accept capitation and delegated financial risk, but an IPA should not be assumed to bear risk merely because it is an IPA.

An MSO provides administrative, technological, financial, or operational services to medical groups, IPAs, health systems, or other organizations. It may operate claims systems, manage provider data, support contracting, produce reports, or provide analytics. An MSO is not automatically a risk-bearing organization, although a particular MSO's role depends on its legal structure and contracts.

In California, an RBO is a regulatory classification associated with a qualifying organization that accepts defined forms of financial risk from a health care service plan. RBOs submit financial filings used by the California Department of Managed Health Care to monitor solvency.

The roles can overlap operationally without becoming interchangeable. A health plan may transfer risk to an IPA or medical group that qualifies as an RBO, while an MSO supplies administrative support. The governing documents identify which legal entity bears risk, performs each function, and holds each obligation.

Read the complete guide to IPAs, MSOs, and RBOs.

Sources and review information

• 42 CFR § 422.504, Medicare Advantage contract provisions
• 42 CFR § 438.230, Medicaid managed-care subcontractual relationships and delegation
• California DMHC, Risk-Bearing Organizations

Written by: Michael Riley, Co-Founder and Chief Product Officer of Gabeo.ai

Reviewed for operational accuracy by: Octavio Campos, Director of Operations at Guidant Health, with more than 20 years of DOFR experience

Last substantively reviewed: August 27, 2026

This material is educational. Delegation, financial responsibility, payment, and oversight depend on applicable requirements, governing agreements, amendments, and current operational configuration.