My Health Record System - PDF

COVER PAGE

Contents
1 Stakeholder map......................................................................................................................................3
2 Questionnaire...........................................................................................................................................5
My Health Record System Questionnaire................................................................................................5
3 Use case diagram......................................................................................................................................7
3.2 Use case descriptions........................................................................................................................7
3.3 Detailed use case description............................................................................................................8
4. References...............................................................................................................................................9

1 Stakeholder map
A stakeholder is an organization or individual that has interest on a certain project. Their interest results
to power over the project or their direct involvement on the project whether during the development of
the project or after the project is deployed and is in use. There are four types of stakeholders;
 Internal operations stakeholders
 Internal executive stakeholders
 External operations stakeholders
 External executive stakeholders
The following stakeholder map shows the involved stakeholders for my health record system
Figure 1: Stakeholder map
According to the stakeholder map, there are two main determinants of where the stakeholder lies in the
project;

 Power- this is the measure of power that the stakeholder has on the project and can be seen on
his ability to influence on the decisions made concerning the project (Gudavajhala, 2017).
Stakeholders who have less power in the project lie in the lower quadrants while stakeholders
who have high influence on the project lie on the higher quadrants of the stakeholder map.
 Importance- the importance of a stakeholder in the project is the measure of their inputs to the
project. The inputs can be in terms of resources for example money to fund and maintain the
project or the input can be in terms of technical implementation of the project. Stakeholders
who are more important to the project are placed on the right quadrants of the stakeholder
map while stakeholders who are less important to the project are place on the left quadrants of
the stakeholder map.
According to my health record system the different stakeholders involved in the project are;
 Internal executive stakeholders- These type of stakeholders are the executive team that is
directly involved in the decision making of the project. These stakeholders make executive
decisions about my health record system. For my health record system these stakeholders are
specifically the management team that will be delegated with management of the project. They
will make all executive decisions and will decide on how the project will proceed. These
stakeholders are very important to the project as they determine the success of the project.
Their decisions directly influence how the project will turn out at the end. They have the power
on how the project is implemented because they make all the executive decisions.
 External executive stakeholders- These type of stakeholders are the stakeholders who have
higher influence or power on the project. They make executive decisions but are not directly
involved with the project so their executive decisions are made externally to the project. For my
health record system, this stakeholder is the commonwealth of Australia who is launching the
project thus they will fund the project. After launching the project they will then hand it over to
the internal executive stakeholders who will make the executive decisions concerning the
project with the input of the external executive stakeholders.
 Internal operation stakeholders- These type of stakeholders are very important to the project
but their influence or power on the project is very low (Project-management, 2017). For my
health record system, these stakeholders are the users of the application who will be directly
using the application. They are very important to the project because the project is directly
targeted to them because they will be the end users of the application and will determine the
success of the project. If the uptake of the application of the internal operation stakeholders will
be high and there will be less cases of opting out, then the project can be seen to be succeeding
but if the uptake is very low then the internal executive stakeholders will have to review the
project to determine why it is not working as expected. These type of stakeholders have no
influence because they are not involved in the executive decision making of the project but data
collected from their feedback will be used by the internal executive stakeholders to facilitate
making of executive decisions.
 External operation stakeholders- these type of stakeholders have the lowest influence or power
on the project and are not very important compared to the other types of stakeholders. For my
health record project, these stakeholders are the health professional who will also be accessing
the application to view or update the patient shared information. These stakeholders have low
influence on the project because they will not be involved with the executive decision making of

