English	French	Notes	Complete/Exclude
Error in Process			
Request Sent			
Awaiting Response			
 - No patient data query exists for this patient.			
No Data Returned Due To: 			
There were no exceptions found.			
Enter an exception type to view: 			
Not a valid selection.			
exceptions that need processing.			
The following exception types are handled by this option:			
Required field(s) Date of Birth or Name missing			
SSN Match Failed			
Name Doesn't Match			
Death Entry on MPI not in VISTA			
Death Entry on Vista not in MPI			
Death Entries on MPI and Vista DO NOT MATCH			
Potential Matches Returned			
no exceptions found			
MISSING MSH SEGMENT			
ICN:			
From Station:			
APPLICATION ACKNOWLEDGMENT TO MSGID: 			
MISSING PARAMETER			
RG FACILITY INTEGRATION SERVER			
ERROR ENCOUNTERED BY HL7 WHILE SENDING FACILITY INTEGRATION MESSAGE: 			
MISSING PARAMETER NEEDED TO BUILD FACILITY INTEGRATION MESSAGE			
UNABLE TO SEND FACILITY INTEGRATION MESSAGE - PATIENT LACKS ICN			
SITE NOT FOUND IN INSTITUTION FILE			
Facility Integration Message not sent to station #  			
RG FACILITY INTEGRATION CLIENT^			
LEGACY STATION NUMBER NOT FOUND UNIQUELY IN THE INSTITUTION FILE!			
PRIMARY STATION NUMBER NOT FOUND UNIQUELY IN THE INSTITUTION FILE!			
RG FACILITY INTEGRATION CLEANUP			
Looking for patients with legacy site as CMOR ...			
Looking for patients with legacy site as treating facility ...			
Returned mail message number:			
HL7 Message sent: 			
*** HL7 Message NOT sent! :			
Patient DFN:   			
Patient ICN:   			
Treating Facilities:			
Process patient			
** Patients with Legacy Site as CMOR **			
** Patients with Legacy Site as Treating Facility **			
** END OF MPI/NDBI SITE CLEANUP REPORT **			
MPI/NDBI SITE CLEANUP REPORT FROM 			
Primary Station: 			
  Legacy Station: 			
Count of Patients Found with Legacy Site as CMOR: 			
MPI/PD at 			
G.MPIF EXCEPTIONS			
MPI/NDBI SITE CLEANUP			
INPUT PARAMETER MISSING, TAG=XCHANGE,RTN=RGFIPM			
INSTITUTION LOOKUP FAILED, STATION# = 			
ERROR CHANGING CMOR TO 			
FAILURE TO DELETE TREATING FACILITY = 			
FAILURE TO ADD SUBSCRIPTION FOR STATION# = 			
FACILITY INTEGRATION ERROR: 			
STATION#			
PATIENT LOOKUP BASED ON ICN FAILED			
LOCAL DATABASE HAS INCORRECT ICN CHECKSUM			
SENT INCORRECT ICN CHECKSUM			
ERROR ENCOUNTERED WHILE PROCESSING FACILITY INTEGRATION MESSAGE			
SITE INTEGRATION MSG TO CMOR NOT FROM LEGACY SITE			
SITE INTEGRATION MSG NOT FROM CMOR, CMOR IS 			
MISSING STATION NUMBER IN MSH SEGMENT FOR SENDING SITE			
EVENT REASON CODE NOT 51			
MISSING ICN IN PID SEGMENT			
MISSING LEGACY STATION # IN NTE SEGMENT			
MISSING PRIMARY STATION # IN NTE SEGMENT			
 From Station:			
