MedBlock
A one stop destination for all your health needs. Decentralised Medical records to Personalised Dashboards, we have it all
Created on 2nd December 2024
•
MedBlock
A one stop destination for all your health needs. Decentralised Medical records to Personalised Dashboards, we have it all
The problem MedBlock solves
In the ever-evolving world, it was fast becoming futile to store important data of the types of a Medical Report on easily destructible commoditiies like paper. The clutter, difficulty in access and storage were just few of the problems faced here, the major ones being the Privacy and Security of the report once signed and the verifiability of a part of then report. This causes various problems to the patients, wrong diagnosis to fraud. So we propose a revamped ecosystem for onboarding the entire Medical scene of the country on a L1 blockchain layer to store the medical records. This will lead to ease of access to read the reports for the patients, because of the report being stored at the wallet address of the patient itself. We also have a novel idea of using the immutable and visible-to-all feature of the blockchain to our benefit. We are using the idea of mapping a public address to the user using wallet registration of Okto to generate unique, chain-specific wallet addresses for a given Email ID. This way the records on the blockchain will only have the public address as the unique identifier, which no one can trace back to the Patient, without his permission. Each time someone tries to access the report's function for the Patient details, the Patient needs to sign the Transaction. So the Patient has the control over the report, thus boosting security. The Mapping for Name to Public address can be similarily stored with a trustless zkEVM proofs. Aptos chain used here brings in the much-needed capabilities of Defi chain, high TPS and Move Language, wherein the modules provide a structured way to interact with functions. Overall this WebApp onbaords the Medcial domain to a platform where it is Accessible and Secure, with the familiarity being maintained as a connect between Web2 and Web3 to help easier onboarding of users.
Challenges we ran into
The foremost problem we encountered was the Migration from JavaScript to TypeScript. We had been more than familiar while building the entire thing on JS, having deployed the smartcontracts and Cross-Chain solution on EVMs before, but doing so entirely on a new environment, with using Non-ethereum chains for the first time was a daunting task. We built the smart contract in Move from ground up, using the CLI interface to deploye and all, running into various bugs and errors along the way. The next step was using the functions declared within the modules, in a Dapp to render on the Frontend. This was the last part after the ardous journey of learning Aptos and Move from scratch to build-ready. This is where we got stuck till the very end, having to go through various iterations of the code, having to change the code becuse of the unability of the code to take the normal logics of for and function/variable pass without using useNavigate and many more. It was frustrating, but in the end we did make atleast 50% of it workable in the forntend too, but alas, in development it ain't worth it if the chain isn't 100% completed for the Frontend to render without error. We have pushed all the code that we experimented and succeeded in implementing as code snippets in the repo.
Tracks Applied (2)
Build on Okto
okto
Consumer Applications
Aptos
Technologies used