Verify practitioner credentials

Overview

Hospitals and clinics can verify a visiting practitioner’s credentials instantly using verifiable, issuer-signed claims.

The hospital does not need to manually chase every regulator or training body before a practitioner can provide care. It needs to know whether the presented licenses, registrations, and certifications are trusted and current.

Why it matters

Credential verification is critical to patient safety but often slow and manual. In time-critical or remote settings, delays can affect access to care, while weak checks create clinical, legal, and reputational risk.

Verifiable Credentials create a cleaner model:

• regulators and training bodies issue trusted practitioner credentials
• practitioners carry evidence in a wallet
• hospitals verify status and scope of practice at onboarding or arrival
• access decisions can be audited without re-collecting source documents

Ecosystem roles

• Issuer: Regulatory bodies and training organizations issuing certifications.
• Holder: The practitioner storing credentials in a wallet.
• Verifier: The hospital or clinic validating credentials on arrival.
• Trust governance: The rules that define accepted regulators, credential types, scope of practice, status checks, and exception handling.

Trust decision

The verifier decision is narrow: can this practitioner provide this type of care at this facility right now?

That decision may depend on registration, certification, specialty, scope of practice, facility policy, expiry, and status.

Privacy and assurance

The verifier should request only credentials needed for the clinical role and facility access decision. It should not need unrelated employment or personal history.

Assurance depends on checking issuer trust, status, expiry, scope of practice, and binding between the practitioner and credentials.

Implementation notes

• Separate license, specialty, training, and facility-access claims where different issuers control them.
• Define emergency and temporary access processes without bypassing auditability.
• Keep verification results available to clinical governance and access control systems.
• Include fallback handling for unsupported issuers, expired credentials, and manual clinical governance review.

Objective

Enable a hospital to verify the credentials of a visiting practitioner.

Description

A visiting practitioner presents license and certification credentials so the hospital can confirm scope and eligibility.

Actors

Visiting medical practitioner; regulator; training body; hospital or clinic verifier.

Dependencies

The practitioner holds relevant certifications in their wallet, and the hospital can check issuer trust and credential status.

Preconditions

The visiting practitioner is expected to provide health care services at the hospital.

Postconditions

The hospital permits, denies, or escalates the practitioner's access based on verified credentials and policy.

flowchart LR
    REG@{icon: "tabler:scale", label: "Regulator", pos: "b"} -->|Issues license VC| WAL@{icon: "tabler:wallet", label: "Wallet", pos: "b"}
    EDU@{icon: "tabler:certificate", label: "Training body", pos: "b"} -->|Issues certification VC| WAL
    WAL -->|Presents credentials| VER@{icon: "tabler:hospital", label: "Hospital / verifier", pos: "b"}
    VER -->|Status check| REG2@{icon: "tabler:book", label: "Credential registry", pos: "b"}

sequenceDiagram
    participant Regulator
    participant Trainer as Training body
    participant Wallet
    participant Practitioner
    participant Verifier as Hospital / verifier
    participant Registry as Credential registry

    Regulator-->>Wallet: Issue license VC
    Trainer-->>Wallet: Issue certification VC
    Practitioner->>Wallet: Stores credentials
    Practitioner->>Verifier: Present license + certification
    Verifier->>Registry: Check status
    Registry-->>Verifier: Valid
    Verifier-->>Practitioner: Access granted