i Demo data — synthetic only. No real PHI. No real patient information.

Walk through 5 live modules
in under 3 minutes

Sign in as a partner, open a synthetic patient case, upload a sample document, sign a versioned consent, and verify the resulting block on the ledger. Every interaction is simulated — no backend, no PHI.

01 — Partner Management

Sign in as a Partner

Pick a sample partner organisation and a role. The walkthrough simulates role-based access — the same RBAC model live partner dashboards enforce.

In progress
Roles (RBAC)
Admin Compliance Officer Care Coordinator Read-only Auditor
Click a role to toggle selection. Multiple roles can be active simultaneously.
Active session No partner selected
Region
Active role(s)
Seats
Last login
Station 1 completes when a partner + at least one role are selected.
02 — Patient Case

View a Synthetic Patient Case

A patient case aggregates every consent record, document, and event in the system. Switch languages to see the same case surface in the patient's preferred locale.

Pending
Case identifier intake
Patient name
Sample Patient A
Case ID
CASE-2026-00471
Nationality
Singapore
Age / Sex
52 / F
Procedure
Executive Health Screening
Hospital
Bumrungrad International
Patient language
String table seeded in-page. Same locales supported by core platform.
Advance workflow
Step through the case state machine.
Case timeline
Station 2 completes when the case reaches documents_collected.
03 — Document

Upload a Sample Document

Every uploaded file is hashed client-side using SHA-256 (WebCrypto). The hash is what gets anchored to the ledger — never the raw bytes.

Pending
Drop a sample document, or click to browse
PDF, image, or any file. SHA-256 is computed in your browser.
Sample bypasses drop/pick — pre-computes a deterministic hash.
No document yet
Size
Type
Uploaded
Visibility
Private (case-scoped)
SHA-256
HASH
Station 3 completes when a document is hashed.
04 — Consent

Sign a Versioned Consent

Consent templates are versioned per language. Each acceptance is hashed, sealed, and appended to the audit chain in the next station.

Pending
All three boxes must be ticked before signing. After signing, Station 5 will receive a new ledger block.
0 / 3 accepted
05 — Trust & Verification

Verify on the Ledger

Every block in the chain links back to the previous one. Click Verify on ledger to compute the verification badge ID — the public proof of authenticity.

Pending
veridoc-ledger-mainnet — blocks
Verification
Not yet verified · Awaiting notarization
Verification compute a deterministic badge ID derived from the new block hash.
What this proves
  • The signed consent exists in the audit chain.
  • The uploading partner certificate is valid.
  • No block in the chain has been altered.
  • The verification URL can be audited independently.

Ready to deploy at your hospital?

Implementation typically takes under one week. Works alongside your existing HIS & EHR. No hardware, no installs.