Use Case Diagram for Healthcare System

This document describes several use case diagrams for a healthcare information system called 'Headspace'. The diagrams detail how different stakeholders, such as practitioners, administrators, and case workers, interact with the system to access and analyze patient stories. Use cases include 'Input Story', 'Access Story', and 'Input Analysis Report'. Each diagram outlines preconditions, postconditions, exceptions, actors, and related use cases, providing a comprehensive understanding of the system's functionality.

Running head: SYSTEM ANALYSIS AND DESIGN
Case Study: Headspace
Name of the Student
Name of the University
Author’s Note

2
SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Stakeholder Map....................................................................................................................3
1.1 Diagram of stakeholder map............................................................................................3
1.2 Description of stakeholder map.......................................................................................3
2. Questionnaire.........................................................................................................................4
3. Use case..................................................................................................................................6
3.1 Use case diagram..............................................................................................................6
3.2 Description of use case.....................................................................................................6
Bibliography.............................................................................................................................11

3
SYSTEM ANALYSIS AND DESIGN
1. Stakeholder Map
1.1 Diagram of stakeholder map
Figure 1: Stakeholder map
(Source: Created by Author)
1.2 Description of stakeholder map
The depiction of the partner outline for the most part gave underneath:
Information storage of the patients: The patients share their issues and also challenges
including their stories because of which they confront issues. The case manager appropriately
stores the stories of the patients with the goal that the patients can be analysed according to
the accounts.
Information sharing of patients: The understanding stories are by and large given to
all the staff so they can utilize it for breaking down and also distinguishing the issues that the

4
SYSTEM ANALYSIS AND DESIGN
patients confront. The stories are by and large recorded for analysis with the goal that the
issue of the patients can be settled.
Practitioner: The professional assumed the whole liability of examining and in
addition distinguishing the patient’s stories keeping in mind the end goal to conclusion the
mental state of the patients. After legitimate finding, the patients get the outcomes as per
which they are kept under drug.
Case worker: The case manager for the most part includes in get-together suitable
data from the different patients and they additionally record the stories of the patients
appropriately into the database with the goal that the specialists can undoubtedly get to the
information for legitimate finding.
Government: keeping in mind the end goal to control the execution and additionally
advancement of data framework inside the association "headspace", the administration
assumes an essential part. Legitimate enactment and additionally controls must be utilized
amid the advancement of data framework for limiting unscrupulous acts.
Legislation: Proper controls and in addition direction are required to be taken after
amid the improvement of data framework. Legitimate investigation of tenets and control are
especially critical before building up the framework appropriately with the goal that the
advancement of the framework occurred by following national and additionally Australian
guidelines.
2. Questionnaire
The questionnaires are as follows:

5
SYSTEM ANALYSIS AND DESIGN
1. What are the distinctive sorts of functionalities that must be joined inside the data
arrangement of the association "headspace"?
2. How the data framework is useful for the patients who are experiencing mental sick
wellbeing conditions?
3. What are the issues that the engineers confront amid executing the data framework
inside the association?
4. What kind of issues does the patient go up against with while sharing their stories by
using the data framework?
5. What changes ought to be fused inside the data framework later on?
6. How the advancement of data framework makes changes inside headspace?
7. For what amount of time, the patient information is available inside the database?
8. How the stories of the patients are separated by the framework?
9. What will occur because of giving incorrect information?
10. How the data arrangement of headspace is profitable for the patients?

6
SYSTEM ANALYSIS AND DESIGN
3. Use case
3.1 Use case diagram
Figure 2: Use case diagram
(Source: Created by Author)
3.2 Description of use case
Illustration of individual use cases:
Name of the use case Register
Description Register is functionality to enter into the
system and perform various operations. Users
need to provide proper details for register.
Actors Practitioner, psychologist and Case worker
Related use case Login

7
SYSTEM ANALYSIS AND DESIGN
Stakeholders Administrator, case worker and Practitioner
Preconditions To user this system uses need to login to this
system. Before login the registration is must.
Post conditions Users need to enter proper registration
details and also need to provide current user
ID and password for future login purpose.
Exception If the database connection is failure, then it
will not perform.
Name of the use case Login
Description To access this system, the users must be
logged in to the system with their register
user ID and password. After login they can
perform various operations.
Actors Case worker, Practitioner, and psychologist
Related use case Register
Stakeholders Practitioner, administrator and case worker
Preconditions Users need to register first before login.
Because the login ID and password will be
saved first into the database. After that the
users can be login to the system.
Post conditions On the off chance that enlistment is done
legitimately then the clients for the most part
gets ID and in addition passwords which will

8
SYSTEM ANALYSIS AND DESIGN
be used for sign in to the framework with the
goal that the whole functionalities of data
framework is used by the client.
Exception In the event that the association that is
available between the frameworks and in
addition database in not precise.
Name of the use case Input Story
Description A meeting is essentially organized with the
case manager and patient where the case
manager helps the patients to share their
issues and difficulties. At that point they
record the stories for refreshing it into the
database with the goal that it can be
effectively open for determination.
Actors Case worker
Related use case Access Story
Stakeholders Practitioner, administrator and case worker
Preconditions The patients are not released until the point
when the case manager records the issues and
also difficulties of the patients as story.
Post conditions After the whole story is recorded it is
refreshed on the database of the data
framework so they can be gotten to
effectively with the assistance of experts for
diagnosing the troubles and wellbeing related

9
SYSTEM ANALYSIS AND DESIGN
issues.
Exception On the off chance that the headspace
database does not record the patient story
legitimately.
Name of the use case Access Story
Description The data framework helps in giving
appropriate approved access to the staffs of
the association so they can undoubtedly get
to the stories that are related with the patient
so the whole conclusion is done effectively.
Actors Practitioner, case worker as well as
psychologist
Related use case Input Story
Stakeholders Administrator, practitioner as well as case
worker
Preconditions Proper approval is fundamentally given to the
staff of the association with the goal that
suitable access is available before the staffs
for using the patient's story for analysis.
Post conditions All the individual from the association are
given access so they can have the capacity to
break down the wellbeing state of the
patients.
Exception If the story that is recorded in not correct.

10
SYSTEM ANALYSIS AND DESIGN
Illustartion of entire use case:
Name of the use case Input Analysis Report
Scenario The staffs of headspace helps with entering
the report of the patients inside the
framework after legitimate tests are embraced
Trigger Event Patient story update
Description The practitioner provides result to the
patients after analyzing the recordings as well
as tests which are undertaken. The results are
generally shared on the information system.
Actors Psychologist, General practitioner, and
psychiatrist
Related use case None
Stakeholders Psychologist, General practitioner, and
psychiatrist
Preconditions The master offers result to the patients in the
wake of separating the records and tests
which are grasped. The results are generally
shared on the information system.
Post conditions For giving legitimate outcomes to the patients
the records of the database are by and large
refreshed every once in a while.
Exemption conditions If the outcome is improper as well as unclear