Issuer
Covered entity / clinical issuer
The issuer binds the consent and clinical attestation locally before producing the proof.
Illustrative ZK disclosure scenario · Not a HIPAA certification
HIPAA / ZK credential
Patient consent, proven without the PHI
An illustrative patient-consent / clinical-attestation proof against HIPAA's minimum-necessary boundary: a payer or clearinghouse verifies a scoped claim while the clinical witness stays with the issuer.
Scope note: Illustrative scenario only. It shows a possible proof shape for partner discussion; it is not a HIPAA certification, legal advice, or a compliance determination.
Concrete ZK disclosure scenario
Consent for prior authorization, proven at the edge
The issuer holds the signed consent and clinical record as the private witness. The proof carries the minimum public facts a payer or clearinghouse needs to verify a defined treatment claim.
Private witness
Signed patient consent + clinical record
Private witness held by the issuer; no PHI enters the proof envelope.
Public statement
patient_consent = valid
prior_authorization · outpatient_mri_imaging
Public proof envelope
Expiry-bound, revocable proof envelopepolicy =
Published HIPAA minimum-necessary policypolicy_hash =
0x7c4e…91b2
claim_type
patient_consent
claim_purpose
prior_authorization
claim_class
outpatient_mri_imaging
consent_validity
valid
policy_hash
0x7c4e…91b2
expiry
bounded validity window
revocation_state
unrevoked / re-checkable
proof_validity
true
Verification result
Payer / clearinghouse
valid = true · policy_hash matched · disclosure_boundary = sealed
The verifier re-checks the proof against the published policy hash and the current revocation state. The clinical witness is never returned with the decision.
Issuer → partner narrative
Bind locally. Verify remotely.
The covered entity or clinical issuer binds and proves the signed consent and clinical attestation locally. It sends the payer or clearinghouse only the proof and the minimum public claim fields needed for the prior-authorization decision; the underlying clinical witness never leaves the issuer boundary.
Wire shape
proof + minimum public claim fields
The disclosure boundary
The verifier gets a decision, not a chart.
What the verifier learns
Scoped, policy-bound outputs
The verifier learns that a patient_consent claim is valid for prior_authorization and the defined treatment class, against the published policy hash, within its expiry and revocation rules. It can verify the proof without receiving the witness.
What remains sealed
No PHI crosses the partner boundary
Patient identity, patient identifiers, diagnosis, chart, clinical notes, the full consent document, and other PHI remain sealed inside the covered entity or clinical issuer.
Credential type
A ZK credential for a minimum-necessary claim.
ZK
patient_consent_v1
A zero-knowledge credential lets a clinical issuer prove a scoped consent claim against a published minimum-necessary policy hash. The proof is revocable and re-checkable without turning the issuer into a PHI relay. See the PrivacyCore™ agent identity explainer for the underlying privacy-rail primitive, and read the FHE workflow for sensitive agent-side computation over regulated inputs.
Partner POC
Make the regulated claim verifiable, not visible.
Use the partner spec to map the issuer boundary, public policy fields, and verification flow for your own regulated workflow.
← Back to Regulated Verticals