Your credentialing file keeps itself current.
Drop in a license or a whole packet. Qdential reads it, suggests where it belongs, and files it when you accept. Then it reminds you before anything lapses, and sends the file where it is needed.
Credentials
Sample dataDrop a file anywhere on Credentials
Licenses
California medical license
G 123456, expires March 14, 2027
From CA_License.pdf
DEA registration
FY3528411, expires April 30, 2027
Nothing is filed until you accept it.
The rest of the file, kept the same way.
Drop a 40-page packet; it comes apart into documents.
Qdential finds where each document starts and what it is. You check the split, and each part is read like any other upload.
A new provider arrives as one folder.
Drop the whole folder: licenses, diplomas, board certificates, COIs, a CV. Reading carries on after you close the tab, and each file waits for you to accept it.
Reminders on the days you choose: 90, 30, 7 and 1 day before, and on the day.
By email or on your phone, for licenses, DEA, certifications, immunizations, malpractice, and affiliation reappointments.
Disclosure answers with a last confirmed date.
Answer the malpractice, licensure and privileges questions once. Every application gets your answers, and the date you last confirmed them.
A Profile that asks one thing at a time.
Guided fill asks for the facts applications need most, one question at a time, and skips what is already on file.
Send the file as one link, and see it opened.
A hospital or payer gets your file, not twelve attachments. You see when it is opened. Their staff office can comment on what it sees, and if the link has expired, ask you for a new one from the same page.
For credentialing offices.
If you onboard providers rather than being one, the same file works from your side.
Your roster, ranked by what is at risk.
Providers are sorted by expired and expiring licenses, certifications and malpractice cover, and by what is missing, not alphabetically. Each line says who has to act.
What an administrator does shows in the provider’s Activity.
Opening a provider’s record, or changing their role in your organization, is written to that provider’s own Activity.
Send your checklist the way you do now.
The provider drops your request email and blank forms into Qdential. It becomes one checklist against their file, and comes back to you as one link.
You can’t yet send a request from inside Qdential. For now, the provider brings yours in.
Providers, most at risk firstSample
- Dr. Aisha MensahDEA registration expired 3 days agoProvider acts
- Dr. Lin ZhaoMalpractice cover ends in 12 daysProvider acts
- Dr. Marcus ReedBoard certificate not on fileProvider acts
- Dr. Priya RamanNothing expires in the next 90 days
What we can actually show you.
No badges we have not earned. These are properties of how the system is built.
Every change to your record is logged by the database itself.
Each change shows in your Activity with who made it, written by a database trigger rather than by the app.
Your rows are yours, in the database itself.
Every query is scoped to you by row-level security, not by application code that could forget.
Administrators leave a trace.
Opening your record or changing your role in an organization appears in your Activity.
Two-factor sign-in on every account.
Available to everyone, not an add-on.
Encrypted in transit and at rest.
The documents themselves, not only the database rows.
Read only to fill your forms.
Documents are read by an AI service under a no-training agreement, only to fill your forms.
Start with the license in your desk drawer.
Qdential is invite-only for now. Tell us who you are and where you practice, and we will send an invitation.