Ignacio Valdes Implementation Log/Episode1 - Revision history

DavidWhitten: DavidWhitten moved page Ignacio Valdes Implementation Log/Episode 1 The Layer Cake to Ignacio Valdes Implementation Log/Episode1 over redirect

2020-11-13T04:40:49Z

DavidWhitten moved page Ignacio Valdes Implementation Log/Episode 1 The Layer Cake to Ignacio Valdes Implementation Log/Episode1 over redirect

← Older revision	Revision as of 04:40, 13 November 2020
(No difference)

DavidWhitten at 04:29, 13 November 2020

2020-11-13T04:29:13Z

← Older revision		Revision as of 04:29, 13 November 2020
Line 178:		Line 178:
	Rick		Rick

	[Ignacio Valdes Implementation Log\|Back to Log Homepage]] [[Ignacio Valdes Implementation Log/Episode2]]		[[Ignacio Valdes Implementation Log\|Back to Log Homepage]] [[Ignacio Valdes Implementation Log/Episode2\|Episode 2]]

	[[Category:Intracare Implementation Log]]		[[Category:Intracare Implementation Log]]

DavidWhitten at 04:28, 13 November 2020

2020-11-13T04:28:33Z

← Older revision		Revision as of 04:28, 13 November 2020
Line 1:		Line 1:
	==The ~~Intracare Implementation Log~~ [[~~Intracare~~ Implementation Log\|(Back to Log Homepage)]] [[Episode2\|(On to Episode 2)]]==		==The [[Ignacio Valdes Implementation Log\|(Back to Log Homepage)]] [[Ignacio Valdes Implementation Log/Episode2\|(On to Episode 2)]]==

	Like most mature systems, VistA is a combination of old and new. Parts are decades old and other parts are as new and modern as yesterday. This is an attempt to divine the layers for newcomers.		Like most mature systems, VistA is a combination of old and new. Parts are decades old and other parts are as new and modern as yesterday. This is an attempt to divine the layers for newcomers.
Line 178:		Line 178:
	Rick		Rick

	[~~[Intracare~~ Implementation Log\|Back to Log Homepage]] [[Episode2]]		[Ignacio Valdes Implementation Log\|Back to Log Homepage]] [[Ignacio Valdes Implementation Log/Episode2]]

	[[Category:Intracare Implementation Log]]		[[Category:Intracare Implementation Log]]

DavidWhitten: DavidWhitten moved page Episode 1 The Layer Cake to Ignacio Valdes Implementation Log/Episode 1 The Layer Cake

2020-11-13T04:22:12Z

DavidWhitten moved page Episode 1 The Layer Cake to Ignacio Valdes Implementation Log/Episode 1 The Layer Cake

← Older revision	Revision as of 04:22, 13 November 2020
(No difference)

NeilArmstrong: Added glossary link to Configuration~

2012-11-01T20:04:28Z

Added glossary link to Configuration~

← Older revision		Revision as of 20:04, 1 November 2012
Line 33:		Line 33:
	So:		So:

	In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient [[record~\|Record]], as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as configuration users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].		In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient [[record~\|Record]], as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as [[configuration~\|Configuration]] users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].

	But for years now [[clinical users~\|Clinical Users]] in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs. Get it [[Astronaut VistA\|here]].		But for years now [[clinical users~\|Clinical Users]] in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs. Get it [[Astronaut VistA\|here]].

NeilArmstrong: Added a glossary link to Business Rules~

2012-08-04T09:43:41Z

Added a glossary link to Business Rules~

