Peachtree summize Essay Example | Topics and Well Written Essays - 1250 words

Peachtree summize - Essay Example The current pressure stems from standardization in other sectors such as banking that cannot be fully afforded to more critical areas like healthcare without great thought. Moreover, recent failures at new Peachtree Healthcare acquisitions are pressuring management to go for an overhaul of the current IT infrastructure. Change of Opinion Before looking into the commentaries, I was more focused on the technical aspect of the problem with regards to implementing either SOA or a monolithic system. The human aspect of the problem as advocated by Kastor was not under consideration while framing recommendations. Moreover, my approach to problem solving for Peachtree Healthcare was more dependent on deriving a fitting monolithic, SOA or hybrid monolithic SOA framework for Peachtree Healthcare but as advocated by Halvorson, such a resolution would not be possible without considering the objectives that require achievement. Creating and maintaining an effective corporate strategy requires tha t objectives are taken into primary focus before any other implementations are considered (Johnson, Scholes, & Whittington, 2008). Ranking Commentator Opinions George C. Halvorson Paul Lefler’s standardization approach will not be able to deliver results for all parts of the healthcare sector in the case of Peachtree Healthcare. ... Another notable aspect of Halvorson’s approach is his critique on trying to use tools without realizing what objectives require achievement. In this respect, Halvorson is totally justified in commenting that Peachtree Healthcare should tabulate its needs and requirements and should then proceed to procure fitting tools. Monte Ford Ford essentially raises an important point and then fails to see through it – risk management. Ford suggests that Peachtree Healthcare should tabulate the available risk but this is not really possible given the eclectic nature of operations at any healthcare institution. He further suggests that Peachtree Healthcare should follow Candace’s opinion of implementing a â€Å"modular SOA† structure (Glaser, 2007) while keeping in mind areas where such a solution would work and where it would not. Again, the recommendation provided by Ford is largely vague and unrealizable since risk tabulation for what would work and what would not w ork requires taking risks that might entail patient’s lives. Providing analogies for an airline reservation system and a clinic’s basic systems is also illogical since clinical operations are too varied to be standardized this simply. For example, a patient requiring treatment for a common cold would differ significantly from a patient requiring treatment for tuberculosis. Randy Heffner Randy Heffner’s ideas are best summarized by his last line in the commentary when he states that Candace should â€Å"redo her decision analysis and strategy planning, looking at SOA through a business lens† (Glaser, 2007). Heffner is right at declaring the rising popularity and efficacy of SOA but