Cloud Base Electronic Health Record Systems -Myassignmenthelp.Com

Question: Discuss About The Cloud Base Electronic Health Record Systems? Answer: Introduction: Headspace is an Australian company dealing with the mental problems of the young generation. The term "cloud-based" denotes the resources, services, and applications that are available to the users by Internet. The project at Headspace has been seeking the cloud-based solutions that are investigated in the report. The various relevant aspects of the cloud-based solutions are identified here. At first, the report describes the non-functional requirements. Next, it has reviewed the cloud-based solutions. Lastly, the relevant SDLC approach is deduced. The Non-functional requirements: Various efficient, innovative applications have been failing and breaking in the market. This happens because they have not been meeting the non-functional requirements or NFR like the overall reliability, response time and the performance. Conventionally, the architects have been reacting to the NFR by modification of the size and shape of Headspace's infrastructure. A number of users active at the same time have been managed through partitioning the user session on a various system that has been moving in parallel (de la Torre-Dez et al., 2015). The response time could be developed through the eradication of the performance bottlenecks that takes place generally in the storage usage and database. The service requirements have been met through incorporating the new devices that are capable of the high volume and quick logging of the event and much more (Gray Rumpe, 2016). However, in the environment of cloud, the options available to Headspace's architect to manage the NFRs have be en more restricted. The nonfunctional requirements are identified below. Critical system qualities: The NFRs has been persistent about the qualities. They are revisited typically as the part of the DoD or "Definition of Done" for every iteration, release and program increment. They existed in every SAFe backlog levels like the portfolio, large solution, program, and team (Helo et al., 2014). System interfaces: Headspace has been creating the POS terminal system interfacing to various service applications like the tax calculator and inventory control. Headspace's system should be tolerant towards the faults. This means as the distant service is unavailable temporarily, it should be able to capture and handle the cash payments. User interface requirements: Headspace must consider the user experience more than just delivering the user interface they have been thinking is proper. It has been turning hard in implementing the good-user interaction and interface for the SaaS offering (Abolfazli et al., 2014). This is because the spectrum of the user could improve much more. System constraints: The constraints of the NFR needed to impose on the system of IT are the technology constraints, business constraints, non-runtime qualities and the runtime qualities. The quality attributes have been the overall factors affecting the system design, user experience, and the run-time behavior. They have been representing the sectors that possess the ability for the solution to have a huge impact around the tiers and layers (Rodrigues et al., 2013). Comparison of the attributes regarding the functional and non-functional requirements: Unlike the case of functional requirements, in the non-functional sector, the application interfaces are designed with the consumer and user in mind. For this reason, they are intuitive in usage and could be localized and localized. They have been further providing access for the disabled users and delivering the efficient user experience. The reliability has been the systems' ability in continuing its operation in the desired way on time. This has been measured as the system's probability that could not fail and do its intended tasks for a particular interval of time (Al-Somali Baghabra, 2016). This has been the indication of the system's responsiveness in executing the particular tasks in a particular time gap. For the NFRs it has been measured according to the throughput and the latency. The performance of the application could affect the scalability directly. Moreover, the lack of the scalability could also affect the performance. This has been the ability of the system in reducing the scopes of accidental or malicious actions external to the designed usage impacting the system. This has been preventing the loss or disclosure of data. The development of security could also raise the system's reliability to reduce the scopes of attack impairing and succeeding the system operation. The securing of the system could also protect the resources and restrict the unauthorized access to the change of data (Sivakumar et al., 2014). The strengths and weaknesses of cloud-based solutions: With the help of cloud computing, the substantial capital expenses could save with empty in-house storage of server and application requirements. The lack of the on-premises infrastructure has been also removing the related operating expenses in the form of administration costs, air-conditioning, and the power. The cloud computing has been much more consistent and reliable with the controlled service platform. Headspace could get advantages from the huge pool of the redundant resources of IT along with the fast failover process. Manageability: The cloud computing has been delivering the simplified and the developed maintenance and management capabilities of IT via the core administration (Wang et al., 2014). The ever-rising resource of computing has been providing the competitive edge on the competitors. Headspace could deploy the critical applications delivering important business profits rather than the upfront expenses and minimal time of provisioning. Since the service providers of cloud have been taking care of various clients all the day, they have been turning overwhelmed and going against the technical outrages. This has been leading to the business processes being suspended temporarily (Khan et al., 2015). Though the service providers have been implementing the most effective security standards and the certifications from the industry, the storage of important files externally has been always being open to risks. For example, in the cloud architecture that has been multi-tenant, the multiple users could be hosted on the similar server. There any hacker could break into that data of the users stored and hosted on the similar server. Though the cloud service providers have been promising that the cloud has been flexible in usage and integration, the switching to the cloud services has not been evolved entirely. Headspace could find that hard to transmit the services from the one to other vendors (Ryan, 2013). Keeping the data secure: As the consumers go for cloud services, making sense of the standards has been important. This includes the responsibilities of the entities and then maintains the patient's trusts. For providing the foundation to address the relevant problems, with clouds, the basic understanding of the HITECH and HIPAA could be considered including the regulations, laws, and rules. The acts include the access, availability, integrity and data control along with the implications of the multitenant environments shared and data security. It has been often neglecting the intricacies of the complicated set of regulations, rules, and laws. The security and privacy have been generally used as the buzzwords, instead of considering the nuances integrated to HITECH and HIPAA. Thus they have been obscuring the value of compliance (Church Goscinski, 2014). It has been consisting of particular standards of privacy and security for particular health information known as HIPAA Privacy Rule and Security Rule. HIIPA has This act needed the secretary for expanding the Privacy and Security rules of HIPAA and raises the penalties to violate the act. At last, the office for the civil rights had the jurisdiction only on the entities covered for the security breaches. In the act of HITECH, the privacy and security rules of HIPAA has been broadened to be applied to the business associates. These are defined as the entities or persona performing particular activities or functions involving the disclosure or use of the PHI. This has been on the behalf of the delivered services to the entity covered (Babu, Lakshmi Rao, 2015). The BAs or Business Agreements has been generally delivering the services like the claims administration or processing, utilization review, data analysis or practice management. The cloud provider has been storing the PHI on the behalf of the entity covered directly. It could also be indirect via other BA. The SDLC Approach: The classic instance of the Predictive SDLC method has been the "Waterfall Model". This has been the set of series of phases flowing in definable steps. They are generally represented as the requirements captured in the software and business, designing in the software and business, construction, testing and debussing, integration, maintenance, and installation (Taleb, 2014). The classic instance of the adaptive SDLC method is the Scrum or the XP or Extreme Programming that are regarded to be agile. The Agile methods have been defined as those who have been following the Agile Manifesto. These are the set of central principles supporting the iterative development. It has been valuing the interactions and the individuals over the tools and processes and the working software on the comprehensive documentation (Inayat et al., 2017). This has also been including the collaboration of customers on the contract negotiation and reacting to the changes on following the plan. Recommendation For the project the Adaptive SDLC is suitable. This reason is described hereafter. It has been focusing on the customer satisfaction through the fast delivery of the helpful software. The working software has been delivered much frequently. This software has been basic measures of development. The late changes in the requirements are also welcomed here. They have been closing the regular operation between the developed and the business people. There could be a direct conversation as the best type of communication (Inayat et al., 2017). The Headspace project could be built across the motivated people, who might be trusted. There has been a continuous focus on the technical excellence and the good design. Moreover, it is simple, comprising of self-organizing groups and regularly adapting the changing scenarios. Conclusion: The report has described the context of the cloud system to be deployed at Headspace. It has compared the various attributes and evaluated the appropriateness. It has been also helpful in differentiating between the collected techniques and assimilating properly to the Headspace project. The report has helped in learning to formulate and justify the models of system requirements on the assessments of the provided situations. Lastly, it has recommended the Agile or Adaptive system of modeling regarding the SDLC to the project. References: Abolfazli, S., Sanaei, Z., Ahmed, E., Gani, A., Buyya, R. (2014). Cloud-based augmentation for mobile devices: motivation, taxonomies, and open challenges.IEEE Communications Surveys Tutorials,16(1), 337-368. Al-Somali, S., Baghabra, H. (2016). Investigating the Determinants of IT Professionals' Intention to Use Cloud-Based Applications and Solutions: An Extension of the Technology Acceptance.International Journal of Cloud Applications and Computing (IJCAC),6(3), 45-62. Babu, S. M., Lakshmi, A. J., Rao, B. T. (2015, April). A study on cloud based Internet of Things: CloudIoT. InCommunication Technologies (GCCT), 2015 Global Conference on(pp. 60-65). IEEE. Church, P. C., Goscinski, A. M. (2014). A survey of cloud-based service computing solutions for mammalian genomics.IEEE Transactions on Services Computing,7(4), 726-740. de la Torre-Dez, I., Lopez-Coronado, M., Soto, B. G. Z., Mendez-Zorrilla, A. (2015). Secure Cloud-Based Solutions for Different eHealth Services in Spanish Rural Health Centers.Journal of medical Internet research,17(7). Gray, J., Rumpe, B. (2016). The evolution of model editors: browser-and cloud-based solutions. Helo, P., Suorsa, M., Hao, Y., Anussornnitisarn, P. (2014). Toward a cloud-based manufacturing execution system for distributed manufacturing.Computers in Industry,65(4), 646-656. Inayat, Z., Gani, A., Anuar, N. B., Anwar, S., Khan, M. K. (2017). Cloud-Based Intrusion Detection and Response System: Open Research Issues, and Solutions.Arabian Journal for Science and Engineering,42(2), 399-423. Khan, Z., Anjum, A., Soomro, K., Tahir, M. A. (2015). Towards cloud based big data analytics for smart future cities.Journal of Cloud Computing,4(1), 2. Rodrigues, J. J., De La Torre, I., Fernndez, G., Lpez-Coronado, M. (2013). Analysis of the security and privacy requirements of cloud-based electronic health records systems.Journal of medical Internet research,15(8). Ryan, M. D. (2013). Cloud computing security: The scientific challenge, and a survey of solutions.Journal of Systems and Software,86(9), 2263-2268. Sivakumar, A., Gopalakrishnan, V., Lee, S., Rao, S., Sen, S., Spatscheck, O. (2014, February). Cloud is not a silver bullet: A case study of cloud-based mobile browsing. InProceedings of the 15th Workshop on Mobile Computing Systems and Applications(p. 21). ACM. Taleb, T. (2014). Toward carrier cloud: Potential, challenges, and solutions.IEEE Wireless Communications,21(3), 80-91. Wang, L., Wang, X. V., Gao, L., Vncza, J. (2014). A cloud-based approach for WEEE remanufacturing.CIRP Annals-Manufacturing Technology,63(1), 409-412.