source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0127.txt@ 1556

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

Internationalization

File size: 10.0 KB
RevLine 
[604]1English French Notes Complete/Exclude
2HBPC Patient Visit Data Report
3(continued from previous page...)
4 Visit Data
5Visit Date:
6Prov No.:
7Prov Name:
8CPT Code:
9HBPC Visit Data Date Range Report
10Visit Data by Date Range
11All Providers Visit
12Last 4:
13Diagnosis:
14HBPC Patient Discharge Data Report
15Patient Discharge Data
1620. Primary Diagnosis @ D/C:
17 2. Discharge Date:
1821. Secondary Diagnoses @ D/C:
19 4. Marital Status @ Discharge:
20Hearing @ Discharge:
21 5. Living Arrangements @ D/C:
2223. Expressive Communication @ D/C:
23 6. Discharge Status:
2424. Receptive Communication @ D/C:
25 7. Transfer Destination:
26 8. Type of Destination Agency:
27Dressing @ Discharge:
28 9. Cause of Death:
29Toilet Usage @ Discharge:
30Transferring @ Discharge:
31Eating @ Discharge:
32Walking @ Discharge:
3326. Bowel Continence @ Discharge:
34Bladder Continence @ Discharge:
3528. Adaptive Tasks @ Discharge:
3629. Behavior Problems @ Discharge:
3731. Mood Disturbance @ Discharge:
3832. Caregiver Limitations @ D/C:
3933. Person Completing Discharge:
40Date Discharge Completed:
41case manager
42case managers
43Case Manager
44Select Admissions or Discharges
45Enter 'A' to include Admissions on the report, 'D' to choose Discharges.
46HBPC
47Date Range Report
48 by Date Range
49 found for Date Range selected.
50HBPC Provider File Report
51Provider File
52Grade
53Provider Name
54Degree
55HBHC Team
56Prov #
57be transmitted.
58No data on file to transmit.
59This option re-transmits the same data included in the last file created for
60transmission to Austin. It should only be run under special circumstances and
61should be coordinated with Austin. Do you wish to continue
62A 'Yes' response will re-transmit the file to Austin. A 'No' response will
63return to the menu without any data being transmitted.
64Re-transmission request has been queued.
65HBPC Re-Transmit
66HBHC Site:
67XXX@Q-HBH.VA.GOV
68This patient has no records containing errors on file.
69Evalution/Admission
70Another user is editing this
711 for Admit
722 for Reject
73This record contains
74 data. Are you sure you want
75Admit/Reject Action field ('Yes' will delete the
76Admit/Reject Action field must either contain
77 or the
78data MUST be deleted by responding 'Yes'.
791 or 2 for Transfer
804 for Died on HBHC
813, 5 or 9 for Discharge
82Discharge Status field ('Yes' will delete the
83Discharge Status field must contain
84Beginning Report Date:
85Ending Report Date:
86Ending Report Date must be closer to today than the Beginning Report Date
87HBPC Team:
88==== End of Report ====
89Transmit Status Flag must be reset before editing this record is allowed.
90Due to automatic Form 6 Correction Record generation, Transmit Status Flag
91CANNOT be reset without this information. Contact IRM to enter this
92information using FileMan.
93Do you wish to reset the Flag
94A 'Yes' response will reset the Transmit Status Flag field data. A 'No'
95response will return you to the menu without resetting the Transmit
96Status Flag.
97BIRTH YEAR:
98SEX:
99Male (1)
100Female (2)
101RACE:
102Black (2)
103American Indian/Alaskan Native (4)
104White (1)
105Hispanic Origin (3)
106Asian/Pacific Islander (5)
107Not Determined (9)
108RACE: Obsolete Field Jan 2003
109*** Contact MAS if value is incorrect. ***
110Do you wish to include ALL
111 on the report
112A 'Yes' response will include ALL
113. A 'No' response will
114prompt for an individual
115Select HBPC
116 Census Report
117Case Census
118Street Address
119City
120No data found for
121 by Date Range selected.
122Patient visit records with pseudo social security numbers (SSNs) exist.
123Print the 'Pseudo Social Security Number Report' located on the HBHC Reports
124Menu to obtain a list of patients with invalid SSNs. HBHC must determine
125what corrective action is appropriate to eliminate these records from the
126HBHC Information System.
127Note: Please use Appointment Management to Correct Visit Errors. Run
128Edit Form Errors Data option when corrections are complete.
129CPT Code must contain 5 numerics for use in a range.
130Will CPT Codes selected be a Range of codes (Y/N)
131Enter 'Y' for Yes, a range of CPT Codes is requested, 'N' for No, individual CPT codes will be selected.
132Select Beginning CPT Code:
133Select Ending CPT Code:
134Ending CPT Code in range must be greater than the Beginning CPT Code
135 (filed for transmit) in ^HBHC(631)
136Processing Admission/Form 3 Data
137Processing Correction/Form 6 Data
138Processing Discharge/Form 5 Data
139Data on file has been transmitted to Austin; duplicate transmission not allowed.
140Transmit Report will be printed on device:
141HBPC Transmission
142Transmission request has been queued. Task number:
143Processing Visit/Form 4 Data
144Beginning Post-Initialization Process
145, Admission Date (#17) field, cross-reference, in HBHC
146Patient (#631) file, to clean up possible dangling cross-reference.
147 reindexing complete.
148- Locating patient records in HBHC Patient (#631) & HBHC Visit (#632) files
149that have a pseudo social security number (SSN). These are invalid for HBHC
150purposes. This routine also locates & deletes any records in the HBHC
151Transmit (#634) file containing pseudo SSNs. Two reports of Patient Names are
152printed listing those patients that must be resolved. See Patch Narrative
153for detailed resolution instructions.
154Please select a PRINTER for device. HBHC will need these Pseudo SSN Reports
155to resolve the invalid SSNs.
156HBHC Pseudo SSN Report
157No patients found with pseudo SSNs. No resolution required!!
158Pseudo SSN Patch Related
159Invalid Message Type
160Invalid Header Segment
161Invalid Receiving Application
162Receiving Application is Inactive
163Invalid Sending Application
164Invalid Sending Facility
165Invalid Receiving Facility
166Invalid HL7 Version
167Invalid HL7 version for Receiving Application
168Inappropriate HL7 Processing ID
169Invalid Message Type for Receiving Application
170No Signature Code on File
171Invalid Electronic Signature Code
172FHS,BHS,MSH,MSA
173FHS,BHS,MSH
174FHS,BHS
175SKIP_EVENT
176at SENDACK^HLCS entry point
177Entry in HL COMMUNICATION SERVER PARAMETER file (#869.3) has
178not been made. Entry must be made in order to start execute
179this option.
180Default number of incoming servers has not been entered into
181the HL COMMUNICATION SERVER PARAMETER file (#869.3). Will use
182a value of
183Default number of incoming servers is set to
184 incoming servers are currently running. No more
185incoming servers will be started.
186Default number of outgoing servers has not been entered into
187Default number of outgoing servers is set to
188 outgoing servers are currently running. No more
189outgoing servers will be started.
190Incoming filer queued as task number
191Unable to queue incoming filer
192Outgoing filer queued as task number
193Unable to queue outgoing filer
194No incoming filers are running
195 has been asked to stop
196No outgoing filers are running
197Are you sure you want to stop all incoming filers ?
198Stopping all incoming filers will prevent messages being
199received through Logical Links from being passed to the
200appropriate application. Answer 'YES' if you really want
201this to occur.
202Incoming filers will not be stopped
203Please wait while all incoming filers are asked to stop ...
204All incoming filers have been asked to stop
205Are you sure you want to stop all outgoing filers ?
206Stopping all outgoing filers will prevent messages from
207being transmitted to external systems through Logical
208Links. Answer 'YES' if you really want this to occur.
209Outgoing filers will not be stopped
210Please wait while all outgoing filers are asked to stop ...
211All outgoing filers have been asked to stop
212HL7 Incoming Filer
213HL7 Outgoing Filer
214Unable to create/find entry in HL COMMUNICATION SERVER
215PARAMETER file (#869.3). Entry must exist in order for
216the incoming & outgoing filers to run. Use FileMan to
217create an initial entry for editing.
218Initial entry in HL COMMUNICATION SERVER PARAMETER file
219(#869.3) has been created.
22011Default number of incoming filers;12Default number of outgoing filers
221Okay to shut down all Links and Filers
222Shutdown Aborted!
223Shutting down all Links and Filers...
224Shutdown and restart ALL AUTOSTART links and filers. Okay
225RESTART Aborted!
226Restarting all Autostart-Enabled Links and Filers...
227HLJ(870,
228Halting
229Shutdown
230Enabled
231 Low Level Protocol
232ERROR
233Make Connection
234-1^Inital Connection Failed
235Got Connection
236HELO
237-1^Initial HELO Failed
238Send Data
239-1^No 220 after send
240TURN
241-1^No 220 after Turn
242-1^No DATA cmd
243QUIT
244HCS-HOME
245-1^Missing input paramerter
246-1^Bad Logical Link
247Client Setup
248500 Bad CMD:
249 Ready for
250Get Data
251PARAM
252Data Sent
253Cmd Read
254Cmd Send
255Server Setup
256DECODE
257500 Data error
258HLJ(773,
259HLJ(772,
260DATA PARAM=
261PARAM=
2621 Out of sync:
263Disconnect
264Logging IO to ^XTMP('HL',N
265Slave Check
266Master Check
267Slave Request
268Slave Ack0
269Slave Read Data
270Slave Write NAK
271SEND NAK
272Master Check Queue
273*Out Queue Empty
274Master Bid
275Master Bid Wait Ack0
276WAIT ACK
277Master Write
278WRITE:
279Write:
280Master Wait for Ack
281WAITING ACK
282HL7 Debug Log
283READ:
284FINISHED READ FOR DLE:
285FINISHED READ FOR ENQ:
286Type Q to Quit:
287In State :
288data set hang-up
289INCOMING MESSAGE
290READ ACK
291VALIDATE NACK
292LLP-NACK
293HLTRANS=
294HLC1=
295HLBLOCK=
296HLC2=
297HLXOR=
298communication server-wide
299in queue
300LLP-ACK
301input queue
302IN STATE
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.