GENEXTMedEd FoundationLearn • Collaborate • Elevate

CERTIFICATE VERIFICATION

Completion should be independently traceable.

Each issued programme-completion certificate should map to a controlled institutional record so authenticity and the scope of the educational programme can be checked without relying on an image of a certificate.

VERIFICATION RECORD

What a valid record should confirm.

Unique certificate / record ID
Learner name
Programme title
Programme type
Host centre / institutional setting
Programme dates or duration
Completion status
Issue date
Authorised institutional record status
Verification result: valid / revoked / superseded / not found
PUBLIC BOUNDARY

Verify authenticity without exposing the learner file.

Public verification

Returns only the minimum information needed to establish whether a certificate corresponds to an institutional completion record.

Controlled academic record

Application documents, detailed assessments, logbook entries and mentor notes remain access-controlled and are not part of public verification.

Scope statement

A verified certificate records completion of the stated educational programme; it does not confer statutory registration, specialist qualification, employment credentialing or clinical privileges.

LIFECYCLE

Issuance is the final step of a controlled chain.

01

Completion review

Programme requirements, assessments, attendance and required sign-offs are reconciled.

02

Authorisation

The completion decision is approved according to the programme’s institutional process.

03

Record creation

A unique verification ID is generated and bound to the controlled completion record.

04

Certificate issue

The certificate displays the verification ID or QR destination.

05

Future verification

The public service returns the current record status, including any later revocation or supersession.

Public lookup will activate with the secure registry.

The verification architecture is now defined; searchable records should go live only after authenticated issuance and controlled registry storage are implemented.

Return to Fellowships