Episode39 - Revision history

DavidWhitten at 05:07, 13 November 2020

2020-11-13T05:07:05Z

← Older revision		Revision as of 05:07, 13 November 2020
Line 1:		Line 1:
			[[Ignacio_Valdes_Implementation_Log]]
			<pre>
	Ignacio Valdes		Ignacio Valdes
	~~View profile~~
	It begins. It is time to connect the WorldVistA system up to the lab and get reports. I would like to try using Mirth. Is there a definitive guide for this? Here we go! -- IV		It begins. It is time to connect the WorldVistA system up to the lab and get reports. I would like to try using Mirth. Is there a definitive guide for this? Here we go! -- IV
	More options Dec 21 2008, 11:39 am		More options Dec 21 2008, 11:39 am
Line 5,495:		Line 5,497:
	Fred Trotter		Fred Trotter
	http://www.fredtrotter.com		http://www.fredtrotter.com
			</pre>

NeilArmstrong: Added a Glossary link to Configuration~

2012-12-04T01:36:02Z

Added a Glossary link to Configuration~

← Older revision		Revision as of 01:36, 4 December 2012
Line 1,012:		Line 1,012:

	Basically you:		Basically you:
	1. Configure a shipping configuration to specify the tests and other		1. Configure a shipping [[configuration~\|Configuration]] to specify the tests and other
	characteristics related to shipping the specimen/test to the reference lab.		characteristics related to shipping the specimen/test to the reference lab.
	2. Build a manifest using a selected configuration to identify the		2. Build a manifest using a selected [[configuration~\|Configuration]] to identify the
	specimens to ship.		specimens to ship.
	3. Mark the manifest as shipped.		3. Mark the manifest as shipped.
Line 1,090:		Line 1,090:

	> Basically you:		> Basically you:
	> 1. Configure a shipping configuration to specify the tests and other		> 1. Configure a shipping [[configuration~\|Configuration]] to specify the tests and other
	> characteristics related to shipping the specimen/test to the reference lab.		> characteristics related to shipping the specimen/test to the reference lab.
	> 2. Build a manifest using a selected configuration to identify the		> 2. Build a manifest using a selected [[configuration~\|Configuration]] to identify the
	> specimens to ship.		> specimens to ship.
	> 3. Mark the manifest as shipped.		> 3. Mark the manifest as shipped.
Line 1,165:		Line 1,165:

	> Basically you:		> Basically you:
	> 1. Configure a shipping configuration to specify the tests and other		> 1. Configure a shipping [[configuration~\|Configuration]] to specify the tests and other
	> characteristics related to shipping the specimen/test to the reference lab.		> characteristics related to shipping the specimen/test to the reference lab.
	> 2. Build a manifest using a selected configuration to identify the		> 2. Build a manifest using a selected [[configuration~\|Configuration]] to identify the
	> specimens to ship.		> specimens to ship.
	> 3. Mark the manifest as shipped.		> 3. Mark the manifest as shipped.
Line 1,249:		Line 1,249:

	>> Basically you:		>> Basically you:
	>> 1. Configure a shipping configuration to specify the tests and other		>> 1. Configure a shipping [[configuration~\|Configuration]] to specify the tests and other
	>> characteristics related to shipping the specimen/test to the reference lab.		>> characteristics related to shipping the specimen/test to the reference lab.
	>> 2. Build a manifest using a selected configuration to identify the		>> 2. Build a manifest using a selected [[configuration~\|Configuration]] to identify the
	>> specimens to ship.		>> specimens to ship.
	>> 3. Mark the manifest as shipped.		>> 3. Mark the manifest as shipped.
Line 1,452:		Line 1,452:

	>>>> Basically you:		>>>> Basically you:
	>>>> 1. Configure a shipping configuration to specify the tests and other		>>>> 1. Configure a shipping [[configuration~\|Configuration]] to specify the tests and other
	>>>> characteristics related to shipping the specimen/test to the reference lab.		>>>> characteristics related to shipping the specimen/test to the reference lab.
	>>>> 2. Build a manifest using a selected configuration to identify the		>>>> 2. Build a manifest using a selected [[configuration~\|Configuration]] to identify the
	>>>> specimens to ship.		>>>> specimens to ship.
	>>>> 3. Mark the manifest as shipped.		>>>> 3. Mark the manifest as shipped.
