Skip to content
A full-stack app for patients and doctors to track pain and strength progress during knee recovery
JavaScript HTML CSS
Branch: develop
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
config/passport
controllers
models
public
routes
test
views
.eslintrc.js
.gitignore
.travis.yml
README.md
package-lock.json
package.json
server.js

README.md

Patellr

Patellr is a full-stack app built to track the progress of patients as they recover from knee pain. It's intended to help boost the morale of and set goals for those going through physical therapy, and it could also provide doctors and insurers with quantifiable data to determine next steps for care.

Table of Contents

Dependencies

Back End

  • Sequelize (to handle queries to the MySQL database)
  • Express (to handle basic routing on the back end)
  • Express Handlebars (to tie our express routing to the Handlebars view engine)
  • Express Session (to help track user status from page visit to page visit)
  • Passport JS (to handle authenticated routing on the back end)
  • bcrypt (to handle the hashing, salting, and decrypting of user passwords during authentication via Passport)

Front End

  • Chart JS (to chart out user data on a nice-looking line graph)
  • Moment JS (to work with the formatting of timestamp data before it's printed to the chart)
  • Axios (to make GET and POST requests to the server)

How It Works

Front-end usability of Patellr is straightforward. A user either logs in from the login page or signs themselves up as a new user from the sign-up page. Thanks to Passport on the back end, each user's unique user page can only be accessed once the user has been authenticated. And, thanks to Express Session, once signed in, a user can navigate away from their user page and return without having to sign in twice.

Once a user is on the user page, their data (or lack of data, if they're visiting for the first time) appears instantly.

A successful login

Then, they simply input their latest pain and strength levels (as well as the location of the pain) and submit it to update the page and see how their latest data fits with past updates.

A successful update

If a user tries to login with an invalid username or password, or if they try to sign up with an existing username, they will return an error and be prompted to resubmit.

A failed login A failed sign-up

Future Plans

Editing of User Entries

The Patellr MVP appropriately and successfully logs each update for each user, but at the moment there's no option for a user to update an entry if they've misclicked. A future release of the site will provide appropriate controls on the front end and verified routing on the back end to allow for such updates.

Progress Tracking for Other Body Parts

Knees aren't the only parts of the human anatomy that commonly need rehabilitation. Future versions of Patellr could track the location and severity of pain for the elbow, the hip, the lower back, and more.

Password Resetting

Currently users cannot reset their passwords once they've created them. New authentication routing and new Passport strategies will need to be created for the hashing of new passwords for existing users.

Admin Access

The current version of Patellr is built solely for patients, allowing them to update with their latest recovery progress. Eventually the app will include admin privileges for doctors or insurers needing access to all patient data, and a new admin page will be created to easily access that data.

You can’t perform that action at this time.