{"aaData": [["1", "
\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
\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
\nMissing BHS Segment in message received from the MPI in the batch load\ninitialization.\n\n
\nMissing MSH segment in MPI Batch Message being processed from the MPI.\n\n
\nMissing QAK segment in MPI Batch Initialization Message from the MPI.\n\n
\nMissing MSA segment from MPI Batch Initialization Message from the MPI.\n\n
\nMissing RDF Segment from MPI Initialization Batch Message from the MPI.\n\n
\nMissing RDT Segment from the Batch Initialization Message from the MPI.\n\n
\nUnable to create VTQ query segment in Batch Initialization Message to the\nMPI. Tracking only missing encoding characters or invalid DFN.\n\n
\nApplication Rejection Error, wrong application sent in message to MPI.\n\n
\nApplication Error returned from the MPI.\n\n
\nRequired fields: Name, date of birth, sex or SSN\nare missing for the patient sent to the MPI for ICN assignment.\n\n
\nPatient DFN is bad, lookup in Patient file failed.\n\n
\nCMOR Lookup failed in Institution file. Maybe two entries with the same\nstation number or missing a station number.\n\n
\nAttempted to add treating facility update to Adt/HL7 Pivot file and it\nfailed to add.\n\n
\nSSN returned from MPI did not match DFN's entry in Patient file.\n\n
\nName returned from MPI did not match DFN's entry in Patient file.\n\n
\nMPI had Date of Death field populated. Vista did not have Date of Death.\n\n
\nVISTA had Date of Death field populated. MPI did not have Date of Death.\n\n
\nMPI and VistA had different dates of death for this patient.\n\n
\nMissing or Local ICN resolution job returned potential matches from the\nMPI. This must be resolved via the Interactive Query option.\n\n
\nThe message being prcessed is missing required field, ICN.\n\n
\nError returned from HL7 call to setup hl7 variables or sending messages.\n\n
\nSite/CMOR not in CMOR message\n\n
\nInvalid Event passed in CMOR message\n\n
\nMissing excepted field\n\n
\nLink was unable to be retrieved.\n\n
\nHave subscribers for given patient and can not have subscribers to perform\naction.\n\n
\nMessage received is not from the CMOR and should not be processed.\n\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
\nThe patient does not exist in the patient file.\n\n
\nA Station Number has been entered for multiple institutions in\nthe Institution (#4) file.\n\n
\nThe CMOR can only accept the Facility Integration Message from the legacy site.\n\n
\nThis site has treating facilities for the patient that the\nCMOR does not have.\n\n
\nThis site has subscribers that the CMOR does not have.\n\n
\nRecord pair rejected during merge due to a conflict in ICN or CMOR data.\nCheck the pair.\n\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
\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
\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