ZK-TLS healthcare AI proof receipts
A healthcare AI proof receipt should expose enough metadata for auditability without exposing the underlying clinical payload. Rapha Protocol uses source-integrity concepts, deterministic hashes, and Polygon mainnet anchoring to make selected commitments public.
What a receipt can show
- Network and chain ID.
- Contract address and transaction hash.
- Event name and timestamp.
- Execution or data commitment hash.
- A statement that raw PHI was not part of the public receipt.
Current Rapha Protocol proof anchor
Proof anchor transaction: 0xfadab8cc5e6bdb531d7ddfd64fd2a325a5dabda1c0f1eb7a21f05d15c618f9a0
Contract: 0xB27704CA8A01Bc151181D1d53E2F0eF11B39B32F
What a receipt does not prove
A proof receipt does not automatically prove clinical validity, regulatory approval, model safety, de-identification, HIPAA compliance, GDPR compliance, or Taiwan PDPA compliance. Those require separate review, controls, and agreements.
Public proof metadata is useful for audit correlation. It must not contain raw patient records, direct identifiers, private keys, or regulated production data.
Related pages: clinical AI training guide, compute-to-data overview, and technical whitepaper.