Question 1

What is Veridoc and what problem does it solve?

Accepted Answer

Veridoc is an AI medical concierge with a blockchain-verified chain of custody for cross-border patient consent. The problem we solve is that paper consent forms are not legally defensible across jurisdictions — a Thai patient treated in Bangkok whose records are interrogated by a U.S. payer has no auditable proof that the consent was informed, in-language, and unaltered. Veridoc captures every consent event as a cryptographic record that any auditor, regulator, or insurer can independently verify.

Question 2

How does notarized consent submission work end-to-end?

Accepted Answer

The patient receives a one-time consent link tied to a specific consent record. They review the form — in their preferred language — review it, and sign with a cryptographically-bound e-signature (21 CFR Part 11). At the moment of signature, Veridoc computes a SHA-256 hash of the consent payload and appends it to a tamper-evident hash chain anchored on the public ledger. From that moment the record carries an immutable proof that the exact form version was reviewed and signed at the exact timestamp from the exact device.

Question 3

What does the chain-of-custody proof show a verifier?

Accepted Answer

Anyone with the record link can render a public audit view showing the consent payload, the cryptographic hash anchoring it on the chain, the form version signed, the timestamp, and the device/IP context. The proof is independently verifiable — a verifier does not need to trust Veridoc, only the cryptography and the chain. You can inspect a sample record at https://veridoc.health/verify/0 to see exactly what a counterparty sees when you send them an audit link.

Question 4

Who is allowed to verify a Veridoc consent record?

Accepted Answer

Verification is public-by-design — anyone holding the record link can render the audit view. That is the point: the proof is strongest when it does not depend on trusting Veridoc. In practice, verifiers fall into three groups: the patient's payer or insurer disputing a claim, a regulator or licensing body auditing cross-border care, and the patient's home physician coordinating aftercare. Every public load of a record is itself logged in our audit log; the chain-of-custody details are explained in our https://veridoc.health/resources article hub and partner directory at https://veridoc.health/partners.

Question 5

What happens when a hospital voids a previously issued consent?

Accepted Answer

Consent records on Veridoc are insert-only — once notarized, the record cannot be edited or deleted. A void is itself a new event appended to the chain: the issuing hospital issues a signed revocation event referencing the original record, with the clinician identity, timestamp, and reason. From that moment, anyone verifying the record sees both the original notarized consent and the revocation trail. Voided records stay in the chain as evidence; this is by design. Intake-side prevention — making voids rare in the first place — is handled in our consent flow at https://veridoc.health/consent, with the underlying immutability policy discussed at https://veridoc.health/resources.

Question 6

Where is patient data stored, and who can read it?

Accepted Answer

Patient identifiers live in a HIPAA-controlled environment under a signed Business Associate Agreement; the on-chain record carries a cryptographic hash of the consent, not the PHI itself. Access is role-scoped: the patient sees their own record; the treating clinician sees records for their patients; the hospital admin sees records issued by their hospital; auditors and counterparties see only what the public record link exposes. Our full controls breakdown is in the HIPAA consent checklist at https://veridoc.health/resources/hipaa-consent-checklist.

Question 7

How does a patient get a copy of their own consent record?

Accepted Answer

Every notarized consent is assigned a numeric record id at the moment of signing. The patient receives that id (and the matching audit link) at submission, so they always have a permanent reference to their record regardless of what happens to their email or hospital portal. To render their record in plain language — hospital, procedure, signed-at timestamp — they visit https://veridoc.health/r/0 with their actual id substituted in; to render the full audit view (hash chain, device, form version) they visit https://veridoc.health/verify/0. The record id IS the auth token: anyone holding the URL sees the same fields the patient sees.

Question 8

How can a hospital get onboarded as a Veridoc pilot?

Accepted Answer

Pilot onboarding begins with a signed Business Associate Agreement and a short scoping call to confirm your hospital's consent flows, EMR integration points, and target languages. Implementation typically completes in under a week — including a parallel-run period where digital and paper consent coexist. Start by booking a demo at https://veridoc.health/demo to see the platform on your own procedures, then visit https://veridoc.health/partners for the pilot-application flow and partner-agency terms.

Veridoc FAQ