Prototype issuer · Not an official DEA system

Issue a DEA registration as a verifiable credential.

This MVP-Lite site demonstrates how a DEA-style registration could be issued and verified as an SD-JWT (verifiable credential), then consumed by hospitals, plans, and registries without re-keying PDFs.

How the issuer works

The interactive demo uses synthetic provider NPIs. This issuer is designed to feed Integrity signals such as DEA revoked, enabling “Restricted” gating in the registry and privileging workflows.

Education & prevention (design reference)

Styled after the public DEA education-and-prevention theme, but tailored to show how credential issuance can support prevention goals—reducing fraudulent prescribing and improving verification at the point of care.

Reduce misuse

Credentialed registration enables verifiable identity checks before dispensing controlled substances.

Improve compliance

Auditable issuance and revocation metadata travel with the credential, not buried in screenshots.

Support integrity workflows

When a registration is revoked, downstream systems can automatically gate privileged workflows and flag the record for review.

Issuer model (VC)

The issuer produces a compact SD-JWT containing the DEA registration number, a binding to the provider NPI, and lifecycle metadata (issuedAt, expiresAt, revocation status).

Credential claims

  • deaNumber (synthetic in MVP-Lite)
  • npi subject binding
  • schedules authorized schedules
  • jurisdiction + registrantType
  • issuedAt / expiresAt / status

The demo token is not a production signature; it is shaped to support UI and policy gating in the MVP.

Why VC format helps

  • Hospitals can verify claims without re-contacting issuers for every packet.
  • Plans can surface trust posture (Active / Under review / Restricted) automatically.
  • Revocation can be expressed as an Integrity signal across systems.

This pairs with the NPVDR registry and Integrity lens rather than replacing it.

Revocation & Integrity signal

In MVP-Lite, a “DEA revoked” alert can drive downstream restrictions. The registry can reflect this as Restricted, while other high-severity signals show Under review.

Demo revocation feed

Use this toggle to simulate a revocation signal for a provider NPI. This does not touch Supabase; it is an in-memory demo action for illustrating gating behavior. 


        

      


      

        

          
Verify a DEA registration VC

          
Paste a credential token to validate the shape and see the claims this relying party would consume.