ZKlinic

What the builder shipped

ZKLinic is a ZK-native clinical trial recruitment protocol built on Midnight Network. It solves the single most expensive problem in medical research - 85% of clinical trials fail to recruit enough patients on time, not because eligible patients don't exist, but because finding them requires those patients to hand their entire medical record to a pharma company they've never met. Here is exactly where Midnight sits in the architecture. A doctor signs a structured health credential for their patient - diagnosis codes, lab values, medication history - using their on-chain registered wallet. The credential lives on the patient's device. It never touches any server. When the patient applies for a trial, ZKLinic generates a ZK proof on their device that checks their credential against the trial's eligibility criteria. That proof - containing only boolean results per criterion, no clinical data - is posted to Midnight's public ledger. The trial recruiter queries the proof ID and sees exactly one thing: this person is eligible, criterion by criterion, verified by a licensed physician, proven by cryptography. They see nothing else. What is verified on-chain: credential issuer validity, eligibility booleans, proof binding to a specific trial. What stays private: the patient's identity, their exact diagnosis, their lab values, their age, their medication history, every clinical detail that produced those booleans. The verifier is the clinical trial recruiter. What they need to see is a yes or no per criterion, backed by a doctor's signature and a ZK proof they can verify independently on the Midnight explorer. That is all they get. That is all they need. ZKLinic is not a diagnostic app. It is not a medical records platform. It is the trust infrastructure that lets a patient prove they qualify for a trial without becoming a data source for the institution running it.

Tech stack

• compact
• midnight
• nextjs
• nodejs
• typescript