Patient Management Dashboard
- Form for adding patients
- Patient dashboard
- Search patients
Bonus:
- Login page
Store patients and users
Patient |
---|
ID (generated, primary key) |
First Name (required) |
Middle Name |
Last Name (required) |
Date of Birth (required) |
Status (required) |
Address |
Other |
Contact?
User |
---|
Email (primary key) |
Password (encrypted |
Google Forms - Google Sheets
Python3 - Flask application
Database - SQLite
HTML - Bootstrap
Flask - Python
Searching with SQL vs. searching in memory with Python
Text search through every field vs Search each option individually
SQL vs NoSQL vs Elasticsearch
Database | Pros | Cons |
---|---|---|
SQL | - SQL filter and queries - Separate tables |
- Not great for text search - Requires structured schema and data |
NoSQL | - Good for unstructured data (Others field) - Scalability for access and queries |
- No data schema |
Elasticsearch | - Text search | - Expensive |
Frontend - React Backend - Typescript - Node.js Database
- Unit testing
- Buggy HTML
- Database encryption for password
- Search - full text search through all fields and return any match?
- Others - JSON + add fields individually (text?)
- Exact match?
- Partial match?
- Search box, filtering
- Templates and design
- Account creation and verification and change password
- Changing patient details/deleting patients
- OAuth
Scalability of database:
- Will a single table be sufficient in the future?
- Do fields need to be split into various table? (one-to-one or potentially one-to-many mappings)
- Availability of data