IDENTITY · VNEID · RAR

Digital Identity & VNeID

A model that separates authentication/SSO from QR-based data sharing and consent. Unverified endpoints, scopes and payloads are not presented as production contracts.

01 · AUTHENTICATION / SSO

Trusted Care → RAR / VNeID → Session

Capability-level flow; callback and mapping specifics remain integration dependent.

Trusted CareAuthentication request

RAR / VNeIDCitizen authentication

CitizenApproval when applicable

IntegrationCallback

IdentityAccount mapping

Trusted CareSession + audit

02 · QR SHAREINFO / CONSENT

QR at reception, kiosk or onboarding

Used where the applicable RAR/VNeID specification supports data-sharing transactions; unverified technical parameters are marked integration dependent.

Create transaction

Generate QR

Scan in VNeID

Review data / consent

Status / result

Evidence

03 · CONSENT MODEL

Who requests what, for which purpose and duration

Subject

Requester

Data

Purpose

Duration

Recipient

Delegation

Withdrawal

Evidence

Status / Audit

METRO INFORMATION DESIGN

RAR QR ShareInfo transaction and consent

rar shareinfo — Identity · Consent · Decision · Exception · Evidence

03 / RS-HUB

RS-HUB connects Trusted Care to RAR/VNeID for distinct purposes

Three journeys remain separate: SSO authentication, QR-based information sharing, and remote signing only where a verified integration applies.

SSO

Trusted Care → RS-HUB → RAR/VNeID → authentication → account mapping → session → audit trail.

QR ShareInfo

Trusted Care or kiosk → RS-HUB → QR creation → citizen approval or decline in VNeID → status → result → consent evidence.

Remote signing

Only where an approved integration applies; identity, consent, authorization and signature remain separate controls.