Blockchain Medical Record System (MyMedVault)
Budget: $30 – $250 USD
I want to launch MyMedVault, a Web3 application that lets patients upload their medical-history records, encrypt them, and place the encrypted hash on the Polygon blockchain. With a patient-controlled private key, they can grant or revoke read-only access to any doctor worldwide.
Core requirements
• Blockchain layer: smart contracts on Polygon that handle record registration, access rights, and audit trails.
• Storage workflow: client-side encryption, then off-chain storage (IPFS, Arweave, or a comparable decentralized file store), with the content hash anchored on-chain.
• Authentication: users sign in with a traditional password plus their private key; no other factors are required at this stage.
• Data scope: only medical-history documents in PDF or FHIR-JSON format for this initial release.
• Doctor portal: lightweight interface where an authorised doctor can decrypt and view a patient’s shared record, with access automatically expiring after a set period unless renewed.
• Patient dashboard: upload, view sharing log, and toggle access for each record.
• Security layer: AES-256 for at-rest files, end-to-end encryption for all transmissions, and clear separation between encryption keys and storage locations.
Deliverables
1. Verified Polygon smart-contract code, deployed on testnet and mainnet.
2. React or Vue front-end (mobile-responsive) integrating MetaMask/WalletConnect for key handling.
3. REST or GraphQL backend service that links the UI, encryption module, and storage network.
4. Technical documentation and a short user manual showing the patient and doctor flows.
5. Post-deployment support through the first production month to fix critical bugs.
Completion is accepted when a patient can:
• create an account with password + key,
• upload an encrypted medical-history file,
• share it with a doctor via generated access key, and
• see an on-chain confirmation of that access.
Core requirements
• Blockchain layer: smart contracts on Polygon that handle record registration, access rights, and audit trails.
• Storage workflow: client-side encryption, then off-chain storage (IPFS, Arweave, or a comparable decentralized file store), with the content hash anchored on-chain.
• Authentication: users sign in with a traditional password plus their private key; no other factors are required at this stage.
• Data scope: only medical-history documents in PDF or FHIR-JSON format for this initial release.
• Doctor portal: lightweight interface where an authorised doctor can decrypt and view a patient’s shared record, with access automatically expiring after a set period unless renewed.
• Patient dashboard: upload, view sharing log, and toggle access for each record.
• Security layer: AES-256 for at-rest files, end-to-end encryption for all transmissions, and clear separation between encryption keys and storage locations.
Deliverables
1. Verified Polygon smart-contract code, deployed on testnet and mainnet.
2. React or Vue front-end (mobile-responsive) integrating MetaMask/WalletConnect for key handling.
3. REST or GraphQL backend service that links the UI, encryption module, and storage network.
4. Technical documentation and a short user manual showing the patient and doctor flows.
5. Post-deployment support through the first production month to fix critical bugs.
Completion is accepted when a patient can:
• create an account with password + key,
• upload an encrypted medical-history file,
• share it with a doctor via generated access key, and
• see an on-chain confirmation of that access.