-
Notifications
You must be signed in to change notification settings - Fork 1
User Journeys
Shreya Pandit edited this page Dec 19, 2017
·
2 revisions
User Journey 1: Create Reference Exercise (Client and server)
- User comes into clinic and clinician signs him up using Anchor web app.
- Clinician logs into Client (Electron app) using his/her anchor credentials [M]
- Anchor should send back list pf patients
- Clinician chooses a patient [M]
- Clinician sees a page to select exercises [M]
- Exercise created in stages ; each stage includes marking of all 12 joints to create a skeleton for each stage. Helpful to practice and compare later [M]
- Clinician submits exercise
User Journey 2: Practicing an exercise at home (Client and server)
- User logs in with patient account
- Anchor sends back list of exercises added for the patients.
- User sees list of available exercises created for him/her and selects one. [M]
- User sees a skeleton for each stage. Once in green circle, match your joints with skeleton to proceed to the next stage. Match score is calculated and stored at each step [M]
- Once at final stage, calculate an average match score and POST to anchor
User Journey 3: Clinician reviewing exercise in clinic (server side)
- Clinician logs into anchor
- Goes to View Exercise page and selects a user email.
- Sees a list of active exercises as [
Squat
,View Details (Link)
] [M] - Maybe a click on the row can open a pane with grid comparison at the bottom? [M]
- How should our grid comparison ideally look like? Could be bar chart too for the MVP, each bar showing overall match score for that run? [M]
- Clicking View Details shows more details on each exercise (Later, not MVP)