From button in the chat page on the doctor side, triggering the following:

• set the 'isActive' field in the consultation entity (not created yet, check issue #73 before doing this one!) to 'false'
• redirect the current user (doctor) to the patient queue page (for now. Later, may redirect to a page for adding notes)
• push the update to the patient user so that they are redirected to the 'rating' page (a job for socket.io ?)

• install all the packages.....
• tsconfig
• eslint
• prettier (?)
• mikroORM config
• .env template if necessary
• Anything else?

• check anywhere else that may be affected by the change

In the update patient resolver, we don't hash the updated password, so the unhashed version is saved in the DB.

It also means that when the user next tries to login with the new password, they cannot as bcrypt compare returns false.

Page 7 in the wireframes, route /consultation/symptoms

Should include the pain slider + other inputs - see here: https://docs.google.com/document/d/1tDUUFW_PT72W5R1m3k29uugzN6yh-bEdyNOCKmM-OOU/edit#heading=h.23un7wczrfwr

• Allow saving messages from livechat to database
• Ensure that users can only see messages sent to/by them

this is an issue

Should be a different route/different page from the patient login to avoid issues

For Tuesday's standup

From the 'logout' button in the rating page, triggering the following:

• delete refresh token/any other authentication step
• redirect user to the login page

Already done.

When the patient enters the doctor code, the backend needs to check the code is associated with an exisiting doctor in the DB.

When receiving a doctor code from the FE, check that the doctor exists and send back true/false