Platform / Credential file

A folder of PDFs is not a credential file.

Every document is evidence for one credential, and the expiration is read off the document itself — so nobody is keeping a second copy of the date.

Credential file · Okafor, D. — MFM9 of 15 sections · 0 expiration dates typed by hand
  • Credential · evidenceExpires
Malpractice coverageConflict
Evidence
Certificate of insuranceProvider-supplied
Verified
Certificate on file03 Aug 2026
Claimed
30 Jun 2027From the application
Expires
14 Sep 2026From the certificate

Neither date is overwritten. Both stay on the credential and it goes to review, because an import that quietly corrects the file is one you cannot audit.

Select a credential to see what it stands onSample file · real document model

Sample file. Domains, origins and verification events follow the product’s own document model.

Why it drifts

The folder and the tracker drift apart.

The document lives in one place and its expiration lives in another, joined by a person who read the first and typed the second.

A renewed license gets uploaded but never re-keyed. An expiration is entered a year off. A certificate is replaced and the row beneath it never moves.

None of that is carelessness. It is what happens when the same fact is stored twice. By the time anyone notices, the file and the tracker have been telling different stories for months — and only one of them is the evidence.

How it works

The date comes off the document.

Which means nobody is keeping a parallel spreadsheet, because there is nothing left in it to keep.

  1. 01

    The document arrives

    Uploaded, photographed after clinic, or returned by the board that issued the credential.

  2. 02

    It attaches to a credential

    Not to a provider-wide pile. The certificate lands on the credential it evidences.

  3. 03

    Fields are read off it

    Number, issue date and expiration are extracted from the document rather than retyped.

  4. 04

    Status follows

    The expiration is the field. Nothing derived from it needs a second person to maintain.

Why it holds up

An audit is a query, not an excavation.

When the evidence hangs on the credential and the date came off the evidence, what was true last March is a lookup.

Was this license current on the date of service?
The board’s own response, with the timestamp it was received, on the license row.
Which document supports this board certification?
The certificate attached to it. One credential, one piece of evidence.
When did coverage actually lapse?
The date on the certificate, sitting beside the date the application claimed, with the conflict still on the row.

Questions we get

The credential file, plainly.

How is this different from a document library?
A library stores files and leaves the meaning to whoever opens them. Here a document is evidence for one credential, so the file already knows what a certificate is for and what it makes true. Nothing gets filed twice, and nothing gets filed nowhere.
What happens when a document and the record disagree?
Neither value is quietly overwritten. The claimed date stays, the document’s date is recorded beside it, and the credential goes to review with both in view. An import that silently corrects the file is an import nobody can audit afterwards.
Which credentials are primary source verified?
Licenses are verified against the issuing board, and exclusions are screened monthly against OIG LEIE. Everything else is labeled provider-supplied on its own row: the document is on file and the date comes off it, but the file never calls a certificate a primary source check.
Does the file travel with the provider?
Yes. The credential file is provider-owned, so a second facility inherits evidence it does not have to collect again. What that facility grants from the file — appointment, privileges — stays with the facility.

Send us one provider’s documents.

We will hand back the file they build, evidence attached to each credential, and you can tell us what it got wrong.