Who owns claims data when a TPA administers the claims?

The short answer: the risk-bearer owns the file, the TPA owns its process

A third-party administrator usually holds claims data as a custodian, not as its owner. On fully insured business the claim file belongs to the carrier that issued the policy; on self-funded programs it belongs to the self-insured employer, public entity or plan that pays the losses. The claims service agreement or administration agreement is the document that settles it, so read that before anyone mentions licensing.

What a TPA owns outright is narrower but still real: the way it handles claims. Its desk procedures, file audit methodology, training curriculum, staffing models, internal communications and operating metrics are its own business records. Those can be candidates for a data license once client information inside them is removed, and claim-level material can be added only where clients agree.

Who controls the claim file in common TPA arrangements

The answer follows the money. Whoever pays the claims normally controls the file, and the administrator works on its behalf.

Copyright authorship is a separate question from file ownership

Who wrote the notes and who controls the file are different legal questions, and both matter. The Copyright Office's circular on works made for hire explains that work an employee prepares within the scope of employment is authored by the employer, while commissioned work from an outside contractor counts as made for hire only in listed categories and with a signed written agreement. Diary notes written by a TPA's staff adjusters are therefore generally the TPA's work, while notes from independent adjusters on contract may not be unless their contracts assign the rights.

Authorship does not override the client contract. An administration agreement can still give the carrier or self-insured client ownership of the whole file, restrict any use beyond administering claims, and require return or destruction when the relationship ends. Both answers need to line up before claim-level notes go anywhere.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

What a TPA can usually license, and what needs client consent

Use a simple rule, the file-or-process test. If a record describes a specific claimant's claim, treat it as the client's. If it describes how the TPA runs its operation, treat it as the TPA's, subject to a confidentiality review.

What makes claim-level notes worth the consent effort is explained in the claims notes data brief.

Checklist before an operating partner makes the introduction

Run this with the TPA's CEO and general counsel. It takes one meeting and prevents an introduction that stalls on rights.

• List the largest clients by claim volume and pull each administration agreement.
• Note who owns claim files, what happens to them at termination, and whether aggregated or de-identified use is permitted.
• Separate fully insured carrier business from self-funded client programs, because the consent conversation differs.
• Check independent adjuster and vendor contracts for assignment of work product.
• Flag lines that are mostly health information, such as group health and workers' compensation medical.
• Confirm the TPA itself had 50+ full-time employees at peak, with contract adjusters excluded from the count.
• Identify who can approve a license: the owner, CEO, CFO or another authorized representative.
• Confirm someone can export the TPA's own operating records from the systems that hold them.

How to respond when the CEO says the data belongs to clients

The CEO is usually right about the claim files, and the reply should say so. Then narrow the question to what the TPA owns.

If a few large self-insured clients seem open to it, the CEO can raise it with them directly. Partners never approach a TPA's clients and never handle the records.

When the concern is valid

Sometimes the objection holds and the right call is to stop:

• Nearly all the useful history sits inside client claim files and no client will consent.
• The book is mostly health claims or medical bill review.
• Major clients have left and their files were transferred out.
• The TPA's own procedures are thin, undocumented or copied from client manuals.
• The administration agreements forbid any use beyond claims administration, including de-identified use.

In those cases, look elsewhere in the portfolio. The same ownership logic applies to warranty administrators, whose warranty claims records are often tied to manufacturer programs, and to MGAs, covered in MGA data ownership and carrier rights.

How the introduction runs once the rights are clear

1. The operating partner introduces the TPA through the referral form, or sends the CEO a referral link to apply directly.
2. SourceX confirms headcount, operating history, the systems involved and which records the TPA owns.
3. The TPA lists its own systems and records as metadata only; the data inventory builder is a practical starting point.
4. SourceX and the TPA agree price, scope, exclusivity and redaction rules before any buyer sees a description.
5. AI labs and data buyers review the opportunity; delivery happens only after a signed agreement and the TPA's authorization.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, paid only after the buyer pays and SourceX receives its fee. No reward is guaranteed.

Next step

Compare the TPA's profile with who qualifies. When the file-or-process test points to records the TPA owns, register as a partner and make the introduction. Other portfolio screens for sponsors are on the operating partner page.