Provider credentialing and payer enrollment tracking

Two things get called credentialing, and a practice loses money at the seam between them.

The first is whether a clinician is qualified: a BCBA certification, a state licence, an RBT registration, each with a date it expires. The second is whether a payer has agreed to pay that clinician: an enrollment application, submitted on some date, effective on another, sometimes terminated later.

They fail differently. A lapsed licence means work delivered after the lapse should not have been delivered. A missing enrollment means the work was fine and the claim will be denied anyway. MegAligna tracks both, separately, and reports the gap.

Licences and certifications, with the date they expire

Each staff member carries a credential list — what it is, its number, and when it runs out. The expiry is the field that matters: it is what turns a qualified clinician into an unbillable one on a specific Tuesday, usually without anyone noticing until a payer does.

Because the registry holds real dates rather than a checkbox, the same data drives the scheduling check that stops a service code being booked against somebody whose credential tier does not cover it.

Which payers have enrolled which providers

Enrollment is recorded per provider, per payer: when the application went in, when it became effective, the identifier that payer files under, and when it ended if it has. Status is derived from those dates rather than stored, so a relationship that lapsed last month reports itself as lapsed without anyone remembering to update a field.

The grid shows every clinician against every payer at once, because the question is always asked as a pair — can this person bill this payer — and a list of enrollment rows makes the absences invisible. The absences are the expensive part.

Applications routinely sit with a payer for 90 to 180 days, so each pending one carries the number of days it has been waiting. That is the number that turns “we submitted it” into “we submitted it in March” when somebody finally calls.

The gap, as a worklist

Delivered work whose rendering provider was not enrolled with that payer on the date of service appears on the billing dashboard, immediately before the export. Every row is a claim a payer is likely to deny for a reason that has nothing to do with the care.

It does not block anything, deliberately. An un-enrolled provider is sometimes a considered decision — a single-case agreement, or deliberate out-of-network billing — and software that silently refused to generate a charge would be a worse surprise than the denial it prevented. The worklist informs the person who can decide; it does not decide for them.

What this is not

MegAligna does not transmit claims to payers. Finished charges are handed to whoever does your billing, as a file or a superbill. Enrollment tracking tells you which of those charges is likely to come back — it does not send them, and it does not check a patient’s benefits.

There is also no automated application filing. Recording an enrollment means recording what you and the payer agreed; the paperwork is still yours.