Selecting an interface engine for your healthcare organization is not a trivial matter. The decision you make will impact the reliability and flexibility of healthcare data delivery within and outside your organization for years to come. The costs are much broader than what you pay the software vendor; deployment, migration, training, and support hours required to adapt to a new engine are usually more than the software licensing fees. The importance of "fit" cannot be overstated; internal costs will vary widely depending on the engine's features and the context and culture of your organization.
Why would I bother with a process when I already know what I want?
You only know what you know; what you don't know can cause much pain and lost opportunity. A rigorous and defined selection process has many benefits for you and your organization. For you it may be simple job preservation; a failed interface engine replacement is not career enhancing. For your organization it is not only better for the bottom line in terms of overall costs and organizational agility, it can be an opportunity to clearly define the interface team's role in your organization. In the process of discovering what the interface team wants as a central application for delivering interfaces they also learn more about how they function as a team which leads to improved effectiveness.
Who else would care about using a process like this?
Anyone who is responsible for selecting a new interface engine should read through and thoroughly understand the process they will be using for selection. An IT Director or Project Manager typically leads the selection process and should be able to articulate to other stakeholders how it works. The Lead interface developers who will be using the tool set selected will be taking an active role in the process so they need to understand it as well as the Director or PM leading the effort. IT portfolio managers will want to understand the process that will be used to select another major platform in the enterprise.