Research Billing Is a False Claims Act Surface. Treat the MCA Like the Control It Is.

THE BILLING GRID
A weekly column on research billing and coverage analysis, by Krishma Shah

A coordinator submits a lab requisition. The central lab bills it to the site. The site bills it to Medicare. The sponsor also reimburses it on the per-patient invoice. Nobody flagged the double charge because the Medical Coverage Analysis said “routine labs” with no visit-level detail and no citation. That is the fact pattern that produces a False Claims Act exposure, and it is more common than most research billing teams want to admit.

The Rush University Medical Center settlement in 2005 is the canonical public example of what happens when research billing controls fail. The core allegation was straightforward: items that the sponsor was contractually obligated to pay were billed to Medicare as if they were ordinary clinical care. The settlement did not require proof of intent. The False Claims Act reaches billing that is knowingly inaccurate, and “we did not check the MCA” is not a defense an auditor will accept.

What a Medical Coverage Analysis Actually Is

A Medical Coverage Analysis, or MCA, is a visit-by-visit, procedure-by-procedure grid that assigns each item in a protocol a billing designation. The three designations that matter are SOC (standard of care, billable to Medicare or a commercial insurer when the trial qualifies), RES (research-paid, meaning the sponsor bears the cost and the item must never appear on a patient or payer claim), and NB/INV (non-billable or invoiceable, meaning the item sits in the budget negotiation but not on a clinical claim).

The defensible unit of analysis is the visit-grid cell, not the procedure name. The same CBC can be SOC at the screening visit and RES at the Week 8 research visit. A document that assigns a billing designation at the procedure level without anchoring it to a specific visit is not a Medical Coverage Analysis. It is a list, and lists do not hold up in audits.

NCD 310.1 and Why Deemed Status Is Not Automatic

Medicare coverage for routine costs in qualifying clinical trials flows through National Coverage Determination 310.1. For a trial to qualify, it generally must carry an IND (Investigational New Drug application), carry therapeutic intent, and study items that fall within a Medicare benefit category. When those conditions are met, certain routine costs that a beneficiary would incur outside a trial become billable to Medicare even when the visit is protocol-driven.

The word “routine” is where sites make their first error. NCD 310.1 does not mean all costs at a qualifying trial visit are billable. It means costs that would be covered for a Medicare beneficiary outside the trial context may retain that coverage inside it. Anything the protocol adds beyond ordinary care, anything a patient would not receive if they were not enrolled, is a research cost the sponsor must pay.

The second error is writing “routine labs” in the MCA with no citation. Lab coverage is procedure-specific. A complete blood count maps to NCD 190.15. Writing a generic lab category with no NCD or Local Coverage Determination reference is the audit weak point. An auditor reviewing your MCA will look for those citations. Their absence does not mean the item is covered; it means you have not demonstrated that it is.

The Imaging Frequency Problem

Imaging is where visit-grid vagueness causes the largest dollar errors. Protocols frequently specify a scan schedule as a parent rule: “CT chest/abdomen/pelvis every 8 weeks for 9 cycles.” When a site builds or receives an MCA that decomposes that into individual scan components without preserving the parent schedule, the MCA may designate coverage for the scan at one visit and leave eight subsequent visits undesignated or incorrectly designated.

This is not a hypothetical. It is a consistent pattern in MCA reviews. Template-based tools do not catch it because the template does not know that the parent schedule existed. A human reviewer comparing the MCA to the protocol visit schedule catches it. The result of missing it is either billing Medicare for scans the sponsor should pay, or failing to bill Medicare for scans that legitimately qualify, either way a compliance or revenue problem.

Protocol-Only MCAs and the Budget Reconciliation Pass

Sites and networks working under aggressive startup timelines sometimes receive an MCA at feasibility, before a budget exists. That is a legitimate deliverable. A protocol-only MCA scopes the coverage landscape, designates SOC and RES items based on the protocol alone, and gives the site’s billing compliance team something to review while the budget negotiation is in progress.

The reconciliation pass happens when the budget arrives. The INVOICEABLE section of the MCA, which captures items the site will bill to the sponsor rather than to a payer, must be reconciled against the charge master. Research-paid items should be priced at the greater of the sponsor’s contracted rate or the charge master rate for those items. If that reconciliation does not happen explicitly, the site risks invoicing the sponsor at a rate inconsistent with its own charge master, which creates a separate compliance exposure on the revenue side.

A Stale MCA Is Worse Than No MCA

When a protocol amendment changes a visit schedule, adds a procedure, or removes one, the MCA must be updated before the amended visit occurs. A site that continues billing under a pre-amendment MCA is billing under a document that no longer matches the protocol the IRB approved and the sponsor is running. That gap is visible to any auditor who pulls the amendment date, the IRB approval date, and the first billing date after the amendment.

In practice, MCA amendments are frequently delayed because nobody owns the trigger. The protocol amendment arrives, the IRB submission goes out, the sponsor sends a protocol deviation notice, and the MCA update sits in a queue. Sites I work with have started treating the MCA amendment as a startup task for every protocol version, not a billing team afterthought. That means assigning a responsible person, a due date tied to the amendment effective date, and a sign-off that appears in the TMF alongside the amendment itself.

Device Trials Add a Layer

Trials running under an Investigational Device Exemption, or IDE, follow a different coverage framework. CMS distinguishes between Category A devices, which are experimental and receive no routine cost coverage, and Category B devices, which are non-experimental or non-investigational and may support routine cost coverage. The IDE approval letter from CMS controls the designation. Sites that bill routine costs to Medicare on a Category A IDE trial without a CMS coverage determination are operating without a coverage basis, regardless of what the MCA says.

The MCA on the Activation Critical Path

The MCA sits on the site activation critical path alongside the contract and IRB approval. A site cannot bill compliantly for a single visit until the MCA is finalized, reviewed by the billing compliance team, and linked to the charge capture workflow. Treating it as a back-office document to be completed after enrollment starts is the operational mistake that creates the False Claims Act surface. The document is a control. Controls work when they are in place before the thing they are controlling begins.