Line 2,892:		Line 2,892:

	Before any interface to VistA Lab can be implemented the general VistA		Before any interface to VistA Lab can be implemented the general VistA
	Lab package would require configuration and implementation. If you just		Lab package would require [[configuration~\|Configuration]] and implementation. If you just
	want to store results then exploring the Lab POC interface may be an		want to store results then exploring the Lab POC interface may be an
	alternative. It's designed to accept results for which no VistA Lab		alternative. It's designed to accept results for which no VistA Lab
Line 2,990:		Line 2,990:

	> Before any interface to VistA Lab can be implemented the general VistA		> Before any interface to VistA Lab can be implemented the general VistA
	> Lab package would require configuration and implementation. If you just		> Lab package would require [[configuration~\|Configuration]] and implementation. If you just
	> want to store results then exploring the Lab POC interface may be an		> want to store results then exploring the Lab POC interface may be an
	> alternative. It's designed to accept results for which no VistA Lab		> alternative. It's designed to accept results for which no VistA Lab
Line 3,093:		Line 3,093:

	>> Before any interface to VistA Lab can be implemented the general VistA		>> Before any interface to VistA Lab can be implemented the general VistA
	>> Lab package would require configuration and implementation. If you just		>> Lab package would require [[configuration~\|Configuration]] and implementation. If you just
	>> want to store results then exploring the Lab POC interface may be an		>> want to store results then exploring the Lab POC interface may be an
	>> alternative. It's designed to accept results for which no VistA Lab		>> alternative. It's designed to accept results for which no VistA Lab
Line 3,138:		Line 3,138:
	On page 78 it shows that the servers are configured with HL7 2.3		On page 78 it shows that the servers are configured with HL7 2.3
	however, the local lab is speaking HL7 2.2 which is an option in the		however, the local lab is speaking HL7 2.2 which is an option in the
	VistA configuration. Will it mess something up for it to be HL7 2.2?		VistA [[configuration~\|Configuration]]. Will it mess something up for it to be HL7 2.2?
	Am I just gonna have to find out? -- IV		Am I just gonna have to find out? -- IV

Line 3,209:		Line 3,209:

	> >> Before any interface to VistA Lab can be implemented the general VistA		> >> Before any interface to VistA Lab can be implemented the general VistA
	> >> Lab package would require configuration and implementation. If you just		> >> Lab package would require [[configuration~\|Configuration]] and implementation. If you just
	> >> want to store results then exploring the Lab POC interface may be an		> >> want to store results then exploring the Lab POC interface may be an
	> >> alternative. It's designed to accept results for which no VistA Lab		> >> alternative. It's designed to accept results for which no VistA Lab
Line 3,265:		Line 3,265:
	> On page 78 it shows that the servers are configured with HL7 2.3		> On page 78 it shows that the servers are configured with HL7 2.3
	> however, the local lab is speaking HL7 2.2 which is an option in the		> however, the local lab is speaking HL7 2.2 which is an option in the
	> VistA configuration. Will it mess something up for it to be HL7 2.2?		> VistA [[configuration~\|Configuration]]. Will it mess something up for it to be HL7 2.2?
	> Am I just gonna have to find out? -- IV		> Am I just gonna have to find out? -- IV

Line 3,369:		Line 3,369:

	> >> Before any interface to VistA Lab can be implemented the general VistA		> >> Before any interface to VistA Lab can be implemented the general VistA
	> >> Lab package would require configuration and implementation. If you just		> >> Lab package would require [[Configuration~configuration]] and implementation. If you just
	> >> want to store results then exploring the Lab POC interface may be an		> >> want to store results then exploring the Lab POC interface may be an
	> >> alternative. It's designed to accept results for which no VistA Lab		> >> alternative. It's designed to accept results for which no VistA Lab
