Data source: committed fixture snapshot (50 consent artifacts) - not a live database
The live Supabase read failed - Gateway Timeout - so the console is reading a committed fixture snapshot instead.
Everything below is computed from that snapshot by the same code the live path uses: the readiness score, the signature verification and the breach clock all run for real over these rows. Nothing on this page is a hardcoded number. Patients, hospital and incidents are synthetic, and the snapshot's signatures were generated with this deployment's demo HMAC key so the verification path is actually exercisable rather than decorative.
Treatment
We will use your medical information to provide treatment and coordinate your care.
Who consented
What was consented
How it was captured
Identity verification
Capture context
No capture-context recorded for this seeded artifact. Live captures from v1+ include hashed IP, geo, and user-agent.
Cryptographic chain
701d1c1b1a190817061504030201001f1e1d1c1b1a1918171615141312111000k8jru+GG…cjY=Audit log
(0 entries · append-only)No audit entries yet. Every view, edit, withdrawal, or supersession will be logged here in production.