Generated by ChatGPT

Overview

• Data challenge Slides► Narrated Slides► Video►
• Overview of our current research on management of depressive disorders Slides► Video►

Objectives

1. Select a common challenge that can be addressed using health informatics methods and EHR data
2. Summarize previous work relevant to your analysis
3. Communicate with executives about your analysis

Assigned Reading for Project on Management of Depression

• Effectiveness of antidepressants PubMed►
• Proxy measure for remission of depression symptoms PubMed►
• Planned project on management of depression in African Americans Read►
• Description of AI system for management of depression Read► (Use instructor's last name for password)
• Overview of AI Challenge for management of major depressive disorder Read►

Assignment

Instruction for Submission of Assignments: Submission should follow these rules:

1. Include a brief summary statement about who in project management teams approved your work
2. Submit you work in Canvas.

Task 1: Complete the abstract (executive summary) for your project, as if you have completed the work.  The abstract should be structured to have the following sections:  Objective, Methods, Results, and Conclusions. The abstract should have one sentence on study objective, It should have two or three sentences on source of data and methods of analysis.  It should have on sentence on study findings.  It should have one sentence on conclusions. The purpose of writing the abstract is to check on your understanding of the task ahead.  Make sure you understand what analysis needs to be done. This assignment shows that you have understood the entire project.

Task 2: Write maximum of three paragraphs on current approaches to your project (see published articles on PubMed) and describe what your analysis contributes.  The introduction section of your report should use one or three sentences to reference existing approaches to guide antidepressant prescriptions.  You should use PubMed to identify previous approaches to guide antidepressant selection.   

Task 3: Complete an adversarial evaluation of the intake process.  A PDF set of files that provide instruction to ChatGPT is available on the web. The password is your instructor's last name and 2024. The ID is Farrokh2024. Ask for project managers for the web link to the site where code is available. The application code runs in the following order:

1. app.py
2. chatController.py
3. depressionConfirmationChat.py
4. ageAndGenderChat.py
5. typesOfDepressionChat.py
6. medicationHistory.py
7. depressionTreatmentHistory.py  

The chatUtilities.py provides some helper functions.   The chatbot-prompt.txt has the main prompt added to the beginning of each prompt sent to ChatGPT.  These files are provided so you can see what is the current instruction to ChatGPT.  These files are not intended to be used by you and you are not expected to complete python code.  The purpose of these files is to give you an advantage in breaking down the AI system by showing you what are the instruction to the AI system.  Also you are expected to do your work for all section and document changes needed for each section separately. 

• System Structure: Our chatbot system is structured with a main controller (chatController.py) that manages the flow of the conversation through various stages. Each stage (e.g., depression confirmation, age and gender collection) is handled by a separate Python file.
• Flow Management: The conversation flow is managed by the code, specifically in chatController.py. This file determines which stage to execute and when to move to the next stage. However, you are not expected to modify this flow.
• Your Task: We are asking you to mess things up and then correct it through better instruction to ChatGPT. For example:
  • Digress in the section and see if it returns you to the conversation properly. Some digressions ask for clarity and are appropriate and some are not. Check that the system acts appropriately to different types of digressions. 
  • Use alternative set of words to describe medical history and see if it is understood.
  • Make sure that your interaction is captured accurately, meaning that the medical history you mention, using any set of words you come up with, are captured appropriately. The system provides summaries after each section and you can check that what you mentioned was in the summary.
  • Once you find a problem, then meticulously document the problem so others can replicate it, and indicate what is the possible change in instructions that could correct the problem. Report your corrections to the project managers.
  • Your focus should be on the instruction-generating functions within each stage-specific file (e.g., depressionConfirmationChat.py, ageAndGenderChat.py). These functions typically include: generate_current_instructions() generate_confirmation_instructions() generate_final_instructions()

Steps to What to Do: 

1. Review the performance of the system within each section separately, taking notes about the  instructions given to the system. 
2.  Test the Chabot's responses to the instructions under various scenarios.  Be creative. 
3.  Identify and document weaknesses, inconsistencies, or areas where the Chatbot might provide inappropriate responses.  Your documentation should have sufficient details (all input and output) so that others can replicate the problem. 
4.  Suggest improvements to the instruction text to make the Chabot more robust, accurate, and appropriate in its responses.
5. Follow up in 3-4 weeks to make sure your modified instruction has improved the performance of the system

Here are some pointers on how to proceed:

• Limited Scope: Once you find a problem, you are only allowed to modify instruction text, which may not address deeper issues in the system's logic or decision-making process.
• Lack of Testing Framework: There's no consistent and timely way for you to see if your modified instruction corrects the problems you have found. A computer programmer, who works on the project, will incorporate some of the instruction changes into the system but this may come at significant delay.  Plan for these delays.
•  No Clear Metrics: There are no defined metrics for what constitutes an "improvement" in the system's performance. This is left to you, to find a problem, articulate the problem in a way that others can repeat on the system, and provide a solution. 
• Isolated Changes: Modifying instructions in isolation may not account for the interdependencies between different stages of the conversation.