Skip to main content

Credentials

The 361 days that are not exam day.

Illustrative example: a credential's record on the public register, as anyone who checks it by number sees it: Clinical Standards Professional, awarded by Meridian Certification Board, credential MCB-24861, effective 24 Sep 2026, expiring 24 Sep 2029, current and verified, checked 24 Sep 2026 at 15:02 UTC; behind it, its Open Badges 3.0 badge, signed and checkable by anyone; in front, the certificate, whose QR code opens this record.

Ask any small board what takes their time and the answer is never the examination. It is renewals, continuing-education claims, the member who let a credential lapse, and the employer on the phone asking whether somebody is really certified.

01 The public register

Verifiable by anyone, controlled by you

  • A credential carries a number, an effective date, an expiration date, a status and its program
  • Verifiable by number at a public address from the moment it exists
  • Listed publicly only with the holder's consent
  • Every result says it reflects the record at the moment it was requested

A credential carries a certification number, an effective date, an expiration date, a status and the program it was awarded under. Anyone can verify it by number at a public address, and the result states plainly that it reflects the record at the moment it was requested — which is the honest thing to say and the thing that makes a verification defensible later.

Whether a credential appears in the searchable public listing is the holder's consent, not the body's assumption. A credential is verifiable by number from the moment it exists; it is listed publicly when the holder agrees. Employers and licensing boards check a credential the same way, without an account and without asking anyone.

02 Certificates

On paper, with a way to check the paper

  • A certificate design per program, or one default: heading, wording, one or two signatories, an accent color, a footer note
  • A design is published in versions and never rewritten
  • The PDF carries a QR code that opens the verification page for that exact certificate
  • Issued once; reissued only when something printed on it changes

A holder downloads a certificate for a credential in force: the holder's name, the credential number, the program, the dates, the signatories, and a QR code that opens the public verification page for this exact certificate. Your body designs it — per program, or one default for all — and publishes the design in versions, so a certificate printed last year is still the certificate it was.

The first download issues the certificate and records the snapshot it was printed from, with the hash of the file. A later download returns the same certificate unless something printed on it has changed — a renewal moved the expiry date, a name was corrected, a new design was published — and then a new certificate supersedes the old one, on the record.

03 Digital badges

Open Badges 3.0, signed, checkable by anyone

  • An OpenBadgeCredential (Open Badges 3.0, Verifiable Credentials 2.0), signed as a compact JWS
  • Names the body as issuer and the program as the achievement; identifies the holder by a salted hash, never by email or name
  • Revocation on a status list anyone can check
  • The platform's signing keys rotate; retired keys keep verifying what they signed
Illustrative example: an Open Badges 3.0 credential as a verifier reads it: issued by Meridian Certification Board for Clinical Standards Professional, the holder identified by a salted hash, signed as a compact JWS; its revocation is on a status list anyone can check.

A holder downloads a digital badge for a credential in force: a signed Open Badges 3.0 credential a wallet, a learning record or a profile can hold, and that any verifier can check without asking Qualeron for permission. The badge names your body as issuer, the program as the achievement and the credential number as the license number; the holder is identified by a salted hash of their sign-in email — never the email itself and never their name — so a badge passed around says nothing a stranger could use, while a verifier who knows the email can confirm it is theirs.

A badge is issued once and reissued when the facts change, with one stable subject across reissues. Revocation is on a status list anyone can check. The platform signs on your behalf with keys it rotates on a schedule; a retired key keeps verifying the badges it signed. Native badges are included in every plan; there is no separate badge provider to buy.

04 Renewal

The cycle runs on the policy you publish

You publish a renewal policy with a version: the cycle length, what a renewal costs, what a late renewal costs, how much continuing education is required and from whom, whether an attestation is needed, how long the grace period runs and how far ahead of expiry the cycle opens. Holders are moved through it on that schedule rather than by somebody remembering, and reminded as the dates approach.

The policy is versioned because a cycle that opened under last year's rules has to finish under them. Changing what you require in March cannot change what you asked of somebody who started renewing in January. Renewal fees are paid through the same checkout as everything else, on your own account.

  • A versioned policy: cycle length, the fee, the late fee, the CE required and from whom, attestation, grace period, how far ahead the cycle opens
  • A cycle that opened under last year's rules finishes under them
  • Holders are moved through it on schedule, with reminders

05 Continuing education

Claims, approved providers, provider reporting and a real audit

  • Holders claim hours against their cycle; you decide whether hours must come from approved providers
  • An approved provider can report completions directly with its own key
  • A configurable percentage of renewals is audited against evidence
  • A credit can be reversed, with a reason, and the ledger says so

Holders claim continuing-education hours against their cycle. You decide whether hours must come from providers you have approved, and you maintain that list. An approved provider can report completions directly — with a reporting key of its own — so a credit lands on the certificant's ledger accepted, with the report it came from, rather than after someone at your body reads an attached certificate.

A configurable percentage of renewals is selected for audit, and an audited renewal asks for the evidence behind the claim before it completes. A percentage audit is the part most systems skip, and it is the part an accreditor asks about: a renewal requirement nobody verifies is not a requirement. A credit that should not have been accepted can be reversed, with a reason, and the ledger keeps both entries.

06 Lapse and reinstatement

A road back, on your terms

  • A credential that is not renewed expires; the record stays and verification tells the truth about it
  • Reinstatement has your own fee and your own conditions, and is recorded as what it was
  • One credential is in force at a time; a newer one supersedes rather than overwrites

A credential that is not renewed expires rather than disappearing — the record stays, the status changes, and verification tells the truth about it. An expired credential has a governed road back through reinstatement, with your own fee and your own conditions, and the reinstatement is recorded as what it was.

A newer credential for the same person and program supersedes the one in force rather than silently overwriting it, and any renewal cycle or reinstatement still open against the old one is closed as part of the same act. One credential is in force at a time, and the history of how that came to be is intact.

Ask about moving your register

Tell us about your program.

Tell us how many candidates you certify and what you run today. You will get a written quote against the published plans — not a discovery call before a number.

Privacy choices

Control optional diagnostics and site-journey measurement. Essential technologies remain active when needed to provide a requested function.

Essential technologies

Authentication, CSRF and form security, anti-abuse controls, checkout and payment integrity, privacy-choice storage, and interface state you asked for.

Always active

Optional diagnostics

Limited client-error events and first-touch, form-journey measurement used to find broken experiences and improve the website. Not advertising.

Advertising and cross-context behavioral tracking

Qualeron does not deploy targeted-advertising cookies or cross-context behavioral advertising trackers on qualeron.com.

Not used

Read Privacy & Cookies