Headspace Project: Streamlining Mental Healthcare In Australia

Importance of Technology in Business and Organizations

The important and criticality of technology in business and organizations around the world is unquestionable. Various technologies and solutions exists for different sectors of industries and the choice of these technologies and solutions are based on the type of operations the business is into. Also, the information systems as well as information management systems have long been in use in multiple industries (Rhyous, 2011).

The project in question here which is known as Headspace project is an important project for Australian government because of the nature of activities planned under it. It also requires a hug investment from the government side to an amount of AUD 54 Million. The main goal of this project is to provide medical assistance to Australian youth suffering mental illnesses. Under the program, the patient is required to share their story individually with all of the case workers involved with his or her case. This requires the same story be told multiple times and leads to alteration of information, loss of information and causes wastage of time and energy. The proposed solution will streamline the entire operation and make it faster, lean, requiring less energy and time.

Stakeholder Name	Type	Interest Save Time On Research and Writing Hire a Pro to Write You a 100% Plagiarism-Free Paper. Get My Paper
Patient	Internal, Operational	These problems are currently present in the system and the core of it is that the story needs to be told multiple times. Instead, now the story shall be recorded at the first session and will be utilized by the rest of the case workers.
Project Management	Internal, Executive	The entire project would be managed using project management principles and accordingly the management, planning and execution would be done methodologically.
Project Team	Internal, Operational	The overall success of the project and the team members working in the project will have direct relation. Also, if the project is a success each and every member involved with the project will be rewarded.
Healthcare Experts and Medical Team	Internal, Operational	The project is deemed to bring streamlining of the entire operations. This means that the entire process would be smoother, faster, more accurate and reliable. This will further enhance the interest and motivation of the case workers working in the case
Australian Government – Project Sponsor	External, Executive	The sponsors required that the project be completed under the allocated budget and time. The overall success of this project as well as it’s accomplishments will lead to improvise the Australian healthcare system.

The stakeholder map presented above lists all the external, internal, executive as well as operational stakeholders involved with the Headspace project. Irrespective to the stakeholders, there would be a lot of information that will be collected from each and every single person who is a stakeholder. Different techniques for data analysis as well as information gathering and investigation techniques would be utilized. Among this, the Questionnaire is a technique that will be utilized that would be questioned to the stakeholders. Their responses and comments for each and every question from the questionnaire will be recorded. The responses would be then analyzed by data analysis group and the required information gained thereafter would be forwarded further (Dennis, Wixom & Tegarden, 2015).

• How important is the patient’s story in determining the health condition of the given patient?
• How many people on an average are involved with the case of the patient?
• What are the current drawbacks and major flaws associated with the system?
• What encryption and information protection techniques are employed at present for securing the patient’s information?
• Is there use of business intelligence tools being made at present?
• What would be preferred mode of accessing the system – Web or Mobile?
• Are you currently aware that there would be certain security measures be setup for automation of the Headspace project?
• Do you use any other ICT based tools?
• Would you prefer hands-on training or system documentation for understanding of the features and functionalities of the automation system?
• What are the essential Australian regulations and policies that apply to the automation system being developed (Bruegge & Dutoit, 2014)?

• Login

In this case, the users of the system would simply be able to login into the system using their given credentials. These credentials will also define the level of access they have within the system.

• Patient Story Feeding

The main goal of the system is to overcome the burning issue that curtails the current process which is related to the repetition of the story of the patient. As a result, the main part of the application is to allow the personnel to feed the story of the patient once in the system and then have the system synchronize the story within the database and make it available whenever needed.

• Information Extraction

The patient and the patient’s case information would be available within the system throughout and it will also be possible to extract the information using the Patient’s unique ID. Any member of the medical team or any new recruit would be able to extract the information provided he or she has a properly authorized working credentials to login into the system,

• Data Analysis

The system would be automated and integrated within the BI or Business Intelligence systems that would allow professions to analyze the patient’s data. The story of the patient would be analyzed and then scrutinize against a database of symptoms and issues. This would aid medical personnel to diagnose the patient faster, more reliably and accurately.

• Medical Comments  

The system would also make it possible for the medical professions as well as Health care workers to attach any of their feedback, notes or comments to the patient story. So that another medical professional down-the-line or in future would be able to refer to that note and make assessment or make use of it to improve their diagnosis and treat the patient accordingly.

• User Management

There would be many users of the system that would use the system for execution of their day-to-day activities. These includes the administrator trying to setup the users of the system, manage their roles and privileges among others. Apart from this, user-centric activities such as addition of a user, deletion of a user and modification of their profile can also be performed by the admin of the system

Name of the use-case	Story feeding
Scenario	The story of the patient would be fed into the system and then the system would synchronize it within its database.
Trigger Event	The medical professional may access the system or the healthcare expert or worker assigned to the case and this would be the trigger point.
Short description	The main goal of the project is to overcome the current issue that curtails the working of the project. The automatic system would allow users to feed in the patient’s story allowing for faster synchronization and information availability at al times.
Related Cases	Data Analysis and Application Login
Actors Associated	System as well as the Patient
Stakeholders Associated	Health Care Experts as well as Patients
Pre-conditions	The healthcare expert needs to have a working credential with appropriate level of user access to be able to login and access the system.
Post-conditions	The system would synchronize the story of the patient along with the Patient’s unique ID and create appropriate copies of the story.
Sequence of activities	Actor	System
	Entering of a combination of password and ID in order to login into the system.	The main page of the headspace system would immediately load.
	Accessing of the patient’s record	The appropriate case record of the patient shall be opened.
	Recording of the patient’s story	The details which has been provided by the patient must be synchronized and stored in the system.
Exception conditions	If the account is deactivated or the login credentials are incorrect (Alhir, 2003).

References

Alhir, S. (2003). Learning UML (2nd ed., pp. 12-14). Sebastopol, Calif.: O’Reilly.

Bourne, L. (2016). Stakeholder Relationship Management. Retrieved 06 September 2017, from https://www.mosaicprojects.com.au/PDF_Papers/P128b_Stakeholder_Relationship_Management.pdf

Bruegge, B., & Dutoit, A. (2014). Object-oriented software engineering (3rd ed., pp. 13-14). Harlow, Essex: Pearson.

Dennis, A., Wixom, B., & Tegarden, D. (2015). Systems Analysis and Design (2nd ed., pp. 12-14). New York: Wiley.

Rhyous,. (2011). The 8 Types of Technical Documentation and Why Each Is Important. Rhyous. Retrieved 06 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 06 September 2017, from https://mosaicprojects.com.au/PDF_Papers/P062_Influence_Stakeholder_Mapping_and_Visualisation.pdf