Peachtree Healthcare has been faced with a quandary. There has been a major IT substructure job within the company for some clip now. Since engineering has taken over in the healthcare field. it is imperative that Peachtree Healthcare acquire the engineering needed so that they can be trusted and good known within the health care industry.
Mission
The mission of Peachtree Healthcare is to guarantee quality. consistence. and continuity of attention across the full web – and to present attention with the highest degrees of efficiency and economic system while keeping regard for patients and staff.
Aims
The infirmary needs to make up one’s mind on what long / short term IT substructure system schemes and roadmaps are needed to increase efficiency. The new system should let sharing of patient records. guarantee quality. consistence. and continuity of attention across full web of infirmaries and doctors.
Key Issues
The IT substructure is non dependable ; hence. utilizations are unable to execute their twenty-four hours to twenty-four hours maps including clinical responsibilities. This is impacting quality and safety of patient attention.
Recommendations
Adopt service oriented architecture ( SOA ) which will enable selective standardisation.
Current SITUATION ( 10 )
Peachtree Healthcare has major IT substructure jobs and is fighting to happen the right hole. Growth through acquisitions has led to the heritage of many incompatible bequest systems. Current IT resources are focused on keeping inefficient procedures in order to maintain the infirmary running. The care costs of the current IT system are so high that farther invention has become a luxury.
In add-on there have been recent meltdowns of clinical information systems. IT substructure is non dependable ; therefore users are unable to execute their twenty-four hours to twenty-four hours maps. including clinical responsibilities. This is impacting quality and safety of patient attention.
Furthermore there is force per unit area from the hospital’s board to standardise infirmary processs and patterns without to the full measuring the demand for it. Max Berndt ( CEO ) . Candace Markovich ( CIO ) and Tom Drane ( CFO ) are fighting to analyse the current state of affairs subjectively in order to decently pull off the force per unit area to follow rivals.
CRITERIA ( 5 )
The infirmary needs to make up one’s mind on what long / short term IT substructure system schemes and roadmaps are needed to increase efficiency. The new system should let sharing of patient records. guarantee quality. consistence. and continuity of attention across full web of infirmaries and doctors. The system should besides guarantee “selective” standardisation of certain medical processs across the web but let sufficient flexibleness to single infirmaries and professionals in other countries.
Other standards include:
• Time to value – when will the new system realize value for each concern unit • Flexibility – easy to modify. ascent and customization capablenesss • Staff buy-in – ability to convert all staff to give this undertaking a attempt
ALTERNATIVES & A ; RECOMMENDATIONS ( 15 )
Alternate 1: Massive System ( Modular Enterprise System ) A massive system is individual set of systems and applications that will supply consistence across Peachtree’s installations but may non give physicians adequate flexibleness. Other pros and cons include:
Alternate 2: Service-Oriented Architecture ( SOA ) System
A servicer-oriented architecture system is modular design that will let Peachtree to standardise incrementally and selectively but poses certain hazards as a newer engineering.
Recommendation:
My recommendation is to wrinkle a scheme of selective standardisation utilizing a SOA system. This means measuring and make up one’s minding on a SOA architecture criterion. Reviewing single concern maps and make up one’s minding on an ideal criterion for that functional unit so migrating others to it. This will let Peachtree to standardise incrementally. which Max has wanted most in an IT substructure.
RISK MANAGEMENT PLAN ( 15 )
Since SOA is a new engineering. there are serious hazards and effects involved with this attack. The SOA engineering is non mature yet and has non been tested in the long term. As a consequence there is a batch of capriciousness.
To extenuate these hazards Peachtree should bit by bit replace its old system with the SOA System. They should continue with SOA in phases by flying smaller undertakings to rapidly supply value to concern units. By bit by bit put ining the SOA. Peachtree and its physicians would larn about how the systems worked and they could so get the hang it in a sense as the substructure moved farther. By bit by bit put ining the substructure. Peachtree would non merely minimise hazard but besides create flexibleness and control. With the gradual acquisition procedure on the new SOA system. Peachtree and its doctors would let IT to switch precedences along the manner.
Peachtree should besides make instance surveies to acquire other concern units and sellers support throughout roll-out procedure. They should besides see engaging external alteration direction advisers to guarantee minimal user break and smooth passage into the new system.