← Older revision		Revision as of 09:43, 4 August 2012
Line 91:		Line 91:
	3. K.S. Bhaskar Local: Fri, Jul 11 2008 6:43 pm		3. K.S. Bhaskar Local: Fri, Jul 11 2008 6:43 pm

	I wonder if there is a confusion between installing VistA and configuring VistA. Installing VistA is truly simple - with a SemiVivA Lite, for example, it is one command. Configuring VistA for a production environment is still way more complicated than it needs to be. However, ultimately, configuring VistA is going to be harder than installing an office suite or an operating system, since it must be configured to the "business rules" (yes, I hate that term, as Greg does) of the practice, and the complexity of configuring VistA for a clinic will be broadly comparable to the decisions to be made when setting up a practice.		I wonder if there is a confusion between installing VistA and configuring VistA. Installing VistA is truly simple - with a SemiVivA Lite, for example, it is one command. Configuring VistA for a production environment is still way more complicated than it needs to be. However, ultimately, configuring VistA is going to be harder than installing an office suite or an operating system, since it must be configured to the "[[business rules~\|Business Rules]]" (yes, I hate that term, as Greg does) of the practice, and the complexity of configuring VistA for a clinic will be broadly comparable to the decisions to be made when setting up a practice.

	-- Bhaskar		-- Bhaskar

NeilArmstrong: Added glossary link to Record~

2012-03-21T19:18:37Z

Added glossary link to Record~

← Older revision		Revision as of 19:18, 21 March 2012
Line 33:		Line 33:
	So:		So:

	In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient record, as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as configuration users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].		In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient [[record~\|Record]], as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as configuration users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].

	But for years now [[clinical users~\|Clinical Users]] in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs. Get it [[Astronaut VistA\|here]].		But for years now [[clinical users~\|Clinical Users]] in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs. Get it [[Astronaut VistA\|here]].

NeilArmstrong: Added Glossary Link to Historical~

2012-03-03T00:57:45Z

Added Glossary Link to Historical~

← Older revision		Revision as of 00:57, 3 March 2012
Line 40:		Line 40:
	----		----
	----		----
	==='''BELOW IS HISTORICAL, OBSOLETE and NOT RECOMMENDED, use Astronaut VistA Installer Suite instead.'''===		==='''BELOW IS [[HISTORICAL~\|Historical]], OBSOLETE and NOT RECOMMENDED, use Astronaut VistA Installer Suite instead.'''===

	Ignacio Valdes Jul 11 2008, 4:28 pm		Ignacio Valdes Jul 11 2008, 4:28 pm

NeilArmstrong: Added glossary link to Clinical Users~

2012-02-28T08:07:48Z

Added glossary link to Clinical Users~

← Older revision		Revision as of 08:07, 28 February 2012
Line 35:		Line 35:
	In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient record, as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as configuration users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].		In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient record, as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as configuration users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].

	But for years now clinical users in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs. Get it [[Astronaut VistA\|here]].		But for years now [[clinical users~\|Clinical Users]] in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs. Get it [[Astronaut VistA\|here]].

Ssw0213: get it here

2010-05-15T21:57:59Z

get it here

← Older revision		Revision as of 21:57, 15 May 2010
Line 35:		Line 35:
	In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient record, as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as configuration users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].		In the beginning, all of VistA was text-based. Clinicians used terminals to enter the patient record, as did support staff to perform their tasks. Fileman and most other VistA applications were designed for text-based use. They can still be accessed via a terminal session from any computer (or even via dumb terminal) that is network-connected to the VistA server running on Linux. This method is menu based and the number of menus is quite large. For that very reason, as configuration users begin to memorize shortcuts to their desired tasks, they still find that text-based access is more efficient than clicking through graphical pages, and they prefer it. A map of those menus is [[VistA Menu Commands / VistA Menu Map\|here]].

	But for years now clinical users in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs.		But for years now clinical users in the VA have relied on the CPRS client, which is fully graphical, for entry of patient notes. Astronaut offers the option to configure the VistA server itself using VistA-Config. The same underlying applications in VistA can now appear as a visual layout of menus, options, and fields, the majority of which can be clicked and edited. Other GUI-based clients are also available for tasks such as entry of vital signs. Get it [[Astronaut VistA\|here]].