Difference between revisions of "Episode39"
From VistApedia
(Added a glossary link to Business Rules~) |
DavidWhitten (talk | contribs) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Ignacio_Valdes_Implementation_Log]] | ||
| + | <pre> | ||
Ignacio Valdes | Ignacio Valdes | ||
| − | + | ||
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 1,012: | Line 1,014: | ||
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,092: | ||
> 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,167: | ||
> 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,251: | ||
>> 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,454: | ||
>>>> 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,894: | ||
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,992: | ||
> 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,095: | ||
>> 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,140: | ||
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,211: | ||
> >> 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,267: | ||
> 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,371: | ||
> >> 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,544: | ||
>>>> 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,616: | ||
> 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,811: | ||
> >>>> 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,321: | ||
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. | ||
| Line 5,495: | Line 5,497: | ||
Fred Trotter | Fred Trotter | ||
http://www.fredtrotter.com | http://www.fredtrotter.com | ||
| + | </pre> | ||
Latest revision as of 05:07, 13 November 2020
Ignacio_Valdes_Implementation_Log
Ignacio Valdes
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
From: "Ignacio Valdes" <ival...@hal-pc.org>
Date: Sun, 21 Dec 2008 10:39:50 -0600
Local: Sun, Dec 21 2008 11:39 am
Subject: 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
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
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sun, 21 Dec 2008 18:42:34 -0800 (PST)
Local: Sun, Dec 21 2008 9:42 pm
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
How do I know if LA*5.2*67 and LR*5.2*290 are installed in WVEHR? In
EVE -> Prog -> KIDS -> Utilities --> Display and I put in LA for the
package, 3 items come up and they all seem to have the 5.2 versions
but the *67 and *290 part I am not sure of and do not see it
particularly. Does WVEHR have these installed by default? These are
possibly necessary to have installed per this document:
http://www.va.gov/vdl/documents/Clinical/Lab-Point_of_Care/lab_52_lr2...
"IRM Staff
IRM staff is required to install the VistA Laboratory Point of Care
(POC) Interface Patches
LA*5.2*67 and LR*5.2*290 software on the VistA systems.
IRM staff must assist with the POC post implementation requirements
setup, if needed. The POC post implementation requirements setup must
to be coordinated with the LIM staff and Laboratory’s ADPAC or ATC."
-- IV
On Dec 21, 10:39 am, "Ignacio Valdes" <ival...@hal-pc.org> wrote:
- Hide quoted text -
- Show quoted text -
> 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
Nancy Anthracite
Subject: Re: [Hardhats] 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
I am not sure how you are only getting 3 items as there are many more. Both
patches are installed.
PACKAGE: AUTOMATED LAB INSTRUMENTS Dec 21, 2008 9:49 pm PAGE 1
PATCH # INSTALLED INSTALLED BY
-------------------------------------------------------------------------------
VERSION: 5.2 JUN 05, 1996
22 SEQ #14 JUL 15, 1996 WVEHR,PATCH INSTALLER
25 SEQ #15 DEC 24, 1996 WVEHR,PATCH INSTALLER
23 SEQ #19 MAY 28, 1997 WVEHR,PATCH INSTALLER
36 SEQ #24 OCT 16, 1997 WVEHR,PATCH INSTALLER
35 SEQ #25 OCT 21, 1997 WVEHR,PATCH INSTALLER
37 SEQ #26 NOV 18, 1997 WVEHR,PATCH INSTALLER
40 SEQ #27 FEB 20, 1998 WVEHR,PATCH INSTALLER
27 MAR 18, 1998 WVEHR,PATCH INSTALLER
42 APR 17, 1998 WVEHR,PATCH INSTALLER
44 SEQ #30 OCT 16, 1998 WVEHR,PATCH INSTALLER
45 SEQ #31 DEC 14, 1998 WVEHR,PATCH INSTALLER
48 SEQ #32 MAY 10, 1999 WVEHR,PATCH INSTALLER
47 SEQ #33 JUL 19, 1999 WVEHR,PATCH INSTALLER
51 SEQ #34 APR 05, 2000 WVEHR,PATCH INSTALLER
50 SEQ #35 APR 05, 2000 WVEHR,PATCH INSTALLER
53 SEQ #36 MAY 25, 2000 WVEHR,PATCH INSTALLER
55 SEQ #37 JUL 11, 2000 WVEHR,PATCH INSTALLER
56 SEQ #38 AUG 16, 2000 WVEHR,PATCH INSTALLER
52 SEQ #39 AUG 16, 2000 WVEHR,PATCH INSTALLER
58 JAN 22, 2001 WVEHR,PATCH INSTALLER
57 SEQ #41 APR 23, 2001 WVEHR,PATCH INSTALLER
59 SEQ #42 JUN 25, 2001 WVEHR,PATCH INSTALLER
PACKAGE: LAB SERVICE Dec 21, 2008 9:49 pm PAGE 1
PATCH # INSTALLED INSTALLED BY
-------------------------------------------------------------------------------
VERSION: 5.2 JUN 10, 1996
105 SEQ #78 JUN 11, 1996 WVEHR,PATCH INSTALLER
100 SEQ #91 JUN 25, 1996 WVEHR,PATCH INSTALLER
119 SEQ #94 JUL 15, 1996 WVEHR,PATCH INSTALLER
125 SEQ #96 AUG 20, 1996 WVEHR,PATCH INSTALLER
127 SEQ #97 SEP 20, 1996 WVEHR,PATCH INSTALLER
136 SEQ #99 OCT 11, 1996 WVEHR,PATCH INSTALLER
59 SEQ #100 OCT 17, 1996 WVEHR,PATCH INSTALLER
101 SEQ #101 NOV 07, 1996 WVEHR,PATCH INSTALLER
126 SEQ #102 NOV 07, 1996 WVEHR,PATCH INSTALLER
138 SEQ #103 NOV 08, 1996 WVEHR,PATCH INSTALLER
134 SEQ #104 NOV 15, 1996 WVEHR,PATCH INSTALLER
137 SEQ #105 NOV 20, 1996 WVEHR,PATCH INSTALLER
141 SEQ #106 NOV 23, 1996 WVEHR,PATCH INSTALLER
128 NOV 29, 1996 WVEHR,PATCH INSTALLER
139 SEQ #108 DEC 10, 1996 WVEHR,PATCH INSTALLER
107 SEQ #109 DEC 24, 1996 WVEHR,PATCH INSTALLER
152 SEQ #110 JAN 22, 1997 WVEHR,PATCH INSTALLER
132 SEQ #111 MAR 21, 1997 WVEHR,PATCH INSTALLER
158 SEQ #112 MAR 26, 1997 WVEHR,PATCH INSTALLER
150 SEQ #113 APR 01, 1997 WVEHR,PATCH INSTALLER
160 SEQ #114 APR 21, 1997 WVEHR,PATCH INSTALLER
165 SEQ #115 MAY 28, 1997 WVEHR,PATCH INSTALLER
140 SEQ #118 JUL 09, 1997 WVEHR,PATCH INSTALLER
143 SEQ #119 JUL 17, 1997 WVEHR,PATCH INSTALLER
164 SEQ #120 JUL 28, 1997 WVEHR,PATCH INSTALLER
171 SEQ #121 JUL 28, 1997 WVEHR,PATCH INSTALLER
172 SEQ #122 AUG 08, 1997 WVEHR,PATCH INSTALLER
163 AUG 19, 1997 WVEHR,PATCH INSTALLER
177 SEQ #124 AUG 27, 1997 WVEHR,PATCH INSTALLER
121 AUG 28, 1997 WVEHR,PATCH INSTALLER
156 SEQ #126 NOV 18, 1997 WVEHR,PATCH INSTALLER
169 SEQ #127 NOV 27, 1997 WVEHR,PATCH INSTALLER
90 SEQ #128 NOV 27, 1997 WVEHR,PATCH INSTALLER
174 SEQ #131 NOV 27, 1997 WVEHR,PATCH INSTALLER
162 SEQ #132 NOV 27, 1997 WVEHR,PATCH INSTALLER
186 SEQ #133 DEC 22, 1997 WVEHR,PATCH INSTALLER
182 SEQ #134 DEC 31, 1997 WVEHR,PATCH INSTALLER
173 SEQ #135 FEB 05, 1998 WVEHR,PATCH INSTALLER
198 SEQ #137 MAR 18, 1998 WVEHR,PATCH INSTALLER
153 MAR 18, 1998 WVEHR,PATCH INSTALLER
203 APR 17, 1998 WVEHR,PATCH INSTALLER
201 APR 17, 1998 WVEHR,PATCH INSTALLER
155 SEQ #141 APR 17, 1998 WVEHR,PATCH INSTALLER
191 SEQ #142 APR 28, 1998 WVEHR,PATCH INSTALLER
208 SEQ #143 APR 28, 1998 WVEHR,PATCH INSTALLER
189 SEQ #144 APR 28, 1998 WVEHR,PATCH INSTALLER
205 SEQ #145 MAY 27, 1998 WVEHR,PATCH INSTALLER
210 JUL 12, 1998 WVEHR,PATCH INSTALLER
193 SEQ #147 JUL 25, 1998 WVEHR,PATCH INSTALLER
200 SEQ #148 JUL 25, 1998 WVEHR,PATCH INSTALLER
192 SEQ #149 JUL 25, 1998 WVEHR,PATCH INSTALLER
195 SEQ #150 AUG 31, 1998 WVEHR,PATCH INSTALLER
188 SEQ #151 AUG 31, 1998 WVEHR,PATCH INSTALLER
175 SEQ #152 AUG 31, 1998 WVEHR,PATCH INSTALLER
161 SEQ #153 SEP 23, 1998 WVEHR,PATCH INSTALLER
217 SEQ #154 SEP 23, 1998 WVEHR,PATCH INSTALLER
202 SEQ #155 OCT 16, 1998 WVEHR,PATCH INSTALLER
185 SEQ #156 OCT 16, 1998 WVEHR,PATCH INSTALLER
187 SEQ #157 OCT 16, 1998 WVEHR,PATCH INSTALLER
190 SEQ #158 OCT 16, 1998 WVEHR,PATCH INSTALLER
176 SEQ #159 OCT 16, 1998 WVEHR,PATCH INSTALLER
214 SEQ #160 NOV 04, 1998 WVEHR,PATCH INSTALLER
219 SEQ #161 NOV 05, 1998 WVEHR,PATCH INSTALLER
211 SEQ #162 NOV 19, 1998 WVEHR,PATCH INSTALLER
220 SEQ #163 DEC 29, 1998 WVEHR,PATCH INSTALLER
213 SEQ #164 FEB 01, 1999 WVEHR,PATCH INSTALLER
227 SEQ #165 FEB 01, 1999 WVEHR,PATCH INSTALLER
225 SEQ #166 FEB 10, 1999 WVEHR,PATCH INSTALLER
224 SEQ #167 FEB 23, 1999 WVEHR,PATCH INSTALLER
226 SEQ #168 FEB 23, 1999 WVEHR,PATCH INSTALLER
223 SEQ #169 MAR 03, 1999 WVEHR,PATCH INSTALLER
166 APR 16, 1999 WVEHR,PATCH INSTALLER
228 SEQ #171 APR 20, 1999 WVEHR,PATCH INSTALLER
215 APR 27, 1999 WVEHR,PATCH INSTALLER
239 SEQ #173 MAY 10, 1999 WVEHR,PATCH INSTALLER
231 SEQ #175 JUN 02, 1999 WVEHR,PATCH INSTALLER
234 SEQ #176 JUL 19, 1999 WVEHR,PATCH INSTALLER
235 SEQ #177 JUL 19, 1999 WVEHR,PATCH INSTALLER
221 SEQ #178 JUL 19, 1999 WVEHR,PATCH INSTALLER
212 SEQ #179 JUL 19, 1999 WVEHR,PATCH INSTALLER
238 SEQ #180 AUG 03, 1999 WVEHR,PATCH INSTALLER
230 SEQ #181 OCT 19, 1999 WVEHR,PATCH INSTALLER
229 SEQ #182 DEC 10, 1999 WVEHR,PATCH INSTALLER
244 SEQ #183 DEC 10, 1999 WVEHR,PATCH INSTALLER
241 SEQ #184 DEC 10, 1999 WVEHR,PATCH INSTALLER
247 DEC 10, 1999 WVEHR,PATCH INSTALLER
250 SEQ #186 DEC 20, 1999 WVEHR,PATCH INSTALLER
251 SEQ #187 JAN 03, 2000 WVEHR,PATCH INSTALLER
242 SEQ #188 JAN 03, 2000 WVEHR,PATCH INSTALLER
252 SEQ #189 JAN 25, 2000 WVEHR,PATCH INSTALLER
253 SEQ #190 JAN 25, 2000 WVEHR,PATCH INSTALLER
245 SEQ #191 JAN 25, 2000 WVEHR,PATCH INSTALLER
246 SEQ #192 JAN 25, 2000 WVEHR,PATCH INSTALLER
240 SEQ #193 FEB 29, 2000 WVEHR,PATCH INSTALLER
206 SEQ #194 MAY 01, 2000 WVEHR,PATCH INSTALLER
254 SEQ #195 MAY 25, 2000 WVEHR,PATCH INSTALLER
243 SEQ #196 JUN 26, 2000 WVEHR,PATCH INSTALLER
263 SEQ #197 JUN 26, 2000 WVEHR,PATCH INSTALLER
218 SEQ #198 JUN 26, 2000 WVEHR,PATCH INSTALLER
260 SEP 05, 2000 WVEHR,PATCH INSTALLER
256 SEQ #200 NOV 06, 2000 WVEHR,PATCH INSTALLER
264 SEQ #201 NOV 27, 2000 WVEHR,PATCH INSTALLER
265 SEQ #202 JAN 03, 2001 WVEHR,PATCH INSTALLER
265 JAN 03, 2001 WVEHR,PATCH INSTALLER
261 SEQ #203 JAN 03, 2001 WVEHR,PATCH INSTALLER
266 JAN 22, 2001
...
read more »
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 21 2008, 9:51 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sun, 21 Dec 2008 18:51:14 -0800 (PST)
Local: Sun, Dec 21 2008 9:51 pm
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
Here is how you query Fileman for if a particular patch like the above
is installed:
GTM>S DUZ=60 D P^DI
VA FileMan 22.0
Select OPTION: ?
Answer with OPTION NUMBER, or NAME
Choose from:
1 ENTER OR EDIT FILE ENTRIES
2 PRINT FILE ENTRIES
3 SEARCH FILE ENTRIES
4 MODIFY FILE ATTRIBUTES
5 INQUIRE TO FILE ENTRIES
6 UTILITY FUNCTIONS
7 OTHER OPTIONS
8 DATA DICTIONARY UTILITIES
9 TRANSFER ENTRIES
Select OPTION: 5 INQUIRE TO FILE ENTRIES
OUTPUT FROM WHAT FILE: KERNEL SYSTEM PARAMETERS// INSTALL
(7163 entries)
Select INSTALL NAME: LA*5.2*67 Install Completed Install
Completed 3/
20/06@15:42:30
=> LA*5.2*67/LR*5.2*290 ;Created on May 26, 2005@16:43:07
ANOTHER ONE: LR*5.2*290 Install Completed Install Completed
3/20/06@1
5:42:32
=> LA*5.2*67/LR*5.2*290 ;Created on May 26, 2005@16:43:07
ANOTHER ONE:
On Dec 21, 8:42 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
- Hide quoted text -
- Show quoted text -
> How do I know if LA*5.2*67 and LR*5.2*290 are installed in WVEHR? In
> EVE -> Prog -> KIDS -> Utilities --> Display and I put in LA for the
> package, 3 items come up and they all seem to have the 5.2 versions
> but the *67 and *290 part I am not sure of and do not see it
> particularly. Does WVEHR have these installed by default? These are
> possibly necessary to have installed per this document:
> http://www.va.gov/vdl/documents/Clinical/Lab-Point_of_Care/lab_52_lr2...
> "IRM Staff
> IRM staff is required to install the VistA Laboratory Point of Care
> (POC) Interface Patches
> LA*5.2*67 and LR*5.2*290 software [[application~|Application]] on the VistA systems.
> IRM staff must assist with the POC post implementation requirements
> setup, if needed. The POC post implementation requirements setup must
> to be coordinated with the LIM staff and Laboratory’s ADPAC or ATC."
> -- IV
> On Dec 21, 10:39 am, "Ignacio Valdes" <ival...@hal-pc.org> wrote:
> > 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
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Dec 22 2008, 1:05 am
From: John McCormack <johnm...@ix.netcom.com>
Date: Mon, 22 Dec 2008 00:05:38 -0600
Local: Mon, Dec 22 2008 1:05 am
Subject: Re: [Hardhats] 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
The KIDS menu option uses FileMan to query the same file. Just the
output is formatted better by the option.
If you used the Display Patches for a Package option then what you are
seeing is the query to select the package. Once you select the package
then it will display the patches associated with that package. To check
for a specific patch it sometimes is easier to use the Install File
Print option.
Patches that are namespaced LR belong to the LAB SERVICE package.
Patches that are namespaced LA belong to AUTOMATED LAB INSTRUMENTS
package. The VistA Laboratory has two name spaces assigned LA and LR.
Select Kernel Installation & Distribution System Option: UTilities
Build File Print
Install File Print
Convert Loaded Package for Redistribution
Display Patches for a Package
Purge Build or Install Files
Rollup Patches into a Build
Update Routine File
Verify a Build
Verify Package Integrity
Select Utilities Option: INSTAll File Print
Select INSTALL NAME: LA*5.2*67 Install Completed Install
Completed 3/20/06@15:42:30
=> LA*5.2*67/LR*5.2*290 ;Created on May 26, 2005@16:43:07
DEVICE: HOME// ^
Build File Print
Install File Print
Convert Loaded Package for Redistribution
Display Patches for a Package
Purge Build or Install Files
Rollup Patches into a Build
Update Routine File
Verify a Build
Verify Package Integrity
Select Utilities Option: Install File Print
Select INSTALL NAME: LR*5.2*290 Install Completed Install
Completed 3/20/06@15:42:32
=> LA*5.2*67/LR*5.2*290 ;Created on May 26, 2005@16:43:07
DEVICE: HOME// ^
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> Here is how you query Fileman for if a particular patch like the above
> is installed:
> GTM>S DUZ=60 D P^DI
> VA FileMan 22.0
> Select OPTION: ?
> Answer with OPTION NUMBER, or NAME
> Choose from:
> 1 ENTER OR EDIT FILE ENTRIES
> 2 PRINT FILE ENTRIES
> 3 SEARCH FILE ENTRIES
> 4 MODIFY FILE ATTRIBUTES
> 5 INQUIRE TO FILE ENTRIES
> 6 UTILITY FUNCTIONS
> 7 OTHER OPTIONS
> 8 DATA DICTIONARY UTILITIES
> 9 TRANSFER ENTRIES
> Select OPTION: 5 INQUIRE TO FILE ENTRIES
> OUTPUT FROM WHAT FILE: KERNEL SYSTEM PARAMETERS// INSTALL
> (7163 entries)
> Select INSTALL NAME: LA*5.2*67 Install Completed Install
> Completed 3/
> 20/06@15:42:30
> => LA*5.2*67/LR*5.2*290 ;Created on May 26, 2005@16:43:07
> ANOTHER ONE: LR*5.2*290 Install Completed Install Completed
> 3/20/06@1
> 5:42:32
> => LA*5.2*67/LR*5.2*290 ;Created on May 26, 2005@16:43:07
> ANOTHER ONE:
> On Dec 21, 8:42 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
>> How do I know if LA*5.2*67 and LR*5.2*290 are installed in WVEHR? In
>> EVE -> Prog -> KIDS -> Utilities --> Display and I put in LA for the
>> package, 3 items come up and they all seem to have the 5.2 versions
>> but the *67 and *290 part I am not sure of and do not see it
>> particularly. Does WVEHR have these installed by default? These are
>> possibly necessary to have installed per this document:
>> http://www.va.gov/vdl/documents/Clinical/Lab-Point_of_Care/lab_52_lr2...
>> "IRM Staff
>> IRM staff is required to install the VistA Laboratory Point of Care
>> (POC) Interface Patches
>> LA*5.2*67 and LR*5.2*290 software [[application~|Application]] on the VistA systems.
>> IRM staff must assist with the POC post implementation requirements
>> setup, if needed. The POC post implementation requirements setup must
>> to be coordinated with the LIM staff and Laboratory's ADPAC or ATC."
>> -- IV
>> On Dec 21, 10:39 am, "Ignacio Valdes" <ival...@hal-pc.org> wrote:
>>> 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
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.9.19/1860 - Release Date: 12/21/2008 3:08 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Discussion subject changed to "Intracare Implementation Log Episode 39: Patient lab reports connection Haiku" by I, Valdes
I, Valdes
View profile
More options Dec 22 2008, 5:32 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Mon, 22 Dec 2008 14:32:18 -0800 (PST)
Local: Mon, Dec 22 2008 5:32 pm
Subject: Re: Intracare Implementation Log Episode 39: Patient lab reports connection Haiku
Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author
Deep and powerful magic this lab stuff is. Learn it I must.
76 different menu items with 'Lab'
This Haiku ends.
-- IV
On Dec 21, 10:39 am, "Ignacio Valdes" <ival...@hal-pc.org> wrote:
- Hide quoted text -
- Show quoted text -
> 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
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Discussion subject changed to "Intracare Implementation Log Episode 39: Patient lab reports connection." by I, Valdes
I, Valdes
View profile
More options Dec 23 2008, 10:43 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Tue, 23 Dec 2008 19:43:46 -0800 (PST)
Local: Tues, Dec 23 2008 10:43 pm
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
Is there a way to import HL7 lab report messages that have been
sftp'ed in a text file onto the server?
-- IV
On Dec 21, 10:39 am, "Ignacio Valdes" <ival...@hal-pc.org> wrote:
- Hide quoted text -
- Show quoted text -
> 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
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
fred trotter
View profile
More options Dec 24 2008, 12:40 am
From: "fred trotter" <fred.trot...@gmail.com>
Date: Tue, 23 Dec 2008 23:40:43 -0600
Local: Wed, Dec 24 2008 12:40 am
Subject: Re: [Hardhats] 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
I would ask on the Mirth forums to see what has been done. Normally,
you get mirth to handle anything that involves parsing hl7, and then
you use it to talk to your database/objects or whatever. Its pretty
straightforward when dealing with SQL, not sure how to get it to talk
to GTM.
Alternatively, if there is an HL7 parser in place, you can use mirth
to get the right "dialect" of HL7 to get it to work with what is in
place already in VistA.
I know that VistA can parse incoming hl7 messages, how does this happen?
-FT
- Hide quoted text -
- Show quoted text -
On Tue, Dec 23, 2008 at 9:43 PM, I, Valdes <ival...@hal-pc.org> wrote:
> Is there a way to import HL7 lab report messages that have been
> sftp'ed in a text file onto the server?
> -- IV
> On Dec 21, 10:39 am, "Ignacio Valdes" <ival...@hal-pc.org> wrote:
>> 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
--
Fred Trotter
http://www.fredtrotter.com
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 24 2008, 1:42 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Wed, 24 Dec 2008 10:42:15 -0800 (PST)
Local: Wed, Dec 24 2008 1:42 pm
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
Here is a real sample electrolyte panel HL7 sent from the lab with
Test Patient as the patient. About 8000 of these are available on
disk. Is there a way of importing/dealing with these? HL7 is version
2.2:
MSH|^~\&|M3REF|SOME MEDICAL LABORATORY|M3REF||200812241015||ORU||P|
2.2|
PID|1| 1941|7777777||TEST^PATIENT^|||M|||^HOUSTON^TX^770540000||0|
PV1|1||||||||
OBR|1||7777777^0^5|1257^ELECTROLYTE PANEL|R|200809221423|200809221423|
200809221424|||||||||||||||||X|||||||||2&MMI&MMI|
OBX|1|NM|17^SODIUM^L^N0||133|MMOL/L|136-145|L|
OBX|2|NM|18^POTASSIUM^L^N0||4|MMOL/L|3.5-5.1||
OBX|3|NM|19^CHLORIDE^L^N0||99|MMOL/L|98-107||
OBX|4|NM|20^CO2^L^N0||33|MMOL/L|22-31|H|
OBX|5|NM|196^ANION GAP^L^N1||9||7-18||
OBX|6|TX|77^COMMENTS:^L^F0||hl7 test||
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 28 2008, 11:58 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sun, 28 Dec 2008 20:58:07 -0800 (PST)
Local: Sun, Dec 28 2008 11:58 pm
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
This http://www.va.gov/vdl/documents/Clinical/Laboratory/lab5_2pi.pdf
Laboratory V. 5.2 Planning and Implementation Guide pdf on vdl has a
bunch of information on using the lab menus generally. 1994 though so
it says nothing about HL7. Can anyone who has set up lab in
communication with a private sector lab via HL7 contact me on or off
list? Thanks! -- IV
On Dec 24, 12:42 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
- Hide quoted text -
- Show quoted text -
> Here is a real sample electrolyte panel HL7 sent from the lab with
> Test Patient as the patient. About 8000 of these are available on
> disk. Is there a way of importing/dealing with these? HL7 is version
> 2.2:
> MSH|^~\&|M3REF|SOME MEDICAL LABORATORY|M3REF||200812241015||ORU||P|
> 2.2|
> PID|1| 1941|7777777||TEST^PATIENT^|||M|||^HOUSTON^TX^770540000||0|
> PV1|1||||||||
> OBR|1||7777777^0^5|1257^ELECTROLYTE PANEL|R|200809221423|200809221423|
> 200809221424|||||||||||||||||X|||||||||2&MMI&MMI|
> OBX|1|NM|17^SODIUM^L^N0||133|MMOL/L|136-145|L|
> OBX|2|NM|18^POTASSIUM^L^N0||4|MMOL/L|3.5-5.1||
> OBX|3|NM|19^CHLORIDE^L^N0||99|MMOL/L|98-107||
> OBX|4|NM|20^CO2^L^N0||33|MMOL/L|22-31|H|
> OBX|5|NM|196^ANION GAP^L^N1||9||7-18||
> OBX|6|TX|77^COMMENTS:^L^F0||hl7 test||
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 29 2008, 12:16 am
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sun, 28 Dec 2008 21:16:55 -0800 (PST)
Local: Mon, Dec 29 2008 12:16 am
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
On or about page 76 of this document: VistA Laboratory Point of Care
(POC) Interface Patches LA*5.2*67/LR*5.2*290 Installation and User
Guide V. 5.2 http://www.va.gov/vdl/documents/Clinical/Lab-Point_of_Care/lab_52_lr2...
It has some instructions for setting up lab to receive HL7 messages.
-- IV
On Dec 28, 10:58 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
- Hide quoted text -
- Show quoted text -
> Thishttp://www.va.gov/vdl/documents/Clinical/Laboratory/lab5_2pi.pdf
> Laboratory V. 5.2 Planning and Implementation Guide pdf on vdl has a
> bunch of information on using the lab menus generally. 1994 though so
> it says nothing about HL7. Can anyone who has set up lab in
> communication with a private sector lab via HL7 contact me on or off
> list? Thanks! -- IV
> On Dec 24, 12:42 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
> > Here is a real sample electrolyte panel HL7 sent from the lab with
> > Test Patient as the patient. About 8000 of these are available on
> > disk. Is there a way of importing/dealing with these? HL7 is version
> > 2.2:
> > MSH|^~\&|M3REF|SOME MEDICAL LABORATORY|M3REF||200812241015||ORU||P|
> > 2.2|
> > PID|1| 1941|7777777||TEST^PATIENT^|||M|||^HOUSTON^TX^770540000||0|
> > PV1|1||||||||
> > OBR|1||7777777^0^5|1257^ELECTROLYTE PANEL|R|200809221423|200809221423|
> > 200809221424|||||||||||||||||X|||||||||2&MMI&MMI|
> > OBX|1|NM|17^SODIUM^L^N0||133|MMOL/L|136-145|L|
> > OBX|2|NM|18^POTASSIUM^L^N0||4|MMOL/L|3.5-5.1||
> > OBX|3|NM|19^CHLORIDE^L^N0||99|MMOL/L|98-107||
> > OBX|4|NM|20^CO2^L^N0||33|MMOL/L|22-31|H|
> > OBX|5|NM|196^ANION GAP^L^N1||9||7-18||
> > OBX|6|TX|77^COMMENTS:^L^F0||hl7 test||
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post:
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Dec 29 2008, 12:25 am
From: John McCormack <johnm...@ix.netcom.com>
Date: Sun, 28 Dec 2008 23:25:52 -0600
Local: Mon, Dec 29 2008 12:25 am
Subject: Re: [Hardhats] 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
http://www.va.gov/vdl/[[application~|Application]].asp?appid=75
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> This http://www.va.gov/vdl/documents/Clinical/Laboratory/lab5_2pi.pdf
> Laboratory V. 5.2 Planning and Implementation Guide pdf on vdl has a
> bunch of information on using the lab menus generally. 1994 though so
> it says nothing about HL7. Can anyone who has set up lab in
> communication with a private sector lab via HL7 contact me on or off
> list? Thanks! -- IV
> On Dec 24, 12:42 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
>> Here is a real sample electrolyte panel HL7 sent from the lab with
>> Test Patient as the patient. About 8000 of these are available on
>> disk. Is there a way of importing/dealing with these? HL7 is version
>> 2.2:
>> MSH|^~\&|M3REF|SOME MEDICAL LABORATORY|M3REF||200812241015||ORU||P|
>> 2.2|
>> PID|1| 1941|7777777||TEST^PATIENT^|||M|||^HOUSTON^TX^770540000||0|
>> PV1|1||||||||
>> OBR|1||7777777^0^5|1257^ELECTROLYTE PANEL|R|200809221423|200809221423|
>> 200809221424|||||||||||||||||X|||||||||2&MMI&MMI|
>> OBX|1|NM|17^SODIUM^L^N0||133|MMOL/L|136-145|L|
>> OBX|2|NM|18^POTASSIUM^L^N0||4|MMOL/L|3.5-5.1||
>> OBX|3|NM|19^CHLORIDE^L^N0||99|MMOL/L|98-107||
>> OBX|4|NM|20^CO2^L^N0||33|MMOL/L|22-31|H|
>> OBX|5|NM|196^ANION GAP^L^N1||9||7-18||
>> OBX|6|TX|77^COMMENTS:^L^F0||hl7 test||
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.1/1867 - Release Date: 12/28/2008 2:23 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post:
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Dec 29 2008, 5:58 am
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Mon, 29 Dec 2008 05:58:05 -0500
Local: Mon, Dec 29 2008 5:58 am
Subject: Re: [Hardhats] 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
http://opensourcevista.net:8888/NancysVistAServer/LabInterface/
On Monday 29 December 2008, John McCormack wrote:
- Hide quoted text -
- Show quoted text -
> http://www.va.gov/vdl/[[application~|Application]].asp?appid=75
> I, Valdes wrote:
> > This http://www.va.gov/vdl/documents/Clinical/Laboratory/lab5_2pi.pdf
> > Laboratory V. 5.2 Planning and Implementation Guide pdf on vdl has a
> > bunch of information on using the lab menus generally. 1994 though so
> > it says nothing about HL7. Can anyone who has set up lab in
> > communication with a private sector lab via HL7 contact me on or off
> > list? Thanks! -- IV
> > On Dec 24, 12:42 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
> >> Here is a real sample electrolyte panel HL7 sent from the lab with
> >> Test Patient as the patient. About 8000 of these are available on
> >> disk. Is there a way of importing/dealing with these? HL7 is version
> >> 2.2:
> >> MSH|^~\&|M3REF|SOME MEDICAL LABORATORY|M3REF||200812241015||ORU||P|
> >> 2.2|
> >> PID|1| 1941|7777777||TEST^PATIENT^|||M|||^HOUSTON^TX^770540000||0|
> >> PV1|1||||||||
> >> OBR|1||7777777^0^5|1257^ELECTROLYTE PANEL|R|200809221423|200809221423|
> >> 200809221424|||||||||||||||||X|||||||||2&MMI&MMI|
> >> OBX|1|NM|17^SODIUM^L^N0||133|MMOL/L|136-145|L|
> >> OBX|2|NM|18^POTASSIUM^L^N0||4|MMOL/L|3.5-5.1||
> >> OBX|3|NM|19^CHLORIDE^L^N0||99|MMOL/L|98-107||
> >> OBX|4|NM|20^CO2^L^N0||33|MMOL/L|22-31|H|
> >> OBX|5|NM|196^ANION GAP^L^N1||9||7-18||
> >> OBX|6|TX|77^COMMENTS:^L^F0||hl7 test||
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG - http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.1/1867 - Release Date:
> > 12/28/2008 2:23 PM
--
Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Dec 29 2008, 5:59 am
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Mon, 29 Dec 2008 05:59:52 -0500
Local: Mon, Dec 29 2008 5:59 am
Subject: Re: [Hardhats] 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
If you are looking to Interface with LabCorp, LabCorp has an interface written
specifically for VistA that many LabCorp folks do not know about.
On Monday 29 December 2008, John McCormack wrote:
- Hide quoted text -
- Show quoted text -
> http://www.va.gov/vdl/[[application~|Application]].asp?appid=75
> I, Valdes wrote:
> > This http://www.va.gov/vdl/documents/Clinical/Laboratory/lab5_2pi.pdf
> > Laboratory V. 5.2 Planning and Implementation Guide pdf on vdl has a
> > bunch of information on using the lab menus generally. 1994 though so
> > it says nothing about HL7. Can anyone who has set up lab in
> > communication with a private sector lab via HL7 contact me on or off
> > list? Thanks! -- IV
> > On Dec 24, 12:42 pm, "I, Valdes" <ival...@hal-pc.org> wrote:
> >> Here is a real sample electrolyte panel HL7 sent from the lab with
> >> Test Patient as the patient. About 8000 of these are available on
> >> disk. Is there a way of importing/dealing with these? HL7 is version
> >> 2.2:
> >> MSH|^~\&|M3REF|SOME MEDICAL LABORATORY|M3REF||200812241015||ORU||P|
> >> 2.2|
> >> PID|1| 1941|7777777||TEST^PATIENT^|||M|||^HOUSTON^TX^770540000||0|
> >> PV1|1||||||||
> >> OBR|1||7777777^0^5|1257^ELECTROLYTE PANEL|R|200809221423|200809221423|
> >> 200809221424|||||||||||||||||X|||||||||2&MMI&MMI|
> >> OBX|1|NM|17^SODIUM^L^N0||133|MMOL/L|136-145|L|
> >> OBX|2|NM|18^POTASSIUM^L^N0||4|MMOL/L|3.5-5.1||
> >> OBX|3|NM|19^CHLORIDE^L^N0||99|MMOL/L|98-107||
> >> OBX|4|NM|20^CO2^L^N0||33|MMOL/L|22-31|H|
> >> OBX|5|NM|196^ANION GAP^L^N1||9||7-18||
> >> OBX|6|TX|77^COMMENTS:^L^F0||hl7 test||
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG - http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.1/1867 - Release Date:
> > 12/28/2008 2:23 PM
--
Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 29 2008, 11:14 am
From: "I, Valdes" <ival...@hal-pc.org>
Date: Mon, 29 Dec 2008 08:14:58 -0800 (PST)
Local: Mon, Dec 29 2008 11:14 am
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
Unfortunately, it isn't Labcorp, but I would really like to know how
anyone including with Labcorp has interfaced this with any lab as how
one actually does the workflow with an outside lab is as important as
the software. -- IV
On Dec 29, 4:59 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
- Hide quoted text -
- Show quoted text -
> If you are looking to Interface with LabCorp, LabCorp has an interface written
> specifically for VistA that many LabCorp folks do not know about.
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Dec 29 2008, 12:33 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Mon, 29 Dec 2008 11:33:16 -0600
Local: Mon, Dec 29 2008 12:33 pm
Subject: Re: [Hardhats] 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
See http://www.va.gov/vdl/[[application~|Application]].asp?appid=75
Specifically
http://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
The LEDI III software is to manage shipment of specimens, send and
receive electronic orders and results with a reference lab be that
another VAMC, DoD Lab or a commercial reference lab.
It is predicated on the facility sending the order (collecting facility)
also physically collecting and sending the laboratory specimen to the
reference lab.
Additionally, predicated on the premise that the collecting facility
performs laboratory testing in-house, that only selected tests are sent
to a reference lab and that testing can be sent to multiple reference
labs concurrently. If there is no HL7 interface then only the shipping
component is implemented.
Basically you:
1. Configure a shipping [[configuration~|Configuration]] to specify the tests and other
characteristics related to shipping the specimen/test to the reference lab.
2. Build a manifest using a selected [[configuration~|Configuration]] to identify the
specimens to ship.
3. Mark the manifest as shipped.
4. If HL7 interface then it sends electronic orders.
5. If HL7 interface wait for results to return via interface and accept
results.
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> Unfortunately, it isn't Labcorp, but I would really like to know how
> anyone including with Labcorp has interfaced this with any lab as how
> one actually does the workflow with an outside lab is as important as
> the software. -- IV
> On Dec 29, 4:59 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
>> If you are looking to Interface with LabCorp, LabCorp has an interface written
>> specifically for VistA that many LabCorp folks do not know about.
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 29 2008, 10:57 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Mon, 29 Dec 2008 19:57:58 -0800 (PST)
Local: Mon, Dec 29 2008 10:57 pm
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
John, This looks like what I was trying to find. How does one actually
id the sample tubes? I think that right now we wrap an id sticky label
with identifying data. With LEDI does one use similar or barcoding?
-- IV
On Dec 29, 11:33 am, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> Seehttp://www.va.gov/vdl/[[application~|Application]].asp?appid=75
> Specificallyhttp://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
> The LEDI III software is to manage shipment of specimens, send and
> receive electronic orders and results with a reference lab be that
> another VAMC, DoD Lab or a commercial reference lab.
> It is predicated on the facility sending the order (collecting facility)
> also physically collecting and sending the laboratory specimen to the
> reference lab.
> Additionally, predicated on the premise that the collecting facility
> performs laboratory testing in-house, that only selected tests are sent
> to a reference lab and that testing can be sent to multiple reference
> labs concurrently. If there is no HL7 interface then only the shipping
> component is implemented.
> Basically you:
> 1. Configure a shipping [[configuration~|Configuration]] to specify the tests and other
> characteristics related to shipping the specimen/test to the reference lab.
> 2. Build a manifest using a selected [[configuration~|Configuration]] to identify the
> specimens to ship.
> 3. Mark the manifest as shipped.
> 4. If HL7 interface then it sends electronic orders.
> 5. If HL7 interface wait for results to return via interface and accept
> results.
> I, Valdes wrote:
> > Unfortunately, it isn't Labcorp, but I would really like to know how
> > anyone including with Labcorp has interfaced this with any lab as how
> > one actually does the workflow with an outside lab is as important as
> > the software. -- IV
> > On Dec 29, 4:59 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
> >> If you are looking to Interface with LabCorp, LabCorp has an interface written
> >> specifically for VistA that many LabCorp folks do not know about.
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 29 2008, 11:01 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Mon, 29 Dec 2008 20:01:28 -0800 (PST)
Local: Mon, Dec 29 2008 11:01 pm
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
Does anyone have a test server up with test lab data that I can
transmit and receive fake test lab results?
-- IV
On Dec 29, 11:33 am, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> Seehttp://www.va.gov/vdl/[[application~}Application]].asp?appid=75
> Specificallyhttp://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
> The LEDI III software is to manage shipment of specimens, send and
> receive electronic orders and results with a reference lab be that
> another VAMC, DoD Lab or a commercial reference lab.
> It is predicated on the facility sending the order (collecting facility)
> also physically collecting and sending the laboratory specimen to the
> reference lab.
> Additionally, predicated on the premise that the collecting facility
> performs laboratory testing in-house, that only selected tests are sent
> to a reference lab and that testing can be sent to multiple reference
> labs concurrently. If there is no HL7 interface then only the shipping
> component is implemented.
> Basically you:
> 1. Configure a shipping [[configuration~|Configuration]] to specify the tests and other
> characteristics related to shipping the specimen/test to the reference lab.
> 2. Build a manifest using a selected [[configuration~|Configuration]] to identify the
> specimens to ship.
> 3. Mark the manifest as shipped.
> 4. If HL7 interface then it sends electronic orders.
> 5. If HL7 interface wait for results to return via interface and accept
> results.
> I, Valdes wrote:
> > Unfortunately, it isn't Labcorp, but I would really like to know how
> > anyone including with Labcorp has interfaced this with any lab as how
> > one actually does the workflow with an outside lab is as important as
> > the software. -- IV
> > On Dec 29, 4:59 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
> >> If you are looking to Interface with LabCorp, LabCorp has an interface written
> >> specifically for VistA that many LabCorp folks do not know about.
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Dec 30 2008, 8:32 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Tue, 30 Dec 2008 19:32:38 -0600
Local: Tues, Dec 30 2008 8:32 pm
Subject: Re: [Hardhats] 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
The LEDI software works in conjunction with normal laboratory
operations. Therefore it assumes and uses the existing accessions that
the facility has collected and started to process. The specimen id is
the one the lab software assigns to the accession which for LEDI
purposes the the accession's UID.
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> John, This looks like what I was trying to find. How does one actually
> id the sample tubes? I think that right now we wrap an id sticky label
> with identifying data. With LEDI does one use similar or barcoding?
> -- IV
> On Dec 29, 11:33 am, John McCormack <johnm...@ix.netcom.com> wrote:
>> Seehttp://www.va.gov/vdl/[[application~|Application]].asp?appid=75
>> Specificallyhttp://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
>> The LEDI III software is to manage shipment of specimens, send and
>> receive electronic orders and results with a reference lab be that
>> another VAMC, DoD Lab or a commercial reference lab.
>> It is predicated on the facility sending the order (collecting facility)
>> also physically collecting and sending the laboratory specimen to the
>> reference lab.
>> Additionally, predicated on the premise that the collecting facility
>> performs laboratory testing in-house, that only selected tests are sent
>> to a reference lab and that testing can be sent to multiple reference
>> labs concurrently. If there is no HL7 interface then only the shipping
>> component is implemented.
>> Basically you:
>> 1. Configure a shipping [[configuration~|Configuration]] to specify the tests and other
>> characteristics related to shipping the specimen/test to the reference lab.
>> 2. Build a manifest using a selected [[configuration~|Configuration]] to identify the
>> specimens to ship.
>> 3. Mark the manifest as shipped.
>> 4. If HL7 interface then it sends electronic orders.
>> 5. If HL7 interface wait for results to return via interface and accept
>> results.
>> I, Valdes wrote:
>>> Unfortunately, it isn't Labcorp, but I would really like to know how
>>> anyone including with Labcorp has interfaced this with any lab as how
>>> one actually does the workflow with an outside lab is as important as
>>> the software. -- IV
>>> On Dec 29, 4:59 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
>>>> If you are looking to Interface with LabCorp, LabCorp has an interface written
>>>> specifically for VistA that many LabCorp folks do not know about.
>>> ------------------------------------------------------------------------
>>> No virus found in this incoming message.
>>> Checked by AVG -http://www.avg.com
>>> Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.1/1869 - Release Date: 12/30/2008 12:06 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Dec 30 2008, 10:34 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Tue, 30 Dec 2008 19:34:02 -0800 (PST)
Local: Tues, Dec 30 2008 10:34 pm
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
So accession number is the critical value and the sample has the
accession number written on it for sure? Anything else usually on the
sample like name just in case? -- IV
On Dec 30, 7:32 pm, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> The LEDI software works in conjunction with normal laboratory
> operations. Therefore it assumes and uses the existing accessions that
> the facility has collected and started to process. The specimen id is
> the one the lab software assigns to the accession which for LEDI
> purposes the the accession's UID.
> I, Valdes wrote:
> > John, This looks like what I was trying to find. How does one actually
> > id the sample tubes? I think that right now we wrap an id sticky label
> > with identifying data. With LEDI does one use similar or barcoding?
> > -- IV
> > On Dec 29, 11:33 am, John McCormack <johnm...@ix.netcom.com> wrote:
> >> Seehttp://www.va.gov/vdl/[[application~|Application]].asp?appid=75
> >> Specificallyhttp://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
> >> The LEDI III software is to manage shipment of specimens, send and
> >> receive electronic orders and results with a reference lab be that
> >> another VAMC, DoD Lab or a commercial reference lab.
> >> It is predicated on the facility sending the order (collecting facility)
> >> also physically collecting and sending the laboratory specimen to the
> >> reference lab.
> >> Additionally, predicated on the premise that the collecting facility
> >> performs laboratory testing in-house, that only selected tests are sent
> >> to a reference lab and that testing can be sent to multiple reference
> >> labs concurrently. If there is no HL7 interface then only the shipping
> >> component is implemented.
> >> Basically you:
> >> 1. Configure a shipping configuration to specify the tests and other
> >> characteristics related to shipping the specimen/test to the reference lab.
> >> 2. Build a manifest using a selected configuration to identify the
> >> specimens to ship.
> >> 3. Mark the manifest as shipped.
> >> 4. If HL7 interface then it sends electronic orders.
> >> 5. If HL7 interface wait for results to return via interface and accept
> >> results.
> >> I, Valdes wrote:
> >>> Unfortunately, it isn't Labcorp, but I would really like to know how
> >>> anyone including with Labcorp has interfaced this with any lab as how
> >>> one actually does the workflow with an outside lab is as important as
> >>> the software. -- IV
> >>> On Dec 29, 4:59 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
> >>>> If you are looking to Interface with LabCorp, LabCorp has an interface written
> >>>> specifically for VistA that many LabCorp folks do not know about.
> >>> ------------------------------------------------------------------------
> >>> No virus found in this incoming message.
> >>> Checked by AVG -http://www.avg.com
> >>> Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.1/1869 - Release Date: 12/30/2008 12:06 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Dec 31 2008, 1:26 am
From: John McCormack <johnm...@ix.netcom.com>
Date: Wed, 31 Dec 2008 00:26:50 -0600
Local: Wed, Dec 31 2008 1:26 am
Subject: Re: [Hardhats] 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
The accession label applied to the specimen will have the patient name,
patient id, patient location, patient info, accession, ordered test,
collection sample, urgency, and appropriate barcode.
P.S. by "written" I assuming your referring to printed labels. Use of
handwritten labels are avoided and haven't been used for 10-15 years for
patient safety reasons.
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> So accession number is the critical value and the sample has the
> accession number written on it for sure? Anything else usually on the
> sample like name just in case? -- IV
> On Dec 30, 7:32 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>> The LEDI software works in conjunction with normal laboratory
>> operations. Therefore it assumes and uses the existing accessions that
>> the facility has collected and started to process. The specimen id is
>> the one the lab software assigns to the accession which for LEDI
>> purposes the the accession's UID.
>> I, Valdes wrote:
>>> John, This looks like what I was trying to find. How does one actually
>>> id the sample tubes? I think that right now we wrap an id sticky label
>>> with identifying data. With LEDI does one use similar or barcoding?
>>> -- IV
>>> On Dec 29, 11:33 am, John McCormack <johnm...@ix.netcom.com> wrote:
>>>> Seehttp://www.va.gov/vdl/[[application~|Application]].asp?appid=75
>>>> Specificallyhttp://www.va.gov/vdl/documents/Clinical/Lab-Electr_Data_Intrchg_(LED...
>>>> The LEDI III software is to manage shipment of specimens, send and
>>>> receive electronic orders and results with a reference lab be that
>>>> another VAMC, DoD Lab or a commercial reference lab.
>>>> It is predicated on the facility sending the order (collecting facility)
>>>> also physically collecting and sending the laboratory specimen to the
>>>> reference lab.
>>>> Additionally, predicated on the premise that the collecting facility
>>>> performs laboratory testing in-house, that only selected tests are sent
>>>> to a reference lab and that testing can be sent to multiple reference
>>>> labs concurrently. If there is no HL7 interface then only the shipping
>>>> component is implemented.
>>>> Basically you:
>>>> 1. Configure a shipping [[configuration~|Configuration]] to specify the tests and other
>>>> characteristics related to shipping the specimen/test to the reference lab.
>>>> 2. Build a manifest using a selected [[configuration~|Configuration]] to identify the
>>>> specimens to ship.
>>>> 3. Mark the manifest as shipped.
>>>> 4. If HL7 interface then it sends electronic orders.
>>>> 5. If HL7 interface wait for results to return via interface and accept
>>>> results.
>>>> I, Valdes wrote:
>>>>> Unfortunately, it isn't Labcorp, but I would really like to know how
>>>>> anyone including with Labcorp has interfaced this with any lab as how
>>>>> one actually does the workflow with an outside lab is as important as
>>>>> the software. -- IV
>>>>> On Dec 29, 4:59 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
>>>>>> If you are looking to Interface with LabCorp, LabCorp has an interface written
>>>>>> specifically for VistA that many LabCorp folks do not know about.
>>>>> ------------------------------------------------------------------------
>>>>> No virus found in this incoming message.
>>>>> Checked by AVG -http://www.avg.com
>>>>> Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM
>>> ------------------------------------------------------------------------
>>> No virus found in this incoming message.
>>> Checked by AVG -http://www.avg.com
>>> Version: 8.0.176 / Virus Database: 270.10.1/1869 - Release Date: 12/30/2008 12:06 PM
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.1/1869 - Release Date: 12/30/2008 12:06 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 1, 3:35 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Thu, 1 Jan 2009 12:35:10 -0800 (PST)
Local: Thurs, Jan 1 2009 3:35 pm
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
What does this mean?
ROLLOVER HAS NOT RUN. ACCESSIONING SHOULDN'T BE DONE NOW.
ROLLOVER HAS BEEN TASKED -- TRY ACCESSIONING LATER
-- IV
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Jan 1, 4:13 pm
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Thu, 01 Jan 2009 16:13:53 -0500
Local: Thurs, Jan 1 2009 4:13 pm
Subject: Re: [Hardhats] 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
This is something that runs at night for lab.
Look at this menu
VOE LAB OPTIONS
I think that may have an option to get that done for you.
On Thursday 01 January 2009, I, Valdes wrote:
> What does this mean?
> ROLLOVER HAS NOT RUN. ACCESSIONING SHOULDN'T BE DONE NOW.
> ROLLOVER HAS BEEN TASKED -- TRY ACCESSIONING LATER
> -- IV
--
Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 1, 4:23 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Thu, 1 Jan 2009 13:23:45 -0800 (PST)
Local: Thurs, Jan 1 2009 4:23 pm
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
Hmm, VOE LAB OPTIONS doesn't seem to appear... I see VOE Fileman and
VOE text version which gives you the version... -- IV
On Jan 1, 3:13 pm, Nancy Anthracite <nanthrac...@verizon.net> wrote:
- Hide quoted text -
- Show quoted text -
> This is something that runs at night for lab.
> Look at this menu
> VOE LAB OPTIONS
> I think that may have an option to get that done for you.
> On Thursday 01 January 2009, I, Valdes wrote:
> > What does this mean?
> > ROLLOVER HAS NOT RUN. ACCESSIONING SHOULDN'T BE DONE NOW.
> > ROLLOVER HAS BEEN TASKED -- TRY ACCESSIONING LATER
> > -- IV
> --
> Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Jan 1, 5:17 pm
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Thu, 01 Jan 2009 17:17:50 -0500
Local: Thurs, Jan 1 2009 5:17 pm
Subject: Re: [Hardhats] 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
wvehr1@edu2:~$ gtm
Do you have the keys you need? Try adding it as a secondary menu and then
using ALL THE KEYS A USER NEEDS
GTM>S DUZ=9 D ^XUP
Setting up programmer environment
This is a TEST account.
Terminal Type set to: C-VT320
You have 7150 new messages.
Select OPTION NAME: VOE
1 VOE CCHIT NPI & DEA EDIT NPI & DEA Edit
2 VOE CCHIT NPI & DEA IDS List NPI, DEA & State IDs
3 VOE CCHIT OTHER IDS List UPIN & Other IDs
4 VOE CCHIT PROVIDER ID MAINT Maintain Provider IDs
5 VOE CCHIT UPIN, ETC MAINT UPIN & Other ID Edits
Press <RETURN> to see more, '^' to exit this list, OR
CHOOSE 1-5:
6 VOE DOQ-IT CAD EXTRACTION VOE DOQ-IT CAD EXTRACTION
7 VOE DOQ-IT DM EXTRACTION VOE DOQ-IT DM EXTRACTION
8 VOE DOQ-IT HF EXTRACTION VOE DOQ-IT HF EXTRACTION
9 VOE DOQ-IT HTN EXTRACTION VOE DOQ-IT HTN EXTRACTION
10 VOE DOQ-IT PC EXTRACT VOE DOQ-IT PC EXTRACTION
Press <RETURN> to see more, '^' to exit this list, OR
CHOOSE 1-10:
11 VOE LAB OPTIONS Lab Options
12 VOE VERSION Voe Version Text
13 VOE FILEMAN DIZ FILEMAN VOE Fileman
14 VOES SCANNING VFGS SCANNING VOES SCANNING
On Thursday 01 January 2009, I, Valdes wrote:
- Hide quoted text -
- Show quoted text -
> Hmm, VOE LAB OPTIONS doesn't seem to appear... I see VOE Fileman and
> VOE text version which gives you the version... -- IV
> On Jan 1, 3:13 pm, Nancy Anthracite <nanthrac...@verizon.net> wrote:
> > This is something that runs at night for lab.
> > Look at this menu
> > VOE LAB OPTIONS
> > I think that may have an option to get that done for you.
> > On Thursday 01 January 2009, I, Valdes wrote:
> > > What does this mean?
> > > ROLLOVER HAS NOT RUN. ACCESSIONING SHOULDN'T BE DONE NOW.
> > > ROLLOVER HAS BEEN TASKED -- TRY ACCESSIONING LATER
> > > -- IV
> > --
> > Nancy Anthracite
--
Nancy Anthracite
Nancy Anthracite
View profile
More options Jan 1, 5:19 pm
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Thu, 01 Jan 2009 17:19:37 -0500
Local: Thurs, Jan 1 2009 5:19 pm
Subject: Re: [Hardhats] 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
OR try ROLLOVER ACCESSION
On Thursday 01 January 2009, Nancy Anthracite wrote:
- Hide quoted text -
- Show quoted text -
> wvehr1@edu2:~$ gtm
> Do you have the keys you need? Try adding it as a secondary menu and then
> using ALL THE KEYS A USER NEEDS
> GTM>S DUZ=9 D ^XUP
> Setting up programmer environment
> This is a TEST account.
> Terminal Type set to: C-VT320
> You have 7150 new messages.
> Select OPTION NAME: VOE
> 1 VOE CCHIT NPI & DEA EDIT NPI & DEA Edit
> 2 VOE CCHIT NPI & DEA IDS List NPI, DEA & State IDs
> 3 VOE CCHIT OTHER IDS List UPIN & Other IDs
> 4 VOE CCHIT PROVIDER ID MAINT Maintain Provider IDs
> 5 VOE CCHIT UPIN, ETC MAINT UPIN & Other ID Edits
> Press <RETURN> to see more, '^' to exit this list, OR
> CHOOSE 1-5:
> 6 VOE DOQ-IT CAD EXTRACTION VOE DOQ-IT CAD EXTRACTION
> 7 VOE DOQ-IT DM EXTRACTION VOE DOQ-IT DM EXTRACTION
> 8 VOE DOQ-IT HF EXTRACTION VOE DOQ-IT HF EXTRACTION
> 9 VOE DOQ-IT HTN EXTRACTION VOE DOQ-IT HTN EXTRACTION
> 10 VOE DOQ-IT PC EXTRACT VOE DOQ-IT PC EXTRACTION
> Press <RETURN> to see more, '^' to exit this list, OR
> CHOOSE 1-10:
> 11 VOE LAB OPTIONS Lab Options
> 12 VOE VERSION Voe Version Text
> 13 VOE FILEMAN DIZ FILEMAN VOE Fileman
> 14 VOES SCANNING VFGS SCANNING VOES SCANNING
> On Thursday 01 January 2009, I, Valdes wrote:
> > Hmm, VOE LAB OPTIONS doesn't seem to appear... I see VOE Fileman and
> > VOE text version which gives you the version... -- IV
> > On Jan 1, 3:13 pm, Nancy Anthracite <nanthrac...@verizon.net> wrote:
> > > This is something that runs at night for lab.
> > > Look at this menu
> > > VOE LAB OPTIONS
> > > I think that may have an option to get that done for you.
> > > On Thursday 01 January 2009, I, Valdes wrote:
> > > > What does this mean?
> > > > ROLLOVER HAS NOT RUN. ACCESSIONING SHOULDN'T BE DONE NOW.
> > > > ROLLOVER HAS BEEN TASKED -- TRY ACCESSIONING LATER
> > > > -- IV
> > > --
> > > Nancy Anthracite
--
Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 1, 5:45 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Thu, 01 Jan 2009 16:45:46 -0600
Local: Thurs, Jan 1 2009 5:45 pm
Subject: Re: [Hardhats] 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
Schedule option LRTASK ROLOVER to run daily at 0001 via the Taskman
Schedule an option.
- Hide quoted text -
- Show quoted text -
Nancy Anthracite wrote:
> OR try ROLLOVER ACCESSION
> On Thursday 01 January 2009, Nancy Anthracite wrote:
>> wvehr1@edu2:~$ gtm
>> Do you have the keys you need? Try adding it as a secondary menu and then
>> using ALL THE KEYS A USER NEEDS
>> GTM>S DUZ=9 D ^XUP
>> Setting up programmer environment
>> This is a TEST account.
>> Terminal Type set to: C-VT320
>> You have 7150 new messages.
>> Select OPTION NAME: VOE
>> 1 VOE CCHIT NPI & DEA EDIT NPI & DEA Edit
>> 2 VOE CCHIT NPI & DEA IDS List NPI, DEA & State IDs
>> 3 VOE CCHIT OTHER IDS List UPIN & Other IDs
>> 4 VOE CCHIT PROVIDER ID MAINT Maintain Provider IDs
>> 5 VOE CCHIT UPIN, ETC MAINT UPIN & Other ID Edits
>> Press <RETURN> to see more, '^' to exit this list, OR
>> CHOOSE 1-5:
>> 6 VOE DOQ-IT CAD EXTRACTION VOE DOQ-IT CAD EXTRACTION
>> 7 VOE DOQ-IT DM EXTRACTION VOE DOQ-IT DM EXTRACTION
>> 8 VOE DOQ-IT HF EXTRACTION VOE DOQ-IT HF EXTRACTION
>> 9 VOE DOQ-IT HTN EXTRACTION VOE DOQ-IT HTN EXTRACTION
>> 10 VOE DOQ-IT PC EXTRACT VOE DOQ-IT PC EXTRACTION
>> Press <RETURN> to see more, '^' to exit this list, OR
>> CHOOSE 1-10:
>> 11 VOE LAB OPTIONS Lab Options
>> 12 VOE VERSION Voe Version Text
>> 13 VOE FILEMAN DIZ FILEMAN VOE Fileman
>> 14 VOES SCANNING VFGS SCANNING VOES SCANNING
>> On Thursday 01 January 2009, I, Valdes wrote:
>>> Hmm, VOE LAB OPTIONS doesn't seem to appear... I see VOE Fileman and
>>> VOE text version which gives you the version... -- IV
>>> On Jan 1, 3:13 pm, Nancy Anthracite <nanthrac...@verizon.net> wrote:
>>>> This is something that runs at night for lab.
>>>> Look at this menu
>>>> VOE LAB OPTIONS
>>>> I think that may have an option to get that done for you.
>>>> On Thursday 01 January 2009, I, Valdes wrote:
>>>>> What does this mean?
>>>>> ROLLOVER HAS NOT RUN. ACCESSIONING SHOULDN'T BE DONE NOW.
>>>>> ROLLOVER HAS BEEN TASKED -- TRY ACCESSIONING LATER
>>>>> -- IV
>>>> --
>>>> Nancy Anthracite
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.1/1870 - Release Date: 12/31/2008 8:44 AM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 1, 9:46 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Thu, 1 Jan 2009 18:46:03 -0800 (PST)
Local: Thurs, Jan 1 2009 9:46 pm
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
I get:
Select EHR Registration Menu Option: ^ROLLOVER
1 Rollover Accession (Manual) [LR ROLLOVER]
2 ROLLOVER ACCESSION [LRTASK ROLLOVER]
Type '^' to stop, or choose a number from 1 to 2 :1 Rollover
Accession (Manual)
NOTIFY IRM SERVICE OF A POTENTIAL TASK MAN PROBLEM
ROLLOVER NOT REQUIRED
What is this supposed to do?
-- IV
On Jan 1, 4:19 pm, Nancy Anthracite <nanthrac...@verizon.net> wrote:
- Hide quoted text -
- Show quoted text -
> OR try ROLLOVER ACCESSION
> On Thursday 01 January 2009, Nancy Anthracite wrote:
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 1, 10:06 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Thu, 1 Jan 2009 19:06:58 -0800 (PST)
Local: Thurs, Jan 1 2009 10:06 pm
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
John, Nancy, Our current nearly all paper lab works like this:
1) Doctor orders lab on paper in chart. Order is taken off by putting
a pre-printed patient name, patient id number, age, dob label onto
form containing about 40 check offs for labs desired. Nurse checks off
which lab is ordered then puts the sheet into the binder with others
for ward collect. This form comes with 6 small sticky labels with a 6
digit unique requisition number from the lab are pre-stocked in the
hospital.
2) Phlebotomist arrives at 6 am and 3pm every day. Collects form in
aforesaid 1) above, takes blood from patients, peels and sticks 6
digit unique requisition number and puts it onto the specimen
container (tube, etc) just drawn.
3) Lab personnel carries specimens and forms like the form in 1) to
the lab. The patients name, id number, date of birth, requisition
number, pre-generated 7 digit specimen id that maps to requisition
number, and test desired are entered into the lab computer. A sticky
label with patient name, bar code and specimen id is generated stuck
to the specimen container and placed in the instrument rack for
testing.
4) Results are printed and faxed to the hospital. Nurses put reports
into charts.
The current lab system is capable of sending us HL7 version 2.2
messages containing reports. It is unknown whether they can accept HL7
orders directly from our system.
Given all this, what do you think is the best way to proceed in
getting this working with VistA?
-- IV
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Jan 1, 10:33 pm
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Thu, 01 Jan 2009 22:33:51 -0500
Local: Thurs, Jan 1 2009 10:33 pm
Subject: Re: [Hardhats] 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
As I understand it, it moves the schedule for tasks not completed in a given
day to the next day so that things are properly dated and sequenced.
On Thursday 01 January 2009, I, Valdes wrote:
- Hide quoted text -
- Show quoted text -
> I get:
> Select EHR Registration Menu Option: ^ROLLOVER
> 1 Rollover Accession (Manual) [LR ROLLOVER]
> 2 ROLLOVER ACCESSION [LRTASK ROLLOVER]
> Type '^' to stop, or choose a number from 1 to 2 :1 Rollover
> Accession (Manual)
> NOTIFY IRM SERVICE OF A POTENTIAL TASK MAN PROBLEM
> ROLLOVER NOT REQUIRED
> What is this supposed to do?
> -- IV
> On Jan 1, 4:19 pm, Nancy Anthracite <nanthrac...@verizon.net> wrote:
> > OR try ROLLOVER ACCESSION
> > On Thursday 01 January 2009, Nancy Anthracite wrote:
--
Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 3, 1:06 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sat, 3 Jan 2009 10:06:29 -0800 (PST)
Local: Sat, Jan 3 2009 1:06 pm
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
Hi all, I followed Page 42 of
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
the gtm [[prompt~|Prompt]] as follows:
Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
Load DMIS ID's
GTM>
Doing a ZSHOW "*" has ZSTATUS=""
Is there something wrong? -- IV
1. IRM: INSTITUTION file (#4) Setup Instructions
Load the DoD DMIS ID codes into your INSTITUION file (#4) using the
Load DMIS ID's
[XUMF DMIS ID LOAD] option installed by Kernel patch XU*8.0*261. LEDI
software
uses the following four fields from the INSTITUION file (#4). Check
both the HOST and
COLLECTION institutions.
• Name Field (#.01): The Institution Master File maintains nationally
controlled entries
for VA and DoD facilities.
• Agency code Field (#95): This field indicates to the LEDI III
software whether the
facility is a VA or DoD facility
• VA facilities should be set to: ‘VA’
• DoD facilities should be set to:
‘AF’ - AIR FORCE
‘ARMY’ - ARMY
‘N’ – NAVY
• Station Number Field (#99): For VA facilities
• Identifier (#9999): For DoD facilities indicate the DMIS ID for this
facility
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 3, 3:00 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Sat, 03 Jan 2009 14:00:54 -0600
Local: Sat, Jan 3 2009 3:00 pm
Subject: Re: [Hardhats] 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
Please note the section your attempting to implement - COLLECTION
facility -- VA to DoD Laboratory Implementation Instructions
This section is used to configure the software to communicate with a DoD
Laboratory facility. The requirement to load DMIS ID codes is due to the
use of DMIS ID codes to identify DoD CHCS Laboratory facilities. They
are used similar to VA station numbers to identify VA facilities.
The option to load DMIS ID retrieves the DoD entries from the VA Master
File Server which contains nationally controlled entries for
institutions from the INSTITUTION file. It tasks a background process to
update the local site's INSTITUTION file with military medical
facilities. This process will probably fail due to the situation of the
VA Master File Server being behind the VA firewall and the use of
10.x.x.x addresses which are not accessible from the public internet.
Additionally, your probably be better off following the setup
instructions for a commercial reference lab.
Page 81 - COLLECTION facility -- VA to Commercial Reference Laboratory
Note that there are specific setup instructions for each of the various
scenarios. These setup variations affect how and what files/fields are
configured and how and what information is contained in the files/fields.
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> Hi all, I followed Page 42 of
> 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
> the gtm [[prompt~|Prompt]] as follows:
> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
> Load DMIS ID's
> GTM>
> Doing a ZSHOW "*" has ZSTATUS=""
> Is there something wrong? -- IV
> 1. IRM: INSTITUTION file (#4) Setup Instructions
> Load the DoD DMIS ID codes into your INSTITUION file (#4) using the
> Load DMIS ID's
> [XUMF DMIS ID LOAD] option installed by Kernel patch XU*8.0*261. LEDI
> software
> uses the following four fields from the INSTITUION file (#4). Check
> both the HOST and
> COLLECTION institutions.
> . Name Field (#.01): The Institution Master File maintains nationally
> controlled entries
> for VA and DoD facilities.
> . Agency code Field (#95): This field indicates to the LEDI III
> software whether the
> facility is a VA or DoD facility
> . VA facilities should be set to: 'VA'
> . DoD facilities should be set to:
> 'AF' - AIR FORCE
> 'ARMY' - ARMY
> 'N' -- NAVY
> . Station Number Field (#99): For VA facilities
> . Identifier (#9999): For DoD facilities indicate the DMIS ID for this
> facility
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 3, 9:44 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sat, 3 Jan 2009 18:44:21 -0800 (PST)
Local: Sat, Jan 3 2009 9:44 pm
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
Ah. -- IV
On Jan 3, 2:00 pm, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> Please note the section your attempting to implement - COLLECTION
> facility -- VA to DoD Laboratory Implementation Instructions
> This section is used to configure the software to communicate with a DoD
> Laboratory facility. The requirement to load DMIS ID codes is due to the
> use of DMIS ID codes to identify DoD CHCS Laboratory facilities. They
> are used similar to VA station numbers to identify VA facilities.
> The option to load DMIS ID retrieves the DoD entries from the VA Master
> File Server which contains nationally controlled entries for
> institutions from the INSTITUTION file. It tasks a background process to
> update the local site's INSTITUTION file with military medical
> facilities. This process will probably fail due to the situation of the
> VA Master File Server being behind the VA firewall and the use of
> 10.x.x.x addresses which are not accessible from the public internet.
> Additionally, your probably be better off following the setup
> instructions for a commercial reference lab.
> Page 81 - COLLECTION facility -- VA to Commercial Reference Laboratory
> Note that there are specific setup instructions for each of the various
> scenarios. These setup variations affect how and what files/fields are
> configured and how and what information is contained in the files/fields.
> I, Valdes wrote:
> > Hi all, I followed Page 42 of
> >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
> > the gtm [[prompt~|Prompt]] as follows:
> > Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
> > Load DMIS ID's
> > GTM>
> > Doing a ZSHOW "*" has ZSTATUS=""
> > Is there something wrong? -- IV
> > 1. IRM: INSTITUTION file (#4) Setup Instructions
> > Load the DoD DMIS ID codes into your INSTITUION file (#4) using the
> > Load DMIS ID's
> > [XUMF DMIS ID LOAD] option installed by Kernel patch XU*8.0*261. LEDI
> > software
> > uses the following four fields from the INSTITUION file (#4). Check
> > both the HOST and
> > COLLECTION institutions.
> > . Name Field (#.01): The Institution Master File maintains nationally
> > controlled entries
> > for VA and DoD facilities.
> > . Agency code Field (#95): This field indicates to the LEDI III
> > software whether the
> > facility is a VA or DoD facility
> > . VA facilities should be set to: 'VA'
> > . DoD facilities should be set to:
> > 'AF' - AIR FORCE
> > 'ARMY' - ARMY
> > 'N' -- NAVY
> > . Station Number Field (#99): For VA facilities
> > . Identifier (#9999): For DoD facilities indicate the DMIS ID for this
> > facility
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 3, 10:50 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sat, 3 Jan 2009 19:50:09 -0800 (PST)
Local: Sat, Jan 3 2009 10:50 pm
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
I'm a little fuzzy on the specifics of how this is done from page 83:
f. Create a Load List to define and accept lab test results
transmitted by the HOST
facility lab. The Load List MUST contain ALL of the lab tests that are
processed by
the HOST facility lab
They have some examples on page 160 and 169 that don't look the same.
What is TAT on page 83? As in:
• Schedule of testing and TAT
Thanks!
-- IV
On Jan 3, 2:00 pm, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> Please note the section your attempting to implement - COLLECTION
> facility -- VA to DoD Laboratory Implementation Instructions
> This section is used to configure the software to communicate with a DoD
> Laboratory facility. The requirement to load DMIS ID codes is due to the
> use of DMIS ID codes to identify DoD CHCS Laboratory facilities. They
> are used similar to VA station numbers to identify VA facilities.
> The option to load DMIS ID retrieves the DoD entries from the VA Master
> File Server which contains nationally controlled entries for
> institutions from the INSTITUTION file. It tasks a background process to
> update the local site's INSTITUTION file with military medical
> facilities. This process will probably fail due to the situation of the
> VA Master File Server being behind the VA firewall and the use of
> 10.x.x.x addresses which are not accessible from the public internet.
> Additionally, your probably be better off following the setup
> instructions for a commercial reference lab.
> Page 81 - COLLECTION facility -- VA to Commercial Reference Laboratory
> Note that there are specific setup instructions for each of the various
> scenarios. These setup variations affect how and what files/fields are
> configured and how and what information is contained in the files/fields.
> I, Valdes wrote:
> > Hi all, I followed Page 42 of
> >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
> > the gtm [[prompt~|Prompt]] as follows:
> > Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
> > Load DMIS ID's
> > GTM>
> > Doing a ZSHOW "*" has ZSTATUS=""
> > Is there something wrong? -- IV
> > 1. IRM: INSTITUTION file (#4) Setup Instructions
> > Load the DoD DMIS ID codes into your INSTITUION file (#4) using the
> > Load DMIS ID's
> > [XUMF DMIS ID LOAD] option installed by Kernel patch XU*8.0*261. LEDI
> > software
> > uses the following four fields from the INSTITUION file (#4). Check
> > both the HOST and
> > COLLECTION institutions.
> > . Name Field (#.01): The Institution Master File maintains nationally
> > controlled entries
> > for VA and DoD facilities.
> > . Agency code Field (#95): This field indicates to the LEDI III
> > software whether the
> > facility is a VA or DoD facility
> > . VA facilities should be set to: 'VA'
> > . DoD facilities should be set to:
> > 'AF' - AIR FORCE
> > 'ARMY' - ARMY
> > 'N' -- NAVY
> > . Station Number Field (#99): For VA facilities
> > . Identifier (#9999): For DoD facilities indicate the DMIS ID for this
> > facility
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 4, 1:13 am
From: John McCormack <johnm...@ix.netcom.com>
Date: Sun, 04 Jan 2009 00:13:31 -0600
Local: Sun, Jan 4 2009 1:13 am
Subject: Re: [Hardhats] 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
TAT - turn around time
Some tests may need to be tested within a certain period of time. When
the reference lab performs/schedules the test may affect when the test
is collected and/or shipped. If the test is only performed once/week and
the specimen needs to be collected within 24 hours of testing then that
affects when you collect the specimen and when you ship it.
Re: Load list - the LEDI software component of VistA Lab utilizes
existing functionality of the Laboratory package. In this case reference
laboratory test results are processed similar to lab personnel
processing test results from a automated laboratory instrument. The
laboratory usually has a load/work list configured to processes
interfaced lab instrument test results. LEDI uses this existing
functionality to also process reference lab results ("big automated
instrument tin the sky").
The example on page 160 is an illustration of processing the results
from a reference lab after the HL7 messages with the results has been
received.
The example on page 169 is an example of the option used to configure
the load list that's used in the page 160 example.
It's like setting up a test first so that you can then select the test
and order it on a patient. Or creating a clinic and setting up the
appointment schedule so that you can schedule patients into the
available slots for the clinic/day.
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> I'm a little fuzzy on the specifics of how this is done from page 83:
> f. Create a Load List to define and accept lab test results
> transmitted by the HOST
> facility lab. The Load List MUST contain ALL of the lab tests that are
> processed by
> the HOST facility lab
> They have some examples on page 160 and 169 that don't look the same.
> What is TAT on page 83? As in:
> . Schedule of testing and TAT
> Thanks!
> -- IV
> On Jan 3, 2:00 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>> Please note the section your attempting to implement - COLLECTION
>> facility -- VA to DoD Laboratory Implementation Instructions
>> This section is used to configure the software to communicate with a DoD
>> Laboratory facility. The requirement to load DMIS ID codes is due to the
>> use of DMIS ID codes to identify DoD CHCS Laboratory facilities. They
>> are used similar to VA station numbers to identify VA facilities.
>> The option to load DMIS ID retrieves the DoD entries from the VA Master
>> File Server which contains nationally controlled entries for
>> institutions from the INSTITUTION file. It tasks a background process to
>> update the local site's INSTITUTION file with military medical
>> facilities. This process will probably fail due to the situation of the
>> VA Master File Server being behind the VA firewall and the use of
>> 10.x.x.x addresses which are not accessible from the public internet.
>> Additionally, your probably be better off following the setup
>> instructions for a commercial reference lab.
>> Page 81 - COLLECTION facility -- VA to Commercial Reference Laboratory
>> Note that there are specific setup instructions for each of the various
>> scenarios. These setup variations affect how and what files/fields are
>> configured and how and what information is contained in the files/fields.
>> I, Valdes wrote:
>>> Hi all, I followed Page 42 of
>>> 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
>>> the gtm [[prompt~|Prompt]] as follows:
>>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
>>> Load DMIS ID's
>>> GTM>
>>> Doing a ZSHOW "*" has ZSTATUS=""
>>> Is there something wrong? -- IV
>>> 1. IRM: INSTITUTION file (#4) Setup Instructions
>>> Load the DoD DMIS ID codes into your INSTITUION file (#4) using the
>>> Load DMIS ID's
>>> [XUMF DMIS ID LOAD] option installed by Kernel patch XU*8.0*261. LEDI
>>> software
>>> uses the following four fields from the INSTITUION file (#4). Check
>>> both the HOST and
>>> COLLECTION institutions.
>>> . Name Field (#.01): The Institution Master File maintains nationally
>>> controlled entries
>>> for VA and DoD facilities.
>>> . Agency code Field (#95): This field indicates to the LEDI III
>>> software whether the
>>> facility is a VA or DoD facility
>>> . VA facilities should be set to: 'VA'
>>> . DoD facilities should be set to:
>>> 'AF' - AIR FORCE
>>> 'ARMY' - ARMY
>>> 'N' -- NAVY
>>> . Station Number Field (#99): For VA facilities
>>> . Identifier (#9999): For DoD facilities indicate the DMIS ID for this
>>> facility
>>> ------------------------------------------------------------------------
>>> No virus found in this incoming message.
>>> Checked by AVG -http://www.avg.com
>>> Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Jan 4, 10:02 am
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Sun, 04 Jan 2009 10:02:08 -0500
Local: Sun, Jan 4 2009 10:02 am
Subject: Re: [Hardhats] 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
This just gave me a profound appreciation of what folks face when they talk to
doctors! Also, it was good for a chuckle!
On Sunday 04 January 2009, John McCormack wrote:
- Hide quoted text -
- Show quoted text -
> TAT - turn around time
> Some tests may need to be tested within a certain period of time. When
> the reference lab performs/schedules the test may affect when the test
> is collected and/or shipped. If the test is only performed once/week and
> the specimen needs to be collected within 24 hours of testing then that
> affects when you collect the specimen and when you ship it.
> Re: Load list - the LEDI software component of VistA Lab utilizes
> existing functionality of the Laboratory package. In this case reference
> laboratory test results are processed similar to lab personnel
> processing test results from a automated laboratory instrument. The
> laboratory usually has a load/work list configured to processes
> interfaced lab instrument test results. LEDI uses this existing
> functionality to also process reference lab results ("big automated
> instrument tin the sky").
> The example on page 160 is an illustration of processing the results
> from a reference lab after the HL7 messages with the results has been
> received.
> The example on page 169 is an example of the option used to configure
> the load list that's used in the page 160 example.
> It's like setting up a test first so that you can then select the test
> and order it on a patient. Or creating a clinic and setting up the
> appointment schedule so that you can schedule patients into the
> available slots for the clinic/day.
> I, Valdes wrote:
> > I'm a little fuzzy on the specifics of how this is done from page 83:
> > f. Create a Load List to define and accept lab test results
> > transmitted by the HOST
> > facility lab. The Load List MUST contain ALL of the lab tests that are
> > processed by
> > the HOST facility lab
> > They have some examples on page 160 and 169 that don't look the same.
> > What is TAT on page 83? As in:
> > . Schedule of testing and TAT
> > Thanks!
> > -- IV
> > On Jan 3, 2:00 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> >> Please note the section your attempting to implement - COLLECTION
> >> facility -- VA to DoD Laboratory Implementation Instructions
> >> This section is used to configure the software to communicate with a DoD
> >> Laboratory facility. The requirement to load DMIS ID codes is due to the
> >> use of DMIS ID codes to identify DoD CHCS Laboratory facilities. They
> >> are used similar to VA station numbers to identify VA facilities.
> >> The option to load DMIS ID retrieves the DoD entries from the VA Master
> >> File Server which contains nationally controlled entries for
> >> institutions from the INSTITUTION file. It tasks a background process to
> >> update the local site's INSTITUTION file with military medical
> >> facilities. This process will probably fail due to the situation of the
> >> VA Master File Server being behind the VA firewall and the use of
> >> 10.x.x.x addresses which are not accessible from the public internet.
> >> Additionally, your probably be better off following the setup
> >> instructions for a commercial reference lab.
> >> Page 81 - COLLECTION facility -- VA to Commercial Reference Laboratory
> >> Note that there are specific setup instructions for each of the various
> >> scenarios. These setup variations affect how and what files/fields are
> >> configured and how and what information is contained in the
> >> files/fields.
> >> I, Valdes wrote:
> >>> Hi all, I followed Page 42 of
> >>> 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
> >>> the gtm [[prompt~|Prompt]] as follows:
> >>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
> >>> Load DMIS ID's
> >>> GTM>
> >>> Doing a ZSHOW "*" has ZSTATUS=""
> >>> Is there something wrong? -- IV
> >>> 1. IRM: INSTITUTION file (#4) Setup Instructions
> >>> Load the DoD DMIS ID codes into your INSTITUION file (#4) using the
> >>> Load DMIS ID's
> >>> [XUMF DMIS ID LOAD] option installed by Kernel patch XU*8.0*261. LEDI
> >>> software
> >>> uses the following four fields from the INSTITUION file (#4). Check
> >>> both the HOST and
> >>> COLLECTION institutions.
> >>> . Name Field (#.01): The Institution Master File maintains nationally
> >>> controlled entries
> >>> for VA and DoD facilities.
> >>> . Agency code Field (#95): This field indicates to the LEDI III
> >>> software whether the
> >>> facility is a VA or DoD facility
> >>> . VA facilities should be set to: 'VA'
> >>> . DoD facilities should be set to:
> >>> 'AF' - AIR FORCE
> >>> 'ARMY' - ARMY
> >>> 'N' -- NAVY
> >>> . Station Number Field (#99): For VA facilities
> >>> . Identifier (#9999): For DoD facilities indicate the DMIS ID for this
> >>> facility
> >>> -----------------------------------------------------------------------
> >>>-
> >>> No virus found in this incoming message.
> >>> Checked by AVG -http://www.avg.com
> >>> Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date:
> >>> 1/2/2009 1:10 PM
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG - http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009
> > 1:10 PM
--
Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 4, 10:10 am
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sun, 4 Jan 2009 07:10:09 -0800 (PST)
Local: Sun, Jan 4 2009 10:10 am
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
Excellent. Is there an example somewhere on the specifics of creating
a Load list? I have the commercial lab paper check off list of tests
in front of me and it is about 40 tests. Examples are: 500372 Basic
metabolic profile (Chem 7 CA) Red top tube, and 503053 ICAdmit
(Intracare Admit panel) which consists of CMP (complete metabolic
panel probably), CBC, RPR, TSH and Free T4 collected in a Red top and
Lavender top. I am about to request of the lab all of the page 83 1c
items. Is the 503053 test number and the rest something that VistA
will accept and can transmit to their lab without code modification?
-- IV
On Jan 4, 12:13 am, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> TAT - turn around time
> Some tests may need to be tested within a certain period of time. When
> the reference lab performs/schedules the test may affect when the test
> is collected and/or shipped. If the test is only performed once/week and
> the specimen needs to be collected within 24 hours of testing then that
> affects when you collect the specimen and when you ship it.
> Re: Load list - the LEDI software component of VistA Lab utilizes
> existing functionality of the Laboratory package. In this case reference
> laboratory test results are processed similar to lab personnel
> processing test results from a automated laboratory instrument. The
> laboratory usually has a load/work list configured to processes
> interfaced lab instrument test results. LEDI uses this existing
> functionality to also process reference lab results ("big automated
> instrument tin the sky").
> The example on page 160 is an illustration of processing the results
> from a reference lab after the HL7 messages with the results has been
> received.
> The example on page 169 is an example of the option used to configure
> the load list that's used in the page 160 example.
> It's like setting up a test first so that you can then select the test
> and order it on a patient. Or creating a clinic and setting up the
> appointment schedule so that you can schedule patients into the
> available slots for the clinic/day.
> I, Valdes wrote:
> > I'm a little fuzzy on the specifics of how this is done from page 83:
> > f. Create a Load List to define and accept lab test results
> > transmitted by the HOST
> > facility lab. The Load List MUST contain ALL of the lab tests that are
> > processed by
> > the HOST facility lab
> > They have some examples on page 160 and 169 that don't look the same.
> > What is TAT on page 83? As in:
> > . Schedule of testing and TAT
> > Thanks!
> > -- IV
> > On Jan 3, 2:00 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> >> Please note the section your attempting to implement - COLLECTION
> >> facility -- VA to DoD Laboratory Implementation Instructions
> >> This section is used to configure the software to communicate with a DoD
> >> Laboratory facility. The requirement to load DMIS ID codes is due to the
> >> use of DMIS ID codes to identify DoD CHCS Laboratory facilities. They
> >> are used similar to VA station numbers to identify VA facilities.
> >> The option to load DMIS ID retrieves the DoD entries from the VA Master
> >> File Server which contains nationally controlled entries for
> >> institutions from the INSTITUTION file. It tasks a background process to
> >> update the local site's INSTITUTION file with military medical
> >> facilities. This process will probably fail due to the situation of the
> >> VA Master File Server being behind the VA firewall and the use of
> >> 10.x.x.x addresses which are not accessible from the public internet.
> >> Additionally, your probably be better off following the setup
> >> instructions for a commercial reference lab.
> >> Page 81 - COLLECTION facility -- VA to Commercial Reference Laboratory
> >> Note that there are specific setup instructions for each of the various
> >> scenarios. These setup variations affect how and what files/fields are
> >> configured and how and what information is contained in the files/fields.
> >> I, Valdes wrote:
> >>> Hi all, I followed Page 42 of
> >>>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
> >>> the gtm [[prompt~|Prompt]] as follows:
> >>> Select OPTION NAME: XUMF DMIS ID LOAD Load DMIS ID's
> >>> Load DMIS ID's
> >>> GTM>
> >>> Doing a ZSHOW "*" has ZSTATUS=""
> >>> Is there something wrong? -- IV
> >>> 1. IRM: INSTITUTION file (#4) Setup Instructions
> >>> Load the DoD DMIS ID codes into your INSTITUION file (#4) using the
> >>> Load DMIS ID's
> >>> [XUMF DMIS ID LOAD] option installed by Kernel patch XU*8.0*261. LEDI
> >>> software
> >>> uses the following four fields from the INSTITUION file (#4). Check
> >>> both the HOST and
> >>> COLLECTION institutions.
> >>> . Name Field (#.01): The Institution Master File maintains nationally
> >>> controlled entries
> >>> for VA and DoD facilities.
> >>> . Agency code Field (#95): This field indicates to the LEDI III
> >>> software whether the
> >>> facility is a VA or DoD facility
> >>> . VA facilities should be set to: 'VA'
> >>> . DoD facilities should be set to:
> >>> 'AF' - AIR FORCE
> >>> 'ARMY' - ARMY
> >>> 'N' -- NAVY
> >>> . Station Number Field (#99): For VA facilities
> >>> . Identifier (#9999): For DoD facilities indicate the DMIS ID for this
> >>> facility
> >>> ------------------------------------------------------------------------
> >>> No virus found in this incoming message.
> >>> Checked by AVG -http://www.avg.com
> >>> Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.2/1872 - Release Date: 1/2/2009 1:10 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 4, 10:45 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Sun, 04 Jan 2009 21:45:19 -0600
Local: Sun, Jan 4 2009 10:45 pm
Subject: Re: [Hardhats] 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
I'm not sure I follow the business setup.
From your description I'm taking away that this is a hospital setting
using a manual system for ward and provider order entry and the
laboratory has a separate lab-centric system.
1. What role are you attempting to use VistA Lab to address?
2. VistA Lab is part of an integrated system. Do you want VistA Lab to
handle orders and display results?
This would require that the general VistA package to be implemented,
at minimum, PIMS (Patient Information Management System) -
inpatient/outpatient, patient registration.
3. Are you implementing the general VistA system?
Before any interface to VistA Lab can be implemented the general VistA
Lab package would require [[configuration~|Configuration]] and implementation. If you just
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
order exists and accepts and stores the results as ancillary testing,
i.e. laboratory testing performed outside the clinical lab.
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> John, Nancy, Our current nearly all paper lab works like this:
> 1) Doctor orders lab on paper in chart. Order is taken off by putting
> a pre-printed patient name, patient id number, age, dob label onto
> form containing about 40 check offs for labs desired. Nurse checks off
> which lab is ordered then puts the sheet into the binder with others
> for ward collect. This form comes with 6 small sticky labels with a 6
> digit unique requisition number from the lab are pre-stocked in the
> hospital.
> 2) Phlebotomist arrives at 6 am and 3pm every day. Collects form in
> aforesaid 1) above, takes blood from patients, peels and sticks 6
> digit unique requisition number and puts it onto the specimen
> container (tube, etc) just drawn.
> 3) Lab personnel carries specimens and forms like the form in 1) to
> the lab. The patients name, id number, date of birth, requisition
> number, pre-generated 7 digit specimen id that maps to requisition
> number, and test desired are entered into the lab computer. A sticky
> label with patient name, bar code and specimen id is generated stuck
> to the specimen container and placed in the instrument rack for
> testing.
> 4) Results are printed and faxed to the hospital. Nurses put reports
> into charts.
> The current lab system is capable of sending us HL7 version 2.2
> messages containing reports. It is unknown whether they can accept HL7
> orders directly from our system.
> Given all this, what do you think is the best way to proceed in
> getting this working with VistA?
> -- IV
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.1/1870 - Release Date: 12/31/2008 8:44 AM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 4, 11:06 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Sun, 4 Jan 2009 20:06:55 -0800 (PST)
Local: Sun, Jan 4 2009 11:06 pm
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
On Jan 4, 9:45 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> I'm not sure I follow the business setup.
> From your description I'm taking away that this is a hospital setting
> using a manual system for ward and provider order entry and the
> laboratory has a separate lab-centric system.
Correct.
> 1. What role are you attempting to use VistA Lab to address?
If possible, I would like to make lab ordering and results obtaining
completely paperless. Failing that, electronic results reporting only
with the paper ordering continuing until we can get it all paperless.
> 2. VistA Lab is part of an integrated system. Do you want VistA Lab to
> handle orders and display results?
> This would require that the general VistA package to be implemented,
> at minimum, PIMS (Patient Information Management System) -
> inpatient/outpatient, patient registration.
This is operational now.
> 3. Are you implementing the general VistA system?
Yes.
> Before any interface to VistA Lab can be implemented the general VistA
> Lab package would require [[configuration~|Configuration]] and implementation. If you just
> 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
> order exists and accepts and stores the results as ancillary testing,
> i.e. laboratory testing performed outside the clinical lab.
Currently the lab can send us results via a HL7 2.2 message inside of
a text file which can be sftp'ed or some such over. However, there
would not be a corresponding order in the computer at this point. This
would be beneficial. Is there a good setup document for the POC
interface?
-- IV
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 4, 11:51 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Sun, 04 Jan 2009 22:51:34 -0600
Local: Sun, Jan 4 2009 11:51 pm
Subject: Re: [Hardhats] 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
> Currently the lab can send us results via a HL7 2.2 message inside of
> a text file which can be sftp'ed or some such over. However, there
> would not be a corresponding order in the computer at this point. This
> would be beneficial. Is there a good setup document for the POC
> interface?
Lab POC documentation: http://www.va.gov/vdl/[[application~|Application]].asp?appid=149
Note that the Lab POC works on the business rule that no existing lab
order exists in VistA Lab. It always creates a lab order, accession and
associates the results with the order/accession created.
VistA HL package is not designed to handle FTPing of files. It's a
system that supports messaging which involves message transmission,
receipt and acknowledgment. Using FTP to wrap messages in a file makes
it very difficult to handle exceptions and/or errors in message
transmission, receipt or processing which could lead to dropped results
and/or other patient safety situations. You may need to investigate the
possibly of a interface engine to act as a front-end between the two
systems.
> If possible, I would like to make lab ordering and results obtaining
> completely paperless. Failing that, electronic results reporting only
> with the paper ordering continuing until we can get it all paperless.
Paper ordering and electronic ordering will change the [[business rules~|Business Rules]]
and determine the type of interface you use.
If you go with electronic ordering then you may need to use LEDI minus
the ordering part if the orders on the external lab system are placed
manually. The external lab system would need to send the VistA Lab
accession UID as the "placer order number" in any HL7 messaging as VistA
is playing the role of placer of the order. The external lab system is
playing the role of "filler" and assigns a filler order number for
processing within their system.
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> On Jan 4, 9:45 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>> I'm not sure I follow the business setup.
>> From your description I'm taking away that this is a hospital setting
>> using a manual system for ward and provider order entry and the
>> laboratory has a separate lab-centric system.
> Correct.
>> 1. What role are you attempting to use VistA Lab to address?
> If possible, I would like to make lab ordering and results obtaining
> completely paperless. Failing that, electronic results reporting only
> with the paper ordering continuing until we can get it all paperless.
>> 2. VistA Lab is part of an integrated system. Do you want VistA Lab to
>> handle orders and display results?
>> This would require that the general VistA package to be implemented,
>> at minimum, PIMS (Patient Information Management System) -
>> inpatient/outpatient, patient registration.
> This is operational now.
>> 3. Are you implementing the general VistA system?
> Yes.
>> Before any interface to VistA Lab can be implemented the general VistA
>> Lab package would require [[configuration~|Configuration]] and implementation. If you just
>> 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
>> order exists and accepts and stores the results as ancillary testing,
>> i.e. laboratory testing performed outside the clinical lab.
> Currently the lab can send us results via a HL7 2.2 message inside of
> a text file which can be sftp'ed or some such over. However, there
> would not be a corresponding order in the computer at this point. This
> would be beneficial. Is there a good setup document for the POC
> interface?
> -- IV
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.2/1874 - Release Date: 1/4/2009 4:32 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 5, 4:47 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Mon, 5 Jan 2009 13:47:06 -0800 (PST)
Local: Mon, Jan 5 2009 4:47 pm
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
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
VistA [[configuration~|Configuration]]. Will it mess something up for it to be HL7 2.2?
Am I just gonna have to find out? -- IV
On Jan 4, 10:51 pm, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> > Currently the lab can send us results via a HL7 2.2 message inside of
> > a text file which can be sftp'ed or some such over. However, there
> > would not be a corresponding order in the computer at this point. This
> > would be beneficial. Is there a good setup document for the POC
> > interface?
> Lab POC documentation:http://www.va.gov/vdl/[[application~|Application]].asp?appid=149
> Note that the Lab POC works on the business rule that no existing lab
> order exists in VistA Lab. It always creates a lab order, accession and
> associates the results with the order/accession created.
> VistA HL package is not designed to handle FTPing of files. It's a
> system that supports messaging which involves message transmission,
> receipt and acknowledgment. Using FTP to wrap messages in a file makes
> it very difficult to handle exceptions and/or errors in message
> transmission, receipt or processing which could lead to dropped results
> and/or other patient safety situations. You may need to investigate the
> possibly of a interface engine to act as a front-end between the two
> systems.
> > If possible, I would like to make lab ordering and results obtaining
> > completely paperless. Failing that, electronic results reporting only
> > with the paper ordering continuing until we can get it all paperless.
> Paper ordering and electronic ordering will change the [[business rules~|Business Rules]]
> and determine the type of interface you use.
> If you go with electronic ordering then you may need to use LEDI minus
> the ordering part if the orders on the external lab system are placed
> manually. The external lab system would need to send the VistA Lab
> accession UID as the "placer order number" in any HL7 messaging as VistA
> is playing the role of placer of the order. The external lab system is
> playing the role of "filler" and assigns a filler order number for
> processing within their system.
> I, Valdes wrote:
> > On Jan 4, 9:45 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> >> I'm not sure I follow the business setup.
> >> From your description I'm taking away that this is a hospital setting
> >> using a manual system for ward and provider order entry and the
> >> laboratory has a separate lab-centric system.
> > Correct.
> >> 1. What role are you attempting to use VistA Lab to address?
> > If possible, I would like to make lab ordering and results obtaining
> > completely paperless. Failing that, electronic results reporting only
> > with the paper ordering continuing until we can get it all paperless.
> >> 2. VistA Lab is part of an integrated system. Do you want VistA Lab to
> >> handle orders and display results?
> >> This would require that the general VistA package to be implemented,
> >> at minimum, PIMS (Patient Information Management System) -
> >> inpatient/outpatient, patient registration.
> > This is operational now.
> >> 3. Are you implementing the general VistA system?
> > Yes.
> >> Before any interface to VistA Lab can be implemented the general VistA
> >> Lab package would require [[configuration~|Configuration]] and implementation. If you just
> >> 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
> >> order exists and accepts and stores the results as ancillary testing,
> >> i.e. laboratory testing performed outside the clinical lab.
> > Currently the lab can send us results via a HL7 2.2 message inside of
> > a text file which can be sftp'ed or some such over. However, there
> > would not be a corresponding order in the computer at this point. This
> > would be beneficial. Is there a good setup document for the POC
> > interface?
> > -- IV
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.2/1874 - Release Date: 1/4/2009 4:32 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Greg Woodhouse
View profile
More options Jan 5, 5:32 pm
From: "Greg Woodhouse" <gregory.woodho...@gmail.com>
Date: Mon, 5 Jan 2009 14:32:13 -0800
Local: Mon, Jan 5 2009 5:32 pm
Subject: Re: [Hardhats] 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
That shouldn't be a problem. The main difference is that in newer versions,
additional messages and trigger events are available. VistA HL7 itself
doesn't care much about the content of the messages (with certain obvious
exceptions, such as the MSH and MSA segments). If it can parse these
segments (along with any batch headers, if you use them) you should be okay.
- Hide quoted text -
- Show quoted text -
On Mon, Jan 5, 2009 at 1:47 PM, I, Valdes <ival...@hal-pc.org> wrote:
> 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
> VistA [[configuration~|Configuration]]. Will it mess something up for it to be HL7 2.2?
> Am I just gonna have to find out? -- IV
> On Jan 4, 10:51 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> > > Currently the lab can send us results via a HL7 2.2 message inside of
> > > a text file which can be sftp'ed or some such over. However, there
> > > would not be a corresponding order in the computer at this point. This
> > > would be beneficial. Is there a good setup document for the POC
> > > interface?
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 5, 6:24 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Mon, 5 Jan 2009 15:24:50 -0800 (PST)
Local: Mon, Jan 5 2009 6:24 pm
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
Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~|Prompt]].
ZSTATUS shows nothing "". -- IV
On Jan 4, 10:51 pm, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> > Currently the lab can send us results via a HL7 2.2 message inside of
> > a text file which can be sftp'ed or some such over. However, there
> > would not be a corresponding order in the computer at this point. This
> > would be beneficial. Is there a good setup document for the POC
> > interface?
> Lab POC documentation:http://www.va.gov/vdl/[[application~|Application]].asp?appid=149
> Note that the Lab POC works on the business rule that no existing lab
> order exists in VistA Lab. It always creates a lab order, accession and
> associates the results with the order/accession created.
> VistA HL package is not designed to handle FTPing of files. It's a
> system that supports messaging which involves message transmission,
> receipt and acknowledgment. Using FTP to wrap messages in a file makes
> it very difficult to handle exceptions and/or errors in message
> transmission, receipt or processing which could lead to dropped results
> and/or other patient safety situations. You may need to investigate the
> possibly of a interface engine to act as a front-end between the two
> systems.
> > If possible, I would like to make lab ordering and results obtaining
> > completely paperless. Failing that, electronic results reporting only
> > with the paper ordering continuing until we can get it all paperless.
> Paper ordering and electronic ordering will change the [[business rules~|Business Rules]]
> and determine the type of interface you use.
> If you go with electronic ordering then you may need to use LEDI minus
> the ordering part if the orders on the external lab system are placed
> manually. The external lab system would need to send the VistA Lab
> accession UID as the "placer order number" in any HL7 messaging as VistA
> is playing the role of placer of the order. The external lab system is
> playing the role of "filler" and assigns a filler order number for
> processing within their system.
> I, Valdes wrote:
> > On Jan 4, 9:45 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> >> I'm not sure I follow the business setup.
> >> From your description I'm taking away that this is a hospital setting
> >> using a manual system for ward and provider order entry and the
> >> laboratory has a separate lab-centric system.
> > Correct.
> >> 1. What role are you attempting to use VistA Lab to address?
> > If possible, I would like to make lab ordering and results obtaining
> > completely paperless. Failing that, electronic results reporting only
> > with the paper ordering continuing until we can get it all paperless.
> >> 2. VistA Lab is part of an integrated system. Do you want VistA Lab to
> >> handle orders and display results?
> >> This would require that the general VistA package to be implemented,
> >> at minimum, PIMS (Patient Information Management System) -
> >> inpatient/outpatient, patient registration.
> > This is operational now.
> >> 3. Are you implementing the general VistA system?
> > Yes.
> >> Before any interface to VistA Lab can be implemented the general VistA
> >> Lab package would require [[Configuration~configuration]] and implementation. If you just
> >> 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
> >> order exists and accepts and stores the results as ancillary testing,
> >> i.e. laboratory testing performed outside the clinical lab.
> > Currently the lab can send us results via a HL7 2.2 message inside of
> > a text file which can be sftp'ed or some such over. However, there
> > would not be a corresponding order in the computer at this point. This
> > would be beneficial. Is there a good setup document for the POC
> > interface?
> > -- IV
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG -http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.2/1874 - Release Date: 1/4/2009 4:32 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 5, 8:56 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Mon, 05 Jan 2009 19:56:39 -0600
Local: Mon, Jan 5 2009 8:56 pm
Subject: Re: [Hardhats] 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
RTFM - the documentation explicitly indicates it should be tasked as a
scheduled option (task) in TaskMan. It's designed to run non-interactive
and therefore has no inputs/outputs other than those documented in the
option.
Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option
Lab messaging will now check that Lab Messaging Nightly Cleanup [LA7TASK
NIGHTY] option is scheduled in TaskMan. If not scheduled then an alert
notifying members of mail group
LAB MESSAGING will be generated. The alert message will read "Lab
Messaging- Option LA7TASK NIGHTY is not scheduled in TaskMan". Note:
Documentation regarding tasking can be found in the VistA Laboratory
LEDI User Guide and on-line via the DESCRIPTION field of the OPTION file
(#19) for this entry.
Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option
Lab messaging has been modified and will now check that Lab Messaging
Nightly Cleanup [LA7TASK NIGHTY] option is scheduled in TaskMan. If this
option is not scheduled then an
alert message notifying members of the LAB MESSAGING mail group is
generated. The alert message will read "Lab Messaging- Option LA7TASK
NIGHTY is not scheduled in
TaskMan." The Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option is
tasked to check the integrity of LA7 MESSAGE QUEUE file (#62.49) and
purge messages that are
eligible for purging. It also purges the following files related to LEDI
- SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85), and LAB
PENDING ORDERS ENTRY (#69.6).
The Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option should be
tasked daily, preferably during period when activity in the Lab
Messaging (i.e. Universal Interface, LEDI)
package is at a minimum. Prior to the purge of LA7 MESSAGE QUEUE file
(#62.49), an integrity check is performed. The integrity check can be
run with the following switches.
NOTE: Documentation regarding tasking can be found in the VistA
Laboratory LEDI User Guide and on-line via the DESCRIPTION field of the
OPTION file (#19) for this entry.
Any outputs are available via this option Print Lab Messaging Integrity
Check Report
If you want to initiate via an interactive option then use FIC Lab
Messaging File Integrity Checker
Select Lab Universal Interface Menu Option: ?
2 Print Lab Universal Interface Log
Display Lab Universal Interface Message
Download to Universal Interface
Start/Stop Auto Download Background Job
PCS Lab Point of Care Setup
FIC Lab Messaging File Integrity Checker
PIC Print Lab Messaging Integrity Check Report
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~|Prompt]].
> ZSTATUS shows nothing "". -- IV
> On Jan 4, 10:51 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>>> Currently the lab can send us results via a HL7 2.2 message inside of
>>> a text file which can be sftp'ed or some such over. However, there
>>> would not be a corresponding order in the computer at this point. This
>>> would be beneficial. Is there a good setup document for the POC
>>> interface?
>> Lab POC documentation:http://www.va.gov/vdl/[[application~|Application]].asp?appid=149
>> Note that the Lab POC works on the business rule that no existing lab
>> order exists in VistA Lab. It always creates a lab order, accession and
>> associates the results with the order/accession created.
>> VistA HL package is not designed to handle FTPing of files. It's a
>> system that supports messaging which involves message transmission,
>> receipt and acknowledgment. Using FTP to wrap messages in a file makes
>> it very difficult to handle exceptions and/or errors in message
>> transmission, receipt or processing which could lead to dropped results
>> and/or other patient safety situations. You may need to investigate the
>> possibly of a interface engine to act as a front-end between the two
>> systems.
>>> If possible, I would like to make lab ordering and results obtaining
>>> completely paperless. Failing that, electronic results reporting only
>>> with the paper ordering continuing until we can get it all paperless.
>> Paper ordering and electronic ordering will change the [[business rules~|Business Rules]]
>> and determine the type of interface you use.
>> If you go with electronic ordering then you may need to use LEDI minus
>> the ordering part if the orders on the external lab system are placed
>> manually. The external lab system would need to send the VistA Lab
>> accession UID as the "placer order number" in any HL7 messaging as VistA
>> is playing the role of placer of the order. The external lab system is
>> playing the role of "filler" and assigns a filler order number for
>> processing within their system.
>> I, Valdes wrote:
>>> On Jan 4, 9:45 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>>>> I'm not sure I follow the business setup.
>>>> From your description I'm taking away that this is a hospital setting
>>>> using a manual system for ward and provider order entry and the
>>>> laboratory has a separate lab-centric system.
>>> Correct.
>>>> 1. What role are you attempting to use VistA Lab to address?
>>> If possible, I would like to make lab ordering and results obtaining
>>> completely paperless. Failing that, electronic results reporting only
>>> with the paper ordering continuing until we can get it all paperless.
>>>> 2. VistA Lab is part of an integrated system. Do you want VistA Lab to
>>>> handle orders and display results?
>>>> This would require that the general VistA package to be implemented,
>>>> at minimum, PIMS (Patient Information Management System) -
>>>> inpatient/outpatient, patient registration.
>>> This is operational now.
>>>> 3. Are you implementing the general VistA system?
>>> Yes.
>>>> Before any interface to VistA Lab can be implemented the general VistA
>>>> Lab package would require [[configuration~|Configuration]] and implementation. If you just
>>>> 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
>>>> order exists and accepts and stores the results as ancillary testing,
>>>> i.e. laboratory testing performed outside the clinical lab.
>>> Currently the lab can send us results via a HL7 2.2 message inside of
>>> a text file which can be sftp'ed or some such over. However, there
>>> would not be a corresponding order in the computer at this point. This
>>> would be beneficial. Is there a good setup document for the POC
>>> interface?
>>> -- IV
>>> ------------------------------------------------------------------------
>>> No virus found in this incoming message.
>>> Checked by AVG -http://www.avg.com
>>> Version: 8.0.176 / Virus Database: 270.10.2/1874 - Release Date: 1/4/2009 4:32 PM
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.3/1877 - Release Date: 1/5/2009 7:20 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 5, 9:05 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Mon, 05 Jan 2009 20:05:22 -0600
Local: Mon, Jan 5 2009 9:05 pm
Subject: Re: [Hardhats] 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
You'll need to change the HL version number of the protocols otherwise
the HL package will reject the messages.
The sending/receiving [[application~|Application]] names and facilities are significant
along with the message type, event type, version number and processing
id. The sending system's message id should be unique. For the LEDI and
POC interfaces enhanced mode acknowledgments are implemented.
- Hide quoted text -
- Show quoted text -
Greg Woodhouse wrote:
> That shouldn't be a problem. The main difference is that in newer
> versions, additional messages and trigger events are available. VistA
> HL7 itself doesn't care much about the content of the messages (with
> certain obvious exceptions, such as the MSH and MSA segments). If it
> can parse these segments (along with any batch headers, if you use
> them) you should be okay.
> On Mon, Jan 5, 2009 at 1:47 PM, I, Valdes <ival...@hal-pc.org
> <mailto:ival...@hal-pc.org>> wrote:
> 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
> VistA [[configuration~|Configuration]]. Will it mess something up for it to be HL7 2.2?
> Am I just gonna have to find out? -- IV
> On Jan 4, 10:51 pm, John McCormack <johnm...@ix.netcom.com
> <mailto:johnm...@ix.netcom.com>> wrote:
> > > Currently the lab can send us results via a HL7 2.2 message
> inside of
> > > a text file which can be sftp'ed or some such over. However, there
> > > would not be a corresponding order in the computer at this
> point. This
> > > would be beneficial. Is there a good setup document for the POC
> > > interface?
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.3/1877 - Release Date: 1/5/2009 7:20 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 5, 10:14 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Mon, 5 Jan 2009 19:14:50 -0800 (PST)
Local: Mon, Jan 5 2009 10:14 pm
Subject: Re: [Hardhats] 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
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~|Prompt]] (or equivalent)? Are
they starting it from a place I am unaware of? Guess it is time to
learn how to start something in taskman...
Select OPTION NAME: LA7TASK NIGHTY <ENTER> Lab Messaging Nightly
Cleanup
ANOTHER ONE: <ENTER>
STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~|Record]] number
(IEN),
no Computed Fields
DISPLAY AUDIT TRAIL? No//<ENTER> NO
NAME: LA7TASK NIGHTY MENU TEXT: Lab Messaging Nightly
Cleanup
TYPE: run routine CREATOR: LABCREATOR, ONE
PACKAGE: AUTOMATED LAB INSTRUMENTS
DESCRIPTION: This is a tasked option to check integrity of LA7 MESSAGE
QUEUE file (#62.49) and purge messages that are eligible for
purging. It also purges the following files related to
LEDI - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT file
(#62.85) and LAB PENDING ORDERS ENTRY (#69.6)
- Hide quoted text -
- Show quoted text -
John McCormack wrote:
> RTFM - the documentation explicitly indicates it should be tasked as a
> scheduled option (task) in TaskMan. It's designed to run non-interactive
> and therefore has no inputs/outputs other than those documented in the
> option.
> Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option
> Lab messaging will now check that Lab Messaging Nightly Cleanup [LA7TASK
> NIGHTY] option is scheduled in TaskMan. If not scheduled then an alert
> notifying members of mail group
> LAB MESSAGING will be generated. The alert message will read "Lab
> Messaging- Option LA7TASK NIGHTY is not scheduled in TaskMan". Note:
> Documentation regarding tasking can be found in the VistA Laboratory
> LEDI User Guide and on-line via the DESCRIPTION field of the OPTION file
> (#19) for this entry.
> Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option
> Lab messaging has been modified and will now check that Lab Messaging
> Nightly Cleanup [LA7TASK NIGHTY] option is scheduled in TaskMan. If this
> option is not scheduled then an
> alert message notifying members of the LAB MESSAGING mail group is
> generated. The alert message will read "Lab Messaging- Option LA7TASK
> NIGHTY is not scheduled in
> TaskMan." The Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option is
> tasked to check the integrity of LA7 MESSAGE QUEUE file (#62.49) and
> purge messages that are
> eligible for purging. It also purges the following files related to LEDI
> - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85), and LAB
> PENDING ORDERS ENTRY (#69.6).
> The Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option should be
> tasked daily, preferably during period when activity in the Lab
> Messaging (i.e. Universal Interface, LEDI)
> package is at a minimum. Prior to the purge of LA7 MESSAGE QUEUE file
> (#62.49), an integrity check is performed. The integrity check can be
> run with the following switches.
> NOTE: Documentation regarding tasking can be found in the VistA
> Laboratory LEDI User Guide and on-line via the DESCRIPTION field of the
> OPTION file (#19) for this entry.
> Any outputs are available via this option Print Lab Messaging Integrity
> Check Report
> If you want to initiate via an interactive option then use FIC Lab
> Messaging File Integrity Checker
> Select Lab Universal Interface Menu Option: ?
> 2 Print Lab Universal Interface Log
> Display Lab Universal Interface Message
> Download to Universal Interface
> Start/Stop Auto Download Background Job
> PCS Lab Point of Care Setup
> FIC Lab Messaging File Integrity Checker
> PIC Print Lab Messaging Integrity Check Report
> I, Valdes wrote:
> > Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~|Prompt]].
> > ZSTATUS shows nothing "". -- IV
> > On Jan 4, 10:51 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> >>> Currently the lab can send us results via a HL7 2.2 message inside of
> >>> a text file which can be sftp'ed or some such over. However, there
> >>> would not be a corresponding order in the computer at this point. This
> >>> would be beneficial. Is there a good setup document for the POC
> >>> interface?
> >> Lab POC documentation:http://www.va.gov/vdl/[[application~|Application]].asp?appid=149
> >> Note that the Lab POC works on the business rule that no existing lab
> >> order exists in VistA Lab. It always creates a lab order, accession and
> >> associates the results with the order/accession created.
> >> VistA HL package is not designed to handle FTPing of files. It's a
> >> system that supports messaging which involves message transmission,
> >> receipt and acknowledgment. Using FTP to wrap messages in a file makes
> >> it very difficult to handle exceptions and/or errors in message
> >> transmission, receipt or processing which could lead to dropped results
> >> and/or other patient safety situations. You may need to investigate the
> >> possibly of a interface engine to act as a front-end between the two
> >> systems.
> >>> If possible, I would like to make lab ordering and results obtaining
> >>> completely paperless. Failing that, electronic results reporting only
> >>> with the paper ordering continuing until we can get it all paperless.
> >> Paper ordering and electronic ordering will change the [[business rules~|Business Rules]]
> >> and determine the type of interface you use.
> >> If you go with electronic ordering then you may need to use LEDI minus
> >> the ordering part if the orders on the external lab system are placed
> >> manually. The external lab system would need to send the VistA Lab
> >> accession UID as the "placer order number" in any HL7 messaging as VistA
> >> is playing the role of placer of the order. The external lab system is
> >> playing the role of "filler" and assigns a filler order number for
> >> processing within their system.
> >> I, Valdes wrote:
> >>> On Jan 4, 9:45 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> >>>> I'm not sure I follow the business setup.
> >>>> From your description I'm taking away that this is a hospital setting
> >>>> using a manual system for ward and provider order entry and the
> >>>> laboratory has a separate lab-centric system.
> >>> Correct.
> >>>> 1. What role are you attempting to use VistA Lab to address?
> >>> If possible, I would like to make lab ordering and results obtaining
> >>> completely paperless. Failing that, electronic results reporting only
> >>> with the paper ordering continuing until we can get it all paperless.
> >>>> 2. VistA Lab is part of an integrated system. Do you want VistA Lab to
> >>>> handle orders and display results?
> >>>> This would require that the general VistA package to be implemented,
> >>>> at minimum, PIMS (Patient Information Management System) -
> >>>> inpatient/outpatient, patient registration.
> >>> This is operational now.
> >>>> 3. Are you implementing the general VistA system?
> >>> Yes.
> >>>> Before any interface to VistA Lab can be implemented the general VistA
> >>>> Lab package would require [[configuration~|Configuration]] and implementation. If you just
> >>>> 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
> >>>> order exists and accepts and stores the results as ancillary testing,
> >>>> i.e. laboratory testing performed outside the clinical lab.
> >>> Currently the lab can send us results via a HL7 2.2 message inside of
> >>> a text file which can be sftp'ed or some such over. However, there
> >>> would not be a corresponding order in the computer at this point. This
> >>> would be beneficial. Is there a good setup document for the POC
> >>> interface?
> >>> -- IV
> >>> ------------------------------------------------------------------------
> >>> No virus found in this incoming message.
> >>> Checked by AVG -http://www.avg.com
> >>> Version: 8.0.176 / Virus Database: 270.10.2/1874 - Release Date: 1/4/2009 4:32 PM
> > ------------------------------------------------------------------------
> > No virus found in this incoming message.
> > Checked by AVG - http://www.avg.com
> > Version: 8.0.176 / Virus Database: 270.10.3/1877 - Release Date: 1/5/2009 7:20 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 6, 12:09 am
From: John McCormack <johnm...@ix.netcom.com>
Date: Mon, 05 Jan 2009 23:09:08 -0600
Local: Tues, Jan 6 2009 12:09 am
Subject: Re: [Hardhats] 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
The example is showing you how to schedule it in TaskMan using the
option Schedule/Unschedule Options.
Select Systems Manager Menu Option: Taskman Management
Schedule/Unschedule Options
One-time Option Queue
Taskman Management Utilities ...
List Tasks
Dequeue Tasks
Requeue Tasks
Delete Tasks
Print Options that are Scheduled to run
Cleanup Task List
Print Options Recommended for Queueing
On the second screen of the ScreenMan form when scheduling you can
define the value for the variables as documented in the option description.
Select OPTION NAME: LA7TASK NIGHTY Lab Messaging Nightly Cleanup
Another one:
Standard Captioned Output? Yes// N (No)
First Print FIELD: [CAPTIONED
Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
[[Record~|Record]] Number
(IEN)
Heading (S/C): OPTION List//
DEVICE: HOME// 0;132;9999 TELNET
OPTION
List
JAN 5,2009@23:05 PAGE 1
------------------------------------------------------------------------------------------------------------------------------------
NUMBER: 8068 NAME: LA7TASK
NIGHTY MENU TEXT: Lab Messaging Nightly Cleanup
TYPE: run routine CREATOR:
USER,PATCH PACKAGE: AUTOMATED LAB INSTRUMENTS
DESCRIPTION: This is a tasked option to check integrity of LA7
MESSAGE QUEUE file (#62.49) and purge messages that are eligible
for purging. It also purges the following files related to LEDI -
SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85) and LAB
PENDING ORDERS ENTRY (#69.6)
This option should be tasked daily, preferably during period when
activity in the Lab Messaging (i.e. Universal Interface, LEDI)
package is at a minimum.
Prior to the purge of LA7 MESSAGE QUEUE file (#62.49), an integrity
check is performed. The integrity check can be run with a
couple of switches.
LA7FIX = 0 - do not fix errors
1 - do fix errors
LA7LOG = 0 - do not log errors in XTMP global.
1 - do log errors in XTMP global
LA7ION = name of device to print error report if set to
log errors (LA7LOG=1).
These parameters can be setup by TaskMan if the site defines them when
scheduling the task.
An example is given below:
Edit Option Schedule
Option Name: LA7TASK NIGHTY
_____________________________________________________________________
VARIABLE NAME: LA7FIX VALUE: 0
VARIABLE NAME: LA7ION VALUE: "IRM DEVELOP LASER1"
VARIABLE NAME: LA7LOG VALUE: 1
If errors are found, an alert is sent to members of the mail group "LAB
MESSAGING" notifying them that errors were detected. If
logging of errors occurred then alert recipients will be able to
print/view error log from the alert system. Alternatively the
error report can be printed using option Print Lab Messaging Integrity
Check [LA7 PRINT INTEGRITY CHECK].
The integrity report can be run alone using option Lab Messaging File
Integrity Checker [LA7 CHECK FILES].
INDEPENDENTLY INVOCABLE: YES ROUTINE:
EN^LA7PURG SCHEDULING RECOMMENDED: YES
UPPERCASE MENU TEXT: LAB MESSAGING NIGHTLY CLEANUP
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> 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~|Prompt]] (or equivalent)? Are
> they starting it from a place I am unaware of? Guess it is time to
> learn how to start something in taskman...
> Select OPTION NAME: LA7TASK NIGHTY <ENTER> Lab Messaging Nightly
> Cleanup
> ANOTHER ONE: <ENTER>
> STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
> Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~|Record]] number
> (IEN),
> no Computed Fields
> DISPLAY AUDIT TRAIL? No//<ENTER> NO
> NAME: LA7TASK NIGHTY MENU TEXT: Lab Messaging Nightly
> Cleanup
> TYPE: run routine CREATOR: LABCREATOR, ONE
> PACKAGE: AUTOMATED LAB INSTRUMENTS
> DESCRIPTION: This is a tasked option to check integrity of LA7 MESSAGE
> QUEUE file (#62.49) and purge messages that are eligible for
> purging. It also purges the following files related to
> LEDI - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT file
> (#62.85) and LAB PENDING ORDERS ENTRY (#69.6)
> John McCormack wrote:
>> RTFM - the documentation explicitly indicates it should be tasked as a
>> scheduled option (task) in TaskMan. It's designed to run non-interactive
>> and therefore has no inputs/outputs other than those documented in the
>> option.
>> Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option
>> Lab messaging will now check that Lab Messaging Nightly Cleanup [LA7TASK
>> NIGHTY] option is scheduled in TaskMan. If not scheduled then an alert
>> notifying members of mail group
>> LAB MESSAGING will be generated. The alert message will read "Lab
>> Messaging- Option LA7TASK NIGHTY is not scheduled in TaskMan". Note:
>> Documentation regarding tasking can be found in the VistA Laboratory
>> LEDI User Guide and on-line via the DESCRIPTION field of the OPTION file
>> (#19) for this entry.
>> Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option
>> Lab messaging has been modified and will now check that Lab Messaging
>> Nightly Cleanup [LA7TASK NIGHTY] option is scheduled in TaskMan. If this
>> option is not scheduled then an
>> alert message notifying members of the LAB MESSAGING mail group is
>> generated. The alert message will read "Lab Messaging- Option LA7TASK
>> NIGHTY is not scheduled in
>> TaskMan." The Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option is
>> tasked to check the integrity of LA7 MESSAGE QUEUE file (#62.49) and
>> purge messages that are
>> eligible for purging. It also purges the following files related to LEDI
>> - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85), and LAB
>> PENDING ORDERS ENTRY (#69.6).
>> The Lab Messaging Nightly Cleanup [LA7TASK NIGHTY] option should be
>> tasked daily, preferably during period when activity in the Lab
>> Messaging (i.e. Universal Interface, LEDI)
>> package is at a minimum. Prior to the purge of LA7 MESSAGE QUEUE file
>> (#62.49), an integrity check is performed. The integrity check can be
>> run with the following switches.
>> NOTE: Documentation regarding tasking can be found in the VistA
>> Laboratory LEDI User Guide and on-line via the DESCRIPTION field of the
>> OPTION file (#19) for this entry.
>> Any outputs are available via this option Print Lab Messaging Integrity
>> Check Report
>> If you want to initiate via an interactive option then use FIC Lab
>> Messaging File Integrity Checker
>> Select Lab Universal Interface Menu Option: ?
>> 2 Print Lab Universal Interface Log
>> Display Lab Universal Interface Message
>> Download to Universal Interface
>> Start/Stop Auto Download Background Job
>> PCS Lab Point of Care Setup
>> FIC Lab Messaging File Integrity Checker
>> PIC Print Lab Messaging Integrity Check Report
>> I, Valdes wrote:
>>> Say, when I invoke LA7TASK NIGHTY it blows me back to the gtm [[prompt~|Prompt]].
>>> ZSTATUS shows nothing "". -- IV
>>> On Jan 4, 10:51 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>>>>> Currently the lab can send us results via a HL7 2.2 message inside of
>>>>> a text file which can be sftp'ed or some such over. However, there
>>>>> would not be a corresponding order in the computer at this point. This
>>>>> would be beneficial. Is there a good setup document for the POC
>>>>> interface?
>>>> Lab POC documentation:http://www.va.gov/vdl/[[application~|Application]].asp?appid=149
>>>> Note that the Lab POC works on the business rule that no existing lab
>>>> order exists in VistA Lab. It always creates a lab order, accession and
>>>> associates the results with the order/accession created.
>>>> VistA HL package is not designed to handle FTPing of files. It's a
>>>> system that supports messaging which involves message transmission,
>>>> receipt and acknowledgment. Using FTP to wrap messages in a file makes
>>>> it very difficult to handle exceptions and/or errors in message
>>>> transmission, receipt or processing which could lead to dropped results
>>>> and/or other patient safety situations. You may need to investigate the
>>>> possibly of a interface engine to act as a front-end between the two
>>>> systems.
>>>>> If possible, I would like to make lab ordering and results obtaining
>>>>> completely paperless. Failing that, electronic results reporting only
>>>>> with the paper ordering continuing until we can get it all paperless.
>>>> Paper ordering and electronic ordering will change the [[business rules~|Business Rules]]
>>>> and determine the type of interface you use.
>>>> If you go with electronic ordering then you may need to use LEDI minus
>>>> the ordering part if the orders on the external lab system are placed
>>>> manually. The external lab system would need to send the VistA Lab
>>>> accession UID as the "placer order number" in any HL7 messaging as VistA
>>>> is playing the role of placer of the order. The external lab system is
>>>> playing the role of "filler" and assigns a filler order number for
>>>> processing within their system.
>>>> I, Valdes wrote:
>>>>> On Jan 4, 9:45 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>>>>>> I'm not sure I follow the business setup.
>>>>>> From your description I'm taking away that this is a hospital
...
read more »
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 6, 9:17 am
From: "I, Valdes" <ival...@hal-pc.org>
Date: Tue, 6 Jan 2009 06:17:53 -0800 (PST)
Local: Tues, Jan 6 2009 9:17 am
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
Um, for some reason it will not accept Jan 07, 2009 04:00:00 am and
many other variations I've tried as a valid time:
Edit Option Schedule
Option Name: LA7TASK NIGHTY
Menu Text: Lab Messaging Nightly Cleanup TASK ID:
__________________________________________________________________________
QUEUED TO RUN AT WHAT TIME: Jan 07, 2009 04:00:00 am
DEVICE FOR QUEUED JOB OUTPUT:
QUEUED TO RUN ON VOLUME SET:
RESCHEDULING FREQUENCY: 1D
TASK PARAMETERS:
SPECIAL QUEUEING: Persistent
_______________________________________________________________________________
Time must be at least 2 minutes in the future and type run, [[action~|Action]],
print
Changing or deleting this date/time field will re-queue
or un-queue the Option.
On Jan 5, 11:09 pm, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> The example is showing you how to schedule it in TaskMan using the
> option Schedule/Unschedule Options.
> Select Systems Manager Menu Option: Taskman Management
> Schedule/Unschedule Options
> One-time Option Queue
> Taskman Management Utilities ...
> List Tasks
> Dequeue Tasks
> Requeue Tasks
> Delete Tasks
> Print Options that are Scheduled to run
> Cleanup Task List
> Print Options Recommended for Queueing
> On the second screen of the ScreenMan form when scheduling you can
> define the value for the variables as documented in the option description.
> Select OPTION NAME: LA7TASK NIGHTY Lab Messaging Nightly Cleanup
> Another one:
> Standard Captioned Output? Yes// N (No)
> First Print FIELD: [CAPTIONED
> Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
> [[Record~|Record]] Number
> (IEN)
> Heading (S/C): OPTION List//
> DEVICE: HOME// 0;132;9999 TELNET
> OPTION
> List
> JAN 5,2009@23:05 PAGE 1
> ------------------------------------------------------------------------------------------------------------------------------------
> NUMBER: 8068 NAME: LA7TASK
> NIGHTY MENU TEXT: Lab Messaging Nightly Cleanup
> TYPE: run routine CREATOR:
> USER,PATCH PACKAGE: AUTOMATED LAB INSTRUMENTS
> DESCRIPTION: This is a tasked option to check integrity of LA7
> MESSAGE QUEUE file (#62.49) and purge messages that are eligible
> for purging. It also purges the following files related to LEDI -
> SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85) and LAB
> PENDING ORDERS ENTRY (#69.6)
> This option should be tasked daily, preferably during period when
> activity in the Lab Messaging (i.e. Universal Interface, LEDI)
> package is at a minimum.
> Prior to the purge of LA7 MESSAGE QUEUE file (#62.49), an integrity
> check is performed. The integrity check can be run with a
> couple of switches.
> LA7FIX = 0 - do not fix errors
> 1 - do fix errors
> LA7LOG = 0 - do not log errors in XTMP global.
> 1 - do log errors in XTMP global
> LA7ION = name of device to print error report if set to
> log errors (LA7LOG=1).
> These parameters can be setup by TaskMan if the site defines them when
> scheduling the task.
> An example is given below:
> Edit Option Schedule
> Option Name: LA7TASK NIGHTY
> _____________________________________________________________________
> VARIABLE NAME: LA7FIX VALUE: 0
> VARIABLE NAME: LA7ION VALUE: "IRM DEVELOP LASER1"
> VARIABLE NAME: LA7LOG VALUE: 1
> If errors are found, an alert is sent to members of the mail group "LAB
> MESSAGING" notifying them that errors were detected. If
> logging of errors occurred then alert recipients will be able to
> print/view error log from the alert system. Alternatively the
> error report can be printed using option Print Lab Messaging Integrity
> Check [LA7 PRINT INTEGRITY CHECK].
> The integrity report can be run alone using option Lab Messaging File
> Integrity Checker [LA7 CHECK FILES].
> INDEPENDENTLY INVOCABLE: YES ROUTINE:
> EN^LA7PURG SCHEDULING RECOMMENDED: YES
> UPPERCASE MENU TEXT: LAB MESSAGING NIGHTLY CLEANUP
> I, Valdes wrote:
> > 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~|Prompt]] (or equivalent)? Are
> > they starting it from a place I am unaware of? Guess it is time to
> > learn how to start something in taskman...
> > Select OPTION NAME: LA7TASK NIGHTY <ENTER> Lab Messaging Nightly
> > Cleanup
> > ANOTHER ONE: <ENTER>
> > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
> > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~|Record]] number
> > (IEN),
> > no Computed Fields
> > DISPLAY AUDIT TRAIL? No//<ENTER> NO
> > NAME: LA7TASK NIGHTY MENU TEXT: Lab Messaging Nightly
> > Cleanup
> > TYPE: run routine CREATOR: LABCREATOR, ONE
> > PACKAGE: AUTOMATED LAB INSTRUMENTS
> > DESCRIPTION: This is a tasked option to check integrity of LA7 MESSAGE
> > QUEUE file (#62.49) and purge messages that are eligible for
> > purging. It also purges the following files related to
> > LEDI - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT file
> > (#62.85) and LAB PENDING ORDERS ENTRY (#69.6)
> > John McCormack wrote:
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 6, 9:48 am
From: "I, Valdes" <ival...@hal-pc.org>
Date: Tue, 6 Jan 2009 06:48:09 -0800 (PST)
Local: Tues, Jan 6 2009 9:48 am
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
For whatever reason, after trying multiple, multiple valid date and
time entries, when I did: T+1@0400 it took it. -- IV
On Jan 6, 8:17 am, "I, Valdes" <ival...@hal-pc.org> wrote:
- Hide quoted text -
- Show quoted text -
> Um, for some reason it will not accept Jan 07, 2009 04:00:00 am and
> many other variations I've tried as a valid time:
> Edit Option Schedule
> Option Name: LA7TASK NIGHTY
> Menu Text: Lab Messaging Nightly Cleanup TASK ID:
> __________________________________________________________________________
> QUEUED TO RUN AT WHAT TIME: Jan 07, 2009 04:00:00 am
> DEVICE FOR QUEUED JOB OUTPUT:
> QUEUED TO RUN ON VOLUME SET:
> RESCHEDULING FREQUENCY: 1D
> TASK PARAMETERS:
> SPECIAL QUEUEING: Persistent
> _______________________________________________________________________________
> Time must be at least 2 minutes in the future and type run, [[action~|Action]],
> print
> Changing or deleting this date/time field will re-queue
> or un-queue the Option.
> On Jan 5, 11:09 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> > The example is showing you how to schedule it in TaskMan using the
> > option Schedule/Unschedule Options.
> > Select Systems Manager Menu Option: Taskman Management
> > Schedule/Unschedule Options
> > One-time Option Queue
> > Taskman Management Utilities ...
> > List Tasks
> > Dequeue Tasks
> > Requeue Tasks
> > Delete Tasks
> > Print Options that are Scheduled to run
> > Cleanup Task List
> > Print Options Recommended for Queueing
> > On the second screen of the ScreenMan form when scheduling you can
> > define the value for the variables as documented in the option description.
> > Select OPTION NAME: LA7TASK NIGHTY Lab Messaging Nightly Cleanup
> > Another one:
> > Standard Captioned Output? Yes// N (No)
> > First Print FIELD: [CAPTIONED
> > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
> > [[Record~|Record]] Number
> > (IEN)
> > Heading (S/C): OPTION List//
> > DEVICE: HOME// 0;132;9999 TELNET
> > OPTION
> > List
> > JAN 5,2009@23:05 PAGE 1
> > ------------------------------------------------------------------------------------------------------------------------------------
> > NUMBER: 8068 NAME: LA7TASK
> > NIGHTY MENU TEXT: Lab Messaging Nightly Cleanup
> > TYPE: run routine CREATOR:
> > USER,PATCH PACKAGE: AUTOMATED LAB INSTRUMENTS
> > DESCRIPTION: This is a tasked option to check integrity of LA7
> > MESSAGE QUEUE file (#62.49) and purge messages that are eligible
> > for purging. It also purges the following files related to LEDI -
> > SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85) and LAB
> > PENDING ORDERS ENTRY (#69.6)
> > This option should be tasked daily, preferably during period when
> > activity in the Lab Messaging (i.e. Universal Interface, LEDI)
> > package is at a minimum.
> > Prior to the purge of LA7 MESSAGE QUEUE file (#62.49), an integrity
> > check is performed. The integrity check can be run with a
> > couple of switches.
> > LA7FIX = 0 - do not fix errors
> > 1 - do fix errors
> > LA7LOG = 0 - do not log errors in XTMP global.
> > 1 - do log errors in XTMP global
> > LA7ION = name of device to print error report if set to
> > log errors (LA7LOG=1).
> > These parameters can be setup by TaskMan if the site defines them when
> > scheduling the task.
> > An example is given below:
> > Edit Option Schedule
> > Option Name: LA7TASK NIGHTY
> > _____________________________________________________________________
> > VARIABLE NAME: LA7FIX VALUE: 0
> > VARIABLE NAME: LA7ION VALUE: "IRM DEVELOP LASER1"
> > VARIABLE NAME: LA7LOG VALUE: 1
> > If errors are found, an alert is sent to members of the mail group "LAB
> > MESSAGING" notifying them that errors were detected. If
> > logging of errors occurred then alert recipients will be able to
> > print/view error log from the alert system. Alternatively the
> > error report can be printed using option Print Lab Messaging Integrity
> > Check [LA7 PRINT INTEGRITY CHECK].
> > The integrity report can be run alone using option Lab Messaging File
> > Integrity Checker [LA7 CHECK FILES].
> > INDEPENDENTLY INVOCABLE: YES ROUTINE:
> > EN^LA7PURG SCHEDULING RECOMMENDED: YES
> > UPPERCASE MENU TEXT: LAB MESSAGING NIGHTLY CLEANUP
> > I, Valdes wrote:
> > > 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~|Prompt]] (or equivalent)? Are
> > > they starting it from a place I am unaware of? Guess it is time to
> > > learn how to start something in taskman...
> > > Select OPTION NAME: LA7TASK NIGHTY <ENTER> Lab Messaging Nightly
> > > Cleanup
> > > ANOTHER ONE: <ENTER>
> > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
> > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~|Record]] number
> > > (IEN),
> > > no Computed Fields
> > > DISPLAY AUDIT TRAIL? No//<ENTER> NO
> > > NAME: LA7TASK NIGHTY MENU TEXT: Lab Messaging Nightly
> > > Cleanup
> > > TYPE: run routine CREATOR: LABCREATOR, ONE
> > > PACKAGE: AUTOMATED LAB INSTRUMENTS
> > > DESCRIPTION: This is a tasked option to check integrity of LA7 MESSAGE
> > > QUEUE file (#62.49) and purge messages that are eligible for
> > > purging. It also purges the following files related to
> > > LEDI - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT file
> > > (#62.85) and LAB PENDING ORDERS ENTRY (#69.6)
> > > John McCormack wrote:
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Jan 6, 10:25 am
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Tue, 06 Jan 2009 10:25:37 -0500
Local: Tues, Jan 6 2009 10:25 am
Subject: Re: [Hardhats] 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
Good thinking!
On Tuesday 06 January 2009, I, Valdes wrote:
- Hide quoted text -
- Show quoted text -
> For whatever reason, after trying multiple, multiple valid date and
> time entries, when I did: T+1@0400 it took it. -- IV
> On Jan 6, 8:17 am, "I, Valdes" <ival...@hal-pc.org> wrote:
> > Um, for some reason it will not accept Jan 07, 2009 04:00:00 am and
> > many other variations I've tried as a valid time:
> > Edit Option Schedule
> > Option Name: LA7TASK NIGHTY
> > Menu Text: Lab Messaging Nightly Cleanup TASK ID:
> > _________________________________________________________________________
> >_
> > QUEUED TO RUN AT WHAT TIME: Jan 07, 2009 04:00:00 am
> > DEVICE FOR QUEUED JOB OUTPUT:
> > QUEUED TO RUN ON VOLUME SET:
> > RESCHEDULING FREQUENCY: 1D
> > TASK PARAMETERS:
> > SPECIAL QUEUEING: Persistent
> > _________________________________________________________________________
> >______ Time must be at least 2 minutes in the future and type run, [[action~|Action]],
> > print
> > Changing or deleting this date/time field will re-queue
> > or un-queue the Option.
> > On Jan 5, 11:09 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> > > The example is showing you how to schedule it in TaskMan using the
> > > option Schedule/Unschedule Options.
> > > Select Systems Manager Menu Option: Taskman Management
> > > Schedule/Unschedule Options
> > > One-time Option Queue
> > > Taskman Management Utilities ...
> > > List Tasks
> > > Dequeue Tasks
> > > Requeue Tasks
> > > Delete Tasks
> > > Print Options that are Scheduled to run
> > > Cleanup Task List
> > > Print Options Recommended for Queueing
> > > On the second screen of the ScreenMan form when scheduling you can
> > > define the value for the variables as documented in the option
> > > description.
> > > Select OPTION NAME: LA7TASK NIGHTY Lab Messaging Nightly Cleanup
> > > Another one:
> > > Standard Captioned Output? Yes// N (No)
> > > First Print FIELD: [CAPTIONED
> > > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
> > > [[Record~|Record]] Number
> > > (IEN)
> > > Heading (S/C): OPTION List//
> > > DEVICE: HOME// 0;132;9999 TELNET
> > > OPTION
> > > List
> > > JAN 5,2009@23:05 PAGE 1
> > > -----------------------------------------------------------------------
> > >-------------------------------------------------------------
> > > NUMBER: 8068 NAME: LA7TASK
> > > NIGHTY MENU TEXT: Lab Messaging Nightly Cleanup
> > > TYPE: run routine CREATOR:
> > > USER,PATCH PACKAGE: AUTOMATED LAB INSTRUMENTS
> > > DESCRIPTION: This is a tasked option to check integrity of LA7
> > > MESSAGE QUEUE file (#62.49) and purge messages that are eligible
> > > for purging. It also purges the following files related to LEDI -
> > > SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85) and LAB
> > > PENDING ORDERS ENTRY (#69.6)
> > > This option should be tasked daily, preferably during period when
> > > activity in the Lab Messaging (i.e. Universal Interface, LEDI)
> > > package is at a minimum.
> > > Prior to the purge of LA7 MESSAGE QUEUE file (#62.49), an integrity
> > > check is performed. The integrity check can be run with a
> > > couple of switches.
> > > LA7FIX = 0 - do not fix errors
> > > 1 - do fix errors
> > > LA7LOG = 0 - do not log errors in XTMP global.
> > > 1 - do log errors in XTMP global
> > > LA7ION = name of device to print error report if set to
> > > log errors (LA7LOG=1).
> > > These parameters can be setup by TaskMan if the site defines them when
> > > scheduling the task.
> > > An example is given below:
> > > Edit Option Schedule
> > > Option Name: LA7TASK NIGHTY
> > >
> > > _____________________________________________________________________
> > > VARIABLE NAME: LA7FIX VALUE: 0
> > > VARIABLE NAME: LA7ION VALUE: "IRM DEVELOP
> > > LASER1" VARIABLE NAME: LA7LOG VALUE: 1
> > > If errors are found, an alert is sent to members of the mail group
> > > "LAB MESSAGING" notifying them that errors were detected. If
> > > logging of errors occurred then alert recipients will be able to
> > > print/view error log from the alert system. Alternatively the
> > > error report can be printed using option Print Lab Messaging Integrity
> > > Check [LA7 PRINT INTEGRITY CHECK].
> > > The integrity report can be run alone using option Lab Messaging File
> > > Integrity Checker [LA7 CHECK FILES].
> > > INDEPENDENTLY INVOCABLE: YES ROUTINE:
> > > EN^LA7PURG SCHEDULING RECOMMENDED: YES
> > > UPPERCASE MENU TEXT: LAB MESSAGING NIGHTLY CLEANUP
> > > I, Valdes wrote:
> > > > 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~|Prompt]] (or
> > > > equivalent)? Are they starting it from a place I am unaware of?
> > > > Guess it is time to learn how to start something in taskman...
> > > > Select OPTION NAME: LA7TASK NIGHTY <ENTER> Lab Messaging Nightly
> > > > Cleanup
> > > > ANOTHER ONE: <ENTER>
> > > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
> > > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~|Record]] number
> > > > (IEN),
> > > > no Computed Fields
> > > > DISPLAY AUDIT TRAIL? No//<ENTER> NO
> > > > NAME: LA7TASK NIGHTY MENU TEXT: Lab Messaging Nightly
> > > > Cleanup
> > > > TYPE: run routine CREATOR: LABCREATOR, ONE
> > > > PACKAGE: AUTOMATED LAB INSTRUMENTS
> > > > DESCRIPTION: This is a tasked option to check integrity of LA7
> > > > MESSAGE QUEUE file (#62.49) and purge messages that are eligible for
> > > > purging. It also purges the following files related to
> > > > LEDI - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT file
> > > > (#62.85) and LAB PENDING ORDERS ENTRY (#69.6)
> > > > John McCormack wrote:
--
Nancy Anthracite
I, Valdes
View profile
More options Jan 6, 1:51 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Tue, 6 Jan 2009 10:51:55 -0800 (PST)
Local: Tues, Jan 6 2009 1:51 pm
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
Co-credit goes to David. -- IV
On Jan 6, 9:25 am, Nancy Anthracite <nanthrac...@verizon.net> wrote:
- Hide quoted text -
- Show quoted text -
> Good thinking!
> On Tuesday 06 January 2009, I, Valdes wrote:
> > For whatever reason, after trying multiple, multiple valid date and
> > time entries, when I did: T+1@0400 it took it. -- IV
> > On Jan 6, 8:17 am, "I, Valdes" <ival...@hal-pc.org> wrote:
> > > Um, for some reason it will not accept Jan 07, 2009 04:00:00 am and
> > > many other variations I've tried as a valid time:
> > > Edit Option Schedule
> > > Option Name: LA7TASK NIGHTY
> > > Menu Text: Lab Messaging Nightly Cleanup TASK ID:
> > > _________________________________________________________________________
> > >_
> > > QUEUED TO RUN AT WHAT TIME: Jan 07, 2009 04:00:00 am
> > > DEVICE FOR QUEUED JOB OUTPUT:
> > > QUEUED TO RUN ON VOLUME SET:
> > > RESCHEDULING FREQUENCY: 1D
> > > TASK PARAMETERS:
> > > SPECIAL QUEUEING: Persistent
> > > _________________________________________________________________________
> > >______ Time must be at least 2 minutes in the future and type run, [[action~|Action]],
> > > print
> > > Changing or deleting this date/time field will re-queue
> > > or un-queue the Option.
> > > On Jan 5, 11:09 pm, John McCormack <johnm...@ix.netcom.com> wrote:
> > > > The example is showing you how to schedule it in TaskMan using the
> > > > option Schedule/Unschedule Options.
> > > > Select Systems Manager Menu Option: Taskman Management
> > > > Schedule/Unschedule Options
> > > > One-time Option Queue
> > > > Taskman Management Utilities ...
> > > > List Tasks
> > > > Dequeue Tasks
> > > > Requeue Tasks
> > > > Delete Tasks
> > > > Print Options that are Scheduled to run
> > > > Cleanup Task List
> > > > Print Options Recommended for Queueing
> > > > On the second screen of the ScreenMan form when scheduling you can
> > > > define the value for the variables as documented in the option
> > > > description.
> > > > Select OPTION NAME: LA7TASK NIGHTY Lab Messaging Nightly Cleanup
> > > > Another one:
> > > > Standard Captioned Output? Yes// N (No)
> > > > First Print FIELD: [CAPTIONED
> > > > Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and
> > > > [[Record~|Record]] Number
> > > > (IEN)
> > > > Heading (S/C): OPTION List//
> > > > DEVICE: HOME// 0;132;9999 TELNET
> > > > OPTION
> > > > List
> > > > JAN 5,2009@23:05 PAGE 1
> > > > -----------------------------------------------------------------------
> > > >-------------------------------------------------------------
> > > > NUMBER: 8068 NAME: LA7TASK
> > > > NIGHTY MENU TEXT: Lab Messaging Nightly Cleanup
> > > > TYPE: run routine CREATOR:
> > > > USER,PATCH PACKAGE: AUTOMATED LAB INSTRUMENTS
> > > > DESCRIPTION: This is a tasked option to check integrity of LA7
> > > > MESSAGE QUEUE file (#62.49) and purge messages that are eligible
> > > > for purging. It also purges the following files related to LEDI -
> > > > SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT (#62.85) and LAB
> > > > PENDING ORDERS ENTRY (#69.6)
> > > > This option should be tasked daily, preferably during period when
> > > > activity in the Lab Messaging (i.e. Universal Interface, LEDI)
> > > > package is at a minimum.
> > > > Prior to the purge of LA7 MESSAGE QUEUE file (#62.49), an integrity
> > > > check is performed. The integrity check can be run with a
> > > > couple of switches.
> > > > LA7FIX = 0 - do not fix errors
> > > > 1 - do fix errors
> > > > LA7LOG = 0 - do not log errors in XTMP global.
> > > > 1 - do log errors in XTMP global
> > > > LA7ION = name of device to print error report if set to
> > > > log errors (LA7LOG=1).
> > > > These parameters can be setup by TaskMan if the site defines them when
> > > > scheduling the task.
> > > > An example is given below:
> > > > Edit Option Schedule
> > > > Option Name: LA7TASK NIGHTY
> > > >
> > > > _____________________________________________________________________
> > > > VARIABLE NAME: LA7FIX VALUE: 0
> > > > VARIABLE NAME: LA7ION VALUE: "IRM DEVELOP
> > > > LASER1" VARIABLE NAME: LA7LOG VALUE: 1
> > > > If errors are found, an alert is sent to members of the mail group
> > > > "LAB MESSAGING" notifying them that errors were detected. If
> > > > logging of errors occurred then alert recipients will be able to
> > > > print/view error log from the alert system. Alternatively the
> > > > error report can be printed using option Print Lab Messaging Integrity
> > > > Check [LA7 PRINT INTEGRITY CHECK].
> > > > The integrity report can be run alone using option Lab Messaging File
> > > > Integrity Checker [LA7 CHECK FILES].
> > > > INDEPENDENTLY INVOCABLE: YES ROUTINE:
> > > > EN^LA7PURG SCHEDULING RECOMMENDED: YES
> > > > UPPERCASE MENU TEXT: LAB MESSAGING NIGHTLY CLEANUP
> > > > I, Valdes wrote:
> > > > > 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~|Prompt]] (or
> > > > > equivalent)? Are they starting it from a place I am unaware of?
> > > > > Guess it is time to learn how to start something in taskman...
> > > > > Select OPTION NAME: LA7TASK NIGHTY <ENTER> Lab Messaging Nightly
> > > > > Cleanup
> > > > > ANOTHER ONE: <ENTER>
> > > > > STANDARD CAPTIONED OUTPUT? Yes//<ENTER> (Yes)
> > > > > Include COMPUTED fields: (N/Y/R/B): NO// <ENTER> - No [[record~|Record]] number
> > > > > (IEN),
> > > > > no Computed Fields
> > > > > DISPLAY AUDIT TRAIL? No//<ENTER> NO
> > > > > NAME: LA7TASK NIGHTY MENU TEXT: Lab Messaging Nightly
> > > > > Cleanup
> > > > > TYPE: run routine CREATOR: LABCREATOR, ONE
> > > > > PACKAGE: AUTOMATED LAB INSTRUMENTS
> > > > > DESCRIPTION: This is a tasked option to check integrity of LA7
> > > > > MESSAGE QUEUE file (#62.49) and purge messages that are eligible for
> > > > > purging. It also purges the following files related to
> > > > > LEDI - SHIPPING MANIFEST (#62.8), LAB SHIPPING EVENT file
> > > > > (#62.85) and LAB PENDING ORDERS ENTRY (#69.6)
> > > > > John McCormack wrote:
> --
> Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jan 7, 1:36 pm
From: "I, Valdes" <ival...@hal-pc.org>
Date: Wed, 7 Jan 2009 10:36:49 -0800 (PST)
Local: Wed, Jan 7 2009 1:36 pm
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
I've just been informed by the lab that they can only send me a text
file with an HL7 message, they cannot transmit it on a tcp port
because it is old software. Is there a way to take the file and fake
transmitting it onto the usual HL7 VistA listening port? Should I
entertain switching to a major lab that has done this before with
VistA? The Mom and Pop lab is not looking responsive. -- IV
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Ben Mehling
View profile
More options Jan 7, 2:01 pm
From: "Ben Mehling" <ben.mehl...@medsphere.com>
Date: Wed, 7 Jan 2009 11:01:00 -0800
Subject: Re: [Hardhats] 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
You should be able to create a Mirth channel that watches a directory for
files, parses the data and places it into an HL7 message that gets sent off
to your listener in VistA. How will they deliver the txt file -- FTP?
- Ben
- Hide quoted text -
- Show quoted text -
On Wed, Jan 7, 2009 at 10:36 AM, I, Valdes <ival...@hal-pc.org> wrote:
> I've just been informed by the lab that they can only send me a text
> file with an HL7 message, they cannot transmit it on a tcp port
> because it is old software. Is there a way to take the file and fake
> transmitting it onto the usual HL7 VistA listening port? Should I
> entertain switching to a major lab that has done this before with
> VistA? The Mom and Pop lab is not looking responsive. -- IV
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post:
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nancy Anthracite
View profile
More options Jan 7, 3:18 pm
From: Nancy Anthracite <nanthrac...@verizon.net>
Date: Wed, 07 Jan 2009 15:18:58 -0500
Local: Wed, Jan 7 2009 3:18 pm
Subject: Re: [Hardhats] 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
Ignacio, I think using Mirth you can do this. Matt's clinic is about to do
something this. Even with the major labs, you may have unsolicited results
coming in that are just like this, so it a problem everywhere and those sorts
of text files will have to be handled.
Most labs have HL7, but it is not HL7 that is strictly tied to the standard,
which is why you need something like Mirth. Even if it is strict, I think
that Mirth could be used with a straight pass-through.
LabCorp has a VistA specific Interface, written for the VA that plugs right
into VistA via a VPN. Quest is working on the same. Many of the LabCorp
reps in areas around the country have no idea that it exists, so it needs to
be coordinated with someone in LabCorp that knows about it, so if you decide
to go that route, please talk to me so I can help you connect the dots.
However, for that there needs to be a "manifest" - that is a paper or other
order that has the required elements so that the manifest can be generated
in VistA and responded to by the lab to deliver the results in directly.
Otherwise, results will be stored in a file for further processing to make it
all work.
I am hoping John McCormach is going to be jumping in here to tell you
everything that I told you that is wrong.
I am very excited about the project that is going to start at Clinica Adelante
with LabCorp as I think it will be the first implementation of this VistA
specific interface outside of the VA.
That said, look at what Bluecliff did for the VOE project for Laboratory
interfacing which I think I pointed you at for the Mom and Pop lab. Also,
the IHS and Clinica Adelante have done Quest interfaces, each one of which is
different) and IHS did an old style LabCorp interface - i.e., not using the
VA specific interface. There may be some help there.
On Wednesday 07 January 2009, I, Valdes wrote:
> I've just been informed by the lab that they can only send me a text
> file with an HL7 message, they cannot transmit it on a tcp port
> because it is old software. Is there a way to take the file and fake
> transmitting it onto the usual HL7 VistA listening port? Should I
> entertain switching to a major lab that has done this before with
> VistA? The Mom and Pop lab is not looking responsive. -- IV
--
Nancy Anthracite
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jan 8, 12:51 am
From: John McCormack <johnm...@ix.netcom.com>
Date: Wed, 07 Jan 2009 23:51:48 -0600
Local: Thurs, Jan 8 2009 12:51 am
Subject: Re: [Hardhats] 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
Just whatever you do stay HIPAA compliant and use a secure/encrypted
means of exchanging this information and avoid exposing your patient's
medical information to the public.
Remember you can always fall back on string and tin cans...
- Hide quoted text -
- Show quoted text -
Nancy Anthracite wrote:
> Ignacio, I think using Mirth you can do this. Matt's clinic is about to do
> something this. Even with the major labs, you may have unsolicited results
> coming in that are just like this, so it a problem everywhere and those sorts
> of text files will have to be handled.
> Most labs have HL7, but it is not HL7 that is strictly tied to the standard,
> which is why you need something like Mirth. Even if it is strict, I think
> that Mirth could be used with a straight pass-through.
> LabCorp has a VistA specific Interface, written for the VA that plugs right
> into VistA via a VPN. Quest is working on the same. Many of the LabCorp
> reps in areas around the country have no idea that it exists, so it needs to
> be coordinated with someone in LabCorp that knows about it, so if you decide
> to go that route, please talk to me so I can help you connect the dots.
> However, for that there needs to be a "manifest" - that is a paper or other
> order that has the required elements so that the manifest can be generated
> in VistA and responded to by the lab to deliver the results in directly.
> Otherwise, results will be stored in a file for further processing to make it
> all work.
> I am hoping John McCormach is going to be jumping in here to tell you
> everything that I told you that is wrong.
> I am very excited about the project that is going to start at Clinica Adelante
> with LabCorp as I think it will be the first implementation of this VistA
> specific interface outside of the VA.
> That said, look at what Bluecliff did for the VOE project for Laboratory
> interfacing which I think I pointed you at for the Mom and Pop lab. Also,
> the IHS and Clinica Adelante have done Quest interfaces, each one of which is
> different) and IHS did an old style LabCorp interface - i.e., not using the
> VA specific interface. There may be some help there.
> On Wednesday 07 January 2009, I, Valdes wrote:
>> I've just been informed by the lab that they can only send me a text
>> file with an HL7 message, they cannot transmit it on a tcp port
>> because it is old software. Is there a way to take the file and fake
>> transmitting it onto the usual HL7 VistA listening port? Should I
>> entertain switching to a major lab that has done this before with
>> VistA? The Mom and Pop lab is not looking responsive. -- IV
> ------------------------------------------------------------------------
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.10.5/1881 - Release Date: 1/7/2009 5:59 PM
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Ignacio Valdes
View profile
More options Jul 8, 4:12 pm
From: Ignacio Valdes <ival...@hal-pc.org>
Date: Wed, 8 Jul 2009 16:12:01 -0500
Local: Wed, Jul 8 2009 4:12 pm
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
Is there any particular port that is usually used for lab tcp
connection with VistA?
-- IV
- Hide quoted text -
- Show quoted text -
On Sun, Dec 21, 2008 at 11:39 AM, Ignacio Valdes<ival...@hal-pc.org> wrote:
> 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
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jul 8, 4:39 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Wed, 08 Jul 2009 16:39:05 -0500
Local: Wed, Jul 8 2009 4:39 pm
Subject: Re: [Hardhats] 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
VistA Lab uses/supports the VA VistA standard HL7 service on port 5000.
That's just a VA standard. There is no predefined port.
The VistA HL package does not "tie" a specific [[application~|Application]] to a specific
port.
All [[application~|Application]]s can be received on the same port as the MSH segment is
inspected and routing within VistA is based on the routing information
found in this segment.
When connecting to non-VA services it's whatever the external service
indicates they are monitoring.
You may want to conform to and avoid the standard ports assigned by IANA.
http://www.iana.org/assignments/port-numbers
Many network security devices now inspect the payload on TCP connections
and compare them to the approved protocol for the port.
If the payload does not conform to the protocol they will terminate the
connection with prejudice as a network security violation.
- Hide quoted text -
- Show quoted text -
Ignacio Valdes wrote:
> Is there any particular port that is usually used for lab tcp
> connection with VistA?
> -- IV
> On Sun, Dec 21, 2008 at 11:39 AM, Ignacio Valdes<ival...@hal-pc.org> wrote:
>> 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
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
I, Valdes
View profile
More options Jul 9, 9:39 am
From: "I, Valdes" <ival...@hal-pc.org>
Date: Thu, 9 Jul 2009 07:39:24 -0700 (PDT)
Local: Thurs, Jul 9 2009 9:39 am
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
Okay, my local non-national lab is showing signs of life. They say
they are ready for a tcp connection to transmit HL7 lab messages. They
do not have the capability of taking orders from VistA, just the
current paper ordering system. I don't have the quick orders setup
either. Is there a simple way of receiving those lab results and
routing them to the Lab tab [[record~|Record]] using only patient demographics/
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
one.
-- IV
On Jul 8, 4:39 pm, John McCormack <johnm...@ix.netcom.com> wrote:
- Hide quoted text -
- Show quoted text -
> VistA Lab uses/supports the VA VistA standard HL7 service on port 5000.
> That's just a VA standard. There is no predefined port.
> The VistA HL package does not "tie" a specific [[application~|Application]] to a specific
> port.
> All [[application~|Application]]s can be received on the same port as the MSH segment is
> inspected and routing within VistA is based on the routing information
> found in this segment.
> When connecting to non-VA services it's whatever the external service
> indicates they are monitoring.
> You may want to conform to and avoid the standard ports assigned by IANA.http://www.iana.org/assignments/port-numbers
> Many network security devices now inspect the payload on TCP connections
> and compare them to the approved protocol for the port.
> If the payload does not conform to the protocol they will terminate the
> connection with prejudice as a network security violation.
> Ignacio Valdes wrote:
> > Is there any particular port that is usually used for lab tcp
> > connection with VistA?
> > -- IV
> > On Sun, Dec 21, 2008 at 11:39 AM, Ignacio Valdes<ival...@hal-pc.org> wrote:
> >> 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
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
fred trotter
View profile
More options Jul 9, 2:43 pm
From: fred trotter <fred.trot...@gmail.com>
Date: Thu, 9 Jul 2009 14:43:44 -0500
Local: Thurs, Jul 9 2009 2:43 pm
Subject: Re: [Hardhats] 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
I recommend that you use Mirth to accept the tcp connection that they
are offering and simply log the lab results to the database. This will
allow you to actually get the tcp connection in place and resolve all
of the networking and political issues that you need to get that done.
Once it is place, mirth can both store a copy of the lab feed to a
database, and it can forward the hl7 on to VistA. Once you are getting
the lab feeds to mirth, then worry about getting into VistA. Once you
start the VistA integration, then change the store and forward mirth
instance to a store, munge and forward.
HTH,
-FT
- Hide quoted text -
- Show quoted text -
On Thu, Jul 9, 2009 at 9:39 AM, I, Valdes<ival...@hal-pc.org> wrote:
> Okay, my local non-national lab is showing signs of life. They say
> they are ready for a tcp connection to transmit HL7 lab messages. They
> do not have the capability of taking orders from VistA, just the
> current paper ordering system. I don't have the quick orders setup
> either. Is there a simple way of receiving those lab results and
> routing them to the Lab tab [[record~|Record]] using only patient demographics/
> 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
> one.
> -- IV
> On Jul 8, 4:39 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>> VistA Lab uses/supports the VA VistA standard HL7 service on port 5000.
>> That's just a VA standard. There is no predefined port.
>> The VistA HL package does not "tie" a specific [[application~|Application]] to a specific
>> port.
>> All [[application~|Application]]s can be received on the same port as the MSH segment is
>> inspected and routing within VistA is based on the routing information
>> found in this segment.
>> When connecting to non-VA services it's whatever the external service
>> indicates they are monitoring.
>> You may want to conform to and avoid the standard ports assigned by IANA.http://www.iana.org/assignments/port-numbers
>> Many network security devices now inspect the payload on TCP connections
>> and compare them to the approved protocol for the port.
>> If the payload does not conform to the protocol they will terminate the
>> connection with prejudice as a network security violation.
>> Ignacio Valdes wrote:
>> > Is there any particular port that is usually used for lab tcp
>> > connection with VistA?
>> > -- IV
>> > On Sun, Dec 21, 2008 at 11:39 AM, Ignacio Valdes<ival...@hal-pc.org> wrote:
>> >> 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
--
Fred Trotter
http://www.fredtrotter.com
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John McCormack
View profile
More options Jul 9, 11:40 pm
From: John McCormack <johnm...@ix.netcom.com>
Date: Thu, 09 Jul 2009 23:40:53 -0500
Local: Thurs, Jul 9 2009 11:40 pm
Subject: Re: [Hardhats] 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
Given that CPRS is basically a shell that interacts with other VistA
packages, for laboratory results to "show up" on the CPRS Lab tab
requires lab orders and results be entered in the VistA Laboratory package.
There are three VistA Lab HL7 interfaces that accept and store lab
results. Each is designed to support different business cases.
1. Lab Universal Interface is designed to send orders to lab automated
instruments and accept and store the results. It's based on existing lab
accessions which are transmitted to the instrument or which when the
instrument sends the results transmits the VistA Lab specimen id
associated with the accession to "marry up" the results with the
existing lab order/accession. Note that this is NOT a CPRS order number
instead a Laboratory ID associated with the particular specimen.
2. The next interface available is the Lab LEDI interface which
interfaces VistA Lab with external reference labs. Again this is based
on a placer/filler model in which VistA Lab transmits order information
which is returned by the reference lab with the results. The order
information returned with the results is used to associate these results
with the existing order to complete the existing order and notify the
ordering provider.
3. The third interface is the Lab Point of Care. This interface takes
test results performed on point of care (ancillary testing equipment).
The interface is based on the business case that no existing order
exists in either CPRS or VistA Laboratory. Based on information
transmitted (patient id, ordering provider, ordering location, orderable
tests, specimen date/time, etc) by the POC system the Laboratory package
creates a new order in VistA Laboratory and CPRS, then processes the
results and stores them with the order just created.
In all three cases above these interfaces usually deal with a subset of
all possible tests performed by a VA laboratory. This requires mapping
of order and result test codes, specimen codes, ordering provider and
verifying personnel. This is to meet Federal government (CLIA) and
accreditation requirements. In attempting to handle ALL types of
laboratory tests your probably dealing with 1000+ possible tests.
The interface that most closely matches the situation you describe is
the Lab POC interface. However this would still require extensive
[[configuration~|Configuration]] and coordination with the external lab. The user guide and
HL7 interface specification is available on the VA VistA VDL.
Then again there's always scanning them into TIU and signing them as
progress notes.
Whatever you do just make sure the proper safeguards and system checks
are in place to insure correct patient, provider, test and specimen
identification. You don't want the system recording a PT/PTT on serum
and pO2 on CSF.
Note that CPRS order numbers generate corresponding orders in the VistA
packages it interacts with.
A CPRS order (number) for laboratory will generate a VistA Laboratory
order (number) which is further separated into one or more VistA
Laboratory accession (numbers) which are the work unit/id used to
process and perform the testing within the laboratory.
A CPRS order for CBC, UA and FBS and Renal panel will generate probably
three lab orders (one for each specimen type - whole blood, urine and
serum) and possibly four lab accessions as the various specimens and
tests are routed within the laboratory.
HTH
- Hide quoted text -
- Show quoted text -
I, Valdes wrote:
> Thanks but then you have an intermediary box where you may not need
> one. Also the trick doesn't seem to be Mirth, the trick seems to be
> getting it into VistA and the report routed to the Lab tab for a
> patient likely without orders. This may have something to do with
> Booleans :-)
> -- IV
> On Jul 9, 2:43 pm, fred trotter <fred.trot...@gmail.com> wrote:
>> I recommend that you use Mirth to accept the tcp connection that they
>> are offering and simply log the lab results to the database. This will
>> allow you to actually get the tcp connection in place and resolve all
>> of the networking and political issues that you need to get that done.
>> Once it is place, mirth can both store a copy of the lab feed to a
>> database, and it can forward the hl7 on to VistA. Once you are getting
>> the lab feeds to mirth, then worry about getting into VistA. Once you
>> start the VistA integration, then change the store and forward mirth
>> instance to a store, munge and forward.
>> HTH,
>> -FT
>> On Thu, Jul 9, 2009 at 9:39 AM, I, Valdes<ival...@hal-pc.org> wrote:
>>> Okay, my local non-national lab is showing signs of life. They say
>>> they are ready for a tcp connection to transmit HL7 lab messages. They
>>> do not have the capability of taking orders from VistA, just the
>>> current paper ordering system. I don't have the quick orders setup
>>> either. Is there a simple way of receiving those lab results and
>>> routing them to the Lab tab [[record~|Record]] using only patient demographics/
>>> 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
>>> one.
>>> -- IV
>>> On Jul 8, 4:39 pm, John McCormack <johnm...@ix.netcom.com> wrote:
>>>> VistA Lab uses/supports the VA VistA standard HL7 service on port 5000.
>>>> That's just a VA standard. There is no predefined port.
>>>> The VistA HL package does not "tie" a specific [[application~|Application]] to a specific
>>>> port.
>>>> All [[application~|Application]]s can be received on the same port as the MSH segment is
>>>> inspected and routing within VistA is based on the routing information
>>>> found in this segment.
>>>> When connecting to non-VA services it's whatever the external service
>>>> indicates they are monitoring.
>>>> You may want to conform to and avoid the standard ports assigned by IANA.http://www.iana.org/assignments/port-numbers
>>>> Many network security devices now inspect the payload on TCP connections
>>>> and compare them to the approved protocol for the port.
>>>> If the payload does not conform to the protocol they will terminate the
>>>> connection with prejudice as a network security violation.
>>>> Ignacio Valdes wrote:
>>>>> Is there any particular port that is usually used for lab tcp
>>>>> connection with VistA?
>>>>> -- IV
>>>>> On Sun, Dec 21, 2008 at 11:39 AM, Ignacio Valdes<ival...@hal-pc.org> wrote:
>>>>>> 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
>> --
>> Fred Trotterhttp://www.fredtrotter.com
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
fred trotter
View profile
More options Jul 10, 2:00 am
From: fred trotter <fred.trot...@gmail.com>
Date: Fri, 10 Jul 2009 02:00:01 -0500
Local: Fri, Jul 10 2009 2:00 am
Subject: Re: [Hardhats] 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
> This may have something to do with
> Booleans :-)
Cold man... that's just cold.
--
Fred Trotter
http://www.fredtrotter.com
Reply to author Forward
Report spam
Reporting spam
Message reported
Rate this post: Text for clearing space
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
fred trotter
View profile
More options Jul 10, 2:00 am
From: fred trotter <fred.trot...@gmail.com>
Date: Fri, 10 Jul 2009 02:00:47 -0500
Local: Fri, Jul 10 2009 2:00 am
Subject: Re: [Hardhats] 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
On Thu, Jul 9, 2009 at 9:28 PM, I, Valdes<ival...@hal-pc.org> wrote:
> Thanks but then you have an intermediary box where you may not need
> one. Also the trick doesn't seem to be Mirth, the trick seems to be
> getting it into VistA and the report routed to the Lab tab for a
> patient likely without orders. This may have something to do with
> Booleans :-)
Not an extra box, an extra process on the VistA box. No reason to have
two CPUs.
-FT
--
Fred Trotter
http://www.fredtrotter.com
