{"aaData": [["1", "NAME FORMAT UNACCEPTABLE", "
\nInconsistency results if the name contains lower case characters,\nnumeric characters and/or any punctuation other than commas, periods\nor hyphens (dashes).\n\n
\nInconsistency occurs if the patient is a veteran and the 'SERVICE\nCONNECTED' prompt is unanswered.\n\n
\nInconsistency results if the 'SERVICE CONNECTED' prompt is\ninconsistent with the 'VETERAN (Y/N)' prompt.\n\n
\nInconsistency results if the patient is a veteran, the 'SERVICE\nCONNECTED' prompt is answered YES and the 'SERVICE CONNECTED\nPERCENTAGE' prompt is not answered.\n\n
\nInconsistency results if the 'PERIOD OF SERVICE' prompt is unanswered.\n\n
\nInconsistency results if the 'ELIGIBILITY CODE' prompt is\nunanswered.\n\n
\nInconsistency results if an 'INELIGIBLE DATE' is entered but no\n'INELIGIBLE REASON' is specified.\n\n
\nInconsistency results if the patient has a 'DATE OF DEATH' entered\nwhich is a future date.\n\n
\nInconsistency results if the patient has expired (a 'DATE OF DEATH'\nis entered) and the patient still has appointments pending.\n\n
\nInconsistency results when the 'VETERAN (Y/N)' prompt is answered\nYES but the 'ELIGIBILITY CODE' assigned is a non-veteran specific\ncode.\n\n
\nInconsistency results if the 'VETERAN (Y/N)' prompt is answered NO\nbut the 'ELIGIBILITY CODE' assigned is a veteran specific code.\n\n
\nInconsistency results if the first character of the 'ALIAS' name\nis not an alphabetic character.\n\n
\nInconsistency results if the 'SERVICE CONNECTED PERCENTAGE' prompt\nis inconsistent with the 'ELIGIBILITY CODE' entered.\n\n
\nInconsistency results if the patient is currently residing in a\ndomiciliary and the 'ELIGIBILITY CODE' is not entered as\n'DOMICILIARY PATIENT'.\n\n
\nInconsistency results if the 'ELIGIBILITY CODE' prompt is answered\nbut is inconsistent with other data elements, i.e., 'IN RECEIPT OF\nA&A', etc.\n\n
\nInconsistency results if the 'ELIG STATUS' prompt is VERIFIED but\nthe 'ELIG STATUS DATE' is unspecified.\n\n
\nInconsistency results if the 'PERIOD OF SERVICE' entered is not\ncompatible with the 'ELIGIBILITY CODE' entered.\n\n
\nInconsistency results if the patient is a veteran, the 'EXPOSED TO AGENT\nORANGE' prompt is answered YES, and the 'PERIOD OF SERVICE' prompt is not\nanswered VIETNAM ERA (#7). This Inconsistency is no longer valid with the \naddition of new Agent Orange Exposure Locations with the PACT Act of \n2022. This check has been set to DON'T CHECK by patch DG*5.3*1090. This \nConsistency Check should not be changed to CHECK at the local level.\n\n
\nInconsistency results if the patient is a non-veteran and the 'DID YOU\nSERVE IN VIETNAM' prompt is answered YES.\n\n
\nInconsistency results if the patient is a non-veteran and the 'EXPOSED\nTO AGENT ORANGE' prompt is answered YES.\n\n
\nInconsistency results if the patient is a non-veteran and the\n'WERE YOU EXPOSED TO RADIATION' prompt is answered YES.\n\n
\nInconsistency results if patient is not a veteran and the 'ARE YOU\nIN RECEIPT OF A&A' prompt is answered YES.\n\n
\nInconsistency results if the 'SEX' prompt is unanswered.\n\n
\nInconsistency results if the patient is a non-veteran but the 'IN\nRECEIPT OF HB BENEFITS' prompt is answered YES.\n\n
\nThe last name of the name components is not present.\nThis applies to patient, spouse and dependents.\n\n
\nThe person's gender value is missing. This applies to\npatient, spouse and dependents.\n\n
\nThe person has a gender value, but it is not either\nmale or female. This applies to patient, spouse and\ndependents.\n\n
\nPatient must have a valid SSN or a Pseudo SSN.\n\n
\nIf a Pseudo SSN number is entered for a person, spouse\nor dependents, then a reason must be entered.\n\n
\nThe Date of Death cannot be prior to the Date of Birth.\n\n
\nThe value of Relationship to Patient does not match\none of the valid values.\n\n
\nInconsistency results if the patient is a non-veteran and the 'ARE\nYOU RECEIVING A VA PENSION' prompt is answered YES.\n\n
\nA dependent is present but the effective date is null.\n\n
\nPerson does not have National ICN.\n\n
\nThis check is to ensure the Newborn being registered is attached to an \neligible mother.\n\n
\nThis check ensures a patient has been asked about their registration, or \ninterest in registration, in My HealtheVet. It will only be checked if the \n'Enable MyHealtheVet Prompts?' (#1100.07) field in the MAS PARAMETERS (#43)\nfile is set to 'YES'.\n\n
\nInconsistency results if the patient is a non-veteran and the 'IN\nRECEIPT OF MILIT RETIREMENT' prompt is answered YES.\n\n
\nInconsistency results if the patient is a non-veteran but the 'DO\nYOU HAVE GI INSURANCE' prompt is answered YES.\n\n
\nInconsistency results if the patient is a non-veteran and the 'WERE\nYOU A PRISONER OF WAR' prompt is answered YES.\n\n
\nInconsistency results is the patient is a non-veteran and the\n'COMBAT (Y/N)' prompt is answered YES.\n\n
\nInconsistency results when the TYPE field of the PATIENT file is not\nspecified for a specific patient. The TYPE field indicates the TYPE\nOF PATIENT as selected from file #391.\n\n
\nInconsistency results when the user responds YES to the WERE YOU A\nPRISONER OF WAR prompt and any (or all) of the following prompts are\nleft unanswered: POW WAR, POW FROM DATE, POW TO DATE. This inconsistency \nalso results when an imprecise date (without at least month and year \nprecision) is entered.\n\n
\nInconsistency results when the user responds YES to the WERE YOU A\nA PRISONER OF WAR prompt and the 'from' date does not precede the 'to'\ndate.\n\n
\nInconsistency results when the user responds YES to the IN COMBAT (Y/N)\nand any (or all) of the following prompts are left unanswered: COMBAT\nWHERE, COMBAT FROM DATE, COMBAT TO DATE. This inconsistency also results\nwhen an imprecise date (without at least month and year precision) is\nentered.\n\n
\nInconsistency results if the 'DOB' prompt is not answered.\n\n
\nInconsistency results when the COMBAT (Y/N) prompt is answered YES\nbut the 'to' date precedes the 'from' date of service.\n\n
\nIf completed, the value of Rated Incompetent must be either yes,\nno, or unknown.\n\n
\nIf completed, the value of Eligible For Medicaid must be either\nyes or no.\n\n
\nThe value of 'Eligible for Medicaid' is Yes, but the Date Medicaid\nLast Asked value is null.\n\n
\nClaim Folder Number must consist of 7 or 8, or 9 numbers if SSN.\n\n
\nThe value of Eligibility Status is completed, but it does not match\none of the values.\n\n
\nA Means Test is present, the status of the test is either MT Co-Pay\nRequired, GMT Co-Pay Required or Pending Adjudication and Agree to\npay Deductible is null.\n\n
\nInconsistency results when user responds YES to the DID YOU SERVE IN\nVETNAM prompt and either (or both) the VIETNAM FROM DATE or VIETNAM\nTO DATE prompts are left unanswered.\n\n
\nEnrollment Application Date must be a precise date.\n\n
\nInconsistency results when the DID YOU SERVE IN VIETNAM prompt is\nanswered YES but the 'to' date of service preceeds the 'from' date.\n\n
\nInconsistency results when the user answers YES to the IN RECEIPT OF\nA&A prompt and yet no dollars are specified.\n\n
\nInconsistency results when user responds YES to IN RECEIPT OF HB\nBENEFITS prompt and yet no dollars are specified.\n\n
\nInconsistency results when user responds YES to RECEIVING A VA PENSION\nprompt and yet no dollars are entered.\n\n
\nInconsistency results when user responds YES to the IN RECEIPT OF SOCIAL\nSECURITY prompt and yet no dollars are entered.\n\n
\nInconsistency results when the user responds YES to the RECEIVING\nA MILITARY RETIREMENT prompt and yet no dollar amount is entered.\n\n
\nInconsistency results when user responds YES to DO YOU HAVE GI\nINSURANCE prompt and yet no dollars are entered.\n\n
\nInconsistency results when user answers the COVERED BY HEALTH INSURANCE\nprompt YES but either there are no policies entered or all of those\nentered have expired.\n\n
\nInconsistency results if the 'MARITAL STATUS' prompt is unanswered.\n\n
\nInconsistency results when the COVERED BY INSURANCE prompt is either\nnot answered or answered other than YES and yet ACTIVE policies are\nfound to be on file.\n\n
\nIf completed, the value of POW Status Indicated must be either\nYes, No, or Unknown.\n\n
\nThe Value of Mil. Dis. Retirement is completed, but does not\nmatch any valid value. (Note: This value is replacing\nDisability Retirement from Military.)\n\n
\nThe Value for Discharge Due to Disability is completed but\nnot a valid value.\n\n
\nIf completed, the value of Exposed to Agent Orange must be\neither Yes, No, or Unknown\n\n
\nIf completed, the value of Radiation Exposure Indicated must\nbe either Yes, No, or Unknown.\n\n
\nIf completed, the value for Southwest Asia Conditions must be\nYes, No or Unknown.\n\n
\nRadiation Exposure Indicated is Yes and Radiation Exposure Method\nis null. This Inconsistency is no longer valid with the addition of new \nRadiation Exposure Methods with the PACT Act of 2022. This check has been \nset to DON'T CHECK by patch DG*5.3*1090. This Consistency Check should \nnot be changed to CHECK at the local level.\n\n
\nThe value of MST Status is completed, but it does not match one\nof the values.\n\n
\nMST Status Change Date is required if MST Status is Yes, No, or\nor Declines to answer.\n\n
\nInconsistency results if PERIOD OF SERVICE is Z, but none of the BRANCH OF\nSERVICE fields (LAST, NTL, or NNTL) are answered 7 (Merchant Seaman) or if\nLAST BRANCH OF SERVICE is 7, but PERIOD OF SERVICE is not Z.\n\n
\nSite Determining MST Status is required if MST Status is Yes, No,\nor Declines to answer.\n\n
\nThe Site Determining MST Status is present, but the type of\n Institution that it points to is not identified as a VA Medical\nCenter or an Outpatient Clinic.\n\n
\nDOB is Inconsistent With Eligibility Of Mexican Border War.\n\n
\nDOB is Inconsistent With Eligibility Of World War I.\n\n
\nInconsistency occurs if there is no response to the 'Covered by Health\nInsurance?' prompt on registration screen 5. This prompt must contain\neither 'YES', 'NO', or 'UNKNOWN'.\n\n
\nInconsistency occurs if there is no response to the 'Employment Status'\nprompt on registration screen 4.\n\n
\nThis inconsistency will be filed if, on screen 8 of registration, the\n verification matching.\nsocial security field is not filled in for either the spouse or one of\nthe dependents. The social security number is required for IVM (Income\nVerification Matching) with the IRS. This data must be filled in as soon\nas possible.\n \nNOTE: Although, you will be allowed to turn this consistency check off, it\n is STRONGLY RECOMMENDED that it remain ON. The collection of the\n social security number for each dependent is mandatory for income\n\n
\nThis inconsistency results if all of the income questions on screen 9\nmedical care copayments is mandatory for all NSC and 0% SC\nnoncompensable patients who do not have any special eligibilities.\nThis data will be utilized for IVM (Income Verification Matching)\nwith the IRS. Although you may turn this consistency check off,\nit is STRONGLY RECOMMENDED it remain ON.\nare null and the patient has not declined to provide their income\ninformation on his/her last Means Test (yet screen 9 is turned on\nfor this type of patient).\n \nYou will not be able to edit the inconsistency by using the checker\noption. You must edit the data on load/edit screen 9.\n \nNote: Collection of income data or agreement to pay the maximum\n\n
\nInconsistency results when the user answers YES to the RECEIVING VA\nDISABILITY prompt and yet no dollars are entered in the TOTAL ANNUAL VA\nCHECK AMOUNT field.\n\n
\nInconsistency results when ELIGIBLE FOR MEDICAID? has been answered YES\nand the DATE MEDICAID LAST ASKED has not been updated in greater than the\nnumber of days indicated in the MAS PARAMETER File Field (#46) DAYS TO \nUPDATE MEDICAID (or 365 days if not specified).\n\n
\nInconsistency results if the Period of Service is not Persian Gulf\nor Somalia and the ENVIRONMENTAL CONTAMINANTS prompt is answered\n'Yes'.\n\n
\nInconsistency results if the CATASTROPHICALLY DISABLED eligibility code is\nentered for the patient without the supporting catastrophic disability\ndetermination, or visa versa.\n\n
\nInconsistency results if the 'RELIGION' prompt is unanswered.\n\n
\nInconsistency results if the 'EXPOSED TO AGENT ORANGE' prompt is answered\nYES and the 'AGENT ORANGE EXPOSURE LOCATION' prompt is not answered.\n\n
\nInconsistency results if the patient's Employment Status is EMPLOYED FULL\nTIME, EMPLOYED PART TIME, or SELF EMPLOYED and the PHONE NUMBER [WORK] has\nnot been entered.\n\n
\nInconsistency results if the emergency contact name is not entered.\n\n
\nInconsistency results if a record with an active confidential\naddress does not contain the first line of the street address,\ncity, state, and zip code for the confidential address.\n\n
\nInconsistency results if the Patient's Place of Birth City or\nState have not been entered.\n\n
\nInconsistency results if the Mother's Maiden Name is not entered.\n\n
\nInconsistency results if a Pseudo SSN has been entered.\n\n
\nCombat Vet status cannot be determined if critical dates are missing or imprecise.\n\n
\nCombat Vet status cannot be determined if critical dates are missing or imprecise.\n\n
\nCombat Vet status cannot be determined if critical dates are missing or imprecise.\n\n
\nInconsistency results if the 'SSN' prompt is unanswered.\n\n
\nCombat Vet status cannot be determined if critical dates are missing or imprecise.\n\n
\nEnter the name of the VA staff physician who made the \ndecision that the patient was catastrophically disabled.\n\n
\nEnter the name of the VA staff physician who made the \ndecision that the patient was catastrophically disabled.\n\n
\nEnter the name of the VA staff physician who made the \ndecision that the patient was catastrophically disabled.\nThis is a required field.\n\n
\nEnter the date that a review to determine Catastrophic Disability \nwas made. This review may be a medical record review or\nphysical exam review.\n\n
\nEnter the date that a review to determine Catastrophic Disability \nwas made. This review may be a medical record review or\nphysical exam review.\n\n
\nThe exact criteria for the score are determined by the\nCATASTROPHIC DISABILITY REASONS file (#27.17). This file\nalso contains the help text for responding to SCORE.\n\n
\nThe Catastrophic Disability Review Date must be before \nthe date of decision.\n\n
\nIf completed, AFFECTED EXTREMITY must be one of \nthe following codes: \n RUE:RIGHT UPPER EXTREMITY\n LUE:LEFT UPPER EXTREMITY\n RLE:RIGHT LOWER EXTREMITY\n LLE:LEFT LOWER EXTREMITY\n\n
\nThe status diagnosis must be a valid diagnosis in the \nCD Reasons File (#27.17).\n\n
\nCombat Vet status cannot be determined if critical dates are missing or imprecise.\n\n
\nThe status procedure must be a valid procedure in the \nCD Reasons File (#27.17).\n\n
\nA CD status reason is required for each CD \nCondition, Diagnosis and Procedure \nthat is entered.\n\n
\nEnter the date the catastrophic disability determination was \nmade. This must be a valid date.\n\n
\nThe 'Date of Catastrophic Disability Decision is required if the patient \nis catastrophically disabled. Enter the date the catastrophic disability \ndetermination was made. This must be a valid date.\n\n
\nThe Facility Making Catastrophic Disability Determination must be \na valid facility and defined in the INSTITUTION file (#4).\n\n
\nMethod of Determination is a required field. Possible values are:\n 2:MEDICAL RECORD REVIEW:\n 3:PHYSICAL EXAMINATION \nThe valid codes may vary depending on the Institution.\n\n
\nMethod of Determination is a required field. Possible values are:\n 2:MEDICAL RECORD REVIEW:\n 3:PHYSICAL EXAMINATION \nThe valid codes may vary depending on the Institution.\n\n
\nNot Enough Diagnoses/Procedures/Conditions To \nqualify For CD Status'\n\n
\nThe Permanent Status Indicator should be one of the following: \n 1:PERMANENT\n 2:NOT PERMANENT\n 3:UNKNOWN \n\n
\nIndicate if the Veteran is Catastrophically Disabled.\nThis is a required field\n\n
\nInconsistency results when any of the required MSE data fields are \neither left blank or an imprecise date (less than month/year precision) \nis entered. The following fields are required for any given Military \nService Episode: BRANCH OF SERVICE, SERVICE ENTRY DATE, SERVICE \nSEPARATION DATE, DISCHARGE TYPE.\n\n
\nThe Veteran Has Enough Diagnoses/Procedures/Conditions To Qualify For CD \nStatus\n\n
\nInconsistency results when the Review date is not a precise calendar date.\n\n
\nInconsistency results when the Date of Decision is not a precise calendar\ndate.\n\n
\nAn Affected Extremity is required for each procedure code received \nfor a Catastrophically Disabled veteran\n\n
\nA score is required for each condition code entered for catastrophically \ndisabled determinations \n\n
\nThe status descriptor must be a valid descriptor in the CD Reasons File\n(#27.17). \n\n
\nA CD status reason is required for each CD Condition, Diagnosis, \nProcedure and Descriptor that is entered.\n\n
\nwhat code is determined by this\n\n
\nInconsistency results when a SERVICE ENTRY DATE is found to be after the\nSERVICE SEPARATION DATE.\n\n
\nThis inconsistency results when a conflict date is either missing or \nincomplete (imprecise dates must have at least month and year). The \nfollowing date fields can trigger this inconsistency: SOMALIA FROM DATE,\nSOMALIA TO DATE, YUGOSLAVIA FROM DATE, YUGOSLAVIA TO DATE, PANAMA FROM \nDATE, PANAMA TO DATE, GRENADA FROM DATE, GRENADA TO DATE, LEBANON FROM \nDATE, LEBANON TO DATE, VIETNAM FROM DATE, VIETNAM TO DATE, GULF WAR FROM\nDATE, GULF WAR TO DATE.\n\n
\nThis inconsistency results when a conflict to date is prior to a conflict \nfrom date. The following date fields can trigger this inconsistency:\nSOMALIA FROM DATE, SOMALIA TO DATE, YUGOSLAVIA FROM DATE, YUGOSLAVIA TO\nDATE, PANAMA FROM DATE, PANAMA TO DATE, GRENADA FROM DATE, GRENADA TO\nDATE, LEBANON FROM DATE, LEBANON TO DATE, VIETNAM FROM DATE, VIETNAM TO\nDATE, GULF WAR FROM DATE, GULF WAR TO DATE.\n\n
\nThis inconsistency results when a conflict from and/or to date is not \nwithin the designated date ranges for the specific conflict.\n \nThe following date fields can trigger this inconsistency:\nSOMALIA FROM DATE, SOMALIA TO DATE, YUGOSLAVIA FROM DATE, YUGOSLAVIA TO\nDATE, PANAMA FROM DATE, PANAMA TO DATE, GRENADA FROM DATE, GRENADA TO\nDATE, LEBANON FROM DATE, LEBANON TO DATE, VIETNAM FROM DATE, VIETNAM TO\nDATE, GULF WAR FROM DATE, GULF WAR TO DATE.\n\n
\nThis inconsistency results when the POW from and/or to date is not \nwithin the designated date range for the specified POW LOCATION.\n\n
\nThis inconsistency results when the COMBAT from and/or to date is \nnot within the designated date range for the specified COMBAT LOCATION.\n\n
\nThis inconsistency results when more than one Military Service \nEpisode exists for this patient on a single day.\n\n
\nInconsistency results if the first line of the street address, city,\nstate, zip code and/or county are not specified.\n\n
\nThis inconsistency results when the entered POW From/To Dates are not \nwithin the patient's military service episodes.\n\n
\nThis inconsistency results when the entered COMBAT From/To Dates are not\nwithin the patient's military service episodes.\n\n
\nThis inconsistency results when the entered Conflict From/To Dates are not\nwithin the patient's military service episodes.\n \nThe following fields could cause this inconsistency to occur: SOMALIA\nFROM DATE, SOMALIA TO DATE, YUGOSLAVIA FROM DATE, YUGOSLAVIA TO DATE,\nPANAMA FROM DATE, PANAMA TO DATE, GRENADA FROM DATE, GRENADA TO DATE,\nLEBANON FROM DATE, LEBANON TO DATE, VIETNAM FROM DATE, VIETNAM TO DATE,\nGULF WAR FROM DATE, GULF WAR TO DATE.\n\n
\nInconsistency results when the Branch of Service is MERCHANT SEAMAN or\none of the Filipino Veteran branches of service (F.COMMONWEALTH,\nF.GUERILLA, F.SCOUTS NEW, F.SCOUTS OLD) but neither the Military\nService Start Date nor the Service End Date is within World War II\n(12/7/1941 - 8/15/1945).\n\n
\nInconsistency results if a Filipino Veteran branch of service is entered\n(F.COMMONWEATH, F.GUERILLA, or F.SCOUTS NEW) but the FILIPINO VET PROOF\nfield is left blank.\n\n
\nInconsistency results if a veteran has a Filipino Veteran branch of\nservice (F.COMMONWEALTH, F.GUERILLA, F.SCOUTS NEW, or F.SCOUTS OLD),\nmilitary service dates during World War II, proof of F.Vet eligibility\n(for the first three BOS only), but the Veteran Status is not 'YES'.\n\n
\nInconsistency results if a veteran has a Filipino Veteran branch of\nservice (F.COMMONWEALTH, F.GUERILLA, F.SCOUTS NEW, or F.SCOUTS OLD),\nbut is ineligible because of no World War II military service dates\nor no proof of F.Vet eligibility (for the first three BOS only), and\nthe Veteran Status is set to 'YES'.\n\n
\nInconsistency results if the PRIMARY ELIGIBILITY CODE\nis a 1 (SERVICE CONNECTED 50% TO 100%) or a 3 (SC LESS THAN 50%)\nand no rated disabilities are present.\n\n
\nInconsistency results if a record with an active temporary\naddress does not contain the first line of the street address, city, state,\nand zip code for a domestic temporary address, or, for a foreign temporary\naddress, the first line of the street address and the city.\n\n
\nPatient Type is incompatible with Primary Eligibility of Expanded MH Care Non-Enrollee\n\n
\nInconsistency results if the 'VETERAN (Y/N)' prompt is not answered.\n\n
\nUnable to check further discrepancies because one or more of the\nfollowing data elements are not defined: Veteran, Eligibility Code\nand Period of Service.\n\n