Re: [Hardhats-members] RE: Vista without CPRS...
Let me just add that the little exercise that we are doing here at UW is directed at just the issues brought out in this dialog thread, namely the creation of an Introduction to VistA which is based upon the the body of conceptual content informatics standards oriented to the basic care scenario. We have participants from the Health Information Management professional discipline program (aka Medical Record Administrators) herwe at UW as well as other healthcare disciplines. The intention is to have the Intro doc point to the exsiting User and Technical documentation but have enough of a global perspective and vernacular to allow entry into meaningful dialog by either non-informatics practitioners of any of the healthcare disciplines or the information engineering disciplines. This will make VistA a useful instructional tool throughout the education of the Healthcare Professions and stimulate dialog regarding evolving capabilities. I have sent one version to Nancy Anthracite for critical input regarding the ObGYn/Peds View of VistA and I solicit those who would be willing to give input regarding other Views. The evolving document set will be openly vailable via World VistA and its Education Committee hwere we hope to provoke discussion of educational approaches and issues regarding informatics subjects in the education of health professions using VistA as a comprehensive enterprise architecture foil for dialog. The intention is to work with contacts in the VA, IHS and DoD via these open organizational links to promote discussion of extensions to VistA configurations that are demonstrations of the common conventions (standards) for the conceptual content. Implementation discussions can then focus on uses of the evolving technology to best serve the target beneficiaries; it is expected that the M Technology can hold its own through performance and scalability in being components of enterprise informtion architectures. The Hardhats are an excellent forum for that kind of discussion if given the clear targets from the Conceptual Content discussion. Thus, content input from Hardhats participants will provide an immediate advantage. As soon as a World VistA and Education Committee organizational framework is documnented. UW will provide the latest versions of this document set to WV for circulation by an Open mechansism. Meantime, we solicit comments and input regarding the outine and section detail (particulalry in the implementation section which is still quite incomplete when compared to what is envisioned) so that the versions distributed ad hoc until the WV activity is formed can reflect the needed comprehensive picture. Copies of this documentation can also be provided for a hardhats central site. Arden W. Forrey PhD Dept of Restorative Dentistry University of Washington School of Dentistry 206-616-1875 Phone 206-543-7783 FAX On Mon, 27 Sep 2004, CS Wagner wrote: I must say that 99% of my frustrations come from the difficulty of finding and reading the documentation. For instance, I had no idea what the 'Add a User' command was when I started. The VA has a great volume of documentation online, but it is broken up by cryptic module names. I had to scan through each and every file on the site until I found something that looked like it might work. Luckily, Nancy sent me a document that had XUSERADD right at the top. Next, adding a patient... I don't know what module that would be in. I just want the command. After scanning a bunch (over 50) of possible docs, I found mention of DG ADD PATIENT. I tried that and it worked (of course, I still don't know what 10-10 Data is or how to add an outpatient). Side note: You cannot easily search PDF and Word documents online. It would be SO much nicer if all the documents were in HTML. I assume that the DG on DG ADD PATIENT means something to those who know the modules, but it means nothing to me because I haven't found a document that lists all the module names and what they do. I know that would be a huge list, but it could be made nicer by listing only the top 10 most used modules at the top. The same with the commands - a list of the top 20 most used commands (and what they do) would be nice. Because I am a software engineer, I recognize the problem too well. This is like trying to convert a Windows user Linux (sans GUI). They may have used DOS and they know that 'dir' will list a directory, but that won't help them figure out that it is 'ls' in Linux. Once they figure out a few commands, telling them to read the man page is a waste of time because the manual is written specifically for those who already know how to use Linux, not for those trying to figure it out. The popularity of Linux is directly related to the translation of the manuals from tech-speak to plain English. I think that Vista has the ability to become more popular as the manuals are translated from cryptic module
RE: [Hardhats-members] RE: Vista without CPRS...
Yes...we still can..thanks :-) Joseph On Mon, 2004-09-27 at 14:10, Beza, Fil wrote: Vista monographs are at http://www1.va.gov/vista_monograph/ Can you get to it from outside the VA? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beza, Fil Sent: Monday, September 27, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] RE: Vista without CPRS... At the same ftp site you obtain the CACHE.ZIP or Vista-GTM-ready.zip you will find namespaces.txt. It lists all those namespaces. Also, when you go to the Packages folder, each package folder name has its namespace, thus you will see the first as Accounts Receivable - PRCA. It might also help if you had the VistA monographs - a publication that describes the various VistA Modules and what they do. I can't find it on the FOIA Ftp site but I'll keep searching. In the meantime, somebody else may know where to get it. Probable, the VistA Documentation Library. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CS Wagner Sent: Monday, September 27, 2004 10:26 AM To: [EMAIL PROTECTED] Subject: Re: [Hardhats-members] RE: Vista without CPRS... I must say that 99% of my frustrations come from the difficulty of finding and reading the documentation. For instance, I had no idea what the 'Add a User' command was when I started. The VA has a great volume of documentation online, but it is broken up by cryptic module names. I had to scan through each and every file on the site until I found something that looked like it might work. Luckily, Nancy sent me a document that had XUSERADD right at the top. Next, adding a patient... I don't know what module that would be in. I just want the command. After scanning a bunch (over 50) of possible docs, I found mention of DG ADD PATIENT. I tried that and it worked (of course, I still don't know what 10-10 Data is or how to add an outpatient). Side note: You cannot easily search PDF and Word documents online. It would be SO much nicer if all the documents were in HTML. I assume that the DG on DG ADD PATIENT means something to those who know the modules, but it means nothing to me because I haven't found a document that lists all the module names and what they do. I know that would be a huge list, but it could be made nicer by listing only the top 10 most used modules at the top. The same with the commands - a list of the top 20 most used commands (and what they do) would be nice. Because I am a software engineer, I recognize the problem too well. This is like trying to convert a Windows user Linux (sans GUI). They may have used DOS and they know that 'dir' will list a directory, but that won't help them figure out that it is 'ls' in Linux. Once they figure out a few commands, telling them to read the man page is a waste of time because the manual is written specifically for those who already know how to use Linux, not for those trying to figure it out. The popularity of Linux is directly related to the translation of the manuals from tech-speak to plain English. I think that Vista has the ability to become more popular as the manuals are translated from cryptic module groups with cryptic file names into plain English. Also, like Linux, there is the version-specific threat. A document about using Fedora may give wrong information to a Debian user, just like a document about VistA might give wrong information to an OpenVista user. -Shaun Kevin Toppenberg wrote: Shaun, Well, my sympathies are with you. I don't know if it will help, but I compiled the following top level menus into a supermenu called adam. It helped me explore the menu options for registering patients, having nurses add vitals etc. You will have to ignore the Field etc. stuff and just look at the menu names. You can create this menu through the menu system (let me know if you need further help in that direction) or you can enter the data into the OPTIONS file directly. Good luck. Field id=MENU/.01EVE/Field Field id=MENU/SYNONYMEVE/Field Field id=MENU/DISPLAY ORDER1/Field Field id=MENU/.01ORMGR/Field Field id=MENU/SYNONYMCPRS/Field Field id=MENU/.01OR OE/RR MENU CLINICIAN/Field Field id=MENU/SYNONYMDOC/Field Field id=MENU/.01MAG SYS MENU/Field Field id=MENU/SYNONYMIMG/Field Field id=MENU/.01XUKEYMGMT/Field Field id=MENU/SYNONYMKEY/Field Field id=MENU/.01OR OE/RR MENU NURSE/Field Field id=MENU/SYNONYMNURS/Field Field id=MENU/.01FBAA MAIN MENU/Field Field id=MENU/SYNONYMPHAR/Field Field id=MENU/.01DG REGISTRATION MENU/Field Field id=MENU/SYNONYMREG/Field Field id=MENU/.01TMG TEXT MENU/Field Field id=MENU/SYNONYMTEXT/Field Field id=MENU/.01TIU MAIN MENU TRANSCRIPTION/Field Field id=MENU/SYNONYMTRAN/Field Field id=MENU/.01GMRVMGR/Field Field id=MENU/SYNONYMVITL/Field Field id=MENU/.01OR OE/RR MENU WARD CLERK
RE: [Hardhats-members] RE: Vista without CPRS...
No. Check out ftp://ftp.va.gov/vista/vistadocs/monograph/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beza, Fil Sent: Monday, September 27, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] RE: Vista without CPRS... Vista monographs are at http://www1.va.gov/vista_monograph/ Can you get to it from outside the VA? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beza, Fil Sent: Monday, September 27, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] RE: Vista without CPRS... At the same ftp site you obtain the CACHE.ZIP or Vista-GTM-ready.zip you will find namespaces.txt. It lists all those namespaces. Also, when you go to the Packages folder, each package folder name has its namespace, thus you will see the first as Accounts Receivable - PRCA. It might also help if you had the VistA monographs - a publication that describes the various VistA Modules and what they do. I can't find it on the FOIA Ftp site but I'll keep searching. In the meantime, somebody else may know where to get it. Probable, the VistA Documentation Library. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CS Wagner Sent: Monday, September 27, 2004 10:26 AM To: [EMAIL PROTECTED] Subject: Re: [Hardhats-members] RE: Vista without CPRS... I must say that 99% of my frustrations come from the difficulty of finding and reading the documentation. For instance, I had no idea what the 'Add a User' command was when I started. The VA has a great volume of documentation online, but it is broken up by cryptic module names. I had to scan through each and every file on the site until I found something that looked like it might work. Luckily, Nancy sent me a document that had XUSERADD right at the top. Next, adding a patient... I don't know what module that would be in. I just want the command. After scanning a bunch (over 50) of possible docs, I found mention of DG ADD PATIENT. I tried that and it worked (of course, I still don't know what 10-10 Data is or how to add an outpatient). Side note: You cannot easily search PDF and Word documents online. It would be SO much nicer if all the documents were in HTML. I assume that the DG on DG ADD PATIENT means something to those who know the modules, but it means nothing to me because I haven't found a document that lists all the module names and what they do. I know that would be a huge list, but it could be made nicer by listing only the top 10 most used modules at the top. The same with the commands - a list of the top 20 most used commands (and what they do) would be nice. Because I am a software engineer, I recognize the problem too well. This is like trying to convert a Windows user Linux (sans GUI). They may have used DOS and they know that 'dir' will list a directory, but that won't help them figure out that it is 'ls' in Linux. Once they figure out a few commands, telling them to read the man page is a waste of time because the manual is written specifically for those who already know how to use Linux, not for those trying to figure it out. The popularity of Linux is directly related to the translation of the manuals from tech-speak to plain English. I think that Vista has the ability to become more popular as the manuals are translated from cryptic module groups with cryptic file names into plain English. Also, like Linux, there is the version-specific threat. A document about using Fedora may give wrong information to a Debian user, just like a document about VistA might give wrong information to an OpenVista user. -Shaun Kevin Toppenberg wrote: Shaun, Well, my sympathies are with you. I don't know if it will help, but I compiled the following top level menus into a supermenu called adam. It helped me explore the menu options for registering patients, having nurses add vitals etc. You will have to ignore the Field etc. stuff and just look at the menu names. You can create this menu through the menu system (let me know if you need further help in that direction) or you can enter the data into the OPTIONS file directly. Good luck. Field id=MENU/.01EVE/Field Field id=MENU/SYNONYMEVE/Field Field id=MENU/DISPLAY ORDER1/Field Field id=MENU/.01ORMGR/Field Field id=MENU/SYNONYMCPRS/Field Field id=MENU/.01OR OE/RR MENU CLINICIAN/Field Field id=MENU/SYNONYMDOC/Field Field id=MENU/.01MAG SYS MENU/Field Field id=MENU/SYNONYMIMG/Field Field id=MENU/.01XUKEYMGMT/Field Field id=MENU/SYNONYMKEY/Field Field id=MENU/.01OR OE/RR MENU NURSE/Field Field id=MENU/SYNONYMNURS/Field Field id=MENU/.01FBAA MAIN MENU/Field Field id=MENU/SYNONYMPHAR/Field Field id=MENU/.01DG REGISTRATION MENU/Field Field id=MENU/SYNONYMREG/Field Field id=MENU/.01TMG TEXT MENU/Field Field id=MENU/SYNONYMTEXT/Field Field id=MENU/.01TIU MAIN MENU TRANSCRIPTION/Field Field id=MENU/SYNONYMTRAN/Field Field id=MENU
Re: [Hardhats-members] RE: Vista without CPRS...
I must say that 99% of my frustrations come from the difficulty of finding and reading the documentation. For instance, I had no idea what the 'Add a User' command was when I started. The VA has a great volume of documentation online, but it is broken up by cryptic module names. I had to scan through each and every file on the site until I found something that looked like it might work. Luckily, Nancy sent me a document that had XUSERADD right at the top. Next, adding a patient... I don't know what module that would be in. I just want the command. After scanning a bunch (over 50) of possible docs, I found mention of DG ADD PATIENT. I tried that and it worked (of course, I still don't know what 10-10 Data is or how to add an outpatient). Side note: You cannot easily search PDF and Word documents online. It would be SO much nicer if all the documents were in HTML. I assume that the DG on DG ADD PATIENT means something to those who know the modules, but it means nothing to me because I haven't found a document that lists all the module names and what they do. I know that would be a huge list, but it could be made nicer by listing only the top 10 most used modules at the top. The same with the commands - a list of the top 20 most used commands (and what they do) would be nice. Because I am a software engineer, I recognize the problem too well. This is like trying to convert a Windows user Linux (sans GUI). They may have used DOS and they know that 'dir' will list a directory, but that won't help them figure out that it is 'ls' in Linux. Once they figure out a few commands, telling them to read the man page is a waste of time because the manual is written specifically for those who already know how to use Linux, not for those trying to figure it out. The popularity of Linux is directly related to the translation of the manuals from tech-speak to plain English. I think that Vista has the ability to become more popular as the manuals are translated from cryptic module groups with cryptic file names into plain English. Also, like Linux, there is the version-specific threat. A document about using Fedora may give wrong information to a Debian user, just like a document about VistA might give wrong information to an OpenVista user. -Shaun Kevin Toppenberg wrote: Shaun, Well, my sympathies are with you. I don't know if it will help, but I compiled the following top level menus into a supermenu called adam. It helped me explore the menu options for registering patients, having nurses add vitals etc. You will have to ignore the Field etc. stuff and just look at the menu names. You can create this menu through the menu system (let me know if you need further help in that direction) or you can enter the data into the OPTIONS file directly. Good luck. Field id=MENU/.01EVE/Field Field id=MENU/SYNONYMEVE/Field Field id=MENU/DISPLAY ORDER1/Field Field id=MENU/.01ORMGR/Field Field id=MENU/SYNONYMCPRS/Field Field id=MENU/.01OR OE/RR MENU CLINICIAN/Field Field id=MENU/SYNONYMDOC/Field Field id=MENU/.01MAG SYS MENU/Field Field id=MENU/SYNONYMIMG/Field Field id=MENU/.01XUKEYMGMT/Field Field id=MENU/SYNONYMKEY/Field Field id=MENU/.01OR OE/RR MENU NURSE/Field Field id=MENU/SYNONYMNURS/Field Field id=MENU/.01FBAA MAIN MENU/Field Field id=MENU/SYNONYMPHAR/Field Field id=MENU/.01DG REGISTRATION MENU/Field Field id=MENU/SYNONYMREG/Field Field id=MENU/.01TMG TEXT MENU/Field Field id=MENU/SYNONYMTEXT/Field Field id=MENU/.01TIU MAIN MENU TRANSCRIPTION/Field Field id=MENU/SYNONYMTRAN/Field Field id=MENU/.01GMRVMGR/Field Field id=MENU/SYNONYMVITL/Field Field id=MENU/.01OR OE/RR MENU WARD CLERK/Field Field id=MENU/SYNONYMWARD/Field Field id=MENU/.01WVMENU/Field Field id=MENU/SYNONYMWO/Field Field id=MENU/.01YSMANAGER/Field Field id=MENU/SYNONYMYSM/Field Field id=MENU/.01ECTMGR/Field Field id=MENU/.01PX PCE CLINICIAN MENU/Field --- CS Wagner [EMAIL PROTECTED] wrote: I've actually been attempting to get Vista to a state where we can use it in production since last November. So, it is almost a year now. It took a very long time to get it installed properly because I didn't realize that M was picky about spacing and the commands kept failing. I then had a major headache getting CPRS to allow users to log in, but got that taken care of for all but one user. His last name is Nida. I set him up the same as everyone else and on the old install and the new one, he is the only one who cannot use CPRS. In the end, firewall issues with CPRS made me give up on that and I'm back to the basics - adding a patient, scheduling the patient, entering patient visit and lab data. As for contracting this to someone else, that isn't easily available. This is merely a grant study on setting up a distributed EMR system for rural clinics. There isn't much money in it. The choice of Vista came because so many of the people here work at the VA. -Shaun Kevin Toppenberg wrote: Shaun,
Re: [Hardhats-members] RE: Vista without CPRS...
Shaun, I'm with you. The documentation is terrible until you already have kind of figured out the subject. There needs to be some bridge documentation. I think our community(including you) will have to write this for the next guy... I think that those that have advanced in knowledge forget the challenges they had in the beginning, so they are not the best ones to write such bridge documentation. So, can you try to document what you figure out as you go along? I could put what you write up on my website. Someone set up a wikki that would be ideal for this...but no one seems to be adding to it. (URL on request) Kevin --- CS Wagner [EMAIL PROTECTED] wrote: I must say that 99% of my frustrations come from the difficulty of finding and reading the documentation. __ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members
RE: [Hardhats-members] RE: Vista without CPRS...
www1.va.gov/vista_monograph works outside the VA. I didn't make it a hyperlink so you could see the underscore. Paste that into your browser as it is and it will go. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Schlehuber, Cameron Sent: Monday, September 27, 2004 2:31 PM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] RE: Vista without CPRS... No. Check out ftp://ftp.va.gov/vista/vistadocs/monograph/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beza, Fil Sent: Monday, September 27, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] RE: Vista without CPRS... Vista monographs are at http://www1.va.gov/vista_monograph/ Can you get to it from outside the VA? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beza, Fil Sent: Monday, September 27, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] RE: Vista without CPRS... At the same ftp site you obtain the CACHE.ZIP or Vista-GTM-ready.zip you will find namespaces.txt. It lists all those namespaces. Also, when you go to the Packages folder, each package folder name has its namespace, thus you will see the first as Accounts Receivable - PRCA. It might also help if you had the VistA monographs - a publication that describes the various VistA Modules and what they do. I can't find it on the FOIA Ftp site but I'll keep searching. In the meantime, somebody else may know where to get it. Probable, the VistA Documentation Library. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CS Wagner Sent: Monday, September 27, 2004 10:26 AM To: [EMAIL PROTECTED] Subject: Re: [Hardhats-members] RE: Vista without CPRS... I must say that 99% of my frustrations come from the difficulty of finding and reading the documentation. For instance, I had no idea what the 'Add a User' command was when I started. The VA has a great volume of documentation online, but it is broken up by cryptic module names. I had to scan through each and every file on the site until I found something that looked like it might work. Luckily, Nancy sent me a document that had XUSERADD right at the top. Next, adding a patient... I don't know what module that would be in. I just want the command. After scanning a bunch (over 50) of possible docs, I found mention of DG ADD PATIENT. I tried that and it worked (of course, I still don't know what 10-10 Data is or how to add an outpatient). Side note: You cannot easily search PDF and Word documents online. It would be SO much nicer if all the documents were in HTML. I assume that the DG on DG ADD PATIENT means something to those who know the modules, but it means nothing to me because I haven't found a document that lists all the module names and what they do. I know that would be a huge list, but it could be made nicer by listing only the top 10 most used modules at the top. The same with the commands - a list of the top 20 most used commands (and what they do) would be nice. Because I am a software engineer, I recognize the problem too well. This is like trying to convert a Windows user Linux (sans GUI). They may have used DOS and they know that 'dir' will list a directory, but that won't help them figure out that it is 'ls' in Linux. Once they figure out a few commands, telling them to read the man page is a waste of time because the manual is written specifically for those who already know how to use Linux, not for those trying to figure it out. The popularity of Linux is directly related to the translation of the manuals from tech-speak to plain English. I think that Vista has the ability to become more popular as the manuals are translated from cryptic module groups with cryptic file names into plain English. Also, like Linux, there is the version-specific threat. A document about using Fedora may give wrong information to a Debian user, just like a document about VistA might give wrong information to an OpenVista user. -Shaun Kevin Toppenberg wrote: Shaun, Well, my sympathies are with you. I don't know if it will help, but I compiled the following top level menus into a supermenu called adam. It helped me explore the menu options for registering patients, having nurses add vitals etc. You will have to ignore the Field etc. stuff and just look at the menu names. You can create this menu through the menu system (let me know if you need further help in that direction) or you can enter the data into the OPTIONS file directly. Good luck. Field id=MENU/.01EVE/Field Field id=MENU/SYNONYMEVE/Field Field id=MENU/DISPLAY ORDER1/Field Field id=MENU/.01ORMGR/Field Field id=MENU/SYNONYMCPRS/Field Field id=MENU/.01OR OE/RR MENU CLINICIAN/Field Field id=MENU/SYNONYMDOC/Field Field id=MENU/.01MAG SYS MENU/Field Field id=MENU/SYNONYMIMG/Field Field id=MENU/.01XUKEYMGMT/Field Field id=MENU/SYNONYMKEY/Field Field id=MENU/.01OR
RE: [Hardhats-members] RE: Vista without CPRS...
I agree with David Sommers, except I am much less sophisticated. Paste your query right into google and it does a nice job of searching the vdl site including the pdf files as well as finding some unexpected other sites. Just be sure to include VistA in the search terms and it does a pretty good job of finding hits - at least with IE which is what I used most of the time until recently, when I started use Mozilla most of the time. Last time I checked, the VA was using Microsoft servers, so maybe it does matter which browser. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of CS Wagner Sent: Monday, September 27, 2004 1:26 PM To: [EMAIL PROTECTED] Subject: Re: [Hardhats-members] RE: Vista without CPRS... I must say that 99% of my frustrations come from the difficulty of finding and reading the documentation. For instance, I had no idea what the 'Add a User' command was when I started. The VA has a great volume of documentation online, but it is broken up by cryptic module names. I had to scan through each and every file on the site until I found something that looked like it might work. Luckily, Nancy sent me a document that had XUSERADD right at the top. Next, adding a patient... I don't know what module that would be in. I just want the command. After scanning a bunch (over 50) of possible docs, I found mention of DG ADD PATIENT. I tried that and it worked (of course, I still don't know what 10-10 Data is or how to add an outpatient). Side note: You cannot easily search PDF and Word documents online. It would be SO much nicer if all the documents were in HTML. I assume that the DG on DG ADD PATIENT means something to those who know the modules, but it means nothing to me because I haven't found a document that lists all the module names and what they do. I know that would be a huge list, but it could be made nicer by listing only the top 10 most used modules at the top. The same with the commands - a list of the top 20 most used commands (and what they do) would be nice. Because I am a software engineer, I recognize the problem too well. This is like trying to convert a Windows user Linux (sans GUI). They may have used DOS and they know that 'dir' will list a directory, but that won't help them figure out that it is 'ls' in Linux. Once they figure out a few commands, telling them to read the man page is a waste of time because the manual is written specifically for those who already know how to use Linux, not for those trying to figure it out. The popularity of Linux is directly related to the translation of the manuals from tech-speak to plain English. I think that Vista has the ability to become more popular as the manuals are translated from cryptic module groups with cryptic file names into plain English. Also, like Linux, there is the version-specific threat. A document about using Fedora may give wrong information to a Debian user, just like a document about VistA might give wrong information to an OpenVista user. -Shaun Kevin Toppenberg wrote: Shaun, Well, my sympathies are with you. I don't know if it will help, but I compiled the following top level menus into a supermenu called adam. It helped me explore the menu options for registering patients, having nurses add vitals etc. You will have to ignore the Field etc. stuff and just look at the menu names. You can create this menu through the menu system (let me know if you need further help in that direction) or you can enter the data into the OPTIONS file directly. Good luck. Field id=MENU/.01EVE/Field Field id=MENU/SYNONYMEVE/Field Field id=MENU/DISPLAY ORDER1/Field Field id=MENU/.01ORMGR/Field Field id=MENU/SYNONYMCPRS/Field Field id=MENU/.01OR OE/RR MENU CLINICIAN/Field Field id=MENU/SYNONYMDOC/Field Field id=MENU/.01MAG SYS MENU/Field Field id=MENU/SYNONYMIMG/Field Field id=MENU/.01XUKEYMGMT/Field Field id=MENU/SYNONYMKEY/Field Field id=MENU/.01OR OE/RR MENU NURSE/Field Field id=MENU/SYNONYMNURS/Field Field id=MENU/.01FBAA MAIN MENU/Field Field id=MENU/SYNONYMPHAR/Field Field id=MENU/.01DG REGISTRATION MENU/Field Field id=MENU/SYNONYMREG/Field Field id=MENU/.01TMG TEXT MENU/Field Field id=MENU/SYNONYMTEXT/Field Field id=MENU/.01TIU MAIN MENU TRANSCRIPTION/Field Field id=MENU/SYNONYMTRAN/Field Field id=MENU/.01GMRVMGR/Field Field id=MENU/SYNONYMVITL/Field Field id=MENU/.01OR OE/RR MENU WARD CLERK/Field Field id=MENU/SYNONYMWARD/Field Field id=MENU/.01WVMENU/Field Field id=MENU/SYNONYMWO/Field Field id=MENU/.01YSMANAGER/Field Field id=MENU/SYNONYMYSM/Field Field id=MENU/.01ECTMGR/Field Field id=MENU/.01PX PCE CLINICIAN MENU/Field --- CS Wagner [EMAIL PROTECTED] wrote: I've actually been attempting to get Vista to a state where we can use it in production since last November. So, it is almost a year now. It took a very long time to get it installed properly because I didn't realize that M was picky about spacing and the commands kept failing. I then had a major
