source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0414.txt@ 1727

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

Internationalization

File size: 14.4 KB
Line 
1English French Notes Complete/Exclude
2Summary for division:
3For clinics with credit pair:
4For clinics with selected credit pair
5For clinics selected by name
6SDARR(
7Clinic Stop Code Pair:
8Detail for clinic:
9Ava.
10Pct.
11Credit Pair
12Sch. Wait
13Availability Date
14Enc.
15Appts Time
16Days Days
17Non-next Available Appointments
18Next Ava. 0-1 0-1 2-7 2-7 8-30 8-30 31-60 31-60 >60 >60
19Ava. Wait
20Days Wait
21Appts Time
22Next Ava. 0-1 0-1 0-1 2-7 2-7 2-7 8-30 8-30 8-30 31-60 31-60 31-60 >60 >60 >60
23Ava. Wait
24Days Wait Wait
25Appts Time1
26Appts Time1 Time2
27Ava. Date Wait Wait
28Scheduled Patient Name SSN Appointment Date Scheduling Request Type Ind. Desired F/U Time1 Time2
29REBOOK DATE
30Date extracted:
31No appointments scheduled during this date range were found.
32Next available
33Not-next ava-C/R
34Not-next ava-P/R
35Walk in appoint
36Multi booking
37Auto rebook
38Not-next available
39NOTE: TYPE '0' represents appointments scheduled during the report time frame not indicated by the user or by calculation to be
40'next available' appointments. TYPE '1' represents appointments defined by the user as being 'next available' appointments. TYPE
41'2' represents appointments calculated to be 'next available' appointments. TYPE '3' represents appointments indicated both by the
42user and by calculation to be 'next available' appointments. WAIT TIME is the average number of days from the date an appointment
43was scheduled to the date it is to be performed. The '% NNA' and '% NA' columns reflect percentage of appointments scheduled within
4430 days for 'non-next available' appointments (types 0 & 2) and 'next available' appointments (types 1 & 3), respectively.
45NOTE: The date range categories ('0-1', '2-7', '8-30', etc.) are based on the difference between the 'desired date' defined for the
46appointment and the date the appointment was performed. 'Wait Time' reflects the average of this difference for all appointments in
47each category. 'Follow up' status is determined by encounter activity to the same DSS ID credit pair as the appointment clinic
48within the previous 24 months.
49the date the appointment was performed. 'Wait Time2' reflects the average difference between the transaction date (the date the
50appointment was entered by the Scheduling package user) and the date the appointment was performed. 'Non-follow up' status is
51determined by the absence of encounter activity to the same DSS ID credit pair as the appointment clinic in the previous 24 months.
52NOTE: 'Next Ava. Ind.' Values--'0' = not indicated by the user or calculation to be a 'next available' appointment, '1' = defined
53by the user as a 'next available' appointment, '2' = indicated by calculation to be a 'next available' appointment, '3' = indicated
54by the user and by calculation to be a 'next available' appointment. 'Wait Time1' = the difference between the 'date desired' and
55the date of the appointment. 'Wait Time2' = the difference between the 'date scheduled' and the date of the appointment.
56Select PATIENT NAME:
57Correct Patient?
58No Patient Selected, OK to proceed?
59ACT REQ
60NOTE: 'APPT TYPE' Values--'0' = user indicated 'Not next available' and calculation indicated 'Not next available' used
61 '1' = user indicated 'Next available' but calculation indicated next available appt not used
62 '2' = user indicated 'Not next available' but calculation indicated next available appointment used
63 '3' = user indicated 'Next available' and calculation indicated 'Next available' apppointment used
64WAIT TIME: -------------- the difference between the 'DATE DESIRED' and 'APPT DATE/TIME'
65TIME TO APPT.: ----------- days from 'DATE SCHEDULED' to 'APPT DATE/TIME'
66APPT STATUS: N - No-show, CC - Canceled by Clinic, NA - No Show & Auto Rebook, CCA -Canceled by Clinic & Auto Rebook,
67 I - Inpatient, CP - Canceled by Patient, CPA - Canceled by Patient & Auto Rebook, NT - No Action Taken,
68 F - Future, CI - Checked In, COA - Checked Out/Action Required, CO - Checked Out
69No activity found within the parameters specified.
70 O U T P A T I E N T V I S I T S
71Act. Req./not accepted visits
72Transmitted, accepted visits
73 O U T P A T I E N T U N I Q U E S
74Act. Req./not accepted unique pts.
75Transmitted, accepted unique pts.
76<*> OUTPATIENT ENCOUNTER WORKLOAD STATISTICS <*>
77For encounter dates
78For station:
79***NONE ASSIGNED***
80Please select fiscal year
81XMITED OE MT=U RPT
82SCDX MTU
83SCDX ASORT
84Outpatient Encounters Scanned
85Outpatient Encounters Reported
86Patient Count
87ACRP MT=U STATS
88Transmitted Outpatient Encounters with Means Test = 'U'
89Medical Ctr
90Encounter Date
91MT Indicator
92* - Transmitted Outpatient Encounter
93No 'action required'/not accepted unique patients identified.
94 'action required'/not accepted unique patient
95<*> LIST OF 'ACTION REQUIRED'/NOT ACCEPTED UNIQUE PATIENTS <*>
96Would you like to print a detailed list of activity for a division
97 WARNING: Selection high activity areas will result in lengthy output!
98Select type of list
99Select transmission status for CHECKED OUT encounters
1005:Transmitted, no acknowledgment;6:Transmitted, rejected;7:Transmitted, error;8:Transmitted, accepted
101Select Medical Center division for detail:
102 Required for patient detail!
103<*> DETAILED LIST OF DIVISION
104Encounters with
105Transmission status:
106No records found in this category.
107 uniques identified.
108 visits identified.
109 encounters identified.
110Outpatient Encounter Workload Statistics
111*** Additional Detail Selection ***
112Break out workload by clinic group
113Specify if subtotals by encounter location CLINIC GROUP should be provided.
114List facility 'action required'/not accepted unique patients
115Outpatient Encounter Workload
116SDZ(
117An error has occurred.
118CURRENT USER
119Scheduling User Data Retrieval
120System Default
121Setting User Query Default
122NULL XMT POINTER
123No (Deleted) Outpatient Encounter entry found.
124Select Patient name, Clinic name, or Error Code:
125Enter as P.patient name, C.clinic name, or E.error name
126Searching for patient
127Searching for Clinic
128Searching for Error Code
129Answer with Yes to accept, or No to ignore
130Enter P.patient name to select a specific patient,
131C.clinic name to select a specific clinic, or E.Error Name
132to select a specific error.
133If selecting a specific error by its description it may be
134necessary to enter more than three characters(Ex. E.Abxxxx).
135Because this is a descriptive field, case sensitivity applies.
136If just a name is entered, any matches will be displayed in
137patient, clinic, error code order. You will have the option
138of selecting or ignoring the choice.
139Scheduling Option^1N
140OPC MENU NOW USED!
141OPTIONS MUST BE INDIVIDUALLY CALLED!
142Special Survey functionality is obsolete!
143SUPERVISOR OPTIONS NO LONGER ACCESSIBLE!
144Environmental Checks Started...
145Environmental Checks Completed.
146Passed
147 on the 'SDAM APPOINTMENT EVENTS' protocol
148is a dangling pointer and must be corrected/removed
149before patch SD*5.3*132 can be installed.
150Please contact the Customer Support Help Desk for assistance.
151 -> At least one patch check failed.
152 -> All patch checks passed.
153not Ok
154SD*5.3*132 OVERRIDE FLAGS
155PACKAGE NAME
156NEEDED VERSION
157REASON TEXT
158REASON NUMBER
159Information On Patches Needed For SD*5.3*132 Install
160Patch or
161...invalid namespace passed!
162 ...override set for '
163 ...override killed for '
164Post-Init Started...
165Post-Init Finished.
166 >>> Deleting MAS PARAMETERS (#43) fields...
167 >>> Deleting HOSPITAL LOCATION (#44) fields...
168 >>> Deleting APPPOINT STATUS UPDATE LOG (409.65) fields...
169 >>> Setting 'ACG' cross references...
170 >>> Queuing task to set 'AG' cross reference.
171SDACS CGSCLIST
172AG Cross Reference Being Set
173 -> Option 'SDACS CGSCLIST' has been placed out of service.
174Setting 'AG' Cross Reference
175 >>> Option 'SDACS CGSCLIST' is back in service.
176Setting of 'AG' Cross Reference Task Information
177 >>> Package Override Flag Information
178 -> Override flag set for '
179 -> No package override flags set.
180 -> Fields already deleted.
181SD-SITE-PAIT
182 Unable to update FACILITY NAME field of file 771
183 Edit entry SD-SITE-PAIT manually
184 HL7 Parameters Updated Successfully
185RE-LINKED
186Re-Linked successfully:
187Error has occurred.
188Please make a note of the following:
189Fix -1 Outpatient Encounters
190Task queued: #
191SDVISIT FIX
192COUNT ONLY
193Bad encounter entry passed
194Unknown Clinic
195ERROR OCCURRED
196SD TO PCE RESYNC
197>>>> Encounter Clean Up Tool for -1 Visit ID's [
198DUZ is not defined.
199No package with 'SD' namespace exists on the system.
200The Unique Visit ID cleanup has run to completion.
201 End Time:
202 Run Mode:
203Count Only
204Fix Entries
205 >>> Task Stopped by user. <<<
206Total number of Outpatient Encounter entries
207that will be
208Note: Child encounters re-linked as part of parent
209 re-linking process are not listed below nor
210 counted in the total above.
211Message Format:
212 Piece Description
213 1 Status of update
214 2 Internal Entry Number of Outpatient Encounter file
215 3 Internal Entry Number of Parent Outpatient Encounter file
216 4 Internal Entry Number of Visit file
217 5 Patient Name
218 6 Encounter Date/Time
219 7 Hospital Location
220Unique Visit ID Cleanup is Complete
221SDVISIT MSG
2221:Count Only;2:Fix Entries
223Select update mode
224You are running this routine in scan mode, which will only identify
225the problems corrected. Please select a device (queueing allowed) so
226that a listing of what would have been done can be obtained.
227ACRP cleanup of files 409.73, 409.74, and 409.75
228Please enter the date/time that you would like this clean up queued to
229run. A summary of what was done will be sent to you and the
230recipients of the SCDX AMBCARE TO NPCDB SUMMARY bulletin.
231** Unable to schedule correction **
232This routine will clean up dangling pointers and orphan entries within
233the ACRP transmission files. The following actions/checks will be
234(1) Entries in the Transmitted Outpatient Encounter file (409.73)
235 that do not have a valid pointer to the Outpatient Encounter
236 file (#409.68) or the Deleted Outpatient Encounter file
237 (#409.74) are deleted.
238(2) Entries in the Transmitted Outpatient Encounter file that have
239 been rejected by the Austin Automation Center and do not have an
240 entry in the Transmitted Outpatient Encounter Error file
241 (#409.75) are marked for re-transmission.
242(3) Entries in the Deleted Outpatient Encounter file that do not
243 have a corresponding entry in the Transmitted Outpatient
244 Encounter file are deleted.
245(4) Entries in the Transmitted Outpatient Encounter Error file that
246 do not have a valid pointer to the Transmitted Outpatient
247Scanning of the Transmitted Outpatient Encounter, Deleted Outpatient
248Encounter, and Transmitted Outpatient Encounter Error files for known
249problems started on
250The following entries in the Transmitted Outpatient Encounter
251file (#409.73) will be acted upon when run in fix mode
252,0) has bad pointer to Outpatient Encounter file
253,0) has bad pointer to Deleted Outpatient Encounter file
254,0) rejected with no reason on file (entry in 409.75)
255Last entry in Transmitted Outpatient Encounter file checked >>
256 entries where checked
257 would have been marked for retransmission
258 would have been deleted
259 have bad Outpatient Encounter pointers
260 have bad Deleted Outpatient Encounter pointers
261The following entries in the Deleted Outpatient Encounter
262file (#409.74) will be deleted when run in fix mode
263,0) not in Transmitted Outpatient Encounter file
264Last entry in Deleted Outpatient Encounter file checked >>
265 entries where checked and
266Error file (#409.75) will be deleted when run in fix mode
267,0) has bad pointer to Transmitted Outpatient Encounter file
268Scan ended on
269Use the entry point FIX^SD53105A to run in fix mode
270Use the entry point SCAN^SD53105A to re-run in scan mode
271SD53105-BULL1
272*** Note that process was asked to stop and did not run to completion ***
273Process began on
274 and completed on
275 entries in the Transmitted Outpatient Encounter file were
276checked and
277 of them were deleted because of bad pointers to the
278Outpatient Encounter file and
279 of them were deleted because of bad
280pointers to the Deleted Outpatient Encounter file. In addition to this,
281 entries were marked for re-transmission because they were rejected and
282did not contain a reason for rejection in the Transmitted Outpatient
283Encounter Error file.
284 entries in the Deleted Outpatient Encounter file were
285 of them were deleted because an associated entry in the
286Transmitted Outpatient Encounter file could not be found.
287were checked and
288Transmitted Outpatient Encounter file.
289ACRP - SD*5.3*105
290>>> Deleting obsolete triggers on the TRANSMISSION REQUIRED field
291 (#.04) of the TRANSMITTED OUTPATIENT ENCOUNTER file (#409.73).
292 Trigger cross reference number
293>>> Updating the ERROR CODE DESCRIPTION field (#11) of
294 the TRANSMITTED OUTPATIENT ENCOUNTER ERROR CODE file
295 (#409.76) for error codes 420 and 105. Definitions
296 were modified to reflect receipt of data by NPCD
297 after close-out.
298Date of Encounter is invalid, after date of transmission, or after close-out.
299Event Date is missing, invalid, after processing date, or after close-out.
300 *** The following error occurred while updating descriptions ***
301>>> Checking for existance of a valid mail group in the
302 LATE ACTIVITY MAIL GROUP field (#217) of the MAS
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.