Line 3,542:		Line 3,542:

	>>>> Before any interface to VistA Lab can be implemented the general VistA		>>>> Before any interface to VistA Lab can be implemented the general VistA
	>>>> Lab package would require configuration and implementation. If you just		>>>> Lab package would require [[configuration~\|Configuration]] and implementation. If you just
	>>>> want to store results then exploring the Lab POC interface may be an		>>>> want to store results then exploring the Lab POC interface may be an
	>>>> alternative. It's designed to accept results for which no VistA Lab		>>>> alternative. It's designed to accept results for which no VistA Lab
Line 3,614:		Line 3,614:
	> On page 78 it shows that the servers are configured with HL7 2.3		> On page 78 it shows that the servers are configured with HL7 2.3
	> however, the local lab is speaking HL7 2.2 which is an option in the		> however, the local lab is speaking HL7 2.2 which is an option in the
	> VistA configuration. Will it mess something up for it to be HL7 2.2?		> VistA [[configuration~\|Configuration]]. Will it mess something up for it to be HL7 2.2?
	> Am I just gonna have to find out? -- IV		> Am I just gonna have to find out? -- IV

Line 3,809:		Line 3,809:

	> >>>> Before any interface to VistA Lab can be implemented the general VistA		> >>>> Before any interface to VistA Lab can be implemented the general VistA
	> >>>> Lab package would require configuration and implementation. If you just		> >>>> Lab package would require [[configuration~\|Configuration]] and implementation. If you just
	> >>>> want to store results then exploring the Lab POC interface may be an		> >>>> want to store results then exploring the Lab POC interface may be an
	> >>>> alternative. It's designed to accept results for which no VistA Lab		> >>>> alternative. It's designed to accept results for which no VistA Lab
Line 5,319:		Line 5,319:
	The interface that most closely matches the situation you describe is		The interface that most closely matches the situation you describe is
	the Lab POC interface. However this would still require extensive		the Lab POC interface. However this would still require extensive
	configuration and coordination with the external lab. The user guide and		[[configuration~\|Configuration]] and coordination with the external lab. The user guide and
	HL7 interface specification is available on the VA VistA VDL.		HL7 interface specification is available on the VA VistA VDL.

NeilArmstrong: Added a glossary link to Business Rules~

2012-08-04T09:52:10Z

Added a glossary link to Business Rules~

NeilArmstrong: Added a glossary link to Action~

2012-07-29T17:32:12Z

Added a glossary link to Action~

← Older revision		Revision as of 17:32, 29 July 2012
Line 4,127:		Line 4,127:

	_______________________________________________________________________________		_______________________________________________________________________________
	Time must be at least 2 minutes in the future and type run, action,		Time must be at least 2 minutes in the future and type run, [[action~\|Action]],
	print		print

Line 4,302:		Line 4,302:

	> _______________________________________________________________________________		> _______________________________________________________________________________
	> Time must be at least 2 minutes in the future and type run, action,		> Time must be at least 2 minutes in the future and type run, [[action~\|Action]],
	> print		> print

Line 4,479:		Line 4,479:

	> > _________________________________________________________________________		> > _________________________________________________________________________
	> >______ Time must be at least 2 minutes in the future and type run, action,		> >______ Time must be at least 2 minutes in the future and type run, [[action~\|Action]],
	> > print		> > print

Line 4,652:		Line 4,652:

	> > > _________________________________________________________________________		> > > _________________________________________________________________________
	> > >______ Time must be at least 2 minutes in the future and type run, action,		> > >______ Time must be at least 2 minutes in the future and type run, [[action~\|Action]],
	> > > print		> > > print

NeilArmstrong: Added a glossary link to Record~

2012-03-24T15:18:22Z

Added a glossary link to Record~

← Older revision		Revision as of 15:18, 24 March 2012
Line 3,665:		Line 3,665:
	ANOTHER ONE: <ENTER>		ANOTHER ONE: <ENTER>
	STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)		STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
	Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No record number		Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~\|Record]] number
	(IEN),		(IEN),
	no Computed Fields		no Computed Fields