the project but their inputs on how the end application should be will be useful while making
decisions. They are not very important to the application because most of the tasks that they
are performing in the application can also be performed by the user who is the internal
operation stakeholder.
2 Questionnaire
For my health record system, the questionnaire to collect requirements should be addressed to the end
users of the application who will be using the application thus their input on how they expect the
application to help them should be very useful for requirements engineering.
My Health Record System Questionnaire
Questionnaire to collect requirements and expectations from end users for the planned My Health
Record System by the Commonwealth Government of Australia.
Please give your honest answers and opinions.
Section 1: Please select choices accordingly.
1. What is your gender?
Male ___
Female ___
2. How many times have you visited the hospital in the past 3 months?
Once ___
Twice ___
Thrice ___
More than five ___
None ___
3. Do you have a personal healthcare provide?
Yes ___
No ___
4. How do you store your medical history?
Online ___
Physical files ___
I don’t ___
5. Would you like to store all your medical history in one integrated application?
Yes ___
No ___
6. Would you approve a health professional to access your medical history?
Yes ___

No ___
7. Have you had any incidence where a health professional missed an allergy or medical condition?
Once __
More than once__
Never __
8. How do you know if any prescribed medications has a negative effect on you?
Online research __
Refer to medical records __
Section 2
9. Give your recommendations on how you would like the new My Health Record system to work
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
10. Who do you think should regulate who accesses your information and why?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Section 3 (Optional)
Please fill this section if you would like to be contacted to be asked further questions regarding My
Health Record System.
Full Names _______________________
Email____________________________
Contact information ________________
Thank you

3 Use case diagram
Figure 2: use case diagram
3.2 Use case descriptions
 Register use case- A new user registers in order to start using My Health Record system.
Registration involves verifying the registration and is done only once
 Login- A user with an account logins in to the system using their username and password.
 Add shared healthcare information- A user adds shared healthcare information about him or
herself to their personal profile. Shared healthcare information can also be added by linking to
Medicare where medical information for the past two years is added to the user’s profile.
 View shard healthcare information- this use case has more than one actor i.e the user,
representative and the healthcare professional. All these actors can access healthcare
information of a user.

 Update shared healthcare information- This use case has more than one actor i.e. Users and a
healthcare professional. An update of existing health care information is done by any of the
actors. This use case includes uploading clinical documents of the user.
 Grant access rights- this use case is done by the user to control who can access their records
within the system. It includes generating record access code to be used by healthcare
professionals, generating limited document access code to control which documents can be
accessed and generating personal access code to be used by a personal representative of the
user.
3.3 Detailed use case description
Use Case ID: UC-1
Use Case Name: View shared healthcare information
Created By: Author Last Updated By: Author
Date Created: 5/1/2018 Date Last Updated: 5/1/2018
Actors: Healthcare professional
Description: A healthcare professional views shared healthcare information for
a specific patient.
Trigger: External
Preconditions: 1. The healthcare professional must have a personal access code
of the patient whom the information belongs to
Postconditions: 1. System should display shared healthcare information of the
user
Normal Flow: 1. Healthcare professional opens view shared healthcare
information page
2. System displays the page and asks the professional to enter
personal access code of the patient.
3. Professional enters the personal access code.
4. System verifies the personal access code
5. System displays the shared healthcare information of the
patient
Alternative Flows: 4. System verifies the personal access code
4.1 System finds the personal access code is incorrect
4.2 System takes back the user to step 2
Exceptions: None
Includes: Verifying access code
Priority: High

Frequency of Use: Very frequent
Business Rules: The patient has control over who can access their shared
healthcare information
Special Requirements: The patient must generate a strong access code to prevent
unauthorized access to their personal information
4. References
Gudavajhala, S. (2017). Top 5 Stakeholder Analysis Techniques in Projects | Stakeholder Analysis in
Project Management. Master of project Academy. Retrieved 1 May 2018, from
https://masterofproject.com/blog/510874/top-5-stakeholders-analysis-techniques-in-projects-
stakeholder-analysis-in-project-management
Jepsen, A. (2009). Stakeholder analysis in projects: Challenges in using current guidelines in the real
world. Science direct. Retrieved 1 May 2018, from
https://www.sciencedirect.com/science/article/abs/pii/S0263786308000549
Project-management. (2017). What is Stakeholder Analysis?. Project magement. Retrieved 1 May 2018,
from https://project-management.com/what-is-stakeholder-analysis/