The problem HealTrack solves

Today, any patient carries an extra responsibility of tracking their medical reports with the fear of getting them lost. Because, if once lost, they have to again give the doctor a visit that results into a long endless cycle of delayed or inaccurate records. Patients, today, lack a control over their own records.

1. Here in this app user can view all his documents via a user friendly timeline.
   -> All the records that has been submited by user will be shown in this app in a very user friendly interface. That timeline will contain all the medical reports and medications that will make user free from his fear of misplacing the documents.

2. User can give access of their timline to the doctors they are getting treatment from
   -> Here, in the app, we allow the user/patient to register themselves and while registering they pass an address which is required by the doctor to later view, add and edit the reports. Which again make it easier for both patient and docotors by just giving access of digital records instead dealing with bulky file of medical reports.

3. Making it easy for doctors to keep a track of their patient records
   -> Doctors just need to register at our platform, and then they will be able to see and edit or add the reports or medications of their patients.

Challenges we ran into

1. While working with our app we first encounterd with the very unfriendly problem that "HOW TO VERIFY DOCTORS?"
   But somehow we came up to a solution that evey doctor has its license number. So, we decided to take and verify their license from their registered Medical Board Association.

2. Material UI: Since it was a new exprience for us to use Material UI a lot of BUGs regarding styling componts, as we were facing syntactical issue.

3. IPFS: Firslty we used third party platforms such as nft.storage and pinnata but they didn't work because we all are new to these thing also they don't have free course on youtube, then again we used nft.storage and resolved the issue using docs.
   4.while deployment of the website tried to deploy on ipfs using fleek as other deployment platforms were paid but fleek was not able to redirect to routes so thought of using netlify but same happened with netlify after doing some reserch about the error got to know about it that netlify was not able to locate the index.html file which was in build directory so had to make a netlify.toml file which positions index.html and then it worked properly