English	French	Notes	Complete/Exclude
Any unreferenced message will be purged if its local create date			
Messages processed:   |1|			
Lowest numbered message:   |1|			
No original message |1| for this response: fixed			
Not in response chain of |1|: fixed			
No original message |1| for this response: not fixed			
Not in response chain of |1|: not fixed			
Piece 8 didn't point to original message |1|: fixed			
Recipient |1| null, no C xref: fixed			
Recipient |1| no C xref: xref created			
Recipient |1| C xref too long: xref shortened			
C xref, but recip |1| null: fixed using xref			
C xref, but recip |1| null: fixed, but CHECK			
C xref for recip |1| doesn't match recip: xref killed			
Messages will be sent to owners of more than |1| messages.			
This process cleans out old messages from user mailboxes.			
Compiling lists of messages to delete in |1| days from *all* baskets			
Compiling lists of messages to delete in |1| days from IN baskets			
You may not access any message prior to |1|,			
Message |1| is a response to message |2|.			
You may not access this message as |1| unless you			
Do you want to forward this message to |1|			
The '|1|' basket name may not be changed.			
Basket '|1|' already exists.			
|1| has no message filters defined.			
Error resequencing the '|1|' basket.			
Resequenced from 1 to |1|.			
The '|1|' basket may not be deleted.			
The '|1|' basket may not be deleted,			
 Latered (Task #|1|)			
Local recipients who are current: |1| of |2|			
Local recipients who are not current: |1| of |2|			
Local recipients who have terminated: |1| of |2|			
Surrogates may not |1| 'confidential' messages.			
You do not have 'read' privilege for |1|.			
You do not have 'send' privilege for |1|.			
You do not have 'read' or 'send' privilege for |1|.			
You may not copy more than the site limit of |1| lines.			
You may not copy more than the site limit of |1| responses.			
Because this message has more than the site limit of |1| recipients,			
 (Surrogate: |1|)			
NEW messages: |1| (|2| in the IN basket)			
You will now choose a date range for the messages to be searched			
Task #|1| will find and forward past messages.			
Can't add it because public group '|1|' already exists.			
Put '|1|' in the TYPE field.			
|1| New Msgs			
The domain for this facility is not christened correctly.			
You are not a surrogate of DUZ |1|.			
There is no person with DUZ |1|.			
There is no access code for DUZ |1|.			
There is no mailbox for DUZ |1|.			
It appears someone is signed on as |1| already.			
POSTMASTER has |1| baskets.			
Editing data in the |1| file:			
ADD'L PHONE |1|			
|1| service for |2|			
You last used MailMan: |1|			
|2| last used MailMan: |1|			
Your current banner: |1|			
|2|'s current banner: |1|			
You have |1| new messages.			
|2| has |1| new messages.			
|2| has 1 new message.			
|2| has no new messages.			
 (|1| in the '|2|' basket)			
(Last arrival: |1|)			
|1| has PRIORITY mail!			
Messages longer than |1| lines may not be sent across the network.			
Invalid recipient type '|1|'			
If |1| is the person you're trying to address, you can't,			
Limited Broadcast entry |1|, field |2| is null.			
Limited Broadcast entry |1|, field |2|: '|3|' does not exist.			
Select Limited Broadcast |1|: 			
Limited Broadcast selection not found: |1|			
Limited Broadcast selection ambiguous: |1|			
Limited Broadcast value '|1|' not found in file |2|.			
Limited Broadcast value '|1|' ambiguous in file |2|.			
Checking: |1|			
Problems in member group: |1| (IEN=|2|)			
 (To |1| Domains)			
Domain not found: |1|			
 via |1|			
Sub-domain '|1|' not found for domain '|2|'			
Valid domain, but need subdomain: |1|			
Domain |1| is a valid Internet domain,			
Domain ambiguous: |1|			
Circular relay domain: |1|			
Domain must be from 1 to |1| characters.			
Domain dot pieces must be from 1 to |1| characters.			
|1| is not valid.			
Domain closed: |1|			
You don't hold key to domain '|1|'.			
Mail group contains circular reference to G.|1|.			
You may not access group '|1|'.			
Finished with group |1|.			
Message |1| is confidential.  SHARED,MAIL removed as recipient.			
Message |1| is closed.  SHARED,MAIL removed as recipient.			
Priority message |1| not forwarded.			
Message |1| not forwarded to remote recipients.			
Message |1| has no addressees.  Not forwarded.			
Message |1| not forwarded to broadcast.			
Site: |1|			
Sender: |1|			
MailMan Fax for |1|			
FAXMail ID: |1|, faxed: |2|			
You are not authorized to be a surrogate of DUZ |1|.			
Message body '|1|' has no data.			
|1| is not valid.			
Basket name '|1|' ambiguous.			
Basket '|1|' not found.			
Bulletin '|1|' not found.			
User '|1|' ambiguous.			
User '|1|' not found.			
Must be |1|-|2| characters.			
Basket '|1|' already exists.			
Server basket '|1|' not found.			
Mail group '|1|' not found.			
Mail group IEN '|1|' not found.			
Mail group '|1|' has no active local members.			
Mail group '|1|' does not have at least |3| active local members.			
Mail group '|1|' has no local members active since '|2|'.			
Mail group '|1|' does not have at least |3| local members			
MailMan: To |1|			
MailMan: To |1| (requeue)			
|1| Requeued			
MailMan: To Device |1|			
MailMan: To Server |1|			
Server task #: |1|			
MailMan: Bulletin |1|			
Transmission Queue History, |1|			
Transmission Queue History, |1| - |2|			
== Appears Inactive - |1| Minutes			
Task |1| queued			
No task scheduled, FLAGS=|1|			
Task |1| scheduled for |2|			
Task |1| just started			
Task |1| is already scheduled for domain |2|			
The errors started on |1|.			
The following errors occurred in the previous |1| attempts:			
To |1| from |2| on |3|			
Script: |1|			
Invalid script command |1| at line |2|.			
Script |1| cannot be found in file 4.6			
Calling script '|1|' (file 4.6)			
Returning to script '|1|'.			
Dialing |1|			
Call failed: |1|			
Error msg set to '|1|'			
Channel opened to |1|			
Device '|1|', Protocol '|2|' (file 3.4)			
Transforming '|1|' to '|2|'			
Undefined reference to '|1|'			
Waiting |1| seconds			
Xecuting '|1|'			
Can't connect using IP address '|1|'			
Resuming script from line |1|			
Look: Timeout=|1|, Command String='|2|'			
Invalid Communications Protocol: '|1|'			
Invalid parameter '|1|'			
Device '|1|' could not be opened by %ZIS.			
|1| sent, |2| received.			
|1| sent, |2| received, |3| retransmissions.			
Messages dumped: |1|			
Receive messages for |1|			
Loading entry #|1| from |2| ...			
No entries found in file 4.281 for |1|			
Messages received: |1|			
Ignore '|1|' - no IP address			
Ignore '|1|' - that's a different site			
Ignore '|1|' - already have that IP address			
Accept '|1|'			
Returned: |1|			
Let's see what we can do...			
Now, let's try: |1|			
Changed IP address in script from '|1|' to '|2|'			
|3| - Changed IP address from '|1|' to '|2|' (MailMan)			
We will not change the IP address in the script because the site			
Task |1| is transmitting this domain's messages now.			
Task |1| is scheduled to transmit this domain's messages			
Do you want to kill task |1| and queue up a new one			
Do you want to kill task |1| before we play the script			
Transcript Date: |1|			
> Putting response |1| into message |2|			
> Delivering message |1|			
HELO Send failed: |1|			
|1| not recognized by |2|			
TURN command disabled for |1|			
A system error occurred in M: |1|			
Remote Procedure Unknown: '|1|' cannot be found.			
Remote Procedure Blank: '|1|' contains no information.			
Remote Procedure InActive: '|1|' cannot be run at this time.			
RPC Context Error :: |1|			
|1|			
Remote Procedure: '|1|' timed out. (|2| seconds)			
Remote Procedure Name '|1|' is different than file entry (|2|).			
Expecting a security message type '|1|', but found unrecognized message type: '|2|'			
Security message action '|1|' is an unknown security action.			
Logon failure: '|1|'			
Logon failure: '|1|'			
Error retrieving user demographics: '|1|'			
Request Handler Loading Error: |1|			
Error Number: 1509000.001			
SCANNING ERROR:  PCE Returned the following Errors and Warnings for Form ID: |5|.			
AICS Error: AICS Manual Data Entry attemped to pass data node |6| with no Data to PCE.			
Warning: a '|7|' bubble was checked.  This information was not passed to PCE or Scheduling.  			
AICS Error:  GAF Score was not filed due to missing information for			
SCANNING ERROR: The type of vital sign |6| is not known to the Package Interface, Error Code 3576001.			
SCANNING ERROR: The Qualifier |11| is not known to the Package Interface, Error Code 3576002.			
SCANNING ERROR: The Package Interface |10| is missing or incomplete, Error Code 3576003.			
SCANNING ERROR: AICS was passed the FORMID |5| but the Form Definition |4| is missing, Error Code 3579501.			
SCANNING ERROR:  Bubble |6| was not found in the Form Definition File |4|, Error Code 3579502			
SCANNING ERROR:  Handprint field |6| was not found in Form Tracking Entry |4|, Error Code 3579503.			
SCANNING ERROR:  |14| Hand Print data with a value of |7| is invalid, Error Code 3579504.			
SCANNING ERROR: Diagnosis Entry "|12|" was sent to PCE as Secondary, Error Code 3579505.			
SCANNING ERROR: AICS failed to convert Clinical Lexicon Term "|12|" to an ICD9 code, Error Code 3579506.			
Printing Error:  During the printing of an encounter form AICS failed to			
SCANNING ERROR:  Dynamic Bubble |6| was not found in the Form Tracking File |5|, probably as a result of marking a bubble with no associated data. Error Code 3579602.			
SCANNING ERROR: The Encounter Provider |7| was set to Secondary, Error Code 3570603.			
SCANNING ERROR: A form ID of "|5|" was passed to AICS and is invalid.  No other information can be determined.  Error code 3579604.			
SCANNING ERROR: AICS was passed a Form ID of "|5|" and this entry does not exist in the Form Tracking file.  			
SCANNING ERROR: A page number of "|17|" (zero or null) is not valid as containing data.  Error Code 3579606.			
SCANNING ERROR: AICS was passed a Form Definition value of "|4|" and is invalid.  Error Code 3579607.			
SCANNING ERROR: The Form Definition of |4| doesn't match the Form Definition found in Forms Tracking for entry |5|.  Error Code 3579608			
SCANNING ERROR: Data from Non-Scannable Page |17| was passed to AICS.  Error Code 3579609.			
SCANNING ERROR: AICS was unable to Store partial form data in Forms Tracking for Form ID: |5|.  Error Code 3579610.			
Printing Error:  During the printing of Encounter Form ID |5| for 			
SCANNING ERROR: AICS was unable to store Procedure Data in PCE for Form ID: |5|.  Error Code 3579612.			
Warning: During scanning of Form ID: |5| the recognition was canceled			
SCANNING ERROR: The type of Vitals Data is required and Missing, Error Code 			
 Error Code: 4030005.001   Type: Missing User Record			
 Error Code: 4035001.001   Type: Missing Query Parameter			
    Error Code: 4035001.002  Type: Inconsistent Selection			
   Error Code: 4035002.001   Type: Template Deletion Error			
Error Code: 4040001.001			
Patient Team Assignment Error			
 Error with TEAM File data entry			
Bad or missing data			
Bad or Missing data. Institution field entry of Team file=|SCINST|			
Error with Practitioner-Position Assignment			
Practioner = |PRACTITIONER|			
This Auto Link pointer value is missing.			
Bad/Missing data relating to TEAM AUTOLINKS file's AUTOLINK field = |SCAU|.			
Bad Data for Postion Data entry			
Position = |POSITION|			
Error Code: 4049001.001			
Error Code: 4049001.004			
Error Code: 4049001.01			
Error Code: 4049004.001			
Error Code: 4049005.001			
Error Code: 4049005.002			
Error Code: 4049005.003			
Error Code: 4049005.004			
Error Number: 4096400.001			
Error Number: 4096800.001			
Error Number: 4096800.002			
Error Number: 4096800.003			
Error Number: 4096800.004			
Error Number: 4096800.005			
Error Number: 4096800.006			
Error Number: 4096800.021			
Error Number: 4096800.022			
Error Number: 4096800.023			
Error Number: 4096800.024			
Error Number: 4096800.025			
Error Number: 4096800.101			
Error Number: 4096800.102			
Error Number: 4096800.103			
Error Number: 4096800.104			
Error Number: 4096800.105			
Error Number: 4096800.106			
Error Number: 4096800.108			
Error Number: 4096800.109			
Error Number: 4096800.113			
ERROR MESSAGE FROM DATA2PCE^PXAPI			
* * * * W A R N I N G * * * *			
* * * * * * WARNING * * * * * *			
    * * * Problem List Error * * *			
ODS software is not on...you can not use this option			
Patient does not have a period of service of ODS			
Do you want to create an ODS ADMISSION entry for 			
Enter 'Y'es if this admission was for care related to Operation			
Desert Shield.  Otherwise, respond 'N'o.			
Record Created			
ODS BACKGROUND JOB			
>>>> Storing Billable Specialties from PTF in ODS file. >>>>			
>>>> Storing Surgeries and Procedures in ODS files. >>>>			
>>>> Storing Diagnoses in ODS files. >>>>			
You may now enter any additional costs related to this ODS admission.			
Select COST DATE: 			
THIS MAY TAKE A FEW MOMENTS^LET ME PUT YOU ON 'HOLD' FOR A SECOND^HOLD ON^JUST A MOMENT PLEASE^I'M WORKING AS FAST AS I CAN^LET ME THINK ABOUT THAT A MOMENT			
Select ODS ADMISSION DATE/TIME: 			
Press RETURN to continue:			
Was this non-VA admission ODS related			
 answer 'Yes' if admission occurred because the patient was			
              displaced to allow an ODS admission			
    or   'No' if it was not ODS related.			
Integrity Check Started at: 			
Integrity Routine			
Integrity Check Finished at: 			
ZL @T F Y=1:1:99 S L=$T(+Y),LN=$L(L) X CC S:'LN Y=99			
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
