source: internationalization/trunk/TranslationSpreadsheets/WV-DIALOG-0390.txt@ 1435

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

Internationalization

File size: 11.9 KB
RevLine 
[604]1English French Notes Complete/Exclude
2Error in Process
3Request Sent
4Awaiting Response
5 - No patient data query exists for this patient.
6No Data Returned Due To:
7There were no exceptions found.
8Enter an exception type to view:
9Not a valid selection.
10exceptions that need processing.
11The following exception types are handled by this option:
12Required field(s) Date of Birth or Name missing
13SSN Match Failed
14Name Doesn't Match
15Death Entry on MPI not in VISTA
16Death Entry on Vista not in MPI
17Death Entries on MPI and Vista DO NOT MATCH
18Potential Matches Returned
19no exceptions found
20MISSING MSH SEGMENT
21ICN:
22From Station:
23APPLICATION ACKNOWLEDGMENT TO MSGID:
24MISSING PARAMETER
25RG FACILITY INTEGRATION SERVER
26ERROR ENCOUNTERED BY HL7 WHILE SENDING FACILITY INTEGRATION MESSAGE:
27MISSING PARAMETER NEEDED TO BUILD FACILITY INTEGRATION MESSAGE
28UNABLE TO SEND FACILITY INTEGRATION MESSAGE - PATIENT LACKS ICN
29SITE NOT FOUND IN INSTITUTION FILE
30Facility Integration Message not sent to station #
31RG FACILITY INTEGRATION CLIENT^
32LEGACY STATION NUMBER NOT FOUND UNIQUELY IN THE INSTITUTION FILE!
33PRIMARY STATION NUMBER NOT FOUND UNIQUELY IN THE INSTITUTION FILE!
34RG FACILITY INTEGRATION CLEANUP
35Looking for patients with legacy site as CMOR ...
36Looking for patients with legacy site as treating facility ...
37Returned mail message number:
38HL7 Message sent:
39*** HL7 Message NOT sent! :
40Patient DFN:
41Patient ICN:
42Treating Facilities:
43Process patient
44** Patients with Legacy Site as CMOR **
45** Patients with Legacy Site as Treating Facility **
46** END OF MPI/NDBI SITE CLEANUP REPORT **
47MPI/NDBI SITE CLEANUP REPORT FROM
48Primary Station:
49 Legacy Station:
50Count of Patients Found with Legacy Site as CMOR:
51MPI/PD at
52G.MPIF EXCEPTIONS
53MPI/NDBI SITE CLEANUP
54INPUT PARAMETER MISSING, TAG=XCHANGE,RTN=RGFIPM
55INSTITUTION LOOKUP FAILED, STATION# =
56ERROR CHANGING CMOR TO
57FAILURE TO DELETE TREATING FACILITY =
58FAILURE TO ADD SUBSCRIPTION FOR STATION# =
59FACILITY INTEGRATION ERROR:
60STATION#
61PATIENT LOOKUP BASED ON ICN FAILED
62LOCAL DATABASE HAS INCORRECT ICN CHECKSUM
63SENT INCORRECT ICN CHECKSUM
64ERROR ENCOUNTERED WHILE PROCESSING FACILITY INTEGRATION MESSAGE
65SITE INTEGRATION MSG TO CMOR NOT FROM LEGACY SITE
66SITE INTEGRATION MSG NOT FROM CMOR, CMOR IS
67MISSING STATION NUMBER IN MSH SEGMENT FOR SENDING SITE
68EVENT REASON CODE NOT 51
69MISSING ICN IN PID SEGMENT
70MISSING LEGACY STATION # IN NTE SEGMENT
71MISSING PRIMARY STATION # IN NTE SEGMENT
72 From Station:
73MISSING SEGMENT:
74ERROR ENCOUNTERED WHILE PROCESSING FACITLIY INTEGRATION MESSAGE: MISSING CMOR
75Facility Integration Message not sent to MPI, no MPI link identified in CIRN SITE PARAMETER file (#991.8)
76Facility Integration Message not sent to primary site, station #
77RG FACILITY INTEGRATION CLIENT
78HL7 Message Exception Report
79MPI/PD Exception:
80MPI/PD exception notification
81RGMSH(773,
82RG MPI SERVER EXCEPTION
83**MPI/PD EXCEPTION**
84EXCEPTION TYPE
85OPTIONAL TEXT
86SITE OF OCCURRENCE
87SITE REPORTING
88DATE/TIME REPORTED
89**PATIENT DATA**
90TREATING FACILITY
91DATE LAST TREATED
92EVENT REASON
93S.MPI EXCEPTION SERVER@
94MPI/PD EXCEPTION
95MESSAGE ID
96EVENT TYPE
97LOGICAL LINK
98-1^INVALID ICN CHECKSUM
99RGSEG(RGPC)
100RGSEG(RGPC,RGPC1)
101RGSEG(RGPC,RGPC1,RGPC2)
102SCN_REQ
103 Bad DFN,
104 See the Exception Handling document on the MPI/PD web site.
105 Mismatched SSN,
106 Bad CMOR
107 for DFN#
108 Mismatched CMOR,
109 Does not exist in patient database.
110 Unable to send Subscription Request from
111. This is not a MPI/PD site.
112 Unable to send Subscription Request to
113REQUIRED PARAMETERS MISSING IN STUB
114RG PT SUBSCRIPTION REQUEST
115RG PT SUBSCRIPTION RECEIVER^
116SUBSCRIPTION REGISTRY
117 Unable to send Subscription. Duplicate station number of
118 in Institution file.
119 Unable to send Subscription from
120. This is not a MPI/PD Site.
121 Unable to send Subscription to
122 Unable to send Subscription Request from,
123 Unable to send Subscription Request to,
124Identify this account as 'Production' or 'Test'.
125This installation is taking place in which account?
126Enter 'P' for Production or 'T' for Test
127HL*1.6*39
128You must have patch HL*1.6*39 installed.
129Environment check is ok.
130Enter 'P' if this installation is taking place in your
131PRODUCTION account. This will require patch HL*1.6*39.
132Enter 'T' if this installation is taking place in your
133TEST account. HL*1.6*39 should NOT be installed in any
134test account.
135This option prints information from the AUDIT file (#1.1) for a
136selected patient and date range.
137For the PATIENT file (#2) entry selected, the report prints the
138patient name and DFN, date/time the field was edited, the user who
139made the change, the field edited, the old value, and the new value.
140The option or protocol (if available) will also be displayed.
141This patient has no audit data available for any date.
142Enter date range for data to be included in report.
143Beginning Date:
144MPI/PD - Print AUDIT File Data for a Specific Patient
145No audit data found in this date range for this patient.
146PATIENT AUDIT LIST at
147Date/Time Edited
148Field Edited
149Edited By
150Old Value / New Value
151Option/Protocol
152This option prints a customized report of information stored in the AUDIT
153file (#1.1) for fields being audited in the PATIENT file (#2). For a
154specified date range, you can view all audited fields or selected fields.
155You can also opt to print only edits that were done by a specific user.
156- If selected fields are viewed, you can choose to see data for all or
157 selected patients.
158- If ALL audited fields are viewed, you must choose patients to examine.
159No fields are currently being audited in the PATIENT file (#2).
160Do you want to see (A)LL or (S)ELECTED audited fields?
161 to see ALL audited fields in the PATIENT file (#2).
162 to select specific audited fields.
163Select FIELD NUMBER of audited field (enter
164 for list):
165Do you want to see audited data for (A)LL or (S)ELECTED patients?
166 to see audited fields for ALL patients.
167 to select specific patients(s).
168Do you want to find only the edits made by a specific user
169Because you selected ALL patients, you MUST queue this report.
170FLD(
171MPI/PD - Print AUDIT File Data from the PATIENT file
172CUR DFN
173NO AUDIT
174 has no audit data available for any date.
175 has no audit data available for selected parameters.
176Select a FIELD NUMBER from the audited field(s) in the PATIENT file:
177Duplicate Record File Statistics Scan
178Your user identification is not set. Please D ^XUP and try again.
179Duplicate Record Statistics Search
180 queued to run.
181DUPLICATE RECORD CHECK
182CURR IEN
183Duplicate Record (^DPT) Statistics
184 Counts by: Merge Status and Match Percentile:
185NOT READY
186 Merge Status:
187 Counts by: Verification Status and Match Percentile:
188POTENTIAL DUP., UNVERIF
189VERIFIED, NOT A DUPLICATE
190VERIFIED DUPLICATE
191VERIF. IN PROGRESS
192REQUIRES RESOLUTION
193 Verification Status:
194Duplicate Record Counts:
195The option, Start/Restart CMOR Score Calculation
196[RG CMOR START], needs to be run before this option.
197DUP. RECORD REPORT BY CMOR SCORE
198NO SCORE
199TOTAL Potential Duplicates (15):
200TOTAL Patients (2):
201TOTAL Potential Duplicates (15)
202TOTAL Patients (2)
203Duplicate Record Count by CMOR Score
204This report is drawn from the Duplicate Record file (#15) with
205CMOR scores from the PATIENT file, CMOR ACTIVITY SCORE field.
206- If both members of a pair have a score of zero the pair is
207 counted in the '0' group.
208- If one or both members of the pair have a score greater than
209 zero, that pair is counted in the group for the higher score.
210- If neither member of the pair have a CMOR score, the pair is
211 counted in the 'NO SCORE' group.
212Score Range
213Duplicate Records by CMOR Score:
214Exception Totals for
215TOTAL EXCEPTIONS:
216At this point it is necessary for you to increase the right margin.
217At the DEVICE prompt enter=> ;255
218DOWNLOAD ABORTED!
219Data string=Site;Run Date;Date CIRN Installed;Exceptions 200-229
220Data string:
221Site;Sta#;;;LocICNs,209,213,214,215,216,217,218,219,223,225,226,227,229
222...purging duplicate Potential Match Exceptions
223VAFC HFS SCRATCH
224RGMT_
225Subscribers:
226ICN History:
227CMOR History:
228CMOR Change Request History:
229and deleted
230Site;Sta#;
231This utility searches the HL7 MESSAGE TEXT (#772) file for a selected
232date range. Each HL7 message in the date range is examined. If the
233RELATED EVENT PROTOCOL field contains the MPI/PD protocols (e.g.,
234) data is compiled into the ^XTMP(
235A cross-reference is built on patient ICN and DFN for faster data retrieval
236for the associated reports.
237The Compile MPI/PD HL7 Data compilation is already running!
238Compile MPI/PD HL7 Data
239 last ran to completion on
240=> Data has been compiled for
241(D)elete existing data and recompile.
242(A)ppend new data after last date of existing data
243D if you want to delete exiting data and recompile.
244A or <RET> to append new data after last date of existing data.
245 to HALT.
246Enter date range for data to be compiled.
247Beginning Date for Report:
248Beginning Date for Report:
249Ending Date for Report:
250Compile MPI/PD HL7 Data (bi-directional)
251FORCE STOP
252NOW PROCESSING DATE
253(Look at ^HL(772,
254Stop HL7 Message Compile.
255<< No compile is currently running >>
256A compile is currently running for
257Do you want to stop this compile
258Show status of HL7 Message Compile.
259Compile range
260The compile was started
261The compile is now processing
262The compile was stopped
263The option
264 must have
265run to completion before this report can be printed!
266 is currently running.
267This report cannot be generated until the compile has run to completion.
268Data has been compiled for
269 option if this range is not sufficient.
270This option allows you to search for activity related to a specific protocol in
271the HL7 MESSAGE TEXT (#772) file for a patient during a selected period of time.
272This search is accomplished using data set into a temporary global built by the
273Select TYPE
274Patient lookup can be done by (P)atient Name/SSN or by (I)CN.
275Select LOOKUP
276The right margin for this print is 80.
277MPI/PD - Print HL7 Message Data for Patient/Single Protocol
278No data found for this patient.
279HL7 TRANSMISSION DATA at
280File #772 IEN
281Batch Msg #
282This patient does not have an ICN!
283Select ICN
284No patient match can be found for this ICN!
285This option allows you to search for ALL activity in the HL7 MESSAGE TEXT
286(#772) file for a specific patient during a selected period of time. This
287search is accomplished using data set into a temporary global built by the
288HL7 TRANSMISSION PATIENT DATA at
289Related Event Protocol
290No patient DFN match can be found for this ICN!
291This patient has no HL7 messaging activity in the current compiled data set.
292Select TYPE of Report - (D)etailed or (S)ummary:
293This option allows you to print information found during the
294Compile MPI/PD
295HL7 Data
296 compilation. The report is sorted by RELATED EVENT PROTOCOL, date,
297transmission type, and status. The total number of messages for each date,
298transmission type, and status are displayed.
299MPI/PD - Print HL7 Message Status (SUMMARY)
300MPI/PD HL7 MESSAGE STATUS REPORT - SUMMARY (
301RELATED EVENT PROTOCOL
302transmission type, and status. Detailed information for each HL7 message is
303#################### #################### ####################
304#################### #################### ####################
305#################### #################### ####################
306#################### #################### ####################
307#################### #################### ####################
Note: See TracBrowser for help on using the repository browser.