1 | English French Notes Complete/Exclude
|
---|
2 | Removing references to KMPS-SAGG mail group ...
|
---|
3 | KMPS-SAGG
|
---|
4 | INFO: KMPS-SAGG mail group is missing.
|
---|
5 | INFO: Removing MEMBER GROUP KMPS-SAGG in
|
---|
6 | mail group ...
|
---|
7 | ERROR: Cannot remove KMPS-SAGG from
|
---|
8 | mail group
|
---|
9 | ERROR: KMP-CAPMAN mail group is missing.
|
---|
10 | Moving KMPS-SAGG mail group members to KMP-CAPMAN ...
|
---|
11 | Pre-install routine complete.
|
---|
12 | Install will continue ...
|
---|
13 | XMVVITAE+1^XMVVITAE
|
---|
14 | MEMBER GROUPS
|
---|
15 | MEMBER GROUP
|
---|
16 | XMB(3.8)
|
---|
17 | MEMBERS - REMOTE
|
---|
18 | DISTRIBUTION LIST
|
---|
19 | FAX RECIPIENT
|
---|
20 | FAX GROUP
|
---|
21 | ERROR: Cannot add
|
---|
22 | to KMP-CAPMAN mail group
|
---|
23 | Running Post-install routine ...
|
---|
24 | Removing KMPS-SAGG mail group ...
|
---|
25 | ERROR: Cannot remove KMPS-SAGG mail group.
|
---|
26 | Use FileMan to delete KMPS-SAGG mail group.
|
---|
27 | Post-install routine complete.
|
---|
28 | SAGG Environment
|
---|
29 | KMPS SAGG REPORT
|
---|
30 | Current Status:
|
---|
31 | Session Number:
|
---|
32 | Start Date:
|
---|
33 | SAGG Master Background Task:
|
---|
34 | option is missing !
|
---|
35 | Queued to run at:
|
---|
36 | Rescheduling frequency:
|
---|
37 | ***It is STRONGLY recommended that this job be rescheduled to run
|
---|
38 | over the weekend every 28 days.***
|
---|
39 | Task ID:
|
---|
40 | Queued by:
|
---|
41 | ***The user that originally queued this task is no longer active.
|
---|
42 | Therefore the 'SAGG Master Background Task' [KMPS SAGG REPORT]
|
---|
43 | must be scheduled again by an active user.***
|
---|
44 | DATA PRESENT
|
---|
45 | Global Location:
|
---|
46 | SAGG Environment (cont.)
|
---|
47 | SAGG Project collection routines will monitor the following:
|
---|
48 | SAGG Project collection routines are still running on:
|
---|
49 | SAGG Project collection routines have recorded an error on
|
---|
50 | the following Volume Set(s):
|
---|
51 | SAGG has been running over a day. Use ^%S
|
---|
52 | and check to see if
|
---|
53 | the KMPSGE routine is still running.
|
---|
54 | NOTE: Any incomplete data that has been collected will be
|
---|
55 | deleted automatically the next time that SAGG runs.
|
---|
56 | First determine the cause of any volume set errors.
|
---|
57 | Reschedule SAGG to collect global data if necessary.
|
---|
58 | Patch Status
|
---|
59 | <No routine patch information available>
|
---|
60 | Currently
|
---|
61 | Need to
|
---|
62 | Install
|
---|
63 | <<<missing routine>>>
|
---|
64 | Ok
|
---|
65 | The SAGG Project collection routines are not running.
|
---|
66 | Current status of SAGG is
|
---|
67 | Do you wish to manually STOP the SAGG Project collection routines (Y/N)
|
---|
68 | The SAGG Project collection routines have been notified to begin an
|
---|
69 | orderly shut-down process.
|
---|
70 | Please specify the Volume Set and UCI which will hold the ^XTMP(
|
---|
71 | Specify the
|
---|
72 | Volume Sets
|
---|
73 | Directories
|
---|
74 | which hold your VistA production globals.
|
---|
75 | For example:
|
---|
76 | Cache for Windows NT => W:\VAA, W:\VBB, W:\VCC ... V:\Vxx
|
---|
77 | Cache for OpenVMS => _$1$DKAn:[CACHSYS.VAA] ... _$1$DKAx:[CACHSYS.Vxx]
|
---|
78 | DSM => ROU, VAA, VBB, VCC ... Vxx
|
---|
79 | Specify all locations of VistA globals
|
---|
80 | Do NOT specify 'test/training'
|
---|
81 | KMP-CAPMAN mail group:
|
---|
82 | (MEMBER GROUP)
|
---|
83 | (DISTRIBUTION LIST)
|
---|
84 | (FAX RECEIPIENT)
|
---|
85 | (FAX GROUP)
|
---|
86 | NO USERS
|
---|
87 | This field will contain the name of the
|
---|
88 | that the site wants
|
---|
89 | to monitor with the SAGG Project collection routines. The site should
|
---|
90 | specify only the
|
---|
91 | which hold their VistA production globals:
|
---|
92 | For example:
|
---|
93 | Cache for Windows NT => W:\VAA, W:\VBB, W:\VCC ... V:\Vxx
|
---|
94 | Cache for OpenVMS => _$1$DKAn:[CACHSYS.VAA] ... _$1$DKAx:[CACHSYS.Vxx]
|
---|
95 | Do NOT specify 'test/training'
|
---|
96 | This is the
|
---|
97 | text to display.
|
---|
98 | IOECH;IOELALL;IOELEOL;IORVON;IORVOFF;IOSTKMPUBM
|
---|
99 | , [N]ext Screen
|
---|
100 | , [P]revious Screen
|
---|
101 | Enter 'X' (or '^') to exit.
|
---|
102 | Enter 'N' to advance to the next screen.
|
---|
103 | Enter 'P' to backup to the previous screen.
|
---|
104 | UTIL($J,
|
---|
105 | ...no array data...
|
---|
106 | ...no information to graph...
|
---|
107 | ...too many data elements to double space on a terminal
|
---|
108 | for a Horizontal Graph...
|
---|
109 | for a Vertical Graph...
|
---|
110 | ...unable to place terminal in graphics mode...
|
---|
111 | ...unable to determine any data to graph or data all zeros...
|
---|
112 | IOECH;IORVOFF;IORVON;IOUOFF;IOUON
|
---|
113 | IORVON,
|
---|
114 | IOG1,
|
---|
115 | The following graph selections are 'optional':
|
---|
116 | Enter one or more option letter(s):
|
---|
117 | Angle Data Titles only available with a Vertical Graph...
|
---|
118 | ...please be aware that because of screen limitations Vertical
|
---|
119 | Graphs are not as accurate as Horizontal Graphs and should be
|
---|
120 | used for visual comparison rather than detailed analysis...
|
---|
121 | ' is not an available option.
|
---|
122 | A: Angle data titles..: Angle the titles (for Vertical Graphs only).
|
---|
123 | D: Double space data..: Will place an empty column/row between graph bars
|
---|
124 | (it is highly recommended that double spacing be used
|
---|
125 | with Vertical graphs).
|
---|
126 | G: Grid...............: Print grid lines on graph.
|
---|
127 | S: Scientific Notation: If values are 1000 or greater the graph will normally
|
---|
128 | display a description as...: (x10k), (x100k), etc.
|
---|
129 | - Scientific notation will be: (x10^2), (x10^3), etc.
|
---|
130 | V: Vertical graph.....: The default is horizontal display.
|
---|
131 | - Selecting this option will display data vertically
|
---|
132 | (graph bars running top to bottom).
|
---|
133 | There are no LAB routines running to check
|
---|
134 | There are no Interface's in the Auto-instrument file.
|
---|
135 | Checking Interface #
|
---|
136 | Routine for this Interface not started.
|
---|
137 | Interface check ... This may take a minute.
|
---|
138 | Interface data line is
|
---|
139 | NOT WORKING
|
---|
140 | OK
|
---|
141 | LET ME TRY ONCE MORE
|
---|
142 | Sending string for Interface #
|
---|
143 | Install Environment Check FAILED
|
---|
144 | Environment Check is Ok ---
|
---|
145 | Terminal Device is not defined
|
---|
146 | Please Log in to set local DUZ... variables
|
---|
147 | You are not a valid user on this system
|
---|
148 | You must have LAB V5.2 Installed
|
---|
149 | Don't Start/Collect
|
---|
150 | Don't Start
|
---|
151 | Rebuild
|
---|
152 | LA7-INST
|
---|
153 | Lab Auto Download
|
---|
154 | include uncollected accessions
|
---|
155 | No download routine (field #94)
|
---|
156 | Invalid download routine (field #94)
|
---|
157 | Invalid download routine label (field #93)
|
---|
158 | specified for AUTO INSTRUMENT:
|
---|
159 | Not Running^Running^Start/Restart Auto Download Job^Shutdown Auto Download Job^Shutdown Auto Download Job and Stop Collecting Accessions
|
---|
160 | Select action
|
---|
161 | accessions waiting checking
|
---|
162 | 1 - Start/Restart the auto download job after changes have been made to
|
---|
163 | file #62.4, AUTO INSTRUMENT, that affect auto downloading,
|
---|
164 | i.e. instrument auto download status changed, tests added/removed,
|
---|
165 | download code changed, etc. or if background job is not running.
|
---|
166 | 2 - Shuts down auto download background job and set flag to not start.
|
---|
167 | Accessions are still collected in list to be downloaded when
|
---|
168 | auto download job is started.
|
---|
169 | 3 - Same as 2 but stops collecting accessions to download.
|
---|
170 | Auto Download flag set to
|
---|
171 | Auto Download
|
---|
172 | - Queued to run as task #
|
---|
173 | - not tasked
|
---|
174 | No instruments currently flagged for automatic downloading.
|
---|
175 | Use build and download a load/worklist options to download.
|
---|
176 | Selection Method
|
---|
177 | Download from
|
---|
178 | No accessions found to download
|
---|
179 | Found
|
---|
180 | accessions that can be downloaded.
|
---|
181 | Ready to download
|
---|
182 | Done -
|
---|
183 | scheduled for downloading!
|
---|
184 | Select Option
|
---|
185 | Enter 'YES' to print the integrity report.
|
---|
186 | Lab Messaging File Integrity Checker
|
---|
187 | LA7*
|
---|
188 | Bad
|
---|
189 | cross-reference of
|
---|
190 | for entry
|
---|
191 | points to incorrect entry
|
---|
192 | points to missing entry
|
---|
193 | on entry
|
---|
194 | for entry:
|
---|
195 | Lab Messaging -Warning-
|
---|
196 | errors found in File #62.49, LA7 MESSAGE QUEUE.
|
---|
197 | LA7ERR-
|
---|
198 | G.LAB MESSAGING
|
---|
199 | Print LA7 File Integrity Report
|
---|
200 | Unable to obtain lock on entry
|
---|
201 | in file #62.49
|
---|
202 | entries in LA(
|
---|
203 | ) global - please check.
|
---|
204 | LA7ADL-
|
---|
205 | - Did NOT finish
|
---|
206 | - Still running
|
---|
207 | No reports on file!
|
---|
208 | Print LA7 Messaging Integrity Check
|
---|
209 | NO entries to print
|
---|
210 | Total number of entries:
|
---|
211 | Total number of errors:
|
---|
212 | Integrity Checker Started:
|
---|
213 | Integrity Checker Finished:
|
---|
214 | --- Lab Messaging Integrity Checker Report ---
|
---|
215 | Lab Messaging File Integrity Checker Report
|
---|
216 | For Date:
|
---|
217 | Do you wish to Add or Edit a Bedside Monitor
|
---|
218 | Enter BEDSIDE MONITOR INTERFACE NAME
|
---|
219 | Enter Bedside Monitor Name (ie. CareVue, Marquette)
|
---|
220 | Enter wards associated with this bedside monitor
|
---|
221 | There is an error with this entry.
|
---|
222 | already on file
|
---|
223 | Current Wards for
|
---|
224 | Current Bedside Monitors
|
---|
225 | Enter the name of the NEW Bedside Monitor
|
---|
226 | exists, please select a new name.
|
---|
227 | does not exist. Do you wish to add it?
|
---|
228 | Ward already on File, DELETE (Y/N) [N]
|
---|
229 | Must enter Y or N
|
---|
230 | LA7D CARELIFE SERVER
|
---|
231 | Unable to send out test result to CAREVUE, Protocol Server is not setup
|
---|
232 | ERROR IN SENDING LAB RESULTS TO
|
---|
233 | G.CARELIFE RESULT ERROR
|
---|
234 | There was an error in building an HL7 Lab Result Message for accession
|
---|
235 | of patient name:
|
---|
236 | The error was
|
---|
237 | Please make a note of it and take any actions that necessary
|
---|
238 | no MSH in 772
|
---|
239 | no config in 62.48
|
---|
240 | config is inactive
|
---|
241 | Log routine was called with a non-existant code number (
|
---|
242 | Lab Messaging Error Log
|
---|
243 | Nothing logged for Today!
|
---|
244 | Look at log for what date?
|
---|
245 | Nothing logged for
|
---|
246 | Select CONFIGURATION:
|
---|
247 | Print message text with error
|
---|
248 | Do you want the text of the message also printed with the error
|
---|
249 | Answer 'Y' or 'N'
|
---|
250 | Lab Interface Error Log
|
---|
251 | Report queued...
|
---|
252 | LA AUTO INST
|
---|
253 | >>>LA AUTO INST entry already exist...
|
---|
254 | >>>Adding HL7 DHCP APPLICATION file entry for LA AUTO INST...
|
---|
255 | LA AUTO INST^a
|
---|
256 | CH,MI
|
---|
257 | LA7-QRY
|
---|
258 | No results found for requested parameters
|
---|
259 | LA7-61
|
---|
260 | LA7-DN
|
---|
261 | LA7-LN
|
---|
262 | LA7-NLT
|
---|
263 | Unknown search code
|
---|
264 | AUTO-INST
|
---|
265 | Invalid patient identifier passed
|
---|
266 | No patient found with requested identifier
|
---|
267 | No laboratory record for requested patient
|
---|
268 | Database error - missing laboratory record for requested patient
|
---|
269 | Invalid list of subscripts: '
|
---|
270 | Are you using a barcode reader
|
---|
271 | Scan barcode
|
---|
272 | Patient/Accession Info (PD)
|
---|
273 | Scan Patient Name Barcode (PD1)
|
---|
274 | Patient Demographics not found
|
---|
275 | Select Shipping Configuration
|
---|
276 | Select SHIPPING CONFIGURATION:
|
---|
277 | Are you editing this entry as the
|
---|
278 | Is this entry used by the Collecting facility to ship specimens,
|
---|
279 | or by the Host facility to accept a shipment.
|
---|
280 | This determines which fields are edited in the file.
|
---|
281 | AGENCY CODE
|
---|
282 | Unable to proceed - institution
|
---|
283 | missing AGENCY CODE field
|
---|
284 | Select SHIPPING CONFIGURATION to COPY FROM:
|
---|
285 | Select SHIPPING CONTAINER:
|
---|
286 | Select SHIPPING METHOD:
|
---|
287 | Select SHIPPING CONDITION:
|
---|
288 | Copy a test profile from
|
---|
289 | Do NOT copy
|
---|
290 | If you want to duplicate a shipping configuration using another configuration
|
---|
291 | or build from the tests marked as catalog tests in the LABORATORY TEST file.
|
---|
292 | Select the appropiate option.
|
---|
293 | Tests already exist for this configuration!
|
---|
294 | Copying tests from configuration:
|
---|
295 | Copying tests from file #60 LABORATORY TEST to
|
---|
296 | FDA(629)
|
---|
297 | LA7DIE(629)
|
---|
298 | Clearing existing tests from configuration:
|
---|
299 | Select action to perform
|
---|
300 | Do you want to ship this manifest
|
---|
301 | Select TEST to Add:
|
---|
302 | User aborted
|
---|
303 | #################### #################### ####################
|
---|
304 | #################### #################### ####################
|
---|
305 | #################### #################### ####################
|
---|
306 | #################### #################### ####################
|
---|
307 | #################### #################### ####################
|
---|