1. What are the questions that you normally ask from the patients in order to understand the mental health condition of the patient?
2. What is the frequency of the discussions that take place with the patients in order to complete the diagnosis and treatment procedure?
3. What are the issues that you face in the current system that is followed in the information recording process which you would want to overcome with the automated system?
4. Can the information be classified in the various categories such as medical and non-medical information or sensitive and non-sensitive information sets?
5. What are the operations that you perform with the story of the patient in terms of analysis of the information, classification of the information and likewise?
6. Where would you like to access the application – web platform, mobile platform or both?
7. What are the systems related qualities that you would like to experience in the application in terms of the easy maintenance, easy usage, and non-stop availability and likewise?
8. Do you have any past experience of working on any similar systems or applications for recording and maintenance of the information?
9. What is the preferred navigation, layout and color scheme that you would want to be applied in the system? Would you like personalization and customization options in these areas?
10. What are the standards that you follow for information protection so that the information is not disclosed in front of the unauthorized entities? Are you aware of the legal and regulatory policies for information protection?
Questions for Understanding Mental Health Condition
There are various sectors that are present all across the globe that perform several activities with varying degrees of significance. One of the sectors that are associated with every country and region is its healthcare sector. There are various activities that the organizations and agencies associated with this sector perform on a daily basis. Australian Government invested $54 Million in the National Youth Mental Health Foundation which was later renamed in to Headspace project. There are various mental health patients that are present belonging to the age group of 12 to 25 years. These patients need care and attention which demands them to tell and share their story with the workers and people working on the case (Rhyous, 2011).
Headspace is a project that records the story of the patients and provides them with the treatment according to their mental condition. In the process, the patients are required to share their story with every worker in the case again and again. This leads to the loss of plot and depth and also builds a sense of irritation in the patients.
It has been decided to overcome the problem by developing an automated system that will record the story of the patient at the first time itself so that they repetition is not required. In this way, the information will be efficiently managed and maintained and the relevant patterns will also be identified from the same.
|
Stakeholder Name
|
Stakeholder Type
|
Interest in the Project
|
|
Patient
|
External and Operational
|
The patients are the entities that will be suffering from a mental condition and will require a treatment for the system. In the current system, the patients have to repeat their story in front of every case worker and a member of the medical team. With the setting up of an automated system for information recording, the need to repeat the story will be eliminated which is why the patients will be interested in the project.
|
|
Case Workers and Medical Team
|
Internal and Operational
|
Currently, there is a lot of problem that the case workers and medical team members face to extract the required information from the patients. It is because of the reason that the patients get irritated when they are asked the same set of questions again and again. This brings up problems in the diagnosis and treatment as well. These issues will be eliminated with the aid of the system which would be of good interest to this group of stakeholders (Watt, 2016)
|
|
Headspace Team - Sponsor
|
Internal and Executive
|
The primary aim of the Australian Government through the Headspace project is to set up mental health and wellbeing in the country. This aim will be fulfilled with the project as it will allow the treatment process to be quicker and accurate. This is the reason for the interest of the stakeholders in this group (Walker, 2016)
|
|
Suppliers and Vendors
|
External and Executive
|
There are many tools that will be necessary for the setting up of the automated information system in terms of the hardware and other equipment. The suppliers and vendors will receive their payments in return which is why they will have a good interest in the project tasks and activities.
|
Headspace project has been designed and approved to allow the execution of the assistance and treatment activities for the mental health patients. There are a lot many internal and external stakeholders that are involved with this project at the internal and external levels. These stakeholders have a lot of interest on the project related activities and can immensely contribute in the project activities as well. It is necessary for the project team members to investigate the information from the stakeholders in such a manner that the maximum information is obtained. With this practice, there will be clarity on the set of requirements and specifications to be implemented in the system.
There will be two actors that will be associated with this use case as the patient and the system. The patients will be asked the medical questions that will be recorded by the system and will be stored in the same. These answers will allow the case workers and medical team to analyze the answers and the responses that are provided by the patients.
An authentication process will be necessary for the system so that only the authorized users are provided with the ability to view the patient details and the associated information. A registration form will be required to be filled in for this purpose which will include the name, contact and other demographic information (Fakhroutdinov, 2016).
There will be access control lists and user roles that will be defined by the system. In this manner, the users such as the workers working on the case or the professionals from the medical team will get the ability to assist in the information protection process.
Frequency of Discussions for Diagnosis and Treatment
The data will be sent to the system in the form of the story that will be provided by the patient. The system will store the data in the database and will assign the story to the patient. The data will be accessible to the users after they pass the authentication checks and are found to be authorized for the process.
There may be new doctors or members that may be added in the medical team that is assigned to a particular case. The addition process will require the doctors or the professionals to have access to the information which will be made possible by the add option in the application. In this manner, the case history will be visible to the new member in the team (Wick, 2016).
The patients will be notified about their diagnosis results and the need to provide further responses by creating alerts and reminders for them regarding the upcoming sessions.
|
Name of the Use Case
|
Provide Answers to the Medical Questions
|
|
Use Case Scenario
|
The system will record the information that will be provided by the patients in the form of the answers to the medical questions and queries
|
|
Triggering event
|
Initiation of the recording session by the case worker or the representative from the medical team.
|
|
Brief description of the use case
|
The medical information and the details of the case will be recorded in the form of a story which will be associated with the patient. The information will be stored in the system and will be accessible later on as well.
|
|
Related use cases
|
Sending of the Data
|
|
Actors
|
Patient, System
|
|
Stakeholders
|
Patient and Case Workers and Medical Team
|
|
Pre-conditions
|
The case worker shall have the valid set of credentials to login to the system
|
|
Post-conditions
|
The data shall be successfully recorded and stored in the system
|
|
Flow of activities
|
Actor
|
System
|
|
|
Enter the valid set of credentials
|
The home page of the application shall be displayed
|
|
|
Enter the patient id
|
The patient information shall be displayed
|
|
|
Ask the medical questions and information and record the same
|
The information shall be recorded in the system
|
|
|
Save the information
|
The patient story shall be saved in the system
|
|
Exception conditions
|
The login details that are entered by the case worker are not correct which will exempt the worker from accessing the system.
|
Conclusion
Headspace is a project that has a lot of significance and relevance in terms of the aim to establish mental wellbeing in the region and country. There is a large share of youth that is currently suffering from the mental health issues and illness. It is necessary to make use of technology to fasten the treatment and diagnosis procedure to make sure that the desired treatment is received by the patients in a timely manner. The automated information system that is being developed and implemented for Headspace is a one step forward in the same direction. It will allow an automated and easy process for the recording of the story of the patients and will also perform additional data operations on the same. There are a number of internal and external stakeholders that are involved with this system such as patients, medical team members, case workers, project sponsor along with the suppliers and vendors. There are various techniques that may be used for investigating and gathering the information from the stakeholders and one such technique is the questionnaire. There are also several other processes and steps that may be followed for collecting the information from the stakeholders. which will provide the project team members with the ease to understand the requirements of the system. There are many use cases that are associated with the system that shall be carefully studied and analyzed.
References
Bourne, L. (2016). Stakeholder Relationship Management. Retrieved 4 September 2017, from https://www.mosaicprojects.com.au/PDF_Papers/P128b_Stakeholder_Relationship_Management.pdf
Fakhroutdinov, K. (2016). UML actor is a role played by a human user of the designed system, some other system or hardware that interacts with the subject by using services of the subject.. Uml-diagrams.org. Retrieved 4 September 2017, from https://www.uml-diagrams.org/use-case-actor.html
Rhyous,. (2011). The 8 Types of Technical Documentation and Why Each Is Important. Rhyous. Retrieved 4 September 2017, from https://www.rhyous.com/2011/07/21/the-different-types-of-technical-documentation-for-software-and-why-each-is-important/
Walker, D. (2016). Influence, Stakeholder Mapping and Visualisation. Retrieved 4 September 2017, from https://mosaicprojects.com.au/PDF_Papers/P062_Influence_Stakeholder_Mapping_and_Visualisation.pdf
Watt, A. (2016). 5. Stakeholder Management | Project Management. Opentextbc.ca. Retrieved 4 September 2017, from https://opentextbc.ca/projectmanagement/chapter/chapter-5-project-stakeholders-project-management/
Wick, S. (2016). User Stories and Use Cases - Don’t Use Both!. Batimes.com. Retrieved 4 September 2017, from https://www.batimes.com/articles/user-stories-and-use-cases-dont-use-both.html
