Skip to content

Home

Jump to bottom
Vikas Kedia edited this page May 6, 2020 · 8 revisions

Welcome to the healthbrain wiki!

Milestone 1

4th may meeting

  1. Doctor loads patient 1 and then patient 2. Then comes back to patient 1. When doctor comes back to P1 the data should come from Local storage and an API fired to get a new JSON back.

  2. In the right hand side when the doctor gives the "recommendations" command and I load the recommendations panel the data should come from local storage and an API fired to get a new JSON back.

Currently the persistant state works that takes care of localstorage giving fast data in case of page reload. But point 2 is about page already loaded and then an API being fired.

  1. Do not allow user to change style from the UI. The style choice will be from a completely separate existing "user preference" application. Only make a DB query and show the style that is returned.

  2. Comment the code so that angular developers on my team can understand.

Goals analysis:

Goal 1: Done

Goal 2: Done

Goal 3: Done

Goal 4: Todo point 2 above

Goal 5: Done

Goal 6: Alexi recommends not to use a library: VK to discuss with his team.

Goal 7:A says style can be imported using the import function. hence not needed.

Goal 8: Decided not to do it.

Goal 9: Done

Goal 10: Done

Mile stone 2

  1. login / authentication. JWT. Also need to send token for API calls.

  2. socket. VM1 "DA" adds a "Rex". On VM2 "D" gets the new Rex. Each component has its own channel with the name of channel being recommendation-patient-id-1

  3. optimistic writes - need to decide - A to decide if we do this or not.

  4. Features shown in first 3 minutes of the video: https://youtu.be/8OSUI2Z17Lg A. search component. B. chat interface for the right hand side cards. Up and down arrows. Each data row has actions that can be invoked by KB. The card header actions can be invoked by KB.

  5. layer 2 popup having siblings like in current code. Like in the demo video. Siblings involved either through KB or mouse. Look at the video for 4th may

  6. laravel 7.7 / mysql for recommendation component.

Mile stone 3 (Evolving)

  1. One component contains other components

  2. Code review for 25 components and implement improvements to the architecture if discovered during writing components.

Mile stone 4 (Evolving)

Code review for 25 components and implement improvements to the architecture if discovered during writing components.

Mile stone 5 (Evolving)

Code review for 25 components and implement improvements to the architecture if discovered during writing components.

Clone this wiki locally