Trust & Verification
In design — architecture definedEstablish trust with the right level of verification for each interaction.
Trusted identity signals with proportionate assurance
Identity and verification capabilities help distinguish an account, a claimed identity, a verified contact channel, an organization affiliation and a credential-backed assertion. These are not interchangeable. DISHA 4.0 HCOS™ should apply proportionate checks based on the risk and purpose of a workflow, communicate what has been verified, and avoid collecting identity evidence that is not necessary.
See how identity, contact, organization and credential verification differ—and how each can support safer access.
Trust levels and verification flows are specified; provider integrations are not yet live.
In depth
Identity is not a single status
An account identifier confirms how a user accesses a service. Email or mobile verification confirms control of a channel at a point in time. Organization verification may confirm affiliation or role. Credential verification checks a specific issuer claim. Higher-assurance identity proofing, where justified, is a separate process with stronger obligations and controls.
Assurance matched to purpose
Low-risk personalization may need only an authenticated account. A professional profile badge may require confirmation from a recognized issuer or employer. Access to institutional or employer workspaces may require organization-level validation and an assigned role. Sensitive actions may require step-up authentication. The product should explain the reason for each check.
Verification methods
Depending on risk, methods may include contact verification, domain or organization checks, authorized institutional confirmation, credential validation, or a specialist identity-proofing provider. The system must document method, evidence scope, timestamp, expiry or review cycle, and any limitations. No verification method should be presented as stronger than it is.
Trust status and lifecycle
Verification can become stale, be withdrawn, expire or be challenged. Maintain status history and provide a clear path to renew or correct a record. Display a concise badge with a detail view explaining exactly what was checked, by whom or by which process, and when.
Fairness and accessibility
Offer alternatives when users cannot complete a particular digital check. Do not equate missing verification with dishonesty or lack of capability. Keep review processes accessible and provide a route for human assistance when automated verification fails.
How it works
Capability domains
Frequently asked questions
Does a verified account mean every profile detail is verified?
No. Each verification applies only to the specific channel, organization, credential or identity claim checked.
What if verification fails?
The experience should explain the failure category and provide a secure retry or support route where available.
Trust & Verification
Experience it inside the live platform.
Open the module that carries this capability, or talk it through with the team.