Smart Health - CSE 40816
Current healthcare systems face numerous challenges such as large cost, lack of preventive care, massive increases in chronic disease conditions and age-related illnesses, widespread obesity, poor adherence to medical regimens, and shortage of healthcare professionals. Smart Health solutions utilize new sensing technologies, smart mobile devices, wireless networks, and big data analytics to provide significantly improved care to anyone, at anytime, and anywhere, while increasing the coverage, quality, and efficiency of healthcare. This course studies how mobile, wireless, sensing, cloud, and big data technologies can be used to implement this vision of future healthcare. Class discussions will touch topics such as prevention techniques, continuous health monitoring, wireless and mobile technologies and standards for medical devices, personalized healthcare solutions, body area networks, implantable devices, mHealth applications, intelligent emergency management systems, pervasive healthcare data access, personal and electronic medical record systems, mobile telemedicine, context-awareness, and case studies of pervasive solutions for various health conditions and challenges. There is no textbook for this course; instead, the course will be based on recent publications in the areas of healthcare and wellness. Student will work on a semester-long development project in the area of smart health and also investigate and present a specific healthcare concern or technology via a brief oral and written report.
Upon successful completion of this course, students will be able to:
-
Understand the fundamentals of the basic building blocks of smart health solutions, such as sensors, mobile devices, edge and cloud computing technologies, data fusion, electronic health record systems, and medical analytics.
-
Establish a connection between the needs of specific medical and wellness challenges and the opportunities provided by new technologies.
-
Discuss current and future opportunities and challenges in smart health, including growing concerns in the areas of privacy, security, and ethics.
-
Identify specific healthcare challenges and opportunities and effectively present their insights to others.
-
Develop solutions to specific healthcare challenges, covering at least one of the following areas: sensing, fusion, biomarker development, intervention, diagnostics, and healthcare analytics.
Logistics
Class Information
- Lecture Time
- Mondays/Wednesdays/Fridays 9.25am-10.15am
Note that several lecture slots will be "independent project time", where we will not meet in the classroom, but either the TA or instructor will be available for questions. Please play close attention to the schedule below for actual lecture times. - Location
- O'Shaughnessy Hall 116
Instructor
- Instructor
- Christian Poellabauer (cpoellab@nd.edu)
- Teaching Assistant
- Afzal Hossain (afzal.hossain.3@nd.edu)
- Office Hours
- Instructor:
- Time: Tue 9-10am, Wed 12-1pm, and by appointment
- Location: 323B Cushing Hall
Teaching Assistant:
- Time: Mon 2-3pm, Fri 1-2pm, during "LAB" times in schedule, and by appointment
- Location: 212 Cushing Hall
Schedule
Requirements
Coursework
| Component | Points |
|---|---|
| Readings Reading assignments. | 35% |
| Homework Written report. | 15% |
| Homework Oral presentation. | 15% |
| Class Project Mid-semester progress report. | 15% |
| Class Project Final project report. | 20% |
| Total | 100% |
Due Dates
Submission details for all deliverables are TBD. Unless specified otherwise, all readings are due before the class starts on the day it is assigned and all other deliverables are due by midnight of the date indicated in the schedule above.
Resources
Reading Assignments
For each reading assignment, a brief summary is due immediately before the lecture where the assignment will be discussed. Submission will be via Sakai and the submitted file should be in PDF format and should have the name of the first author (e.g., Sagner.pdf would be the name of the submission for the first reading assignment). In no more than 250 words, the summary should describe the main takeaways of the publication, e.g., what specific problem is being discussed or what solution is proposed or what is the most important lesson you learnt from the assignment, etc. The main purpose of these assignments is to prepare you for the lecture discussions and to provide you with additional detail beyond what is discussed in class.Late Policy: Reading reports can be submitted up to 24 hours past the deadline for partial credit (75% for reports up to 6 hours late, 30% for reports up to 24 hours late).
Project Proposal
The project proposal (one proposal per team) should be no more than 3 pages, submitted as PDF file via Sakai and contain the following pieces of information:- Project title
- Name(s) of project member(s)
- Problem description (what are you trying to solve)
- Solution description (how are you going to solve it)
- Technical details (e.g., what hardware if any will be needed, what software tools will be needed, what is your proposed timeline, etc.)
- References (optional)
Mid-Semester Progress Report
This report is due by midnight on March 6th; submission is via Sakai (it is sufficient if one team member submits the report), the submitted file must be a PDF document. Submissions that are late by up to 6 hours will automatically lose 25%; and another 25% for each 4-hour window afterwards. This report is the only graded project component in the first half of the semester and essential to providing the instructor with a comprehensive view of your efforts and achievements so far! There are no page limitations, but the report should consist of the following components:- Project title
- Name(s) of project member(s)
- Original problem/solution description: This is a brief summary (one paragraph) of the originally proposed project.
- Update to problem/solution/technical description: This should describe any additions or changes to the original problem description or proposed solution (typically 2-3 paragraphs). This section provides you with an opportunity to be more specific about your proposed solution, i.e., what hardware/software tools are used, what will be the specific features and abilities of the final product, how will you evaluate and test the product, etc.
- Additional information: Provide an itemized list of activities completed, ongoing activities, and planned activities (clearly identify these three categories). Also propose a timeline for the remainder of the semester. Further, describe any significant concerns and problems you have encountered and how you have addressed them or plan to address them; any other information that you think will help the instructor assess the complexity of your project, your progress to date, etc.
Seminar Topic Proposal
For the seminar report/presentation, choose a topic that you would like to explore in more depth, e.g., how technology is being used to address a specific healthcare concern. This part of the course is to be done individually. The proposal is submitted as PDF file via Sakai and is a short document that provides a title of your investigation, your name, and one paragraph (about 1/2 of a page) describing some details about your investigation.Written Seminar Report
The written seminar report is due April 8th (midnight); submission is via Sakai. For your report, choose 3-5 publications or reports that you will read and describe in your report. Your written report should be a PDF file of up to 5 pages (everything included) where you describe the topic you investigated and your findings from the publications you read. Provide references for the publications and feel free to reuse images/graphs from the publications as you see fit. The audience for your report is the class, i.e., the goal is to provide an overview of a specific healthcare challenge, technology, etc., that goes beyond what has been discussed in the class lectures.Oral Seminar Report
The oral report is a brief narrated Powerpoint presentation of the topic of your seminar report. You can submit this either as a powerpoint presentation with narration added or as a video file that shows your slides while you describe their content. There are no strict constraints, but typically a presentation would be about 12-15 slides or 7-10 minutes. Submission is via Sakai and the deadline is April 15th (midnight).Final Project Report
The deadline for the project report is April 29 (midnight), submission is via Sakai. The format for this is intentionally flexible, i.e., there are no length requirements, etc. However, the report should describe the problem you investigated and how you addressed it, i.e., provide as much detail about your solution as possible. This can include things such as:- Design choices (including mock-ups, flow-graphs, etc.)
- Development methods, tools, and technologies (i.e., how exactly did you implement and build your solution)
- Solution features (i.e., what exactly does your solution do)
- Evaluation results, measurements, etc.
- Graphs, screenshots, etc.
- Relevant references The exact content of the report will of course depend on the topic of your work. Think of the report as your opportunity to impress the instructor and to convince the instructor that you have developed a cool/important/etc. solution. Also, if you worked on the project as a team, describe briefly each member's contributions. Finally, since we do not have an in-class demo or presentation, you are encouraged (but not required) to add a brief video (as a link in the main document or as a separate file) that shows your solution in action; this can be just a very brief demo (I would recommend keeping demons to less than a minute) of what you have done or built.