Line 3,884:		Line 3,884:

	Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and		Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
	Record Number		[[Record~\|Record]] Number
	(IEN)		(IEN)
	Heading (S/C): OPTION List//		Heading (S/C): OPTION List//
Line 3,958:		Line 3,958:
	> ANOTHER ONE: <ENTER>		> ANOTHER ONE: <ENTER>
	> STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)		> STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
	> Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No record number		> Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~\|Record]] number
	> (IEN),		> (IEN),
	> no Computed Fields		> no Computed Fields
Line 4,162:		Line 4,162:

	> Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and		> Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
	> Record Number		> [[Record~\|Record]] Number
	> (IEN)		> (IEN)
	> Heading (S/C): OPTION List//		> Heading (S/C): OPTION List//
Line 4,234:		Line 4,234:
	> > ANOTHER ONE: <ENTER>		> > ANOTHER ONE: <ENTER>
	> > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)		> > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
	> > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No record number		> > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~\|Record]] number
	> > (IEN),		> > (IEN),
	> > no Computed Fields		> > no Computed Fields
Line 4,335:		Line 4,335:

	> > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and		> > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
	> > Record Number		> > [[Record~\|Record]] Number
	> > (IEN)		> > (IEN)
	> > Heading (S/C): OPTION List//		> > Heading (S/C): OPTION List//
Line 4,407:		Line 4,407:
	> > > ANOTHER ONE: <ENTER>		> > > ANOTHER ONE: <ENTER>
	> > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)		> > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
	> > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No record number		> > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~\|Record]] number
	> > > (IEN),		> > > (IEN),
	> > > no Computed Fields		> > > no Computed Fields
Line 4,512:		Line 4,512:

	> > > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and		> > > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
	> > > Record Number		> > > [[Record~\|Record]] Number
	> > > (IEN)		> > > (IEN)
	> > > Heading (S/C): OPTION List//		> > > Heading (S/C): OPTION List//
Line 4,586:		Line 4,586:
	> > > > ANOTHER ONE: <ENTER>		> > > > ANOTHER ONE: <ENTER>
	> > > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)		> > > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
	> > > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No record number		> > > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~\|Record]] number
	> > > > (IEN),		> > > > (IEN),
	> > > > no Computed Fields		> > > > no Computed Fields
Line 4,685:		Line 4,685:

	> > > > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and		> > > > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
	> > > > Record Number		> > > > [[Record~\|Record]] Number
	> > > > (IEN)		> > > > (IEN)
	> > > > Heading (S/C): OPTION List//		> > > > Heading (S/C): OPTION List//
Line 4,759:		Line 4,759:
	> > > > > ANOTHER ONE: <ENTER>		> > > > > ANOTHER ONE: <ENTER>
	> > > > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)		> > > > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
	> > > > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No record number		> > > > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~\|Record]] number
	> > > > > (IEN),		> > > > > (IEN),
	> > > > > no Computed Fields		> > > > > no Computed Fields
Line 5,121:		Line 5,121:
	current paper ordering system. I don't have the quick orders setup		current paper ordering system. I don't have the quick orders setup
	either. Is there a simple way of receiving those lab results and		either. Is there a simple way of receiving those lab results and
	routing them to the Lab tab record using only patient demographics/		routing them to the Lab tab [[record~\|Record]] using only patient demographics/
	Health record number? It does not need to be fancy at this point. Any		Health [[record~\|Record]] number? It does not need to be fancy at this point. Any
	electronic method is likely to be much better than the current paper		electronic method is likely to be much better than the current paper
	one.		one.
Line 5,210:		Line 5,210:
	> current paper ordering system. I don't have the quick orders setup		> current paper ordering system. I don't have the quick orders setup
	> either. Is there a simple way of receiving those lab results and		> either. Is there a simple way of receiving those lab results and
	> routing them to the Lab tab record using only patient demographics/		> routing them to the Lab tab [[record~\|Record]] using only patient demographics/
	> Health record number? It does not need to be fancy at this point. Any		> Health [[record~\|Record]] number? It does not need to be fancy at this point. Any
	> electronic method is likely to be much better than the current paper		> electronic method is likely to be much better than the current paper
	> one.		> one.
