Mental Health Care Patient Management †Free Samples for Students

Question: Mental Health Care Patient How Do Management? Answer: Introduction Health information is extremely important and sensitive information that is required to be handled with utmost care. One of the regional health authorities wishes to manage the health information associated with it by implementing an automated information system. Mental Health Care Patient Management System (MHCPMS) is being developed in order to fulfill the requirements of the authority. MHCPMS Stakeholders There are several stakeholders that are associated with MHCPMS which are listed and described below. Owner of the regional health authority: The owner of the regional health authority will gain abilities to easily manage and streamline the health information. External Partners and Suppliers: There is a lot of medical equipment that is supplied to the regional health authority and the exact need of the equipment will be calculated and devised through the system [1]. End Users: Clinical staff, receptionist and medical records staff will be using the system to handle and organize the information. Patients: The health information of the patients will be handled safely and securely. Requirements Gathering Interviews Interviews shall be organized with the end users of the system, owners along with the medical fraternity to understand the specifications of the system. Interview sessions shall focus upon gaining the maximum response from the interviewees and the questions shall be designed accordingly [2]. Questionnaire and Surveys There will be multiple entities that will be associated with MHCPMS and questionnaires around the requirements will make it easy to understand and analyze the response that is provided. Brainstorming Sessions and Workshops These activities shall be carried out in groups to understand the areas of requirements that shall be focused upon [3]. Identification of System Requirements Apart from the stakeholders associated with the system, it would be necessary to understand the functional and non-functional aspect of the system to come up with a desired end product as an outcome. System requirements will therefore play a significant role in association with MHCPMS. These system requirements shall be determine by collecting data from several sources such as drawbacks of the existing system, expectations of the end users, comments from system experts and analysts and likewise. Also, the compatibility of the system to be developed with other information systems in the regional health authority shall also be determined [4]. It would be extremely essential to identify the system requirements precisely because the output would depend upon the activities that would be covered under this particular step. Primary Functional Requirements Ability to the users to log in to the Mental Health Care Patient Management System to gain access to the health information Ability to uniquely identify the health information of every mental health patient with the aid of a unique patient id [5] Ability to allow the clinical staff and other users to key in the patient id to retrieve the health information of a medical health patient Ability to allow the users to retrieve the health information on the basis of a particular mental health condition, medical provider or as per specific date Ability to allow the users to extract reports from the system on the basis of several parameters such as mental health patient, specific dates, specific medical practitioner and likewise Ability of the system to show the messages to the users in case of a wrong input or an incorrect search keyword [6] Ability to allow the users to manage their user account by allowing them to update their account password and also make changes to their personal information Ability to allow the users to choose from several formats before downloading the medical reports Ability to allow the admin user to grant privileges and roles to the user accounts that are set up on the Mental Health Care Patient Management System Non-functional Requirements Usability Usability shall be included as a non-functional requirement and as a system quality in Mental Health Care Patient Management System. The users shall be allowed to experience a system that shall be easy to use and navigate. Also, the system shall allow the users to understand the various options offered by the system without any need to seek for assistance and support. The functionalities and features that are provided by the system must also fall in line with the specifications and requirements that are provided [7]. Safety Safety of the health information is very essential as the health information of a patient is extremely sensitive in nature. Also, there are two different legislations that apply to the information that will be contained under Mental Health Care Patient Management System. The system therefore shall be designed in such a manner that it has the security mechanisms installed to prevent, detect and control all of the security risks and attacks. Also, it shall not allow the malevolent entities to gain entry to the system without authorized access. The entire information sets shall also be encrypted to ensure that there are no compromises on the safety and security. Privacy Privacy of information will also be equally essential as the safety of the medical information contained in Mental Health Care Patient Management System. The system shall therefore be designed in such a manner that the identity and access control is reflected and maintained at all times. The health information associated with any of the mental health patient shall not be lost or leaked at any point of time [8]. Operational Cost Manual handling of such huge clusters of information leads to the redundancy and duplication of a lot of data leading to unnecessary re-work and management. There is a lot of operational cost that is involved in such cases which would be minimized with the adoption and implementation of Mental Health Care Patient Management System. The information would be stored and handled in an automated manner which would remove all the unnecessary expenditure associated with the operations. References [1]L. Bourne, "Stakeholder Relationship Management", 2016. [Online]. Available: https://www.mosaicprojects.com.au/PDF_Papers/P128b_Stakeholder_Relationship_Management.pdf. [Accessed: 28- Apr- 2017]. [2]R. Silhavy, "Requirements Gathering Methods in System Engineering", 2014. [Online]. Available: https://www.wseas.us/e-library/conferences/2011/Lanzarote/ACMOS/ACMOS-17.pdf. [Accessed: 28- Apr- 2017]. [3]R. Young, "Recommended Requirements Gathering Practices", 2012. [Online]. Available: https://pdfs.semanticscholar.org/5544/e7366b6c1e261a7c099af89475f1e71f6ac4.pdf. [Accessed: 28- Apr- 2017]. [4]A. Chakraborty, "The Role of Requirement Engineering in Software Development Life Cycle", 2012. [Online]. Available: https://www.researchgate.net/publication/267631563_The_Role_of_Requirement_Engineering_in_Software_Development_Life_Cycle. [Accessed: 28- Apr- 2017]. [5]R. Malan, "Functional Requirements and Use Cases", 2011. [Online]. Available: https://www.bredemeyer.com/pdf_files/functreq.pdf. [Accessed: 28- Apr- 2017]. [6]B. Paech, "Functional requirements, non-functional requirements, and architecture should not be separated A position paper", 2012. [Online]. Available: https://pdfs.semanticscholar.org/322f/5199bbf08f9b1b442b50ae961672277e52dd.pdf. [Accessed: 28- Apr- 2017]. [7]L. Chung, "Non-Functional Requirements", 2013. [Online]. Available: https://www.utdallas.edu/~chung/SYSM6309/NFR-18-4-on-1.pdf. [Accessed: 28- Apr- 2017]. [8]M. Glinz, "On Non-Functional Requirements", 2015. [Online]. Available: https://www.ptidej.net/courses/log3410/fall11/Lectures/Article_6.pdf. [Accessed: 28- Apr- 2017].