Patient portal access
Use wallet-backed identity for patient portal access.
Let a patient present supported identity data through a relying-party flow before the portal applies its normal account, consent, and authorization controls.
A password-only sign-in may not provide enough confidence for sensitive health services or account recovery.
How it works
A simple flow.
A verifiable result.
- 01
Set the required assurance
Choose an authentication flow that matches the portal’s risk, wallet capabilities, and applicable policy.
- 02
Request a wallet presentation
Ask for the required PID or other permitted evidence and let the patient approve it.
- 03
Apply portal access controls
Use the verified sign-in result alongside the portal’s account linking, authorization, and session controls.
Online identification and authentication
- Offer an alternative to password-only recovery
- Minimize identity data requested at sign-in
- Keep access decisions with the healthcare provider
OID4VP by itself does not establish an eIDAS assurance level or encrypt patient records. The credential’s assurance depends on its notified scheme and wallet; records remain protected by the provider’s own security and access-control systems.
DLBR EID verifies supported wallet presentations and returns a verification result. Credential issuance, the relying party’s decision, and sector-specific processes stay with the relevant organization.
See the EUDI Wallet Architecture and Reference Framework Opens in a new tabStart with a wallet flow
Explore a verification in your sandbox.
Test the gateway with sample credentials, then confirm issuer and wallet support for your production use case.