Line 5,377:		Line 5,377:
	>>> current paper ordering system. I don't have the quick orders setup		>>> current paper ordering system. I don't have the quick orders setup
	>>> either. Is there a simple way of receiving those lab results and		>>> either. Is there a simple way of receiving those lab results and
	>>> routing them to the Lab tab record using only patient demographics/		>>> routing them to the Lab tab [[record~\|Record]] using only patient demographics/
	>>> Health record number? It does not need to be fancy at this point. Any		>>> Health [[record~\|Record]] number? It does not need to be fancy at this point. Any
	>>> electronic method is likely to be much better than the current paper		>>> electronic method is likely to be much better than the current paper
	>>> one.		>>> one.

NeilArmstrong: Added Glossary Link to Prompt~

2012-03-05T12:25:46Z

Added Glossary Link to Prompt~

NeilArmstrong: Added glossary link to Application~

2012-02-22T16:29:15Z

Added glossary link to Application~

Show changes

Ivaldes1 at 03:36, 22 September 2009

2009-09-22T03:36:00Z

Show changes

← Older revision		Revision as of 09:52, 4 August 2012
Line 3,051:		Line 3,051:
	> with the paper ordering continuing until we can get it all paperless.		> with the paper ordering continuing until we can get it all paperless.

	Paper ordering and electronic ordering will change the business rules		Paper ordering and electronic ordering will change the [[business rules~\|Business Rules]]
	and determine the type of interface you use.		and determine the type of interface you use.
	If you go with electronic ordering then you may need to use LEDI minus		If you go with electronic ordering then you may need to use LEDI minus
Line 3,169:		Line 3,169:
	> > with the paper ordering continuing until we can get it all paperless.		> > with the paper ordering continuing until we can get it all paperless.

	> Paper ordering and electronic ordering will change the business rules		> Paper ordering and electronic ordering will change the [[business rules~\|Business Rules]]
	> and determine the type of interface you use.		> and determine the type of interface you use.
	> If you go with electronic ordering then you may need to use LEDI minus		> If you go with electronic ordering then you may need to use LEDI minus
Line 3,329:		Line 3,329:
	> > with the paper ordering continuing until we can get it all paperless.		> > with the paper ordering continuing until we can get it all paperless.

	> Paper ordering and electronic ordering will change the business rules		> Paper ordering and electronic ordering will change the [[business rules~\|Business Rules]]
	> and determine the type of interface you use.		> and determine the type of interface you use.
	> If you go with electronic ordering then you may need to use LEDI minus		> If you go with electronic ordering then you may need to use LEDI minus
Line 3,501:		Line 3,501:
	>>> with the paper ordering continuing until we can get it all paperless.		>>> with the paper ordering continuing until we can get it all paperless.

	>> Paper ordering and electronic ordering will change the business rules		>> Paper ordering and electronic ordering will change the [[business rules~\|Business Rules]]
	>> and determine the type of interface you use.		>> and determine the type of interface you use.
	>> If you go with electronic ordering then you may need to use LEDI minus		>> If you go with electronic ordering then you may need to use LEDI minus
Line 3,768:		Line 3,768:
	> >>> with the paper ordering continuing until we can get it all paperless.		> >>> with the paper ordering continuing until we can get it all paperless.

	> >> Paper ordering and electronic ordering will change the business rules		> >> Paper ordering and electronic ordering will change the [[business rules~\|Business Rules]]
	> >> and determine the type of interface you use.		> >> and determine the type of interface you use.
	> >> If you go with electronic ordering then you may need to use LEDI minus		> >> If you go with electronic ordering then you may need to use LEDI minus
