1 / 9

Too Far Ahead of the IT Curve?

Too Far Ahead of the IT Curve?. Michele Hom Dr. Minder Chen BUS 550 5/10/11. Harvard Business Review – July/August 2007. Agenda. Background The dilemma Monolithic vs SOA Pros and Cons Possible Solutions Question Discussion (if time permits). PEACHTREE HEALTHCARE.

edita
Download Presentation

Too Far Ahead of the IT Curve?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Too Far Ahead of the IT Curve? Michele Hom Dr. Minder Chen BUS 550 5/10/11 Harvard Business Review – July/August 2007

  2. Agenda • Background • The dilemma • Monolithic vs SOA • Pros and Cons • Possible Solutions • Question • Discussion (if time permits)

  3. PEACHTREE HEALTHCARE • CEO= Max Berndt (12 yrs at institution) • Encompasses 11 mid-large sized institutions plus: • Supported by: • Ancillary clinics • Practicing MDs • Trauma centers • Rehabilitation facilities • SNFs • Over 4000 employees • Mission is: • To deliver the best quality and efficient care • IT infostructure is collapsing

  4. Should the CEO approve a shift to risky new technology or for with the time-tested monolithic system?

  5. MONOLITHIC SYSTEM • Functionally distinguishable aspects are • not architecturally separate components • but are all interwoven SERVICE-ORIENTED ARCHITECHTURE • Loosely coupled architecture designed to • meet the business needs of the organization • Autonomous services

  6. Monolithic System SOA Outline PROS CONS • Consistent infostructure • Unifying for all new/current • facilities • Allows MDs to work together • Quick • Flexibility in $ • Ability to integrate new • facilities • Immature market • Experimental • Different for all • Never before in HC • Cost ?? • Time ?? • $500 million + • TIME • Redesign acquired facilities • Curbs MD independence

  7. POSSIBLE Solutions?? • Define clear criteria for system capabilities • Create a risk profile • Construct from the desired goals and establish a • plan for achievement • Incorporate a β center and expand

  8. Question The ability to loosely couple architecture designed to meet the business needs of the organization is: A. Monolithic system B. Enterprise system C. SOA (Pick this one!) D. Microlithic system

  9. Discussion • How do you think the implementation of a • SOA can impact healthcare? • Can a system streamline medical decisions • or will there be push back from MDs?

More Related