source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0132.txt@ 1749

Last change on this file since 1749 was 604, checked in by George Lilly, 15 years ago

Internationalization

File size: 11.7 KB
Line 
1English French Notes Complete/Exclude
2CHECK 773 AC XREF
3HL7DevelopmentTeam@med.va.gov
4LINK (870) CHECKS
5Environment check OK...
6Warning
7Press RETURN to
8There are inbound queues with un-processed messages. Before patch HL*1.6*109
9can be installed, the inbound queues must be empty. You may continue loading
10these patches. But, remember to clear the inbound queues before loading.
11(To clear the queues, start one or more incoming filer(s) to process the
12messages until there are no messages in the queue.)
13incoming filer(s) to process the messages until there are no messages in the
14queue. Then, try to install patch HL*1.6*109 again.
15Conversion already run!
16Post-init will identify all incomplete messages associated with TCP links
17These incomplete messages were a result of Network errors
18encountered by the DIRECT CONNECT API.
19These messages will be removed from the outbound TCP queue.
20Scanning for incomplete messages...
21No messages in the outbound TCP queue.
22Installation of PROTOCOLS not performed
23Installation of LIST TEMPLATES not performed
24Running of file conversions not performed
25Select output device for file conversion:
26Running of the file conversions not performed
27FILE CONVERSIONS REQUIRED BY INSTALLATION OF HL7 V1.6
28** Running of file conversions could not be queued **
29** File conversions will be run interactively **
30Running of file conversions queued as task number
31Task will begin execution on
32- File conversions started on
33Copying entries from HL7 NON-DHCP APPLICATION PARAMETER file (#770)
34to HL7 APPLICATION PARAMETER file (#771)
35** Conversion halted **
36** Unable to lock HL7 APPLICATION PARAMETER file **
37** Use the entry point REQUEUE^HLPOST to requeue the file conversions **
38** Unable to lock HL7 NON-DHCP APPLICATION PARAMETER file **
39* Entry number
40 does not have an application name
41* Unable to copy
42** Conversion of files has been asked to stop **
43Purging data from HL7 MESSAGE TEXT file (#772)
44Converting newly defined fields in HL7 MESSAGE TEXT file (#772)
45* Unable to lock entry number
46 - entry not converted
47 does not have a date & time of message
48- File conversions completed on
49Do you wish to continue ?
50Post-init was already run on
51This post-init has already been run. Answering 'YES' will allow you to
52selectively re-run portions of the post-init. If you do not want to do
53this, answer 'NO' (the default response).
54Do you want to re-install PROTOCOLS ?
55This package distributes a set of protocols which may have already
56been installed. Answering 'YES' (the default and recommended response)
57will re-install these protocols.
58Do you want to re-install LIST TEMPLATES ?
59This package distributes a set of list templates which may have already
60will re-install these list templates.
61Do you want to re-run the file conversions ?
62Installation of this package requires that a set of file conversions be
63run. Answering 'YES' (the default and recommended response) will allow
64these conversions to be re-run. Answer 'NO' if the file conversions
65have already run to completion.
66Starting Pre-Init
67RESULTS RPT/STATUSCHNG-DATE/TI
68.01///RESULTS RPT/STATUS CHNG-DATE/TIME
69Pre-Init Finished
70S.HL SERVER
71Missing subscription control number.
72Missing logical link.
73Invalid Subscription Control number
74Invalid Logical Link
75Invalid logical link
76Invalid receiving application.
77Note: You must select a Non-DHCP Application for which an HL7 Device has
78been defined.
79HL7 Message Processor for
80 is already tasked.
81-1^Did not pass valid pointer to Message Text file (#772)
82Application Reject
83Application Error
84Error During Receipt of Acknowledgement Message
85 - Application Reject
86 - Application Error
87Failed to create an Event in STATUS^HLTF0:
88Application Error Text:
89Initial Message in this transaction protocol:
90 Initial Message ID:
91 Logical Link of Initial Message:
92 Inital Message Type:
93 Inital Message Event:
94HL(772
95 at GENERATE^HLTP entry point
96 at PROCESS^HLTP0 entry point
97AA,CA
98 at GENACK^HLTP1 entry point
99 at PROCACK^HLTP0 entry point
100MTP_ETP
101Missing MSA segment
102Incorrect sending app.
103INIT-1
104INIT-2
105 at CHK^HLTPCK1 entry point
106Field Separator Missing
107Invalid Field Separator
108Encoding Characters Missing
109Invalid Encoding Characters
110Invalid Message Header Segment
111ACK,ADR,MCF,MFK,MFR,ORF,ORR,RRA,RRD,RRE,RRG,TBR
112MSA Segment Missing
113AL,NE,ER,SU
114Invalid accept ack type
115Invalid application ack type
116Missing HL7 Version
117Original Outgoing Message not found
118Event Protocol pointer (field #772,10) missing
119Event Type REQUIRED
120Invalid Event Type
121Invalid Message Structure Code
122Missing Sending Application
123Invalid Message Control ID in MSA Segment
124Event Protocol not found
125Invalid Receiving Application for this Event
126Missing required receiving facility
127Receiving Facility/App Parameter mismatch.
128Receiving Facility mismatch.
129Missing required sending facility
130Sending Facility/App Parameter mismatch.
131Unrecognized domain in sending facility
132Invalid HL7 Processing ID
133Cannot validate PROCESSING ID
134Processing ID Mismatch with Event Driver
135Processing ID Mismatch with Site Parameters
136Invalid access code
137Invalid HL7 Version for Receiving Application
138Event Protocol pointer (field #773,8) missing
139Event Type Required
140Unrecognized/ambiguous domain in sending facility
141HL7 Message
142Unable to determine receipients for mail message.
143Unable to transmit HL7 message due to the following Application Error:
144Non-DHCP
145 Application Name
146Invalid Non-DHCP Application Name
147Invalid DHCP Application Name
148DON'T ADD. COLLECT3~HLUCM003
149HLUCM
150HLUCM Data
151Print Totals Report & Debug Data to Screen
152OK! No ^TMP(TOTALS,$J) totals report will be printed...
153No ^TMP($J,
154) debug data exists...
155Press RETURN to restart, or '^' to exit...
156Debug Data from ^TMP($J,
157Print raw DEBUG DATA (Y/N): Yes//
158Print filtered DEBUG DATA (Y/N): Yes//
159You will be allowed to print report totals (from ^TMP(TOTALS,$J), and/or you
160may print the debug data (in ^TMP($J,
161Report Totals from ^TMP(
162Print REPORT TOTALS (Y/N): Yes//
163Include subtotals (Y/N): NO//
164Printing from
165Enter subscript holding the ^TMP(TOTALS,$J) data:
166You must pass in the initial subscript and $JOB number...
167Some entries were not included in the totals. There are 3 possible reasons
168for entries being excluded: (1) The beginning time of a message or unit is
169before the report's start time, (2) The number of seconds to transmit the
170message is over 1799 seconds, and (3) The protocol or namespace doesn't meet
171Failure Reason
172Beginning time too early
173Excessive xmit time
174Prot/Nmsp mismatch
175Totals:
176ZZZ~0
177DEBUG GLOBAL
178INVALID START TIME
179INVALID END TIME
180END TIME PRECEDES START TIME
181BOTH NAMESPACES(S) AND PROTOCOL(S) MUST BE PASSED SPECIFICALLY
182INVALID NAMESPACE PARAMETER
183INVALID PROTOCOL PARAMETER
184CAN'T FIND PROTOCOL
185Display of ^TMP($J,
186Type Totals
187Enter text in messages to include and exclude...
188Restrict # messages: 999//
189No data exists...
190No matching entries found...
191 matching entries displayed...
192 entries skipped...
193Every parent node that includes one of the EXCLUDE values that you enter now
194will not be included in the entries displayed.
195Every parent node that doesn't include one of the INCLUDE values that you
196enter now will not be included in the entries displayed.
197 XTMP-stored Reports
198Run-time
199API Call
200You may choose to print the totals report from stored XTMP data if you like.
201If so, enter the number of the XTMP report from above now. (Otherwise,
202press RETURN.)
203Enter XTMP Report#:
204STARTandEND
205TO ID
206NMSP(
207HEC
208VAFC ADMIT
209VAFC ADT
210VAFH A
211VAFH CLIENT A
212REMOTE RPC^
213Print T nodes(Y/N): No//
214Print X nodes(Y/N): No//
215Print U nodes(Y/N): Yes//
216No data found. Press RETURN to continue...
217About to print ^TMP(
218,$J) data report. Press RETURN...
219 Total Total Total Main
220#Chars #Msgs #Sec Sort Sub1 Sub2 Sub3
221DATA(
222HL7 DHCP Application Parameters
223HL7 Non-DHCP Application Parameters
224HL7 Message Types
225HL7 Segment Names
226HL7 Data Types
227HL7 Version Numbers
228HL7 Fields
229Log of HL7 Transmissions in Awaiting or Pending Status
230EZ,?
231Log of Failed HL7 Transmissions
232Select the Non-DHCP Application for which you wish to start/stop the HL7 log
233of transmissions.
234You must define an HL7 Device for this Non-DHCP Application before you can
235start the log.
236The HL7 log is currently turned
237Do you want to purge existing log entries
238Don't
239 (#772,15), is set to 1.
240queue job
241start purging
242, or enter '^' to exit...
243 no task started...
244HLPDT(
245Purge HL7 message text on or before
246 queued to run now...
247 Queuing of Purge task failed.
248NO-LOCK
249 entries purged...
250Looping through file 773...
251START-773
252END-773
253Looping through file 772...
254START-772
255END-772
256ABORTED-TASKMAN
257HLUOPT2
258HLUOPT2 Message Body Deletion
259HLUOPT1 9999999.999999
260HLUOPT1
261As purging jobs run, they record critical information in the ^XTMP global for
262later review. (This information is updated every two minutes.) You can view
263purge information now...
264Option #1 displays all available purging data, for the last job.
265Option #2 displays the most valuable purging data, but not all data. This
266option includes data for the last purging job, plus previous puring jobs.
267Option #3 displays purging times and totals in a graphic representation.
268 Task-Number Start-Time Timestamp Finish-time 772@ 773@ Time-NOW
269There is no currently running purge job...
270Any old jobs that exist will be shown above. The current (or last) purge job
271is shown below. The information on each line will automatically refresh
272 seconds (or whenever you press RETURN.)
273Note!!
274 Enter '^' when you are ready to exit.
275Current (or last) purge job...
276HLUOPT1 9999999.99999
277Recent purge runs...
278HLUOPT1 Purging
279The '^HL(
280)' lock is already owned by another purge job! So, this
281purge job cannot be started.
282Successfully Completed
283 Enter inclusive date up to which to purge SUCCESSFULLY COMPLETED
284 The suggested cutoff date to purge 'Successfully Completed' messages
285 is seven days prior to today.
286 Must be on or before
287Awaiting Acknowledgement
288 The suggested cutoff date to purge 'Awaiting Acknowledgment' messages
289 is thirty days prior to today.
290 of status (except ERROR status)
291 The suggested cutoff date to purge all messages (except for 'Error' messages)
292 is 90 days prior to today.
293 Do you also want to purge messages with an ERROR status
294 Enter 'Yes' to purge entries whose status is 'error'.
295 If you have reviewed/resolved the cause of the problem of those
296 entries with an 'error' status answer 'Yes'. Otherwise answer 'No'.
297 WARNING: You should have investigated all errors because purging
298 these messages permanently removes them from the system.
299 Enter inclusive date up to which to purge ERROR
300 The suggested cutoff date to purge 'Error' messages
301 Would you like to queue this purge?
302 If run in the foreground, you will see dots and a total count.
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.