Line 4,061:		Line 4,061:
	>>>>> with the paper ordering continuing until we can get it all paperless.		>>>>> with the paper ordering continuing until we can get it all paperless.

	>>>> Paper ordering and electronic ordering will change the business rules		>>>> Paper ordering and electronic ordering will change the [[business rules~\|Business Rules]]
	>>>> and determine the type of interface you use.		>>>> and determine the type of interface you use.
	>>>> If you go with electronic ordering then you may need to use LEDI minus		>>>> If you go with electronic ordering then you may need to use LEDI minus

← Older revision		Revision as of 12:25, 5 March 2012
Line 2,060:		Line 2,060:
	http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...		http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
	reproduced below but when I try to load DMIS ID, it throws me out to		reproduced below but when I try to load DMIS ID, it throws me out to
	the gtm prompt as follows:		the gtm [[prompt~\|Prompt]] as follows:

	Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's		Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Line 2,145:		Line 2,145:
	> http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...		> http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
	> reproduced below but when I try to load DMIS ID, it throws me out to		> reproduced below but when I try to load DMIS ID, it throws me out to
	> the gtm prompt as follows:		> the gtm [[prompt~\|Prompt]] as follows:

	> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's		> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Line 2,240:		Line 2,240:
	> >http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...		> >http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
	> > reproduced below but when I try to load DMIS ID, it throws me out to		> > reproduced below but when I try to load DMIS ID, it throws me out to
	> > the gtm prompt as follows:		> > the gtm [[prompt~\|Prompt]] as follows:

	> > Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's		> > Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Line 2,350:		Line 2,350:
	> >http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...		> >http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
	> > reproduced below but when I try to load DMIS ID, it throws me out to		> > reproduced below but when I try to load DMIS ID, it throws me out to
	> > the gtm prompt as follows:		> > the gtm [[prompt~\|Prompt]] as follows:

	> > Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's		> > Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Line 2,491:		Line 2,491:
	>>> http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...		>>> http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
	>>> reproduced below but when I try to load DMIS ID, it throws me out to		>>> reproduced below but when I try to load DMIS ID, it throws me out to
	>>> the gtm prompt as follows:		>>> the gtm [[prompt~\|Prompt]] as follows:

	>>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's		>>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Line 2,641:		Line 2,641:
	> >>> http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED..		> >>> http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED..
	> >>>. reproduced below but when I try to load DMIS ID, it throws me out to		> >>>. reproduced below but when I try to load DMIS ID, it throws me out to
	> >>> the gtm prompt as follows:		> >>> the gtm [[prompt~\|Prompt]] as follows:

	> >>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's		> >>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Line 2,806:		Line 2,806:
	> >>>http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...		> >>>http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
	> >>> reproduced below but when I try to load DMIS ID, it throws me out to		> >>> reproduced below but when I try to load DMIS ID, it throws me out to
	> >>> the gtm prompt as follows:		> >>> the gtm [[prompt~\|Prompt]] as follows:

	> >>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's		> >>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Line 3,298:		Line 3,298:
	Subject: Re: Intracare Implementation Log Episode 39: Patient lab reports connection.		Subject: Re: Intracare Implementation Log Episode 39: Patient lab reports connection.
	Reply to author \| Forward \| Print \| Individual message \| Show original \| Report this message \| Find messages by this author		Reply to author \| Forward \| Print \| Individual message \| Show original \| Report this message \| Find messages by this author
	Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm prompt.		Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~\|Prompt]].
	ZSTATUS shows nothing "". -- IV		ZSTATUS shows nothing "". -- IV

Line 3,472:		Line 3,472:
	- Show quoted text -		- Show quoted text -
	I, Valdes wrote:		I, Valdes wrote:
	> Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm prompt.		> Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~\|Prompt]].
	> ZSTATUS shows nothing "". -- IV		> ZSTATUS shows nothing "". -- IV

Line 3,657:		Line 3,657:
	Reply to author \| Forward \| Print \| Individual message \| Show original \| Report this message \| Find messages by this author		Reply to author \| Forward \| Print \| Individual message \| Show original \| Report this message \| Find messages by this author
	Why does the example at the bottom of page 84 look very different than		Why does the example at the bottom of page 84 look very different than
	what I get, ie not blowing out to the gtm prompt (or equivalent)? Are		what I get, ie not blowing out to the gtm [[prompt~\|Prompt]] (or equivalent)? Are
	they starting it from a place I am unaware of? Guess it is time to		they starting it from a place I am unaware of? Guess it is time to
	learn how to start something in taskman...		learn how to start something in taskman...
