I think you must have missed my post that the DOD does not have it and the IHS pays for an excellent program to do it. What we need is an algorithm. The general description is relatively easy and has been done in one way or another on the CDC web site and in the document describing the IHS proprietary system. Just writing down what is needed is not needed so much as the hard work of figuring out the algorithm.
On Monday 15 November 2004 03:33 pm, A. Forrey wrote: > On Mon, 15 Nov 2004, Pat wrote: > > Nancy, and all, > > Just got off the phone with my contact from the DC Vaccines for Children > > Program. > > He did some checking after I asked him about the CDC code. > > Basically it doesn't work, hasn't worked in a while and will not be > > supported. > > The CDC may have even sent queries from this group along to him since he > > remembers getting e-mails from CDC on similar subjects. > > Nancy, Pat and all > > What would be most useful is a straighforward decription of 1) what were > the interaction (screens) and what were the data on the screens. 2) what > was staifactory or unsatisfactory about the entire dialog. 3) what would > have been most cognitively useful to pediatrians regarding child > immunizations. With that information, the descriptive documentation for > VistA can indicate what capability will be provided and what data may > already be in VIstA and what data will need to be added. The design team > can then look at the immunization function and its relationship to the > VA/DOD/IHS current functions and data structures and then working ( if > possible with the VA -with Camerons's guidance - and DoD/IHS) to propose > changes that will provide those capabilities (and later be part of FOIA > configurations). When you have some convergence on that then the > management of the Project to provide this (perhaps) different capability > that could then be a modular part of an (Open) VistA configuration could > begin and succeed in creating a architetcural component that could be > available via WV by whatever licensing arrangement is appropriate. DoD has > been immunizing folks for a long time so immunization data mangment > capbility amy already be present but it needs a different presentation. > IHS also has probably done this for Tribal health clinics. Lets learn > collbaoratively from what has been done. > > > The code he developed is proprietary and they have no plans to release > > it. > > > > He did suggest a way to start tho. Generally most programs simply count > > doses of immunizations. He indicated it's not perfectly accurate since > > there are limitations on time depending on the antigen. > > Which illustrtates that the capabilities were limited to strt with and > those needed are more extensive; the best step is to understand the > functional requirements and not rush to fiddle code. > > Arden > > > Wish I had better news. > > > > If I can be of any help with working out the algorithm let me know. > > > > Pat Evans > > > > Nancy E. Anthracite wrote: > >> Frankly, the documentation that is more sorely needed is what I have > >> called the bridging documentation between the installation instructions > >> and the VA documentation written for the VA folks that already know what > >> they are doing. The documents that Dr. Forrey is talking about are > >> indeed desirable, but with limited resources, I think we need to work on > >> these bridging documents first and then the documents that Dr. Forrey is > >> referring to except, perhaps, for the overview document that he has been > >> writing. > >> I know Dr. Forrey has put a huge number of hours into trying to start > >> the documents up for us, and I appreciate it very much, but to get > >> people up to speed to be able to use the system and to largely manage it > >> for themselves, especially those that will be planning to use it > >> developing countries, we need the bridging documents. > >> > >> On Monday 15 November 2004 12:45 pm, A. Forrey wrote: > >>> Kevin: > >>> Your situation is general to all who would adopt VistA or its various > >>> configurations. THat has been the reason that I ahve been collecting > >>> various perp[sective and putting them into the Open VistA Introduction > >>> docuimentation and associated project templates; it is intended that > >>> these documents (which are still woefully incomplete when compared to > >>> what is needed) would then be available via the WV Education Committee. > >>> We need to flesh them out here at UW in order to teach the "enterprise > >>> View, LIfe Cycel Princilpes" perspective to Health Inofrmatics Students > >>> in several programs here. But it is recognized that this general > >>> documentation should also be useful to the various Suppliers members of > >>> WV and contain all the general information about conceptual content, > >>> professional specialty perspectives as well as the general approach to > >>> implementation (including enterprise strategic planning and > >>> organizational project management related to any configuration > >>> selected). This general documentation should continue to be updated by > >>> contributions from various parties (educational and others) so that > >>> both Acquirers (such as your colleagues) and Suppliers have a complete > >>> general global picture of the realities of the VistA Information > >>> Architecture and can focus in on specializing that documentation > >>> productively for the needs of the individual enterprise and its > >>> peprspective in not only acquiring a VistA Confi=figuration but also > >>> making objective ansd accurate comparision with marketplace products > >>> and services. This will objectively, help acquirers understand how > >>> composite architetcures migt be assembled using VistA components and > >>> help Suppliers propose effective composite alternatives that make best > >>> use of the available products and services in innovative ways. Such > >>> documnteation will help the Open Source segment of the market best > >>> explain their benefits and it will provide options for healthcare > >>> enterprises. Meantime, the educational insitutions can be educating > >>> knowledgeable professional disciplines who can participate in these > >>> activities as masterful customers in concert with skilled Suppliers. If > >>> we can achive this, OpenVistA, WV and the Community can be a recognized > >>> influence in the journey to the EHr environment. > >>> > >>> Thus we need your input to flesh out this documnetation and plan its > >>> availablity to the Community via WV Education Committee activities and > >>> help save folks a lot of redundant work in understnading what VIstA is > >>> and how to use it. > >>> > >>> On Sat, 13 Nov 2004, Kevin Toppenberg wrote: > >>>> Hey all, > >>>> > >>>> I have just learned that my group is expecting me to make a VistA > >>>> presentation > >>> > >>> the first day I get back from my vacation. Surprises are the spice of > >>> life ;-) > >>> > >>>> One of the big factors the group has stressed is that they want a firm > >>> > >>> backup plan for support for any system they go with. Thus, if I leave > >>> the group etc, they would not be stuck with a system they don't > >>> understand etc. > >>> > >>> This is true of any hea;lthcare enterprise. > >>> > >>>> So I am now requesting that support venders send me e-mails for prices > >>>> for > >>> > >>> support. This would be for a system that I set up. I will be happy to > >>> go through what I have done for the setup when we get started etc. We > >>> would probably want to consider several types of coverage options. > >>> I'll list these below. > >>> > >>> We need general information for a WV informational website about the > >>> nature of the marketplace; i. e. Venodors, products, standards > >>> conformance attributes. > >>> > >>>> I have been given some estimates that were "on the high end" when I > >>>> first > >>> > >>> started learning VistA, though these were for a complete install. I > >>> mention this because I'm not interested in anyone making a fast buck > >>> off our group. We will happily pay fair wages for services rendered. > >>> But we want reasonable rates. Also, I have been asked in the past to > >>> keep bids sent to me secret. I think this is contrary to competition, > >>> so would not be able to promise this. > >>> > >>>> So with that behind us, I'd love to receive bids for VistA software > >>>> support. > >>>> > >>>> > >>>> > >>>> I started to try to device a division plan for the various levels of > >>>> support, > >>> > >>> i.e. 24-7 vs. weekdays, installation programming vs. telephone support > >>> etc. But it seemed that every company may already have theirown scheme. > >>> So I'll just see what you all have to offer. > >>> > >>>> So this is where the OpenSource model is supposed to shine: Free > >>>> code, > >>> > >>> but viability through paid support. I hope its all true.... > >>> > >>> Gather the info as it will be valuable for not only the current > >>> purchasers considering VistA but also the educational setting where the > >>> current students will be looking at the Supplier's lists. > >>> > >>> The WV meeting this Friday should address getting thsi kind of > >>> information collected and also passed to the education activities -its > >>> your future market! > > >>> > >>>> Kevin > >>>> > >>>> > >>>> > >>>> --------------------------------- > >>>> Do you Yahoo!? > >>>> Check out the new Yahoo! Front Page. www.yahoo.com > >>> > >>> ------------------------------------------------------- > >>> This SF.Net email is sponsored by: InterSystems CACHE > >>> FREE OODBMS DOWNLOAD - A multidimensional database that combines > >>> robust object and relational technologies, making it a perfect match > >>> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > >>> _______________________________________________ > >>> Hardhats-members mailing list > >>> [EMAIL PROTECTED] > >>> https://lists.sourceforge.net/lists/listinfo/hardhats-members > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: InterSystems CACHE > > FREE OODBMS DOWNLOAD - A multidimensional database that combines > > robust object and relational technologies, making it a perfect match > > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > > _______________________________________________ > > Hardhats-members mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > ------------------------------------------------------- > This SF.Net email is sponsored by: InterSystems CACHE > FREE OODBMS DOWNLOAD - A multidimensional database that combines > robust object and relational technologies, making it a perfect match > for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 > _______________________________________________ > Hardhats-members mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members
