Automated System for Headspace: Improving Mental Health Treatment

This report recommends the development of an automated system for Headspace to improve mental health treatment. The system will securely store and allow access to patient data by authenticated personnel only. The report includes a stakeholder map, questionnaire, use case diagram, and use case description.

ADS AC A MA D S S MHE P E – UTO TE Y TE

Table of Contents
Introduction
......................................................................................................................2
Stakeholder Map
...............................................................................................................2
Questionnaire
....................................................................................................................3
Set of Questions - Case Workers and Medical Team.................................................................3
Use Case Diagram
.............................................................................................................4
Use Case Description...................................................................................................................4
Conclusion
........................................................................................................................6
References
.........................................................................................................................7
1

Introduction
In the given report, an automated system is recommended to be developed for the
organization NSW. It has been assigned a task of trialing NewAccess with the people of age
less than or equal to 12. The Australian government is ready to invest around $54 million for
this task. There are large number of youths who are currently suffering from mental health
issues. These issues require immediate attention with accessible treatment. The automated
system will break the barrier between the youth, suffering from mental issues, and the
specialist. It will break the need of telling about the condition repeatedly to different case
workers and medical person. The automated system will feed data once and later can be
accessed by any authorized person.
Stakeholder Map
Operational Executive
Internal Case worker – The case worker
faces various issues and challenges
with the current system. They need
to obtain information regarding
patients when they need
appointment or any other help.
Every time, they are asked same set
of questions again and again. As a
result of which they get irritated.
This can raise issues in diagnosis as
the specialist or Emergency
Department may not able to get the
required information to treat the
patient.
The proposed system will eliminate
these redundancies which will help
both patients and Emergency
Department (Valacich, George &
Hoffer, 2014).
Headspace team – Australian
Government aims at developing a
system which can improvise the
mental health in the country. The
proposed project will bring a system
that will make treatment process more
accurately. The well-being of the
country shall help in raising the
working opportunities for the youths.
External Patient – Theses stakeholders are
those individuals who are suffering
from mental conditions and need
treatment. The current system
needs them to answer about their
same condition to different
Vendors and suppliers – During the
set -up of the proposed system,
various equipments are required with
respect to hardware and software. The
organization can buy them using
tenders and allocating it to one of the
2

persons / case workers / medical
team again and again from the
beginning. This can be
embarrassing for them.
The proposed project will provide a
platform where the details of the
patients and their medical
conditions are recorded only once
and then can be shared with
authorized case workers and
medical person. The repetition can
help in letting patients to come
forward more and get treatment on
time.
vendors. After supplying the
equipments, organization pay them
for the orders.
Questionnaire
Set of Questions - Case Workers and Medical Team
 What are the main questions that would normally get asked from patients so as to
understand the patient’s mental health (Stevens & Pooley, 2008)?
 The total number of meetings that has to be done with the patient before he or she is
fully diagnosed?
 What are the core issues being faced into the current system right now that becomes a
hindrance in recording or accessing of information and also other areas?
 Is the information being recorded need to be classified in multiple categories for
instance as sensitive or non-sensitive and medical or non-medical?
 Core operations that needs to be performed after the story has been given to the case
workers? Any information classification or analysis needs to be done on the story?
 The choice of method of accessing the system? Mobile, Web or Desktop?
 What are some of the system and technical features that needs to be present within the
system? For instance, easy usage, easy maintenance and non-stop availability?
 Have you got any past experience in working with a similar kind of system which
recorded patient’s health and condition?
 What could be the preferred choice for navigation for instance menus, buttons,
gestures? What color scheme would you like to choose? What personalization options
do you expect?
3

 What are the current standards being followed with the existing method of recording,
storing and accessing patient’s data that relates to law and authority? Do you want to
include any regulatory and legal policies within the system for data protection (Miles
& Hamilton, 2008)?
Use Case Diagram
Use Case Description
 Providing answers to Medical based questions
There would be in total 2 actors which would be associated with the given use case
i.e., the system and the patient. Patients would be asked questions related to their
medical condition and would also be stored. These aforementioned answers would
allow caseworkers to analyze it and make appropriate notes.
 Register
Authorization process is an integral part for the system so as to make sure that only
authorized users are passed through and have the ability to access patient details. A
registration form is required to be duly filled with all the essential details.
(Maksimchuk & Naiburg, 2008).
4

 Definition of the Access Privileges
There would be user roles and access control lists which would be defined. In this
case, the users that are essentially workers that are working on the case will have the
ability to assist in data protection.
 Sending of the data
The data would then be sent to the system in the method of a story which was
provided by the patient. The system would then store data in database and would
assign a particular story to patient. The data is then made accessible for future use.
 Add Doctor
There might be some new members or doctor which has been added to the medical
team that was assigned to some case. The process of addition would require doctors to
get access to the data which will be added to the application. By this method, the data
is then made visible to the team.
 Notify Customer
The patients are notified about any diagnosis or results and then they would further
provide responses in the way of alerts and reminders for any upcoming meetings.
Use Case Answers to medical enquiries
Scenario The system would be recording information which would then be
provided by the visiting patients.
Trigger As soon as the case worker begins recording the session with the
patient.
Description The entire information given by the patient is recorded in a
manner of a story and all other key details are also captured
within the system for later use.
Related case Data being sent
Actors System and Patient
Stakeholders Medical Team, Case Workers and the Patient themselves
Pre-conditions Case worker needs to have a working credentials to login into the
5

system
Post-conditions The system will allow data access or storage
Activity Flow Actor System
Entering of a valid working
credential.
Homepage of the system shall
be displayed
Inputting the patient ID Information of the patient being
displayed
Asking medical queries and
recording of the same
Information getting recorded
into the system.
Saving the recorded
information
Saving of the patient story
Exception The login details being not correct and the system barring the
person accessing the system (Eliot, 2016).
Conclusion
The automated system, which will be developed for Headspace, will take the organization
one step ahead as compare to other organization. It shall allow data to be securely stored and
accessed by authenticated person only. It can be accessed by different internal and external
stakeholders which are involved in the system i.e. patients, case worker, medical specialist,
Emergency Department along with vendors. The development of the system shall be based on
the questionnaire which will provide the key requirements of the end users. Along with the
data collection technique, use case modelling has also been used in order to understand the
functional and non-functional requirements of the proposed system. The report has presented
various use cases and also given the description of one critical use case.
6

References
Eliot, G. (2016). The mill on the Floss (2nd ed., pp. 22-23). New York: Open Road Integrated
Media.
Maksimchuk, R., & Naiburg, E. (2008). UML (2nd ed., pp. 22-23). London: Addison-
Wesley.
Miles, R., & Hamilton, K. (2008). Learning UML 2.0 (2nd ed., pp. 12-14). Sebastopol:
O'Reilly Media, Inc.
Stevens, P., & Pooley, R. (2008). Using UML (4th ed., pp. 22-24). Harlow: Addison-Wesley.
Valacich, J., George, J., & Hoffer, J. (2014). Essentials of systems analysis and design (2nd
ed., pp. 12-13). USA: Princeton.
7