Line 3,739:		Line 3,739:

	> I, Valdes wrote:		> I, Valdes wrote:
	> > Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm prompt.		> > Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~\|Prompt]].
	> > ZSTATUS shows nothing "". -- IV		> > ZSTATUS shows nothing "". -- IV

Line 3,950:		Line 3,950:
	I, Valdes wrote:		I, Valdes wrote:
	> Why does the example at the bottom of page 84 look very different than		> Why does the example at the bottom of page 84 look very different than
	> what I get, ie not blowing out to the gtm prompt (or equivalent)? Are		> what I get, ie not blowing out to the gtm [[prompt~\|Prompt]] (or equivalent)? Are
	> they starting it from a place I am unaware of? Guess it is time to		> they starting it from a place I am unaware of? Guess it is time to
	> learn how to start something in taskman...		> learn how to start something in taskman...
Line 4,032:		Line 4,032:
	>> I, Valdes wrote:		>> I, Valdes wrote:

	>>> Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm prompt.		>>> Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~\|Prompt]].
	>>> ZSTATUS shows nothing "". -- IV		>>> ZSTATUS shows nothing "". -- IV

Line 4,226:		Line 4,226:
	> I, Valdes wrote:		> I, Valdes wrote:
	> > Why does the example at the bottom of page 84 look very different than		> > Why does the example at the bottom of page 84 look very different than
	> > what I get, ie not blowing out to the gtm prompt (or equivalent)? Are		> > what I get, ie not blowing out to the gtm [[prompt~\|Prompt]] (or equivalent)? Are
	> > they starting it from a place I am unaware of? Guess it is time to		> > they starting it from a place I am unaware of? Guess it is time to
	> > learn how to start something in taskman...		> > learn how to start something in taskman...
Line 4,399:		Line 4,399:
	> > I, Valdes wrote:		> > I, Valdes wrote:
	> > > Why does the example at the bottom of page 84 look very different than		> > > Why does the example at the bottom of page 84 look very different than
	> > > what I get, ie not blowing out to the gtm prompt (or equivalent)? Are		> > > what I get, ie not blowing out to the gtm [[prompt~\|Prompt]] (or equivalent)? Are
	> > > they starting it from a place I am unaware of? Guess it is time to		> > > they starting it from a place I am unaware of? Guess it is time to
	> > > learn how to start something in taskman...		> > > learn how to start something in taskman...
Line 4,578:		Line 4,578:
	> > > I, Valdes wrote:		> > > I, Valdes wrote:
	> > > > Why does the example at the bottom of page 84 look very different		> > > > Why does the example at the bottom of page 84 look very different
	> > > > than what I get, ie not blowing out to the gtm prompt (or		> > > > than what I get, ie not blowing out to the gtm [[prompt~\|Prompt]] (or
	> > > > equivalent)? Are they starting it from a place I am unaware of?		> > > > equivalent)? Are they starting it from a place I am unaware of?
	> > > > Guess it is time to learn how to start something in taskman...		> > > > Guess it is time to learn how to start something in taskman...
Line 4,751:		Line 4,751:
	> > > > I, Valdes wrote:		> > > > I, Valdes wrote:
	> > > > > Why does the example at the bottom of page 84 look very different		> > > > > Why does the example at the bottom of page 84 look very different
	> > > > > than what I get, ie not blowing out to the gtm prompt (or		> > > > > than what I get, ie not blowing out to the gtm [[prompt~\|Prompt]] (or
	> > > > > equivalent)? Are they starting it from a place I am unaware of?		> > > > > equivalent)? Are they starting it from a place I am unaware of?
	> > > > > Guess it is time to learn how to start something in taskman...		> > > > > Guess it is time to learn how to start something in taskman...