English	French	Notes	Complete/Exclude
HL7 Msg#			
 contained an invalid STATION#			
 for ICN#			
Unable to change CMOR in HL7 Msg#			
 due to 			
Error returned in GENERATE^HLMA  			
) array for this patient			
-1^Unknown Logical Link for Station # 			
 Unable to notify of Change of CMOR for patient 			
No MPI Link defined			
Msg#			
 Unable to add/update SC for facility IEN 			
, for patient 			
Missing new CMOR or Patient to be changed			
 for change CMOR request HL7 msg 			
Missing CMOR site number in Change CMOR message for ICN 			
Missing Patient ICN in Change CMOR message HL7 msg# 			
ICN 			
 not found from Change CMOR message HL7 msg# 			
CMOR Site name is not on file for Station Number 			
 processing Change CMOR msg for ICN 			
Unable to update CMOR for site 			
. For DFN 			
 Processing CHANGE CMOR message 			
Received CMOR Change Request for ICN 			
 ICN not Found. Request # 			
MPI VISTA Package			
MPIF(1,			
New Coordinating Master Of Record (CMOR) request received for patient 			
 no mail group defined for CMOR requests			
CMOR Change Request #			
CMOR not sent in Change CMOR message for patient DFN= 			
Unable to Change CMOR to 			
 in a CMOR Change Message for Patient DFN= 			
Auto change - CMOR pushed here			
MPIF RESOLUTION			
CMOR Request # 			
 Does Not Exist attempting to generate approved/not approved msg			
MPIF CMOR APPROVE/DISAPPROVE			
 for Approved/Not Approved msg HL Error			
-1^LINK FOR MPI NOT FOUND			
MPIF CMOR APP/DIS^			
Error Generating HL7 msg for Approve/Not Approved CMOR Request # 			
 Does Not Exist CMORs may be out of sync for ICN 			
 received CMOR request for 			
Processed by: 			
Select CMOR request to review: 			
*** Request is not pending review ***			
**** There are other PENDING Requests for this patient.  If you approve one the rest will automatically be disapproved. ***			
Select Review Action (			
APPROVE/			
DISAPPROVE, OR '^' to Exit)? 			
 ... No Action!			
Unable to change CMOR for Change CMOR Request for patient DFN= 			
  Problem Changing CMOR, resetting status to pending approval.  May be duplicates in Institution file for new CMOR or Patient file entry was already being edited.			
 Problem during Broadcast - 			
Have others to Disapprove -- automatically			
*** No request to approve ***			
Do you want to approve by SITE			
*** No requests to approve for this site ***			
Remote Procedure from MPI^RPC from MPI for ICN Information			
No current ICN			
No Current ICN			
NATIONAL ICN			
ICN HISTORY			
CMOR HISTORY			
No Exceptions			
NO EXCEPTIONS			
 with No Exceptions			
 with Exceptions			
ICNS PROCESSED			
-1^No ICN Passed			
-1^Invalid ICN			
-1^ICN is not active			
-1^Missing Required fields			
-1^Unknown ICN			
-1^Unknown Institution			
-1^No SSN or DFN Passed			
-1^Invalid SSN			
SSN USED 			
-1^No such DFN			
DFN USED 			
 already has an ICN, ICN=			
DFN 			
 Patient should not be sent to the MPI -- SSN has 5 leading 0s or name has been ZZ'd			
 problem getting ICN assinged 			
-1^Unable to get ICN			
 Local ICN assigned 			
-1^Local ICN assigned			
-1^Missing required parameter			
-1^No patient has that SSN at this site			
-1^More than one patient has that SSN at this site			
-1^Patient has a national ICN, ICN=			
-1^Problem building A24 (ADD TF) for Pt			
-1^Did not pass valid DFN			
If DOB is inexact or if SSN is not passed or if common name,			
this could take some time - please be patient....			
Could not connect to MPI or Time-out occured, try again later.			
Patient was not found in the MPI.			
Found potential matches			
Found One Match			
Continue to next Patient? 			
<<THIS ICN IS ACTIVELY BEING WORKED ON - CASE #			
Case Worker: 			
ICN      : 			
Name     : 			
SSN      : 			
DOB      : 			
Multiple Birth Indicator: Yes			
Sex      : 			
Claim #  : 			
Place of Birth: 			
Mother's Maiden Name: 			
POW Status: 			
Is Patient in the PATIENT file 			
DOB is missing - Required field			
Patient not found.  Try Again			
PATIENT NAME (last,first middle)			
Name should be Last,first middle and at least 3 characters and no more than 30			
9 Digit SSN (No Dashes)			
SSN should be 9 numbers			
MPIF_SEEDING			
A31 SEEDING FOR SITE			
CNT=			
SEEDING COMPLETED			
Seeding has been completed at site 			
Round of seeding has been completed at site 			
Site stats for seeding (total to date): 			
     AICN x-refs Processed:  			
MPIF VISTA PACKAGE			
Seeding msg 			
G.CIRN DEV@FORUM.VA.GOV			
MPIF SEEDING TASK			
MPIF SEEDING TASK doesn't exist in OPTION file			
MPIF SEEDING TASK isn't scheduled to run			
MPIF SEEDING TASK is scheduled to run at 			
I WILL PAD TO 16!			
-1^No Mailgroup defined			
*** Patient not defined for this request ***			
*** Patient has not been assigned a CMOR Site ***			
*** Patient already has an open request (			
*** You must enter a site to send this request to ***			
*** You cannot send a request to your own site ***			
*** You cannot send a request to a site that isn't a treating facility for this patient ***			
-1^No Requests on File			
) to change CMOR to 			
-1^no encoding characters			
-1^invalid DFN			
-1^Patient merged 			
-1^Patient being merged DFN= 			
-1^ICN already assigned 			
-1^5 zero SSN			
-1^EEE Patient			
-1^Missing Required Field(s)			
 is Missing Required Field(s)			
   *** Warning: this may be a missing patient, a message is being   ***			
   *** sent to notify the MPR Coordinators.  Be prepared to answer  ***			
   *** questions from the MPR Coordinator about this patient.       ***			
                     Press return key to continue			
This patient was reported as missing from 			
.  The National Missing Patient Register has			
 listed as: 			
  MISSING PATIENT INFORMATION:			
    MISSING PATIENT:       			
    RECORD REFERENCED BY:  			
    ..PHONE NUMBER:        			
    ..OPTION EMPLOYED:     			
 is determined to be a missing patient use the MPR option			
'Enter/Edit Found Patient' to update the Local and National MPR data base.			
G.MPR COORDINATORS			
MPR FOUND PATIENT BULLETIN			
MPR*			
MPR FOUND PATIENT			
Missing Patient Register			
Select a NATIONAL MISSING PATIENT: 			
) has never been a patient			
at this facility.			
DATE PATIENT FOUND			
Enter the date that the patient was found			
Please enter the patient's condition when found			
Please enter a narrative describing how the patient was found.			
You have not answered all the necessary information associated with this			
found patient.			
Do you want to finish editing now			
If you do not finish editing, no information will be updated.			
MPR Found Patient Background Filer.			
 created to file and transmit data to the National			
