Stakeholder Analysis Map And Use Case Description For My Health Record System

Stakeholder Analysis Map

The identified stakeholders, who are involved in the My Health Record system scenario, are listed above. The Stakeholder analysis Map helps to uniquely segregate the stakeholder groups according to their scope of responsibilities and abilities or power (Thompson, 2012). The individuals are divided into 4 groups, namely the Internal Operations, Internal Executive, The External Operations and finally the External Executive group. They are meant to operate and supervise over the successful execution of the system, all over Australia. The specific roles of the individual entities of the map are as follows:

• Internal Operations

1. The Commonwealth Government of Australia: The Government, in this case plays the most crucial role of all. They are the ones, who are responsible for the initiation of the project. Therefore, on the stakeholders map, they are given the highest point on both the power and the interest ports. It is their ultimate duty to make sure that the plan has been executed accordingly.
2. Health and Safety Board of Directors: They have slightly less control over the system than the Government. However, their interest in the system is equally matching to that of the Government. Their duty as a stakeholder is to make sure that the system ensures each law and policy of the Health department (Gostin & Sridhar, 2014). They have the right to amend changes in the system by consulting directly or indirectly with the IT company in charge of the development.
3. The Development Company CEO: The CEO of the company that is given the rights to develop the system plays a vital role. His or her interest in the system may be lesser when compared to the Government or the Board, but however he is responsible to ensure that the project is successfully compiled by his or her employees. The CEO presides over the company and has a higher level of power over the administration of the project (Ebert, 2014).
4. The IT Development Manager: He, along with the other managers of the IT farm, works under the company head and has the power and responsibility to supervise over the working of the development team. He has the prime interest over the working of his team (Wiegers & Beatty, 2013).
5. The Network Manager: He supervises the network team and has the responsibility of ensuring that a top-notch security level is maintained in the system. This depicts the network manager’s interest in the project, as security on a public server application is considered to be of the highest priority (Perlman, Kaufman, & Speciner, 2016).
6. The Sales Manager: Has a high interest level in the project. It is the sales manager’s responsibility to ensure that the system is well-managed and promoted to reach the public and is used by every local clinic and hospital (Flaherty et al., 2012).

• Internal Executive

1. Investors: They have the highest interest in the projects among other Internal Executives and also they have decent power to negotiate details of the project with other officials involved.
2. IT and Network team: They work under their respective managers and have almost the same interest in the project with equal power.
3. Sales team: They work under te Sales Manager and are responsible for the real time execution of the promotional plans to spread the project’s awareness.
4. Customer Service: They have the lowest power and interest of all Internal stakeholders. Their job is to attend to customer complaints and report them to their supervisors in the network or IT team (Jahanshani et al., 2014).

• External Operations

1. Patients: They form one of the most important stakeholder groups for the system. Their interest is high for the proper use of the system. Though they are given the freedom to share only relevant information in the system, it is their duty to add necessary health information and dutifully provide necessary access level. Ultimately, their health is in consideration (Myhealthrecord.gov.au, 2017).
2. Hospital Management: They can check the user information history on the system and update if necessary.
3. Test Labs: They have little interest in the system but they have the power to add medical test results of the patients.
4. Local Clinics: They view the doctor-updated prescription and provide medicines accordingly. They have fair interest n the system, though low power.

• External Executive

1. Doctors: They have fair interest in the project but little power to amend changes in it.
2. Suppliers: They provide services to the system or the respective health organizations. They have little power.
3. Nurses: They have neither any power nor interest in the project. Their duty is to only respond to the advices given by the doctors and act accordingly.

Requirement Gathering Questionnaire

The questionnaire is to be sent to the Government officials, who are in duty to initiate the project.This questionnaire would help in the purpose of requirement gathering. The necessary aspects of the system are to be noted down according to the answers and the project is to be developed accordingly (Wiegers & Beatty, 2013).

Use Case Description

• Create Account: Helps new users to initiate an account.
• Add Personal Details: An inclusion of the Create Account use case, to add basic personal information.
• Set General Privacy Level: An inclusion of the Create Account use case, used to set the default privacy level of the health information to be entered.
• SignIn Error: Reports any error during account creation.
• Login: Users can login to their account.
• LogIn Error: Reports error at login.
• Home Portal Access: The Login use case includes this to give portal access.
• Edit Health Information: Allows only the user to make changes to his or her personal health information.
• View Information: Allows the user and the doctors to view already updated information. Doctors only get an abstract view of the information according to privacy.
• Help: Allows the user to seek for help, related to any problem they face using the system.
• Add Health Information: Allows the user, doctor and test labs to enter respective health related updates with time.
• Add Special Privacy: Gives the user an opportunity to put access privacy levels to their entered information, only if they wish.
• Produce Prescription: Doctors store their prescription here, the Add Health Information use case extends this on condition that user wants to add this to their database.
• Input Test Results: The test lab produces the test results and updates the database on user’s permission.
• View Prescription: Medical clinics are allowed to view the prescriptions as entered by the doctors.
• Maintenance: This use case includes several integrated sub-cases.
• Modify: This allows the software team to modify the system as initiated by the administrator.
• Repair: This allows the software team to repair the system as initiated by the administrator.
• Respond to Complaints: Review user and client complaints.

Important Use Case Description

The LogIn use case can be considered as one of the most important use cases with in the My Health Care system. It controls the operation of the entire system. It includes and extends most of the other necessary cases that are necessary for the proper execution of the entire system. The users would need this use case part to login to their respective accounts. In case of any login related error, they will be reported back with the Error use case which is an extension. Furthermore, it includes the Portal Access use case, which helps in adding, editing and viewing health information. Even the doctors and test labs can add health information of the respective patient; the user can however edit the privacy of the information (Myhealthrecord.gov.au2, 2017).

References

Digitalhealth.gov.au. (2017). My Health Record system and Healthcare Identifiers (HI) – Australian Digital Health Agency. [online] Available at: https://www.digitalhealth.gov.au/get-started-with-digital-health/what-is-digital-health/features-of-the-my-health-record-system/my-health-record-system-healthcare-identifiers [Accessed 12 Dec. 2017].

Ebert, C. (2014). Software product management. IEEE Software, 31(3), 21-24.

Flaherty, K., Lam, S. K., Lee, N., Mulki, J. P., & Dixon, A. L. (2012). Social network theory and the sales manager role: engineering the right relationship flows. Journal of Personal Selling & Sales Management, 32(1), 29-40.

Gostin, L. O., & Sridhar, D. (2014). Global health and the law. New England Journal of Medicine, 370(18), 1732-1740.

Jahanshani, A. A., Hajizadeh, G. M. A., Mirdhamadi, S. A., Nawaser, K., & Khaksar, S. M. S. (2014). Study the effects of customer service and product quality on customer satisfaction and loyalty.

Myhealthrecord.gov.au.1 (2017). My Health Record | Welcome to My Health Record. [online] Available at: https://myhealthrecord.gov.au/internet/mhr/publishing.nsf/content/home [Accessed 12 Dec. 2017].

Myhealthrecord.gov.au.2 (2017). My Health Record | Managing access, privacy and security. [online] Available at: https://myhealthrecord.gov.au/internet/mhr/publishing.nsf/Content/privacy [Accessed 12 Dec. 2017].

Perlman, R., Kaufman, C., & Speciner, M. (2016). Network security: private communication in a public world. Pearson Education India.

Thompson, R. (2012). Stakeholder analysis. Mind Tools.

Wiegers, K., & Beatty, J. (2013). Software requirements. Pearson Education.