{"aaData": [["1", "
SEVERE
\n", "
Invalid integration control number
\n", "
MPI EXCEPTION HANDLER
\n", "", "
5
\n", "
MPIF EXCEPTIONS
\n", "
\nThe integration control number (ICN) is used to uniquely identify a patient \npatient.  Further processing of the message is not possible until this problem \nis resolved.  Possible causes include a bad checksum stored in the PATIENT file \nof either the sending or the receiving institution, or a message that was \ncorrupted during transmission.\nwithin VHA.  This patient's ICN has failed validation for one of the reasons \nlisted below:\n\nNO MPI NODE or NO ICN:  The patient has not been assigned an ICN.  This should \nnot occur under normal circumstances.\n\nBAD ICN CHECKSUM:  The checksum accompanying the ICN in the message does not \nmatch that stored in the ICN CHECKSUM field of the PATIENT file entry for this \n
\n
\n"], ["18", "
INFORMATIONAL
\n", "
Unclassified exception
\n", "
NONE
\n", "", "
0
\n", "", "
\nRefer to the supplemental text reported with this exception to determine the \nnature of the problem.  This exception type should normally not be used, but is \nprovided for backward compatibility.\n
\n
\n"], ["200", "
SEVERE
\n", "
Missing BHS Segment
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMissing BHS Segment in message received from the MPI in the batch load\ninitialization.\n
\n
\n"], ["201", "
MINOR
\n", "
Missing MSH Segment
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMissing MSH segment in MPI Batch Message being processed from the MPI.\n
\n
\n"], ["202", "
MINOR
\n", "
Missing QAK Segment
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMissing QAK segment in MPI Batch Initialization Message from the MPI.\n
\n
\n"], ["203", "
MINOR
\n", "
Missing MSA Segment
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMissing MSA segment from MPI Batch Initialization Message from the MPI.\n
\n
\n"], ["204", "
MINOR
\n", "
Missing RDF Segment
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMissing RDF Segment from MPI Initialization Batch Message from the MPI.\n
\n
\n"], ["205", "
MINOR
\n", "
Missing RDT Segment
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMissing RDT Segment from the Batch Initialization Message from the MPI.\n
\n
\n"], ["206", "
MINOR
\n", "
Could Not Create VTQ
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nUnable to create VTQ query segment in Batch Initialization Message to the\nMPI.  Tracking only missing encoding characters or invalid DFN.\n
\n
\n"], ["207", "
SEVERE
\n", "
Application Reject Error
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nApplication Rejection Error, wrong application sent in message to MPI.\n
\n
\n"], ["208", "
SEVERE
\n", "
Application Error
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nApplication Error returned from the MPI.\n
\n
\n"], ["209", "
MINOR
\n", "
Required field(s) missing for patient sent to MPI
\n", "", "", "
0
\n", "", "
\nRequired fields: Name, date of birth, sex or SSN\nare missing for the patient sent to the MPI for ICN assignment.\n
\n
\n"], ["210", "
MINOR
\n", "
Patient DFN Failed
\n", "
MPI EXCEPTION HANDLER
\n", "", "
1
\n", "
MPIF EXCEPTIONS
\n", "
\nPatient DFN is bad, lookup in Patient file failed.\n
\n
\n"], ["211", "
MINOR
\n", "
CMOR Lookup Failed
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nCMOR Lookup failed in Institution file.  Maybe two entries with the same\nstation number or missing a station number.\n
\n
\n"], ["212", "
MINOR
\n", "
TF Update Failed in Pivot file
\n", "
MPI EXCEPTION HANDLER
\n", "", "
6
\n", "
MPIF EXCEPTIONS
\n", "
\nAttempted to add treating facility update to Adt/HL7 Pivot file and it\nfailed to add.\n
\n
\n"], ["213", "
MINOR
\n", "
SSN Match Failed
\n", "", "", "
0
\n", "", "
\nSSN returned from MPI did not match DFN's entry in Patient file.\n
\n
\n"], ["214", "
MINOR
\n", "
Name Doesn't Match
\n", "", "", "
0
\n", "", "
\nName returned from MPI did not match DFN's entry in Patient file.\n
\n
\n"], ["215", "
MINOR
\n", "
Death Entry on MPI not in VISTA
\n", "", "", "
0
\n", "", "
\nMPI had Date of Death field populated.  Vista did not have Date of Death.\n
\n
\n"], ["216", "
MINOR
\n", "
Death Entry on Vista not in MPI
\n", "", "", "
0
\n", "", "
\nVISTA had Date of Death field populated.  MPI did not have Date of Death.\n
\n
\n"], ["217", "
MINOR
\n", "
Death Entries on MPI and Vista DO NOT Match
\n", "", "", "
0
\n", "", "
\nMPI and VistA had different dates of death for this patient.\n
\n
\n"], ["218", "
INFORMATIONAL
\n", "
Potential Matches Returned
\n", "", "", "
0
\n", "", "
\nMissing or Local ICN resolution job returned potential matches from the\nMPI.  This must be resolved via the Interactive Query option.\n
\n
\n"], ["219", "
SEVERE
\n", "
Missing ICN
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nThe message being prcessed is missing required field, ICN.\n
\n
\n"], ["220", "
SEVERE
\n", "
Error Setting Up HL7
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nError returned from HL7 call to setup hl7 variables or sending messages.\n
\n
\n"], ["221", "
INFORMATIONAL
\n", "
Missing Site/CMOR
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nSite/CMOR not in CMOR message\n
\n
\n"], ["222", "
SEVERE
\n", "
Invalid Event Type
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nInvalid Event passed in CMOR message\n
\n
\n"], ["223", "
INFORMATIONAL
\n", "
Missing Excepted Field
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMissing excepted field\n
\n
\n"], ["224", "
SEVERE
\n", "
Missing/Unable to get Logical Link
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nLink was unable to be retrieved.\n
\n
\n"], ["225", "
SEVERE
\n", "
Have Subscribers
\n", "
MAIL
\n", "", "
0
\n", "
RG CIRN DEMOGRAPHIC ISSUES
\n", "
\nHave subscribers for given patient and can not have subscribers to perform\naction.\n
\n
\n"], ["226", "
SEVERE
\n", "
Not CMOR
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nMessage received is not from the CMOR and should not be processed.\n
\n
\n"], ["227", "
MINOR
\n", "
Multiple ICNs
\n", "
MAIL
\n", "", "
9
\n", "", "
\nThere is a new business rule that "More than one patient in a single\n Patient file can not have the same ICN".  If an ICN is returned from the\n MPI and another patient in that database already has that same ICN, an\n exception will be logged and the ICN, CMOR, etc will not be updated for\n this new patient. \n
\n
\n"], ["228", "
SEVERE
\n", "
Patient Does Not Exist
\n", "
MPI EXCEPTION HANDLER
\n", "", "
4
\n", "
MPIF EXCEPTIONS
\n", "
\nThe patient does not exist in the patient file.\n
\n
\n"], ["229", "
SEVERE
\n", "
Duplicate Station Number in Institution File (#4)
\n", "
MPI EXCEPTION HANDLER
\n", "", "
6
\n", "
MPIF EXCEPTIONS
\n", "
\nA Station Number has been entered for multiple institutions in\nthe Institution (#4) file.\n
\n
\n"], ["230", "
SEVERE
\n", "
Invalid Sender Of Facility Integration Message
\n", "
MPI EXCEPTION HANDLER
\n", "", "", "
MPIF EXCEPTIONS
\n", "
\nThe CMOR can only accept the Facility Integration Message from the legacy site.\n
\n
\n"], ["231", "
MINOR
\n", "
Treating Facility Not Known To CMOR
\n", "
MPI EXCEPTION HANDLER
\n", "", "", "
MPIF EXCEPTIONS
\n", "
\nThis site has treating facilities for the patient that the\nCMOR does not have.\n
\n
\n"], ["232", "
MINOR
\n", "
Subscriber Not Known To CMOR
\n", "
MPI EXCEPTION HANDLER
\n", "", "", "
MPIF EXCEPTIONS
\n", "
\nThis site has subscribers that the CMOR does not have.\n
\n
\n"], ["233", "
SEVERE
\n", "
Cannot Merge Duplicate Pair
\n", "
MAIL
\n", "", "", "
RG CIRN DEMOGRAPHIC ISSUES
\n", "
\nRecord pair rejected during merge due to a conflict in ICN or CMOR data.\nCheck the pair.\n
\n
\n"], ["234", "
MINOR
\n", "
Primary View Reject
\n", "", "", "
76
\n", "", "
\nVistA data was rejected on the MPI either because the Authority Score was \nnot high enough, or it failed a business rule.\n
\n
\n"], ["6", "
SEVERE
\n", "
Unexpected system error
\n", "
MPI EXCEPTION HANDLER
\n", "", "
1517
\n", "
MPIF EXCEPTIONS
\n", "
\nAn unexpected error caused processing of the message to terminate prematurely.  \nThis should be reported to the CIRN Support Team for analysis and remedial \naction.\n
\n
\n"], ["7", "
SEVERE
\n", "
Unknown segment identifier
\n", "
MPI EXCEPTION HANDLER
\n", "", "
0
\n", "
MPIF EXCEPTIONS
\n", "
\nA segment identifier is not recognized as valid by CIRN.  This could be caused \nby a corrupt message, a message that has been directed to the wrong receiver, \nor a change in the format of the message. \n
\n
\n"]]}