Contract disclosure clauses: the license events you must report to payers

Do I have to tell my payers about a license event?

Usually, yes — but the obligation comes from your contract, not from a law that applies to every clinician. Each health plan you join sets its own disclosure terms in the participation agreement you sign, and there is no uniform national standard. The binding question is always: what does this plan's contract say I must report, and by when?

There is no single national rule, and each plan publishes its provider policies separately — Anthem 1Ref 1Anthem (2026).Anthem Provider Policies.Named example that each payer publishes its own provider policies, supporting that there is no uniform national rule and the participation contract controls what must be disclosed., Aetna 2Ref 2Aetna (2026).Aetna Clinical Policy Bulletins.Second named example that a payer publishes its own policies separately, reinforcing that disclosure terms vary plan to plan and the contract controls., and UnitedHealthcare 3Ref 3UnitedHealthcare (2026).UnitedHealthcare Policies and Protocols.Third named example that a payer maintains its own published provider policies, supporting the no-uniform-rule framing. each maintain their own provider-policy libraries, and the reimbursement and credentialing rules differ plan to plan. The duty that actually binds you is the one written into the contract you signed with that plan, so reading a payer contract before you sign is the only way to know your disclosure exposure in advance.

What counts as a reportable 'license event'

Most disclosure clauses reach far more than a full revocation. Read yours for the exact list, but the events plans commonly require you to report include any restriction or condition placed on your license, formal probation, a suspension, a voluntary or involuntary surrender, a revocation, and — the one solos miss — the mere opening of a board investigation or the filing of a formal complaint, before any finding.

• Restrictions and conditions — a stipulation, a chaperone requirement, a practice limitation.
• Probation, suspension, revocation — the formal disciplinary tiers.
• Voluntary surrender — treated as an adverse action, not a clean exit.
• An open investigation or complaint — many clauses trigger here, before any adjudication.
• A status change — a quietly lapsed license can count too. If your contract requires you to maintain licensure in good standing, the lapsed license — even a clerical one — may breach that term or trip the disclosure clause on its own.

The notice window: read the clause, not a generic number

Disclosure clauses set their own clock, and it is short — often counted in business days from the event, not from when the dust settles. Because the number varies by contract, do not rely on a figure you read anywhere else: open the agreement, find the notification clause, and read the trigger and the count. Then calendar that deadline the day the event happens, not the day you get around to it.

Two details decide the deadline. First, the trigger — does the clock start at the board's action, or at the moment you learn of it? Second, the channel — most contracts name a specific address, portal, or credentialing contact, and notice sent anywhere else may not count. Send it in writing through the designated channel and keep proof of delivery.

Who to notify first: the parallel duties

A license event rarely triggers only your payer contracts. The same order that restricts your license usually starts several independent clocks at once, each with its own recipient and its own deadline. Work them in parallel, because a missed report to one body does not excuse a missed report to another. Build the list once, in advance, so the day it happens you are executing a checklist, not improvising.

When the license event began as a billing problem

Some license events grow out of a billing or coding problem the board learned about — an audit finding, an overpayment, a fraud referral. If yours does, the disclosure question widens: a self-identified overpayment has its own refund path, and conduct that implicates the federal fraud laws can be routed through the OIG's self-disclosure protocol 4Ref 4HHS Office of Inspector General (2026).Health Care Fraud Self-Disclosure Protocol.The escalation path when a license event grew from conduct implicating federal health-program fraud laws — the OIG self-disclosure protocol and what it is for, distinct from a simple overpayment refund., which lets a provider report and resolve it on defined terms.

The two paths are different and should not be confused. Returning a plain overpayment is a refund, and your contract's audit and lookback clauses may separately require you to return the money before any board matter closes. A self-disclosure, by contrast, is an admission of conduct with legal consequences that reach past the refund. Because of that, this is a point where the trigger list genuinely calls for counsel before you file anything.

What nondisclosure costs — and how to write the notice

Staying quiet is the expensive option. Nondisclosure is usually a separate breach of the participation agreement in its own right, independent of the underlying license event, and it hands the plan a clean for-cause termination — the exit that skips the 90-day exit you would otherwise get. It can also surface later through dispute resolution, or through the assignment clauses re-checked during a practice sale, when the plan re-credentials you.

The notice itself is short. A workable skeleton:

• Your name, NPI, and the panel or provider ID the plan knows you by.
• The plan and the contract you are writing under.
• The event, the date it occurred, and the exact action taken (restriction, suspension, surrender, open investigation).
• Your current practice status and whether it affects your ability to see that plan's members.
• A request for written acknowledgment.

Send it through the contract's designated channel, keep proof of delivery, and file a copy with the credentialing paperwork you will need at renewal.