MISSING SEGMENT: 			
ERROR ENCOUNTERED WHILE PROCESSING FACITLIY INTEGRATION MESSAGE: MISSING CMOR			
Facility Integration Message not sent to MPI, no MPI link identified in CIRN SITE PARAMETER file (#991.8)			
Facility Integration Message not sent to primary site, station # 			
RG FACILITY INTEGRATION CLIENT			
HL7 Message Exception Report			
MPI/PD Exception: 			
MPI/PD exception notification			
RGMSH(773,			
RG MPI SERVER EXCEPTION			
**MPI/PD EXCEPTION**			
EXCEPTION TYPE			
OPTIONAL TEXT			
SITE OF OCCURRENCE			
SITE REPORTING			
DATE/TIME REPORTED			
**PATIENT DATA**			
TREATING FACILITY			
DATE LAST TREATED			
EVENT REASON			
S.MPI EXCEPTION SERVER@			
MPI/PD EXCEPTION			
MESSAGE ID			
EVENT TYPE			
LOGICAL LINK			
-1^INVALID ICN CHECKSUM			
RGSEG(RGPC)			
RGSEG(RGPC,RGPC1)			
RGSEG(RGPC,RGPC1,RGPC2)			
SCN_REQ			
 Bad DFN, 			
 See the Exception Handling document on the MPI/PD web site.			
 Mismatched SSN,			
 Bad CMOR 			
 for DFN#			
 Mismatched CMOR, 			
 Does not exist in patient database. 			
 Unable to send Subscription Request from 			
.  This is not a MPI/PD site.			
 Unable to send Subscription Request to 			
REQUIRED PARAMETERS MISSING IN STUB			
RG PT SUBSCRIPTION REQUEST			
RG PT SUBSCRIPTION RECEIVER^			
SUBSCRIPTION REGISTRY			
 Unable to send Subscription.  Duplicate station number of 			
 in Institution file.			
 Unable to send Subscription from 			
.  This is not a MPI/PD Site.			
 Unable to send Subscription to 			
 Unable to send Subscription Request from, 			
 Unable to send Subscription Request to, 			
Identify this account as 'Production' or 'Test'.			
This installation is taking place in which account? 			
Enter 'P' for Production or 'T' for Test			
HL*1.6*39			
You must have patch HL*1.6*39 installed.			
Environment check is ok.			
Enter 'P' if this installation is taking place in your			
PRODUCTION account.  This will require patch HL*1.6*39.			
Enter 'T' if this installation is taking place in your			
TEST account.  HL*1.6*39 should NOT be installed in any			
test account.			
This option prints information from the AUDIT file (#1.1) for a			
selected patient and date range.			
For the PATIENT file (#2) entry selected, the report prints the			
patient name and DFN, date/time the field was edited, the user who			
made the change, the field edited, the old value, and the new value.			
The option or protocol (if available) will also be displayed.			
This patient has no audit data available for any date.			
Enter date range for data to be included in report.			
Beginning Date:  			
MPI/PD - Print AUDIT File Data for a Specific Patient			
No audit data found in this date range for this patient.			
PATIENT AUDIT LIST at 			
Date/Time Edited			
Field Edited			
Edited By			
Old Value / New Value			
Option/Protocol			
This option prints a customized report of information stored in the AUDIT			
file (#1.1) for fields being audited in the PATIENT file (#2).  For a			
specified date range, you can view all audited fields or selected fields.			
You can also opt to print only edits that were done by a specific user.			
- If selected fields are viewed, you can choose to see data for all or			
  selected patients.			
- If ALL audited fields are viewed, you must choose patients to examine.			
No fields are currently being audited in the PATIENT file (#2).			
Do you want to see (A)LL or (S)ELECTED audited fields? 			
 to see ALL audited fields in the PATIENT file (#2).			
 to select specific audited fields.			
Select FIELD NUMBER of audited field (enter 			
 for list): 			
Do you want to see audited data for (A)LL or (S)ELECTED patients? 			
 to see audited fields for ALL patients.			
 to select specific patients(s).			
Do you want to find only the edits made by a specific user			
Because you selected ALL patients, you MUST queue this report.			
FLD(			
MPI/PD - Print AUDIT File Data from the PATIENT file			
CUR DFN			
NO AUDIT			
 has no audit data available for any date.			
 has no audit data available for selected parameters.			
Select a FIELD NUMBER from the audited field(s) in the PATIENT file:			
Duplicate Record File Statistics Scan			
Your user identification is not set.  Please D ^XUP and try again.			
Duplicate Record Statistics Search			
 queued to run.			
DUPLICATE RECORD CHECK			
CURR IEN			
Duplicate Record (^DPT) Statistics			
  Counts by:  Merge Status and Match Percentile:			
NOT READY			
    Merge Status: 			
  Counts by:  Verification Status and Match Percentile:			
POTENTIAL DUP., UNVERIF			
VERIFIED, NOT A DUPLICATE			
VERIFIED DUPLICATE			
VERIF. IN PROGRESS			
REQUIRES RESOLUTION			
    Verification Status: 			
Duplicate Record Counts: 			
The option, Start/Restart CMOR Score Calculation			
[RG CMOR START], needs to be run before this option.			
DUP. RECORD REPORT BY CMOR SCORE			
NO SCORE			
TOTAL Potential Duplicates (15): 			
TOTAL Patients (2): 			
TOTAL Potential Duplicates (15)       			
TOTAL Patients (2)                    			
Duplicate Record Count by CMOR Score			
This report is drawn from the Duplicate Record file (#15) with			
CMOR scores from the PATIENT file, CMOR ACTIVITY SCORE field.			
- If both members of a pair have a score of zero the pair is			
  counted in the '0' group.			
- If one or both members of the pair have a score greater than			
  zero, that pair is counted in the group for the higher score.			
- If neither member of the pair have a CMOR score, the pair is			
  counted in the 'NO SCORE' group.			
Score Range			
Duplicate Records by CMOR Score: 			
Exception Totals for 			
TOTAL EXCEPTIONS: 			
At this point it is necessary for you to increase the right margin.			
At the DEVICE prompt enter=> ;255			
DOWNLOAD ABORTED!			
Data string=Site;Run Date;Date CIRN Installed;Exceptions 200-229			
Data string:			
Site;Sta#;;;LocICNs,209,213,214,215,216,217,218,219,223,225,226,227,229			
...purging duplicate Potential Match Exceptions			
VAFC HFS SCRATCH			
RGMT_			
Subscribers:			
ICN History:			
CMOR History:			
CMOR Change Request History:			
and deleted			
Site;Sta#;			
This utility searches the HL7 MESSAGE TEXT (#772) file for a selected			
date range.  Each HL7 message in the date range is examined.  If the			
RELATED EVENT PROTOCOL field contains the MPI/PD protocols (e.g., 			
) data is compiled into the ^XTMP(			
A cross-reference is built on patient ICN and DFN for faster data retrieval			
for the associated reports.			
The Compile MPI/PD HL7 Data compilation is already running!			
Compile MPI/PD HL7 Data			
 last ran to completion on 			
=> Data has been compiled for 			
(D)elete existing data and recompile.			
(A)ppend new data after last date of existing data			
D if you want to delete exiting data and recompile.			
A or <RET> to append new data after last date of existing data.			
 to HALT.			
Enter date range for data to be compiled.			
Beginning Date for Report: 			
Beginning Date for Report:  			
Ending Date for Report:  			
Compile MPI/PD HL7 Data (bi-directional)			
FORCE STOP			
NOW PROCESSING DATE			
(Look at ^HL(772,			
Stop HL7 Message Compile.			
<< No compile is currently running >>			
A compile is currently running for 			
Do you want to stop this compile			
Show status of HL7 Message Compile.			
Compile range 			
The compile was started 			
The compile is now processing 			
The compile was stopped 			
The option 			
 must have			
run to completion before this report can be printed!			
 is currently running.			
This report cannot be generated until the compile has run to completion.			
Data has been compiled for 			
 option if this range is not sufficient.			
This option allows you to search for activity related to a specific protocol in			
the HL7 MESSAGE TEXT (#772) file for a patient during a selected period of time.			
This search is accomplished using data set into a temporary global built by the			
Select TYPE			
Patient lookup can be done by (P)atient Name/SSN or by (I)CN.			
Select LOOKUP			
The right margin for this print is 80.			
MPI/PD - Print HL7 Message Data for Patient/Single Protocol			
No data found for this patient.			
HL7 TRANSMISSION DATA at 			
File #772 IEN			
Batch Msg #			
This patient does not have an ICN!			
Select ICN			
No patient match can be found for this ICN!			
This option allows you to search for ALL activity in the HL7 MESSAGE TEXT			
(#772) file for a specific patient during a selected period of time.  This			
search is accomplished using data set into a temporary global built by the			
HL7 TRANSMISSION PATIENT DATA at 			
Related Event Protocol			
No patient DFN match can be found for this ICN!			
This patient has no HL7 messaging activity in the current compiled data set.			
Select TYPE of Report - (D)etailed or (S)ummary:  			
This option allows you to print information found during the 			
Compile MPI/PD			
HL7 Data			
 compilation. The report is sorted by RELATED EVENT PROTOCOL, date,			
transmission type, and status. The total number of messages for each date,			
transmission type, and status are displayed.			
MPI/PD - Print HL7 Message Status (SUMMARY)			
MPI/PD HL7 MESSAGE STATUS REPORT - SUMMARY (			
RELATED EVENT PROTOCOL			
transmission type, and status. Detailed information for each HL7 message is			
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################