Missing Patient Register database.			
MPRFMSG(			
MPR Found Patient Data			
 has NOT been added to the Missing Patient Register.			
 has been added to the Missing Patient Register.			
MPR Missing Patient Background Filer.			
NO TASK			
 created to transmit data to			
National Missing Patient Register Database.			
Someone is currently editing that patient, please try later.			
Next of Kin can not be notified before the patient was reported missing.			
PLEASE CONFIRM, IS THE PATIENT OF LOW RISK: 			
NOW-72H			
Date the patient was discovered missing: 			
   Enter the date that the patient was discovered missing.			
   Patient must be missing for 72 hrs. before entry to Missing Patient Register.			
   The date must be before 			
MPREMTSK Created on 			
MPR LOCAL DATA MESSAGE			
MPRMSG(			
Acknowledgment string			
Missing/Found field			
 is missing for this entry.			
Entry is not a ACKnowledgment entry.			
The IEN in this ACKnowledgment message is not in the ^MPR(850) database.			
This ACKnowledgment message is not a Missing or Found entry.			
Status for entry 			
 in file 850 is not a 'T'.			
 in file 850 is not a 'T' or 'A'.			
The MPR Acknowledgment server has encountered an error.			
Sender: 			
Option Name: MPRSACK			
MPRSACK Server Error			
G.MPR MESSAGES@			
MPRERR(			
Message is not proper format for the Missing Patient Register Server.			
Message data is not in proper format for the Missing Patient Register Server.			
UNABLE TO STORE DATA.  INVALID SSN.			
The MPR Data server has encountered an error.			
Option Name: MPRSDATA			
MPRSDATA Server Error			
<attribute name>			
<attribute value>			
Invoking XML Parser...			
Parser Summary:			
Elements			
Non-markup Content			
Processing Instructions			
External Entities			
Notation Declarations			
Warning^Validation Error^Conformance Error			
Line 			
<?xml version=			
E3R Entry Number   : 			
Suspense Date: 			
Priority           : 			
Functional Category: 			
Status             : 			
Resolved Date: 			
Submitted By       : 			
Submitted Date: 			
Responsible Package: 			
Message #:			
Impact:			
Recommendation:			
Arbitrator Comments:			
EP/ARG Comments:			
Package/Developer Comments:			
Final Resolution:			
SHORT DESCRIPTION			
Do you want to enter a new request			
You must enter a Description before you can transmit this			
E3R request to the Package/Developer.			
Do you want to re-edit this request now			
You currently have no E3R's under development for you to edit.			
You have no 'under development' E3R's to cancel or are not authorized to			
cancel E3R's assigned or under arbitration.			
NTSE ARBITRATOR			
Are you sure you want to cancel this E3R report			
Would you like to review the existing data for this E3R report			
Is this E3R ready to be transmitted to the package/developers for action			
You may select E3R 			
 to edit it later, or choose the cancel option			
to dispose of it.			
E3R requests may be selected by entering one of the following:			
2.  The beginning of the short description.			
3.  The namespace of the related package or the namespace, a hyphen and the			
version number (e.g., DENT or DENT-1.14).			
Select E3R ENTRY NUMBER: 			
This entry is already being edited by someone.  Try again later.			
Are you sure you want to refer this E3R to the arbitrator			
This E3R has been referred to the arbitrator (DBIC) for assignment			
to the appropriate responsible package.			
This report was assigned to your package by the arbitrator.			
You are not allowed to refer it back to the arbitrator.			
If you do not agree with this assignment, you may discuss it further with			
the arbitrator (DBIC).			
Is this E3R report considered assigned to the responsible package			
This option can only be used by EP members.  You are not designated as an EP			
member for any of the packages in the package file.			
Is this E3R report now considered resolved			
The user representative or developer, 			
has resolved the E3R request # 			
Package/Developer comments:			
EP Comments:			
NTSE MASTER			
ELECTRONIC ERROR & ENHANCEMENT REPORT			
Package Prefix: 			
under development			
under arbitration			
Resolved			
DELETE CONDITION			
ARBITRATOR COMMENTS			
PACKAGE/DEVELOPER COMMENTS			
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################