Wednesday, December 11, 2019
System Analysis and Design for Health System - MyAssignmenthelp
Question: Discuss about theSystem Analysis and Design for Health System. Answer: Introduction My Health Records system is designed in such a way that the data of the patient is used for happier, healthier and provide more productive life benefits. Digital health system will provide the users to have greater access and control of information. This approach works with a key focus on engaging more into innovation, safety of data and clinical quality. The main agenda and focus of the system is to put the data safe that is the data which is related to patients, healthcare professionals and also consumers who have the access to look after them (Australian Digital Health Agency, 2017; Middleton, et al., 2013). System Quality and Interfaces With the introduction of health information technology, rather than improving the data quality that has to be recorded, the systems are recording data which is bad quantity and also wasting data usage. Although the systems are designed to mitigate medical errors, new type of errors comes into existence and that has to be monitored efficiently. Medical errors can be possibly eradicated with the help of automation alerts. Lack of monitoring systems safety, systems may (Agency for Helathcare Reseach and Quality, 2013): Have developed with incomplete or improper design (Bowman, 2013) Depending on unreliable software or hardware Have bugs in the programming Introducing failure models into the system etc. Poor user Interface and System Constraints In addition to poor functionality, adding poor user interface with complex nature and lack of user friendliness will degrade the trust of user. Also, it will not be able to provided intended benefit with the approach of the government. False information may lead to confusing screen errors and that gets really complicated because the end user would not even get what the error is about (Bowman, 2013). System constraints may include like inappropriate capture of the documentation, allowing the users to copy and paste any information in the data fields. This is an issue because allowing copy paste mechanism will not give complete description of the patients or users information. The data which is of readymade is used to paste and every patient has different symptoms and for this, the functionality has to be disabled and along with that, one can run or inject any malware if the user is allowed to copy and paste and then run the application to submit the data (Cloud Standards Customer Council, 2017). Along with this, security is also a big constraint in My Health Records system because the data that has been entered and sent to the databases of the system should only be accessed with the user that has been registered and unauthorized access of data will lead to steal users identification and also it is threat to the user. Performance should also be kept in mind. When there is either data breach or if the load on the server is too high, system would not respond to the user and the data that flows through the application will end up in showing error pages which is hard for an end user to know what it is (Cloud Standards Customer Council, 2017). Review of Cloud Based Architecture in My Health Records Cloud technology is attracting each and every business towards it and it is because the power it has to accumulate the data on cloud from moving out from old traditional systems of storing data in data centers which gets difficult to provide service for the customers who are outside of the zone of an organization (Singh, 2015). Take it either public, private or hybrid cloud and each of them have their own limitations and depending up on the usage and cost, organizations should decide what deployment cloud model they have to adapt to fulfill the customers and in My Health Records, providing data to the authorized users without any data-centric breaches and free flow of data from client and server end. Strengths of usage cloud architecture: Goodbye to old model systems with minimal expenditure, cloud based systems will provide adequate services that will ensure that the services are satisfactory. Accessing data from any environment one can access to data from any environment such as mobile devices, IPad, tablets etc. Expenses eliminator cloud systems will eliminate the software expenses that were in use before. Data centralization and recovery of data the data of the organization is just stored at one place and the data can be accessible from any remote location once the data is moved on cloud. And cloud systems will automatically backup data on regular basis and this will cut out the costs that were handled to maintain data in hardware which is worth of spending lots of dollars (Singh, 2015). Cloud security and free cloud storage cloud systems provide free storage service and of course upon certain limit, cost will be put onto the data. With data, deploying private or hybrid cloud will help in securing the data that is moved on cloud. Weakness of cloud based systems Internet connection and low bandwidth - to access the data which is on cloud, internet connection should be established and if the cloud architecture doesnt support enough number of users to access data then bandwidth consumption per user will be very low and this will lead to load the data more slowly and time consuming (Singh, 2015). Security issues encryption of data. Non-negotiable SLA agreements when a cloud service is chosen, organization should make sure that they concentrate on what service they are going to get and what are terms and conditions of that service. Incompatibility and complexity issues SDLC Approach on My Health Records Since My Health Records system knows what the application is about and also has clear objectives that are what to achieve and what are the outcomes of the project, clearly it is predictive SDLC approach. Since the outcomes are expected in predictive approach, following waterfall method will give enough maintainability of the system in the cycle. Pros: Known outcome Familiarity of the project for the entire team Development of the project will be thoroughly documented first Predictability of change (Warner, 2005) Cons: Limited flexibility Hard to break up the project into components and reuse them Cannot adapt with the changing technology (Warner, 2005) Adaptive SDLC approach it is generally agile and it is best in changing environments where flexibility is given as primary choice. Pros: Ready to adapt any environment Components based architecture Reusable components Ultimate flexibility (Warner, 2005) Cons: Does not have a predefined goal and outcomes are not predictive Changing environment along with the goals will take infinite time to build the application Team or the project is small because of limited resources (Warner, 2005) References Agency for Helathcare Reseach and Quality. (2013, May). Module 17. Electronic Health Records and Meaningful Use. Retrieved May 2017, from Ahrq.gov: https://www.ahrq.gov/professionals/prevention-chronic-care/improve/system/pfhandbook/mod17.html Australian Digital Health Agency. (2017). About the Agency. Retrieved May 2017, from Digitalhealth.gov.au: https://www.digitalhealth.gov.au/about-the-agency Bowman, S. (2013, October). Impact of Electronic Health Record Systems on Information Integrity: Quality and Safety Implications. Perspectives in Health Information Management, 10(Fall). Retrieved May 2017, from https://perspectives.ahima.org/impact-of-electronic-health-record-systems-on-information-integrity-quality-and-safety-implications/ Cloud Standards Customer Council. (2017, February). Impact of cloud computing on healthcare. Retrieved from https://www.cloud-council.org/deliverables/CSCC-Impact-of-Cloud-Computing-on-Healthcare.pdf Middleton, B., Bloomrosen, M., Dente, M. A., Hashmat, B., Koppel, R., Overhage, J. M., Zhang, J. (2013). Enhancing patient safety and quality of care by improving the usability of electronic health record systems: recommendations from AMIA. Journal of the American Medical Informatics Association, 20(e1), e2-e8. Retrieved May 2017 Singh, U. (2015, April 27). 11 Pros and Cons of Cloud Computing Everyone Should Know. Retrieved May 2017, from Linkedin.com: https://www.linkedin.com/pulse/11-pros-cons-cloud-computing-everyone-should-know-umesh-singh Warner, E. (2005, December 02). Adaptive vs. Predictive: Is the end clear? Retrieved may 2017, from idea.org: https://www.idea.org/blog/2005/12/02/adaptive-vs-predictive-is-the-end-clear/
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.