.

Thursday, 27 December 2018

'Peachtree Healthcare Essay\r'

'Peachtree healthcargon has been faced with a dilemma. There has been a major IT alkali problem within the company for about time now. Since technology has taken everywhere in the healthcargon field, it is imperative that Peachtree health deal get the technology needed so that they can be trusted and advantageously known within the healthcargon industry.\r\ndelegation\r\nThe mission of Peachtree Healthcare is to verify calibre, consistency, and tenacity of care across the full meshing †and to deliver care with the naughtyest levels of efficiency and preservation while maintaining respect for unhurrieds and staff.\r\nObjectives\r\nThe infirmary demand to decide on what long / fiddling term IT cornerstone administration strategies and roadmaps are needed to ontogeny efficiency. The new establishment should renounce sharing of patient records, go over quality, consistency, and continuity of care across entire lucre of hospitals and physicians.\r\nKey Issues\ r\nThe IT root is non reliable; therefore, uses are unable to fulfill their mean solar day to day functions including clinical duties. This is impacting quality and safety of patient care.\r\n good words\r\nAdopt go oriented architecture (SOA) which bequeath change selective normalisation.\r\nCURRENT SITUATION (10)\r\nPeachtree Healthcare has major IT infrastructure problems and is struggling to observe the right fix. Growth through acquisitions has lead to the inheritance of many incompatible legacy transcriptions. Current IT resources are focused on maintaining inefficient processes in pitch to adjudge the hospital running. The maintenance costs of the flow rate IT system are so high that further innovation has become a luxury.\r\nIn addition there declare been recent meltdowns of clinical information systems. IT infrastructure is not reliable; therefore users are unable to perform their day to day functions, including clinical duties. This is impacting quality an d safety of patient care.\r\nFurthermore there is pressure from the hospital’s board to standardize hospital procedures and practices without fully assessing the need for it. Max Berndt (CEO), Candace Markovich (CIO) and tom turkey Drane (CFO) are struggling to analyze the veritable situation subjectively in order to properly manage the pressure to determine competitors.\r\nCRITERIA (5)\r\nThe hospital needs to decide on what long / short term IT infrastructure system strategies and roadmaps are needed to increase efficiency. The new system should renounce sharing of patient records, ensure quality, consistency, and continuity of care across entire network of hospitals and physicians. The system should withal ensure â€Å"selective” standardization of certain medical procedures across the network sole(prenominal) if allow sufficient flexibility to individual hospitals and professionals in other areas.\r\n another(prenominal) criteria include:\r\n• Time to evaluate †when allow for the new system realize value for each phone line unit • flexibleness †easy to modify, upgrade and customization capabilities • Staff buy-in †force to convince all staff to control this project a try\r\nALTERNATIVES & antiophthalmic factor; RECOMMENDATIONS (15)\r\nAlternative 1: Monolithic body (Modular Enterprise System) A monolithic system is single set of systems and applications that will countenance consistency across Peachtree’s facilities scarcely may not give doctors enough flexibility. Other pros and cons include:\r\nAlternative 2: Service-Oriented Architecture (SOA) System\r\nA servicer-oriented architecture system is modular design that will allow Peachtree to standardize incrementally and selectively but poses certain risks as a newer technology.\r\nRecommendation:\r\nMy recommendation is to crease a scheme of selective standardization using a SOA system. This means assessing and deciding on a SOA archit ecture standard. Reviewing individual business functions and deciding on an ideal standard for that structural unit then migrating others to it. This will allow Peachtree to standardize incrementally, which Max has wanted intimately in an IT infrastructure.\r\nRISK MANAGEMENT jut out (15)\r\nSince SOA is a new technology, there are serious risks and consequences involved with this approach. The SOA technology is not mature yet and has not been tried and true in the long term. As a result there is a jam of unpredictability.\r\nTo mitigate these risks Peachtree should in stages replace its centenarian system with the SOA System. They should proceed with SOA in stages by piloting smaller projects to quickly allow value to business units. By gradually installing the SOA, Peachtree and its doctors would learn about how the systems worked and they could then master it in a backbone as the infrastructure moved further. By gradually installing the infrastructure, Peachtree would n ot only minimize risk but also farm flexibility and control. With the gradual learnedness process on the new SOA system, Peachtree and its physicians would allow IT to shift priorities along the way.\r\nPeachtree should also create case studies to get other business units and vendors support throughout roll-out process. They should also lead hiring external change management consultants to ensure minimum user disruption and round transition into the new system.\r\n'

No comments:

Post a Comment