For issuing organizations
For training, credential and other issuing organizations. Bring one record type, and we’ll work through where it comes from, how it changes, who may receive it and how a person gets it corrected.
ExampleThe short answer
What an issuer agrees before a source is connected.
Before connecting a source, agree the record type, the issuing authority, the source identifier, who may receive the record and why, how renewals and status changes work, the correction route, and what evidence a recipient gets. The issuer stays responsible for its record; a recipient makes its own decision about it.
A first conversation needs five answers. Use a made-up example, and please don’t send personal records through the contact form.
The issuer and its authority
Name the issuing organization and why it is the right source for this record.
The record and its status
Describe the record type, its source identifier and how its status changes.
Who may receive it, and why
The recipient’s permission and the purpose it may be shared for.
Corrections and changes
How a person corrects a mistake, and how a changed or revoked record is passed on.
Who owns the source system
The owner of the source system, and the evidence a connection would return.
ExampleThe issuer is responsible for its own record. A clinician controls who may see their career information. An employer keeps the decisions that belong to it. A source connection never turns one party’s authority into another’s.
ExampleWrite down how the issuer changes a status, how a person asks for a correction, whether a recipient must be told, and who owns each answer.
Step 1
A status changes
The issuer records a renewal, an expiry or a revocation in its own system.
Step 2
A person asks for a correction
They know whom to ask, and the issuer owns the answer.
Step 3
The source record changes
The correction is made at the source, not in a copy of it.
Step 4
Recipients are told, where permission holds
A correction changes the record. It does not decide an employer’s or any other organization’s outcome.
ExampleWe need to agree the record, the source terms, the technical path, recipient permissions and the correction process. This page does not enroll an issuer, upload records or set up a live connection.
One record type
Define one record type and its authoritative source.
Changes, written down
Write the correction, revocation and renewal processes.
Recipients and purposes
Name who may receive the record, and for what.
Evidence and owners
Agree the evidence, security and owners needed before a connection is discussed.
What should an issuer prepare before a source connection?
Document the record, the issuing authority, the source system, how status changes, the recipient’s purpose, the correction contact and the technical owner. Use a made-up example for an early conversation, and don’t send personal records through a general contact form.
How should renewals and corrections be communicated?
Name who can change the source record, how a person asks for a correction, how a changed or revoked record is shown, and which recipient permissions stay valid. A source update is not an employer decision.
Does this page connect an issuer?
No. This page doesn’t enroll an issuer, accept records, set up a connection or give any organization authority over another party’s record. It starts a conversation about one record type.
Start an issuer conversation