Bhaskar makes an important point but note that the Life Cycle processes denote the ways to document standards conformity to "requirements" and carry these forward during the acquisition steps well described in Life Cycle standards. Health Acquirers MUST learn the these principles or risk being conned out of their skivvies as there are ample examples to illustrate. Thus, the M community must understand how the capabilities noted in the acquisition documents will pose the technical capabilities for components of information architectures being acquired and be prepared to respond effectively. The fact that many acquirers are presently ignoramuses should not deter M Supplier from being competent to respond to those that are not but require documnted responses regarding standards conformance. The NHIN ONCHIT effort will hopefully, awaken via incentives and rewards, the skills and knowledge by both Suppliers and Acquirers needed to get effective information architectures. M and VistA components could certainly contribute but be sure and understabnd both Conceptual Content as well as Implementing Technology as they are synergistic. The NHIN WILL be built on standrds conformance else it wont work. So be ready.

On Thu, 25 Nov 2004, K.S. Bhaskar wrote:

While I like the idea of standards, and have been involved in standards
activities in other places and times (although not personally in the
MDC, I did pay for representation from GT.M), it would seem to me that
useful standards require multiple implementations from competing
vendors.

For vendors to implement systems that are compliant with standards,
there must be some financial incentive for them to do so, such as
customers requiring standards compliance for the products they select.
Otherwise, vendors that invest in making their products standards
compliant are only shooting themselves in the foot, because competitors
that don't invest in standards compliance will laugh all the way to the
bank.

In the area of desktop operating systems, for example, there are no
standards because customers have not provided an incentive for the
industry leader to implement any standard except its own proprietary
"standard".  M may not be in that different a state.

If we are going to revive standards efforts, let's make sure we have a
plan for the effort to take us somewhere.

-- Bhaskar



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Hardhats-members mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to