Case Study - Too Far Ahead of the It Curve Essay

1185 Words Feb 18th, 2013 5 Pages
CASE STUDY
Too Far Ahead of the IT Curve
EXECUTIVE SUMMARY
Peachtree Healthcare (PH)’s mission are ensures quality, provide consistency and continuity of care across the entire network, to deliver care with the highest levels of efficiency and economy, and maintain respect for patients and staff. The objective of PH is to offer all kinds of treatments so patients' care would be continued without any disruption.
PH’s patchwork IT infrastructure is in critical condition, so it has major IT infrastructure problems. CEO of PH Max Berndt is trying to find the right solution. He has an option to go with monolithic system that will provide consistency across PH’s facilities but may not give doctors enough flexibility or he can choose
…show more content…
The objective of PH is to offer all kinds of treatments (i.e. ancillary clinics, physician practices, rehabilitation facilities, trauma centers, and nursing homes) so patients' care would be continued without any disruption. Nowadays healthcare’s trend is to have a network of clinics instead specialization ones.
PH should focus on ensures quality, provide consistency and continuity of care across the entire network, to deliver care with the highest levels of efficiency and economy, and maintain respect for patients and staff. So these are important to the stakeholders of PH: employees, patients and their family, business partners, and board of directors.
ALTERNATIVES AND RECOMMENDATION
There are two options to address the current problems and meet future objectives: * Arrange a monolithic system that will be much more manageable but will also standardize the business processes across the network * Apply Service Oriented Architecture (SOA) which will enable selective standardization
Proposed IT Systems for PH: SOA Vs Monolithic Systems
Pros of SOA: * Easy to use Web services * Quickness/replace old system overtime * Flexibility to go after selective standardization * Can attempt on a limited scale/move slowly to reduce risk * Full advantage of the legacy system’s functionality
Cons of SOA: * Immature SOA market/New

Related Documents