Healthcare credentialing solutions: software, service, or the two together

Updated

Healthcare credentialing solutions is a phrase vendors use for two different products, and buying the wrong one is the common expensive mistake. One is software: a record that holds each practitioner's licence, DEA registration, malpractice cover, board certification and payer enrolments, with every expiry date visible and nothing else. The other is a service: people who do the primary source verification and file the payer applications on your behalf. They solve different problems. A group whose credentialing specialist is competent and drowning needs the first. A group with no credentialing specialist at all needs the second, and will eventually need the first as well. This page is written for the practice administrator or credentialing lead working out which of those they actually have, and what each costs in time rather than in licence fees.

What credentialing software covers

A record per practitioner, with a dated item for each document: state licence, DEA registration, malpractice cover, board certification, and one line per payer enrolment with its revalidation date. The value is not storage, which a folder does; it is that every expiry is visible together and early enough to start the renewal, because the paperwork always takes longer than the notice period suggests.

What a credentialing service does instead

A service employs the people. They collect the documents, perform primary source verification, assemble the payer applications and chase them, and they charge per practitioner or per application. That is labour, not software, and it is the right purchase when the alternative is a clinician doing it between clinics. It does not remove the need for a record: at the end of the engagement, somebody still has to hold the expiry dates.

The cycles the record has to carry

Enrolment is not a one-off. Medicare requires a provider or supplier other than a DMEPOS supplier to resubmit and recertify the accuracy of its enrolment information every 5 years (42 CFR 424.515), and a DMEPOS supplier must revalidate every 3 years after privileges are first granted (42 CFR 424.57(g)). Those cycles are long enough to fall out of anyone's working memory, which is exactly why they belong on a record rather than in a calendar reminder somebody set two jobs ago.

Why the contracts belong beside them

A payer agreement names the practitioners it covers, and the value of that agreement depends on those practitioners being enrolled. Keeping the credential files on the same record as the contracts is what turns a lapsing licence from an administrative note into what it actually is, which is a revenue risk against a named agreement.

Questions people ask about healthcare credentialing solutions

Does Medcontra do primary source verification?

No. It records what you verified, from which source and on what date. The verification is your team's work and the judgement stays theirs; we hold the evidence trail and the dates.

Does it submit payer enrolment applications?

No. Enrolment appears on the practitioner's file as a dated item with its revalidation cycle, so the work is visible and scheduled. Filing the applications is your team's or your service's job.

We already use a credentialing service. Is there anything here for us?

Yes, and it is the part services rarely leave behind: the record. When the engagement ends or the account manager changes, the expiry dates and the verification evidence should already be yours, on the same record as the agreements they support.

Sources

Related answers

Keep this abstract in Medcontra ProNever miss a renewal: start Pro