On Mon, 28 Feb 2005, Michael Ginsburg wrote:
What about a VDC?
I presume you are implying a "VistA Development Committee". Yes, such an organization could be a useful contribution and the question remains "under whose auspices?". The MDC orginally was was ANSI accredited as a Canvass type SDO but I am unaware of the proposed mechanism to be used in reactivating the MDC; originally the MUG/MTA was the Secretariat but that does not now exist for that function.
VistA is an implemented information architecture using M as a data management platform for healthcare (just one of many possible application areas which might use M). The data management technology is just one aspect of VistA. A huge component is the Conceptual Content and there are other ANSI-accredited SDOs (many of whom are members of the ANSI HISB) that deal with various aspects of the conceptual components of the Health Information Domain. A VSA would need to develop a Strategic Plan of how it would utilize the various SDO perspectives and standards in addition to having a specific relationship with the DVA about use of Life Cycle Principles (IS 12207 and IEEE standards) in definition and management of the Enterprise View encompassed by VistA. That area of VDC responsibility intersects the MDC and takes advantage of its role but also extends into many other areas that complement the MDC. Those relationships and the involvement of the health professional specialty disciplines (such AAFP) need sto be carefully laid out so that each participant knows how the different parts work. My point about the MDC is that its role in the data management platform role in the implementation infrastructure is key for VistA and provides the focal point for organizing a major part of the approaches to conceptual content as well as to the interaction with other technologies in other health information architectures with which VIstA must interoperate. Reactivation of the MDC will quickly provide a clear picture of that posture an evolutionary trajectory and that picture will facilitate the dialogs with DVA, other federal healthcare agencies and the health professional disciplines as well as industry. This will stimulate participation and help clarify how the various technologies (and their associatee products and services) might contribute and interact in a synergistic fashion. This would then involve statements of problems, alternative solutions (involving various technologies), criteria, data su[pporting the various alternatives, and documentation about decisions on implementation approaches. M would stand objectively supported by the facts and VistA architectures would likewise be understood on how such architectures used the technologic capabilities in the solution of defined problems. Today, most informatics products for healthcare are not based on that posture but rather hype and allegation. VSA should strive to defend VistA on an objective basis, exactly the way that M did within its community but which didnt reach out generally so that healthcare overall understood why the Technology to be celebrated in Boston was a signal achivement. We need to get back to this task in documnting how M contributed to VistA and how it can contribute in the future: "Enterprise View, Life Cycel Principles"
I look forward to your explicit ideas on a VDC to complemnt WV anbd VSA.
[EMAIL PROTECTED] 02/28/05 11:14 AM >>>
On Mon, 28 Feb 2005, Terry wrote:
Why?
I would argue that to have an ongoing data management component for enterprise information architectures used in healthcare enterprise there must be an organizational mechanism to examine, and update the common conventions in the M environment that enable it to interoperate with othe components in an optimally consistent way when building such architectures. Without that capability, regardless of how frequently or
infrequently it is invoked, the M environment has no ability to evolve and respond to new situations. That abilty to evolve is critical to its creditability and the present inability to do that and educate the world how the conventions in the M standards make that possible is one of the
arguments for "MUMPS is Dead!" attitudes that exist regardless of the performance/scalability and other attributes. That posture must exist in the view of those not technologically masterful of how M works.
To what end?
The component interopreability of the NHII and the NHIN that Brailer is
pushing has to be built upon a pyramid of common conventions that are seen to be dynamic, evolving and serve key roles in health information architectures as they are crafted to become an NHIN. They have to be capble of representing every complex concept that may be used in healthcare so that the technologic implementation of those cocepts best
serve the practitioner (of all specialty disciplies within healthcare) who utilizes those concept in some aspect of healthcare. The common conventions enable consistent, powerful education that show how informatics ENABLES the other four core competencies (IOM 2003). That education is still embryonic in spite of powerful tools such as the M environment. The MDC will be one of the M (and VistA)community's contribution to sthandards armamentarium meeded for consistent powerful
education; and it is key to other contributions. We either got to Fish or Cut Bait! and we must not Wait For Godot. That is the reality from my perpspective.
the
Terry L. Wiechmann
By now everyone is sick of hearing me harp on this, but this Bostonmeetingand get together with this active group of M programmers seems to meinvited ourplace to try to get the MDC going again. I trust someone hashaveGerman friends and British contacts, etc., to the get together. Ihad noaboutresponse to my email sent to Japan. If anyone has informationwho Itheirshould contact at the NEMUG to see if there is and interest amongofmembership, or if someone who has the experience and knows membersthatusers.group and could find out who has been invited and if there is anyinterest inreviving the MDC, I would appreciate hearing from you. -- Nancy Anthracite
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from realnow.Discover which products truly live up to the hype. Start readingusers.http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Terry L. Wiechmann
--
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from realDiscover which products truly live up to the hype. Start readingnow.http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
