Every access, signed by the patient.
Every hospital, on the same chain.
VitalMesh is a patient-issued consent ledger for hospitals. An unconscious patient rolls into a hospital they have never visited. Verified clinicians decrypt six months of signed grants with their credentials, a 1-of-3 multi-approval opens access when the patient can’t, and every read is appended to a tamper-evident ledger.
- DPDP Act §14
- SHA-256 audit chain
- 6 hospitals live
Consent, bridge, audit chain.
Three things, done well. The patient issues consent. The hospital reads it. Every read is recorded on a tamper-evident ledger.
Patient-issued consent
Every grant is a W3C Verifiable Credential signed by the patient wallet. Hospitals verify the signature on every read; they cannot mint or replay a grant.
24-hour cross-hospital bridge
A referral used to be a PDF. The bridge is an HMAC-signed channel that the receiver hospital opens against the ledger. The token rotates on first open, so a leaked string is worthless.
Hash-chained audit ledger
Every access is appended to a tamper-evident chain. Each row carries the previous row’s hash, and we pin each row to Solana devnet so the chain is verifiable from any device.
15-second AI risk loop
The risk-score engine runs against the patient’s rolling vitals. Unconscious patients trigger a 1-of-3 multi-approval so a verified clinician at another hospital can open access in under a minute.
How a read happens.
Cross-hospital bridge.
The patient authorises a 24-hour bridge from their dashboard. The receiver hospital opens an HMAC-signed stream against the ledger; the token rotates on first open so a captured link cannot reconnect. Revocation propagates within one second.
Pricing.
Three plans, billed in Bangladeshi Taka. Free for one patient.
For one patient. Signed consent, your own audit log, six months of history.
Family viewer accounts. Multi-approver right-to-erasure. 10 on-chain publishes per month.
Verified-clinician dashboard, AI risk loop, 1-of-3 emergency pipeline. Annual invoicing.
Questions we hear before the contract.
If yours isn’t here, write to hello@vitalmesh.health.
01Who owns the consent grant — the patient or the hospital?
The patient. Every grant is signed by the patient wallet at issue time and held in a hash-chained ledger. Hospitals verify the signature on every read; they cannot mint a grant without the patient wallet signing it. Family accounts may co-sign, never replace, the patient signature.
02How does the cross-hospital bridge differ from a referral?
A referral is a one-shot document. The bridge is a 24-hour HMAC-signed channel: the patient authorises it once, the receiver hospital opens an SSE stream against the ledger for the duration, and the token rotates on first open so a leaked string is worthless. Revocation is instant from either side.
03Why hash-chain the audit log — isn’t a database enough?
A database row is mutable. The chain pins every row to the previous row’s hash, so any tampering with a historical entry breaks the link and surfaces the moment integrity is checked. We additionally pin each row’s hash to a Solana devnet memo so the chain is verifiable from any device.
04Why is the Hospital plan priced this way?
A 100-bed ICU averages ৳1.2 Cr/month in monitoring when done traditionally. The ৳14,000 Hospital plan covers the AI risk loop running 24/7 for every admitted patient, per-event Solana anchoring, and the audit chain — a 99.6% cost reduction on the legacy baseline.
05How long does hospital onboarding take?
Two weeks. Week 1: SSO setup, EHR/HIS webhook integration (HL7v2 + FHIR R4), clinician roster import. Week 2: shadow-mode runs where our AI risk-score sits alongside your existing triage for comparison, then a one-click cutover.
06Can family members see my data without my consent?
No. Family accounts default to zero access. The patient must explicitly grant a viewer (with an expiry — typically 7 days) and can revoke at any time. Revocation is itself appended to the audit chain so the family cannot quietly retain old data.
07Can we run a pilot before committing to a Hospital plan?
Yes. The 30-day pilot is free of charge, full Hospital plan access, with a dedicated onboarding engineer. If you decide not to roll forward at the end, we export all your data — audit log included — and shut down the org. No charge.
- Patient wallet signs every grant
- AES-256 envelope encryption at rest
- Hash-chained audit ledger, Solana-anchored
- DPDP Act §14 data residency
- 1-of-3 multi-approval for unconscious patients
- Argon2id passwords, rate-limited endpoints