“One of the realities of the IT domain is that, unless you are the first vendor to offer a solution for a particular domain, you are quite likely to be replacing a legacy solution with your offering.
The existence of a legacy system makes the process of EHR implementation much more complex compared to lack of it, and this complexity is usually not managed very well, leading a couple of repeating, hard to avoid problems. The definition of a legacy system is important in this context, since I am claiming that it is a part of an anti pattern. I’d like to describe the legacy system a little bit more, so that the upcoming problem definitions do not refer to a vaguely defined context.”
Article
Musings by Seref Arikan, 15 March 2010
