-
Notifications
You must be signed in to change notification settings - Fork 7
Meeting minutes
Divleen12 edited this page Mar 29, 2024
·
56 revisions
- Progressive Web App (PWA) agreed
- Frontend: React + Next.js (to confirm Next.js)
- Backend: Express
- Styling: Tailwind (proposed by frontend team)
- Scripting/Programming: TypeScript
- Database and Deployment: Firebase
- Standard Chosen: FHIR
- Registration/Authentication/Security
-
Data Retrieval and Display (charting)
- E.g. appointments, vaccinations, lab results, medications, etc.
-
Personal Data Tracking
- Medical record, i.e., biodata, allergies, family history, past procedures, etc.
-
Push Notifications
- E.g. take your meds, go to appointment, do your exercises
- Chat with Doctor
-
Symptom Checker with AI
- Involving 3rd party is a concern? Is it secure? Consider limiting and keeping it simple.
- To reconsider after more instructions from Rigby.
-
Data Sharing with Other Users
- Possible security concern?
- How do they give/take consent to share with others?
- Privacy and protection act issues?
- Social Media Integration
- Fitness/Health Devices Integration
- READ ONLY (NO WRITING allowed to users)
- MVC (Model-View-Controller)
- Frontend: Jan, Divleen, Christina
- Full Stack: Julien, Imran
- Backend: Jonathan, Adir, Reuven, Jiayi, Xavier
- Devops: Jonathan, Adir, Imran, Reuven
- Testers: Everyone writes unit tests (Jiayi will verify testing)
- Main Debugger (First person to reach out when debugging is needed by anyone in the team): Jonathan
- Documentation: Will be decided once we know what is the required documentation and the requirements/instructions given to us.
- Research about HL7 (Health Level 7)
- Do we go with HL7? Tell your answer.
- If we don't want to use HL7, we can have our own database hosted somewhere and access data from there, acting like our own "Quebec Health Record."
Deadline to tell your answer: 14 July 2023
- Look into the clinical practice guidelines with regard to making judgments (symptom-checker feature).
- Regulations around security and logging of the data.
- A security feature like facial recognition.
- Make user stories and get the stakeholder sign-off to begin with the first sprint.
- Front-end: React + Next.js confirmed.
- Everything else remains the same for now (Express, Firestore, Firebase) unless issues arise.
- End-to-end Testing: Jest, SuperTest, Cypress.
- Firebase for push notifications and the chatting system.
- GitHub Actions for the CI/CD pipeline.
- Registration/Authentication/Security.
- Data Retrieval and Display (charting): E.g. appointments, vaccinations, lab results, medications, etc.
- Personal Data Tracking: Medical record, i.e., biodata, allergies, family history, past procedures, etc.
- Symptom checker using AI.
- Push Notifications: E.g. take your meds, go to appointment, do your exercises.
- Private messaging with the doctor.
- Physical assistance and translation services.
- Data sharing with a designated caregiver.
- Personal preference.
- Assigned on JIRA.
- Architecture diagram for every commit?
- If resources are available for help for FHIR.
- Which Firebase version to use depending on the existing documentation for each.
- Something like Javadoc for comments.
- Whether to use two repositories or one for the client and server.
- Deployment tool (finalized) before the first sprint.
(tied with Figma and proposal document)
Confirmed list of pages:
- Splash screen
- Login page
- Have MFA feature
- Forgot password
- Registration page (doctors and patients)
- About us section
- Home
- Navbar
- Home
- Journals
- Diabetes
- Activity
- Food intake
- Weight
- Mood
- Symptom
- Personal notes
- My Data
- Contact
- Profile (settings, notifications, legal disclaimers)
- Your Information
- Biodata
- Appointments
- List of lab results
- Medications list
- Immunizations
- Allergies
- Help
- Symptom checker
- Chat with physician
- Request for assistance (fill a form)
- Settings
- Account security
- Push notifications
- Logout
- Due Date: September 29th, 2023
- Features:
- Splash page
- Main menu
- Login page
- Registration
- Logout
- Settings
- Profile
- Forget password
- Look at encryption
- Documentation:
- Class diagrams
- Testing and CI/CD
- Due Date: October 13th, 2023
- Features:
- Display view lab results
- Bio data, procedure data
- Notifications
- Iteration release
- Set up user stories on GitHub
- Setup testing for frontend and cloud functions
- Start Sprint 1
- Assigned story points, risk, and priority for our user stories.
- Story Points: Indicating how difficult or time-consuming each task is.
- Risk: Evaluating the level of risk, whether it's low, medium, or high, especially related to security for users and their information.
- Priority: Assigning priorities from 1 to 5 to determine how important each task is to the project.
- Story points, risk levels, and priorities were assigned to user stories, helping to better understand the project's scope and challenges.
- Finalized the information we will be asking from users when they register.
- Set up a meeting with Randy, the stakeholder, at 7 pm Sept. 18th (optional).
- Jonathan brought up the issue of MFA, considering its potential cost. It was noted that it might cost approximately $0.50 to $1.00 per person.
- Jonathan will explore alternative MFA solutions, such as using Google for MFA.
- The team discussed testing requirements. It was decided that achieving an 80% coverage rate is the primary goal.
- Frontend (FE) will focus on UI testing, while Backend (BE) will concentrate on unit testing for functions.
- The team acknowledged that the CI/CD pipeline is currently broken and agreed to make it the top priority for the backend team. It will be fixed as soon as possible.
- Christina raised the topic of the booking option. It was agreed to move this feature to the archive for the time being. The application will only allow users to view appointments.
- Due to privacy and security concerns, the data sharing feature must be removed from the project. The team decided to notify Professor Rigby of this decision via email.
- Julian will take on the responsibility of configuring the Progressive Web App (PWA) instead of Jan. He will also address any frontend tasks that were inadvertently omitted from the previous meeting.
- It was decided that the chatting feature will be implemented in Iteration 2 to allow more time for focus on midterm exams.
- Team members provided updates on their progress thus far and reported any issues they encountered.
Please note that the meeting with Randy, the stakeholder, is optional and may provide additional insights into project requirements.
-
Discussion on the changes to the application and on the highest risk (privacy) and our options to increase privacy. (Encryption/MFA..).
-
Jan explains different built-in encryption methods with Postgres, and we discuss what fields to encrypt.
-
The goal of the application altered towards the elderly.
- Initial decision to keep the symptom checker API feature, now considering that it is too complicated with the tech stack changes, therefore we decided to remove it.
- Decided on implementing logging backend with Morgan for this sprint.
- Decided to stay with the subscription model for the income model.
- Make a demo video of what you code/implement.
- Each member mentioned what they did and their blockers for tasks they are currently working on.
- We successfully planned our iteration 2 stories and assigned tasks to everyone for the next sprint.
- Finish View and CRUD operations on Appointments
- Journal for entries (Weight/Activity)
- Reminders (depending on journals)
- Speed Dial to close relatives and health professionals
- Announcement of increasing team effort to meet deadlines better in next sprint as sprint 1 some people did not respect the deadline and they were late finishing their tasks.
- Made some suggestions by leader to have some effort in time management and efficient project planning to avoid same problem in next sprints.
- Went over tasks that were not completed so that they can be done as soon as possible regarding sprint 1
- Each member mentioned what they did and their blockers for tasks they are currently working on.
- Went over quickly on assigned tasks.
October 10th remains deadline agreed by everyone.
- Removed all elements of address from users so that no unnecessary information is collected.
- Removed physcial translation services from planned features.
- Each member mentioned they're progress and what they're working on.
- Discussed which stories and issues would be covered during iteration 3
- Julien to collaborate with Imran on the appointment task.
- Adjust and delegate new tasks among team members.
- Emphasis on updating documents post each iteration.
- Xavier to manage documentation tasks.
- Discussions on push notification functionality and its intricacies.
- Sprint 4 considerations, especially risky features.
- Adir to handle backend tasks.
- Emphasize bug fixes and app optimization.
- Frontend improvement deliberations.
- Jonathan proposes Reuven and Adir transition to full-stack roles.
- Deliberations on privacy enhancement.
- Consideration of integrating activity diagrams.
- Encourage proactive task handling by team members.
- Julien and Imran are collaborating on the appointment task.
- There was a significant discussion on task adjustments among team members.
- Xavier has taken over the documentation task.
- The importance of updating documents after each iteration was stressed.
- Julien explained the push notifications feature, specifically for reminders and appointments.
- The team debated on the push notifications' frequency and settled for daily reminders.
- Jonathan suggested enhancing the feature, making it customizable for users (daily, weekly, etc.), to be incorporated in future phases.
- The team discussed addressing risky features. Most of these have been addressed, but the team is still working on the weight journal risk.
- The tasks to start were differentiated from those to be put on hold.
- Adir was assigned to the backend tasks.
- The team engaged in a conversation about addressing bugs and making improvements.
- A further discussion on app optimization took place.
- Jonathan suggested that Reuven and Adir should take on full-stack roles, enhancing team versatility.it was refused by the team, instead it was agreed to have them help in fixing bugs and improvements in front end if the front end team agrees and gives the consent to do so.
- Discussions focused on refining and improving the frontend.
- The team deliberated on methods for enhancing privacy.
- The team contemplated the integration of sequence diagrams into the project for clarity and visualization. Then agreed to have it as activity diagram.
- A sentiment was expressed that if there's a task pending and members find time, they can fix it after asking the agreement of the person who has been working on that task and taking the consent from him/her.
For any further clarifications or actions, team members are encouraged to reach out and communicate effectively.
- cleaned all the branches that are no longer in use
- go through the release grading scheme to make sure everything will be covered
- all meetings will be on Tuesday for future sprints.
- discussed and agreed that all members have to ask for the author's permission before altering other people's code
- discussed the design of the client-side application, and agreed that don't make major changes before the first release
- ask the TA questions about the feedback
- go through the task status of sprint3
- move the speed-dial task from sprint4 to sprint5
- additional long-term issues added to improve app UX
- internal deadline: Nov 8
- home page design in progress
- addition of alerts
- go through task status for sprint 4 (release 1)
- diabetic journal backend done
- back buttons routing correctly
- storing user notification in progress
- frontend error handling
- discuss about our meeting with TA
- discuss our plan for sprint 5
- Decide what we will do for sprint 5 and sprint 6 (Sprint 5 will be finishing the features of our app and start optimizing and Sprint 6 will mainly about bug fixing and performance fixing)
- Registration will have user sign in immediately instead of redirecting them to login
- Reminders will be completed for this release just need to add small changes.
- Most optimization are done for performance
- Reuven added a handle error context on the client side.
- Jonathan is planning to deploy the app and also fix the issue TA is having with docker.
- Jan's updates on deployment.
- Setting up a deployment deadline.
- Proposal for logging.
- Assigning tasks.
- Planning for code optimization.
- Discussing the involvement of students taking the 491 class in implementing a new feature.
- Jan's Deployment Update: Jan provided updates on the current status of deployment.
- Deployment Deadline: A deadline for deployment was established.
- Logging Proposal: A proposal was made to introduce a new logging system.
- Task Assignment: Tasks were distributed among team members.
- Code Optimization: Plans were made to optimize the code.
- Student Involvement: Discussed the involvement of students enrolled in the 491 class for implementing a new feature.
- Iteration 7 tasks are planned to be focused on release 1 feedback
- Server hosting will be evaluated on Concordia servers if possible
- Discussed possible fix for timeout bug
- Round table update on everyone's progress
- Decision of weekly meetings day next semester based on availabilities
- Confirming next meeting date
- Review of Feedback for Release 1
- Preparation of questions for office hours
discussed the major priorities in the project and agreed on following :
- first priority is solving the post deployment bugs
- doing the Machine learning new feature (another meeting to come).
- improving user experience and performance for the front end as third and last priority for the release 2.
it was agreed to have teammate Jan regularly push to production branch for the deployment every week Friday evenings provided things work.
round table was done where everyone except teammate Reuven Ostrofsky shared their status.
next meeting was agreed to be on January 3rd 7 pm 2024.
- Round table for update on everyone's progress
- Post deployment bugs are of the highest priority
- Hugging Face library to be used for ML
- Next meeting scheduled for January 09 at 7:00 pm
- Round table for update on everyone's progress
- Post deployment bugs almost cleared
- AI feature partially trained to allow post-training code to be made
- Next meeting not yet scheduled until consensus from When2Meet
- The reminder feature issue was addressed. Jan, Julien, and Imran successfully fixed it.
- Testing of the reminder feature is crucial as it's not functioning correctly on some phones. All team members are requested to test it on their devices.
- Julian has created a document explaining how the reminder feature works on both iOS and Android phones.
- Round table discussion on current tasks and progress made by each team member.
- Brainstorming ideas for upcoming user testing sessions. Detailed planning will be discussed in the upcoming weeks.
- Exploring options for improving AI model accuracy. Two options were proposed:
- Adding more data from a larger dataset (challenge: data size is too large to process on our current computers).
- Considering a switch to a multitask model.
- Update the README file to reflect recent changes, including the addition of new features and the use of different tools.
- Final discussion: Team members are reminded to create individual videos for the release 2 update.
- Round table discussion on current tasks and progress made by each team member.
- Github actions usage minutes is reaching the limit often. Once its reached, there is no CICD running.
- Potential solution for the github actions issue is to move python server from heroku to huggingface
- Discussion of the meeting Imran had with professor Rigby:
- A/B testing is optional as the google forms are enough for user feedback. It is not current priority
- New features should be put as a low priority at the moment, as fixing bugs and improving user experience is more important according to the professor
- Brainstorming of which metric to collect from users to improve engagement with the application. Potential one is time spent on a page. Professor advise to only do this when we have enough users
- Discussion of current user feedback:
- Improve user profile page
- Contact page can have 2 identical phone number
- Add onboarding page or instructions on how to download the app
- Make UI more clear when selecting entries
- Password requirements to be more strict
- Adding calories to food intake
- Can make a issue that compiles all user feedback issues
- Round table discussion on current tasks and progress made by each team member.
- The number of real users should be collected and released in the google doc at the end of the last sprint.
- The model training will be probably finished in sprint 10
- The python server deployment will be manual instead of automated through the pipeline. If it doesn’t work, the hugging face endpoints will be created and the Heroku deployment will be used to fetch information from the hugging face.
- Round table where we discuss our progress on the current sprint.
- We will decide to add a new feature to our app (AI snoring feature)
- The pill identifier AI model will be manually deployed on hugging face
- Went over new feedback from user that was received from the google forms.
- May advertise our app on Facebook and possible subreddits in later sprints to increase user testing.
- Decided that a automatic prompt button will be added for PWA installation on mobile (for the user installation instruction feedback)
- Team Updates: Each team member shared updates on their current tasks and progress.
-
Sprint 11 Planning:
- Adir outlined his plans for tasks in sprint 11.
- New tasks were assigned to those who either did not have any or had completed their previous tasks.
-
Project Updates:
-
Snoring AI and PillIdentifier AI: Announced as completed.
- Adir proposed limiting the PillIdentifier AI to a certain number of pills to improve accuracy. Jan is expected to work on implementing this feature.
-
Snoring AI and PillIdentifier AI: Announced as completed.
-
Deployment Strategy:
- Jonathan has decided to proceed with manual deployment of the application.
-
Backend Development:
- Reuven and Jonathan are set to work on the backend for the blood pressure journal feature.
-
Feature Exploration:
- Reuven will investigate potential new features for development.
-
Team Updates: Each team member shared updates on their current tasks and progress.
-
Deployment of snoring feature is at risk of being removed from deployment and just be continued to work on local due to budget and time limitations. The team will reassess this possibility soon.
-
Meeting lasted 12 minutes.
-
Team Updates: Each team member shared updates on their current tasks and progress for this sprint so far.
-
Discussed improved accuracy of Pill Identification Model as well as gathering the material for the capstone presentation.
-
Meeting lasted 11 minutes.
-
Each team member shared updates on their current tasks and progress for this sprint so far.
-
Discussed objection to see if we can put the compass public.
-
Conducted a round table discussion.
-
Talked about the updates we need for our overall domain model.
-
Discussed preparation for the demo.
-
Meeting lasted 20 minutes.
-
Each team member shared updates on tasks and progress for the final sprint.
-
Round table discussion.
-
All PRs to be merged by 31 March latest in order for those features to be in the demo.
-
Meeting lasted 15 minutes.
Meeting Minute Contributors:
- Meeting #1: Christina Darstbanian
- Meeting #2: Divleen Ahluwalia
- Meeting #3: Julien Phan
- Meeting #4: Xavier Morgan-Tracy
- Meeting #5: Adir Ben-David
- Meeting #6: Jonathan Abitbol
- Meeting #7: Christina Darstbanian
- Meeting #8: Xavier Morgan-Tracy
- Meeting #9: Reuven Ostrofsky
- Meeting #10: Jiayi Chen
- Meeting #11: Jan Ong
- Meeting #12: Imran Ahmed
- Meeting #13: Reuven Ostrofsky
- Meeting #14: Xavier Morgan-Tracy
- Meeting #15: Jonathan Abitbol
- Meeting #16: Christina Darstbanian
- Meeting #17: Divleen Kaur Ahluwalia
- Meeting #18: Jan Ong
- Meeting #19: Adir Ben-David
- Meeting #20: Julien Phan
- Meeting #21: Jiayi Chen
- Meeting #22 : Imran Ahmed
- Meeting #23 : Reuven Ostrofsky
- Meeting #24 : Christina Darstbanian
- Meeting #25 : Jonathan Abitbol
- Meeting #26 : Adir Ben-David
- Meeting #27 : Divleen Kaur Ahluwalia