July 31, 2004

Architecture

A sound architectural plan will make an IT strategy, but without an IT strategy there really isn’t anyway to have an architectural plan. With the right architectural strategy, health care organizations can roll out new apps faster, and reduce maintenance costs, by having standardized structures in place. Architectural evaluation and strategizing for the future state is not really for the weak of heart. First, it is a good idea to understand what the current state of application architecture. In exhaustive detail, list all of the applications, interfaces, and processes. Include the language, vendor, platform, database engine, last release, last update for application. For interfaces include the transport mechanism, whether it is realtime or batch, if there is a standardized transaction format, the trigger mechanism, if it is manual. Have a process guide that links all of the steps together to get from the starting point to the ending point. Next figure out where you want to go, and develop a sound architectural team that will help you get there. Develop a bridge strategy, with a couple of quick wins that will help the outcome. Architecture encompasses a design of the infrastructure and policies on how to build and maintain the infrastructure. There are policies on technology standards, security standards, usability standards, change management standards, operations standards, and mechanisms for evaluating and exploiting new technologies. The goal of a good architectural strategy is to reduce complexity and cost, and make the most of what one has in house.

Posted by Elyse at July 31, 2004 7:52 PM | TrackBack
Comments
Post a comment









Remember personal info?