Business Analysis for My Health Record- MyAssignmenthelp.com

Question: Discuss about theBusiness Analysis for My Health Record. Answer: Increased technology has facilitated the development of business and consumer-oriented online applications in various areas including healthcare. For the past few years, the healthcare sector has established numerous initiatives meant to improve the health and well-being of patients through the digital platforms. This led to the introduction of My Health Record which is to be used by health organizations to enhance the patients empowerment and their overall health. My health record is an online system that stores the summary of a patients health information. This system allows individuals to control what content should be captured and who can access their records. Also, patients have the right to choose the medical professionals to share their health information. Presently, at least 20 percent of the Australian populations are listed to My Health Record which translates to about 5 million people (My Health Record, 2012). At the same time close to 10,000 health care providers including hospitals, pharmacies, aged care facilities are connected to the system (My Health Record, 2012). To ensure that every person is receiving efficient medical services, the Australian government is working to safeguard that every Australian is registered for My Health Record. This paper tries to examine the non-functional requirements, the efficiency of the cloud-based solutions and the benefits and weaknesses of using My Health Record SDLC approach. Non-functional Requirements This section will explore the non-functional requirements that apply to My Health Records. Non-functional requirements are those features or limitations implicated on a product or system. In most cases, these requirements are usually poorly understood forcing relevant users to neglect them which pose a serious risk in requirements operations (Meulendijk et.al. 2014). FURPS is an abbreviation that is commonly used to represent a model for categorizing the quality and efficiencies of a system. They include components like usability, reliability, performance and security. Usability Refers to the simplicity in which a system can be learned or used. My health Record should be adequately intuitive to enable first-hand users to learn the basic operations of the system within a short time. Similarly, the users should be able to access any page with immediate response time and should be denied access when moving or using more than one screen to complete an obligation. Reliability Refers to the extent in which the system should work for the end users and how data can be made available to relevant parties. The specifications for this requirement incorporate the aspects of accuracy, repair time, availability and downtime. With the exception of severe disasters that distract the whole population, health organizations must have adequate local redundancies to power down non-critical systems. My Health Record should also be installed in a manner that it can immediately run on a backup power supply like the generators for a few hours to backup data. Performance Refers to the response time, capacity, and throughput of the system. It would be efficient for the user-interface monitor to respond within seconds. While searching the system for say, medication, My Health Record database should be able to display sufficient amount of data per page and give a response in a matter of seconds after retrieving a patient's information. Security Refers to the ability to provide absolute data confidentiality, availability, and integrity. My Health Record is designed in a manner to allow user authentication. This requires that anyone accessing the database must have a Login password and every patient should identify themselves when using the system End-user authentication to several applications must be enabled by a single authorization on the system. Medical practitioners with no treatment relationship with patients should only be allowed to search a patient's confidential health information through the break the glass procedure in documented critical emergencies and should generate an audit log. Review of the Cloud-based Each day more multiple billion bytes of data is produced, and the amount generated continues to grow exponentially. As a result, organizations including those in healthcare demand the need of owning and maintaining their own servers. This has contributed to the development of cloud-based technology which has become the most popular alternative. The healthcare sector, just like in other fields, requires consistent technological innovations so as to stay efficient, reliable, and timely and to deliver high standard services. To develop an effective digital health platform that the medical professionals and the patients can understand and use, it should be able to capture all data in a presentable and manageable format. The system must be easy to use and flexible to be incorporated into the daily health software in all aspects of medical care. It is evident that cloud-based computing will offer health organizations with numerous benefits. Shifting to the cloud-based system provides cost effective software for medical professionals that requires less expensive servers. Many experts believe that cloud-based technology will improve the healthcare sector by minimizing the costs associated with electronic health record start-up (Li et.al, 2013). The system automates the procedures of capturing a clients data through a series of sensors that are linked to the medical equipment and machines, and sends these data to the medical centres, that is the cloud for processing, storing, and dissemination (SENCER, 2015). Users of the cloud-based computing may also benefit for obtain immediate data collection processes anytime. The cloud system is user-friendly to help reduce manual work collection which smoothes the deployment procedures (RACGP, n.d). Financial reporting will be simplified and will be quick to generate data. This implies t hat staff will spend minimal time calculating numbers and will utilize much of their time to facilitate financially stable and cost-effective and gainful practices. There are numerous challenges that will face the healthcare organizations when they move their electronic data to the cloud. One major problem is the issue regarding the integrity and security of the patients health information (RACGP, n.d). It is possible that when data is stored on the cloud-based system, health care providers will not have full control over the security of their client's information (SENCER, 2015). There are possible dangers that patients data may be exposed to unauthorized parties or may be lost (Chen Zhao, 2012, March). Also, regulations implemented are many and may differ from one region to another concerning a clients information. Such features may make compliance with several principles possibly complex. There also exists cases where the servers may experience outages or difficulties, during such instances, availability to access patients data may be restricted. SDLC Approach Systems Development Life Cycle is a blend of the iterative and incremental processes to enhance adaptability and customer satisfaction by providing working software products (McMurtrey, 2013). SDLC offers a standard that is commonly used in project management to enhance the quality of information system. The SDLC phases involve various functional groups to work concurrently on the areas of planning, analysis, design, testing, implementation, and the maintenance. Agile and waterfall approaches are some of the SDLC models. Agile uses the adaptive approach whereas waterfall uses the predictive software development approach. The predictive approach mainly relies on the requirement planning and analysis undertaken at the start of a cycle (Georgetown University, 2017). When My Health Record is aligned with these models, any adjustments that are to be incorporated are taken through a severe modification control prioritization and management. The predictive model has numerous benefits. The approach has been found to be simple to use and understand. It has been found to work well with small projects where requirements are properly understood (Okoli Carillo, 2012). It is also easy to manage the predictive approach because of its rigidity characteristics. This is due to the fact that every stage includes some deliverables and a review process. Also, the processes and outcomes are properly documented and presented. The drawbacks of the predictive approach are that once a system has moved to the testing stage, it may be problematic to go back and make the necessary adjustments (Mikoluk, 2013). As such, this model may not work well with long, continuous and complicated projects. This model may also not be suitable for a project where requirements are highly susceptible to changes. Thus, uncertainties and threats are increasingly high with this model. The adaptive approach is mostly used where there is no detailed planning, and there exists some clarity on future obligations only in respect of what areas needs to be modified (Stoica, Mircea Ghilic-Micu, 2013). This model allows feature oriented developments and the team members involved quickly adapt to transforming the product requirement vigorously. The product developed is tested regularly to minimize the challenges of experiencing significant failures in future (Mikoluk, 2013). This approach may offer many benefits to My Health Record implementation process. This model helps to promote effective teamwork as well as cross training. Since products can be modified at the testing stage, then the adaptive approach may be the most suitable model for features that are fixed or change frequently (Okoli Carillo, 2012). Few rules may apply for this method and documentation is readily engaged. Also, this model warrants the development of concurrent products and provides results within a specified planned framework. The disadvantages of the adaptive model are that it is not suitable for handling complicated dependencies (Mikoluk, 2013). Also, an overall plan is a must otherwise the project may not generate desired output. Conclusion The concept of My Health Record is a significant step in the direction of the contemporary digitally connected environment. My Health Record has the capability of saving many human lives, time, and taxpayers' money. As must as there are doubts and uncertainties from every angle as to how My Health Record will effectively work, there is room for improvement and this system will prove to be the way forward to efficient and quality medical services. It has an absolute need among the Australian population. This system should, in theory, decrease healthcare expenses by minimizing at the very least pointless investigations. The adaptive method may be suitable when designing and implementing the My Health Record because it offers a very accurate approach to software development. References Chen, D., Zhao, H. (2012, March). Data security and privacy protection issues in cloud computing. In Computer Science and Electronics Engineering (ICCSEE), 2012 International Conference on (Vol. 1, pp. 647-651). IEEE. Georgetown University. (2017). Pros and Cons of Predictive Analysis. Retrieved on 24 May, 2017, from https://scsonline.georgetown.edu/programs/masters-technology-management/resources/pros-cons-predictive-analysis Li, M., Yu, S., Zheng, Y., Ren, K., Lou, W. (2013). Scalable and secure sharing of personal health records in cloud computing using attribute-based encryption. IEEE transactions on parallel and distributed systems, 24(1), 131-143. McMurtrey, M. (2013). A case study of the application of the systems development life cycle (sdlc) in 21st century health care: Something old, something new?. Journal of the Southern Association for Information Systems, 1(1). Meulendijk, M., Meulendijks, E., Jansen, P., Numans, M., Spruit, M. (2014). What concerns users of medical apps? Exploring non-functional requirements of medical mobile applications. Mikoluk, K. (2013). Agile vs. waterfall: Evaluating the pros and cons. Udemy/BLOG. My Health Record. (2012). Welcome to My Health Record. Retrieved on 24 May, 2017, from https://myhealthrecord.gov.au/internet/mhr/publishing.nsf/content/home Okoli, C., Carillo, K. (2012). The best of adaptive and predictive methodologies: Open source software development, a balance between agility and discipline. International Journal of Information Technology and Management, 11(1-2), 153-166. RACGP. (n.d). 2.3 Cloud Computing. Retrieved on 24 May, 2017, from https://www.racgp.org.au/digital-business-kit/cloud-computing/ SENCER. (2015). Is Storing Health-care Data in the Cloud a Good Idea? Retrieved on 24 May, 2017, from https://ww2.kqed.org/learning/2015/11/18/is-storing-health-care-data-in-the-cloud-a-good-idea/ Stoica, M., Mircea, M., Ghilic-Micu, B. (2013). Software Development: Agile vs. Traditional. Informatica Economica, 17(4), 64.