General project description on devpost.
Main server back end code is at GitLab.
- Bird's eye view of project
- Front page sketch
- Submission sketch
- Search case sketch
- API Big data page sketch
- Database overview
- legal: when is data anonimous enough? Discussion of dabase and privacy is in Google docs folder
STRUCTURE
- agree on input data required - done
- agree which data should be indexed for quick queries - done
- agree on user registration - done
- agree on structure of database - done
- agree on structure of JSON exchanged between front end and back end - done
- agree on general layout -done
FUNCTIONALITY
- landing page - done
- front end input form --- data input + - done
- front end retrival form (for medical doctors) - done
- front end retrival info (for data scientists) - done
- back end - database - done
- back end - queries from front end - done
FEEL
- front end input form --- make good design - done
- front end retrival form (for medical doctors) --- make good design - done
We need discrete inputs to ensure that data entered into the database is normalised (and hence machine searchable).
Everything on one place (at least with US approved drugs) https://clinicaltables.nlm.nih.gov/
Autocompleters API documentation Autocompleter demo page and code page
- javascript for finding codes in International Classification of Disease (ICD10) -- datasource via rest api: https://clinicaltables.nlm.nih.gov/apidoc/conditions/v3/doc.html (autocomplete search for conditions, including synonims, providing ICD10 and ICD9 codes) -- datasource WHO https://icd.who.int/icdapi/docs2/icd11ect-1.2/ and https://icd.who.int/icdapi
- javascript for finding normalised drug names -- data source: https://melclass.edqm.eu/prescriptions/list_medicines