Crosswalk - Validation Rules

7 - T-MSIS V1_1 to V2_0 Validation Rules Comparison- 2015-11-24.xlsx

Medicaid Statistical Information System (MSIS) and the Transformed - Medicaid Statistical Information System (T-MSIS) (CMS-R-284)

Crosswalk - Validation Rules

OMB: 0938-0345

Document [xlsx]
Download: xlsx | pdf

Overview

SMRY v1.1 to v2.0 Changes
v1.1 to v2.0 Valdtn Rules xWalk
Reading the Validation Logic

Sheet 1: SMRY v1.1 to v2.0 Changes
Summary of V1.1 to V2.0 Validation Rule Changes









V1.1 Error Number - all -





What changed Count of RowNo

Added: consistency 18
<--- Rules added so that validation checks are applied consistently in all analogous circumstances.
Added: format rule 1007
<--- Rules added so that a simple format check is applied consistently to all data elements.
Logic updated: other 226
<--- Rules revised because the assumptions on which they were based are faulty or because the logic was not robust enough to handle all scenarios.
Logic updated: parent/child overlap 4
<--- Revised logic to be consistent with V2.0 rule structure.
Logic updated: string matching 194
<--- Set of valid alphanumeric characters were expanded to allow any characters except pipes (|) and asterisks (*).
Merged 954
<--- Checks that can be performed together are combined. The entent of the rules remains unchanged.
Moved to R&C 244
<--- Checks are more appropriately performed during receipt and control processing. The entent of the rules remains unchanged.
No logic changes 1047
<--- The logic of these validation rules is essentially unchanged.
Retired: MSIS ID checks 61
<--- Rules retired because it is unnecessay to compare the structure of MSIS IDs to state-supplied naming conventions.
Retired: Other reasons 87
<--- Rules retired because the assumptions on which they were based are faulty or because the logic was not robust enough to handle all scenarios.
Revised rules may or may not be implemented in the future.
Retired: required value checks There were 2,868 rules in T-MSIS V1.1. The lines in the blue-highlighted box describe the changes to these rules that occurred in V2.0. See the tab entitled "v1.1 to v2.0 Valdtn Rules xWalk" for the specific rules impacted and the details of each change. 51
<--- T-MSIS is no longer issuing an error message on every instance of required data element not being reported.
























NOTE: This is the latest T-MSIS V1.1 -> V2.0 rules crosswalk document as of 2015-11-04. It is automatically generated from the T-MSIS 2.0 system, with some formatting done manually, and will be updated as bugs are discovered and fixed during the T-MSIS 2.0 beta.

Sheet 2: v1.1 to v2.0 Valdtn Rules xWalk




































































































































































































































RowNo Filter this column to see the rule-by-rule details for each category of change. What changed Filter this column to see the changes to a specific V1.1 rule. V1.1 Rule ID (CR_NO) V2.0 Rule Id File Name File Segment (With Record ID) Data Element Number Data Element Name V1.1 Tier This column describes the V1.1 rule logic. V1.1 Business Rule V1.1 Error Number V1.1 Error Message V2.0 Error Tier V2.0 Error Tier Name V2.0 Error Category V2.0 Error Category Name V2.0 Rule Type V2.0 Primary Record Type V2.0 Primary Record Type Id V2.0 Secondary Record Type V2.0 Secondary Record Type Id V2.0 Tertiary Record Type V2.0 Tertiary Record Type Id This column describes the V2.0 rule logic. (See the tab entitled "Reading the Validation Logic" for help in understanding the V2.0 rule nomenclature.) V2.0 Validation Logic V2.0 Primary Record Type Fields V2.0 Primary Record Type Fields (ids) V2.0 Secondary Record Type Fields V2.0 Secondary Record Type Fields (ids) V2.0 Tertiary Record Type Fields V2.0 Tertiary Record Type Fields (ids) V2.0 Primary Record Type Group Fields V2.0 Primary Record Type Group Fields (ids) V2.0 Secondary Record Type Group Fields V2.0 Secondary Record Type Group Fields (ids) V2.0 Primary to Tertiary Type Group Fields V2.0 Primary to Tertiary Type Group Fields (ids) V2.0 Tertiary Type Group Fields V2.0 Tertiary Type Group Fields (ids)
1 Moved to R&C CIP001-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2 Moved to R&C CIP001-0004
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP001 RECORD-ID 2 If FILE-NAME = "CLAIM-IP", then the first 3 positions of RECORD-ID must = "CIP" 150 Invalid or missing RECORD-ID

























3 Moved to R&C CIP003-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP003 SUBMISSION-TRANSACTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























4 Moved to R&C CIP004-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP004 FILE-ENCODING-SPECIFICATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























5 Moved to R&C CIP006-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP006 FILE-NAME 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























6 Moved to R&C CIP007-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP007 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























7 Moved to R&C CIP007-0004
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























8 Merged CIP008-0001 RULE-304 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED CIP008











9 Merged CIP008-0002 RULE-304 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED CIP008











10 Moved to R&C CIP008-0003
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed

























11 Moved to R&C CIP008-0004
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























12 Merged CIP009-0001 RULE-308 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD CIP009











13 Merged CIP009-0002 RULE-308 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP009 START-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD CIP009











14 Moved to R&C CIP009-0003
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























15 Moved to R&C CIP009-0004
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























16 Merged CIP010-0001 RULE-312 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP010 END-OF-TIME-PERIOD 1 If END-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD CIP010











17 Merged CIP010-0002 RULE-312 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD CIP010











18 Moved to R&C CIP010-0003
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP010 END-OF-TIME-PERIOD 2-M
2122


























19 Moved to R&C CIP010-0004
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP010 END-OF-TIME-PERIOD 2-M
2019


























20 Moved to R&C CIP011-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP011 FILE-STATUS-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























21 Moved to R&C CIP011-0002
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























22 Moved to R&C CIP012-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP012 SSN-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























23 Logic updated: other CIP012-0002 RULE-319 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP012 SSN-INDICATOR 3 Value for SSN-INDICATOR [CLAIMIP] must match SSN-INDICATOR [ELIGIBLE] 3007 Relational edit between SSN-INDICATOR [CLAIMIP] and SSN-INDICATOR [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) FILE-HEADER-RECORD-IP CIP00001 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@primaryRecord.SSN-INDICATOR) && fns.hasValue(@secondaryRecord.SSN-INDICATOR), then fns.isEqual(@primaryRecord.SSN-INDICATOR, @secondaryRecord.SSN-INDICATOR)' SSN-INDICATOR CIP012 SSN-INDICATOR ELG012

SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD CIP007,CIP009,CIP010 SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD ELG007,ELG009,ELG010



24 No logic changes CIP013-0001 RULE-320 CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP013 TOT-REC-CNT 1 If TOT-REC-CNT = 0. 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT CIP013











25 Moved to R&C CIP013-0002
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record

























26 Moved to R&C CIP014-0001
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























27 Moved to R&C CIP016-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























28 Moved to R&C CIP016-0004
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP016 RECORD-ID 2 If FILE-NAME = "CLAIM-IP", then the first 3 positions of RECORD-ID must = "CIP" 150 Invalid or missing RECORD-ID

























29 No logic changes CIP017-0001 RULE-325 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP017 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE CIP017











30 Logic updated: other CIP017-0004 RULE-326 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-IP-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 FILE-HEADER-RECORD-IP CIP00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE CIP017 SUBMITTING-STATE CIP007









31 Retired: Other reasons CIP018-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP018 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























32 No logic changes CIP018-0003 RULE-328 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-HEADER-RECORD-IP CIP00002



Field RECORD-NUMBER should be unique across all records of type CLAIM-HEADER-RECORD-IP RECORD-NUMBER CIP018











33 Logic updated: string matching CIP019-0001 RULE-329 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP019 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ORIG 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG CIP019











34 Logic updated: string matching CIP020-0001 RULE-330 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP020 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ CIP020











35 Retired: required value checks CIP021-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP021 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported.

























36 Retired: MSIS ID checks CIP022-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP022 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























37 Retired: MSIS ID checks CIP022-0002
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP022 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























38 No logic changes CIP022-0003 RULE-334 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP022 MSIS-IDENTIFICATION-NUM 2 If TYPE-OF-CLAIM = "4", "D", OR "X", then the first byte of MSIS-IDENTIFICATION-NUM must = "&" 2331 Relational edit between MSIS-IDENTIFICATION-NUM and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "4", "D", "X"), then fns.matches(@val.MSIS-IDENTIFICATION-NUM, "^&.*$")' TYPE-OF-CLAIM,MSIS-IDENTIFICATION-NUM CIP100,CIP022











39 Logic updated: other CIP022-0005 RULE-335 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP022 MSIS-IDENTIFICATION-NUM 3 MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3026 Edit that claim has matching PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 record failed 3 Relational error E3001 Missing corresponding record (multi file) (ex. missing eligibility record for claim header) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

For every record of type CLAIM-HEADER-RECORD-IP, there must be a valid record of type PRIMARY-DEMOGRAPHICS-ELIGIBILITY that matches on the join keys





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



40 No logic changes CIP023-0001 RULE-336 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP023 CROSSOVER-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CROSSOVER-INDICATOR CROSSOVER-INDICATOR CIP023











41 No logic changes CIP024-0001 RULE-337 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP024 TYPE-OF-HOSPITAL 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-HOSPITAL TYPE-OF-HOSPITAL CIP024











42 No logic changes CIP025-0001 RULE-338 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP025 1115A-DEMONSTRATION-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: 1115A-DEMONSTRATION-IND 1115A-DEMONSTRATION-IND CIP025











43 No logic changes CIP025-0003 RULE-339 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP025 1115A-DEMONSTRATION-IND 3 If 1115A-DEMONSTRATION-IND [ELIGIBLE] = 0 or 8-filled, then 1115A-DEMONSTRATION-IND must = 0 or 8-filled where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] 3055 An 1115A-DEMONSTRATION-IND does not match the 1115A-DEMONSTRATION-IND in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) 1115A-DEMONSTRATION-INFORMATION ELG00018 CLAIM-HEADER-RECORD-IP CIP00002

'if !fns.hasValue(@primaryRecord.1115A-DEMONSTRATION-IND) || fns.isEqual(@primaryRecord.1115A-DEMONSTRATION-IND, "0"), then !fns.hasValue(@secondaryRecord.1115A-DEMONSTRATION-IND) || fns.isEqual(@secondaryRecord.1115A-DEMONSTRATION-IND, "0")' 1115A-DEMONSTRATION-IND ELG233 1115A-DEMONSTRATION-IND CIP025

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG230,ELG232 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



44 No logic changes CIP026-0001 RULE-340 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP026 ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-IND ADJUSTMENT-IND CIP026











45 No logic changes CIP027-0001 RULE-341 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP027 ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE ADJUSTMENT-REASON-CODE CIP027











46 No logic changes CIP028-0001 RULE-342 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP028 ADMISSION-TYPE 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: ADMISSION-TYPE ADMISSION-TYPE CIP028











47 No logic changes CIP029-0001 RULE-343 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP029 DRG-DESCRIPTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DRG-DESCRIPTION DRG-DESCRIPTION CIP029











48 Merged CIP030-0001 RULE-344 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP030 ADMITTING-DIAGNOSIS-CODE 1 ADMITTING-DIAGNOSIS-CODE must equal a valid ICD9/10 valid value without embedded characters. 101 Value is not in required format 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE ADMITTING-DIAGNOSIS-CODE CIP030











49 Merged CIP030-0002 RULE-344 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP030 ADMITTING-DIAGNOSIS-CODE 1 ADMITTING-DIAGNOSIS-CODE <> 'E000'-'E9999 127 Admitting diagnosis code cannot be 'E000'-'E9999' 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE ADMITTING-DIAGNOSIS-CODE CIP030











50 No logic changes CIP031-0001 RULE-346 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP031 ADMITTING-DIAGNOSIS-CODE-FLAG 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG ADMITTING-DIAGNOSIS-CODE-FLAG CIP031











51 Merged CIP032-0001 RULE-347 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP032 DIAGNOSIS-CODE-1 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-1 CIP032











52 Merged CIP032-0002 RULE-347 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP032 DIAGNOSIS-CODE-1 1 If DIAGNOSIS-CODE-1 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-1 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-1 CIP032











53 No logic changes CIP033-0001 RULE-349 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP033 DIAGNOSIS-CODE-FLAG-1 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-1 CIP033











54 No logic changes CIP034-0001 RULE-350 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP034 DIAGNOSIS-POA-FLAG-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-1 CIP034











55 Merged CIP035-0001 RULE-351 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP035 DIAGNOSIS-CODE-2 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-2 CIP035











56 Merged CIP035-0002 RULE-351 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP035 DIAGNOSIS-CODE-2 1 If DIAGNOSIS-CODE-2 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-2 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-2 CIP035











57 Merged CIP035-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP035 DIAGNOSIS-CODE-2 2 If DIAGNOSIS-CODE-2 is not 8-filled, then DIAGNOSIS-CODE-2 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











58 No logic changes CIP035-0008 RULE-354 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP035 DIAGNOSIS-CODE-2 2 DIAGNOSIS-CODE-2 must be 8-filled if value for DIAGNOSIS-CODE-1 is 8-filled 2263 Relational edit between DIAGNOSIS-CODE-2 and DIAGNOSIS-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-1), then !fns.hasValue(@val.DIAGNOSIS-CODE-2)' DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2 CIP032,CIP035











59 No logic changes CIP036-0001 RULE-355 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP036 DIAGNOSIS-CODE-FLAG-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-2 CIP036











60 No logic changes CIP037-0001 RULE-356 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP037 DIAGNOSIS-POA-FLAG-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-2 CIP037











61 Merged CIP038-0001 RULE-357 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP038 DIAGNOSIS-CODE-3 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-3 CIP038











62 Merged CIP038-0002 RULE-357 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP038 DIAGNOSIS-CODE-3 1 If DIAGNOSIS-CODE-3 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-3 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-3 CIP038











63 Merged CIP038-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP038 DIAGNOSIS-CODE-3 2 If DIAGNOSIS-CODE-3 is not 8-filled, then DIAGNOSIS-CODE-3 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











64 No logic changes CIP038-0008 RULE-360 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP038 DIAGNOSIS-CODE-3 2 DIAGNOSIS-CODE-3 must be 8-filled if value for DIAGNOSIS-CODE-2 is 8-filled 2265 Relational edit between DIAGNOSIS-CODE-3 and DIAGNOSIS-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-2), then !fns.hasValue(@val.DIAGNOSIS-CODE-3)' DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3 CIP035,CIP038











65 No logic changes CIP039-0001 RULE-361 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP039 DIAGNOSIS-CODE-FLAG-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-3 CIP039











66 No logic changes CIP040-0001 RULE-362 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP040 DIAGNOSIS-POA-FLAG-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-3 CIP040











67 Merged CIP041-0001 RULE-363 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP041 DIAGNOSIS-CODE-4 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-4 CIP041











68 Merged CIP041-0002 RULE-363 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP041 DIAGNOSIS-CODE-4 1 If DIAGNOSIS-CODE-4 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-4 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-4 CIP041











69 Merged CIP041-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP041 DIAGNOSIS-CODE-4 2 If DIAGNOSIS-CODE-4 is not 8-filled, then DIAGNOSIS-CODE-4 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











70 No logic changes CIP041-0008 RULE-366 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP041 DIAGNOSIS-CODE-4 2 DIAGNOSIS-CODE-4 must be 8-filled if value for DIAGNOSIS-CODE-3 is 8-filled 2266 Relational edit between DIAGNOSIS-CODE-4 and DIAGNOSIS-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-3), then !fns.hasValue(@val.DIAGNOSIS-CODE-4)' DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4 CIP038,CIP041











71 No logic changes CIP042-0001 RULE-367 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP042 DIAGNOSIS-CODE-FLAG-4 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-4 CIP042











72 No logic changes CIP043-0001 RULE-368 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP043 DIAGNOSIS-POA-FLAG-4 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-4 CIP043











73 Merged CIP044-0001 RULE-369 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP044 DIAGNOSIS-CODE-5 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-5 CIP044











74 Merged CIP044-0002 RULE-369 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP044 DIAGNOSIS-CODE-5 1 If DIAGNOSIS-CODE-5 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-5 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-5 CIP044











75 Merged CIP044-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP044 DIAGNOSIS-CODE-5 2 If DIAGNOSIS-CODE-5 is not 8-filled, then DIAGNOSIS-CODE-5 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











76 No logic changes CIP044-0008 RULE-372 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP044 DIAGNOSIS-CODE-5 2 DIAGNOSIS-CODE-5 must be 8-filled if value for DIAGNOSIS-CODE-4 is 8-filled 2267 Relational edit between DIAGNOSIS-CODE-5 and DIAGNOSIS-CODE-4 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-4), then !fns.hasValue(@val.DIAGNOSIS-CODE-5)' DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 CIP041,CIP044











77 No logic changes CIP045-0001 RULE-373 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP045 DIAGNOSIS-CODE-FLAG-5 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-5 CIP045











78 No logic changes CIP046-0001 RULE-374 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP046 DIAGNOSIS-POA-FLAG-5 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-5 CIP046











79 Merged CIP047-0001 RULE-375 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP047 DIAGNOSIS-CODE-6 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-6 CIP047











80 Merged CIP047-0002 RULE-375 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP047 DIAGNOSIS-CODE-6 1 If DIAGNOSIS-CODE-6 is populated, it must contains valid characters. 120 Field contains invalid characters - If DIAGNOSIS-CODE-6 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-6 CIP047











81 Merged CIP047-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP047 DIAGNOSIS-CODE-6 2 If DIAGNOSIS-CODE-6 is not 8-filled, then DIAGNOSIS-CODE-6 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











82 No logic changes CIP047-0008 RULE-378 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP047 DIAGNOSIS-CODE-6 2 DIAGNOSIS-CODE-6 must be 8-filled if value for DIAGNOSIS-CODE-5 is 8-filled 2268 Relational edit between DIAGNOSIS-CODE-6 and DIAGNOSIS-CODE-5 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-5), then !fns.hasValue(@val.DIAGNOSIS-CODE-6)' DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6 CIP044,CIP047











83 No logic changes CIP048-0001 RULE-379 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP048 DIAGNOSIS-CODE-FLAG-6 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-6 CIP048











84 Merged CIP050-0001 RULE-380 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP050 DIAGNOSIS-CODE-7 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-7 CIP050











85 Merged CIP050-0002 RULE-380 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP050 DIAGNOSIS-CODE-7 1 If DIAGNOSIS-CODE-7 is populated, it must contains valid characters. 120 Field contains invalid characters - If DIAGNOSIS-CODE-7 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-7 CIP050











86 Merged CIP050-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP050 DIAGNOSIS-CODE-7 2 If DIAGNOSIS-CODE-7 is not 8-filled, then DIAGNOSIS-CODE-7 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











87 No logic changes CIP050-0008 RULE-383 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP050 DIAGNOSIS-CODE-7 2 DIAGNOSIS-CODE-7 must be 8-filled if value for DIAGNOSIS-CODE-6 is 8-filled 2269 Relational edit between DIAGNOSIS-CODE-7 and DIAGNOSIS-CODE-6 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-6), then !fns.hasValue(@val.DIAGNOSIS-CODE-7)' DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7 CIP047,CIP050











88 No logic changes CIP051-0001 RULE-384 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP051 DIAGNOSIS-CODE-FLAG-7 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-7 CIP051











89 Merged CIP053-0001 RULE-385 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP053 DIAGNOSIS-CODE-8 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-8 CIP053











90 Merged CIP053-0002 RULE-385 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP053 DIAGNOSIS-CODE-8 1 If DIAGNOSIS-CODE-8 is populated, it must contains valid characters. 120 Field contains invalid characters - If DIAGNOSIS-CODE-8 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-8 CIP053











91 Merged CIP053-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP053 DIAGNOSIS-CODE-8 2 If DIAGNOSIS-CODE-8 is not 8-filled, then DIAGNOSIS-CODE-8 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











92 No logic changes CIP053-0008 RULE-388 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP053 DIAGNOSIS-CODE-8 2 DIAGNOSIS-CODE-8 must be 8-filled if value for DIAGNOSIS-CODE-7 is 8-filled 2270 Relational edit between DIAGNOSIS-CODE-8 and DIAGNOSIS-CODE-7 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-7), then !fns.hasValue(@val.DIAGNOSIS-CODE-8)' DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8 CIP050,CIP053











93 No logic changes CIP054-0001 RULE-389 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP054 DIAGNOSIS-CODE-FLAG-8 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-8 CIP054











94 Merged CIP056-0001 RULE-390 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP056 DIAGNOSIS-CODE-9 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-9 CIP056











95 Merged CIP056-0002 RULE-390 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP056 DIAGNOSIS-CODE-9 1 If DIAGNOSIS-CODE-9 is populated, it must contains valid characters. 120 Field contains invalid characters - If DIAGNOSIS-CODE-9 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-9 CIP056











96 Merged CIP056-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP056 DIAGNOSIS-CODE-9 2 If DIAGNOSIS-CODE-9 is not 8-filled, then DIAGNOSIS-CODE-9 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











97 No logic changes CIP056-0008 RULE-393 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP056 DIAGNOSIS-CODE-9 2 DIAGNOSIS-CODE-9 must be 8-filled if value for DIAGNOSIS-CODE-8 is 8-filled 2271 Relational edit between DIAGNOSIS-CODE-9 and DIAGNOSIS-CODE-8 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-8), then !fns.hasValue(@val.DIAGNOSIS-CODE-9)' DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9 CIP053,CIP056











98 No logic changes CIP057-0001 RULE-394 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP057 DIAGNOSIS-CODE-FLAG-9 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-9 CIP057











99 Merged CIP059-0001 RULE-395 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP059 DIAGNOSIS-CODE-10 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-10 CIP059











100 Merged CIP059-0002 RULE-395 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP059 DIAGNOSIS-CODE-10 1 If DIAGNOSIS-CODE-10 is populated, it must contains valid characters. 120 Field contains invalid characters - If DIAGNOSIS-CODE-10 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-10 CIP059











101 Merged CIP059-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP059 DIAGNOSIS-CODE-10 2 If DIAGNOSIS-CODE-10 is not 8-filled, then DIAGNOSIS-CODE-10 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











102 No logic changes CIP059-0008 RULE-398 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP059 DIAGNOSIS-CODE-10 2 DIAGNOSIS-CODE-10 must be 8-filled if value for DIAGNOSIS-CODE-9 is 8-filled 2260 Relational edit between DIAGNOSIS-CODE-10 and DIAGNOSIS-CODE-9 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-9), then !fns.hasValue(@val.DIAGNOSIS-CODE-10)' DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10 CIP056,CIP059











103 No logic changes CIP060-0001 RULE-399 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP060 DIAGNOSIS-CODE-FLAG-10 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-10 CIP060











104 Merged CIP062-0001 RULE-400 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP062 DIAGNOSIS-CODE-11 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-11 CIP062











105 Merged CIP062-0002 RULE-400 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP062 DIAGNOSIS-CODE-11 1 If DIAGNOSIS-CODE-11 is populated, it must contains valid characters. 120 Field contains invalid characters - If DIAGNOSIS-CODE-11 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-11 CIP062











106 Merged CIP062-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP062 DIAGNOSIS-CODE-11 2 If DIAGNOSIS-CODE-11 is not 8-filled, then DIAGNOSIS-CODE-11 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











107 No logic changes CIP062-0008 RULE-403 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP062 DIAGNOSIS-CODE-11 2 DIAGNOSIS-CODE-11 must be 8-filled if value for DIAGNOSIS-CODE-10 is 8-filled 2261 Relational edit between DIAGNOSIS-CODE-11 and DIAGNOSIS-CODE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-10), then !fns.hasValue(@val.DIAGNOSIS-CODE-11)' DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11 CIP059,CIP062











108 No logic changes CIP063-0001 RULE-404 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP063 DIAGNOSIS-CODE-FLAG-11 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-11 CIP063











109 Merged CIP065-0001 RULE-405 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP065 DIAGNOSIS-CODE-12 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-12 CIP065











110 Merged CIP065-0002 RULE-405 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP065 DIAGNOSIS-CODE-12 1 If DIAGNOSIS-CODE-12 is populated, it must contains valid characters. 120 Field contains invalid characters - If DIAGNOSIS-CODE-12 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-12 CIP065











111 Merged CIP065-0007 RULE-353 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP065 DIAGNOSIS-CODE-12 2 If DIAGNOSIS-CODE-12 is not 8-filled, then DIAGNOSIS-CODE-12 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5,DIAGNOSIS-CODE-6,DIAGNOSIS-CODE-7,DIAGNOSIS-CODE-8,DIAGNOSIS-CODE-9,DIAGNOSIS-CODE-10,DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP032,CIP035,CIP038,CIP041,CIP044,CIP047,CIP050,CIP053,CIP056,CIP059,CIP062,CIP065











112 No logic changes CIP065-0008 RULE-408 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP065 DIAGNOSIS-CODE-12 2 DIAGNOSIS-CODE-12 must be 8-filled if value for DIAGNOSIS-CODE-11 is 8-filled 2262 Relational edit between DIAGNOSIS-CODE-12 and DIAGNOSIS-CODE-11 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-11), then !fns.hasValue(@val.DIAGNOSIS-CODE-12)' DIAGNOSIS-CODE-11,DIAGNOSIS-CODE-12 CIP062,CIP065











113 No logic changes CIP066-0001 RULE-409 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP066 DIAGNOSIS-CODE-FLAG-12 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-12 CIP066











114 No logic changes CIP068-0001 RULE-410 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP068 DIAGNOSIS-RELATED-GROUP 1 If DIAGNOSIS-RELATED-GROUP not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.DIAGNOSIS-RELATED-GROUP), then fns.isPositive(@val.DIAGNOSIS-RELATED-GROUP)' DIAGNOSIS-RELATED-GROUP CIP068











115 Logic updated: other CIP069-0001 RULE-411 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP069 DIAGNOSIS-RELATED-GROUP-IND 1 Value is not in required format 101 Value is not in required format 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'fns.isValidDiagnosisRelatedGroupIndicator(@val.SUBMITTING-STATE, @val.DIAGNOSIS-RELATED-GROUP-IND)' SUBMITTING-STATE,DIAGNOSIS-RELATED-GROUP-IND CIP017,CIP069











116 No logic changes CIP069-0003 RULE-412 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP069 DIAGNOSIS-RELATED-GROUP-IND 2 If DIAGNOSIS-RELATED-GROUP is not 8-filled, then DIAGNOSIS-RELATED-GROUP-IND must not be 8-filled 2272 Relational edit between DIAGNOSIS-RELATED-GROUP-IND and DIAGNOSIS-RELATED-GROUP failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.DIAGNOSIS-RELATED-GROUP), then fns.hasValue(@val.DIAGNOSIS-RELATED-GROUP-IND)' DIAGNOSIS-RELATED-GROUP,DIAGNOSIS-RELATED-GROUP-IND CIP068,CIP069











117 No logic changes CIP070-0001 RULE-413 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP070 PROCEDURE-CODE-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE PROCEDURE-CODE-1 CIP070











118 Merged CIP070-0003 RULE-414 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP070 PROCEDURE-CODE-1 2 If PROCEDURE-CODE-FLAG-1 is 8-filled, then PROCEDURE-CODE-1 must be 8-filled 2381 Relational edit between PROCEDURE-CODE-FLAG-1 and PROCEDURE-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-1), then fns.hasValue(@val.PROCEDURE-CODE-1)' PROCEDURE-CODE-FLAG-1,PROCEDURE-CODE-1 CIP072,CIP070











119 Merged CIP070-0004 RULE-414 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP070 PROCEDURE-CODE-1 2 If PROCEDURE-CODE-FLAG-1 is not 8-filled, then PROCEDURE-CODE-1 must not be 8-filled 2381 Relational edit between PROCEDURE-CODE-FLAG-1 and PROCEDURE-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-1), then fns.hasValue(@val.PROCEDURE-CODE-1)' PROCEDURE-CODE-FLAG-1,PROCEDURE-CODE-1 CIP072,CIP070











120 No logic changes CIP071-0001 RULE-416 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP071 PROCEDURE-CODE-MOD-1 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-1 CIP071











121 No logic changes CIP071-0003 RULE-417 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP071 PROCEDURE-CODE-MOD-1 2 If PROCEDURE-CODE-1 is 8-filled, then PROCEDURE-CODE-MOD-1 must be 8-filled 2382 Relational edit between PROCEDURE-CODE-MOD-1 and PROCEDURE-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-1), then !fns.hasValue(@val.PROCEDURE-CODE-MOD-1)' PROCEDURE-CODE-1,PROCEDURE-CODE-MOD-1 CIP070,CIP071











122 No logic changes CIP072-0001 RULE-418 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP072 PROCEDURE-CODE-FLAG-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-FLAG PROCEDURE-CODE-FLAG-1 CIP072











123 Merged CIP073-0001 RULE-419 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP073 PROCEDURE-CODE-DATE-1 1 If PROCEDURE-CODE-DATE-1 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-1 CIP073











124 Merged CIP073-0002 RULE-419 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP073 PROCEDURE-CODE-DATE-1 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-1 CIP073











125 No logic changes CIP073-0003 RULE-421 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP073 PROCEDURE-CODE-DATE-1 2 If PROCEDURE-CODE-1 is 8-filled, then PROCEDURE-CODE-DATE-1 must be 8-filled 2376 Relational edit between PROCEDURE-CODE-DATE-1 and PROCEDURE-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-1), then !fns.hasValue(@val.PROCEDURE-CODE-DATE-1)' PROCEDURE-CODE-1,PROCEDURE-CODE-DATE-1 CIP070,CIP073











126 Logic updated: other CIP073-0004 RULE-422 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP073 PROCEDURE-CODE-DATE-1 2 PROCEDURE-CODE-DATE-1 must be <= ENDING-DATE-OF-SERVICE 2449 Relational edit between PROCEDURE-CODE-DATE-1 and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-1) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@primaryRecord.PROCEDURE-CODE-DATE-1, @secondaryRecord.ENDING-DATE-OF-SERVICE)' PROCEDURE-CODE-DATE-1 CIP073 ENDING-DATE-OF-SERVICE CIP244

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



127 Logic updated: other CIP073-0005 RULE-423 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP073 PROCEDURE-CODE-DATE-1 2 PROCEDURE-CODE-DATE-1 must be >= BEGINNING-DATE-OF-SERVICE 2450 Relational edit between PROCEDURE-CODE-DATE-1 and BEGINNING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-1), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.PROCEDURE-CODE-DATE-1)' PROCEDURE-CODE-DATE-1 CIP073 BEGINNING-DATE-OF-SERVICE CIP243

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



128 Logic updated: other CIP073-0006 RULE-1 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP073 PROCEDURE-CODE-DATE-1 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then PROCEDURE-CODE-DATE-1 must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3041 Relational edit between PROCEDURE-CODE-DATE-1 and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PROCEDURE-CODE-DATE-1), then fns.isLessThanOrEqual(@secondaryRecord.PROCEDURE-CODE-DATE-1, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PROCEDURE-CODE-DATE-1 CIP073

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



129 No logic changes CIP074-0001 RULE-425 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP074 PROCEDURE-CODE-2 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE PROCEDURE-CODE-2 CIP074











130 Merged CIP074-0008 RULE-426 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP074 PROCEDURE-CODE-2 2 If PROCEDURE-CODE-FLAG-2 is 8-filled, then PROCEDURE-CODE-2 must be 8-filled 2371 Relational edit between PROCEDURE-CODE-2 and PROCEDURE-CODE-FLAG-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if !fns.hasValue(@val.PROCEDURE-CODE-FLAG-2), then !fns.hasValue(@val.PROCEDURE-CODE-2)' PROCEDURE-CODE-FLAG-2,PROCEDURE-CODE-2 CIP076,CIP074











131 Merged CIP074-0009 RULE-426 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP074 PROCEDURE-CODE-2 2 If PROCEDURE-CODE-FLAG-2 is not 8-filled, then PROCEDURE-CODE-2 must not be 8-filled 2371 Relational edit between PROCEDURE-CODE-2 and PROCEDURE-CODE-FLAG-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if !fns.hasValue(@val.PROCEDURE-CODE-FLAG-2), then !fns.hasValue(@val.PROCEDURE-CODE-2)' PROCEDURE-CODE-FLAG-2,PROCEDURE-CODE-2 CIP076,CIP074











132 Merged CIP074-0011 RULE-428 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP074 PROCEDURE-CODE-2 2 If PROCEDURE-CODE-2 is not 8-filled, then PROCEDURE-CODE-2 must <> value for the other instances of PROCEDURE-CODE 2146 Duplicate values of PROCEDURE-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 CIP070,CIP074,CIP078,CIP082,CIP086,CIP090











133 No logic changes CIP075-0001 RULE-429 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP075 PROCEDURE-CODE-MOD-2 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-2 CIP075











134 No logic changes CIP075-0003 RULE-430 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP075 PROCEDURE-CODE-MOD-2 2 If PROCEDURE-CODE-2 is 8-filled, then PROCEDURE-CODE-MOD-2 must be 8-filled 2383 Relational edit between PROCEDURE-CODE-MOD-2 and PROCEDURE-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-2), then !fns.hasValue(@val.PROCEDURE-CODE-MOD-2)' PROCEDURE-CODE-2,PROCEDURE-CODE-MOD-2 CIP074,CIP075











135 No logic changes CIP076-0001 RULE-431 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP076 PROCEDURE-CODE-FLAG-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-FLAG PROCEDURE-CODE-FLAG-2 CIP076











136 Merged CIP077-0001 RULE-432 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP077 PROCEDURE-CODE-DATE-2 1 If PROCEDURE-CODE-DATE-2 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-2 CIP077











137 Merged CIP077-0002 RULE-432 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP077 PROCEDURE-CODE-DATE-2 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-2 CIP077











138 No logic changes CIP077-0003 RULE-434 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP077 PROCEDURE-CODE-DATE-2 2 If PROCEDURE-CODE-2 is 8-filled, then PROCEDURE-CODE-DATE-2 must be 8-filled 2377 Relational edit between PROCEDURE-CODE-DATE-2 and PROCEDURE-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-2), then !fns.hasValue(@val.PROCEDURE-CODE-DATE-2)' PROCEDURE-CODE-2,PROCEDURE-CODE-DATE-2 CIP074,CIP077











139 Logic updated: other CIP077-0004 RULE-435 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP077 PROCEDURE-CODE-DATE-2 2 If PROCEDURE-CODE-DATE-2 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-2 must be <= ENDING-DATE-OF-SERVICE 2097 Relational edit between PROCEDURE-CODE-DATE-2 and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-2) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@primaryRecord.PROCEDURE-CODE-DATE-2, @secondaryRecord.ENDING-DATE-OF-SERVICE)' PROCEDURE-CODE-DATE-2 CIP077 ENDING-DATE-OF-SERVICE CIP244

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



140 Logic updated: other CIP077-0005 RULE-436 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP077 PROCEDURE-CODE-DATE-2 2 If PROCEDURE-CODE-DATE-2 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-2 must be >= BEGINNING-DATE-OF-SERVICE 2096 Relational edit between PROCEDURE-CODE-DATE-2 and BEGINNING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-2) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.PROCEDURE-CODE-DATE-2)' PROCEDURE-CODE-DATE-2 CIP077 BEGINNING-DATE-OF-SERVICE CIP243

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



141 Logic updated: other CIP077-0006 RULE-437 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP077 PROCEDURE-CODE-DATE-2 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then PROCEDURE-CODE-DATE-2 must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3042 Relational edit between PROCEDURE-CODE-DATE-2 and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PROCEDURE-CODE-DATE-2), then fns.isLessThanOrEqual(@secondaryRecord.PROCEDURE-CODE-DATE-2, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PROCEDURE-CODE-DATE-2 CIP077

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



142 No logic changes CIP078-0001 RULE-438 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP078 PROCEDURE-CODE-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE PROCEDURE-CODE-3 CIP078











143 Merged CIP078-0008 RULE-439 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP078 PROCEDURE-CODE-3 2 If PROCEDURE-CODE-FLAG-3 is 8-filled, then PROCEDURE-CODE-3 must be 8-filled 2372 Relational edit between PROCEDURE-CODE-3 and PROCEDURE-CODE-FLAG-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-3), then fns.hasValue(@val.PROCEDURE-CODE-3)' PROCEDURE-CODE-FLAG-3,PROCEDURE-CODE-3 CIP080,CIP078











144 Merged CIP078-0009 RULE-439 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP078 PROCEDURE-CODE-3 2 If PROCEDURE-CODE-FLAG-3 is not 8-filled, then PROCEDURE-CODE-3 must not be 8-filled 2372 Relational edit between PROCEDURE-CODE-3 and PROCEDURE-CODE-FLAG-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-3), then fns.hasValue(@val.PROCEDURE-CODE-3)' PROCEDURE-CODE-FLAG-3,PROCEDURE-CODE-3 CIP080,CIP078











145 Merged CIP078-0011 RULE-428 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP078 PROCEDURE-CODE-3 2 If PROCEDURE-CODE-3 is not 8-filled, then PROCEDURE-CODE-3 must <> value for the other instances of PROCEDURE-CODE 2146 Duplicate values of PROCEDURE-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 CIP070,CIP074,CIP078,CIP082,CIP086,CIP090











146 No logic changes CIP079-0001 RULE-442 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP079 PROCEDURE-CODE-MOD-3 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-3 CIP079











147 No logic changes CIP079-0002 RULE-443 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP079 PROCEDURE-CODE-MOD-3 2 If PROCEDURE-CODE-3 is 8-filled, then PROCEDURE-CODE-MOD-3 must be 8-filled 2384 Relational edit between PROCEDURE-CODE-MOD-3 and PROCEDURE-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-3), then !fns.hasValue(@val.PROCEDURE-CODE-MOD-3)' PROCEDURE-CODE-3,PROCEDURE-CODE-MOD-3 CIP078,CIP079











148 No logic changes CIP080-0001 RULE-444 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP080 PROCEDURE-CODE-FLAG-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-FLAG PROCEDURE-CODE-FLAG-3 CIP080











149 Merged CIP081-0001 RULE-445 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP081 PROCEDURE-CODE-DATE-3 1 If PROCEDURE-CODE-DATE-2 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-3 CIP081











150 Merged CIP081-0002 RULE-445 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP081 PROCEDURE-CODE-DATE-3 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-3 CIP081











151 No logic changes CIP081-0003 RULE-447 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP081 PROCEDURE-CODE-DATE-3 2 If PROCEDURE-CODE-3 is 8-filled, then PROCEDURE-CODE-DATE-3 must be 8-filled 2378 Relational edit between PROCEDURE-CODE-DATE-3 and PROCEDURE-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-3), then !fns.hasValue(@val.PROCEDURE-CODE-DATE-3)' PROCEDURE-CODE-3,PROCEDURE-CODE-DATE-3 CIP078,CIP081











152 Logic updated: other CIP081-0004 RULE-448 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP081 PROCEDURE-CODE-DATE-3 2 If PROCEDURE-CODE-DATE-3 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-3 must be <= ENDING-DATE-OF-SERVICE 2099 Relational edit between PROCEDURE-CODE-DATE-3 and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-3) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@primaryRecord.PROCEDURE-CODE-DATE-3, @secondaryRecord.ENDING-DATE-OF-SERVICE)' PROCEDURE-CODE-DATE-3 CIP081 ENDING-DATE-OF-SERVICE CIP244

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



153 Logic updated: other CIP081-0005 RULE-449 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP081 PROCEDURE-CODE-DATE-3 2 If PROCEDURE-CODE-DATE-3 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-3 must be >= BEGINNING-DATE-OF-SERVICE 2098 Relational edit between PROCEDURE-CODE-DATE-3 and BEGINNING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-3) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.PROCEDURE-CODE-DATE-3)' PROCEDURE-CODE-DATE-3 CIP081 BEGINNING-DATE-OF-SERVICE CIP243

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



154 Logic updated: other CIP081-0006 RULE-450 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP081 PROCEDURE-CODE-DATE-3 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then PROCEDURE-CODE-DATE-3 must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3043 Relational edit between PROCEDURE-CODE-DATE-3 and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PROCEDURE-CODE-DATE-3), then fns.isLessThanOrEqual(@secondaryRecord.PROCEDURE-CODE-DATE-3, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PROCEDURE-CODE-DATE-3 CIP081

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



155 No logic changes CIP082-0001 RULE-451 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP082 PROCEDURE-CODE-4 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE PROCEDURE-CODE-4 CIP082











156 Merged CIP082-0009 RULE-428 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP082 PROCEDURE-CODE-4 2 If PROCEDURE-CODE-4 is not 8-filled, then PROCEDURE-CODE-4 must <> value for the other instances of PROCEDURE-CODE 2146 Duplicate values of PROCEDURE-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 CIP070,CIP074,CIP078,CIP082,CIP086,CIP090











157 Merged CIP082-0010 RULE-453 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP082 PROCEDURE-CODE-4 2 If PROCEDURE-CODE-FLAG-4 is 8-filled, then PROCEDURE-CODE-4 must be 8-filled 2373 Relational edit between PROCEDURE-CODE-4 and PROCEDURE-CODE-FLAG-4 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-4), then fns.hasValue(@val.PROCEDURE-CODE-4)' PROCEDURE-CODE-FLAG-4,PROCEDURE-CODE-4 CIP084,CIP082











158 Merged CIP082-0011 RULE-453 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP082 PROCEDURE-CODE-4 2 If PROCEDURE-CODE-FLAG-4 is not 8-filled, then PROCEDURE-CODE-4 must not be 8-filled 2373 Relational edit between PROCEDURE-CODE-4 and PROCEDURE-CODE-FLAG-4 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-4), then fns.hasValue(@val.PROCEDURE-CODE-4)' PROCEDURE-CODE-FLAG-4,PROCEDURE-CODE-4 CIP084,CIP082











159 No logic changes CIP083-0001 RULE-455 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP083 PROCEDURE-CODE-MOD-4 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-4 CIP083











160 Merged CIP083-0002 RULE-456 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP083 PROCEDURE-CODE-MOD-4 2 If PROCEDURE-CODE-4 is 8-filled, then PROCEDURE-CODE-MOD-4 must be 8-filled 2385 Relational edit between PROCEDURE-CODE-MOD-4 and PROCEDURE-CODE-4 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-4), then !fns.hasValue(@val.PROCEDURE-CODE-MOD-4)' PROCEDURE-CODE-4,PROCEDURE-CODE-MOD-4 CIP082,CIP083











161 Merged CIP083-0003 RULE-456 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP083 PROCEDURE-CODE-MOD-4 2 If PROCEDURE-CODE is not 8-filled, then PROCEDURE-CODE-MOD-4 must not be 8-filled 2385 Relational edit between PROCEDURE-CODE-MOD-4 and PROCEDURE-CODE-4 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-4), then !fns.hasValue(@val.PROCEDURE-CODE-MOD-4)' PROCEDURE-CODE-4,PROCEDURE-CODE-MOD-4 CIP082,CIP083











162 No logic changes CIP084-0001 RULE-458 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP084 PROCEDURE-CODE-FLAG-4 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-FLAG PROCEDURE-CODE-FLAG-4 CIP084











163 Merged CIP085-0001 RULE-459 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP085 PROCEDURE-CODE-DATE-4 1 If PROCEDURE-CODE-DATE-2 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-4 CIP085











164 Merged CIP085-0002 RULE-459 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP085 PROCEDURE-CODE-DATE-4 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-4 CIP085











165 No logic changes CIP085-0003 RULE-461 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP085 PROCEDURE-CODE-DATE-4 2 If PROCEDURE-CODE-4 is 8-filled, then PROCEDURE-CODE-DATE-4 must be 8-filled 2379 Relational edit between PROCEDURE-CODE-DATE-4 and PROCEDURE-CODE-4 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-4), then !fns.hasValue(@val.PROCEDURE-CODE-DATE-4)' PROCEDURE-CODE-4,PROCEDURE-CODE-DATE-4 CIP082,CIP085











166 Logic updated: other CIP085-0004 RULE-462 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP085 PROCEDURE-CODE-DATE-4 2 If PROCEDURE-CODE-DATE-4 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-4 must be <= ENDING-DATE-OF-SERVICE 2101 Relational edit between PROCEDURE-CODE-DATE-4 and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-4) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@primaryRecord.PROCEDURE-CODE-DATE-4, @secondaryRecord.ENDING-DATE-OF-SERVICE)' PROCEDURE-CODE-DATE-4 CIP085 ENDING-DATE-OF-SERVICE CIP244

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



167 Logic updated: other CIP085-0005 RULE-463 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP085 PROCEDURE-CODE-DATE-4 2 If PROCEDURE-CODE-DATE-4 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-4 must be >= BEGINNING-DATE-OF-SERVICE 2100 Relational edit between PROCEDURE-CODE-DATE-4 and BEGINNING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-4) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.PROCEDURE-CODE-DATE-4)' PROCEDURE-CODE-DATE-4 CIP085 BEGINNING-DATE-OF-SERVICE CIP243

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



168 Logic updated: other CIP085-0006 RULE-464 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP085 PROCEDURE-CODE-DATE-4 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, PROCEDURE-CODE-DATE-4 must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3044 Relational edit between PROCEDURE-CODE-DATE-4 and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PROCEDURE-CODE-DATE-4), then fns.isLessThanOrEqual(@secondaryRecord.PROCEDURE-CODE-DATE-4, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PROCEDURE-CODE-DATE-4 CIP085

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



169 No logic changes CIP086-0001 RULE-465 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP086 PROCEDURE-CODE-5 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE PROCEDURE-CODE-5 CIP086











170 Merged CIP086-0008 RULE-428 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP086 PROCEDURE-CODE-5 2 If PROCEDURE-CODE-5 is not 8-filled, then PROCEDURE-CODE-5 must <> value for the other instances of PROCEDURE-CODE 2146 Duplicate values of PROCEDURE-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 CIP070,CIP074,CIP078,CIP082,CIP086,CIP090











171 Merged CIP086-0009 RULE-467 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP086 PROCEDURE-CODE-5 2 If PROCEDURE-CODE-FLAG-5 is 8-filled, then PROCEDURE-CODE-5 must be 8-filled 2374 Relational edit between PROCEDURE-CODE-5 and PROCEDURE-CODE-FLAG-5 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-5), then fns.hasValue(@val.PROCEDURE-CODE-5)' PROCEDURE-CODE-FLAG-5,PROCEDURE-CODE-5 CIP088,CIP086











172 Merged CIP086-0010 RULE-467 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP086 PROCEDURE-CODE-5 2 If PROCEDURE-CODE-FLAG-5 is not 8-filled, then PROCEDURE-CODE-5 must not be 8-filled 2374 Relational edit between PROCEDURE-CODE-5 and PROCEDURE-CODE-FLAG-5 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-5), then fns.hasValue(@val.PROCEDURE-CODE-5)' PROCEDURE-CODE-FLAG-5,PROCEDURE-CODE-5 CIP088,CIP086











173 No logic changes CIP087-0001 RULE-469 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP087 PROCEDURE-CODE-MOD-5 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-5 CIP087











174 No logic changes CIP087-0002 RULE-470 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP087 PROCEDURE-CODE-MOD-5 2 If PROCEDURE-CODE-5 is 8-filled, then PROCEDURE-CODE-MOD-5 must be 8-filled 2386 Relational edit between PROCEDURE-CODE-MOD-5 and PROCEDURE-CODE-5 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-5), then !fns.hasValue(@val.PROCEDURE-CODE-MOD-5)' PROCEDURE-CODE-5,PROCEDURE-CODE-MOD-5 CIP086,CIP087











175 No logic changes CIP088-0001 RULE-471 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP088 PROCEDURE-CODE-FLAG-5 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-FLAG PROCEDURE-CODE-FLAG-5 CIP088











176 Merged CIP089-0001 RULE-472 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP089 PROCEDURE-CODE-DATE-5 1 If PROCEDURE-CODE-DATE-2 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-5 CIP089











177 Merged CIP089-0002 RULE-472 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP089 PROCEDURE-CODE-DATE-5 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-5 CIP089











178 No logic changes CIP089-0003 RULE-474 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP089 PROCEDURE-CODE-DATE-5 2 If PROCEDURE-CODE-5 is 8-filled, then PROCEDURE-CODE-DATE-5 must be 8-filled 2380 Relational edit between PROCEDURE-CODE-DATE-5 and PROCEDURE-CODE-5 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-5), then !fns.hasValue(@val.PROCEDURE-CODE-DATE-5)' PROCEDURE-CODE-5,PROCEDURE-CODE-DATE-5 CIP086,CIP089











179 Logic updated: other CIP089-0004 RULE-475 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP089 PROCEDURE-CODE-DATE-5 2 If PROCEDURE-CODE-DATE-5 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-5 must be <= ENDING-DATE-OF-SERVICE 2103 Relational edit between PROCEDURE-CODE-DATE-5 and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-5) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@primaryRecord.PROCEDURE-CODE-DATE-5, @secondaryRecord.ENDING-DATE-OF-SERVICE)' PROCEDURE-CODE-DATE-5 CIP089 ENDING-DATE-OF-SERVICE CIP244

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



180 Logic updated: other CIP089-0005 RULE-476 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP089 PROCEDURE-CODE-DATE-5 2 If PROCEDURE-CODE-DATE-5 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-5 must be >= BEGINNING-DATE-OF-SERVICE 2102 Relational edit between PROCEDURE-CODE-DATE-5 and BEGINNING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-5) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.PROCEDURE-CODE-DATE-5)' PROCEDURE-CODE-DATE-5 CIP089 BEGINNING-DATE-OF-SERVICE CIP243

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



181 Logic updated: other CIP089-0006 RULE-477 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP089 PROCEDURE-CODE-DATE-5 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then PROCEDURE-CODE-DATE-5 must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3045 Relational edit between PROCEDURE-CODE-DATE-5 and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PROCEDURE-CODE-DATE-5), then fns.isLessThanOrEqual(@secondaryRecord.PROCEDURE-CODE-DATE-5, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PROCEDURE-CODE-DATE-5 CIP089

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



182 No logic changes CIP090-0001 RULE-478 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP090 PROCEDURE-CODE-6 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE PROCEDURE-CODE-6 CIP090











183 Merged CIP090-0008 RULE-428 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP090 PROCEDURE-CODE-6 2 If PROCEDURE-CODE-6 is not 8-filled, then PROCEDURE-CODE-6 must <> value for the other instances of PROCEDURE-CODE 2146 Duplicate values of PROCEDURE-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 PROCEDURE-CODE-1,PROCEDURE-CODE-2,PROCEDURE-CODE-3,PROCEDURE-CODE-4,PROCEDURE-CODE-5,PROCEDURE-CODE-6 CIP070,CIP074,CIP078,CIP082,CIP086,CIP090











184 Merged CIP090-0009 RULE-480 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP090 PROCEDURE-CODE-6 2 If PROCEDURE-CODE-FLAG-6 is 8-filled, then PROCEDURE-CODE-6 must be 8-filled 2375 Relational edit between PROCEDURE-CODE-6 and PROCEDURE-CODE-FLAG-6 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-6), then fns.hasValue(@val.PROCEDURE-CODE-6)' PROCEDURE-CODE-FLAG-6,PROCEDURE-CODE-6 CIP092,CIP090











185 Merged CIP090-0010 RULE-480 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP090 PROCEDURE-CODE-6 2 If PROCEDURE-CODE-FLAG-6 is not 8-filled, then PROCEDURE-CODE-6 must not be 8-filled 2375 Relational edit between PROCEDURE-CODE-6 and PROCEDURE-CODE-FLAG-6 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.PROCEDURE-CODE-FLAG-6), then fns.hasValue(@val.PROCEDURE-CODE-6)' PROCEDURE-CODE-FLAG-6,PROCEDURE-CODE-6 CIP092,CIP090











186 No logic changes CIP091-0001 RULE-482 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP091 PROCEDURE-CODE-MOD-6 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-6 CIP091











187 No logic changes CIP091-0002 RULE-483 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP091 PROCEDURE-CODE-MOD-6 2 If PROCEDURE-CODE-6 is 8-filled, then PROCEDURE-CODE-MOD-6 must be 8-filled 2387 Relational edit between PROCEDURE-CODE-MOD-6 and PROCEDURE-CODE-6 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-6), then !fns.hasValue(@val.PROCEDURE-CODE-MOD-6)' PROCEDURE-CODE-6,PROCEDURE-CODE-MOD-6 CIP090,CIP091











188 No logic changes CIP092-0001 RULE-484 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP092 PROCEDURE-CODE-FLAG-6 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-FLAG PROCEDURE-CODE-FLAG-6 CIP092











189 Merged CIP093-0001 RULE-485 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP093 PROCEDURE-CODE-DATE-6 1 If PROCEDURE-CODE-DATE-2 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-6 CIP093











190 Merged CIP093-0002 RULE-485 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP093 PROCEDURE-CODE-DATE-6 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE-6 CIP093











191 Logic updated: other CIP093-0004 RULE-487 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP093 PROCEDURE-CODE-DATE-6 2 If PROCEDURE-CODE-DATE-6 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-6 must be <= ENDING-DATE-OF-SERVICE 2105 Relational edit between PROCEDURE-CODE-DATE-6 and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-6) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@primaryRecord.PROCEDURE-CODE-DATE-6, @secondaryRecord.ENDING-DATE-OF-SERVICE)' PROCEDURE-CODE-DATE-6 CIP093 ENDING-DATE-OF-SERVICE CIP244

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



192 Logic updated: other CIP093-0005 RULE-488 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP093 PROCEDURE-CODE-DATE-6 2 If PROCEDURE-CODE-DATE-6 is not (8-filled or 9-filled), then PROCEDURE-CODE-DATE-6 must be >= BEGINNING-DATE-OF-SERVICE 2104 Relational edit between PROCEDURE-CODE-DATE-6 and BEGINNING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.PROCEDURE-CODE-DATE-6) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.PROCEDURE-CODE-DATE-6)' PROCEDURE-CODE-DATE-6 CIP093 BEGINNING-DATE-OF-SERVICE CIP243

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



193 Logic updated: other CIP093-0006 RULE-489 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP093 PROCEDURE-CODE-DATE-6 3 If DATE-OF-DEATH is not 8-filled, then PROCEDURE-CODE-DATE-6 must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3046 Relational edit between PROCEDURE-CODE-DATE-6 and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PROCEDURE-CODE-DATE-6), then fns.isLessThanOrEqual(@secondaryRecord.PROCEDURE-CODE-DATE-6, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PROCEDURE-CODE-DATE-6 CIP093

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



194 No logic changes CIP093-0007 RULE-490 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP093 PROCEDURE-CODE-DATE-6 2 If PROCEDURE-CODE-6 is 8-filled, then PROCEDURE-CODE-DATE-6 must be 8-filled 2547 Relational edit between PROCEDURE-CODE-DATE-6 and PROCEDURE-CODE-6 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.PROCEDURE-CODE-6), then !fns.hasValue(@val.PROCEDURE-CODE-DATE-6)' PROCEDURE-CODE-6,PROCEDURE-CODE-DATE-6 CIP090,CIP093











195 Merged CIP094-0001 RULE-491 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP094 ADMISSION-DATE 1 If ADMISSION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD ADMISSION-DATE CIP094











196 Merged CIP094-0002 RULE-491 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP094 ADMISSION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD ADMISSION-DATE CIP094











197 Merged CIP094-0003 RULE-493 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP094 ADMISSION-DATE 2-M
2002
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ADMISSION-DATE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.ADJUDICATION-DATE)' ADMISSION-DATE,ADJUDICATION-DATE CIP094,CIP098











198 Merged CIP094-0004 RULE-494 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP094 ADMISSION-DATE 2 If DISCHARGE-DATE is not (8-filled or 9-filled), then ADMISSION-DATE must be <= DISCHARGE-DATE 2006 Relational edit between ADMISSION-DATE and DISCHARGE-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.DISCHARGE-DATE) && fns.hasValue(@val.ADMISSION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.DISCHARGE-DATE)' DISCHARGE-DATE,ADMISSION-DATE CIP096,CIP094











199 Logic updated: other CIP094-0006 RULE-495 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP094 ADMISSION-DATE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then ADMISSION-DATE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3001 Relational edit between ADMISSION-DATE and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ADMISSION-DATE), then fns.isLessThanOrEqual(@secondaryRecord.ADMISSION-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ADMISSION-DATE CIP094

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



200 No logic changes CIP095-0001 RULE-496 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP095 ADMISSION-HOUR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: HOUR ADMISSION-HOUR CIP095











201 Merged CIP096-0001 RULE-497 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP096 DISCHARGE-DATE 1 If DISCHARGE-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD DISCHARGE-DATE CIP096











202 Merged CIP096-0002 RULE-497 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP096 DISCHARGE-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD DISCHARGE-DATE CIP096











203 Merged CIP096-0004 RULE-494 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP096 DISCHARGE-DATE 2-M
2006
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.DISCHARGE-DATE) && fns.hasValue(@val.ADMISSION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.DISCHARGE-DATE)' DISCHARGE-DATE,ADMISSION-DATE CIP096,CIP094











204 Logic updated: other CIP096-0005 RULE-500 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP096 DISCHARGE-DATE 2 If DISCHARGE-DATE is not (8-filled or 9-filled), then DISCHARGE-DATE must be <= ADJUDICATION-DATE [CLAIM-HEADER-RECORD-IP] 2024 Relational edit between DISCHARGE-DATE and ADJUDICATION-DATE [CLAIM-HEADER-RECORD-IP] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.DISCHARGE-DATE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.DISCHARGE-DATE, @val.ADJUDICATION-DATE)' DISCHARGE-DATE,ADJUDICATION-DATE CIP096,CIP098











205 No logic changes CIP096-0006 RULE-501 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP096 DISCHARGE-DATE 2 If DISCHARGE-HOUR is not 8-filled, then DISCHARGE-DATE must not be 8-filled 2274 Relational edit between DISCHARGE-DATE and DISCHARGE-HOUR 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.DISCHARGE-HOUR), then fns.hasValue(@val.DISCHARGE-DATE)' DISCHARGE-HOUR,DISCHARGE-DATE CIP097,CIP096











206 Logic updated: other CIP096-0008 RULE-502 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP096 DISCHARGE-DATE 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then DISCHARGE-DATE must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3053 Relational edit with DISCHARGE-DATE and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.DISCHARGE-DATE), then fns.isLessThanOrEqual(@secondaryRecord.DISCHARGE-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 DISCHARGE-DATE CIP096

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



207 No logic changes CIP097-0001 RULE-503 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP097 DISCHARGE-HOUR 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: HOUR DISCHARGE-HOUR CIP097











208 Merged CIP098-0001 RULE-504 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP098 ADJUDICATION-DATE 1 If ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CIP098











209 Merged CIP098-0002 RULE-504 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP098 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CIP098











210 Logic updated: other CIP098-0006 RULE-506 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP098 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 FILE-HEADER-RECORD-IP CIP00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE CIP098 END-OF-TIME-PERIOD CIP010









211 Merged CIP098-0007 RULE-493 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP098 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be >= ADMISSION-DATE 2002 Relational edit between ADJUDICATION-DATE and ADMISSION-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ADMISSION-DATE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.ADJUDICATION-DATE)' ADMISSION-DATE,ADJUDICATION-DATE CIP094,CIP098











212 Merged CIP099-0001 RULE-508 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP099 MEDICAID-PAID-DATE 1 If MEDICAID-PAID-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE CIP099











213 Merged CIP099-0002 RULE-508 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP099 MEDICAID-PAID-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE CIP099











214 No logic changes CIP100-0001 RULE-510 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP100 TYPE-OF-CLAIM 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-CLAIM TYPE-OF-CLAIM CIP100











215 No logic changes CIP101-0001 RULE-511 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP101 TYPE-OF-BILL 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.TYPE-OF-BILL), then fns.isValidTypeOfBill(@val.TYPE-OF-BILL)' TYPE-OF-BILL CIP101











216 No logic changes CIP102-0001 RULE-512 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP102 CLAIM-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-STATUS CIP102











217 No logic changes CIP103-0001 RULE-513 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP103 CLAIM-STATUS-CATEGORY 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS-CATEGORY CLAIM-STATUS-CATEGORY CIP103











218 No logic changes CIP104-0001 RULE-514 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP104 SOURCE-LOCATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: SOURCE-LOCATION SOURCE-LOCATION CIP104











219 Logic updated: string matching CIP105-0001 RULE-515 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP105 CHECK-NUM 1 If CHECK-NUM is populated, it must contains valid characters. 120 Field contains invalid characters - CHECK-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.CHECK-NUM), then fns.matches(@val.CHECK-NUM, "^[^|*]*$")' CHECK-NUM CIP105











220 Merged CIP106-0001 RULE-516 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP106 CHECK-EFF-DATE 1 If CHECK-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE CIP106











221 Merged CIP106-0002 RULE-516 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP106 CHECK-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE CIP106











222 No logic changes CIP107-0001 RULE-518 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP107 ALLOWED-CHARGE-SRC 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: ALLOWED-CHARGE-SRC ALLOWED-CHARGE-SRC CIP107











223 Logic updated: other CIP107-0002 RULE-519 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP107 ALLOWED-CHARGE-SRC 3 If DUAL-ELIGIBLE-CODE [ELIGIBLE]= "00" and (BEGINNING-DATE-OF-SERVICE >= ELIGIBILITY-DETERMINANT-EFF-DATE) and (BEGINNING-DATE-OF-SERVICE <= ELIGIBILITY-DETERMINANT-END-DATE), then ALLOWED-CHARGE-SRC must <> "1", "I", "K", or "M", where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] 3032 Relational edit between ALLOWED-CHARGE-SRC [CLAIMIP] and DUAL-ELIGIBLE-CODE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003 ELIGIBILITY-DETERMINANTS ELG00005 'if fns.isEqual(@tertiaryRecord.DUAL-ELIGIBLE-CODE, "00") && fns.isLessThanOrEqual(@tertiaryRecord.ELIGIBILITY-DETERMINANT-EFF-DATE, @secondaryRecord.BEGINNING-DATE-OF-SERVICE) && fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @tertiaryRecord.ELIGIBILITY-DETERMINANT-END-DATE), then !fns.isEqualToAny(@primaryRecord.ALLOWED-CHARGE-SRC, "1", "I", "K", "M")' ALLOWED-CHARGE-SRC CIP107 BEGINNING-DATE-OF-SERVICE CIP243 DUAL-ELIGIBLE-CODE,ELIGIBILITY-DETERMINANT-EFF-DATE,ELIGIBILITY-DETERMINANT-END-DATE ELG085,ELG099,ELG100 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP017,CIP020,CIP019,CIP098 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP232,CIP236,CIP235,CIP286 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082
224 No logic changes CIP108-0001 RULE-7086 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP108 CLAIM-PYMT-REM-CODE-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-1 CIP108











225 Merged CIP108-0002 RULE-521 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP108 CLAIM-PYMT-REM-CODE-1 2 If CLAIM-PYMT-REM-CODE-1 is not 8-filled, then CLAIM-PYMT-REM-CODE-1 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CIP108,CIP109,CIP110,CIP111











226 No logic changes CIP109-0001 RULE-522 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP109 CLAIM-PYMT-REM-CODE-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-2 CIP109











227 Merged CIP109-0002 RULE-521 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP109 CLAIM-PYMT-REM-CODE-2 2 If CLAIM-PYMT-REM-CODE-2 is not 8-filled, then CLAIM-PYMT-REM-CODE-2 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CIP108,CIP109,CIP110,CIP111











228 No logic changes CIP109-0003 RULE-524 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP109 CLAIM-PYMT-REM-CODE-2 2 CLAIM-PYMT-REM-CODE-2 must be 8-filled if value for CLAIM-PYMT-REM-CODE-1 is 8-filled 2243 Relational edit between CLAIM-PYMT-REM-CODE-2 and CLAIM-PYMT-REM-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-1), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2)' CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2 CIP108,CIP109











229 No logic changes CIP110-0001 RULE-525 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP110 CLAIM-PYMT-REM-CODE-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-3 CIP110











230 Merged CIP110-0002 RULE-521 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP110 CLAIM-PYMT-REM-CODE-3 2 If CLAIM-PYMT-REM-CODE-3 is not 8-filled, then CLAIM-PYMT-REM-CODE-3 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CIP108,CIP109,CIP110,CIP111











231 No logic changes CIP110-0003 RULE-527 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP110 CLAIM-PYMT-REM-CODE-3 2 CLAIM-PYMT-REM-CODE-3 must be 8-filled if value for CLAIM-PYMT-REM-CODE-2 is 8-filled 2244 Relational edit between CLAIM-PYMT-REM-CODE-3 and CLAIM-PYMT-REM-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3)' CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3 CIP109,CIP110











232 No logic changes CIP111-0001 RULE-528 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP111 CLAIM-PYMT-REM-CODE-4 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-4 CIP111











233 Merged CIP111-0002 RULE-521 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP111 CLAIM-PYMT-REM-CODE-4 2 If CLAIM-PYMT-REM-CODE-4 is not 8-filled, then CLAIM-PYMT-REM-CODE-4 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CIP108,CIP109,CIP110,CIP111











234 No logic changes CIP111-0003 RULE-530 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP111 CLAIM-PYMT-REM-CODE-4 2 CLAIM-PYMT-REM-CODE-4 must be 8-filled if value for CLAIM-PYMT-REM-CODE-3 is 8-filled 2245 Relational edit between CLAIM-PYMT-REM-CODE-4 and CLAIM-PYMT-REM-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-4)' CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CIP110,CIP111











235 No logic changes CIP112-0001 RULE-531 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP112 TOT-BILLED-AMT 1 If TOT-BILLED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-BILLED-AMT CIP112











236 No logic changes CIP112-0003 RULE-532 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP112 TOT-BILLED-AMT 2 If TYPE-OF-CLAIM = "4", "D", or "X", then TOT-BILLED-AMT must = 0 2426 Relational edit between TOT-BILLED-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "4", "D", "X"), then fns.isEqual(@val.TOT-BILLED-AMT, "0.00")' TYPE-OF-CLAIM,TOT-BILLED-AMT CIP100,CIP112











237 No logic changes CIP113-0001 RULE-533 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP113 TOT-ALLOWED-AMT 1 If TOT-ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-ALLOWED-AMT CIP113











238 Merged CIP113-0002 RULE-534 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP113 TOT-ALLOWED-AMT 2 TOT-ALLOWED-AMT must = the sum of the ALLOWED-AMT at each claim line level 2424 Relational edit between TOT-ALLOWED-AMT and detail ALLOWED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'fns.isDollarSumEqual(@primaryRecord.TOT-ALLOWED-AMT, @secondaryRecords.ALLOWED-AMT)' TOT-ALLOWED-AMT CIP113 ALLOWED-AMT CIP252

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



239 Merged CIP113-0003 RULE-534 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP113 TOT-ALLOWED-AMT 2 TOT-ALLOWED-AMT must = the sum of ALLOWED-AMT at each claim line level, where SUBMITTING-STATE, ICN-ORIG, and ICN-ADJ match 2125 Relational edit between TOT-ALLOWED-AMT and ALLOWED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'fns.isDollarSumEqual(@primaryRecord.TOT-ALLOWED-AMT, @secondaryRecords.ALLOWED-AMT)' TOT-ALLOWED-AMT CIP113 ALLOWED-AMT CIP252

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



240 No logic changes CIP114-0001 RULE-536 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP114 TOT-MEDICAID-PAID-AMT 1 If TOT-MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICAID-PAID-AMT CIP114











241 No logic changes CIP115-0001 RULE-537 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP115 TOT-COPAY-AMT 1 If TOT-COPAY-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-COPAY-AMT CIP115











242 No logic changes CIP116-0001 RULE-538 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP116 TOT-MEDICARE-DEDUCTIBLE-AMT 1 If TOT-MEDICARE-DEDUCTIBLE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-DEDUCTIBLE-AMT CIP116











243 Logic updated: other CIP116-0003 RULE-539 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP116 TOT-MEDICARE-DEDUCTIBLE-AMT 2 TOT-MEDICARE-DEDUCIBLE-AMT must be <=TOT-BILLED-AMT 2127 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT) && fns.hasValue(@val.TOT-BILLED-AMT), then fns.isLessThanOrEqual(@val.TOT-MEDICARE-DEDUCTIBLE-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-BILLED-AMT CIP116,CIP112











244 Merged CIP116-0004 RULE-544 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP116 TOT-MEDICARE-DEDUCTIBLE-AMT 2 If TOT-MEDICARE-COINS-AMT is 8-filled, then TOT-MEDICARE-DEDUCIBLE-AMT must be 8-filled 2431 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and TOT-MEDICARE-COINS-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-MEDICARE-COINS-AMT CIP116,CIP117











245 No logic changes CIP117-0001 RULE-541 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP117 TOT-MEDICARE-COINS-AMT 1 If TOT-MEDICARE-COINS-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-COINS-AMT CIP117











246 No logic changes CIP117-0002 RULE-542 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP117 TOT-MEDICARE-COINS-AMT 2 If TYPE-OF-CLAIM = "3", "C", "W", then TOT-MEDICARE-COINS-AMT must be 8-filled 2429 Relational edit between TOT-MEDICARE-COINS-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then !fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TYPE-OF-CLAIM,TOT-MEDICARE-COINS-AMT CIP100,CIP117











247 No logic changes CIP117-0003 RULE-543 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP117 TOT-MEDICARE-COINS-AMT 2 TOT-MEDICARE-COINS-AMT must be < TOT-BILLED-AMT 2126 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'fns.isLessThan(@val.TOT-MEDICARE-COINS-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-COINS-AMT,TOT-BILLED-AMT CIP117,CIP112











248 Merged CIP117-0004 RULE-544 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP117 TOT-MEDICARE-COINS-AMT 2 If TOT-MEDICARE-DEDUCTIBLE-AMT is 8-filled, then TOT-MEDICARE-COINS-AMT must be 8-filled. 2428 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-MEDICARE-DEDUCTIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-MEDICARE-COINS-AMT CIP116,CIP117











249 No logic changes CIP117-0005 RULE-545 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP117 TOT-MEDICARE-COINS-AMT 2 If MEDICARE-COMB-DED-IND = "1", then TOT-MEDICARE-COINS-AMT must = 0 2427 Relational edit between TOT-MEDICARE-COINS-AMT and MEDICARE-COMB-DED-IND 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqual(@val.MEDICARE-COMB-DED-IND, "1"), then fns.isEqual(@val.TOT-MEDICARE-COINS-AMT, "0.00")' MEDICARE-COMB-DED-IND,TOT-MEDICARE-COINS-AMT CIP128,CIP117











250 No logic changes CIP118-0001 RULE-546 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP118 TOT-TPL-AMT 1 If TOT-TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-TPL-AMT CIP118











251 Logic updated: other CIP118-0002 RULE-547 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP118 TOT-TPL-AMT 2 The absolute value of TOT-TPL-AMT must be <= the absolute value of (TOT-BILLED-AMT minus TOT-MEDICARE-COINS-AMT plus TOT-MEDICARE-DEDUCIBLE-AMT) 2432 Relational edit between TOT-TPL-AMT, TOT-BILLED-AMT, MEDICARE-COINS-AMT, and TOT-MEDICARE-DEDUCIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.TOT-TPL-AMT) && fns.hasValue(@val.TOT-BILLED-AMT) && fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.isLessThanOrEqual(@val.TOT-TPL-AMT, fns.remainingLiability(@val.TOT-BILLED-AMT, @val.TOT-MEDICARE-COINS-AMT, @val.TOT-MEDICARE-DEDUCTIBLE-AMT))' TOT-TPL-AMT,TOT-BILLED-AMT,TOT-MEDICARE-COINS-AMT,TOT-MEDICARE-DEDUCTIBLE-AMT CIP118,CIP112,CIP117,CIP116











252 No logic changes CIP119-0001 RULE-548 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP119 TOT-OTHER-INSURANCE-AMT 1 If OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-OTHER-INSURANCE-AMT CIP119











253 No logic changes CIP121-0001 RULE-549 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP121 OTHER-INSURANCE-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-INSURANCE-IND OTHER-INSURANCE-IND CIP121











254 No logic changes CIP122-0001 RULE-550 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP122 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION CIP122











255 No logic changes CIP123-0001 RULE-551 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP123 SERVICE-TRACKING-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: SERVICE-TRACKING-TYPE SERVICE-TRACKING-TYPE CIP123











256 No logic changes CIP124-0001 RULE-552 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP124 SERVICE-TRACKING-PAYMENT-AMT 1 If SERVICE-TRACKING-PAYMENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 SERVICE-TRACKING-PAYMENT-AMT CIP124











257 No logic changes CIP124-0004 RULE-553 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP124 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE <> "00" AND (TOT-MEDICAID-PAID-AMT = 0), then SERVICE-TRACKING-PAYMENT-AMT must be > 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isEqual(@val.TOT-MEDICAID-PAID-AMT, "0.00"), then fns.isGreaterThanZero(@val.SERVICE-TRACKING-PAYMENT-AMT)' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT CIP123,CIP114,CIP124











258 No logic changes CIP124-0006 RULE-554 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP124 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE = "00" AND (TOT-MEDICAID-PAID-AMT > 0), then SERVICE-TRACKING-PAYMENT-AMT must = 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isGreaterThanZero(@val.TOT-MEDICAID-PAID-AMT), then fns.isEqual(@val.SERVICE-TRACKING-PAYMENT-AMT, "0.00")' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT CIP123,CIP114,CIP124











259 No logic changes CIP125-0001 RULE-555 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP125 FIXED-PAYMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: FIXED-PAYMENT-IND FIXED-PAYMENT-IND CIP125











260 No logic changes CIP126-0001 RULE-556 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP126 FUNDING-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-CODE FUNDING-CODE CIP126











261 No logic changes CIP127-0001 RULE-557 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP127 FUNDING-SOURCE-NONFEDERAL-SHARE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-SOURCE-NONFEDERAL-SHARE FUNDING-SOURCE-NONFEDERAL-SHARE CIP127











262 No logic changes CIP128-0001 RULE-558 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP128 MEDICARE-COMB-DED-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-COMB-DED-IND MEDICARE-COMB-DED-IND CIP128











263 No logic changes CIP128-0004 RULE-559 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP128 MEDICARE-COMB-DED-IND 2 If CROSSOVER-INDICATOR = "0" or TYPE-OF-CLAIM = "3", "C", or "W", then MEDICARE-COMB-DED-IND must = 0 2328 Relational edit between MEDICARE-COMB-DED-IND, CROSSOVER-INDICATOR, and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "0") || fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then fns.isEqual(@val.MEDICARE-COMB-DED-IND, "0")' CROSSOVER-INDICATOR,TYPE-OF-CLAIM,MEDICARE-COMB-DED-IND CIP023,CIP100,CIP128











264 No logic changes CIP129-0001 RULE-560 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP129 PROGRAM-TYPE 1 Valueis not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROGRAM-TYPE PROGRAM-TYPE CIP129











265 No logic changes CIP129-0002 RULE-561 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP129 PROGRAM-TYPE 2 If PROGRAM-TYPE = "07", then WAIVER-TYPE must = "06" through "20" 2388 Relational edit between PROGRAM-TYPE and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqual(@val.PROGRAM-TYPE, "07"), then fns.isEqualToAny(@val.WAIVER-TYPE, "06", "07", "08", "09", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20")' PROGRAM-TYPE,WAIVER-TYPE CIP129,CIP177











266 No logic changes CIP129-0004 RULE-562 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP129 PROGRAM-TYPE 3 If PROGRAM-TYPE = "13", then STATE-PLAN-OPTION-TYPE [ELIGIBLE] must = "02" where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] 3047 Relational edit between PROGRAM TYPE and STATE-PLAN-OPTION-TYPE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) STATE-PLAN-OPTION-PARTICIPATION ELG00011 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.isEqual(@secondaryRecord.PROGRAM-TYPE, "13"), then fns.isEqual(@primaryRecord.STATE-PLAN-OPTION-TYPE, "02")' STATE-PLAN-OPTION-TYPE ELG163 PROGRAM-TYPE CIP129

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG162,ELG160 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CIP022,CIP017



267 Logic updated: string matching CIP130-0001 RULE-563 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP130 PLAN-ID-NUMBER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PLAN-ID-NUMBER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.PLAN-ID-NUMBER), then fns.matches(@val.PLAN-ID-NUMBER, "^[^|*]*$")' PLAN-ID-NUMBER CIP130











268 No logic changes CIP130-0003 RULE-564 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP130 PLAN-ID-NUMBER 2 If TYPE-OF-SERVICE = "119", "120", OR "122", then PLAN-ID-NUM must = BILLING-PROV-NUM 2364 Relational edit between PLAN-ID-NUM, BILLING-PROV-NUM, and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "122"), then fns.isEqual(@primaryRecord.PLAN-ID-NUMBER, @primaryRecord.BILLING-PROV-NUM)' PLAN-ID-NUMBER,BILLING-PROV-NUM CIP130,CIP179 TYPE-OF-SERVICE CIP257

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



269 No logic changes CIP130-0005 RULE-565 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP130 PLAN-ID-NUMBER 2 If TYPE-OF-CLAIM <> 3, C or W, then PLAN-ID-NUMBER must be 8-filled 2363 Relational edit between PLAN-ID-NUM and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if !fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then !fns.hasValue(@val.PLAN-ID-NUMBER)' TYPE-OF-CLAIM,PLAN-ID-NUMBER CIP100,CIP130











270 Logic updated: string matching CIP131-0001 RULE-566 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP131 NATIONAL-HEALTH-CARE-ENTITY-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-ID, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-ID CIP131











271 No logic changes CIP131-0003 RULE-567 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP131 NATIONAL-HEALTH-CARE-ENTITY-ID 2 If START-OF-TIME-PERIOD >= 20151105, then NATIONAL-HEALTH-CARE-ENTITY-ID must not be (8-filled or 9-filled) 2332 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 FILE-HEADER-RECORD-IP CIP00001

if fns.isGreaterThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, "2015-11-10"), then fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID CIP131 START-OF-TIME-PERIOD CIP009









272 No logic changes CIP131-0004 RULE-568 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP131 NATIONAL-HEALTH-CARE-ENTITY-ID 3 If TYPE-OF-CLAIM = "C", "3", or "W", then NATIONAL-HEALTH-CARE-ENTITY-ID [CLAIM-HEADER-RECORD-IP-CIP00002] must = NATIONAL-HEALTH-CARE-ENTITY-ID [MANAGED-CARE-PARTICIPATION-ELG00014], where SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] and MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014]. 3027 Edit that NATIONAL-HEALTH-CARE-ENTITY-ID matches value in MANAGED-CARE-PARTICIPATION-ELG00014 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) MANAGED-CARE-PARTICIPATION ELG00014 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.isEqual(@secondaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID, @primaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID ELG194 TYPE-OF-CLAIM,NATIONAL-HEALTH-CARE-ENTITY-ID CIP100,CIP131

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG189,ELG191 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



273 No logic changes CIP132-0001 RULE-569 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP132 PAYMENT-LEVEL-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PAYMENT-LEVEL-IND PAYMENT-LEVEL-IND CIP132











274 No logic changes CIP133-0001 RULE-570 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP133 MEDICARE-REIM-TYPE 1 Value must be a valid value 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-REIM-TYPE MEDICARE-REIM-TYPE CIP133











275 No logic changes CIP134-0001 RULE-571 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP134 NON-COV-DAYS 1 If NON-COV-DAYS is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: S9(5) NON-COV-DAYS CIP134











276 No logic changes CIP134-0002 RULE-572 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP134 NON-COV-DAYS 2 Sum (NON-COVERED-DAYS plus MEDICAID-COV-INPATIENT-DAYS plus 1) must be <= (BEGINNING-DATE-OF-SERVICE minus ENDING-DATE-OF-SERVICE (in days)) 2335 Relational edit between NON-COV-DAYS, MEDICAID-COV-INPATIENT-DAYS, and ADMISSION-DATE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'fns.isSumOfDaysLessThanOrEqualToTotalLengthOfStay(@primaryRecord.NON-COV-DAYS, @primaryRecord.MEDICAID-COV-INPATIENT-DAYS, @secondaryRecords.BEGINNING-DATE-OF-SERVICE, @secondaryRecords.ENDING-DATE-OF-SERVICE)' NON-COV-DAYS,MEDICAID-COV-INPATIENT-DAYS CIP134,CIP136 BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CIP243,CIP244

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



277 No logic changes CIP135-0001 RULE-573 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP135 NON-COV-CHARGES 1 If NON-COV-CHARGES is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 NON-COV-CHARGES CIP135











278 No logic changes CIP136-0001 RULE-574 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP136 MEDICAID-COV-INPATIENT-DAYS 1 If MEDICAID-COV-INPATIENT-DAYS is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: S9(7) MEDICAID-COV-INPATIENT-DAYS CIP136











279 Logic updated: other CIP136-0003 RULE-575 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP136 MEDICAID-COV-INPATIENT-DAYS 2 MEDICAID-COV-INPATIENT-DAYS must not be > [(DISCHARGE-DATE minus ADMISSION-DATE plus 1 (in days)) times 2]. 2327 Relational edit between MEDICAID-COV-INPATIENT-DAYS, DISCHARGE-DATE, and ADMISSION-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.MEDICAID-COV-INPATIENT-DAYS) && fns.hasValue(@val.ADMISSION-DATE) && fns.hasValue(@val.DISCHARGE-DATE), then fns.isValueLessThanOrEqualToTwoTimesStayDuration(@val.MEDICAID-COV-INPATIENT-DAYS, @val.ADMISSION-DATE, @val.DISCHARGE-DATE)' MEDICAID-COV-INPATIENT-DAYS,ADMISSION-DATE,DISCHARGE-DATE CIP136,CIP094,CIP096











280 Retired: required value checks CIP137-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP137 CLAIM-LINE-COUNT 1 If CLAIM-LINE-COUNT =0 113 Required data element has not been reported.

























281 Logic updated: other CIP137-0003 RULE-577 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP137 CLAIM-LINE-COUNT 2 CLAIM-LINE-COUNT must = total number of lines in the claim 2445 Value does not equal the total number of lines in the claim 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.CLAIM-LINE-COUNT), then fns.isValueEqualToNumberOfRecords(@primaryRecord.CLAIM-LINE-COUNT, @secondaryRecords.LINE-NUM-ORIG)' CLAIM-LINE-COUNT CIP137 LINE-NUM-ORIG CIP237

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



282 No logic changes CIP138-0001 RULE-578 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP138 FORCED-CLAIM-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: FORCED-CLAIM-IND FORCED-CLAIM-IND CIP138











283 No logic changes CIP139-0001 RULE-579 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP139 HEALTH-CARE-ACQUIRED-CONDITION-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-CARE-ACQUIRED-CONDITION-IND HEALTH-CARE-ACQUIRED-CONDITION-IND CIP139











284 No logic changes CIP140-0001 RULE-580 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP140 OCCURRENCE-CODE-01 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-01 CIP140











285 No logic changes CIP141-0001 RULE-581 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP141 OCCURRENCE-CODE-02 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-02 CIP141











286 No logic changes CIP142-0001 RULE-582 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP142 OCCURRENCE-CODE-03 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-03 CIP142











287 No logic changes CIP143-0001 RULE-583 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP143 OCCURRENCE-CODE-04 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-04 CIP143











288 No logic changes CIP144-0001 RULE-584 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP144 OCCURRENCE-CODE-05 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-05 CIP144











289 No logic changes CIP145-0001 RULE-585 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP145 OCCURRENCE-CODE-06 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-06 CIP145











290 No logic changes CIP146-0001 RULE-586 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP146 OCCURRENCE-CODE-07 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-07 CIP146











291 No logic changes CIP147-0001 RULE-587 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP147 OCCURRENCE-CODE-08 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-08 CIP147











292 No logic changes CIP148-0001 RULE-588 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP148 OCCURRENCE-CODE-09 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-09 CIP148











293 No logic changes CIP149-0001 RULE-589 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP149 OCCURRENCE-CODE-10 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-10 CIP149











294 Merged CIP150-0001 RULE-590 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP150 OCCURRENCE-CODE-EFF-DATE-01 1 If OCCURRENCE-CODE-EFF-DATE-01 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-01 CIP150











295 Merged CIP150-0002 RULE-590 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP150 OCCURRENCE-CODE-EFF-DATE-01 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-01 CIP150











296 No logic changes CIP150-0003 RULE-592 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP150 OCCURRENCE-CODE-EFF-DATE-01 2 If OCCURRENCE-CODE-01 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-01 must not be 8-filled 2337 Relational edit between OCCURRENCE-CODE-01 and OCCURRENCE-CODE-EFF-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-01), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01)' OCCURRENCE-CODE-01,OCCURRENCE-CODE-EFF-DATE-01 CIP140,CIP150











297 Merged CIP150-0005 RULE-593 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP150 OCCURRENCE-CODE-EFF-DATE-01 2 OCCURRENCE-CODE-EFF-DATE-01 must be <= OCCURRENCE-CODE-END-DATE-01 2069 Relational edit between OCCURRENCE-CODE-EFF-DATE-01 and OCCURRENCE-CODE-END-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-01, @val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-EFF-DATE-01,OCCURRENCE-CODE-END-DATE-01 CIP150,CIP160











298 Merged CIP151-0001 RULE-594 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP151 OCCURRENCE-CODE-EFF-DATE-02 1 If OCCURRENCE-CODE-EFF-DATE-02 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-02 CIP151











299 Merged CIP151-0002 RULE-594 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP151 OCCURRENCE-CODE-EFF-DATE-02 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-02 CIP151











300 No logic changes CIP151-0003 RULE-596 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP151 OCCURRENCE-CODE-EFF-DATE-02 2 If OCCURRENCE-CODE-02 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-02 must not be 8-filled 2339 Relational edit between OCCURRENCE-CODE-02 and OCCURRENCE-CODE-EFF-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-02), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-02)' OCCURRENCE-CODE-02,OCCURRENCE-CODE-EFF-DATE-02 CIP141,CIP151











301 Merged CIP151-0005 RULE-597 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP151 OCCURRENCE-CODE-EFF-DATE-02 2 OCCURRENCE-CODE-EFF-DATE-02 must be <= OCCURRENCE-CODE-END-DATE-02 2070 Relational edit between OCCURRENCE-CODE-EFF-DATE-02 and OCCURRENCE-CODE-END-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-02, @val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-EFF-DATE-02,OCCURRENCE-CODE-END-DATE-02 CIP151,CIP161











302 Merged CIP152-0001 RULE-598 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP152 OCCURRENCE-CODE-EFF-DATE-03 1 If OCCURRENCE-CODE-EFF-DATE-03 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-03 CIP152











303 Merged CIP152-0002 RULE-598 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP152 OCCURRENCE-CODE-EFF-DATE-03 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-03 CIP152











304 No logic changes CIP152-0003 RULE-600 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP152 OCCURRENCE-CODE-EFF-DATE-03 2 If OCCURRENCE-CODE-03 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-03 must not be 8-filled 2341 Relational edit between OCCURRENCE-CODE-03 and OCCURRENCE-CODE-EFF-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-03), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03)' OCCURRENCE-CODE-03,OCCURRENCE-CODE-EFF-DATE-03 CIP142,CIP152











305 Merged CIP152-0005 RULE-601 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP152 OCCURRENCE-CODE-EFF-DATE-03 2 OCCURRENCE-CODE-EFF-DATE-03 must be <= OCCURRENCE-CODE-END-DATE-03 2071 Relational edit between OCCURRENCE-CODE-EFF-DATE-03 and OCCURRENCE-CODE-END-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-03, @val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-EFF-DATE-03,OCCURRENCE-CODE-END-DATE-03 CIP152,CIP162











306 Merged CIP153-0001 RULE-602 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP153 OCCURRENCE-CODE-EFF-DATE-04 1 If OCCURRENCE-CODE-EFF-DATE-04 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-04 CIP153











307 Merged CIP153-0002 RULE-602 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP153 OCCURRENCE-CODE-EFF-DATE-04 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-04 CIP153











308 No logic changes CIP153-0003 RULE-604 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP153 OCCURRENCE-CODE-EFF-DATE-04 2 If OCCURRENCE-CODE-04 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-04 must not be 8-filled 2343 Relational edit between OCCURRENCE-CODE-04 and OCCURRENCE-CODE-EFF-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-04), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04)' OCCURRENCE-CODE-04,OCCURRENCE-CODE-EFF-DATE-04 CIP143,CIP153











309 Merged CIP153-0006 RULE-605 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP153 OCCURRENCE-CODE-EFF-DATE-04 2 OCCURRENCE-CODE-EFF-DATE-04 must be <= OCCURRENCE-CODE-END-DATE-04 2072 Relational edit between OCCURRENCE-CODE-EFF-DATE-04 and OCCURRENCE-CODE-END-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-04, @val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-EFF-DATE-04,OCCURRENCE-CODE-END-DATE-04 CIP153,CIP163











310 Merged CIP154-0001 RULE-606 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP154 OCCURRENCE-CODE-EFF-DATE-05 1 If OCCURRENCE-CODE-EFF-DATE-05 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-05 CIP154











311 Merged CIP154-0002 RULE-606 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP154 OCCURRENCE-CODE-EFF-DATE-05 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-05 CIP154











312 No logic changes CIP154-0003 RULE-608 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP154 OCCURRENCE-CODE-EFF-DATE-05 2 If OCCURRENCE-CODE-05 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-05 must not be 8-filled 2345 Relational edit between OCCURRENCE-CODE-05 and OCCURRENCE-CODE-EFF-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-05), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05)' OCCURRENCE-CODE-05,OCCURRENCE-CODE-EFF-DATE-05 CIP144,CIP154











313 Merged CIP154-0005 RULE-609 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP154 OCCURRENCE-CODE-EFF-DATE-05 2 OCCURRENCE-CODE-EFF-DATE-05 must be <= OCCURRENCE-CODE-END-DATE-05 2073 Relational edit between OCCURRENCE-CODE-EFF-DATE-05 and OCCURRENCE-CODE-END-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-05, @val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-EFF-DATE-05,OCCURRENCE-CODE-END-DATE-05 CIP154,CIP164











314 Merged CIP155-0001 RULE-610 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP155 OCCURRENCE-CODE-EFF-DATE-06 1 If OCCURRENCE-CODE-EFF-DATE-06 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-06 CIP155











315 Merged CIP155-0002 RULE-610 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP155 OCCURRENCE-CODE-EFF-DATE-06 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-06 CIP155











316 No logic changes CIP155-0003 RULE-612 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP155 OCCURRENCE-CODE-EFF-DATE-06 2 If OCCURRENCE-CODE-06 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-06 must not be 8-filled 2347 Relational edit between OCCURRENCE-CODE-06 and OCCURRENCE-CODE-EFF-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-06), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06)' OCCURRENCE-CODE-06,OCCURRENCE-CODE-EFF-DATE-06 CIP145,CIP155











317 Merged CIP155-0005 RULE-613 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP155 OCCURRENCE-CODE-EFF-DATE-06 2 OCCURRENCE-CODE-EFF-DATE-06 must be <= OCCURRENCE-CODE-END-DATE-06 2074 Relational edit between OCCURRENCE-CODE-EFF-DATE-06 and OCCURRENCE-CODE-END-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-06, @val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-EFF-DATE-06,OCCURRENCE-CODE-END-DATE-06 CIP155,CIP165











318 Merged CIP156-0001 RULE-614 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP156 OCCURRENCE-CODE-EFF-DATE-07 1 If OCCURRENCE-CODE-EFF-DATE-07 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-07 CIP156











319 Merged CIP156-0002 RULE-614 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP156 OCCURRENCE-CODE-EFF-DATE-07 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-07 CIP156











320 No logic changes CIP156-0003 RULE-616 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP156 OCCURRENCE-CODE-EFF-DATE-07 2 If OCCURRENCE-CODE-07 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-07 must not be 8-filled 2349 Relational edit between OCCURRENCE-CODE-07 and OCCURRENCE-CODE-EFF-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-07), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07)' OCCURRENCE-CODE-07,OCCURRENCE-CODE-EFF-DATE-07 CIP146,CIP156











321 Merged CIP156-0005 RULE-617 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP156 OCCURRENCE-CODE-EFF-DATE-07 2 OCCURRENCE-CODE-EFF-DATE-07 must be <= OCCURRENCE-CODE-END-DATE-07 2075 Relational edit between OCCURRENCE-CODE-EFF-DATE-07 and OCCURRENCE-CODE-END-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-07, @val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-EFF-DATE-07,OCCURRENCE-CODE-END-DATE-07 CIP156,CIP166











322 Merged CIP157-0001 RULE-618 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP157 OCCURRENCE-CODE-EFF-DATE-08 1 If OCCURRENCE-CODE-EFF-DATE-08 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-08 CIP157











323 Merged CIP157-0002 RULE-618 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP157 OCCURRENCE-CODE-EFF-DATE-08 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-08 CIP157











324 No logic changes CIP157-0003 RULE-620 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP157 OCCURRENCE-CODE-EFF-DATE-08 2 If OCCURRENCE-CODE-08 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-08 must not be 8-filled 2351 Relational edit between OCCURRENCE-CODE-08 and OCCURRENCE-CODE-EFF-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-08), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08)' OCCURRENCE-CODE-08,OCCURRENCE-CODE-EFF-DATE-08 CIP147,CIP157











325 Merged CIP157-0005 RULE-621 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP157 OCCURRENCE-CODE-EFF-DATE-08 2 OCCURRENCE-CODE-EFF-DATE-08 must be <= OCCURRENCE-CODE-END-DATE-08 2076 Relational edit between OCCURRENCE-CODE-EFF-DATE-08 and OCCURRENCE-CODE-END-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-08, @val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-EFF-DATE-08,OCCURRENCE-CODE-END-DATE-08 CIP157,CIP167











326 Merged CIP158-0001 RULE-622 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP158 OCCURRENCE-CODE-EFF-DATE-09 1 If OCCURRENCE-CODE-EFF-DATE-09 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-09 CIP158











327 Merged CIP158-0002 RULE-622 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP158 OCCURRENCE-CODE-EFF-DATE-09 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-09 CIP158











328 No logic changes CIP158-0003 RULE-624 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP158 OCCURRENCE-CODE-EFF-DATE-09 2 If OCCURRENCE-CODE-09 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-09 must not be 8-filled 2353 Relational edit between OCCURRENCE-CODE-09 and OCCURRENCE-CODE-EFF-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-09), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09)' OCCURRENCE-CODE-09,OCCURRENCE-CODE-EFF-DATE-09 CIP148,CIP158











329 Merged CIP158-0005 RULE-625 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP158 OCCURRENCE-CODE-EFF-DATE-09 2 OCCURRENCE-CODE-EFF-DATE-09 must be <= OCCURRENCE-CODE-END-DATE-09 2077 Relational edit between OCCURRENCE-CODE-EFF-DATE-09 and OCCURRENCE-CODE-END-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-09, @val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-EFF-DATE-09,OCCURRENCE-CODE-END-DATE-09 CIP158,CIP168











330 Merged CIP159-0001 RULE-626 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP159 OCCURRENCE-CODE-EFF-DATE-10 1 If OCCURRENCE-CODE-EFF-DATE-10 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-10 CIP159











331 Merged CIP159-0002 RULE-626 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP159 OCCURRENCE-CODE-EFF-DATE-10 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-10 CIP159











332 No logic changes CIP159-0003 RULE-628 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP159 OCCURRENCE-CODE-EFF-DATE-10 2 If OCCURRENCE-CODE-10 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-10 must not be 8-filled 2355 Relational edit between OCCURRENCE-CODE-10 and OCCURRENCE-CODE-EFF-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-10), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-10)' OCCURRENCE-CODE-10,OCCURRENCE-CODE-EFF-DATE-10 CIP149,CIP159











333 Merged CIP159-0005 RULE-629 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP159 OCCURRENCE-CODE-EFF-DATE-10 2 OCCURRENCE-CODE-EFF-DATE-10 must be <= OCCURRENCE-CODE-END-DATE-10 2078 Relational edit between OCCURRENCE-CODE-EFF-DATE-10 and OCCURRENCE-CODE-END-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-10, @val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-EFF-DATE-10,OCCURRENCE-CODE-END-DATE-10 CIP159,CIP169











334 Merged CIP160-0001 RULE-630 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP160 OCCURRENCE-CODE-END-DATE-01 1 If OCCURRENCE-CODE-END-DATE-01 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-01 CIP160











335 Merged CIP160-0002 RULE-630 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP160 OCCURRENCE-CODE-END-DATE-01 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-01 CIP160











336 No logic changes CIP160-0004 RULE-632 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP160 OCCURRENCE-CODE-END-DATE-01 2 If OCCURRENCE-CODE-01 is not 8-filled, then OCCURRENCE-CODE-END-DATE-01 must not be 8-filled 2338 Relational edit between OCCURRENCE-CODE-01 and OCCURRENCE-CODE-END-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-01), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-01,OCCURRENCE-CODE-END-DATE-01 CIP140,CIP160











337 Merged CIP160-0006 RULE-593 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP160 OCCURRENCE-CODE-END-DATE-01 2-M
2069
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-01, @val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-EFF-DATE-01,OCCURRENCE-CODE-END-DATE-01 CIP150,CIP160











338 Merged CIP161-0001 RULE-634 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP161 OCCURRENCE-CODE-END-DATE-02 1 If OCCURRENCE-CODE-END-DATE-02 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-02 CIP161











339 Merged CIP161-0002 RULE-634 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP161 OCCURRENCE-CODE-END-DATE-02 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-02 CIP161











340 No logic changes CIP161-0004 RULE-636 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP161 OCCURRENCE-CODE-END-DATE-02 2 If OCCURRENCE-CODE-02 is not 8-filled, then OCCURRENCE-CODE-END-DATE-02 must not be 8-filled 2340 Relational edit between OCCURRENCE-CODE-02 and OCCURRENCE-CODE-END-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-02), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-02,OCCURRENCE-CODE-END-DATE-02 CIP141,CIP161











341 Merged CIP161-0006 RULE-597 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP161 OCCURRENCE-CODE-END-DATE-02 2-M
2070
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-02, @val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-EFF-DATE-02,OCCURRENCE-CODE-END-DATE-02 CIP151,CIP161











342 Merged CIP162-0001 RULE-638 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP162 OCCURRENCE-CODE-END-DATE-03 1 If OCCURRENCE-CODE-END-DATE-03 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-03 CIP162











343 Merged CIP162-0002 RULE-638 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP162 OCCURRENCE-CODE-END-DATE-03 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-03 CIP162











344 No logic changes CIP162-0004 RULE-640 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP162 OCCURRENCE-CODE-END-DATE-03 2 If OCCURRENCE-CODE-03 is not 8-filled, then OCCURRENCE-CODE-END-DATE-03 must not be 8-filled 2342 Relational edit between OCCURRENCE-CODE-03 and OCCURRENCE-CODE-END-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-03), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-03,OCCURRENCE-CODE-END-DATE-03 CIP142,CIP162











345 Merged CIP162-0006 RULE-601 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP162 OCCURRENCE-CODE-END-DATE-03 2-M
2071
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-03, @val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-EFF-DATE-03,OCCURRENCE-CODE-END-DATE-03 CIP152,CIP162











346 Merged CIP163-0001 RULE-642 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP163 OCCURRENCE-CODE-END-DATE-04 1 If OCCURRENCE-CODE-END-DATE-04 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-04 CIP163











347 Merged CIP163-0002 RULE-642 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP163 OCCURRENCE-CODE-END-DATE-04 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-04 CIP163











348 No logic changes CIP163-0004 RULE-644 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP163 OCCURRENCE-CODE-END-DATE-04 2 If OCCURRENCE-CODE-04 is not 8-filled, then OCCURRENCE-CODE-END-DATE-04 must not be 8-filled. 2344 Relational edit between OCCURRENCE-CODE-04 and OCCURRENCE-CODE-END-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-04), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-04,OCCURRENCE-CODE-END-DATE-04 CIP143,CIP163











349 Merged CIP163-0006 RULE-605 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP163 OCCURRENCE-CODE-END-DATE-04 2-M
2072
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-04, @val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-EFF-DATE-04,OCCURRENCE-CODE-END-DATE-04 CIP153,CIP163











350 Merged CIP164-0001 RULE-646 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP164 OCCURRENCE-CODE-END-DATE-05 1 If OCCURRENCE-CODE-END-DATE-05 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-05 CIP164











351 Merged CIP164-0002 RULE-646 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP164 OCCURRENCE-CODE-END-DATE-05 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-05 CIP164











352 No logic changes CIP164-0004 RULE-648 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP164 OCCURRENCE-CODE-END-DATE-05 2 If OCCURRENCE-CODE-05 is not 8-filled, then OCCURRENCE-CODE-END-DATE-05 must not be 8-filled 2346 Relational edit between OCCURRENCE-CODE-05 and OCCURRENCE-CODE-END-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-05), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-05,OCCURRENCE-CODE-END-DATE-05 CIP144,CIP164











353 Merged CIP164-0006 RULE-609 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP164 OCCURRENCE-CODE-END-DATE-05 2-M
2073
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-05, @val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-EFF-DATE-05,OCCURRENCE-CODE-END-DATE-05 CIP154,CIP164











354 Merged CIP165-0001 RULE-650 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP165 OCCURRENCE-CODE-END-DATE-06 1 If OCCURRENCE-CODE-END-DATE-06 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-06 CIP165











355 Merged CIP165-0002 RULE-650 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP165 OCCURRENCE-CODE-END-DATE-06 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-06 CIP165











356 No logic changes CIP165-0004 RULE-652 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP165 OCCURRENCE-CODE-END-DATE-06 2 If OCCURRENCE-CODE-06 is not 8-filled, then OCCURRENCE-CODE-END-DATE-06 must not be 8-filled 2348 Relational edit between OCCURRENCE-CODE-06 and OCCURRENCE-CODE-END-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-06), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-06,OCCURRENCE-CODE-END-DATE-06 CIP145,CIP165











357 Merged CIP165-0006 RULE-613 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP165 OCCURRENCE-CODE-END-DATE-06 2-M
2074
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-06, @val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-EFF-DATE-06,OCCURRENCE-CODE-END-DATE-06 CIP155,CIP165











358 Merged CIP166-0001 RULE-654 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP166 OCCURRENCE-CODE-END-DATE-07 1 If OCCURRENCE-CODE-END-DATE-07 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-07 CIP166











359 Merged CIP166-0002 RULE-654 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP166 OCCURRENCE-CODE-END-DATE-07 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-07 CIP166











360 No logic changes CIP166-0004 RULE-656 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP166 OCCURRENCE-CODE-END-DATE-07 2 If OCCURRENCE-CODE-07 is not 8-filled, then OCCURRENCE-CODE-END-DATE-07 must not be 8-filled 2350 Relational edit between OCCURRENCE-CODE-07 and OCCURRENCE-CODE-END-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-07), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-07,OCCURRENCE-CODE-END-DATE-07 CIP146,CIP166











361 Merged CIP166-0006 RULE-617 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP166 OCCURRENCE-CODE-END-DATE-07 2-M
2075
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-07, @val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-EFF-DATE-07,OCCURRENCE-CODE-END-DATE-07 CIP156,CIP166











362 Merged CIP167-0001 RULE-658 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP167 OCCURRENCE-CODE-END-DATE-08 1 If OCCURRENCE-CODE-END-DATE-08 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-08 CIP167











363 Merged CIP167-0002 RULE-658 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP167 OCCURRENCE-CODE-END-DATE-08 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-08 CIP167











364 No logic changes CIP167-0004 RULE-660 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP167 OCCURRENCE-CODE-END-DATE-08 2 If OCCURRENCE-CODE-08 is not 8-filled, then OCCURRENCE-CODE-END-DATE-08 must not be 8-filled 2352 Relational edit between OCCURRENCE-CODE-08 and OCCURRENCE-CODE-END-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-08), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-08,OCCURRENCE-CODE-END-DATE-08 CIP147,CIP167











365 Merged CIP167-0006 RULE-621 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP167 OCCURRENCE-CODE-END-DATE-08 2-M
2076
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-08, @val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-EFF-DATE-08,OCCURRENCE-CODE-END-DATE-08 CIP157,CIP167











366 Merged CIP168-0001 RULE-662 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP168 OCCURRENCE-CODE-END-DATE-09 1 If OCCURRENCE-CODE-END-DATE-09 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-09 CIP168











367 Merged CIP168-0002 RULE-662 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP168 OCCURRENCE-CODE-END-DATE-09 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-09 CIP168











368 No logic changes CIP168-0004 RULE-664 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP168 OCCURRENCE-CODE-END-DATE-09 2 If OCCURRENCE-CODE-09 is not 8-filled, then OCCURRENCE-CODE-END-DATE-09 must not be 8-filled 2354 Relational edit between OCCURRENCE-CODE-09 and OCCURRENCE-CODE-END-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-09), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-09,OCCURRENCE-CODE-END-DATE-09 CIP148,CIP168











369 Merged CIP168-0006 RULE-625 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP168 OCCURRENCE-CODE-END-DATE-09 2-M
2077
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-09, @val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-EFF-DATE-09,OCCURRENCE-CODE-END-DATE-09 CIP158,CIP168











370 Merged CIP169-0001 RULE-666 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP169 OCCURRENCE-CODE-END-DATE-10 1 If OCCURRENCE-CODE-END-DATE-10 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-10 CIP169











371 Merged CIP169-0002 RULE-666 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP169 OCCURRENCE-CODE-END-DATE-10 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-10 CIP169











372 No logic changes CIP169-0004 RULE-668 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP169 OCCURRENCE-CODE-END-DATE-10 2 If OCCURRENCE-CODE-10 is not 8-filled then OCCURRENCE-CODE-END-DATE-10 must not be 8-filled 2356 Relational edit between OCCURRENCE-CODE-10 and OCCURRENCE-CODE-END-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.OCCURRENCE-CODE-10), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-10,OCCURRENCE-CODE-END-DATE-10 CIP149,CIP169











373 Merged CIP169-0006 RULE-629 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP169 OCCURRENCE-CODE-END-DATE-10 2-M
2078
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-10, @val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-EFF-DATE-10,OCCURRENCE-CODE-END-DATE-10 CIP159,CIP169











374 Retired: required value checks CIP170-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP170 BIRTH-WEIGHT-GRAMS 1 Required data element has not been reported. 113 Required data element has not been reported.

























375 Logic updated: string matching CIP171-0001 RULE-671 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP171 PATIENT-CONTROL-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PATIENT-CONTROL-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.PATIENT-CONTROL-NUM), then fns.matches(@val.PATIENT-CONTROL-NUM, "^[^|*]*$")' PATIENT-CONTROL-NUM CIP171











376 Logic updated: string matching CIP172-0001 RULE-672 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP172 ELIGIBLE-LAST-NAME 1 ELIGIBLE-LAST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid character - ELIGIBLE-LAST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ELIGIBLE-LAST-NAME), then fns.matches(@val.ELIGIBLE-LAST-NAME, "^[^|*]*$")' ELIGIBLE-LAST-NAME CIP172











377 Logic updated: string matching CIP173-0001 RULE-673 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP173 ELIGIBLE-FIRST-NAME 1 ELIGIBLE-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - ELIGIBLE-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ELIGIBLE-FIRST-NAME), then fns.matches(@val.ELIGIBLE-FIRST-NAME, "^[^|*]*$")' ELIGIBLE-FIRST-NAME CIP173











378 Logic updated: string matching CIP174-0001 RULE-674 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP174 ELIGIBLE-MIDDLE-INIT 1 ELIGIBLE-MIDDLE-INIT must not contain non-alphabetic characters 120 Field contains invalid characters - ELIGIBLE-MIDDLE-INIT 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ELIGIBLE-MIDDLE-INIT), then fns.matches(@val.ELIGIBLE-MIDDLE-INIT, "^[^|*]*$")' ELIGIBLE-MIDDLE-INIT CIP174











379 Merged CIP175-0001 RULE-675 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP175 DATE-OF-BIRTH 1 If DATE-OF-BIRTH is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH CIP175











380 Merged CIP175-0002 RULE-675 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP175 DATE-OF-BIRTH 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH CIP175











381 Logic updated: other CIP175-0007 RULE-677 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP175 DATE-OF-BIRTH 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled
and
CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64",
then DATE-OF-BIRTH must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002]		 3037 Relational edit between DATE-OF-BIRTH and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-IP CIP00002 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 if fns.hasValue(@secondaryRecord.DATE-OF-DEATH) && !fns.isEqual(@tertiaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && !fns.isEqual(@tertiaryRecord.ELIGIBILITY-GROUP, "64"), then fns.isLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @secondaryRecord.DATE-OF-DEATH)' DATE-OF-BIRTH CIP175 DATE-OF-DEATH ELG025 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082
382 Logic updated: other CIP175-0008 RULE-678 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP175 DATE-OF-BIRTH 3 If CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64", then DATE-OF-BIRTH must = DATE-OF-BIRTH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3023 A DATE-OF-BIRTH does not match the DATE-OF-BIRTH in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-IP CIP00002 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 'if !fns.isEqual(@tertiaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && !fns.isEqual(@tertiaryRecord.ELIGIBILITY-GROUP, "64"), then fns.isEqual(@primaryRecord.DATE-OF-BIRTH, @secondaryRecord.DATE-OF-BIRTH)' DATE-OF-BIRTH CIP175 DATE-OF-BIRTH ELG024 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082
383 No logic changes CIP176-0001 RULE-679 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP176 HEALTH-HOME-PROV-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-HOME-PROV-IND HEALTH-HOME-PROV-IND CIP176











384 No logic changes CIP176-0003 RULE-680 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP176 HEALTH-HOME-PROV-IND 2 If HEALTH-HOME-ENTITY-NAME is not 8-filled, then HEALTH-HOME-PROV-IND must = "1" 2294 Relational edit between HEALTH-HOME-PROV-IND and HEALTH-HOME-ENTITY-NAME failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.isEqual(@val.HEALTH-HOME-PROV-IND, "1")' HEALTH-HOME-ENTITY-NAME,HEALTH-HOME-PROV-IND CIP214,CIP176











385 No logic changes CIP177-0001 RULE-681 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP177 WAIVER-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-TYPE WAIVER-TYPE CIP177











386 Merged CIP178-0001 RULE-682 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP178 WAIVER-ID 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID CIP178











387 Merged CIP178-0005 RULE-683 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP178 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CIP177,CIP178











388 Merged CIP178-0009 RULE-682 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP178 WAIVER-ID 3 WAIVER-ID must = waiver ID in state-provided crosswalk 3029 Edit with an external reference (state provided WAIVER-ID-/WAIVER-TYPE crosswalk) failed 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID CIP178











389 Merged CIP178-0010 RULE-683 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP178 WAIVER-ID 2 If WAIVER-TYPE is 8-filled, then WAIVER-ID must be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CIP177,CIP178











390 Merged CIP178-0011 RULE-683 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP178 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CIP177,CIP178











391 Retired: Other reasons CIP179-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP179 BILLING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























392 Logic updated: other CIP179-0004 RULE-688 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP179 BILLING-PROV-NUM 3 BILLING-PROV-NUM must = a value in PROV-IDENTIFIER [PROVIDER] where FACILITY-GROUP-INDIVIDUAL-CODE [PROVIDER] = 01 3033 Relational edit between BILLING-PROV-NUM, PROVIDER-IDENTIFIER [PROVIDER], and FACILITY-GROUP-INDIVIDUAL-CODE [PROVIDER] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-IP CIP00002 For every record of type PROV-IDENTIFIERS, there must be a valid record of type PROV-ATTRIBUTES-MAIN that matches on the join keys, where fns.isEqual(@primaryRecord.FACILITY-GROUP-INDIVIDUAL-CODE, "01") FACILITY-GROUP-INDIVIDUAL-CODE PRV026



SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV073,PRV075 SUBMITTING-STATE,PROV-IDENTIFIER
SUBMITTING-STATE,BILLING-PROV-NUM CIP017,CIP179
393 Logic updated: other CIP179-0005 RULE-689 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP179 BILLING-PROV-NUM 3 If ( BILLING-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then BILLING-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-IP CIP00002

For every record of type CLAIM-HEADER-RECORD-IP, if fns.hasValue(@secondaryRecord.BILLING-PROV-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "1") PROV-IDENTIFIER-TYPE PRV077 BILLING-PROV-NUM,TYPE-OF-CLAIM CIP179,CIP100

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,BILLING-PROV-NUM CIP017,CIP179



394 Merged CIP180-0001 RULE-690 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP180 BILLING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM CIP180











395 Merged CIP180-0002 RULE-690 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP180 BILLING-PROV-NPI-NUM 1 If BILLING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM CIP180











396 Logic updated: other CIP180-0006 RULE-692 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP180 BILLING-PROV-NPI-NUM 2 BILLING-PROV-NPI-NUM must = a value in PROV-IDENTIFIER [PROVIDER] where FACILITY-GROUP-INDIVIDUAL-CODE [PROVIDER] = 01 and PROV-IDENTIFIER-TYPE [PROVIDER] = "2" 2239 Relational edit between BILLING-PROV-NPI-NUM, PROVIDER-IDENTIFIER [PROVIDER], FACILITY-GROUP-INDIVIDUAL-CODE [PROVIDER] and PROV-IDENTIFIER-TYPE [PROVIDER] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-IP CIP00002 For every record of type PROV-IDENTIFIERS, there must be a valid record of type PROV-ATTRIBUTES-MAIN that matches on the join keys, where fns.isEqual(@primaryRecord.FACILITY-GROUP-INDIVIDUAL-CODE, "01") && fns.isEqual(@secondaryRecord.PROV-IDENTIFIER-TYPE, "2") FACILITY-GROUP-INDIVIDUAL-CODE PRV026 PROV-IDENTIFIER-TYPE PRV077

SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV073,PRV075 SUBMITTING-STATE,PROV-IDENTIFIER
SUBMITTING-STATE,BILLING-PROV-NPI-NUM CIP017,CIP180
397 No logic changes CIP181-0001 RULE-693 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP181 BILLING-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY BILLING-PROV-TAXONOMY CIP181











398 No logic changes CIP182-0001 RULE-694 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP182 BILLING-PROV-TYPE 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE BILLING-PROV-TYPE CIP182











399 No logic changes CIP183-0001 RULE-695 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP183 BILLING-PROV-SPECIALTY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY BILLING-PROV-SPECIALTY CIP183











400 Merged CIP184-0001 RULE-696 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP184 ADMITTING-PROV-NPI-NUM 1 If ADMITTING-PROV-NPI-NUM not > or = 0 120 Field contains invalid characters - ADMITTING-PROV-NPI-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ADMITTING-PROV-NPI-NUM), then fns.isValidNPI(@val.ADMITTING-PROV-NPI-NUM)' ADMITTING-PROV-NPI-NUM CIP184











401 Merged CIP184-0002 RULE-696 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP184 ADMITTING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.ADMITTING-PROV-NPI-NUM), then fns.isValidNPI(@val.ADMITTING-PROV-NPI-NUM)' ADMITTING-PROV-NPI-NUM CIP184











402 Retired: Other reasons CIP185-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP185 ADMITTING-PROV-NUM 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























403 No logic changes CIP186-0001 RULE-699 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP186 ADMITTING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY ADMITTING-PROV-SPECIALTY CIP186











404 No logic changes CIP187-0001 RULE-700 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP187 ADMITTING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY ADMITTING-PROV-TAXONOMY CIP187











405 No logic changes CIP188-0001 RULE-701 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP188 ADMITTING-PROV-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE ADMITTING-PROV-TYPE CIP188











406 Retired: Other reasons CIP189-0001
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP189 REFERRING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























407 Merged CIP190-0001 RULE-703 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP190 REFERRING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.REFERRING-PROV-NPI-NUM), then fns.isValidNPI(@val.REFERRING-PROV-NPI-NUM)' REFERRING-PROV-NPI-NUM CIP190











408 Merged CIP190-0002 RULE-703 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP190 REFERRING-PROV-NPI-NUM 1 If REFERRING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.REFERRING-PROV-NPI-NUM), then fns.isValidNPI(@val.REFERRING-PROV-NPI-NUM)' REFERRING-PROV-NPI-NUM CIP190











409 No logic changes CIP191-0001 RULE-705 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP191 REFERRING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY REFERRING-PROV-TAXONOMY CIP191











410 No logic changes CIP192-0001 RULE-706 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP192 REFERRING-PROV-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE REFERRING-PROV-TYPE CIP192











411 No logic changes CIP193-0001 RULE-707 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP193 REFERRING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY REFERRING-PROV-SPECIALTY CIP193











412 No logic changes CIP194-0001 RULE-708 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP194 DRG-OUTLIER-AMT 1 If DRG-OUTLIER-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 DRG-OUTLIER-AMT CIP194











413 Merged CIP194-0002 RULE-709 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP194 DRG-OUTLIER-AMT 2 If OUTLIER-CODE = "01", "02", or "10", then DRG-OUTLIER-AMT must not be 8-filled 2276 Relational edit between DRG-OUTLIER-AMT and OUTLIER-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.isEqualToAny(@val.OUTLIER-CODE, "01", "02", "10"), then fns.hasValue(@val.DRG-OUTLIER-AMT)' OUTLIER-CODE,DRG-OUTLIER-AMT CIP197,CIP194











414 No logic changes CIP194-0003 RULE-710 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP194 DRG-OUTLIER-AMT 2 If OUTLIER-CODE = "00" or "09", then DRG-OUTLIER-AMT must be "0" or 8-filled 2276 Relational edit between DRG-OUTLIER-AMT and OUTLIER-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqualToAny(@val.OUTLIER-CODE, "00", "09"), then !fns.hasValue(@val.DRG-OUTLIER-AMT) || fns.isEqual(@val.DRG-OUTLIER-AMT, "0.00")' OUTLIER-CODE,DRG-OUTLIER-AMT CIP197,CIP194











415 No logic changes CIP195-0001 RULE-711 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP195 DRG-REL-WEIGHT 1 If DRG-REL-WEIGHT not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.DRG-REL-WEIGHT), then fns.isNonNegative(@val.DRG-REL-WEIGHT)' DRG-REL-WEIGHT CIP195











416 Logic updated: string matching CIP196-0001 RULE-712 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP196 MEDICARE-HIC-NUM 1 Field contains invalid characters -MEDICARE-HIC-NUM 120 Field contains invalid characters -MEDICARE-HIC-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.matches(@val.MEDICARE-HIC-NUM, "^[^|*]*$")' MEDICARE-HIC-NUM CIP196











417 No logic changes CIP196-0003 RULE-713 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP196 MEDICARE-HIC-NUM 2 If CROSSOVER-INDICATOR= "1" and MEDICARE-BENEFICIARY-IDENTIFIER is 8-filled, then MEDICARE-HIC-NUM must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.hasValue(@val.MEDICARE-HIC-NUM)' CROSSOVER-INDICATOR,MEDICARE-BENEFICIARY-IDENTIFIER,MEDICARE-HIC-NUM CIP023,CIP222,CIP196











418 No logic changes CIP197-0001 RULE-714 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP197 OUTLIER-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: OUTLIER-CODE OUTLIER-CODE CIP197











419 Merged CIP197-0002 RULE-709 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP197 OUTLIER-CODE 2 If DRG-OUTLIER-AMT is not 8-filled, then OUTLIER-CODE must = "01" or "02" or "10" 2360 Relational edit between OUTLIER-CODE and DRG-OUTLIER-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if and only if fns.isEqualToAny(@val.OUTLIER-CODE, "01", "02", "10"), then fns.hasValue(@val.DRG-OUTLIER-AMT)' OUTLIER-CODE,DRG-OUTLIER-AMT CIP197,CIP194











420 No logic changes CIP198-0001 RULE-716 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP198 OUTLIER-DAYS 1 If OUTLIER-DAYS is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: S9(5) OUTLIER-DAYS CIP198











421 No logic changes CIP198-0003 RULE-717 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP198 OUTLIER-DAYS 2 If OUTLIER-CODE = "01", then OUTLIER-DAYS must not be 8-filled 2361 Relational edit between OUTLIER-DAYS and OUTLIER-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqual(@val.OUTLIER-CODE, "01"), then fns.hasValue(@val.OUTLIER-DAYS)' OUTLIER-CODE,OUTLIER-DAYS CIP197,CIP198











422 No logic changes CIP199-0001 RULE-718 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP199 PATIENT-STATUS 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PATIENT-STATUS PATIENT-STATUS CIP199











423 No logic changes CIP199-0002 RULE-719 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP199 PATIENT-STATUS 3 If DATE-OF-DEATH [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] is <= DISCHARGE-DATE, then PATIENT-STATUS must = "20", "40", "41", OR "42" where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3039 Relational edit between PATIENT-STATUS and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-IP CIP00002

'if fns.isLessThanOrEqual(@primaryRecord.DATE-OF-DEATH, @secondaryRecord.DISCHARGE-DATE), then fns.isEqualToAny(@secondaryRecord.PATIENT-STATUS, "20", "40", "41", "42")' DATE-OF-DEATH ELG025 DISCHARGE-DATE,PATIENT-STATUS CIP096,CIP199

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP017,CIP022



424 No logic changes CIP201-0001 RULE-720 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP201 BMI 1 If BMI is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: S9(5)V9 BMI CIP201











425 Logic updated: string matching CIP202-0001 RULE-721 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP202 REMITTANCE-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - REMITTANCE-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.REMITTANCE-NUM), then fns.matches(@val.REMITTANCE-NUM, "^[^|*]*$")' REMITTANCE-NUM CIP202











426 Retired: required value checks CIP202-0002
CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP202 REMITTANCE-NUM 1 If REMITTANCE-NUM is null 113 Required data element has not been reported.

























427 No logic changes CIP203-0001 RULE-723 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP203 SPLIT-CLAIM-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: SPLIT-CLAIM-IND SPLIT-CLAIM-IND CIP203











428 No logic changes CIP204-0001 RULE-724 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP204 BORDER-STATE-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: BORDER-STATE-IND BORDER-STATE-IND CIP204











429 No logic changes CIP206-0001 RULE-725 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP206 BENEFICIARY-COINSURANCE-AMOUNT 1 If BENEFICIARY-COINSURANCE-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COINSURANCE-AMOUNT CIP206











430 Merged CIP207-0001 RULE-726 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP207 BENEFICIARY-COINSURANCE-DATE-PAID 1 If BENEFICIARY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID CIP207











431 Merged CIP207-0002 RULE-726 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP207 BENEFICIARY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID CIP207











432 No logic changes CIP208-0001 RULE-728 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP208 BENEFICIARY-COPAYMENT-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COPAYMENT-AMOUNT CIP208











433 Merged CIP209-0001 RULE-729 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP209 BENEFICIARY-COPAYMENT-DATE-PAID 1 If BENEFICIARY-COPAYMENT-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COPAYMENT-DATE-PAID CIP209











434 Merged CIP209-0002 RULE-729 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP209 BENEFICIARY-COPAYMENT-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COPAYMENT-DATE-PAID CIP209











435 No logic changes CIP210-0001 RULE-731 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP210 BENEFICIARY-DEDUCTIBLE-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-DEDUCTIBLE-AMOUNT CIP210











436 Merged CIP211-0001 RULE-732 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP211 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 If BENEFICIARY-DEDUCTIBLE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID CIP211











437 Merged CIP211-0002 RULE-732 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP211 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID CIP211











438 No logic changes CIP212-0001 RULE-734 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP212 CLAIM-DENIED-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-DENIED-INDICATOR CLAIM-DENIED-INDICATOR CIP212











439 No logic changes CIP212-0003 RULE-735 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP212 CLAIM-DENIED-INDICATOR 2 If TYPE-OF-CLAIM = "Z", then CLAIM-DENIED-INDICATOR must = "0" 2242 Relational edit between CLAIM-DENIED-INDICATOR and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.isEqual(@val.TYPE-OF-CLAIM, "Z"), then fns.isEqual(@val.CLAIM-DENIED-INDICATOR, "0")' TYPE-OF-CLAIM,CLAIM-DENIED-INDICATOR CIP100,CIP212











440 No logic changes CIP213-0001 RULE-736 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP213 COPAY-WAIVED-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: COPAY-WAIVED-IND COPAY-WAIVED-IND CIP213











441 Logic updated: string matching CIP214-0001 RULE-737 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP214 HEALTH-HOME-ENTITY-NAME 1 If HEALTH-HOME-ENTITY-NAME is populated, it must contains valid characters. 120 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.matches(@val.HEALTH-HOME-ENTITY-NAME, "^[^|*]*$")' HEALTH-HOME-ENTITY-NAME CIP214











442 No logic changes CIP216-0001 RULE-738 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP216 THIRD-PARTY-COINSURANCE-AMOUNT-PAID 1 If THIRD-PARTY-COINSURANCE-AMOUNT-PAID is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COINSURANCE-AMOUNT-PAID CIP216











443 Merged CIP217-0001 RULE-739 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP217 THIRD-PARTY-COINSURANCE-DATE-PAID 1 If THIRD-PARTY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID CIP217











444 Merged CIP217-0002 RULE-739 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP217 THIRD-PARTY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID CIP217











445 No logic changes CIP218-0001 RULE-741 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP218 THIRD-PARTY-COPAYMENT-AMOUNT-PAID 1 If THIRD-PARTY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COPAYMENT-AMOUNT-PAID CIP218











446 Merged CIP219-0001 RULE-742 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP219 THIRD-PARTY-COPAYMENT-DATE-PAID 1 If THIRD-PARTY-COPAYMENT-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID CIP219











447 Merged CIP219-0002 RULE-742 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP219 THIRD-PARTY-COPAYMENT-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID CIP219











448 No logic changes CIP220-0001 RULE-744 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP220 MEDICAID-AMOUNT-PAID-DSH 1 If MEDICAID-AMOUNT-PAID-DSH is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-AMOUNT-PAID-DSH CIP220











449 Merged CIP221-0001 RULE-745 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP221 HEALTH-HOME-PROVIDER-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI CIP221











450 Merged CIP221-0002 RULE-745 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP221 HEALTH-HOME-PROVIDER-NPI 1 If HEALTH-HOME-PROVIDER-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI CIP221











451 Logic updated: other CIP221-0004 RULE-747 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP221 HEALTH-HOME-PROVIDER-NPI 3 If ( HEALTH-HOME-PROVIDER-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then HEALTH-HOME-PROVIDER-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-IP CIP00002

For every record of type CLAIM-HEADER-RECORD-IP, if fns.hasValue(@secondaryRecord.HEALTH-HOME-PROVIDER-NPI) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "2") PROV-IDENTIFIER-TYPE PRV077 HEALTH-HOME-PROVIDER-NPI,TYPE-OF-CLAIM CIP221,CIP100

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,HEALTH-HOME-PROVIDER-NPI CIP017,CIP221



452 Logic updated: string matching CIP222-0001 RULE-748 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP222 MEDICARE-BENEFICIARY-IDENTIFIER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - MEDICARE-BENEFICIARY-IDENTIFIER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.matches(@val.MEDICARE-BENEFICIARY-IDENTIFIER, "^[^|*]*$")' MEDICARE-BENEFICIARY-IDENTIFIER CIP222











453 No logic changes CIP222-0003 RULE-749 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP222 MEDICARE-BENEFICIARY-IDENTIFIER 2 If END-OF-TIME-PERIOD >= "20151110", CROSSOVER-INDICATOR= "1" and MEDICARE-HIC-NUM is 8-filled, then MEDICARE-BENEFICIARY-IDENTIFIER must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 FILE-HEADER-RECORD-IP CIP00001

'if fns.isGreaterThanOrEqual(@fileHeader.END-OF-TIME-PERIOD, "2015-11-10") && fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER)' CROSSOVER-INDICATOR,MEDICARE-HIC-NUM,MEDICARE-BENEFICIARY-IDENTIFIER CIP023,CIP196,CIP222 END-OF-TIME-PERIOD CIP010









454 No logic changes CIP223-0001 RULE-750 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP223 OPERATING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY OPERATING-PROV-TAXONOMY CIP223











455 Merged CIP224-0001 RULE-751 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP224 UNDER-DIRECTION-OF-PROV-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.UNDER-DIRECTION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-DIRECTION-OF-PROV-NPI)' UNDER-DIRECTION-OF-PROV-NPI CIP224











456 Merged CIP224-0002 RULE-751 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP224 UNDER-DIRECTION-OF-PROV-NPI 1 If UNDER-DIRECTION-OF-PROV-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.UNDER-DIRECTION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-DIRECTION-OF-PROV-NPI)' UNDER-DIRECTION-OF-PROV-NPI CIP224











457 No logic changes CIP225-0001 RULE-753 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP225 UNDER-DIRECTION-OF-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY UNDER-DIRECTION-OF-PROV-TAXONOMY CIP225











458 Merged CIP226-0001 RULE-754 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP226 UNDER-SUPERVISION-OF-PROV-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.UNDER-SUPERVISION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-SUPERVISION-OF-PROV-NPI)' UNDER-SUPERVISION-OF-PROV-NPI CIP226











459 Merged CIP226-0002 RULE-754 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP226 UNDER-SUPERVISION-OF-PROV-NPI 1 If UNDER-SUPERVISION-OF-PROV-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.UNDER-SUPERVISION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-SUPERVISION-OF-PROV-NPI)' UNDER-SUPERVISION-OF-PROV-NPI CIP226











460 No logic changes CIP227-0001 RULE-756 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP227 UNDER-SUPERVISION-OF-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY UNDER-SUPERVISION-OF-PROV-TAXONOMY CIP227











461 No logic changes CIP228-0001 RULE-757 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP228 MEDICARE-PAID-AMT 1 If MEDICARE-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICARE-PAID-AMT CIP228











462 Logic updated: string matching CIP229-0001 RULE-758 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP229 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION CIP229











463 Moved to R&C CIP231-0001
CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP231 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























464 Moved to R&C CIP231-0004
CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP231 RECORD-ID 2 If FILE-NAME = "CLAIM-IP", then the first 3 positions of RECORD-ID must = "CIP" 150 Invalid or missing RECORD-ID

























465 No logic changes CIP232-0001 RULE-761 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP232 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE CIP232











466 Logic updated: other CIP232-0004 RULE-762 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP232 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-IP-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-IP CIP00003 FILE-HEADER-RECORD-IP CIP00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE CIP232 SUBMITTING-STATE CIP007









467 Retired: Other reasons CIP233-0001
CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP233 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























468 No logic changes CIP233-0003 RULE-764 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP233 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-LINE-RECORD-IP CIP00003



Field RECORD-NUMBER should be unique across all records of type CLAIM-LINE-RECORD-IP RECORD-NUMBER CIP233











469 Retired: MSIS ID checks CIP234-0001
CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP234 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























470 Retired: MSIS ID checks CIP234-0002
CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP234 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























471 No logic changes CIP234-0003 RULE-767 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP234 MSIS-IDENTIFICATION-NUM 2 If TYPE-OF-CLAIM = "4", "D", OR "X", then the first byte of MSIS-IDENTIFICATION-NUM must = "&" 2331 Relational edit between MSIS-IDENTIFICATION-NUM and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "4", "D", "X"), then fns.matches(@secondaryRecord.MSIS-IDENTIFICATION-NUM, "^&.*$")' TYPE-OF-CLAIM CIP100 MSIS-IDENTIFICATION-NUM CIP234

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



472 Logic updated: parent/child overlap CIP234-0005 RULE-768 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP234 MSIS-IDENTIFICATION-NUM 2 ICN-ORIG [SUBMITTING-STATE CLAIM-LINE-RECORD-IP-CIP00003] must = ICN-ORIG [CLAIM-HEADER-RECORD-IP-CIP00002],
and ICN-ADJ [SUBMITTING-STATE CLAIM-LINE-RECORD-IP-CIP00003] must = ICN-ADJ [CLAIM-HEADER-RECORD-IP-CIP00002],
and ADJUDICATION-DATE [SUBMITTING-STATE CLAIM-LINE-RECORD-IP-CIP00003] must = ADJUDICATION-DATE [CLAIM-HEADER-RECORD-IP-CIP00002] on any record in the file,
and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] must = SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] on the same record in the file		 2189 Edit that CLAIM-LINE-RECORD-IP-CIP00003 child record has a CLAIM-HEADER-RECORD-IP-CIP00002 parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

record CLAIM-LINE-RECORD-IP has corresponding parent record CLAIM-HEADER-RECORD-IP





SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



473 Logic updated: string matching CIP235-0001 RULE-769 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP235 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ORIG 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG CIP235











474 Logic updated: string matching CIP236-0001 RULE-770 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP236 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ CIP236











475 No logic changes CIP237-0001 RULE-771 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP237 LINE-NUM-ORIG 1 If LINE-NUM-ORIG not >=0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.LINE-NUM-ORIG), then fns.isNonNegative(@val.LINE-NUM-ORIG)' LINE-NUM-ORIG CIP237











476 No logic changes CIP238-0001 RULE-772 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP238 LINE-NUM-ADJ 1 If LINE-NUM-ADJ not >=0. 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.isNonNegative(@val.LINE-NUM-ADJ)' LINE-NUM-ADJ CIP238











477 No logic changes CIP238-0002 RULE-773 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP238 LINE-NUM-ADJ 2 If LINE-ADJUSTMENT-IND = "0", then LINE-NUM-ADJ must be 8-filled 2312 Relational edit between LINE-NUM-ADJ and LINE-ADJUSTMENT-IND failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.isEqual(@val.LINE-ADJUSTMENT-IND, "0"), then !fns.hasValue(@val.LINE-NUM-ADJ)' LINE-ADJUSTMENT-IND,LINE-NUM-ADJ CIP239,CIP238











478 No logic changes CIP239-0001 RULE-774 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP239 LINE-ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: LINE-ADJUSTMENT-IND LINE-ADJUSTMENT-IND CIP239











479 No logic changes CIP239-0002 RULE-775 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP239 LINE-ADJUSTMENT-IND 2 If LINE-NUM-ADJ is not 8-filled, then LINE-ADJUSTMENT-IND must not be 8-filled 2310 Relational edit between LINE-ADJUSTMENT-IND and LINE-NUM-ADJ failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.hasValue(@val.LINE-ADJUSTMENT-IND)' LINE-NUM-ADJ,LINE-ADJUSTMENT-IND CIP238,CIP239











480 No logic changes CIP240-0001 RULE-776 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP240 LINE-ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE LINE-ADJUSTMENT-REASON-CODE CIP240











481 Retired: required value checks CIP241-0001
CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP241 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported.

























482 No logic changes CIP242-0001 RULE-778 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP242 CLAIM-LINE-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-LINE-STATUS CIP242











483 Merged CIP243-0001 RULE-779 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP243 BEGINNING-DATE-OF-SERVICE 1 If BEGINNING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE CIP243











484 Merged CIP243-0002 RULE-779 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP243 BEGINNING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE CIP243











485 Merged CIP243-0003 RULE-781 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP243 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2013 Relational edit between BEGINNING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-IP CIP00003 FILE-HEADER-RECORD-IP CIP00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE CIP243 END-OF-TIME-PERIOD CIP010









486 Merged CIP243-0004 RULE-782 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP243 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CIP243,CIP244











487 Logic updated: other CIP243-0005 RULE-783 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP243 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-LINE-RECORD-IP] 2009 Relational edit between BEGINNING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-LINE-RECORD-IP] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' BEGINNING-DATE-OF-SERVICE,ADJUDICATION-DATE CIP243,CIP286











488 Logic updated: other CIP243-0006 RULE-784 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP243 BEGINNING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then BEGINNING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-IP-CIP00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3002 Relational edit between BEGINNING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 BEGINNING-DATE-OF-SERVICE CIP243

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP232,CIP234



489 Merged CIP243-0010 RULE-781 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP243 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-IP CIP00003 FILE-HEADER-RECORD-IP CIP00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE CIP243 END-OF-TIME-PERIOD CIP010









490 Merged CIP244-0001 RULE-786 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP244 ENDING-DATE-OF-SERVICE 1 If ENDING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE CIP244











491 Merged CIP244-0002 RULE-786 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP244 ENDING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE CIP244











492 Merged CIP244-0003 RULE-782 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP244 ENDING-DATE-OF-SERVICE 2-M
2012
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CIP243,CIP244











493 Logic updated: other CIP244-0004 RULE-789 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP244 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-LINE-RECORD-IP] 2034 Relational edit between ENDING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-LINE-RECORD-IP] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' ENDING-DATE-OF-SERVICE,ADJUDICATION-DATE CIP244,CIP286











494 Logic updated: other CIP244-0005 RULE-790 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP244 ENDING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), ENDING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-IP-CIP00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] =SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3005 Relational edit between ENDING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.ENDING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ENDING-DATE-OF-SERVICE CIP244

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP232,CIP234



495 Logic updated: other CIP244-0008 RULE-791 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP244 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2036 Relational edit between ENDING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-IP CIP00003 FILE-HEADER-RECORD-IP CIP00001

'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' ENDING-DATE-OF-SERVICE CIP244 END-OF-TIME-PERIOD CIP010









496 No logic changes CIP245-0001 RULE-792 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP245 REVENUE-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: REVENUE-CODE REVENUE-CODE CIP245











497 No logic changes CIP248-0001 RULE-793 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP248 IMMUNIZATION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: IMMUNIZATION-TYPE IMMUNIZATION-TYPE CIP248











498 No logic changes CIP249-0001 RULE-794 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP249 IP-LT-QUANTITY-OF-SERVICE-ACTUAL 1 If IP-LT-QUANTITY-OF-SERVICE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: S9(6)V999 IP-LT-QUANTITY-OF-SERVICE-ACTUAL CIP249











499 No logic changes CIP250-0001 RULE-795 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP250 IP-LT-QUANTITY-OF-SERVICE-ALLOWED 1 If IP-LT-QUANTITY-OF-SERVICE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: S9(6)V999 IP-LT-QUANTITY-OF-SERVICE-ALLOWED CIP250











500 No logic changes CIP251-0001 RULE-796 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP251 REVENUE-CHARGE 1 If REVENUE-CHARGE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 REVENUE-CHARGE CIP251











501 Logic updated: other CIP251-0005 RULE-797 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP251 REVENUE-CHARGE 2 The absolute value of the sum of REVENUE-CHARGE on each detail line record must be <= absolute value of TOT-BILLED-AMT 2409 Relational edit between REVENUE-CHARGE and TOT-BILLED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'fns.isDollarSumLessThanOrEqual(@primaryRecord.TOT-BILLED-AMT, @secondaryRecords.REVENUE-CHARGE)' TOT-BILLED-AMT CIP112 REVENUE-CHARGE CIP251

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



502 Merged CIP251-0006 RULE-798 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP251 REVENUE-CHARGE 2 If REVENUE-CODE is 8-filled, then REVENUE-CHARGE must be 8-filled 2408 Relational edit between REVENUE-CHARGE and REVENUE-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if and only if fns.hasValue(@val.REVENUE-CODE), then fns.hasValue(@val.REVENUE-CHARGE)' REVENUE-CODE,REVENUE-CHARGE CIP245,CIP251











503 Merged CIP251-0007 RULE-798 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP251 REVENUE-CHARGE 2 If REVENUE-CODE is not 8-filled, then REVENUE-CHARGE must not be 8-filled 2408 Relational edit between REVENUE-CHARGE and REVENUE-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if and only if fns.hasValue(@val.REVENUE-CODE), then fns.hasValue(@val.REVENUE-CHARGE)' REVENUE-CODE,REVENUE-CHARGE CIP245,CIP251











504 No logic changes CIP252-0001 RULE-800 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP252 ALLOWED-AMT 1 If ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 ALLOWED-AMT CIP252











505 No logic changes CIP253-0001 RULE-801 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP253 TPL-AMT 1 If TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TPL-AMT CIP253











506 No logic changes CIP254-0001 RULE-802 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP254 MEDICAID-PAID-AMT 1 If MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-PAID-AMT CIP254











507 No logic changes CIP255-0001 RULE-803 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP255 MEDICAID-FFS-EQUIVALENT-AMT 1 If MEDICAID-FFS-EQUIVALENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-FFS-EQUIVALENT-AMT CIP255











508 No logic changes CIP255-0002 RULE-804 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP255 MEDICAID-FFS-EQUIVALENT-AMT 2 If TYPE-OF-CLAIM = "C", "3", or "W", then MEDICAID-FFS-EQUIVALENT-AMT must not be 8-filled 2443 Relational edit with MEDICAID-FFS-EQUIVALENT-AMT and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.hasValue(@secondaryRecord.MEDICAID-FFS-EQUIVALENT-AMT)' TYPE-OF-CLAIM CIP100 MEDICAID-FFS-EQUIVALENT-AMT CIP255

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



509 No logic changes CIP256-0001 RULE-805 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP256 BILLING-UNIT 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: BILLING-UNIT BILLING-UNIT CIP256











510 No logic changes CIP257-0001 RULE-806 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP257 TYPE-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-SERVICE TYPE-OF-SERVICE CIP257











511 No logic changes CIP257-0005 RULE-807 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP257 TYPE-OF-SERVICE 2 If FILE-NAME = "CLAIMIP", then TYPE-OF-SERVICE must = 001, 058, 060, 084, 086, 090, 091, 092, 093, 123, 132, OR 135 2289 Relational edit between FILE-NAME and TYPE-OF-SERVICE failed 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'fns.isEqualToAny(@val.TYPE-OF-SERVICE, "001", "058", "060", "084", "086", "090", "091", "092", "093", "123", "132", "135")' TYPE-OF-SERVICE CIP257











512 No logic changes CIP257-0006 RULE-808 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP257 TYPE-OF-SERVICE 3 TYPE-OF-SERVICE must <> "086" where SEX = "M" [ELIGIBLE] and MSIS-IDENTIFICATION-NUM and [CLAIM-LINE-RECORD-IP-CIP00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3013 Relational edit between TYPE-OF-SERVICE and SEX [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqual(@primaryRecord.SEX, "M"), then !fns.isEqual(@secondaryRecord.TYPE-OF-SERVICE, "086")' SEX ELG023 TYPE-OF-SERVICE CIP257

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP232,CIP234



513 Retired: Other reasons CIP260-0001
CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP260 SERVICING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























514 Logic updated: other CIP260-0007 RULE-810 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP260 SERVICING-PROV-NUM 3 If ( SERVICING-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then SERVICING-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003 PROV-IDENTIFIERS PRV00005 For every record of type CLAIM-LINE-RECORD-IP, if fns.hasValue(@secondaryRecord.SERVICING-PROV-NUM) && !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type CLAIM-HEADER-RECORD-IP that matches on the join keys, where fns.isEqual(@tertiaryRecord.PROV-IDENTIFIER-TYPE, "1") TYPE-OF-CLAIM CIP100 SERVICING-PROV-NUM CIP260 PROV-IDENTIFIER-TYPE PRV077 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP017,CIP020,CIP019,CIP098 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP232,CIP236,CIP235,CIP286 SUBMITTING-STATE,SERVICING-PROV-NUM
SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081
515 Merged CIP261-0001 RULE-812 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP261 SERVICING-PROV-NPI-NUM 1 If SERVICING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.SERVICING-PROV-NPI-NUM), then fns.isValidNPI(@val.SERVICING-PROV-NPI-NUM)' SERVICING-PROV-NPI-NUM CIP261











516 Merged CIP261-0002 RULE-812 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP261 SERVICING-PROV-NPI-NUM 2 If NPI <> ("8888888888" or "9999999999") then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.SERVICING-PROV-NPI-NUM), then fns.isValidNPI(@val.SERVICING-PROV-NPI-NUM)' SERVICING-PROV-NPI-NUM CIP261











517 Logic updated: other CIP261-0006 RULE-813 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP261 SERVICING-PROV-NPI-NUM 3 If ( SERVICING-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then SERVICING-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003 PROV-IDENTIFIERS PRV00005 For every record of type CLAIM-LINE-RECORD-IP, if fns.hasValue(@secondaryRecord.SERVICING-PROV-NPI-NUM) && !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type CLAIM-HEADER-RECORD-IP that matches on the join keys, where fns.isEqual(@tertiaryRecord.PROV-IDENTIFIER-TYPE, "2") TYPE-OF-CLAIM CIP100 SERVICING-PROV-NPI-NUM CIP261 PROV-IDENTIFIER-TYPE PRV077 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP017,CIP020,CIP019,CIP098 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP232,CIP236,CIP235,CIP286 SUBMITTING-STATE,SERVICING-PROV-NPI-NUM
SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081
518 No logic changes CIP262-0001 RULE-814 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP262 SERVICING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY SERVICING-PROV-TAXONOMY CIP262











519 No logic changes CIP263-0001 RULE-815 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP263 SERVICING-PROV-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE SERVICING-PROV-TYPE CIP263











520 No logic changes CIP264-0001 RULE-816 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP264 SERVICING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY SERVICING-PROV-SPECIALTY CIP264











521 Merged CIP265-0001 RULE-817 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP265 OPERATING-PROV-NPI-NUM 1 If OPERATING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.OPERATING-PROV-NPI-NUM), then fns.isValidNPI(@val.OPERATING-PROV-NPI-NUM)' OPERATING-PROV-NPI-NUM CIP265











522 Merged CIP265-0002 RULE-817 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP265 OPERATING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.OPERATING-PROV-NPI-NUM), then fns.isValidNPI(@val.OPERATING-PROV-NPI-NUM)' OPERATING-PROV-NPI-NUM CIP265











523 Logic updated: other CIP265-0005 RULE-819 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP265 OPERATING-PROV-NPI-NUM 3 If ( OPERATING-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then OPERATING-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003 PROV-IDENTIFIERS PRV00005 For every record of type CLAIM-LINE-RECORD-IP, if fns.hasValue(@secondaryRecord.OPERATING-PROV-NPI-NUM) && !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type CLAIM-HEADER-RECORD-IP that matches on the join keys, where fns.isEqual(@tertiaryRecord.PROV-IDENTIFIER-TYPE, "2") TYPE-OF-CLAIM CIP100 OPERATING-PROV-NPI-NUM CIP265 PROV-IDENTIFIER-TYPE PRV077 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP017,CIP020,CIP019,CIP098 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP232,CIP236,CIP235,CIP286 SUBMITTING-STATE,OPERATING-PROV-NPI-NUM
SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081
524 No logic changes CIP266-0001 RULE-820 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP266 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION CIP266











525 No logic changes CIP267-0001 RULE-821 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP267 PROV-FACILITY-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-FACILITY-TYPE PROV-FACILITY-TYPE CIP267











526 No logic changes CIP268-0001 RULE-822 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP268 BENEFIT-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: BENEFIT-TYPE BENEFIT-TYPE CIP268











527 No logic changes CIP269-0001 RULE-823 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP269 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CIP269











528 No logic changes CIP269-0002 RULE-824 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP269 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If CHIP-CODE [ELIGIBLE] = "0" , "1", or "2", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT must <> "02" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-IP-CIP00003] = MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] = SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] 3034 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and CHIP-CODE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqualToAny(@primaryRecord.CHIP-CODE, "0", "1", "2"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "02")' CHIP-CODE ELG054 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CIP269

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP232,CIP234



529 No logic changes CIP269-0003 RULE-825 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP269 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] = "0", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT must <> "01" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-IP-CIP00003] = MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] = SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] 3035 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqual(@primaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "00"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "01")' MEDICAID-BASIS-OF-ELIGIBILITY ELG084 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CIP269

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP232,CIP234



530 No logic changes CIP270-0001 RULE-826 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP270 XIX-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: XIX-MBESCBES-CATEGORY-OF-SERVICE XIX-MBESCBES-CATEGORY-OF-SERVICE CIP270











531 No logic changes CIP270-0002 RULE-827 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP270 XIX-MBESCBES-CATEGORY-OF-SERVICE 3 XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMIP] must <> ("14", "35", "42", or "44") where SEX = "M" [ELIGIBLE] and (MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-IP-CIP00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00001] and SUBMITTING-STATE [CLAIM-LINE-RECORD-IP-CIP00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00001] ) 3014 Relational edit between XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMIP] and SEX [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqual(@primaryRecord.SEX, "M"), then !fns.isEqualToAny(@secondaryRecord.XIX-MBESCBES-CATEGORY-OF-SERVICE, "14", "35", "42", "44")' SEX ELG023 XIX-MBESCBES-CATEGORY-OF-SERVICE CIP270

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CIP232,CIP234



532 No logic changes CIP271-0001 RULE-828 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP271 XXI-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: XXI-MBESCBES-CATEGORY-OF-SERVICE XXI-MBESCBES-CATEGORY-OF-SERVICE CIP271











533 No logic changes CIP272-0001 RULE-829 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP272 OTHER-INSURANCE-AMT 1 If OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 OTHER-INSURANCE-AMT CIP272











534 Logic updated: string matching CIP273-0001 RULE-830 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP273 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION CIP273











535 Moved to R&C CIP275-0002
CLAIMIP FILE-HEADER-RECORD-IP-CIP00001 CIP275 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range

























536 No logic changes CIP278-0001 RULE-832 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP278 NDC-QUANTITY 1 If NDC-QUANTITY is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: S9(6)V999 NDC-QUANTITY CIP278











537 Logic updated: other CIP279-0001 RULE-833 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP279 HCPCS-RATE 1 If HCPCS-RATE is not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.HCPCS-RATE), then fns.matches(@val.HCPCS-RATE, "^[^|*]*$")' HCPCS-RATE CIP279











538 Merged CIP284-0001 RULE-834 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP284 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CIP284











539 Merged CIP284-0002 RULE-834 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP284 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CIP284











540 Merged CIP284-0003 RULE-834 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP284 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CIP284











541 No logic changes CIP285-0001 RULE-837 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP285 NDC-UNIT-OF-MEASURE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: NDC-UNIT-OF-MEASURE NDC-UNIT-OF-MEASURE CIP285











542 Merged CIP286-0001 RULE-838 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP286 ADJUDICATION-DATE 1 If ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CIP286











543 Merged CIP286-0002 RULE-838 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP286 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CIP286











544 Logic updated: other CIP286-0006 RULE-840 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP286 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-IP CIP00003 FILE-HEADER-RECORD-IP CIP00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE CIP286 END-OF-TIME-PERIOD CIP010









545 Logic updated: other CIP286-0007 RULE-841 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP286 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be >= ADMISSION-DATE 2002 Relational edit between ADJUDICATION-DATE and ADMISSION-DATE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.hasValue(@primaryRecord.ADMISSION-DATE) && fns.hasValue(@secondaryRecord.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@primaryRecord.ADMISSION-DATE, @secondaryRecord.ADJUDICATION-DATE)' ADMISSION-DATE CIP094 ADJUDICATION-DATE CIP286

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



546 No logic changes CIP287-0001 RULE-842 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP287 SELF-DIRECTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-IP CIP00003



If the field is populated, the value must be contained in the set of valid values with id: SELF-DIRECTION-TYPE SELF-DIRECTION-TYPE CIP287











547 Logic updated: string matching CIP288-0001 RULE-843 CLAIMIP CLAIM-LINE-RECORD-IP-CIP00003 CIP288 PRE-AUTHORIZATION-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PRE-AUTHORIZATION-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-IP CIP00003



'if fns.hasValue(@val.PRE-AUTHORIZATION-NUM), then fns.matches(@val.PRE-AUTHORIZATION-NUM, "^[^|*]*$")' PRE-AUTHORIZATION-NUM CIP288











548 Logic updated: string matching CIP289-0001 RULE-844 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP289 PROV-LOCATION-ID 1 If characters in text string are not alpha characters (A-Z), numbers (0-9) 120 Field contains invalid characters - PROV-LOCATION-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-IP CIP00002



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID CIP289











549 Logic updated: other CIP289-0002 RULE-845 CLAIMIP CLAIM-HEADER-RECORD-IP-CIP00002 CIP289 PROV-LOCATION-ID 3 PROV-LOCATION-ID [CLAIMIP] must = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] where SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002]= SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SERVICING-PROV-NUM [CLAIMIP] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] 3048 Relational edit between PROV-LOCATION-ID [CLAIMIP] and PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003 PROV-LOCATION-AND-CONTACT-INFO PRV00003 'fns.isEqual(@primaryRecord.PROV-LOCATION-ID, @tertiaryRecord.PROV-LOCATION-ID)' PROV-LOCATION-ID CIP289

PROV-LOCATION-ID PRV043 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP017,CIP020,CIP019,CIP098 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CIP232,CIP236,CIP235,CIP286 SUBMITTING-STATE,SERVICING-PROV-NUM
SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV040,PRV042
550 Moved to R&C CLT001-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























551 Moved to R&C CLT001-0004
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT001 RECORD-ID 2 If FILE-NAME = "CLAIM-LT", then the first 3 positions of RECORD-ID must = "CLT" 150 Invalid or missing RECORD-ID

























552 Moved to R&C CLT003-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT003 SUBMISSION-TRANSACTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























553 Moved to R&C CLT004-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT004 FILE-ENCODING-SPECIFICATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























554 Moved to R&C CLT006-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT006 FILE-NAME 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























555 Moved to R&C CLT007-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT007 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























556 Moved to R&C CLT007-0004
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























557 Merged CLT008-0001 RULE-853 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED CLT008











558 Merged CLT008-0002 RULE-853 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED CLT008











559 Moved to R&C CLT008-0003
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed

























560 Moved to R&C CLT008-0004
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























561 Merged CLT009-0001 RULE-857 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD CLT009











562 Merged CLT009-0002 RULE-857 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT009 START-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD CLT009











563 Moved to R&C CLT009-0003
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























564 Moved to R&C CLT009-0004
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























565 Merged CLT010-0001 RULE-861 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT010 END-OF-TIME-PERIOD 1 If END-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD CLT010











566 Merged CLT010-0002 RULE-861 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD CLT010











567 Moved to R&C CLT010-0003
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT010 END-OF-TIME-PERIOD 2-M
2122


























568 Moved to R&C CLT010-0004
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT010 END-OF-TIME-PERIOD 2-M
2019


























569 Moved to R&C CLT011-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT011 FILE-STATUS-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























570 Moved to R&C CLT011-0002
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























571 Moved to R&C CLT012-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT012 SSN-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























572 Logic updated: other CLT012-0002 RULE-868 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT012 SSN-INDICATOR 3 Value for SSN-INDICATOR [CLAIMLT] must match SSN-INDICATOR [ELIGIBLE] 3008 Relational edit between SSN-INDICATOR [CLAIMLT] and SSN-INDICATOR [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) FILE-HEADER-RECORD-LT CLT00001 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@primaryRecord.SSN-INDICATOR) && fns.hasValue(@secondaryRecord.SSN-INDICATOR), then fns.isEqual(@primaryRecord.SSN-INDICATOR, @secondaryRecord.SSN-INDICATOR)' SSN-INDICATOR CLT012 SSN-INDICATOR ELG012

SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD CLT007,CLT009,CLT010 SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD ELG007,ELG009,ELG010



573 No logic changes CLT013-0001 RULE-6237 CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT013 TOT-REC-CNT 1 If TOT-REC-CNT = 0 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT CLT013











574 Moved to R&C CLT013-0002
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record

























575 Moved to R&C CLT014-0001
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























576 Moved to R&C CLT016-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























577 Moved to R&C CLT016-0004
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT016 RECORD-ID 2 If FILE-NAME = "CLAIM-LT", then the first 3 positions of RECORD-ID must = "CLT" 150 Invalid or missing RECORD-ID

























578 No logic changes CLT017-0001 RULE-874 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT017 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE CLT017











579 Logic updated: other CLT017-0004 RULE-875 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-LT-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE CLT017 SUBMITTING-STATE CLT007









580 Retired: Other reasons CLT018-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT018 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























581 No logic changes CLT018-0004 RULE-877 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-HEADER-RECORD-LT CLT00002



Field RECORD-NUMBER should be unique across all records of type CLAIM-HEADER-RECORD-LT RECORD-NUMBER CLT018











582 Logic updated: string matching CLT019-0001 RULE-878 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT019 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ORIG 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG CLT019











583 Logic updated: string matching CLT020-0001 RULE-879 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT020 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ CLT020











584 Retired: required value checks CLT021-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT021 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported.

























585 Retired: MSIS ID checks CLT022-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT022 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























586 Retired: MSIS ID checks CLT022-0002
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT022 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























587 No logic changes CLT022-0003 RULE-883 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT022 MSIS-IDENTIFICATION-NUM 2 If TYPE-OF-CLAIM = "4", "D", OR "X", then the first byte of MSIS-IDENTIFICATION-NUM must = "&" 2331 Relational edit between MSIS-IDENTIFICATION-NUM and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "4", "D", "X"), then fns.matches(@val.MSIS-IDENTIFICATION-NUM, "^&.*$")' TYPE-OF-CLAIM,MSIS-IDENTIFICATION-NUM CLT052,CLT022











588 Logic updated: other CLT022-0005 RULE-884 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT022 MSIS-IDENTIFICATION-NUM 3 MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3026 Edit that claim has matching PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 record failed 3 Relational error E3001 Missing corresponding record (multi file) (ex. missing eligibility record for claim header) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-LT CLT00002

For every record of type CLAIM-HEADER-RECORD-LT, there must be a valid record of type PRIMARY-DEMOGRAPHICS-ELIGIBILITY that matches on the join keys





MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CLT022,CLT017



589 No logic changes CLT023-0001 RULE-885 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT023 CROSSOVER-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CROSSOVER-INDICATOR CROSSOVER-INDICATOR CLT023











590 No logic changes CLT024-0001 RULE-886 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT024 1115A-DEMONSTRATION-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: 1115A-DEMONSTRATION-IND 1115A-DEMONSTRATION-IND CLT024











591 No logic changes CLT024-0003 RULE-887 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT024 1115A-DEMONSTRATION-IND 3 If 1115A-DEMONSTRATION-IND [ELIGIBLE] = 0or 8-filled, then 1115A-DEMONSTRATION-IND must = 0 or 8-filled where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] 3055 An 1115A-DEMONSTRATION-IND does not match the 1115A-DEMONSTRATION-IND in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) 1115A-DEMONSTRATION-INFORMATION ELG00018 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.isEqual(@primaryRecord.1115A-DEMONSTRATION-IND, "0") || !fns.hasValue(@primaryRecord.1115A-DEMONSTRATION-IND), then !fns.hasValue(@secondaryRecord.1115A-DEMONSTRATION-IND) || fns.isEqual(@secondaryRecord.1115A-DEMONSTRATION-IND, "0")' 1115A-DEMONSTRATION-IND ELG233 1115A-DEMONSTRATION-IND CLT024

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG230,ELG232 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT017,CLT022



592 No logic changes CLT025-0001 RULE-888 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT025 ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-IND ADJUSTMENT-IND CLT025











593 No logic changes CLT026-0001 RULE-889 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT026 ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE ADJUSTMENT-REASON-CODE CLT026











594 No logic changes CLT027-0001 RULE-890 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT027 ADMITTING-DIAGNOSIS-CODE 1 ADMITTING-DIAGNOSIS-CODE must equal a valid ICD9/10 valid value without embedded characters. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE ADMITTING-DIAGNOSIS-CODE CLT027











595 No logic changes CLT028-0001 RULE-891 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT028 ADMITTING-DIAGNOSIS-CODE-FLAG 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG ADMITTING-DIAGNOSIS-CODE-FLAG CLT028











596 Merged CLT029-0001 RULE-892 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT029 DIAGNOSIS-CODE-1 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-1 CLT029











597 Merged CLT029-0002 RULE-892 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT029 DIAGNOSIS-CODE-1 1 If DIAGNOSIS-CODE-1 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-1 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-1 CLT029











598 No logic changes CLT030-0001 RULE-894 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT030 DIAGNOSIS-CODE-FLAG-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-1 CLT030











599 No logic changes CLT031-0001 RULE-895 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT031 DIAGNOSIS-POA-FLAG-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-1 CLT031











600 Merged CLT032-0001 RULE-896 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT032 DIAGNOSIS-CODE-2 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-2 CLT032











601 Merged CLT032-0002 RULE-896 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT032 DIAGNOSIS-CODE-2 1 If DIAGNOSIS-CODE-2 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-2 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-2 CLT032











602 Merged CLT032-0007 RULE-898 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT032 DIAGNOSIS-CODE-2 2 If DIAGNOSIS-CODE-2 is not 8-filled, then DIAGNOSIS-CODE-2 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 CLT029,CLT032,CLT035,CLT038,CLT041











603 No logic changes CLT032-0008 RULE-899 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT032 DIAGNOSIS-CODE-2 2 DIAGNOSIS-CODE-2 must be 8-filled if value for DIAGNOSIS-CODE-1 is 8-filled 2263 Relational edit between DIAGNOSIS-CODE-2 and DIAGNOSIS-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-1), then !fns.hasValue(@val.DIAGNOSIS-CODE-2)' DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2 CLT029,CLT032











604 No logic changes CLT033-0001 RULE-900 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT033 DIAGNOSIS-CODE-FLAG-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-2 CLT033











605 No logic changes CLT034-0001 RULE-901 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT034 DIAGNOSIS-POA-FLAG-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-2 CLT034











606 Merged CLT035-0001 RULE-902 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT035 DIAGNOSIS-CODE-3 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-3 CLT035











607 Merged CLT035-0002 RULE-902 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT035 DIAGNOSIS-CODE-3 1 If DIAGNOSIS-CODE-2 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-2 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-3 CLT035











608 Merged CLT035-0007 RULE-898 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT035 DIAGNOSIS-CODE-3 2 If DIAGNOSIS-CODE-3 is not 8-filled, then DIAGNOSIS-CODE-3 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 CLT029,CLT032,CLT035,CLT038,CLT041











609 No logic changes CLT035-0008 RULE-905 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT035 DIAGNOSIS-CODE-3 2 DIAGNOSIS-CODE-3 must be 8-filled if value for DIAGNOSIS-CODE-2 is 8-filled 2265 Relational edit between DIAGNOSIS-CODE-3 and DIAGNOSIS-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-2), then !fns.hasValue(@val.DIAGNOSIS-CODE-3)' DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3 CLT032,CLT035











610 No logic changes CLT036-0001 RULE-906 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT036 DIAGNOSIS-CODE-FLAG-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-3 CLT036











611 No logic changes CLT037-0001 RULE-907 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT037 DIAGNOSIS-POA-FLAG-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-3 CLT037











612 Merged CLT038-0001 RULE-908 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT038 DIAGNOSIS-CODE-4 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-4 CLT038











613 Merged CLT038-0002 RULE-908 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT038 DIAGNOSIS-CODE-4 1 If DIAGNOSIS-CODE-2 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-2 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-4 CLT038











614 Merged CLT038-0007 RULE-898 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT038 DIAGNOSIS-CODE-4 2 If DIAGNOSIS-CODE-4 is not 8-filled, then DIAGNOSIS-CODE-4 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 CLT029,CLT032,CLT035,CLT038,CLT041











615 No logic changes CLT038-0008 RULE-911 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT038 DIAGNOSIS-CODE-4 2 DIAGNOSIS-CODE-4 must be 8-filled if value for DIAGNOSIS-CODE-3 is 8-filled 2266 Relational edit between DIAGNOSIS-CODE-4 and DIAGNOSIS-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-3), then !fns.hasValue(@val.DIAGNOSIS-CODE-4)' DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4 CLT035,CLT038











616 No logic changes CLT039-0001 RULE-912 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT039 DIAGNOSIS-CODE-FLAG-4 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-4 CLT039











617 No logic changes CLT040-0001 RULE-913 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT040 DIAGNOSIS-POA-FLAG-4 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-4 CLT040











618 Merged CLT041-0001 RULE-914 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT041 DIAGNOSIS-CODE-5 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-5 CLT041











619 Merged CLT041-0002 RULE-914 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT041 DIAGNOSIS-CODE-5 1 If DIAGNOSIS-CODE-2 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-2 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-5 CLT041











620 Merged CLT041-0007 RULE-898 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT041 DIAGNOSIS-CODE-5 2 If DIAGNOSIS-CODE-5 is not 8-filled, then DIAGNOSIS-CODE-5 must <> value for the other instances of DIAGNOSIS-CODE 2145 Duplicate values of DIAGNOSIS-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-3,DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 CLT029,CLT032,CLT035,CLT038,CLT041











621 No logic changes CLT041-0008 RULE-917 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT041 DIAGNOSIS-CODE-5 2 DIAGNOSIS-CODE-5 must be 8-filled if value for DIAGNOSIS-CODE-4 is 8-filled 2267 Relational edit between DIAGNOSIS-CODE-5 and DIAGNOSIS-CODE-4 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-4), then !fns.hasValue(@val.DIAGNOSIS-CODE-5)' DIAGNOSIS-CODE-4,DIAGNOSIS-CODE-5 CLT038,CLT041











622 No logic changes CLT042-0001 RULE-918 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT042 DIAGNOSIS-CODE-FLAG-5 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-5 CLT042











623 No logic changes CLT043-0001 RULE-919 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT043 DIAGNOSIS-POA-FLAG-5 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-5 CLT043











624 Merged CLT044-0001 RULE-920 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT044 ADMISSION-DATE 1 If ADMISSION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD ADMISSION-DATE CLT044











625 Merged CLT044-0002 RULE-920 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT044 ADMISSION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD ADMISSION-DATE CLT044











626 Merged CLT044-0003 RULE-922 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT044 ADMISSION-DATE 2-M
2002
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ADMISSION-DATE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.ADJUDICATION-DATE)' ADMISSION-DATE,ADJUDICATION-DATE CLT044,CLT050











627 Merged CLT044-0004 RULE-923 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT044 ADMISSION-DATE 2 If DISCHARGE-DATE is not (8-filled or 9-filled), then ADMISSION-DATE must be <= DISCHARGE-DATE" 2006 Relational edit between ADMISSION-DATE and DISCHARGE-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.DISCHARGE-DATE) && fns.hasValue(@val.ADMISSION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.DISCHARGE-DATE)' DISCHARGE-DATE,ADMISSION-DATE CLT046,CLT044











628 Logic updated: other CLT044-0006 RULE-924 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT044 ADMISSION-DATE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then ADMISSION-DATE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3001 Relational edit between ADMISSION-DATE and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ADMISSION-DATE), then fns.isLessThanOrEqual(@secondaryRecord.ADMISSION-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ADMISSION-DATE CLT044

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CLT022,CLT017



629 No logic changes CLT045-0001 RULE-925 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT045 ADMISSION-HOUR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: HOUR ADMISSION-HOUR CLT045











630 Merged CLT046-0001 RULE-926 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT046 DISCHARGE-DATE 1 If DISCHARGE-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD DISCHARGE-DATE CLT046











631 Merged CLT046-0002 RULE-926 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT046 DISCHARGE-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD DISCHARGE-DATE CLT046











632 Merged CLT046-0003 RULE-923 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT046 DISCHARGE-DATE 2-M
2006
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.DISCHARGE-DATE) && fns.hasValue(@val.ADMISSION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.DISCHARGE-DATE)' DISCHARGE-DATE,ADMISSION-DATE CLT046,CLT044











633 Logic updated: other CLT046-0004 RULE-929 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT046 DISCHARGE-DATE 2 If DISCHARGE-DATE is not 8-filled, then DISCHARGE-DATE must be <= ADJUDICATION-DATE [CLAIM-HEADER-RECORD-LT] 2025 Relational edit between DISCHARGE-DATE and ADJUDICATION-DATE [CLAIM-HEADER-RECORD-LT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.DISCHARGE-DATE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.DISCHARGE-DATE, @val.ADJUDICATION-DATE)' DISCHARGE-DATE,ADJUDICATION-DATE CLT046,CLT050











634 Logic updated: other CLT046-0007 RULE-930 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT046 DISCHARGE-DATE 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then DISCHARGE-DATE must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3053 Relational edit with DISCHARGE-DATE and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.DISCHARGE-DATE), then fns.isLessThanOrEqual(@secondaryRecord.DISCHARGE-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 DISCHARGE-DATE CLT046

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CLT022,CLT017



635 No logic changes CLT047-0001 RULE-931 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT047 DISCHARGE-HOUR 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: HOUR DISCHARGE-HOUR CLT047











636 Merged CLT048-0001 RULE-932 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT048 BEGINNING-DATE-OF-SERVICE 1 If BEGINNING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE CLT048











637 Merged CLT048-0002 RULE-932 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT048 BEGINNING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE CLT048











638 Merged CLT048-0003 RULE-934 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT048 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2013 Relational edit between BEGINNING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE CLT048 END-OF-TIME-PERIOD CLT010









639 Merged CLT048-0004 RULE-935 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT048 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CLT048,CLT049











640 Logic updated: other CLT048-0005 RULE-936 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT048 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-HEADER-RECORD-LT] 2007 Relational edit between BEGINNING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-HEADER-RECORD-LT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' BEGINNING-DATE-OF-SERVICE,ADJUDICATION-DATE CLT048,CLT050











641 Logic updated: other CLT048-0006 RULE-937 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT048 BEGINNING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then BEGINNING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3002 Relational edit between BEGINNING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 BEGINNING-DATE-OF-SERVICE CLT048

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CLT022,CLT017



642 Merged CLT048-0010 RULE-934 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT048 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE CLT048 END-OF-TIME-PERIOD CLT010









643 Merged CLT049-0001 RULE-939 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT049 ENDING-DATE-OF-SERVICE 1 If ENDING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE CLT049











644 Merged CLT049-0002 RULE-939 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT049 ENDING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE CLT049











645 Merged CLT049-0003 RULE-935 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT049 ENDING-DATE-OF-SERVICE 2-M
2012
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CLT048,CLT049











646 Logic updated: other CLT049-0004 RULE-942 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT049 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-HEADER-RECORD-LT] 2037 Relational edit between ENDING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-HEADER-RECORD-LT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' ENDING-DATE-OF-SERVICE,ADJUDICATION-DATE CLT049,CLT050











647 Logic updated: other CLT049-0005 RULE-943 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT049 ENDING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then ENDING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3005 Relational edit between ENDING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.ENDING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ENDING-DATE-OF-SERVICE CLT049

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CLT022,CLT017



648 Logic updated: other CLT049-0007 RULE-944 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT049 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2036 Relational edit between ENDING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' ENDING-DATE-OF-SERVICE CLT049 END-OF-TIME-PERIOD CLT010









649 Merged CLT050-0001 RULE-945 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT050 ADJUDICATION-DATE 1 If ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CLT050











650 Merged CLT050-0002 RULE-945 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT050 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CLT050











651 Logic updated: other CLT050-0006 RULE-947 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT050 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE CLT050 END-OF-TIME-PERIOD CLT010









652 Merged CLT050-0007 RULE-922 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT050 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be >= ADMISSION-DATE 2002 Relational edit between ADJUDICATION-DATE and ADMISSION-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ADMISSION-DATE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ADMISSION-DATE, @val.ADJUDICATION-DATE)' ADMISSION-DATE,ADJUDICATION-DATE CLT044,CLT050











653 Merged CLT051-0001 RULE-949 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT051 MEDICAID-PAID-DATE 1 If MEDICAID-PAID-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE CLT051











654 Merged CLT051-0002 RULE-949 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT051 MEDICAID-PAID-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE CLT051











655 No logic changes CLT052-0001 RULE-951 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT052 TYPE-OF-CLAIM 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-CLAIM TYPE-OF-CLAIM CLT052











656 No logic changes CLT053-0001 RULE-952 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT053 TYPE-OF-BILL 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.TYPE-OF-BILL), then fns.isValidTypeOfBill(@val.TYPE-OF-BILL)' TYPE-OF-BILL CLT053











657 No logic changes CLT054-0001 RULE-953 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT054 CLAIM-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-STATUS CLT054











658 No logic changes CLT055-0001 RULE-954 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT055 CLAIM-STATUS-CATEGORY 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS-CATEGORY CLAIM-STATUS-CATEGORY CLT055











659 No logic changes CLT056-0001 RULE-955 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT056 SOURCE-LOCATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: SOURCE-LOCATION SOURCE-LOCATION CLT056











660 Logic updated: string matching CLT057-0001 RULE-956 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT057 CHECK-NUM 1 If CHECK-NUM is populated, it must contains valid characters. 120 Field contains invalid characters - CHECK-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.CHECK-NUM), then fns.matches(@val.CHECK-NUM, "^[^|*]*$")' CHECK-NUM CLT057











661 Merged CLT058-0001 RULE-957 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT058 CHECK-EFF-DATE 1 If CHECK-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE CLT058











662 Merged CLT058-0002 RULE-957 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT058 CHECK-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE CLT058











663 No logic changes CLT059-0001 RULE-959 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT059 CLAIM-PYMT-REM-CODE-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-1 CLT059











664 Merged CLT059-0002 RULE-960 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT059 CLAIM-PYMT-REM-CODE-1 2 If CLAIM-PYMT-REM-CODE-1 is not 8-filled, then CLAIM-PYMT-REM-CODE-1 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLT059,CLT060,CLT061,CLT062











665 No logic changes CLT060-0001 RULE-961 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT060 CLAIM-PYMT-REM-CODE-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-2 CLT060











666 Merged CLT060-0002 RULE-960 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT060 CLAIM-PYMT-REM-CODE-2 2 If CLAIM-PYMT-REM-CODE-2 is not 8-filled, then CLAIM-PYMT-REM-CODE-2 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLT059,CLT060,CLT061,CLT062











667 No logic changes CLT060-0003 RULE-963 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT060 CLAIM-PYMT-REM-CODE-2 2 CLAIM-PYMT-REM-CODE-2 must be 8-filled if value for CLAIM-PYMT-REM-CODE-1 is 8-filled 2243 Relational edit between CLAIM-PYMT-REM-CODE-2 and CLAIM-PYMT-REM-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-1), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2)' CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2 CLT059,CLT060











668 No logic changes CLT061-0001 RULE-964 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT061 CLAIM-PYMT-REM-CODE-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-3 CLT061











669 Merged CLT061-0002 RULE-960 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT061 CLAIM-PYMT-REM-CODE-3 2 If CLAIM-PYMT-REM-CODE-3 is not 8-filled, then CLAIM-PYMT-REM-CODE-3 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLT059,CLT060,CLT061,CLT062











670 No logic changes CLT061-0003 RULE-966 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT061 CLAIM-PYMT-REM-CODE-3 2 CLAIM-PYMT-REM-CODE-3 must be 8-filled if value for CLAIM-PYMT-REM-CODE-2 is 8-filled 2244 Relational edit between CLAIM-PYMT-REM-CODE-3 and CLAIM-PYMT-REM-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3)' CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3 CLT060,CLT061











671 No logic changes CLT062-0001 RULE-967 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT062 CLAIM-PYMT-REM-CODE-4 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-4 CLT062











672 Merged CLT062-0002 RULE-960 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT062 CLAIM-PYMT-REM-CODE-4 2 If CLAIM-PYMT-REM-CODE-4 is not 8-filled, then CLAIM-PYMT-REM-CODE-4 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLT059,CLT060,CLT061,CLT062











673 No logic changes CLT062-0003 RULE-969 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT062 CLAIM-PYMT-REM-CODE-4 2 CLAIM-PYMT-REM-CODE-4 must be 8-filled if value for CLAIM-PYMT-REM-CODE-3 is 8-filled 2245 Relational edit between CLAIM-PYMT-REM-CODE-4 and CLAIM-PYMT-REM-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-4)' CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLT061,CLT062











674 No logic changes CLT063-0001 RULE-970 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT063 TOT-BILLED-AMT 1 If TOT-BILLED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-BILLED-AMT CLT063











675 No logic changes CLT063-0003 RULE-971 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT063 TOT-BILLED-AMT 2 If TYPE-OF-CLAIM = "4", "D", or "X", then TOT-BILLED-AMT must = 0 2426 Relational edit between TOT-BILLED-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "4", "D", "X"), then fns.isEqual(@val.TOT-BILLED-AMT, "0.00")' TYPE-OF-CLAIM,TOT-BILLED-AMT CLT052,CLT063











676 No logic changes CLT064-0001 RULE-972 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT064 TOT-ALLOWED-AMT 1 If TOT-ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-ALLOWED-AMT CLT064











677 Merged CLT064-0002 RULE-973 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT064 TOT-ALLOWED-AMT 2 TOT-ALLOWED-AMT must = the sum of the ALLOWED-AMT at each claim line level 2424 Relational edit between TOT-ALLOWED-AMT and detail ALLOWED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'fns.isDollarSumEqual(@primaryRecord.TOT-ALLOWED-AMT, @secondaryRecords.ALLOWED-AMT)' TOT-ALLOWED-AMT CLT064 ALLOWED-AMT CLT205

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



678 Merged CLT064-0003 RULE-973 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT064 TOT-ALLOWED-AMT 2 TOT-ALLOWED-AMT must = the sum of ALLOWED-AMT at each claim line level, where SUBMITTING-STATE, ICN-ORIG, and ICN-ADJ match 2125 Relational edit between TOT-ALLOWED-AMT and ALLOWED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'fns.isDollarSumEqual(@primaryRecord.TOT-ALLOWED-AMT, @secondaryRecords.ALLOWED-AMT)' TOT-ALLOWED-AMT CLT064 ALLOWED-AMT CLT205

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



679 No logic changes CLT065-0001 RULE-975 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT065 TOT-MEDICAID-PAID-AMT 1 If TOT-MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICAID-PAID-AMT CLT065











680 No logic changes CLT066-0001 RULE-976 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT066 TOT-COPAY-AMT 1 If TOT-COPAY-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-COPAY-AMT CLT066











681 No logic changes CLT067-0001 RULE-977 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT067 TOT-MEDICARE-DEDUCTIBLE-AMT 1 If TOT-MEDICARE-DEDUCTIBLE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-DEDUCTIBLE-AMT CLT067











682 Logic updated: other CLT067-0002 RULE-978 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT067 TOT-MEDICARE-DEDUCTIBLE-AMT 2 TOT-MEDICARE-DEDUCIBLE-AMT must be <=TOT-BILLED-AMT 2127 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT) && fns.hasValue(@val.TOT-BILLED-AMT), then fns.isLessThanOrEqual(@val.TOT-MEDICARE-DEDUCTIBLE-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-BILLED-AMT CLT067,CLT063











683 Merged CLT067-0003 RULE-983 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT067 TOT-MEDICARE-DEDUCTIBLE-AMT 2 If TOT-MEDICARE-COINS-AMT is 8-filled, then TOT-MEDICARE-DEDUCIBLE-AMT must be 8-filled 2431 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and TOT-MEDICARE-COINS-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if and only if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-MEDICARE-COINS-AMT CLT067,CLT068











684 No logic changes CLT068-0001 RULE-980 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT068 TOT-MEDICARE-COINS-AMT 1 If TOT-MEDICARE-COINS-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-COINS-AMT CLT068











685 No logic changes CLT068-0002 RULE-981 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT068 TOT-MEDICARE-COINS-AMT 2 If TYPE-OF-CLAIM = "3", "C", "W", then TOT-MEDICARE-COINS-AMT must be 8-filled 2429 Relational edit between TOT-MEDICARE-COINS-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then !fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TYPE-OF-CLAIM,TOT-MEDICARE-COINS-AMT CLT052,CLT068











686 Logic updated: other CLT068-0003 RULE-982 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT068 TOT-MEDICARE-COINS-AMT 2 TOT-MEDICARE-COINS-AMT must be < TOT-BILLED-AMT 2126 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-BILLED-AMT), then fns.isLessThan(@val.TOT-MEDICARE-COINS-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-COINS-AMT,TOT-BILLED-AMT CLT068,CLT063











687 Merged CLT068-0004 RULE-983 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT068 TOT-MEDICARE-COINS-AMT 2 If TOT-MEDICARE-DEDUCTIBLE-AMT is 8-filled, then TOT-MEDICARE-COINS-AMT must be 8-filled. 2428 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-MEDICARE-DEDUCTIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if and only if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-MEDICARE-COINS-AMT CLT067,CLT068











688 No logic changes CLT068-0005 RULE-984 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT068 TOT-MEDICARE-COINS-AMT 2 If MEDICARE-COMB-DED-IND = "1", then TOT-MEDICARE-COINS-AMT must = 0 2427 Relational edit between TOT-MEDICARE-COINS-AMT and MEDICARE-COMB-DED-IND 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqual(@val.MEDICARE-COMB-DED-IND, "1"), then fns.isEqual(@val.TOT-MEDICARE-COINS-AMT, "0.00")' MEDICARE-COMB-DED-IND,TOT-MEDICARE-COINS-AMT CLT078,CLT068











689 No logic changes CLT069-0001 RULE-985 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT069 TOT-TPL-AMT 1 If TOT-TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-TPL-AMT CLT069











690 Logic updated: other CLT069-0002 RULE-986 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT069 TOT-TPL-AMT 2 The absolute value of TOT-TPL-AMT must be <= the absolute value of (TOT-BILLED-AMT minus TOT-MEDICARE-COINS-AMT plus TOT-MEDICARE-DEDUCIBLE-AMT) 2432 Relational edit between TOT-TPL-AMT, TOT-BILLED-AMT, MEDICARE-COINS-AMT, and TOT-MEDICARE-DEDUCIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.TOT-TPL-AMT) && fns.hasValue(@val.TOT-BILLED-AMT) && fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.isLessThanOrEqual(@val.TOT-TPL-AMT, fns.remainingLiability(@val.TOT-BILLED-AMT, @val.TOT-MEDICARE-COINS-AMT, @val.TOT-MEDICARE-DEDUCTIBLE-AMT))' TOT-TPL-AMT,TOT-BILLED-AMT,TOT-MEDICARE-COINS-AMT,TOT-MEDICARE-DEDUCTIBLE-AMT CLT069,CLT063,CLT068,CLT067











691 No logic changes CLT070-0001 RULE-987 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT070 TOT-OTHER-INSURANCE-AMT 1 If TOT-OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-OTHER-INSURANCE-AMT CLT070











692 No logic changes CLT071-0001 RULE-988 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT071 OTHER-INSURANCE-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-INSURANCE-IND OTHER-INSURANCE-IND CLT071











693 No logic changes CLT072-0001 RULE-989 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT072 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION CLT072











694 No logic changes CLT073-0001 RULE-990 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT073 SERVICE-TRACKING-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: SERVICE-TRACKING-TYPE SERVICE-TRACKING-TYPE CLT073











695 No logic changes CLT074-0001 RULE-991 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT074 SERVICE-TRACKING-PAYMENT-AMT 1 If SERVICE-TRACKING-PAYMENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 SERVICE-TRACKING-PAYMENT-AMT CLT074











696 No logic changes CLT074-0004 RULE-992 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT074 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE <> "00" AND (TOT-MEDICAID-PAID-AMT = 0), then SERVICE-TRACKING-PAYMENT-AMT must be > 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isEqual(@val.TOT-MEDICAID-PAID-AMT, "0.00"), then fns.isGreaterThanZero(@val.SERVICE-TRACKING-PAYMENT-AMT)' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT CLT073,CLT065,CLT074











697 No logic changes CLT074-0006 RULE-993 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT074 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE = "00" AND (TOT-MEDICAID-PAID-AMT > 0), then SERVICE-TRACKING-PAYMENT-AMT must = 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isGreaterThanZero(@val.TOT-MEDICAID-PAID-AMT), then fns.isEqual(@val.SERVICE-TRACKING-PAYMENT-AMT, "0.00")' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT CLT073,CLT065,CLT074











698 No logic changes CLT075-0001 RULE-994 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT075 FIXED-PAYMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: FIXED-PAYMENT-IND FIXED-PAYMENT-IND CLT075











699 No logic changes CLT076-0001 RULE-995 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT076 FUNDING-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-CODE FUNDING-CODE CLT076











700 No logic changes CLT077-0001 RULE-996 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT077 FUNDING-SOURCE-NONFEDERAL-SHARE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-SOURCE-NONFEDERAL-SHARE FUNDING-SOURCE-NONFEDERAL-SHARE CLT077











701 No logic changes CLT078-0001 RULE-997 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT078 MEDICARE-COMB-DED-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-COMB-DED-IND MEDICARE-COMB-DED-IND CLT078











702 No logic changes CLT078-0004 RULE-998 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT078 MEDICARE-COMB-DED-IND 2 If CROSSOVER-INDICATOR = "0" or TYPE-OF-CLAIM = "3", "C", or "W", then MEDICARE-COMB-DED-IND must = 0 2328 Relational edit between MEDICARE-COMB-DED-IND, CROSSOVER-INDICATOR, and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "0") || fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then fns.isEqual(@val.MEDICARE-COMB-DED-IND, "0")' CROSSOVER-INDICATOR,TYPE-OF-CLAIM,MEDICARE-COMB-DED-IND CLT023,CLT052,CLT078











703 No logic changes CLT079-0001 RULE-999 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT079 PROGRAM-TYPE 1 Valueis not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROGRAM-TYPE PROGRAM-TYPE CLT079











704 No logic changes CLT079-0002 RULE-1000 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT079 PROGRAM-TYPE 2 If PROGRAM-TYPE = "07", then WAIVER-TYPE must = "06" through "20" 2388 Relational edit between PROGRAM-TYPE and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqual(@val.PROGRAM-TYPE, "07"), then fns.isEqualToAny(@val.WAIVER-TYPE, "06", "07", "08", "09", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20")' PROGRAM-TYPE,WAIVER-TYPE CLT079,CLT128











705 No logic changes CLT079-0004 RULE-1001 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT079 PROGRAM-TYPE 3 If PROGRAM-TYPE = "13", then STATE-PLAN-OPTION-TYPE [ELIGIBLE] must = "02" where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] 3047 Relational edit between PROGRAM TYPE and STATE-PLAN-OPTION-TYPE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) STATE-PLAN-OPTION-PARTICIPATION ELG00011 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.isEqual(@secondaryRecord.PROGRAM-TYPE, "13"), then fns.isEqual(@primaryRecord.STATE-PLAN-OPTION-TYPE, "02")' STATE-PLAN-OPTION-TYPE ELG163 PROGRAM-TYPE CLT079

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG162,ELG160 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CLT022,CLT017



706 Logic updated: string matching CLT080-0001 RULE-1002 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT080 PLAN-ID-NUMBER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PLAN-ID-NUMBER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.PLAN-ID-NUMBER), then fns.matches(@val.PLAN-ID-NUMBER, "^[^|*]*$")' PLAN-ID-NUMBER CLT080











707 No logic changes CLT080-0003 RULE-1003 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT080 PLAN-ID-NUMBER 2 If TYPE-OF-CLAIM <> "3", "C" or "W", then PLAN-ID-NUMBER must be 8-filled 2363 Relational edit between PLAN-ID-NUM and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if !fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then !fns.hasValue(@val.PLAN-ID-NUMBER)' TYPE-OF-CLAIM,PLAN-ID-NUMBER CLT052,CLT080











708 No logic changes CLT080-0004 RULE-1004 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT080 PLAN-ID-NUMBER 2 If TYPE-OF-SERVICE = "119", "120", OR "122", then PLAN-ID-NUM must = BILLING-PROV-NUM 2364 Relational edit between PLAN-ID-NUM, BILLING-PROV-NUM, and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "122"), then fns.isEqual(@primaryRecord.PLAN-ID-NUMBER, @primaryRecord.BILLING-PROV-NUM)' PLAN-ID-NUMBER,BILLING-PROV-NUM CLT080,CLT130 TYPE-OF-SERVICE CLT211

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



709 Logic updated: string matching CLT081-0001 RULE-1005 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT081 NATIONAL-HEALTH-CARE-ENTITY-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-ID, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-ID CLT081











710 No logic changes CLT081-0003 RULE-1006 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT081 NATIONAL-HEALTH-CARE-ENTITY-ID 2 If START-OF-TIME-PERIOD >= 20151105, then NATIONAL-HEALTH-CARE-ENTITY-ID must not be (8-filled or 9-filled) 2332 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 FILE-HEADER-RECORD-LT CLT00001

'if fns.isGreaterThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, "2015-11-05"), then fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID CLT081 START-OF-TIME-PERIOD CLT009









711 No logic changes CLT081-0004 RULE-1007 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT081 NATIONAL-HEALTH-CARE-ENTITY-ID 3 If TYPE-OF-CLAIM = "C", "3", or "W", then NATIONAL-HEALTH-CARE-ENTITY-ID [CLAIM-HEADER-RECORD-LT-CLT00002] must = NATIONAL-HEALTH-CARE-ENTITY-ID [MANAGED-CARE-PARTICIPATION-ELG00014], where SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] and MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014] 3027 Edit that NATIONAL-HEALTH-CARE-ENTITY-ID matches value in MANAGED-CARE-PARTICIPATION-ELG00014 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) MANAGED-CARE-PARTICIPATION ELG00014 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.isEqual(@secondaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID, @primaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID ELG194 TYPE-OF-CLAIM,NATIONAL-HEALTH-CARE-ENTITY-ID CLT052,CLT081

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG189,ELG191 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT017,CLT022



712 No logic changes CLT082-0001 RULE-1008 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT082 PAYMENT-LEVEL-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PAYMENT-LEVEL-IND PAYMENT-LEVEL-IND CLT082











713 No logic changes CLT083-0001 RULE-1009 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT083 MEDICARE-REIM-TYPE 1 Value must be a valid value 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-REIM-TYPE MEDICARE-REIM-TYPE CLT083











714 No logic changes CLT084-0001 RULE-1010 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT084 NON-COV-DAYS 1 If NON-COV-DAYS is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: S9(5) NON-COV-DAYS CLT084











715 Logic updated: other CLT084-0002 RULE-1011 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT084 NON-COV-DAYS 2 Sum (NON-COVERED-DAYS plus MEDICAID-COV-INPATIENT-DAYS plus 1) must be <= (BEGINNING-DATE-OF-SERVICE minus ENDING-DATE-OF-SERVICE (in days)) 2335 Relational edit between NON-COV-DAYS, MEDICAID-COV-INPATIENT-DAYS, and ADMISSION-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.NON-COV-DAYS) && fns.hasValue(@val.MEDICAID-COV-INPATIENT-DAYS) && fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isSumOfDaysLessThanOrEqualToLengthOfStay(@val.NON-COV-DAYS, @val.MEDICAID-COV-INPATIENT-DAYS, @val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' NON-COV-DAYS,MEDICAID-COV-INPATIENT-DAYS,BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CLT084,CLT086,CLT048,CLT049











716 No logic changes CLT085-0001 RULE-1012 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT085 NON-COV-CHARGES 1 If NON-COV-CHARGES is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 NON-COV-CHARGES CLT085











717 No logic changes CLT086-0001 RULE-1013 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT086 MEDICAID-COV-INPATIENT-DAYS 1 If MEDICAID-COV-INPATIENT-DAYS not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: S9(5) MEDICAID-COV-INPATIENT-DAYS CLT086











718 Logic updated: other CLT086-0003 RULE-1014 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT086 MEDICAID-COV-INPATIENT-DAYS 2 MEDICAID-COV-INPATIENT-DAYS must not be > [(DISCHARGE-DATE - ADMISSION-DATE + 1 (in days)) x 2]. 2327 Relational edit between MEDICAID-COV-INPATIENT-DAYS, DISCHARGE-DATE, and ADMISSION-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.MEDICAID-COV-INPATIENT-DAYS) && fns.hasValue(@val.ADMISSION-DATE) && fns.hasValue(@val.DISCHARGE-DATE), then fns.isValueLessThanOrEqualToTwoTimesStayDuration(@val.MEDICAID-COV-INPATIENT-DAYS, @val.ADMISSION-DATE, @val.DISCHARGE-DATE)' MEDICAID-COV-INPATIENT-DAYS,ADMISSION-DATE,DISCHARGE-DATE CLT086,CLT044,CLT046











719 Retired: required value checks CLT087-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT087 CLAIM-LINE-COUNT 1 If CLAIM-LINE-COUNT =0 113 Required data element has not been reported.

























720 Logic updated: other CLT087-0003 RULE-1016 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT087 CLAIM-LINE-COUNT 2 CLAIM-LINE-COUNT must = total number of lines in the claim 2445 Value does not equal the total number of lines in the claim 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.hasValue(@primaryRecord.CLAIM-LINE-COUNT), then fns.isValueEqualToNumberOfRecords(@primaryRecord.CLAIM-LINE-COUNT, @secondaryRecords.LINE-NUM-ORIG)' CLAIM-LINE-COUNT CLT087 LINE-NUM-ORIG CLT190

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



721 No logic changes CLT090-0001 RULE-1017 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT090 FORCED-CLAIM-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: FORCED-CLAIM-IND FORCED-CLAIM-IND CLT090











722 No logic changes CLT091-0001 RULE-1018 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT091 HEALTH-CARE-ACQUIRED-CONDITION-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-CARE-ACQUIRED-CONDITION-IND HEALTH-CARE-ACQUIRED-CONDITION-IND CLT091











723 No logic changes CLT092-0001 RULE-1019 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT092 OCCURRENCE-CODE-01 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-01 CLT092











724 No logic changes CLT093-0001 RULE-1020 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT093 OCCURRENCE-CODE-02 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-02 CLT093











725 No logic changes CLT094-0001 RULE-1021 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT094 OCCURRENCE-CODE-03 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-03 CLT094











726 No logic changes CLT095-0001 RULE-1022 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT095 OCCURRENCE-CODE-04 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-04 CLT095











727 No logic changes CLT096-0001 RULE-1023 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT096 OCCURRENCE-CODE-05 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-05 CLT096











728 No logic changes CLT097-0001 RULE-1024 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT097 OCCURRENCE-CODE-06 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-06 CLT097











729 No logic changes CLT098-0001 RULE-1025 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT098 OCCURRENCE-CODE-07 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-07 CLT098











730 No logic changes CLT099-0001 RULE-1026 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT099 OCCURRENCE-CODE-08 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-08 CLT099











731 No logic changes CLT100-0001 RULE-1027 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT100 OCCURRENCE-CODE-09 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-09 CLT100











732 No logic changes CLT101-0001 RULE-1028 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT101 OCCURRENCE-CODE-10 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-10 CLT101











733 Merged CLT102-0001 RULE-1029 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT102 OCCURRENCE-CODE-EFF-DATE-01 1 If OCCURRENCE-CODE-EFF-DATE-01 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-01 CLT102











734 Merged CLT102-0002 RULE-1029 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT102 OCCURRENCE-CODE-EFF-DATE-01 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-01 CLT102











735 No logic changes CLT102-0003 RULE-1031 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT102 OCCURRENCE-CODE-EFF-DATE-01 2 If OCCURRENCE-CODE-01 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-01 must not be 8-filled 2337 Relational edit between OCCURRENCE-CODE-01 and OCCURRENCE-CODE-EFF-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-01), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01)' OCCURRENCE-CODE-01,OCCURRENCE-CODE-EFF-DATE-01 CLT092,CLT102











736 Merged CLT102-0005 RULE-1032 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT102 OCCURRENCE-CODE-EFF-DATE-01 2 OCCURRENCE-CODE-EFF-DATE-01 must be <= OCCURRENCE-CODE-END-DATE-01 2069 Relational edit between OCCURRENCE-CODE-EFF-DATE-01 and OCCURRENCE-CODE-END-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-01, @val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-EFF-DATE-01,OCCURRENCE-CODE-END-DATE-01 CLT102,CLT112











737 Merged CLT103-0001 RULE-1033 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT103 OCCURRENCE-CODE-EFF-DATE-02 1 If OCCURRENCE-CODE-EFF-DATE-02 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-02 CLT103











738 Merged CLT103-0002 RULE-1033 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT103 OCCURRENCE-CODE-EFF-DATE-02 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-02 CLT103











739 No logic changes CLT103-0003 RULE-1035 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT103 OCCURRENCE-CODE-EFF-DATE-02 2 If OCCURRENCE-CODE-02 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-02 must not be 8-filled 2339 Relational edit between OCCURRENCE-CODE-02 and OCCURRENCE-CODE-EFF-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-02), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-02)' OCCURRENCE-CODE-02,OCCURRENCE-CODE-EFF-DATE-02 CLT093,CLT103











740 Logic updated: other CLT103-0005 RULE-1036 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT103 OCCURRENCE-CODE-EFF-DATE-02 2 OCCURRENCE-CODE-EFF-DATE-02 must be <= OCCURRENCE-CODE-END-DATE-02 2070 Relational edit between OCCURRENCE-CODE-EFF-DATE-02 and OCCURRENCE-CODE-END-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-02) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-02), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-02, @val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-EFF-DATE-02,OCCURRENCE-CODE-END-DATE-02 CLT103,CLT113











741 Merged CLT104-0001 RULE-1037 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT104 OCCURRENCE-CODE-EFF-DATE-03 1 If OCCURRENCE-CODE-EFF-DATE-03 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-03 CLT104











742 Merged CLT104-0002 RULE-1037 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT104 OCCURRENCE-CODE-EFF-DATE-03 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-03 CLT104











743 No logic changes CLT104-0003 RULE-1039 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT104 OCCURRENCE-CODE-EFF-DATE-03 2 If OCCURRENCE-CODE-03 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-03 must not be 8-filled 2341 Relational edit between OCCURRENCE-CODE-03 and OCCURRENCE-CODE-EFF-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-03), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03)' OCCURRENCE-CODE-03,OCCURRENCE-CODE-EFF-DATE-03 CLT094,CLT104











744 Merged CLT104-0005 RULE-1040 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT104 OCCURRENCE-CODE-EFF-DATE-03 2 OCCURRENCE-CODE-EFF-DATE-03 must be <= OCCURRENCE-CODE-END-DATE-03 2071 Relational edit between OCCURRENCE-CODE-EFF-DATE-03 and OCCURRENCE-CODE-END-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-03, @val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-EFF-DATE-03,OCCURRENCE-CODE-END-DATE-03 CLT104,CLT114











745 Merged CLT105-0001 RULE-1041 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT105 OCCURRENCE-CODE-EFF-DATE-04 1 If OCCURRENCE-CODE-EFF-DATE-04 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-04 CLT105











746 Merged CLT105-0002 RULE-1041 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT105 OCCURRENCE-CODE-EFF-DATE-04 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-04 CLT105











747 No logic changes CLT105-0003 RULE-1043 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT105 OCCURRENCE-CODE-EFF-DATE-04 2 If OCCURRENCE-CODE-04 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-04 must not be 8-filled 2343 Relational edit between OCCURRENCE-CODE-04 and OCCURRENCE-CODE-EFF-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-04), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04)' OCCURRENCE-CODE-04,OCCURRENCE-CODE-EFF-DATE-04 CLT095,CLT105











748 Merged CLT105-0005 RULE-1044 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT105 OCCURRENCE-CODE-EFF-DATE-04 2 OCCURRENCE-CODE-EFF-DATE-04 must be <= OCCURRENCE-CODE-END-DATE-04 2072 Relational edit between OCCURRENCE-CODE-EFF-DATE-04 and OCCURRENCE-CODE-END-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-04, @val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-EFF-DATE-04,OCCURRENCE-CODE-END-DATE-04 CLT105,CLT115











749 Merged CLT106-0001 RULE-1045 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT106 OCCURRENCE-CODE-EFF-DATE-05 1 If OCCURRENCE-CODE-EFF-DATE-05 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-05 CLT106











750 Merged CLT106-0002 RULE-1045 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT106 OCCURRENCE-CODE-EFF-DATE-05 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-05 CLT106











751 No logic changes CLT106-0003 RULE-1047 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT106 OCCURRENCE-CODE-EFF-DATE-05 2 If OCCURRENCE-CODE-05 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-05 must not be 8-filled 2345 Relational edit between OCCURRENCE-CODE-05 and OCCURRENCE-CODE-EFF-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-05), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05)' OCCURRENCE-CODE-05,OCCURRENCE-CODE-EFF-DATE-05 CLT096,CLT106











752 Merged CLT106-0005 RULE-1048 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT106 OCCURRENCE-CODE-EFF-DATE-05 2 OCCURRENCE-CODE-EFF-DATE-05 must be <= OCCURRENCE-CODE-END-DATE-05 2073 Relational edit between OCCURRENCE-CODE-EFF-DATE-05 and OCCURRENCE-CODE-END-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-05, @val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-EFF-DATE-05,OCCURRENCE-CODE-END-DATE-05 CLT106,CLT116











753 Merged CLT107-0001 RULE-1049 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT107 OCCURRENCE-CODE-EFF-DATE-06 1 If OCCURRENCE-CODE-EFF-DATE-06 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-06 CLT107











754 Merged CLT107-0002 RULE-1049 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT107 OCCURRENCE-CODE-EFF-DATE-06 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-06 CLT107











755 No logic changes CLT107-0003 RULE-1051 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT107 OCCURRENCE-CODE-EFF-DATE-06 2 If OCCURRENCE-CODE-06 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-06 must not be 8-filled 2347 Relational edit between OCCURRENCE-CODE-06 and OCCURRENCE-CODE-EFF-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-06), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06)' OCCURRENCE-CODE-06,OCCURRENCE-CODE-EFF-DATE-06 CLT097,CLT107











756 Merged CLT107-0005 RULE-1052 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT107 OCCURRENCE-CODE-EFF-DATE-06 2 OCCURRENCE-CODE-EFF-DATE-06 must be <= OCCURRENCE-CODE-END-DATE-06 2074 Relational edit between OCCURRENCE-CODE-EFF-DATE-06 and OCCURRENCE-CODE-END-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-06, @val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-EFF-DATE-06,OCCURRENCE-CODE-END-DATE-06 CLT107,CLT117











757 Merged CLT108-0001 RULE-1053 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT108 OCCURRENCE-CODE-EFF-DATE-07 1 If OCCURRENCE-CODE-EFF-DATE-07 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-07 CLT108











758 Merged CLT108-0002 RULE-1053 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT108 OCCURRENCE-CODE-EFF-DATE-07 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-07 CLT108











759 No logic changes CLT108-0003 RULE-1055 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT108 OCCURRENCE-CODE-EFF-DATE-07 2 If OCCURRENCE-CODE-07 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-07 must not be 8-filled 2349 Relational edit between OCCURRENCE-CODE-07 and OCCURRENCE-CODE-EFF-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-07), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07)' OCCURRENCE-CODE-07,OCCURRENCE-CODE-EFF-DATE-07 CLT098,CLT108











760 Merged CLT108-0005 RULE-1056 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT108 OCCURRENCE-CODE-EFF-DATE-07 2 OCCURRENCE-CODE-EFF-DATE-07 must be <= OCCURRENCE-CODE-END-DATE-07 2075 Relational edit between OCCURRENCE-CODE-EFF-DATE-07 and OCCURRENCE-CODE-END-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-07, @val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-EFF-DATE-07,OCCURRENCE-CODE-END-DATE-07 CLT108,CLT118











761 Merged CLT109-0001 RULE-1057 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT109 OCCURRENCE-CODE-EFF-DATE-08 1 If OCCURRENCE-CODE-EFF-DATE-08 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-08 CLT109











762 Merged CLT109-0002 RULE-1057 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT109 OCCURRENCE-CODE-EFF-DATE-08 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-08 CLT109











763 No logic changes CLT109-0003 RULE-1059 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT109 OCCURRENCE-CODE-EFF-DATE-08 2 If OCCURRENCE-CODE-08 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-08 must not be 8-filled 2351 Relational edit between OCCURRENCE-CODE-08 and OCCURRENCE-CODE-EFF-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-08), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08)' OCCURRENCE-CODE-08,OCCURRENCE-CODE-EFF-DATE-08 CLT099,CLT109











764 Merged CLT109-0005 RULE-1060 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT109 OCCURRENCE-CODE-EFF-DATE-08 2 OCCURRENCE-CODE-EFF-DATE-08 must be <= OCCURRENCE-CODE-END-DATE-08 2076 Relational edit between OCCURRENCE-CODE-EFF-DATE-08 and OCCURRENCE-CODE-END-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-08, @val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-EFF-DATE-08,OCCURRENCE-CODE-END-DATE-08 CLT109,CLT119











765 Merged CLT110-0001 RULE-1061 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT110 OCCURRENCE-CODE-EFF-DATE-09 1 If OCCURRENCE-CODE-EFF-DATE-09 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-09 CLT110











766 Merged CLT110-0002 RULE-1061 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT110 OCCURRENCE-CODE-EFF-DATE-09 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-09 CLT110











767 No logic changes CLT110-0003 RULE-1063 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT110 OCCURRENCE-CODE-EFF-DATE-09 2 If OCCURRENCE-CODE-09 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-09 must not be 8-filled 2353 Relational edit between OCCURRENCE-CODE-09 and OCCURRENCE-CODE-EFF-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-09), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09)' OCCURRENCE-CODE-09,OCCURRENCE-CODE-EFF-DATE-09 CLT100,CLT110











768 Merged CLT110-0005 RULE-1064 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT110 OCCURRENCE-CODE-EFF-DATE-09 2 OCCURRENCE-CODE-EFF-DATE-09 must be <= OCCURRENCE-CODE-END-DATE-09 2077 Relational edit between OCCURRENCE-CODE-EFF-DATE-09 and OCCURRENCE-CODE-END-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-09, @val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-EFF-DATE-09,OCCURRENCE-CODE-END-DATE-09 CLT110,CLT120











769 Merged CLT111-0001 RULE-1065 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT111 OCCURRENCE-CODE-EFF-DATE-10 1 If OCCURRENCE-CODE-EFF-DATE-10 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-10 CLT111











770 Merged CLT111-0002 RULE-1065 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT111 OCCURRENCE-CODE-EFF-DATE-10 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-10 CLT111











771 No logic changes CLT111-0003 RULE-1067 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT111 OCCURRENCE-CODE-EFF-DATE-10 2 If OCCURRENCE-CODE-10 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-10 must not be 8-filled 2355 Relational edit between OCCURRENCE-CODE-10 and OCCURRENCE-CODE-EFF-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-10), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-10)' OCCURRENCE-CODE-10,OCCURRENCE-CODE-EFF-DATE-10 CLT101,CLT111











772 Merged CLT111-0005 RULE-1068 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT111 OCCURRENCE-CODE-EFF-DATE-10 2 OCCURRENCE-CODE-EFF-DATE-10 must be <= OCCURRENCE-CODE-END-DATE-10 2078 Relational edit between OCCURRENCE-CODE-EFF-DATE-10 and OCCURRENCE-CODE-END-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-10) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-10), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-10, @val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-EFF-DATE-10,OCCURRENCE-CODE-END-DATE-10 CLT111,CLT121











773 Merged CLT112-0001 RULE-1069 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT112 OCCURRENCE-CODE-END-DATE-01 1 If OCCURRENCE-CODE-END-DATE-01 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-01 CLT112











774 Merged CLT112-0002 RULE-1069 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT112 OCCURRENCE-CODE-END-DATE-01 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-01 CLT112











775 No logic changes CLT112-0004 RULE-1071 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT112 OCCURRENCE-CODE-END-DATE-01 2 If OCCURRENCE-CODE-01 is not 8-filled, then OCCURRENCE-CODE-END-DATE-01 must not be 8-filled 2338 Relational edit between OCCURRENCE-CODE-01 and OCCURRENCE-CODE-END-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-01), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-01,OCCURRENCE-CODE-END-DATE-01 CLT092,CLT112











776 Merged CLT112-0006 RULE-1032 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT112 OCCURRENCE-CODE-END-DATE-01 2-M
2069
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-01, @val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-EFF-DATE-01,OCCURRENCE-CODE-END-DATE-01 CLT102,CLT112











777 Merged CLT113-0001 RULE-1073 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT113 OCCURRENCE-CODE-END-DATE-02 1 If OCCURRENCE-CODE-END-DATE-02 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-02 CLT113











778 Merged CLT113-0002 RULE-1073 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT113 OCCURRENCE-CODE-END-DATE-02 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-02 CLT113











779 Merged CLT113-0004 RULE-1075 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT113 OCCURRENCE-CODE-END-DATE-02 2 If OCCURRENCE-CODE-02 is not 8-filled, then OCCURRENCE-CODE-END-DATE-02 must not be 8-filled 2340 Relational edit between OCCURRENCE-CODE-02 and OCCURRENCE-CODE-END-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-02), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-02,OCCURRENCE-CODE-END-DATE-02 CLT093,CLT113











780 Merged CLT113-0006 RULE-1075 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT113 OCCURRENCE-CODE-END-DATE-02 2-M
2070
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-02), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-02,OCCURRENCE-CODE-END-DATE-02 CLT093,CLT113











781 Merged CLT114-0001 RULE-1077 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT114 OCCURRENCE-CODE-END-DATE-03 1 If OCCURRENCE-CODE-END-DATE-03 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-03 CLT114











782 Merged CLT114-0002 RULE-1077 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT114 OCCURRENCE-CODE-END-DATE-03 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-03 CLT114











783 No logic changes CLT114-0004 RULE-1079 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT114 OCCURRENCE-CODE-END-DATE-03 2 If OCCURRENCE-CODE-03 is not 8-filled, then OCCURRENCE-CODE-END-DATE-03 must not be 8-filled 2342 Relational edit between OCCURRENCE-CODE-03 and OCCURRENCE-CODE-END-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-03), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-03,OCCURRENCE-CODE-END-DATE-03 CLT094,CLT114











784 Merged CLT114-0006 RULE-1040 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT114 OCCURRENCE-CODE-END-DATE-03 2-M
2071
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-03, @val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-EFF-DATE-03,OCCURRENCE-CODE-END-DATE-03 CLT104,CLT114











785 Merged CLT115-0001 RULE-1081 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT115 OCCURRENCE-CODE-END-DATE-04 1 If OCCURRENCE-CODE-END-DATE-04 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-04 CLT115











786 Merged CLT115-0002 RULE-1081 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT115 OCCURRENCE-CODE-END-DATE-04 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-04 CLT115











787 No logic changes CLT115-0004 RULE-1083 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT115 OCCURRENCE-CODE-END-DATE-04 2 If OCCURRENCE-CODE-04 is not 8-filled, then OCCURRENCE-CODE-END-DATE-04 must not be 8-filled 2344 Relational edit between OCCURRENCE-CODE-04 and OCCURRENCE-CODE-END-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-04), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-04,OCCURRENCE-CODE-END-DATE-04 CLT095,CLT115











788 Merged CLT115-0006 RULE-1044 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT115 OCCURRENCE-CODE-END-DATE-04 2-M
2072
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-04, @val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-EFF-DATE-04,OCCURRENCE-CODE-END-DATE-04 CLT105,CLT115











789 Merged CLT116-0001 RULE-1085 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT116 OCCURRENCE-CODE-END-DATE-05 1 If OCCURRENCE-CODE-END-DATE-05 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-05 CLT116











790 Merged CLT116-0002 RULE-1085 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT116 OCCURRENCE-CODE-END-DATE-05 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-05 CLT116











791 No logic changes CLT116-0004 RULE-1087 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT116 OCCURRENCE-CODE-END-DATE-05 2 If OCCURRENCE-CODE-05 is not 8-filled, then OCCURRENCE-CODE-END-DATE-05 must not be 8-filled 2346 Relational edit between OCCURRENCE-CODE-05 and OCCURRENCE-CODE-END-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-05), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-05,OCCURRENCE-CODE-END-DATE-05 CLT096,CLT116











792 Merged CLT116-0006 RULE-1048 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT116 OCCURRENCE-CODE-END-DATE-05 2-M
2073
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-05, @val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-EFF-DATE-05,OCCURRENCE-CODE-END-DATE-05 CLT106,CLT116











793 Merged CLT117-0001 RULE-1089 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT117 OCCURRENCE-CODE-END-DATE-06 1 If OCCURRENCE-CODE-END-DATE-06 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-06 CLT117











794 Merged CLT117-0002 RULE-1089 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT117 OCCURRENCE-CODE-END-DATE-06 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-06 CLT117











795 No logic changes CLT117-0004 RULE-1091 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT117 OCCURRENCE-CODE-END-DATE-06 2 If OCCURRENCE-CODE-06 is not 8-filled, then OCCURRENCE-CODE-END-DATE-06 must not be 8-filled 2348 Relational edit between OCCURRENCE-CODE-06 and OCCURRENCE-CODE-END-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-06), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-06,OCCURRENCE-CODE-END-DATE-06 CLT097,CLT117











796 Merged CLT117-0006 RULE-1052 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT117 OCCURRENCE-CODE-END-DATE-06 2-M
2074
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-06, @val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-EFF-DATE-06,OCCURRENCE-CODE-END-DATE-06 CLT107,CLT117











797 Merged CLT118-0001 RULE-1093 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT118 OCCURRENCE-CODE-END-DATE-07 1 If OCCURRENCE-CODE-END-DATE-07 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-07 CLT118











798 Merged CLT118-0002 RULE-1093 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT118 OCCURRENCE-CODE-END-DATE-07 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-07 CLT118











799 No logic changes CLT118-0004 RULE-1095 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT118 OCCURRENCE-CODE-END-DATE-07 2 If OCCURRENCE-CODE-07 is not 8-filled, then OCCURRENCE-CODE-END-DATE-07 must not be 8-filled 2350 Relational edit between OCCURRENCE-CODE-07 and OCCURRENCE-CODE-END-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-07), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-07,OCCURRENCE-CODE-END-DATE-07 CLT098,CLT118











800 Merged CLT118-0006 RULE-1056 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT118 OCCURRENCE-CODE-END-DATE-07 2-M
2075
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-07, @val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-EFF-DATE-07,OCCURRENCE-CODE-END-DATE-07 CLT108,CLT118











801 Merged CLT119-0001 RULE-1097 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT119 OCCURRENCE-CODE-END-DATE-08 1 If OCCURRENCE-CODE-END-DATE-08 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-08 CLT119











802 Merged CLT119-0002 RULE-1097 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT119 OCCURRENCE-CODE-END-DATE-08 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-08 CLT119











803 No logic changes CLT119-0004 RULE-1099 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT119 OCCURRENCE-CODE-END-DATE-08 2 If OCCURRENCE-CODE-08 is not 8-filled, then OCCURRENCE-CODE-END-DATE-08 must not be 8-filled 2352 Relational edit between OCCURRENCE-CODE-08 and OCCURRENCE-CODE-END-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-08), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-08,OCCURRENCE-CODE-END-DATE-08 CLT099,CLT119











804 Merged CLT119-0006 RULE-1060 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT119 OCCURRENCE-CODE-END-DATE-08 2-M
2076
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-08, @val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-EFF-DATE-08,OCCURRENCE-CODE-END-DATE-08 CLT109,CLT119











805 Merged CLT120-0001 RULE-1101 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT120 OCCURRENCE-CODE-END-DATE-09 1 If OCCURRENCE-CODE-END-DATE-09 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-09 CLT120











806 Merged CLT120-0002 RULE-1101 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT120 OCCURRENCE-CODE-END-DATE-09 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-09 CLT120











807 No logic changes CLT120-0004 RULE-1103 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT120 OCCURRENCE-CODE-END-DATE-09 2 If OCCURRENCE-CODE-09 is not 8-filled, then OCCURRENCE-CODE-END-DATE-09 must not be 8-filled 2354 Relational edit between OCCURRENCE-CODE-09 and OCCURRENCE-CODE-END-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-09), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-09,OCCURRENCE-CODE-END-DATE-09 CLT100,CLT120











808 Merged CLT120-0006 RULE-1064 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT120 OCCURRENCE-CODE-END-DATE-09 2-M
2077
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-09, @val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-EFF-DATE-09,OCCURRENCE-CODE-END-DATE-09 CLT110,CLT120











809 Merged CLT121-0001 RULE-1105 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT121 OCCURRENCE-CODE-END-DATE-10 1 If OCCURRENCE-CODE-END-DATE-10 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-10 CLT121











810 Merged CLT121-0002 RULE-1105 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT121 OCCURRENCE-CODE-END-DATE-10 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-10 CLT121











811 No logic changes CLT121-0004 RULE-1107 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT121 OCCURRENCE-CODE-END-DATE-10 2 If OCCURRENCE-CODE-10 is not 8-filled, then OCCURRENCE-CODE-END-DATE-10 must not be 8-filled 2356 Relational edit between OCCURRENCE-CODE-10 and OCCURRENCE-CODE-END-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-10), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-10,OCCURRENCE-CODE-END-DATE-10 CLT101,CLT121











812 Merged CLT121-0006 RULE-1068 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT121 OCCURRENCE-CODE-END-DATE-10 2-M
2078
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-10) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-10), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-10, @val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-EFF-DATE-10,OCCURRENCE-CODE-END-DATE-10 CLT111,CLT121











813 Logic updated: string matching CLT122-0001 RULE-1109 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT122 PATIENT-CONTROL-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PATIENT-CONTROL-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.PATIENT-CONTROL-NUM), then fns.matches(@val.PATIENT-CONTROL-NUM, "^[^|*]*$")' PATIENT-CONTROL-NUM CLT122











814 Logic updated: string matching CLT123-0001 RULE-1110 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT123 ELIGIBLE-LAST-NAME 1 ELIGIBLE-LAST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid character - ELIGIBLE-LAST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ELIGIBLE-LAST-NAME), then fns.matches(@val.ELIGIBLE-LAST-NAME, "^[^|*]*$")' ELIGIBLE-LAST-NAME CLT123











815 Logic updated: string matching CLT124-0001 RULE-1111 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT124 ELIGIBLE-FIRST-NAME 1 ELIGIBLE-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - ELIGIBLE-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ELIGIBLE-FIRST-NAME), then fns.matches(@val.ELIGIBLE-FIRST-NAME, "^[^|*]*$")' ELIGIBLE-FIRST-NAME CLT124











816 Logic updated: string matching CLT125-0001 RULE-1112 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT125 ELIGIBLE-MIDDLE-INIT 1 ELIGIBLE-MIDDLE-INIT must not contain non-alphabetic characters 120 Field contains invalid characters - ELIGIBLE-MIDDLE-INIT 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ELIGIBLE-MIDDLE-INIT), then fns.matches(@val.ELIGIBLE-MIDDLE-INIT, "^[^|*]*$")' ELIGIBLE-MIDDLE-INIT CLT125











817 Merged CLT126-0001 RULE-1113 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT126 DATE-OF-BIRTH 1 If DATE-OF-BIRTH is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH CLT126











818 Merged CLT126-0002 RULE-1113 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT126 DATE-OF-BIRTH 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH CLT126











819 Logic updated: other CLT126-0007 RULE-1115 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT126 DATE-OF-BIRTH 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled
and
CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64",
then DATE-OF-BIRTH must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002]		 3037 Relational edit between DATE-OF-BIRTH and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-LT CLT00002 ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 'if fns.hasValue(@secondaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@secondaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64") && fns.hasValue(@tertiaryRecord.DATE-OF-DEATH), then fns.isLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @tertiaryRecord.DATE-OF-DEATH)' DATE-OF-BIRTH CLT126 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-DEATH ELG025 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT017,CLT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT017,CLT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019
820 Logic updated: other CLT126-0008 RULE-1116 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT126 DATE-OF-BIRTH 3 If CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64", then DATE-OF-BIRTH must = DATE-OF-BIRTH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3023 A DATE-OF-BIRTH does not match the DATE-OF-BIRTH in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-LT CLT00002 ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 if fns.hasValue(@secondaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@secondaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64"), then fns.isEqual(@primaryRecord.DATE-OF-BIRTH, @tertiaryRecord.DATE-OF-BIRTH)' DATE-OF-BIRTH CLT126 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-BIRTH ELG024 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT017,CLT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT017,CLT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019
821 No logic changes CLT127-0001 RULE-1117 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT127 HEALTH-HOME-PROV-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-HOME-PROV-IND HEALTH-HOME-PROV-IND CLT127











822 No logic changes CLT127-0003 RULE-1118 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT127 HEALTH-HOME-PROV-IND 2 If HEALTH-HOME-ENTITY-NAME is not 8-filled, then HEALTH-HOME-PROV-IND must = "1" 2294 Relational edit between HEALTH-HOME-PROV-IND and HEALTH-HOME-ENTITY-NAME failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.isEqual(@val.HEALTH-HOME-PROV-IND, "1")' HEALTH-HOME-ENTITY-NAME,HEALTH-HOME-PROV-IND CLT161,CLT127











823 No logic changes CLT128-0001 RULE-1119 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT128 WAIVER-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-TYPE WAIVER-TYPE CLT128











824 Merged CLT129-0001 RULE-1120 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT129 WAIVER-ID 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID CLT129











825 Merged CLT129-0005 RULE-1121 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT129 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CLT128,CLT129











826 Merged CLT129-0009 RULE-1120 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT129 WAIVER-ID 3 WAIVER-ID must = waiver ID in state-provided crosswalk 3029 Edit with an external reference (state provided WAIVER-ID-/WAIVER-TYPE crosswalk) failed 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID CLT129











827 Merged CLT129-0010 RULE-1121 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT129 WAIVER-ID 2 If WAIVER-TYPE is 8-filled, then WAIVER-ID must be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CLT128,CLT129











828 Merged CLT129-0011 RULE-1121 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT129 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CLT128,CLT129











829 Retired: Other reasons CLT130-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT130 BILLING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























830 Logic updated: other CLT130-0004 RULE-1126 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT130 BILLING-PROV-NUM 3 If ( BILLING-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then BILLING-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-LT CLT00002

For every record of type CLAIM-HEADER-RECORD-LT, if fns.hasValue(@secondaryRecord.BILLING-PROV-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "1") PROV-IDENTIFIER-TYPE PRV077 BILLING-PROV-NUM,TYPE-OF-CLAIM CLT130,CLT052

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,BILLING-PROV-NUM CLT017,CLT130



831 Merged CLT131-0001 RULE-1127 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT131 BILLING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM CLT131











832 Merged CLT131-0002 RULE-1127 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT131 BILLING-PROV-NPI-NUM 1 If BILLING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM CLT131











833 Logic updated: other CLT131-0006 RULE-1129 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT131 BILLING-PROV-NPI-NUM 3 If ( BILLING-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then BILLING-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-LT CLT00002

For every record of type CLAIM-HEADER-RECORD-LT, if fns.hasValue(@secondaryRecord.BILLING-PROV-NPI-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "2") PROV-IDENTIFIER-TYPE PRV077 BILLING-PROV-NPI-NUM,TYPE-OF-CLAIM CLT131,CLT052

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,BILLING-PROV-NPI-NUM CLT017,CLT131



834 No logic changes CLT132-0001 RULE-1130 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT132 BILLING-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY BILLING-PROV-TAXONOMY CLT132











835 No logic changes CLT133-0001 RULE-1131 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT133 BILLING-PROV-TYPE 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE BILLING-PROV-TYPE CLT133











836 No logic changes CLT134-0001 RULE-1132 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT134 BILLING-PROV-SPECIALTY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY BILLING-PROV-SPECIALTY CLT134











837 Retired: Other reasons CLT135-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT135 REFERRING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























838 Merged CLT136-0001 RULE-1134 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT136 REFERRING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.REFERRING-PROV-NPI-NUM), then fns.isValidNPI(@val.REFERRING-PROV-NPI-NUM)' REFERRING-PROV-NPI-NUM CLT136











839 Merged CLT136-0002 RULE-1134 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT136 REFERRING-PROV-NPI-NUM 1 If REFERRING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.REFERRING-PROV-NPI-NUM), then fns.isValidNPI(@val.REFERRING-PROV-NPI-NUM)' REFERRING-PROV-NPI-NUM CLT136











840 No logic changes CLT137-0001 RULE-1136 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT137 REFERRING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY REFERRING-PROV-TAXONOMY CLT137











841 No logic changes CLT138-0001 RULE-1137 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT138 REFERRING-PROV-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE REFERRING-PROV-TYPE CLT138











842 No logic changes CLT139-0001 RULE-1138 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT139 REFERRING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY REFERRING-PROV-SPECIALTY CLT139











843 Logic updated: string matching CLT140-0001 RULE-1139 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT140 MEDICARE-HIC-NUM 1 Field contains invalid characters -MEDICARE-HIC-NUM 120 Field contains invalid characters -MEDICARE-HIC-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.matches(@val.MEDICARE-HIC-NUM, "^[^|*]*$")' MEDICARE-HIC-NUM CLT140











844 No logic changes CLT140-0003 RULE-1140 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT140 MEDICARE-HIC-NUM 2 If CROSSOVER-INDICATOR= "1" and MEDICARE-BENEFICIARY-IDENTIFIER is 8-filled, then MEDICARE-HIC-NUM must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.hasValue(@val.MEDICARE-HIC-NUM)' CROSSOVER-INDICATOR,MEDICARE-BENEFICIARY-IDENTIFIER,MEDICARE-HIC-NUM CLT023,CLT168,CLT140











845 No logic changes CLT141-0001 RULE-1141 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT141 PATIENT-STATUS 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PATIENT-STATUS PATIENT-STATUS CLT141











846 No logic changes CLT141-0002 RULE-1142 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT141 PATIENT-STATUS 3 If DATE-OF-DEATH [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] is <= DISCHARGE-DATE, then PATIENT-STATUS must = "20", "40", "41", OR "42" where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-LT-CLT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3039 Relational edit between PATIENT-STATUS and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-LT CLT00002

'if fns.isLessThanOrEqual(@primaryRecord.DATE-OF-DEATH, @secondaryRecord.DISCHARGE-DATE), then fns.isEqualToAny(@secondaryRecord.PATIENT-STATUS, "20", "40", "41", "42")' DATE-OF-DEATH ELG025 DISCHARGE-DATE,PATIENT-STATUS CLT046,CLT141

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE CLT022,CLT017



847 No logic changes CLT143-0001 RULE-6438 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT143 BMI 1 If BMI is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: S9(5)V9 BMI CLT143











848 Logic updated: string matching CLT144-0001 RULE-1144 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT144 REMITTANCE-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - REMITTANCE-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.REMITTANCE-NUM), then fns.matches(@val.REMITTANCE-NUM, "^[^|*]*$")' REMITTANCE-NUM CLT144











849 Retired: required value checks CLT144-0002
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT144 REMITTANCE-NUM 1 If REMITTANCE-NUM is null 113 Required data element has not been reported.

























850 No logic changes CLT145-0001 RULE-1146 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT145 LTC-RCP-LIAB-AMT 1 if LTC-RCP-LIAB-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 LTC-RCP-LIAB-AMT CLT145











851 Logic updated: other CLT145-0002 RULE-1147 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT145 LTC-RCP-LIAB-AMT 2 Absolute value of LTC-RCP-LIAB-AMT must be <= Absolute value of [TOT-BILLED-AMT minus (TOT-MEDICARE-COINS-AMT plus TOT-MEDICARE-DEDUCTIBLE-AMT)] 2442 Relational edit with LTC-RCP-LIAB-AMT, TOT-BILLED-AMT, TOT-MEDICARE-COINS-AMT, and TOT-MEDICARE-DEDUCTIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.LTC-RCP-LIAB-AMT) && fns.hasValue(@val.TOT-BILLED-AMT) && fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.isLessThanOrEqual(@val.LTC-RCP-LIAB-AMT, fns.remainingLiability(@val.TOT-BILLED-AMT, @val.TOT-MEDICARE-COINS-AMT, @val.TOT-MEDICARE-DEDUCTIBLE-AMT))' LTC-RCP-LIAB-AMT,TOT-BILLED-AMT,TOT-MEDICARE-COINS-AMT,TOT-MEDICARE-DEDUCTIBLE-AMT CLT145,CLT063,CLT068,CLT067











852 No logic changes CLT146-0001 RULE-1148 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT146 DAILY-RATE 1 If DAILY-RATE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(5)V99 DAILY-RATE CLT146











853 No logic changes CLT147-0001 RULE-1149 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT147 ICF-IID-DAYS 1 If ICF-IID-DAYS not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: S9(5) ICF-IID-DAYS CLT147











854 Logic updated: other CLT147-0004 RULE-1150 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT147 ICF-IID-DAYS 2 ICF-IID-DAYS must be <= [(ENDING-DATE-OF-SERVICE - BEGINNING-DATE OF-SERVICE plus 1 (in number of days))] 2298 Relational edit between ICF-IID-DAYS, BEGINNING-DATE-OF-SERVICE, and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ICF-IID-DAYS) && fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isValueLessThanOrEqualToStayDuration(@val.ICF-IID-DAYS, @val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' ICF-IID-DAYS,BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CLT147,CLT048,CLT049











855 No logic changes CLT147-0005 RULE-1151 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT147 ICF-IID-DAYS 2 If TYPE-OF-SERVICE = "046", then ICF-IID-DAYS must not be 8-filled 2297 Relational edit between ICF-IID-DAYS and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqual(@secondaryRecord.TYPE-OF-SERVICE, "046"), then fns.hasValue(@primaryRecord.ICF-IID-DAYS)' ICF-IID-DAYS CLT147 TYPE-OF-SERVICE CLT211

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



856 No logic changes CLT147-0006 RULE-1152 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT147 ICF-IID-DAYS 2 If TYPE-OF-SERVICE = "009","044", "045", "047", "048", or "050", then ICF-IID-DAYS must be 8-filled 2297 Relational edit between ICF-IID-DAYS and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "009", "044", "045", "047", "048", "050"), then !fns.hasValue(@primaryRecord.ICF-IID-DAYS)' ICF-IID-DAYS CLT147 TYPE-OF-SERVICE CLT211

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



857 No logic changes CLT148-0001 RULE-1153 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT148 LEAVE-DAYS 1 If LEAVE-DAYS is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: S9(5) LEAVE-DAYS CLT148











858 No logic changes CLT149-0001 RULE-1154 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT149 NURSING-FACILITY-DAYS 1 If NURSING-FACILITY-DAYS is not numeric 109 Non-numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: S9(5) NURSING-FACILITY-DAYS CLT149











859 Logic updated: other CLT149-0005 RULE-1155 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT149 NURSING-FACILITY-DAYS 2 If NURSING-FACILITY-DAYS <> "0" or is not 8-filled, then NURSING-FACILITY-DAYS must be <= (ENDING-DATE-OF-SERVICE minus BEGINNING-DATE-OF-SERVICE plus 1 (in days)). 2336 Relational edit between NURSING-FACILITY-DAYS , BEGINNING-DATE-OF-SERVICE, and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.NURSING-FACILITY-DAYS) && !fns.isEqual(@val.NURSING-FACILITY-DAYS, "0"), then fns.isValueLessThanOrEqualToStayDuration(@val.NURSING-FACILITY-DAYS, @val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' NURSING-FACILITY-DAYS,BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CLT149,CLT048,CLT049











860 No logic changes CLT150-0001 RULE-1156 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT150 SPLIT-CLAIM-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: SPLIT-CLAIM-IND SPLIT-CLAIM-IND CLT150











861 No logic changes CLT151-0001 RULE-1157 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT151 BORDER-STATE-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: BORDER-STATE-IND BORDER-STATE-IND CLT151











862 No logic changes CLT153-0001 RULE-1158 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT153 BENEFICIARY-COINSURANCE-AMOUNT 1 If BENEFICIARY-COINSURANCE-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COINSURANCE-AMOUNT CLT153











863 Merged CLT154-0001 RULE-1159 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT154 BENEFICIARY-COINSURANCE-DATE-PAID 1 If BENEFICIARY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID CLT154











864 Merged CLT154-0002 RULE-1159 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT154 BENEFICIARY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID CLT154











865 No logic changes CLT155-0001 RULE-1161 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT155 BENEFICIARY-COPAYMENT-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COPAYMENT-AMOUNT CLT155











866 Merged CLT156-0001 RULE-1162 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT156 BENEFICIARY-COPAYMENT-DATE-PAID 1 If BENEFICIARY-COPAYMENT-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COPAYMENT-DATE-PAID CLT156











867 Merged CLT156-0002 RULE-1162 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT156 BENEFICIARY-COPAYMENT-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COPAYMENT-DATE-PAID CLT156











868 No logic changes CLT157-0001 RULE-1164 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT157 BENEFICIARY-DEDUCTIBLE-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-DEDUCTIBLE-AMOUNT CLT157











869 Merged CLT158-0001 RULE-1165 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT158 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 If BENEFICIARY-DEDUCTIBLE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID CLT158











870 Merged CLT158-0002 RULE-1165 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT158 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID CLT158











871 No logic changes CLT159-0001 RULE-1167 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT159 CLAIM-DENIED-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-DENIED-INDICATOR CLAIM-DENIED-INDICATOR CLT159











872 No logic changes CLT159-0003 RULE-1168 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT159 CLAIM-DENIED-INDICATOR 2 If TYPE-OF-CLAIM = "Z", then CLAIM-DENIED-INDICATOR must = "0" 2242 Relational edit between CLAIM-DENIED-INDICATOR and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.isEqual(@val.TYPE-OF-CLAIM, "Z"), then fns.isEqual(@val.CLAIM-DENIED-INDICATOR, "0")' TYPE-OF-CLAIM,CLAIM-DENIED-INDICATOR CLT052,CLT159











873 No logic changes CLT160-0001 RULE-1169 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT160 COPAY-WAIVED-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: COPAY-WAIVED-IND COPAY-WAIVED-IND CLT160











874 Logic updated: string matching CLT161-0001 RULE-1170 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT161 HEALTH-HOME-ENTITY-NAME 1 If HEALTH-HOME-ENTITY-NAME is populated, it must contains valid characters. 120 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.matches(@val.HEALTH-HOME-ENTITY-NAME, "^[^|*]*$")' HEALTH-HOME-ENTITY-NAME CLT161











875 No logic changes CLT163-0001 RULE-1171 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT163 THIRD-PARTY-COINSURANCE-AMOUNT-PAID 1 If THIRD-PARTY-COINSURANCE-AMOUNT-PAID is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COINSURANCE-AMOUNT-PAID CLT163











876 Merged CLT164-0001 RULE-1172 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT164 THIRD-PARTY-COINSURANCE-DATE-PAID 1 If THIRD-PARTY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID CLT164











877 Merged CLT164-0002 RULE-1172 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT164 THIRD-PARTY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID CLT164











878 No logic changes CLT165-0001 RULE-1174 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT165 THIRD-PARTY-COPAYMENT-AMOUNT-PAID 1 If THIRD-PARTY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COPAYMENT-AMOUNT-PAID CLT165











879 Merged CLT166-0001 RULE-1175 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT166 THIRD-PARTY-COPAYMENT-DATE-PAID 1 If THIRD-PARTY-COPAYMENT-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID CLT166











880 Merged CLT166-0002 RULE-1175 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT166 THIRD-PARTY-COPAYMENT-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID CLT166











881 Merged CLT167-0001 RULE-1177 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT167 HEALTH-HOME-PROVIDER-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI CLT167











882 Merged CLT167-0002 RULE-1177 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT167 HEALTH-HOME-PROVIDER-NPI 1 If HEALTH-HOME-PROVIDER-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI CLT167











883 Logic updated: other CLT167-0004 RULE-1179 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT167 HEALTH-HOME-PROVIDER-NPI 3 If ( HEALTH-HOME-PROVIDER-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then HEALTH-HOME-PROVIDER-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-LT CLT00002

For every record of type CLAIM-HEADER-RECORD-LT, if fns.hasValue(@secondaryRecord.HEALTH-HOME-PROVIDER-NPI) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "2") PROV-IDENTIFIER-TYPE PRV077 HEALTH-HOME-PROVIDER-NPI,TYPE-OF-CLAIM CLT167,CLT052

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,HEALTH-HOME-PROVIDER-NPI CLT017,CLT167



884 Logic updated: string matching CLT168-0001 RULE-1180 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT168 MEDICARE-BENEFICIARY-IDENTIFIER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - MEDICARE-BENEFICIARY-IDENTIFIER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.matches(@val.MEDICARE-BENEFICIARY-IDENTIFIER, "^[^|*]*$")' MEDICARE-BENEFICIARY-IDENTIFIER CLT168











885 No logic changes CLT168-0003 RULE-1181 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT168 MEDICARE-BENEFICIARY-IDENTIFIER 2 If END-OF-TIME-PERIOD >= "20151110", CROSSOVER-INDICATOR= "1" and MEDICARE-HIC-NUM is 8-filled, then MEDICARE-BENEFICIARY-IDENTIFIER must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 FILE-HEADER-RECORD-LT CLT00001

'if fns.isGreaterThanOrEqual(@fileHeader.END-OF-TIME-PERIOD, "2015-11-10") && fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER)' CROSSOVER-INDICATOR,MEDICARE-HIC-NUM,MEDICARE-BENEFICIARY-IDENTIFIER CLT023,CLT140,CLT168 END-OF-TIME-PERIOD CLT010









886 No logic changes CLT169-0001 RULE-1182 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT169 UNDER-DIRECTION-OF-PROV-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.UNDER-DIRECTION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-DIRECTION-OF-PROV-NPI)' UNDER-DIRECTION-OF-PROV-NPI CLT169











887 No logic changes CLT170-0001 RULE-1183 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT170 UNDER-DIRECTION-OF-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY UNDER-DIRECTION-OF-PROV-TAXONOMY CLT170











888 Merged CLT171-0001 RULE-1184 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT171 UNDER-SUPERVISION-OF-PROV-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.UNDER-SUPERVISION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-SUPERVISION-OF-PROV-NPI)' UNDER-SUPERVISION-OF-PROV-NPI CLT171











889 Merged CLT171-0002 RULE-1184 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT171 UNDER-SUPERVISION-OF-PROV-NPI 1 If UNDER-SUPERVISION-OF-PROV-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.UNDER-SUPERVISION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-SUPERVISION-OF-PROV-NPI)' UNDER-SUPERVISION-OF-PROV-NPI CLT171











890 No logic changes CLT172-0001 RULE-1186 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT172 UNDER-SUPERVISION-OF-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY UNDER-SUPERVISION-OF-PROV-TAXONOMY CLT172











891 Logic updated: string matching CLT173-0001 RULE-1187 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT173 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION CLT173











892 Merged CLT174-0001 RULE-1189 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT174 ADMITTING-PROV-NPI-NUM 1 If ADMITTING-PROV-NPI-NUM not > or = 0 120 Field contains invalid characters - ADMITTING-PROV-NPI-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ADMITTING-PROV-NPI-NUM), then fns.isValidNPI(@val.ADMITTING-PROV-NPI-NUM)' ADMITTING-PROV-NPI-NUM CLT174











893 Merged CLT174-0002 RULE-1189 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT174 ADMITTING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.ADMITTING-PROV-NPI-NUM), then fns.isValidNPI(@val.ADMITTING-PROV-NPI-NUM)' ADMITTING-PROV-NPI-NUM CLT174











894 Retired: Other reasons CLT175-0001
CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT175 ADMITTING-PROV-NUM 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























895 No logic changes CLT176-0001 RULE-1191 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT176 ADMITTING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY ADMITTING-PROV-SPECIALTY CLT176











896 No logic changes CLT177-0001 RULE-1192 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT177 ADMITTING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY ADMITTING-PROV-TAXONOMY CLT177











897 No logic changes CLT178-0001 RULE-1193 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT178 ADMITTING-PROV-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-LT CLT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE ADMITTING-PROV-TYPE CLT178











898 No logic changes CLT179-0001 RULE-1194 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT179 MEDICARE-PAID-AMT 1 If MEDICARE-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICARE-PAID-AMT CLT179











899 Moved to R&C CLT184-0001
CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT184 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























900 Moved to R&C CLT184-0004
CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT184 RECORD-ID 2 If FILE-NAME = "CLAIM-LT", then the first 3 positions of RECORD-ID must = "CLT" 150 Invalid or missing RECORD-ID

























901 No logic changes CLT185-0001 RULE-1197 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT185 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE CLT185











902 Logic updated: other CLT185-0004 RULE-1198 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT185 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-LT-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-LT CLT00003 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE CLT185 SUBMITTING-STATE CLT007









903 Retired: Other reasons CLT186-0001
CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT186 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























904 No logic changes CLT186-0004 RULE-1200 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT186 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-LINE-RECORD-LT CLT00003



Field RECORD-NUMBER should be unique across all records of type CLAIM-LINE-RECORD-LT RECORD-NUMBER CLT186











905 Retired: MSIS ID checks CLT187-0001
CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT187 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























906 Retired: MSIS ID checks CLT187-0002
CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT187 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























907 No logic changes CLT187-0003 RULE-1203 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT187 MSIS-IDENTIFICATION-NUM 2 If TYPE-OF-CLAIM = "4", "D", OR "X", then the first byte of MSIS-IDENTIFICATION-NUM must = "&" 2331 Relational edit between MSIS-IDENTIFICATION-NUM and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "4", "D", "X"), then fns.matches(@secondaryRecord.MSIS-IDENTIFICATION-NUM, "^&.*$")' TYPE-OF-CLAIM CLT052 MSIS-IDENTIFICATION-NUM CLT187

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



908 Logic updated: parent/child overlap CLT187-0005 RULE-1204 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT187 MSIS-IDENTIFICATION-NUM 2 ICN-ORIG [SUBMITTING-STATE CLAIM-LINE-RECORD-LT-CLT00003] must = ICN-ORIG [CLAIM-HEADER-RECORD-LT-CLT00002],
and ICN-ADJ [SUBMITTING-STATE CLAIM-LINE-RECORD-LT-CLT00003] must = ICN-ADJ [CLAIM-HEADER-RECORD-LT-CLT00002],
and ADJUDICATION-DATE [SUBMITTING-STATE CLAIM-LINE-RECORD-LT-CLT00003] must = ADJUDICATION-DATE [CLAIM-HEADER-RECORD-LT-CLT00002] on any record in the file,
and SUBMITTING-STATE [CLAIM-LINE-RECORD-LT-CLT00003] must = SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] on the same record in the file		 2190 Edit that CLAIM-LINE-RECORD-LT-CLT00003 child record has a CLAIM-HEADER-RECORD-LT-CLT00002 parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

record CLAIM-LINE-RECORD-LT has corresponding parent record CLAIM-HEADER-RECORD-LT





SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



909 Logic updated: string matching CLT188-0001 RULE-1205 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT188 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ORIG 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG CLT188











910 Logic updated: string matching CLT189-0001 RULE-1206 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT189 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ CLT189











911 No logic changes CLT190-0001 RULE-1207 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT190 LINE-NUM-ORIG 1 If LINE-NUM-ORIG not >=0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.LINE-NUM-ORIG), then fns.isNonNegative(@val.LINE-NUM-ORIG)' LINE-NUM-ORIG CLT190











912 No logic changes CLT191-0001 RULE-1208 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT191 LINE-NUM-ADJ 1 if LINE-NUM-ADJ not >=0. 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.isNonNegative(@val.LINE-NUM-ADJ)' LINE-NUM-ADJ CLT191











913 No logic changes CLT191-0002 RULE-1209 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT191 LINE-NUM-ADJ 2 If LINE-ADJUSTMENT-IND = "0", then LINE-NUM-ADJ must be 8-filled 2312 Relational edit between LINE-NUM-ADJ and LINE-ADJUSTMENT-IND failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.isEqual(@val.LINE-ADJUSTMENT-IND, "0"), then !fns.hasValue(@val.LINE-NUM-ADJ)' LINE-ADJUSTMENT-IND,LINE-NUM-ADJ CLT192,CLT191











914 No logic changes CLT191-0003 RULE-1210 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT191 LINE-NUM-ADJ 2 If ADJUSTMENT-IND = "0", then LINE-NUM-ADJ must be 8-filled 2311 Relational edit between LINE-NUM-ADJ and ADJUSTMENT-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqual(@primaryRecord.ADJUSTMENT-IND, "0"), then !fns.hasValue(@secondaryRecord.LINE-NUM-ADJ)' ADJUSTMENT-IND CLT025 LINE-NUM-ADJ CLT191

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



915 No logic changes CLT192-0001 RULE-1211 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT192 LINE-ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: LINE-ADJUSTMENT-IND LINE-ADJUSTMENT-IND CLT192











916 No logic changes CLT192-0002 RULE-1212 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT192 LINE-ADJUSTMENT-IND 2 If LINE-NUM-ADJ is not 8-filled then LINE-ADJUSTMENT-IND must not be 8-filled 2310 Relational edit between LINE-ADJUSTMENT-IND and LINE-NUM-ADJ failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.hasValue(@val.LINE-ADJUSTMENT-IND)' LINE-NUM-ADJ,LINE-ADJUSTMENT-IND CLT191,CLT192











917 No logic changes CLT193-0001 RULE-1213 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT193 LINE-ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE LINE-ADJUSTMENT-REASON-CODE CLT193











918 Retired: required value checks CLT194-0001
CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT194 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported.

























919 No logic changes CLT195-0001 RULE-1215 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT195 CLAIM-LINE-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-LINE-STATUS CLT195











920 Merged CLT196-0001 RULE-1216 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT196 BEGINNING-DATE-OF-SERVICE 1 If BEGINNING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE CLT196











921 Merged CLT196-0002 RULE-1216 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT196 BEGINNING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE CLT196











922 Merged CLT196-0003 RULE-1218 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT196 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CLT196,CLT197











923 Logic updated: other CLT196-0004 RULE-1219 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT196 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2013 Relational edit between BEGINNING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-LT CLT00003 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE CLT196 END-OF-TIME-PERIOD CLT010









924 Logic updated: other CLT196-0005 RULE-1220 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT196 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-LINE-RECORD-LT] 2010 Relational edit between BEGINNING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-LINE-RECORD-LT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' BEGINNING-DATE-OF-SERVICE,ADJUDICATION-DATE CLT196,CLT233











925 Logic updated: other CLT196-0006 RULE-1221 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT196 BEGINNING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then BEGINNING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-LT-CLT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-LT-CLT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3002 Relational edit between BEGINNING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 BEGINNING-DATE-OF-SERVICE CLT196

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT185,CLT187



926 Merged CLT197-0001 RULE-1222 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT197 ENDING-DATE-OF-SERVICE 1 If ENDING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE CLT197











927 Merged CLT197-0002 RULE-1222 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT197 ENDING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE CLT197











928 Merged CLT197-0003 RULE-1218 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT197 ENDING-DATE-OF-SERVICE 2-M
2012
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE CLT196,CLT197











929 Logic updated: other CLT197-0004 RULE-1225 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT197 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-LINE-RECORD-LT] 2039 Relational edit between ENDING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-LINE-RECORD-LT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' ENDING-DATE-OF-SERVICE,ADJUDICATION-DATE CLT197,CLT233











930 Logic updated: other CLT197-0005 RULE-1226 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT197 ENDING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then ENDING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-LT-CLT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-LT-CLT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3005 Relational edit between ENDING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.ENDING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ENDING-DATE-OF-SERVICE CLT197

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT185,CLT187



931 Logic updated: other CLT197-0008 RULE-1227 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT197 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2036 Relational edit between ENDING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-LT CLT00003 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' ENDING-DATE-OF-SERVICE CLT197 END-OF-TIME-PERIOD CLT010









932 No logic changes CLT198-0001 RULE-1228 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT198 REVENUE-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: REVENUE-CODE REVENUE-CODE CLT198











933 No logic changes CLT201-0001 RULE-1229 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT201 IMMUNIZATION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: IMMUNIZATION-TYPE IMMUNIZATION-TYPE CLT201











934 No logic changes CLT202-0001 RULE-1230 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT202 IP-LT-QUANTITY-OF-SERVICE-ACTUAL 1 If IP-LT-QUANTITY-OF-SERVICE-ACTUAL is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: S9(6)V999 IP-LT-QUANTITY-OF-SERVICE-ACTUAL CLT202











935 No logic changes CLT203-0001 RULE-1231 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT203 IP-LT-QUANTITY-OF-SERVICE-ALLOWED 1 If IP-LT-QUANTITY-OF-SERVICE-ALLOWED is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: S9(6)V999 IP-LT-QUANTITY-OF-SERVICE-ALLOWED CLT203











936 No logic changes CLT204-0001 RULE-1232 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT204 REVENUE-CHARGE 1 If REVENUE-CHARGE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 REVENUE-CHARGE CLT204











937 Logic updated: other CLT204-0005 RULE-1233 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT204 REVENUE-CHARGE 2 The absolute value of the sum of REVENUE-CHARGE on each detail line record must be <= absolute value of TOT-BILLED-AMT 2409 Relational edit between REVENUE-CHARGE and TOT-BILLED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'fns.isDollarSumLessThanOrEqual(@primaryRecord.TOT-BILLED-AMT, @secondaryRecords.REVENUE-CHARGE)' TOT-BILLED-AMT CLT063 REVENUE-CHARGE CLT204

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



938 Merged CLT204-0006 RULE-1234 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT204 REVENUE-CHARGE 2 If REVENUE-CODE is 8-filled, then REVENUE-CHARGE must be 8-filled 2408 Relational edit between REVENUE-CHARGE and REVENUE-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if and only if fns.hasValue(@val.REVENUE-CODE), then fns.hasValue(@val.REVENUE-CHARGE)' REVENUE-CODE,REVENUE-CHARGE CLT198,CLT204











939 Merged CLT204-0007 RULE-1234 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT204 REVENUE-CHARGE 2 If REVENUE-CODE is not 8-filled, then REVENUE-CHARGE must not be 8-filled 2408 Relational edit between REVENUE-CHARGE and REVENUE-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if and only if fns.hasValue(@val.REVENUE-CODE), then fns.hasValue(@val.REVENUE-CHARGE)' REVENUE-CODE,REVENUE-CHARGE CLT198,CLT204











940 No logic changes CLT205-0001 RULE-1236 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT205 ALLOWED-AMT 1 If ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 ALLOWED-AMT CLT205











941 No logic changes CLT206-0001 RULE-1237 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT206 TPL-AMT 1 If TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TPL-AMT CLT206











942 No logic changes CLT207-0001 RULE-1238 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT207 OTHER-INSURANCE-AMT 1 If OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 OTHER-INSURANCE-AMT CLT207











943 No logic changes CLT208-0001 RULE-1239 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT208 MEDICAID-PAID-AMT 1 If MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-PAID-AMT CLT208











944 No logic changes CLT209-0001 RULE-1240 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT209 MEDICAID-FFS-EQUIVALENT-AMT 1 If MEDICAID-FFS-EQUIVALENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-FFS-EQUIVALENT-AMT CLT209











945 No logic changes CLT209-0002 RULE-1241 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT209 MEDICAID-FFS-EQUIVALENT-AMT 2 If TYPE-OF-CLAIM = "C", "3", or "W", then MEDICAID-FFS-EQUIVALENT-AMT must not be 8-filled 2443 Relational edit with MEDICAID-FFS-EQUIVALENT-AMT and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.hasValue(@secondaryRecord.MEDICAID-FFS-EQUIVALENT-AMT)' TYPE-OF-CLAIM CLT052 MEDICAID-FFS-EQUIVALENT-AMT CLT209

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



946 No logic changes CLT210-0001 RULE-1242 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT210 BILLING-UNIT 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: BILLING-UNIT BILLING-UNIT CLT210











947 No logic changes CLT211-0001 RULE-1243 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT211 TYPE-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-SERVICE TYPE-OF-SERVICE CLT211











948 No logic changes CLT211-0005 RULE-1244 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT211 TYPE-OF-SERVICE 2 If FILE-NAME = "CLAIMLT", then TYPE-OF-SERVICE must = 009, 044, 045, 046, 047, 048, 050, 059, OR 133 2434 Relational edit between TYPE-OF-SERVICE and FILE-NAME failed 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'fns.isEqualToAny(@val.TYPE-OF-SERVICE, "009", "044", "045", "046", "047", "048", "050", "059", "133")' TYPE-OF-SERVICE CLT211











949 Retired: Other reasons CLT212-0001
CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT212 SERVICING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























950 Logic updated: other CLT212-0006 RULE-1246 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT212 SERVICING-PROV-NUM 3 If ( SERVICING-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then SERVICING-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-LT-CLT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003 PROV-IDENTIFIERS PRV00005 For every record of type CLAIM-LINE-RECORD-LT, if fns.hasValue(@secondaryRecord.SERVICING-PROV-NUM) && !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type CLAIM-HEADER-RECORD-LT that matches on the join keys, where fns.isEqual(@tertiaryRecord.PROV-IDENTIFIER-TYPE, "1") TYPE-OF-CLAIM CLT052 SERVICING-PROV-NUM CLT212 PROV-IDENTIFIER-TYPE PRV077 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CLT017,CLT020,CLT019,CLT050 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CLT185,CLT189,CLT188,CLT233 SUBMITTING-STATE,SERVICING-PROV-NUM
SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081
951 Merged CLT213-0001 RULE-1248 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT213 SERVICING-PROV-NPI-NUM 1 If SERVICING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.SERVICING-PROV-NPI-NUM), then fns.isValidNPI(@val.SERVICING-PROV-NPI-NUM)' SERVICING-PROV-NPI-NUM CLT213











952 Merged CLT213-0002 RULE-1248 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT213 SERVICING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.SERVICING-PROV-NPI-NUM), then fns.isValidNPI(@val.SERVICING-PROV-NPI-NUM)' SERVICING-PROV-NPI-NUM CLT213











953 Logic updated: other CLT213-0006 RULE-1249 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT213 SERVICING-PROV-NPI-NUM 3 If ( SERVICING-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then SERVICING-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-LINE-RECORD-LT-CLT00003] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003 PROV-IDENTIFIERS PRV00005 For every record of type CLAIM-LINE-RECORD-LT, if fns.hasValue(@secondaryRecord.SERVICING-PROV-NUM) && !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type CLAIM-HEADER-RECORD-LT that matches on the join keys, where fns.isEqual(@tertiaryRecord.PROV-IDENTIFIER-TYPE, "2") TYPE-OF-CLAIM CLT052 SERVICING-PROV-NUM CLT212 PROV-IDENTIFIER-TYPE PRV077 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CLT017,CLT020,CLT019,CLT050 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CLT185,CLT189,CLT188,CLT233 SUBMITTING-STATE,SERVICING-PROV-NPI-NUM
SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081
954 No logic changes CLT214-0001 RULE-1250 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT214 SERVICING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY SERVICING-PROV-TAXONOMY CLT214











955 No logic changes CLT215-0001 RULE-1251 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT215 SERVICING-PROV-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE SERVICING-PROV-TYPE CLT215











956 No logic changes CLT216-0001 RULE-1252 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT216 SERVICING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY SERVICING-PROV-SPECIALTY CLT216











957 No logic changes CLT217-0001 RULE-1253 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT217 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION CLT217











958 No logic changes CLT218-0001 RULE-1254 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT218 BENEFIT-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: BENEFIT-TYPE BENEFIT-TYPE CLT218











959 No logic changes CLT219-0001 RULE-1255 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT219 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CLT219











960 No logic changes CLT219-0002 RULE-1256 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT219 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If CHIP-CODE [ELIGIBLE] = "0" , "1", or "2", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT must <> "02" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-LT-CLT00003] = MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] and SUBMITTING-STATE [CLAIM-LINE-RECORD-LT-CLT00003] = SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] 3034 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and CHIP-CODE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqualToAny(@primaryRecord.CHIP-CODE, "0", "1", "2"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "02")' CHIP-CODE ELG054 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CLT219

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT185,CLT187



961 No logic changes CLT219-0003 RULE-1257 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT219 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] = "0", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENTmust <> "01" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-LT-CLT00003] = MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] and SUBMITTING-STATE [CLAIM-LINE-RECORD-LT-CLT00003] = SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] 3035 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqual(@primaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "00"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "01")' MEDICAID-BASIS-OF-ELIGIBILITY ELG084 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CLT219

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT185,CLT187



962 No logic changes CLT221-0001 RULE-1258 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT221 PROV-FACILITY-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-FACILITY-TYPE PROV-FACILITY-TYPE CLT221











963 No logic changes CLT224-0001 RULE-1259 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT224 XIX-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: XIX-MBESCBES-CATEGORY-OF-SERVICE XIX-MBESCBES-CATEGORY-OF-SERVICE CLT224











964 No logic changes CLT224-0002 RULE-1260 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT224 XIX-MBESCBES-CATEGORY-OF-SERVICE 3 XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMLT] must <> ("14", "35", "42", or "44") where SEX = "M" [ELIGIBLE] and MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-LT-CLT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-LT-CLT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3015 Relational edit between XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMLT] and SEX [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.isEqual(@primaryRecord.SEX, "M"), then !fns.isEqualToAny(@secondaryRecord.XIX-MBESCBES-CATEGORY-OF-SERVICE, "14", "35", "42", "44")' SEX ELG023 XIX-MBESCBES-CATEGORY-OF-SERVICE CLT224

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CLT185,CLT187



965 No logic changes CLT225-0001 RULE-1261 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT225 XXI-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: XXI-MBESCBES-CATEGORY-OF-SERVICE XXI-MBESCBES-CATEGORY-OF-SERVICE CLT225











966 Logic updated: string matching CLT226-0001 RULE-1262 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT226 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION CLT226











967 Moved to R&C CLT227-0002
CLAIMLT FILE-HEADER-RECORD-LT-CLT00001 CLT227 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range

























968 Merged CLT228-0001 RULE-1264 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT228 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CLT228











969 Merged CLT228-0002 RULE-1264 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT228 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CLT228











970 Merged CLT228-0003 RULE-1264 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT228 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CLT228











971 No logic changes CLT229-0001 RULE-1267 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT229 NDC-UNIT-OF-MEASURE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: NDC-UNIT-OF-MEASURE NDC-UNIT-OF-MEASURE CLT229











972 No logic changes CLT230-0001 RULE-6661 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT230 NDC-QUANTITY 1 If NDC-QUANTITY is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: S9(6)V999 NDC-QUANTITY CLT230











973 No logic changes CLT231-0001 RULE-7002 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT231 HCPCS-RATE 1 If HCPCS-RATE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(14) HCPCS-RATE CLT231











974 Merged CLT233-0001 RULE-1270 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT233 ADJUDICATION-DATE 1 If ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CLT233











975 Merged CLT233-0002 RULE-1270 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT233 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CLT233











976 Logic updated: other CLT233-0006 RULE-1272 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT233 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-LT CLT00003 FILE-HEADER-RECORD-LT CLT00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE CLT233 END-OF-TIME-PERIOD CLT010









977 Logic updated: other CLT233-0007 RULE-1273 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT233 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be >= ADMISSION-DATE 2002 Relational edit between ADJUDICATION-DATE and ADMISSION-DATE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003

'if fns.hasValue(@primaryRecord.ADMISSION-DATE) && fns.hasValue(@secondaryRecord.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@primaryRecord.ADMISSION-DATE, @secondaryRecord.ADJUDICATION-DATE)' ADMISSION-DATE CLT044 ADJUDICATION-DATE CLT233

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT017,CLT019,CLT020,CLT050 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CLT185,CLT188,CLT189,CLT233



978 No logic changes CLT234-0001 RULE-1274 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT234 SELF-DIRECTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-LT CLT00003



If the field is populated, the value must be contained in the set of valid values with id: SELF-DIRECTION-TYPE SELF-DIRECTION-TYPE CLT234











979 Logic updated: string matching CLT235-0001 RULE-1275 CLAIMLT CLAIM-LINE-RECORD-LT-CLT00003 CLT235 PRE-AUTHORIZATION-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PRE-AUTHORIZATION-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.PRE-AUTHORIZATION-NUM), then fns.matches(@val.PRE-AUTHORIZATION-NUM, "^[^|*]*$")' PRE-AUTHORIZATION-NUM CLT235











980 Logic updated: string matching CLT237-0001 RULE-1276 CLAIMLT CLAIM-HEADER-RECORD-LT-CLT00002 CLT237 PROV-LOCATION-ID 1 If characters in text string are not alpha characters (A-Z), numbers (0-9) 120 Field contains invalid characters - PROV-LOCATION-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID CLT237











981 No logic changes COT001-0001 RULE-7076 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE COT001











982 Moved to R&C COT001-0004
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT001 RECORD-ID 2 If FILE-NAME = "CLAIM-OT", then the first 3 positions of RECORD-ID must = "COT" 150 Invalid or missing RECORD-ID

























983 Moved to R&C COT003-0001
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT003 SUBMISSION-TRANSACTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























984 Moved to R&C COT004-0001
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT004 FILE-ENCODING-SPECIFICATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























985 Moved to R&C COT006-0001
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT006 FILE-NAME 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























986 Moved to R&C COT007-0001
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT007 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























987 Moved to R&C COT007-0004
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























988 Merged COT008-0001 RULE-1284 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED COT008











989 Merged COT008-0002 RULE-1284 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED COT008











990 Merged COT008-0003 RULE-1284 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED COT008











991 Moved to R&C COT008-0004
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























992 Merged COT009-0001 RULE-1288 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD COT009











993 Merged COT009-0002 RULE-1288 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT009 START-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD COT009











994 Moved to R&C COT009-0003
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























995 Moved to R&C COT009-0004
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























996 Merged COT010-0001 RULE-1292 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT010 END-OF-TIME-PERIOD 1 If ENDING-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD COT010











997 Merged COT010-0002 RULE-1292 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD COT010











998 Moved to R&C COT010-0003
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT010 END-OF-TIME-PERIOD 2-M
2122


























999 Moved to R&C COT010-0004
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT010 END-OF-TIME-PERIOD 2-M
2019


























1,000 Moved to R&C COT011-0001
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT011 FILE-STATUS-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,001 Moved to R&C COT011-0002
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























1,002 Moved to R&C COT012-0001
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT012 SSN-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,003 Logic updated: other COT012-0002 RULE-1321 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT012 SSN-INDICATOR 3 Value for SSN-INDICATOR [CLAIMOT] must match SSN-INDICATOR [ELIGIBLE] 3009 Relational edit between SSN-INDICATOR [CLAIMOT] and SSN-INDICATOR [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) FILE-HEADER-RECORD-OT COT00001 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@primaryRecord.SSN-INDICATOR) && fns.hasValue(@secondaryRecord.SSN-INDICATOR), then fns.isEqual(@primaryRecord.SSN-INDICATOR, @secondaryRecord.SSN-INDICATOR)' SSN-INDICATOR COT012 SSN-INDICATOR ELG012

SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD COT007,COT009,COT010 SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD ELG007,ELG009,ELG010



1,004 No logic changes COT013-0001 RULE-1322 CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT013 TOT-REC-CNT 1 If TOT-REC-CNT = 0 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT COT013











1,005 Moved to R&C COT013-0002
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record

























1,006 Moved to R&C COT014-0001
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























1,007 No logic changes COT016-0001 RULE-6881 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE COT016











1,008 Moved to R&C COT016-0004
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT016 RECORD-ID 2 If FILE-NAME = "CLAIM-OT", then the first 3 positions of RECORD-ID must = "COT" 150 Invalid or missing RECORD-ID

























1,009 No logic changes COT017-0001 RULE-1327 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT017 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE COT017











1,010 Logic updated: other COT017-0004 RULE-1328 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-OT-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE COT017 SUBMITTING-STATE COT007









1,011 Retired: Other reasons COT018-0001
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT018 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,012 No logic changes COT018-0004 RULE-1330 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-HEADER-RECORD-OT COT00002



Field RECORD-NUMBER should be unique across all records of type CLAIM-HEADER-RECORD-OT RECORD-NUMBER COT018











1,013 Logic updated: string matching COT019-0001 RULE-1331 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT019 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ORIG 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG COT019











1,014 Logic updated: string matching COT020-0001 RULE-1332 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT020 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ COT020











1,015 No logic changes COT021-0001 RULE-7096 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT021 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported. 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID COT021











1,016 Retired: MSIS ID checks COT022-0001
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT022 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,017 Retired: MSIS ID checks COT022-0002
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT022 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,018 No logic changes COT022-0003 RULE-1336 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT022 MSIS-IDENTIFICATION-NUM 2 If TYPE-OF-CLAIM = "4", "D", OR "X", then the first byte of MSIS-IDENTIFICATION-NUM must = "&" 2331 Relational edit between MSIS-IDENTIFICATION-NUM and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "4", "D", "X"), then fns.matches(@val.MSIS-IDENTIFICATION-NUM, "^&.*$")' TYPE-OF-CLAIM,MSIS-IDENTIFICATION-NUM COT037,COT022











1,019 Logic updated: other COT022-0005 RULE-1337 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT022 MSIS-IDENTIFICATION-NUM 3 MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-OT-COT00002] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3026 Edit that claim has matching PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 record failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-OT COT00002

For every record of type CLAIM-HEADER-RECORD-OT, there must be a valid record of type PRIMARY-DEMOGRAPHICS-ELIGIBILITY that matches on the join keys





MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT022,COT017



1,020 No logic changes COT023-0001 RULE-1338 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT023 CROSSOVER-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CROSSOVER-INDICATOR CROSSOVER-INDICATOR COT023











1,021 No logic changes COT024-0001 RULE-1339 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT024 1115A-DEMONSTRATION-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: 1115A-DEMONSTRATION-IND 1115A-DEMONSTRATION-IND COT024











1,022 No logic changes COT024-0003 RULE-1340 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT024 1115A-DEMONSTRATION-IND 3 If 1115A-DEMONSTRATION-IND [ELIGIBLE] = 0or 8-filled, then 1115A-DEMONSTRATION-IND must = 0 or 8-filled where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-OT-COT00002] = MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] 3055 An 1115A-DEMONSTRATION-IND does not match the 1115A-DEMONSTRATION-IND in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) 1115A-DEMONSTRATION-INFORMATION ELG00018 CLAIM-HEADER-RECORD-OT COT00002

'if fns.isEqual(@primaryRecord.1115A-DEMONSTRATION-IND, "0") || !fns.hasValue(@primaryRecord.1115A-DEMONSTRATION-IND), then fns.isEqual(@secondaryRecord.1115A-DEMONSTRATION-IND, "0") || !fns.hasValue(@secondaryRecord.1115A-DEMONSTRATION-IND)' 1115A-DEMONSTRATION-IND ELG233 1115A-DEMONSTRATION-IND COT024

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG232,ELG230 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT022,COT017



1,023 No logic changes COT025-0001 RULE-1341 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT025 ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-IND ADJUSTMENT-IND COT025











1,024 No logic changes COT026-0001 RULE-1342 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT026 ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE ADJUSTMENT-REASON-CODE COT026











1,025 Merged COT027-0001 RULE-1343 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT027 DIAGNOSIS-CODE-1 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-1 COT027











1,026 Merged COT027-0002 RULE-1343 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT027 DIAGNOSIS-CODE-1 1 If DIAGNOSIS-CODE-1 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-1 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-1 COT027











1,027 No logic changes COT028-0001 RULE-1345 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT028 DIAGNOSIS-CODE-FLAG-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-1 COT028











1,028 No logic changes COT029-0001 RULE-1346 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT029 DIAGNOSIS-POA-FLAG-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-1 COT029











1,029 Merged COT030-0001 RULE-1347 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT030 DIAGNOSIS-CODE-2 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-2 COT030











1,030 Merged COT030-0002 RULE-1347 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT030 DIAGNOSIS-CODE-2 1 If DIAGNOSIS-CODE-2 is populated, it must contains valid characters. 120 Field contains invalid characters - DIAGNOSIS-CODE-2 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE DIAGNOSIS-CODE-2 COT030











1,031 No logic changes COT030-0007 RULE-1349 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT030 DIAGNOSIS-CODE-2 2 If DIAGNOSIS-CODE-2 is not 8-filled,
then DIAGNOSIS-CODE-2 must <> DIAGNOSIS-CODE-1		 2264 Relational edit between DIAGNOSIS-CODE-2 and DIAGNOSIS-CODE-1 failed (duplicate value entered) 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.DIAGNOSIS-CODE-2), then !fns.isEqual(@val.DIAGNOSIS-CODE-1, @val.DIAGNOSIS-CODE-2)' DIAGNOSIS-CODE-2,DIAGNOSIS-CODE-1 COT030,COT027











1,032 No logic changes COT031-0001 RULE-1350 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT031 DIAGNOSIS-CODE-FLAG-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-CODE-FLAG DIAGNOSIS-CODE-FLAG-2 COT031











1,033 No logic changes COT032-0001 RULE-1351 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT032 DIAGNOSIS-POA-FLAG-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-2 COT032











1,034 Merged COT033-0001 RULE-1352 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT033 BEGINNING-DATE-OF-SERVICE 1 If BEGINNING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE COT033











1,035 Merged COT033-0002 RULE-1352 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT033 BEGINNING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE COT033











1,036 Merged COT033-0003 RULE-1354 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT033 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2013 Relational edit between BEGINNING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE COT033 END-OF-TIME-PERIOD COT010









1,037 Merged COT033-0004 RULE-1355 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT033 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE COT033,COT034











1,038 Logic updated: other COT033-0005 RULE-1356 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT033 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-HEADER-RECORD-OT] 2008 Relational edit between BEGINNING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-HEADER-RECORD-OT]failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' ADJUDICATION-DATE,BEGINNING-DATE-OF-SERVICE COT035,COT033











1,039 Logic updated: other COT033-0006 RULE-1357 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT033 BEGINNING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then BEGINNING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-OT-COT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3002 Relational edit between BEGINNING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-OT COT00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 BEGINNING-DATE-OF-SERVICE COT033

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT022,COT017



1,040 Merged COT033-0010 RULE-1354 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT033 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE COT033 END-OF-TIME-PERIOD COT010









1,041 Merged COT034-0001 RULE-1359 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT034 ENDING-DATE-OF-SERVICE 1 If ENDING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE COT034











1,042 Merged COT034-0002 RULE-1359 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT034 ENDING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE COT034











1,043 Merged COT034-0003 RULE-1355 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT034 ENDING-DATE-OF-SERVICE 2-M
2012
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE COT033,COT034











1,044 Logic updated: other COT034-0004 RULE-1362 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT034 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-HEADER-RECORD-OT] 2038 Relational edit between ENDING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-HEADER-RECORD-OT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' ADJUDICATION-DATE,ENDING-DATE-OF-SERVICE COT035,COT034











1,045 Logic updated: other COT034-0005 RULE-1363 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT034 ENDING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then ENDING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-OT-COT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3005 Relational edit between ENDING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-OT COT00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.ENDING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ENDING-DATE-OF-SERVICE COT034

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT022,COT017



1,046 Logic updated: other COT034-0008 RULE-1364 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT034 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2036 Relational edit between ENDING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' ENDING-DATE-OF-SERVICE COT034 END-OF-TIME-PERIOD COT010









1,047 Merged COT035-0001 RULE-1365 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT035 ADJUDICATION-DATE 1 ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE COT035











1,048 Merged COT035-0002 RULE-1365 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT035 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE COT035











1,049 Logic updated: other COT035-0005 RULE-1367 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT035 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE COT035 END-OF-TIME-PERIOD COT010









1,050 Merged COT036-0001 RULE-1368 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT036 MEDICAID-PAID-DATE 1 If MEDICAID-PAID-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE COT036











1,051 Merged COT036-0002 RULE-1368 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT036 MEDICAID-PAID-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE COT036











1,052 No logic changes COT037-0001 RULE-1370 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT037 TYPE-OF-CLAIM 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-CLAIM TYPE-OF-CLAIM COT037











1,053 No logic changes COT038-0001 RULE-1371 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT038 TYPE-OF-BILL 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.TYPE-OF-BILL), then fns.isValidTypeOfBill(@val.TYPE-OF-BILL)' TYPE-OF-BILL COT038











1,054 No logic changes COT039-0001 RULE-1372 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT039 CLAIM-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-STATUS COT039











1,055 No logic changes COT040-0001 RULE-1373 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT040 CLAIM-STATUS-CATEGORY 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS-CATEGORY CLAIM-STATUS-CATEGORY COT040











1,056 No logic changes COT041-0001 RULE-1374 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT041 SOURCE-LOCATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: SOURCE-LOCATION SOURCE-LOCATION COT041











1,057 Logic updated: string matching COT042-0001 RULE-1375 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT042 CHECK-NUM 1 If CHECK-NUM is populated, it must contains valid characters. 120 Field contains invalid characters - CHECK-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.CHECK-NUM), then fns.matches(@val.CHECK-NUM, "^[^|*]*$")' CHECK-NUM COT042











1,058 Merged COT043-0001 RULE-1376 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT043 CHECK-EFF-DATE 1 If CHECK-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE COT043











1,059 Merged COT043-0002 RULE-1376 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT043 CHECK-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE COT043











1,060 No logic changes COT044-0001 RULE-1378 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT044 CLAIM-PYMT-REM-CODE-1 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-1 COT044











1,061 Merged COT044-0002 RULE-1379 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT044 CLAIM-PYMT-REM-CODE-1 2 If CLAIM-PYMT-REM-CODE-1 is not 8-filled, then CLAIM-PYMT-REM-CODE-1 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 COT044,COT045,COT046,COT047











1,062 No logic changes COT045-0001 RULE-1380 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT045 CLAIM-PYMT-REM-CODE-2 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-2 COT045











1,063 Merged COT045-0002 RULE-1379 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT045 CLAIM-PYMT-REM-CODE-2 2 If CLAIM-PYMT-REM-CODE-2 is not 8-filled, then CLAIM-PYMT-REM-CODE-2 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 COT044,COT045,COT046,COT047











1,064 No logic changes COT045-0003 RULE-1382 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT045 CLAIM-PYMT-REM-CODE-2 2 CLAIM-PYMT-REM-CODE-2 must be 8-filled if value for CLAIM-PYMT-REM-CODE-1 is 8-filled 2243 Relational edit between CLAIM-PYMT-REM-CODE-2 and CLAIM-PYMT-REM-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-1), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2)' CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2 COT044,COT045











1,065 No logic changes COT046-0001 RULE-1383 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT046 CLAIM-PYMT-REM-CODE-3 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-3 COT046











1,066 Merged COT046-0002 RULE-1379 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT046 CLAIM-PYMT-REM-CODE-3 2 If CLAIM-PYMT-REM-CODE-3 is not 8-filled, then CLAIM-PYMT-REM-CODE-3 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 COT044,COT045,COT046,COT047











1,067 No logic changes COT046-0003 RULE-1385 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT046 CLAIM-PYMT-REM-CODE-3 2 CLAIM-PYMT-REM-CODE-3 must be 8-filled if value for CLAIM-PYMT-REM-CODE-2 is 8-filled 2244 Relational edit between CLAIM-PYMT-REM-CODE-3 and CLAIM-PYMT-REM-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3)' CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3 COT045,COT046











1,068 No logic changes COT047-0001 RULE-1386 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT047 CLAIM-PYMT-REM-CODE-4 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-4 COT047











1,069 Merged COT047-0002 RULE-1379 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT047 CLAIM-PYMT-REM-CODE-4 2 If CLAIM-PYMT-REM-CODE-4 is not 8-filled, then CLAIM-PYMT-REM-CODE-4 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 COT044,COT045,COT046,COT047











1,070 No logic changes COT047-0003 RULE-1388 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT047 CLAIM-PYMT-REM-CODE-4 2 CLAIM-PYMT-REM-CODE-4 must be 8-filled if value for CLAIM-PYMT-REM-CODE-3 is 8-filled 2245 Relational edit between CLAIM-PYMT-REM-CODE-4 and CLAIM-PYMT-REM-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-4)' CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 COT046,COT047











1,071 No logic changes COT048-0001 RULE-1389 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT048 TOT-BILLED-AMT 1 If TOT-BILLED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-BILLED-AMT COT048











1,072 No logic changes COT048-0003 RULE-1390 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT048 TOT-BILLED-AMT 2 If TYPE-OF-CLAIM = "4", "D", or "X", then TOT-BILLED-AMT must = 0 2426 Relational edit between TOT-BILLED-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "4", "D", "X"), then fns.isEqual(@val.TOT-BILLED-AMT, "0.00")' TYPE-OF-CLAIM,TOT-BILLED-AMT COT037,COT048











1,073 No logic changes COT048-0005 RULE-1391 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT048 TOT-BILLED-AMT 2 The absolute value of the sum of BILLED-AMT on each detail line record must = absolute value of TOT-BILLED-AMT 2425 Relational edit between TOT-BILLED-AMT and BILLED-AMT 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'fns.isDollarSumEqual(@primaryRecord.TOT-BILLED-AMT, @secondaryRecords.BILLED-AMT)' TOT-BILLED-AMT COT048 BILLED-AMT COT174

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,074 No logic changes COT049-0001 RULE-1392 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT049 TOT-ALLOWED-AMT 1 If TOT-ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-ALLOWED-AMT COT049











1,075 No logic changes COT049-0002 RULE-1393 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT049 TOT-ALLOWED-AMT 2 TOT-ALLOWED-AMT must = the sum of ALLOWED-AMT at each claim line level, where SUBMITTING-STATE, ICN-ORIG, and ICN-ADJ match 2125 Relational edit between TOT-ALLOWED-AMT and ALLOWED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'fns.isDollarSumEqual(@primaryRecord.TOT-ALLOWED-AMT, @secondaryRecords.ALLOWED-AMT)' TOT-ALLOWED-AMT COT049 ALLOWED-AMT COT175

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,076 No logic changes COT050-0001 RULE-1394 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT050 TOT-MEDICAID-PAID-AMT 1 If TOT-MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICAID-PAID-AMT COT050











1,077 No logic changes COT051-0001 RULE-1395 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT051 TOT-COPAY-AMT 1 If TOT-COPAY-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-COPAY-AMT COT051











1,078 No logic changes COT052-0001 RULE-1396 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT052 TOT-MEDICARE-DEDUCTIBLE-AMT 1 If TOT-MEDICARE-DEDUCTIBLE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-DEDUCTIBLE-AMT COT052











1,079 Logic updated: other COT052-0002 RULE-1397 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT052 TOT-MEDICARE-DEDUCTIBLE-AMT 2 TOT-MEDICARE-DEDUCIBLE-AMT must be <=TOT-BILLED-AMT 2127 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT) && fns.hasValue(@val.TOT-BILLED-AMT), then fns.isLessThanOrEqual(@val.TOT-MEDICARE-DEDUCTIBLE-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-BILLED-AMT COT052,COT048











1,080 Merged COT052-0003 RULE-1402 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT052 TOT-MEDICARE-DEDUCTIBLE-AMT 2 If TOT-MEDICARE-COINS-AMT is 8-filled, then TOT-MEDICARE-DEDUCIBLE-AMT must be 8-filled 2431 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and TOT-MEDICARE-COINS-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if and only if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-MEDICARE-COINS-AMT COT052,COT053











1,081 No logic changes COT053-0001 RULE-1399 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT053 TOT-MEDICARE-COINS-AMT 1 If TOT-MEDICARE-COINS-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-COINS-AMT COT053











1,082 No logic changes COT053-0002 RULE-1400 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT053 TOT-MEDICARE-COINS-AMT 2 If TYPE-OF-CLAIM = "3", "C", "W", then TOT-MEDICARE-COINS-AMT must be 8-filled 2429 Relational edit between TOT-MEDICARE-COINS-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then !fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TYPE-OF-CLAIM,TOT-MEDICARE-COINS-AMT COT037,COT053











1,083 Logic updated: other COT053-0003 RULE-1401 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT053 TOT-MEDICARE-COINS-AMT 2 TOT-MEDICARE-COINS-AMT must be < TOT-BILLED-AMT 2126 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-BILLED-AMT), then fns.isLessThan(@val.TOT-MEDICARE-COINS-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-COINS-AMT,TOT-BILLED-AMT COT053,COT048











1,084 Merged COT053-0004 RULE-1402 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT053 TOT-MEDICARE-COINS-AMT 2 If TOT-MEDICARE-DEDUCTIBLE-AMT is 8-filled, then TOT-MEDICARE-COINS-AMT must be 8-filled. 2428 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-MEDICARE-DEDUCTIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if and only if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-MEDICARE-COINS-AMT COT052,COT053











1,085 No logic changes COT053-0005 RULE-1403 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT053 TOT-MEDICARE-COINS-AMT 2 If MEDICARE-COMB-DED-IND = "1", then TOT-MEDICARE-COINS-AMT must = 0 2427 Relational edit between TOT-MEDICARE-COINS-AMT and MEDICARE-COMB-DED-IND 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqual(@val.MEDICARE-COMB-DED-IND, "1"), then fns.isEqual(@val.TOT-MEDICARE-COINS-AMT, "0.00")' MEDICARE-COMB-DED-IND,TOT-MEDICARE-COINS-AMT COT064,COT053











1,086 No logic changes COT054-0001 RULE-1404 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT054 TOT-TPL-AMT 1 If TOT-TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-TPL-AMT COT054











1,087 Logic updated: other COT054-0002 RULE-1405 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT054 TOT-TPL-AMT 2 The absolute value of TOT-TPL-AMT must be <= the absolute value of (TOT-BILLED-AMT minus TOT-MEDICARE-COINS-AMT plus TOT-MEDICARE-DEDUCIBLE-AMT) 2432 Relational edit between TOT-TPL-AMT, TOT-BILLED-AMT, MEDICARE-COINS-AMT, and TOT-MEDICARE-DEDUCIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.TOT-TPL-AMT) && fns.hasValue(@val.TOT-BILLED-AMT) && fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.isLessThanOrEqual(@val.TOT-TPL-AMT, fns.remainingLiability(@val.TOT-BILLED-AMT, @val.TOT-MEDICARE-COINS-AMT, @val.TOT-MEDICARE-DEDUCTIBLE-AMT))' TOT-TPL-AMT,TOT-BILLED-AMT,TOT-MEDICARE-COINS-AMT,TOT-MEDICARE-DEDUCTIBLE-AMT COT054,COT048,COT053,COT052











1,088 No logic changes COT056-0001 RULE-1406 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT056 TOT-OTHER-INSURANCE-AMT 1 If TOT-OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-OTHER-INSURANCE-AMT COT056











1,089 No logic changes COT057-0001 RULE-1407 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT057 OTHER-INSURANCE-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-INSURANCE-IND OTHER-INSURANCE-IND COT057











1,090 No logic changes COT058-0001 RULE-1408 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT058 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION COT058











1,091 No logic changes COT059-0001 RULE-1409 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT059 SERVICE-TRACKING-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: SERVICE-TRACKING-TYPE SERVICE-TRACKING-TYPE COT059











1,092 No logic changes COT060-0001 RULE-1410 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT060 SERVICE-TRACKING-PAYMENT-AMT 1 If SERVICE-TRACKING-PAYMENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 SERVICE-TRACKING-PAYMENT-AMT COT060











1,093 No logic changes COT060-0004 RULE-1411 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT060 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE <> "00" AND (TOT-MEDICAID-PAID-AMT = 0 ), then SERVICE-TRACKING-PAYMENT-AMT must be > 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if !fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isEqual(@val.TOT-MEDICAID-PAID-AMT, "0.00"), then fns.isGreaterThanZero(@val.SERVICE-TRACKING-PAYMENT-AMT)' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT COT059,COT050,COT060











1,094 No logic changes COT060-0006 RULE-1412 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT060 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE = "00" AND (TOT-MEDICAID-PAID-AMT > 0), then SERVICE-TRACKING-PAYMENT-AMT must = 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isGreaterThanZero(@val.TOT-MEDICAID-PAID-AMT), then fns.isEqual(@val.SERVICE-TRACKING-PAYMENT-AMT, "0.00")' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT COT059,COT050,COT060











1,095 No logic changes COT061-0001 RULE-1413 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT061 FIXED-PAYMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: FIXED-PAYMENT-IND FIXED-PAYMENT-IND COT061











1,096 No logic changes COT062-0001 RULE-1414 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT062 FUNDING-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-CODE FUNDING-CODE COT062











1,097 No logic changes COT063-0001 RULE-1415 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT063 FUNDING-SOURCE-NONFEDERAL-SHARE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-SOURCE-NONFEDERAL-SHARE FUNDING-SOURCE-NONFEDERAL-SHARE COT063











1,098 No logic changes COT064-0001 RULE-1416 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT064 MEDICARE-COMB-DED-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-COMB-DED-IND MEDICARE-COMB-DED-IND COT064











1,099 No logic changes COT064-0006 RULE-1417 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT064 MEDICARE-COMB-DED-IND 2 If CROSSOVER-INDICATOR = "0" or TYPE-OF-CLAIM = "3", "C", or "W", then MEDICARE-COMB-DED-IND must = 0 2328 Relational edit between MEDICARE-COMB-DED-IND, CROSSOVER-INDICATOR, and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "0") || fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then fns.isEqual(@val.MEDICARE-COMB-DED-IND, "0")' CROSSOVER-INDICATOR,TYPE-OF-CLAIM,MEDICARE-COMB-DED-IND COT023,COT037,COT064











1,100 No logic changes COT065-0001 RULE-1418 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT065 PROGRAM-TYPE 1 Valueis not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROGRAM-TYPE PROGRAM-TYPE COT065











1,101 No logic changes COT065-0002 RULE-1419 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT065 PROGRAM-TYPE 2 If PROGRAM-TYPE = "07", then WAIVER-TYPE must = "06" through "20" 2388 Relational edit between PROGRAM-TYPE and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqual(@val.PROGRAM-TYPE, "07"), then fns.isEqualToAny(@val.WAIVER-TYPE, "06", "07", "08", "09", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20")' PROGRAM-TYPE,WAIVER-TYPE COT065,COT110











1,102 No logic changes COT065-0004 RULE-1420 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT065 PROGRAM-TYPE 3 If PROGRAM-TYPE = "13", then STATE-PLAN-OPTION-TYPE [ELIGIBLE] must = "02" where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] 3047 Relational edit between PROGRAM TYPE and STATE-PLAN-OPTION-TYPE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) STATE-PLAN-OPTION-PARTICIPATION ELG00011 CLAIM-HEADER-RECORD-OT COT00002

'if fns.isEqual(@secondaryRecord.PROGRAM-TYPE, "13"), then fns.isEqual(@primaryRecord.STATE-PLAN-OPTION-TYPE, "02")' STATE-PLAN-OPTION-TYPE ELG163 PROGRAM-TYPE COT065

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG162,ELG160 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT022,COT017



1,103 Logic updated: string matching COT066-0001 RULE-1421 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT066 PLAN-ID-NUMBER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PLAN-ID-NUMBER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.PLAN-ID-NUMBER), then fns.matches(@val.PLAN-ID-NUMBER, "^[^|*]*$")' PLAN-ID-NUMBER COT066











1,104 No logic changes COT066-0004 RULE-1422 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT066 PLAN-ID-NUMBER 2 If TYPE-OF-CLAIM <> "3", "C" or "W" or TYPE-OF-SERVICE <> "119", "120", "121", or "122", then PLAN-ID-NUMBER must be 8-filled 2365 Relational edit between PLAN-ID-NUM, TYPE-OF-CLAIM, and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W") || !fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@primaryRecord.PLAN-ID-NUMBER)' TYPE-OF-CLAIM,PLAN-ID-NUMBER COT037,COT066 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,105 No logic changes COT066-0005 RULE-1423 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT066 PLAN-ID-NUMBER 2 If TYPE-OF-SERVICE = "119", "120", OR "122", then PLAN-ID-NUM must = BILLING-PROV-NUM 2364 Relational edit between PLAN-ID-NUM, BILLING-PROV-NUM, and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "122"), then fns.isEqual(@primaryRecord.PLAN-ID-NUMBER, @primaryRecord.BILLING-PROV-NUM)' PLAN-ID-NUMBER,BILLING-PROV-NUM COT066,COT112 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,106 Logic updated: string matching COT067-0001 RULE-1424 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT067 NATIONAL-HEALTH-CARE-ENTITY-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-ID, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-ID COT067











1,107 No logic changes COT067-0003 RULE-1425 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT067 NATIONAL-HEALTH-CARE-ENTITY-ID 2 If START-OF-TIME-PERIOD >= 20151105, then NATIONAL-HEALTH-CARE-ENTITY-ID must not be (8-filled or 9-filled) 2332 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 FILE-HEADER-RECORD-OT COT00001

'if fns.isGreaterThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, "2015-11-05"), then fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID COT067 START-OF-TIME-PERIOD COT009









1,108 No logic changes COT067-0004 RULE-1426 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT067 NATIONAL-HEALTH-CARE-ENTITY-ID 3 If TYPE-OF-CLAIM = "C", "3", or "W", then NATIONAL-HEALTH-CARE-ENTITY-ID [CLAIM-HEADER-RECORD-OT-COT00002] must = NATIONAL-HEALTH-CARE-ENTITY-ID [MANAGED-CARE-PARTICIPTATION-ELG00014], where SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] and MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-OT-COT00002] = MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014] 3027 Edit that NATIONAL-HEALTH-CARE-ENTITY-ID matches value in MANAGED-CARE-PARTICIPATION-ELG00014 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) MANAGED-CARE-PARTICIPATION ELG00014 CLAIM-HEADER-RECORD-OT COT00002

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.isEqual(@primaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID, @secondaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID ELG194 TYPE-OF-CLAIM,NATIONAL-HEALTH-CARE-ENTITY-ID COT037,COT067

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG191,ELG189 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT022,COT017



1,109 No logic changes COT068-0001 RULE-1427 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT068 PAYMENT-LEVEL-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PAYMENT-LEVEL-IND PAYMENT-LEVEL-IND COT068











1,110 No logic changes COT069-0001 RULE-1428 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT069 MEDICARE-REIM-TYPE 1 Value must be a valid value 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-REIM-TYPE MEDICARE-REIM-TYPE COT069











1,111 Retired: required value checks COT070-0001
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT070 CLAIM-LINE-COUNT 1 If CLAIM-LINE-COUNT =0 113 Required data element has not been reported.

























1,112 Logic updated: other COT070-0003 RULE-1430 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT070 CLAIM-LINE-COUNT 2 CLAIM-LINE-COUNT must = total number of lines in the claim 2445 Value does not equal the total number of lines in the claim 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.hasValue(@primaryRecord.CLAIM-LINE-COUNT), then fns.isValueEqualToNumberOfRecords(@primaryRecord.CLAIM-LINE-COUNT, @secondaryRecords.LINE-NUM-ORIG)' CLAIM-LINE-COUNT COT070 LINE-NUM-ORIG COT160

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,113 No logic changes COT072-0001 RULE-1431 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT072 FORCED-CLAIM-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: FORCED-CLAIM-IND FORCED-CLAIM-IND COT072











1,114 No logic changes COT073-0001 RULE-1432 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT073 HEALTH-CARE-ACQUIRED-CONDITION-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-CARE-ACQUIRED-CONDITION-IND HEALTH-CARE-ACQUIRED-CONDITION-IND COT073











1,115 No logic changes COT074-0001 RULE-1433 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT074 OCCURRENCE-CODE-01 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-01 COT074











1,116 No logic changes COT075-0001 RULE-1434 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT075 OCCURRENCE-CODE-02 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-02 COT075











1,117 No logic changes COT076-0001 RULE-1435 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT076 OCCURRENCE-CODE-03 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-03 COT076











1,118 No logic changes COT077-0001 RULE-1436 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT077 OCCURRENCE-CODE-04 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-04 COT077











1,119 No logic changes COT078-0001 RULE-1437 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT078 OCCURRENCE-CODE-05 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-05 COT078











1,120 No logic changes COT079-0001 RULE-1438 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT079 OCCURRENCE-CODE-06 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-06 COT079











1,121 No logic changes COT080-0001 RULE-1439 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT080 OCCURRENCE-CODE-07 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-07 COT080











1,122 No logic changes COT081-0001 RULE-1440 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT081 OCCURRENCE-CODE-08 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-08 COT081











1,123 No logic changes COT082-0001 RULE-1441 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT082 OCCURRENCE-CODE-09 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-09 COT082











1,124 No logic changes COT083-0001 RULE-1442 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT083 OCCURRENCE-CODE-10 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: OCCURRENCE-CODE OCCURRENCE-CODE-10 COT083











1,125 Merged COT084-0001 RULE-1443 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT084 OCCURRENCE-CODE-EFF-DATE-01 1 If OCCURRENCE-CODE-EFF-DATE-01 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-01 COT084











1,126 Merged COT084-0002 RULE-1443 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT084 OCCURRENCE-CODE-EFF-DATE-01 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-01 COT084











1,127 No logic changes COT084-0003 RULE-1445 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT084 OCCURRENCE-CODE-EFF-DATE-01 2 If OCCURRENCE-CODE-01 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-01 must not be 8-filled 2337 Relational edit between OCCURRENCE-CODE-01 and OCCURRENCE-CODE-EFF-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-01), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01)' OCCURRENCE-CODE-01,OCCURRENCE-CODE-EFF-DATE-01 COT074,COT084











1,128 Merged COT084-0005 RULE-1446 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT084 OCCURRENCE-CODE-EFF-DATE-01 2 OCCURRENCE-CODE-EFF-DATE-01 must be <= OCCURRENCE-CODE-END-DATE-01 2069 Relational edit between OCCURRENCE-CODE-EFF-DATE-01 and OCCURRENCE-CODE-END-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-01, @val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-EFF-DATE-01,OCCURRENCE-CODE-END-DATE-01 COT084,COT094











1,129 Merged COT085-0001 RULE-1447 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT085 OCCURRENCE-CODE-EFF-DATE-02 1 If OCCURRENCE-CODE-EFF-DATE-02 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-02 COT085











1,130 Merged COT085-0002 RULE-1447 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT085 OCCURRENCE-CODE-EFF-DATE-02 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-02 COT085











1,131 No logic changes COT085-0003 RULE-1449 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT085 OCCURRENCE-CODE-EFF-DATE-02 2 If OCCURRENCE-CODE-02 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-02 must not be 8-filled 2339 Relational edit between OCCURRENCE-CODE-02 and OCCURRENCE-CODE-EFF-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-02), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-02)' OCCURRENCE-CODE-02,OCCURRENCE-CODE-EFF-DATE-02 COT075,COT085











1,132 Merged COT085-0005 RULE-1450 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT085 OCCURRENCE-CODE-EFF-DATE-02 2 OCCURRENCE-CODE-EFF-DATE-02 must be <= OCCURRENCE-CODE-END-DATE-02 2070 Relational edit between OCCURRENCE-CODE-EFF-DATE-02 and OCCURRENCE-CODE-END-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-02) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-02), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-02, @val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-EFF-DATE-02,OCCURRENCE-CODE-END-DATE-02 COT085,COT095











1,133 Merged COT086-0001 RULE-1451 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT086 OCCURRENCE-CODE-EFF-DATE-03 1 If OCCURRENCE-CODE-EFF-DATE-03 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-03 COT086











1,134 Merged COT086-0002 RULE-1451 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT086 OCCURRENCE-CODE-EFF-DATE-03 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-03 COT086











1,135 No logic changes COT086-0003 RULE-1453 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT086 OCCURRENCE-CODE-EFF-DATE-03 2 If OCCURRENCE-CODE-03 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-03 must not be 8-filled 2341 Relational edit between OCCURRENCE-CODE-03 and OCCURRENCE-CODE-EFF-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-03), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03)' OCCURRENCE-CODE-03,OCCURRENCE-CODE-EFF-DATE-03 COT076,COT086











1,136 Merged COT086-0005 RULE-1454 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT086 OCCURRENCE-CODE-EFF-DATE-03 2 OCCURRENCE-CODE-EFF-DATE-03 must be <= OCCURRENCE-CODE-END-DATE-03 2071 Relational edit between OCCURRENCE-CODE-EFF-DATE-03 and OCCURRENCE-CODE-END-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-03, @val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-EFF-DATE-03,OCCURRENCE-CODE-END-DATE-03 COT086,COT096











1,137 Merged COT087-0001 RULE-1455 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT087 OCCURRENCE-CODE-EFF-DATE-04 1 If OCCURRENCE-CODE-EFF-DATE-04 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-04 COT087











1,138 Merged COT087-0002 RULE-1455 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT087 OCCURRENCE-CODE-EFF-DATE-04 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-04 COT087











1,139 No logic changes COT087-0003 RULE-1457 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT087 OCCURRENCE-CODE-EFF-DATE-04 2 If OCCURRENCE-CODE-04 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-04 must not be 8-filled 2343 Relational edit between OCCURRENCE-CODE-04 and OCCURRENCE-CODE-EFF-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-04), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04)' OCCURRENCE-CODE-04,OCCURRENCE-CODE-EFF-DATE-04 COT077,COT087











1,140 Merged COT087-0005 RULE-1458 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT087 OCCURRENCE-CODE-EFF-DATE-04 2 OCCURRENCE-CODE-EFF-DATE-04 must be <= OCCURRENCE-CODE-END-DATE-04 2072 Relational edit between OCCURRENCE-CODE-EFF-DATE-04 and OCCURRENCE-CODE-END-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-04, @val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-EFF-DATE-04,OCCURRENCE-CODE-END-DATE-04 COT087,COT097











1,141 Merged COT088-0001 RULE-1459 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT088 OCCURRENCE-CODE-EFF-DATE-05 1 If OCCURRENCE-CODE-EFF-DATE-05 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-05 COT088











1,142 Merged COT088-0002 RULE-1459 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT088 OCCURRENCE-CODE-EFF-DATE-05 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-05 COT088











1,143 No logic changes COT088-0003 RULE-1461 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT088 OCCURRENCE-CODE-EFF-DATE-05 2 If OCCURRENCE-CODE-05 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-05 must not be 8-filled 2345 Relational edit between OCCURRENCE-CODE-05 and OCCURRENCE-CODE-EFF-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-05), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05)' OCCURRENCE-CODE-05,OCCURRENCE-CODE-EFF-DATE-05 COT078,COT088











1,144 Merged COT088-0005 RULE-1462 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT088 OCCURRENCE-CODE-EFF-DATE-05 2 OCCURRENCE-CODE-EFF-DATE-05 must be <= OCCURRENCE-CODE-END-DATE-05 2073 Relational edit between OCCURRENCE-CODE-EFF-DATE-05 and OCCURRENCE-CODE-END-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-05, @val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-EFF-DATE-05,OCCURRENCE-CODE-END-DATE-05 COT088,COT098











1,145 Merged COT089-0001 RULE-1463 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT089 OCCURRENCE-CODE-EFF-DATE-06 1 If OCCURRENCE-CODE-EFF-DATE-06 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-06 COT089











1,146 Merged COT089-0002 RULE-1463 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT089 OCCURRENCE-CODE-EFF-DATE-06 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-06 COT089











1,147 No logic changes COT089-0003 RULE-1465 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT089 OCCURRENCE-CODE-EFF-DATE-06 2 If OCCURRENCE-CODE-06 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-06 must not be 8-filled 2347 Relational edit between OCCURRENCE-CODE-06 and OCCURRENCE-CODE-EFF-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-06), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06)' OCCURRENCE-CODE-06,OCCURRENCE-CODE-EFF-DATE-06 COT079,COT089











1,148 Merged COT089-0005 RULE-1466 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT089 OCCURRENCE-CODE-EFF-DATE-06 2 OCCURRENCE-CODE-EFF-DATE-06 must be <= OCCURRENCE-CODE-END-DATE-06 2074 Relational edit between OCCURRENCE-CODE-EFF-DATE-06 and OCCURRENCE-CODE-END-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-06, @val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-EFF-DATE-06,OCCURRENCE-CODE-END-DATE-06 COT089,COT099











1,149 Merged COT090-0001 RULE-1467 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT090 OCCURRENCE-CODE-EFF-DATE-07 1 If OCCURRENCE-CODE-EFF-DATE-07 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-07 COT090











1,150 Merged COT090-0002 RULE-1467 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT090 OCCURRENCE-CODE-EFF-DATE-07 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-07 COT090











1,151 No logic changes COT090-0003 RULE-1469 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT090 OCCURRENCE-CODE-EFF-DATE-07 2 If OCCURRENCE-CODE-07 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-07 must not be 8-filled 2349 Relational edit between OCCURRENCE-CODE-07 and OCCURRENCE-CODE-EFF-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-07), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07)' OCCURRENCE-CODE-07,OCCURRENCE-CODE-EFF-DATE-07 COT080,COT090











1,152 Merged COT090-0005 RULE-1470 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT090 OCCURRENCE-CODE-EFF-DATE-07 2 OCCURRENCE-CODE-EFF-DATE-07 must be <= OCCURRENCE-CODE-END-DATE-07 2075 Relational edit between OCCURRENCE-CODE-EFF-DATE-07 and OCCURRENCE-CODE-END-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-07, @val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-EFF-DATE-07,OCCURRENCE-CODE-END-DATE-07 COT090,COT100











1,153 Merged COT091-0001 RULE-1471 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT091 OCCURRENCE-CODE-EFF-DATE-08 1 If OCCURRENCE-CODE-EFF-DATE-08 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-08 COT091











1,154 Merged COT091-0002 RULE-1471 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT091 OCCURRENCE-CODE-EFF-DATE-08 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-08 COT091











1,155 No logic changes COT091-0003 RULE-1473 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT091 OCCURRENCE-CODE-EFF-DATE-08 2 If OCCURRENCE-CODE-08 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-08 must not be 8-filled 2351 Relational edit between OCCURRENCE-CODE-08 and OCCURRENCE-CODE-EFF-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-08), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08)' OCCURRENCE-CODE-08,OCCURRENCE-CODE-EFF-DATE-08 COT081,COT091











1,156 Merged COT091-0005 RULE-1474 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT091 OCCURRENCE-CODE-EFF-DATE-08 2 OCCURRENCE-CODE-EFF-DATE-08 must be <= OCCURRENCE-CODE-END-DATE-08 2076 Relational edit between OCCURRENCE-CODE-EFF-DATE-08 and OCCURRENCE-CODE-END-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-08, @val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-EFF-DATE-08,OCCURRENCE-CODE-END-DATE-08 COT091,COT101











1,157 Merged COT092-0001 RULE-1475 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT092 OCCURRENCE-CODE-EFF-DATE-09 1 If OCCURRENCE-CODE-EFF-DATE-09 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-09 COT092











1,158 Merged COT092-0002 RULE-1475 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT092 OCCURRENCE-CODE-EFF-DATE-09 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-09 COT092











1,159 No logic changes COT092-0003 RULE-1477 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT092 OCCURRENCE-CODE-EFF-DATE-09 2 If OCCURRENCE-CODE-09 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-09 must not be 8-filled 2353 Relational edit between OCCURRENCE-CODE-09 and OCCURRENCE-CODE-EFF-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-09), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09)' OCCURRENCE-CODE-09,OCCURRENCE-CODE-EFF-DATE-09 COT082,COT092











1,160 Merged COT092-0005 RULE-1478 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT092 OCCURRENCE-CODE-EFF-DATE-09 2 OCCURRENCE-CODE-EFF-DATE-09 must be <= OCCURRENCE-CODE-END-DATE-09 2077 Relational edit between OCCURRENCE-CODE-EFF-DATE-09 and OCCURRENCE-CODE-END-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-09, @val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-EFF-DATE-09,OCCURRENCE-CODE-END-DATE-09 COT092,COT102











1,161 Merged COT093-0001 RULE-1479 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT093 OCCURRENCE-CODE-EFF-DATE-10 1 If OCCURRENCE-CODE-EFF-DATE-10 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-10 COT093











1,162 Merged COT093-0002 RULE-1479 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT093 OCCURRENCE-CODE-EFF-DATE-10 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-EFF-DATE-10 COT093











1,163 No logic changes COT093-0003 RULE-1481 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT093 OCCURRENCE-CODE-EFF-DATE-10 2 If OCCURRENCE-CODE-10 is not 8-filled, then OCCURRENCE-CODE-EFF-DATE-10 must not be 8-filled 2355 Relational edit between OCCURRENCE-CODE-10 and OCCURRENCE-CODE-EFF-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-10), then fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-10)' OCCURRENCE-CODE-10,OCCURRENCE-CODE-EFF-DATE-10 COT083,COT093











1,164 Merged COT093-0005 RULE-1482 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT093 OCCURRENCE-CODE-EFF-DATE-10 2 OCCURRENCE-CODE-EFF-DATE-10 must be <= OCCURRENCE-CODE-END-DATE-10 2078 Relational edit between OCCURRENCE-CODE-EFF-DATE-10 and OCCURRENCE-CODE-END-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-10) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-10), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-10, @val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-EFF-DATE-10,OCCURRENCE-CODE-END-DATE-10 COT093,COT103











1,165 Merged COT094-0001 RULE-1483 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT094 OCCURRENCE-CODE-END-DATE-01 1 If OCCURRENCE-CODE-END-DATE-01 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-01 COT094











1,166 Merged COT094-0002 RULE-1483 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT094 OCCURRENCE-CODE-END-DATE-01 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-01 COT094











1,167 No logic changes COT094-0004 RULE-1485 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT094 OCCURRENCE-CODE-END-DATE-01 2 If OCCURRENCE-CODE-01 is not 8-filled, then OCCURRENCE-CODE-END-DATE-01 must not be 8-filled 2338 Relational edit between OCCURRENCE-CODE-01 and OCCURRENCE-CODE-END-DATE-01 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-01), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-01,OCCURRENCE-CODE-END-DATE-01 COT074,COT094











1,168 Merged COT094-0006 RULE-1446 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT094 OCCURRENCE-CODE-END-DATE-01 2-M
2069
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-01) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-01), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-01, @val.OCCURRENCE-CODE-END-DATE-01)' OCCURRENCE-CODE-EFF-DATE-01,OCCURRENCE-CODE-END-DATE-01 COT084,COT094











1,169 Merged COT095-0001 RULE-1487 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT095 OCCURRENCE-CODE-END-DATE-02 1 If OCCURRENCE-CODE-END-DATE-02 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-02 COT095











1,170 Merged COT095-0002 RULE-1487 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT095 OCCURRENCE-CODE-END-DATE-02 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-02 COT095











1,171 No logic changes COT095-0004 RULE-1489 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT095 OCCURRENCE-CODE-END-DATE-02 2 If OCCURRENCE-CODE-02 is not 8-filled, then OCCURRENCE-CODE-END-DATE-02 must not be 8-filled 2340 Relational edit between OCCURRENCE-CODE-02 and OCCURRENCE-CODE-END-DATE-02 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-02), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-02,OCCURRENCE-CODE-END-DATE-02 COT075,COT095











1,172 Merged COT095-0006 RULE-1450 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT095 OCCURRENCE-CODE-END-DATE-02 2-M
2070
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-02) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-02), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-02, @val.OCCURRENCE-CODE-END-DATE-02)' OCCURRENCE-CODE-EFF-DATE-02,OCCURRENCE-CODE-END-DATE-02 COT085,COT095











1,173 Merged COT096-0001 RULE-1491 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT096 OCCURRENCE-CODE-END-DATE-03 1 If OCCURRENCE-CODE-END-DATE-03 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-03 COT096











1,174 Merged COT096-0002 RULE-1491 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT096 OCCURRENCE-CODE-END-DATE-03 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-03 COT096











1,175 No logic changes COT096-0004 RULE-1493 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT096 OCCURRENCE-CODE-END-DATE-03 2 If OCCURRENCE-CODE-03 is not 8-filled, then OCCURRENCE-CODE-END-DATE-03 must not be 8-filled 2342 Relational edit between OCCURRENCE-CODE-03 and OCCURRENCE-CODE-END-DATE-03 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-03), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-03,OCCURRENCE-CODE-END-DATE-03 COT076,COT096











1,176 Merged COT096-0006 RULE-1454 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT096 OCCURRENCE-CODE-END-DATE-03 2-M
2071
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-03) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-03), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-03, @val.OCCURRENCE-CODE-END-DATE-03)' OCCURRENCE-CODE-EFF-DATE-03,OCCURRENCE-CODE-END-DATE-03 COT086,COT096











1,177 Merged COT097-0001 RULE-1495 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT097 OCCURRENCE-CODE-END-DATE-04 1 If OCCURRENCE-CODE-END-DATE-04 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-04 COT097











1,178 Merged COT097-0002 RULE-1495 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT097 OCCURRENCE-CODE-END-DATE-04 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-04 COT097











1,179 No logic changes COT097-0004 RULE-1497 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT097 OCCURRENCE-CODE-END-DATE-04 2 If OCCURRENCE-CODE-04 is not 8-filled, then OCCURRENCE-CODE-END-DATE-04 must not be 8-filled 2344 Relational edit between OCCURRENCE-CODE-04 and OCCURRENCE-CODE-END-DATE-04 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-04), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-04,OCCURRENCE-CODE-END-DATE-04 COT077,COT097











1,180 Merged COT097-0006 RULE-1458 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT097 OCCURRENCE-CODE-END-DATE-04 2-M
2072
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-04) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-04), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-04, @val.OCCURRENCE-CODE-END-DATE-04)' OCCURRENCE-CODE-EFF-DATE-04,OCCURRENCE-CODE-END-DATE-04 COT087,COT097











1,181 Merged COT098-0001 RULE-1499 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT098 OCCURRENCE-CODE-END-DATE-05 1 If OCCURRENCE-CODE-END-DATE-05 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-05 COT098











1,182 Merged COT098-0002 RULE-1499 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT098 OCCURRENCE-CODE-END-DATE-05 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-05 COT098











1,183 No logic changes COT098-0004 RULE-1501 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT098 OCCURRENCE-CODE-END-DATE-05 2 If OCCURRENCE-CODE-05 is not 8-filled, then OCCURRENCE-CODE-END-DATE-05 must not be 8-filled 2346 Relational edit between OCCURRENCE-CODE-05 and OCCURRENCE-CODE-END-DATE-05 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-05), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-05,OCCURRENCE-CODE-END-DATE-05 COT078,COT098











1,184 Merged COT098-0006 RULE-1462 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT098 OCCURRENCE-CODE-END-DATE-05 2-M
2073
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-05) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-05), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-05, @val.OCCURRENCE-CODE-END-DATE-05)' OCCURRENCE-CODE-EFF-DATE-05,OCCURRENCE-CODE-END-DATE-05 COT088,COT098











1,185 Merged COT099-0001 RULE-1503 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT099 OCCURRENCE-CODE-END-DATE-06 1 If OCCURRENCE-CODE-END-DATE-06 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-06 COT099











1,186 Merged COT099-0002 RULE-1503 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT099 OCCURRENCE-CODE-END-DATE-06 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-06 COT099











1,187 No logic changes COT099-0004 RULE-1505 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT099 OCCURRENCE-CODE-END-DATE-06 2 If OCCURRENCE-CODE-06 is not 8-filled, then OCCURRENCE-CODE-END-DATE-06 must not be 8-filled 2348 Relational edit between OCCURRENCE-CODE-06 and OCCURRENCE-CODE-END-DATE-06 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-06), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-06,OCCURRENCE-CODE-END-DATE-06 COT079,COT099











1,188 Merged COT099-0006 RULE-1466 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT099 OCCURRENCE-CODE-END-DATE-06 2-M
2074
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-06) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-06), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-06, @val.OCCURRENCE-CODE-END-DATE-06)' OCCURRENCE-CODE-EFF-DATE-06,OCCURRENCE-CODE-END-DATE-06 COT089,COT099











1,189 Merged COT100-0001 RULE-1507 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT100 OCCURRENCE-CODE-END-DATE-07 1 If OCCURRENCE-CODE-END-DATE-07 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-07 COT100











1,190 Merged COT100-0002 RULE-1507 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT100 OCCURRENCE-CODE-END-DATE-07 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-07 COT100











1,191 No logic changes COT100-0004 RULE-1509 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT100 OCCURRENCE-CODE-END-DATE-07 2 If OCCURRENCE-CODE-07 is not 8-filled, then OCCURRENCE-CODE-END-DATE-07 must not be 8-filled 2350 Relational edit between OCCURRENCE-CODE-07 and OCCURRENCE-CODE-END-DATE-07 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-07), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-07,OCCURRENCE-CODE-END-DATE-07 COT080,COT100











1,192 Merged COT100-0006 RULE-1470 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT100 OCCURRENCE-CODE-END-DATE-07 2-M
2075
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-07) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-07), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-07, @val.OCCURRENCE-CODE-END-DATE-07)' OCCURRENCE-CODE-EFF-DATE-07,OCCURRENCE-CODE-END-DATE-07 COT090,COT100











1,193 Merged COT101-0001 RULE-1511 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT101 OCCURRENCE-CODE-END-DATE-08 1 If OCCURRENCE-CODE-END-DATE-08 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-08 COT101











1,194 Merged COT101-0002 RULE-1511 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT101 OCCURRENCE-CODE-END-DATE-08 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-08 COT101











1,195 No logic changes COT101-0004 RULE-1513 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT101 OCCURRENCE-CODE-END-DATE-08 2 If OCCURRENCE-CODE-08 is not 8-filled, then OCCURRENCE-CODE-END-DATE-08 must not be 8-filled 2352 Relational edit between OCCURRENCE-CODE-08 and OCCURRENCE-CODE-END-DATE-08 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-08), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-08,OCCURRENCE-CODE-END-DATE-08 COT081,COT101











1,196 Merged COT101-0006 RULE-1474 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT101 OCCURRENCE-CODE-END-DATE-08 2-M
2076
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-08) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-08), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-08, @val.OCCURRENCE-CODE-END-DATE-08)' OCCURRENCE-CODE-EFF-DATE-08,OCCURRENCE-CODE-END-DATE-08 COT091,COT101











1,197 Merged COT102-0001 RULE-1515 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT102 OCCURRENCE-CODE-END-DATE-09 1 If OCCURRENCE-CODE-END-DATE-09 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-09 COT102











1,198 Merged COT102-0002 RULE-1515 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT102 OCCURRENCE-CODE-END-DATE-09 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-09 COT102











1,199 No logic changes COT102-0004 RULE-1517 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT102 OCCURRENCE-CODE-END-DATE-09 2 If OCCURRENCE-CODE-09 is not 8-filled, then OCCURRENCE-CODE-END-DATE-09 must not be 8-filled 2354 Relational edit between OCCURRENCE-CODE-09 and OCCURRENCE-CODE-END-DATE-09 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-09), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-09,OCCURRENCE-CODE-END-DATE-09 COT082,COT102











1,200 Merged COT102-0006 RULE-1478 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT102 OCCURRENCE-CODE-END-DATE-09 2-M
2077
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-09) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-09), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-09, @val.OCCURRENCE-CODE-END-DATE-09)' OCCURRENCE-CODE-EFF-DATE-09,OCCURRENCE-CODE-END-DATE-09 COT092,COT102











1,201 Merged COT103-0001 RULE-1519 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT103 OCCURRENCE-CODE-END-DATE-10 1 If OCCURRENCE-CODE-END-DATE-10 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-10 COT103











1,202 Merged COT103-0002 RULE-1519 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT103 OCCURRENCE-CODE-END-DATE-10 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD OCCURRENCE-CODE-END-DATE-10 COT103











1,203 No logic changes COT103-0004 RULE-1521 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT103 OCCURRENCE-CODE-END-DATE-10 2 If OCCURRENCE-CODE-10 is not 8-filled, then OCCURRENCE-CODE-END-DATE-10 must not be 8-filled 2356 Relational edit between OCCURRENCE-CODE-10 and OCCURRENCE-CODE-END-DATE-10 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-10), then fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-10,OCCURRENCE-CODE-END-DATE-10 COT083,COT103











1,204 Merged COT103-0006 RULE-1482 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT103 OCCURRENCE-CODE-END-DATE-10 2-M
2078
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.OCCURRENCE-CODE-EFF-DATE-10) && fns.hasValue(@val.OCCURRENCE-CODE-END-DATE-10), then fns.isLessThanOrEqual(@val.OCCURRENCE-CODE-EFF-DATE-10, @val.OCCURRENCE-CODE-END-DATE-10)' OCCURRENCE-CODE-EFF-DATE-10,OCCURRENCE-CODE-END-DATE-10 COT093,COT103











1,205 Logic updated: string matching COT104-0001 RULE-1523 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT104 PATIENT-CONTROL-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PATIENT-CONTROL-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.PATIENT-CONTROL-NUM), then fns.matches(@val.PATIENT-CONTROL-NUM, "^[^|*]*$")' PATIENT-CONTROL-NUM COT104











1,206 Logic updated: string matching COT105-0001 RULE-1524 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT105 ELIGIBLE-LAST-NAME 1 ELIGIBLE-LAST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid character - ELIGIBLE-LAST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.ELIGIBLE-LAST-NAME), then fns.matches(@val.ELIGIBLE-LAST-NAME, "^[^|*]*$")' ELIGIBLE-LAST-NAME COT105











1,207 Logic updated: string matching COT106-0001 RULE-1525 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT106 ELIGIBLE-FIRST-NAME 1 ELIGIBLE-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - ELIGIBLE-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.ELIGIBLE-FIRST-NAME), then fns.matches(@val.ELIGIBLE-FIRST-NAME, "^[^|*]*$")' ELIGIBLE-FIRST-NAME COT106











1,208 Logic updated: string matching COT107-0001 RULE-1526 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT107 ELIGIBLE-MIDDLE-INIT 1 ELIGIBLE-MIDDLE-INIT must not contain non-alphabetic characters 120 Field contains invalid characters - ELIGIBLE-MIDDLE-INIT 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.ELIGIBLE-MIDDLE-INIT), then fns.matches(@val.ELIGIBLE-MIDDLE-INIT, "^[^|*]*$")' ELIGIBLE-MIDDLE-INIT COT107











1,209 Merged COT108-0001 RULE-1527 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT108 DATE-OF-BIRTH 1 If DATE-OF-BIRTH is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH COT108











1,210 Merged COT108-0002 RULE-1527 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT108 DATE-OF-BIRTH 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH COT108











1,211 Logic updated: other COT108-0007 RULE-1529 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT108 DATE-OF-BIRTH 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled
and
CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64",
then DATE-OF-BIRTH must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-OT-COT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002]		 3037 Relational edit between DATE-OF-BIRTH and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-OT COT00002 ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 'if fns.hasValue(@secondaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@secondaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64") && fns.hasValue(@primaryRecord.DATE-OF-BIRTH) && fns.hasValue(@tertiaryRecord.DATE-OF-DEATH), then fns.isLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @tertiaryRecord.DATE-OF-DEATH)' DATE-OF-BIRTH COT108 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-DEATH ELG025 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM COT017,COT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM COT017,COT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019
1,212 Logic updated: other COT108-0008 RULE-1530 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT108 DATE-OF-BIRTH 3 If CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64", then DATE-OF-BIRTH must = DATE-OF-BIRTH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-OT-COT00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3023 A DATE-OF-BIRTH does not match the DATE-OF-BIRTH in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-OT COT00002 ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 'if fns.hasValue(@secondaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@secondaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64") && fns.hasValue(@primaryRecord.DATE-OF-BIRTH) && fns.hasValue(@tertiaryRecord.DATE-OF-BIRTH), then fns.isEqual(@primaryRecord.DATE-OF-BIRTH, @tertiaryRecord.DATE-OF-BIRTH)' DATE-OF-BIRTH COT108 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-BIRTH ELG024 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM COT017,COT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM COT017,COT022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019
1,213 No logic changes COT109-0001 RULE-6157 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT109 HEALTH-HOME-PROV-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-HOME-PROV-IND COT109











1,214 No logic changes COT109-0003 RULE-1532 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT109 HEALTH-HOME-PROV-IND 2 If HEALTH-HOME-ENTITY-NAME is not 8-filled, then HEALTH-HOME-PROV-IND must = "1" 2294 Relational edit between HEALTH-HOME-PROV-IND and HEALTH-HOME-ENTITY-NAME failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.isEqual(@val.HEALTH-HOME-PROV-IND, "1")' HEALTH-HOME-ENTITY-NAME,HEALTH-HOME-PROV-IND COT138,COT109











1,215 No logic changes COT110-0001 RULE-1533 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT110 WAIVER-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-TYPE WAIVER-TYPE COT110











1,216 Merged COT111-0001 RULE-1534 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT111 WAIVER-ID 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID COT111











1,217 Merged COT111-0005 RULE-1535 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT111 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID COT110,COT111











1,218 Merged COT111-0009 RULE-1534 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT111 WAIVER-ID 3 WAIVER-ID must = waiver ID in state-provided crosswalk 3029 Edit with an external reference (state provided WAIVER-ID-/WAIVER-TYPE crosswalk) failed 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID COT111











1,219 Merged COT111-0010 RULE-1535 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT111 WAIVER-ID 2 If WAIVER-TYPE is 8-filled, then WAIVER-ID must be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID COT110,COT111











1,220 Merged COT111-0011 RULE-1535 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT111 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID COT110,COT111











1,221 Retired: Other reasons COT112-0001
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT112 BILLING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























1,222 Logic updated: other COT112-0004 RULE-1540 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT112 BILLING-PROV-NUM 3 If ( BILLING-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then BILLING-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-OT COT00002

For every record of type CLAIM-HEADER-RECORD-OT, if fns.hasValue(@secondaryRecord.BILLING-PROV-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "1") PROV-IDENTIFIER-TYPE PRV077 BILLING-PROV-NUM,TYPE-OF-CLAIM COT112,COT037

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,BILLING-PROV-NUM COT017,COT112



1,223 Merged COT113-0001 RULE-1541 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT113 BILLING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM COT113











1,224 Merged COT113-0002 RULE-1541 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT113 BILLING-PROV-NPI-NUM 1 If BILLING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM COT113











1,225 No logic changes COT113-0005 RULE-1543 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT113 BILLING-PROV-NPI-NUM 2 If TYPE-OF-SERVICE = 119, 120, 121, or 122, then BILLING-PROV-NPI-NUM must be 8-filled 2238 Relational edit between BILLING-PROV-NPI-NUM and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@primaryRecord.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM COT113 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,226 Logic updated: other COT113-0007 RULE-1544 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT113 BILLING-PROV-NPI-NUM 3 If ( BILLING-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then BILLING-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-OT COT00002

For every record of type CLAIM-HEADER-RECORD-OT, if fns.hasValue(@secondaryRecord.BILLING-PROV-NPI-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "2") PROV-IDENTIFIER-TYPE PRV077 BILLING-PROV-NPI-NUM,TYPE-OF-CLAIM COT113,COT037

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,BILLING-PROV-NPI-NUM COT017,COT113



1,227 No logic changes COT114-0001 RULE-1545 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT114 BILLING-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY BILLING-PROV-TAXONOMY COT114











1,228 No logic changes COT114-0003 RULE-1546 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT114 BILLING-PROV-TAXONOMY 2 If TYPE-OF-SERVICE = 119, 120, 121, OR 122, then BILLING-PROV-TAXONOMY must be 8-filled 2451 Relational edit between BILLING-PROV-TAXONOMY and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@primaryRecord.BILLING-PROV-TAXONOMY)' BILLING-PROV-TAXONOMY COT114 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,229 No logic changes COT115-0001 RULE-1547 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT115 BILLING-PROV-TYPE 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE BILLING-PROV-TYPE COT115











1,230 No logic changes COT116-0001 RULE-1548 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT116 BILLING-PROV-SPECIALTY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY BILLING-PROV-SPECIALTY COT116











1,231 Retired: Other reasons COT117-0001
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT117 REFERRING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























1,232 Merged COT118-0001 RULE-1550 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT118 REFERRING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.REFERRING-PROV-NPI-NUM), then fns.isValidNPI(@val.REFERRING-PROV-NPI-NUM)' REFERRING-PROV-NPI-NUM COT118











1,233 Merged COT118-0002 RULE-1550 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT118 REFERRING-PROV-NPI-NUM 1 If REFERRING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.REFERRING-PROV-NPI-NUM), then fns.isValidNPI(@val.REFERRING-PROV-NPI-NUM)' REFERRING-PROV-NPI-NUM COT118











1,234 No logic changes COT118-0005 RULE-1552 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT118 REFERRING-PROV-NPI-NUM 2 If TYPE-OF-SERVICE= "121", then REFERRING-PROV-NPI must be 8-filled 2406 Relational edit between REFERRING-PROV-NPI and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqual(@secondaryRecord.TYPE-OF-SERVICE, "121"), then !fns.hasValue(@primaryRecord.REFERRING-PROV-NPI-NUM)' REFERRING-PROV-NPI-NUM COT118 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,235 No logic changes COT119-0001 RULE-1553 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT119 REFERRING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY REFERRING-PROV-TAXONOMY COT119











1,236 No logic changes COT119-0003 RULE-1554 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT119 REFERRING-PROV-TAXONOMY 2 If TYPE-OF-SERVICE = 119, 120, 121, OR 122, then REFERRING-PROV-TAXONOMY must be 8-filled 2407 Relational edit between REFERRING-PROV-TAXONOMY and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@primaryRecord.REFERRING-PROV-TAXONOMY)' REFERRING-PROV-TAXONOMY COT119 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,237 No logic changes COT120-0001 RULE-1555 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT120 REFERRING-PROV-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE REFERRING-PROV-TYPE COT120











1,238 No logic changes COT121-0001 RULE-1556 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT121 REFERRING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY REFERRING-PROV-SPECIALTY COT121











1,239 Logic updated: string matching COT122-0001 RULE-1557 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT122 MEDICARE-HIC-NUM 1 Field contains invalid characters -MEDICARE-HIC-NUM 120 Field contains invalid characters -MEDICARE-HIC-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.matches(@val.MEDICARE-HIC-NUM, "^[^|*]*$")' MEDICARE-HIC-NUM COT122











1,240 No logic changes COT122-0003 RULE-1558 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT122 MEDICARE-HIC-NUM 2 If CROSSOVER-INDICATOR= "1" and MEDICARE-BENEFICIARY-IDENTIFIER is 8-filled, then MEDICARE-HIC-NUM must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.hasValue(@val.MEDICARE-HIC-NUM)' CROSSOVER-INDICATOR,MEDICARE-BENEFICIARY-IDENTIFIER,MEDICARE-HIC-NUM COT023,COT147,COT122











1,241 No logic changes COT123-0001 RULE-1559 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT123 PLACE-OF-SERVICE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PLACE-OF-SERVICE PLACE-OF-SERVICE COT123











1,242 No logic changes COT123-0004 RULE-1560 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT123 PLACE-OF-SERVICE 2 If TYPE-OF-SERVICE = "119", "120", "121", or "122", then PLACE-OF-SERVICE must be 8-filled 2362 Relational edit between PLACE-OF-SERVICE and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@primaryRecord.PLACE-OF-SERVICE)' PLACE-OF-SERVICE COT123 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,243 No logic changes COT125-0001 RULE-1561 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT125 BMI 1 If BMI is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: S9(5)V9 BMI COT125











1,244 Logic updated: string matching COT126-0001 RULE-1562 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT126 REMITTANCE-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - REMITTANCE-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.REMITTANCE-NUM), then fns.matches(@val.REMITTANCE-NUM, "^[^|*]*$")' REMITTANCE-NUM COT126











1,245 Retired: required value checks COT126-0002
CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT126 REMITTANCE-NUM 1 If REMITTANCE-NUM is null 113 Required data element has not been reported.

























1,246 No logic changes COT127-0001 RULE-1564 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT127 DAILY-RATE 1 If DAILY-RATE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(5)V99 DAILY-RATE COT127











1,247 No logic changes COT128-0001 RULE-1565 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT128 BORDER-STATE-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: BORDER-STATE-IND BORDER-STATE-IND COT128











1,248 No logic changes COT130-0001 RULE-1566 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT130 BENEFICIARY-COINSURANCE-AMOUNT 1 If BENEFICIARY-COINSURANCE-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COINSURANCE-AMOUNT COT130











1,249 Merged COT131-0001 RULE-1567 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT131 BENEFICIARY-COINSURANCE-DATE-PAID 1 If BENEFICIARY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID COT131











1,250 Merged COT131-0002 RULE-1567 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT131 BENEFICIARY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID COT131











1,251 No logic changes COT132-0001 RULE-1569 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT132 BENEFICIARY-COPAYMENT-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COPAYMENT-AMOUNT COT132











1,252 Merged COT133-0001 RULE-1570 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT133 BENEFICIARY-COPAYMENT-DATE-PAID 1 If BENEFICIARY-COPAYMENT-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COPAYMENT-DATE-PAID COT133











1,253 Merged COT133-0002 RULE-1570 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT133 BENEFICIARY-COPAYMENT-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COPAYMENT-DATE-PAID COT133











1,254 No logic changes COT134-0001 RULE-1572 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT134 BENEFICIARY-DEDUCTIBLE-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-DEDUCTIBLE-AMOUNT COT134











1,255 Merged COT135-0001 RULE-1573 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT135 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 If BENEFICIARY-DEDUCTIBLE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID COT135











1,256 Merged COT135-0002 RULE-1573 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT135 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID COT135











1,257 No logic changes COT136-0001 RULE-1575 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT136 CLAIM-DENIED-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-DENIED-INDICATOR CLAIM-DENIED-INDICATOR COT136











1,258 No logic changes COT136-0003 RULE-1576 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT136 CLAIM-DENIED-INDICATOR 2 If TYPE-OF-CLAIM = "Z", then CLAIM-DENIED-INDICATOR must = "0" 2242 Relational edit between CLAIM-DENIED-INDICATOR and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.isEqual(@val.TYPE-OF-CLAIM, "Z"), then fns.isEqual(@val.CLAIM-DENIED-INDICATOR, "0")' TYPE-OF-CLAIM,CLAIM-DENIED-INDICATOR COT037,COT136











1,259 No logic changes COT137-0001 RULE-1577 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT137 COPAY-WAIVED-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: COPAY-WAIVED-IND COPAY-WAIVED-IND COT137











1,260 Logic updated: string matching COT138-0001 RULE-1578 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT138 HEALTH-HOME-ENTITY-NAME 1 If HEALTH-HOME-ENTITY-NAME is populated, it must contains valid characters. 120 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.matches(@val.HEALTH-HOME-ENTITY-NAME, "^[^|*]*$")' HEALTH-HOME-ENTITY-NAME COT138











1,261 No logic changes COT140-0001 RULE-1579 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT140 THIRD-PARTY-COINSURANCE-AMOUNT-PAID 1 If THIRD-PARTY-COINSURANCE-AMOUNT-PAID is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COINSURANCE-AMOUNT-PAID COT140











1,262 Merged COT141-0001 RULE-1580 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT141 THIRD-PARTY-COINSURANCE-DATE-PAID 1 If THIRD-PARTY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID COT141











1,263 Merged COT141-0002 RULE-1580 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT141 THIRD-PARTY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID COT141











1,264 No logic changes COT142-0001 RULE-1582 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT142 THIRD-PARTY-COPAYMENT-AMOUNT-PAID 1 If THIRD-PARTY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COPAYMENT-AMOUNT-PAID COT142











1,265 Merged COT143-0001 RULE-1583 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT143 THIRD-PARTY-COPAYMENT-DATE-PAID 1 If THIRD-PARTY-COPAYMENT-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID COT143











1,266 Merged COT143-0002 RULE-1583 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT143 THIRD-PARTY-COPAYMENT-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID COT143











1,267 Merged COT144-0001 RULE-1585 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT144 DATE-CAPITATED-AMOUNT-REQUESTED 1 If DATE-CAPITATED-AMOUNT-REQUESTED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD DATE-CAPITATED-AMOUNT-REQUESTED COT144











1,268 Merged COT144-0002 RULE-1585 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT144 DATE-CAPITATED-AMOUNT-REQUESTED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid date of the form CCYYMMDD DATE-CAPITATED-AMOUNT-REQUESTED COT144











1,269 No logic changes COT145-0001 RULE-6819 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT145 CAPITATED-PAYMENT-AMT-REQUESTED 1 If CAPITATED-PAYMENT-AMT-REQUESTED is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 CAPITATED-PAYMENT-AMT-REQUESTED COT145











1,270 Merged COT146-0001 RULE-1588 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT146 HEALTH-HOME-PROVIDER-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI COT146











1,271 Merged COT146-0002 RULE-1588 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT146 HEALTH-HOME-PROVIDER-NPI 1 If HEALTH-HOME-PROVIDER-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI COT146











1,272 No logic changes COT146-0003 RULE-1590 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT146 HEALTH-HOME-PROVIDER-NPI 2 If TYPE-OF-SERVICE= "121", then HEALTH-HOME-PROVIDER-NPI must be 8-filled 2293 Relational edit between HEALTH-HOME-PROVIDER-NPI and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqual(@secondaryRecord.TYPE-OF-SERVICE, "121"), then !fns.hasValue(@primaryRecord.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI COT146 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,273 Logic updated: other COT146-0004 RULE-1591 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT146 HEALTH-HOME-PROVIDER-NPI 3 If ( HEALTH-HOME-PROVIDER-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then HEALTH-HOME-PROVIDER-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-OT COT00002

For every record of type CLAIM-HEADER-RECORD-OT, if fns.hasValue(@secondaryRecord.HEALTH-HOME-PROVIDER-NPI) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "2") PROV-IDENTIFIER-TYPE PRV077 HEALTH-HOME-PROVIDER-NPI,TYPE-OF-CLAIM COT146,COT037

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,HEALTH-HOME-PROVIDER-NPI COT017,COT146



1,274 Logic updated: string matching COT147-0001 RULE-1592 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT147 MEDICARE-BENEFICIARY-IDENTIFIER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - MEDICARE-BENEFICIARY-IDENTIFIER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.matches(@val.MEDICARE-BENEFICIARY-IDENTIFIER, "^[^|*]*$")' MEDICARE-BENEFICIARY-IDENTIFIER COT147











1,275 No logic changes COT147-0003 RULE-1593 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT147 MEDICARE-BENEFICIARY-IDENTIFIER 2 If END-OF-TIME-PERIOD >= "20151110", CROSSOVER-INDICATOR= "1" and MEDICARE-HIC-NUM is 8-filled, then MEDICARE-BENEFICIARY-IDENTIFIER must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 FILE-HEADER-RECORD-OT COT00001

'if fns.isGreaterThanOrEqual(@fileHeader.END-OF-TIME-PERIOD, "2015-11-10") && fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER)' CROSSOVER-INDICATOR,MEDICARE-HIC-NUM,MEDICARE-BENEFICIARY-IDENTIFIER COT023,COT122,COT147 END-OF-TIME-PERIOD COT010









1,276 No logic changes COT148-0001 RULE-1594 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT148 UNDER-DIRECTION-OF-PROV-NPI 2 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.UNDER-DIRECTION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-DIRECTION-OF-PROV-NPI)' UNDER-DIRECTION-OF-PROV-NPI COT148











1,277 No logic changes COT149-0001 RULE-1595 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT149 UNDER-DIRECTION-OF-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY UNDER-DIRECTION-OF-PROV-TAXONOMY COT149











1,278 Merged COT150-0001 RULE-1596 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT150 UNDER-SUPERVISION-OF-PROV-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.UNDER-SUPERVISION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-SUPERVISION-OF-PROV-NPI)' UNDER-SUPERVISION-OF-PROV-NPI COT150











1,279 Merged COT150-0002 RULE-1596 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT150 UNDER-SUPERVISION-OF-PROV-NPI 1 If UNDER-SUPERVISION-OF-PROV-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.UNDER-SUPERVISION-OF-PROV-NPI), then fns.isValidNPI(@val.UNDER-SUPERVISION-OF-PROV-NPI)' UNDER-SUPERVISION-OF-PROV-NPI COT150











1,280 No logic changes COT150-0003 RULE-1598 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT150 UNDER-SUPERVISION-OF-PROV-NPI 2 If TYPE-OF-SERVICE= "121", then UNDER-SUPERVISION-OF-PROV-NPI must be 8-filled 2438 Relational edit between UNDER-SUPERVISION-OF-PROV-NPI and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqual(@secondaryRecord.TYPE-OF-SERVICE, "121"), then !fns.hasValue(@primaryRecord.UNDER-SUPERVISION-OF-PROV-NPI)' UNDER-SUPERVISION-OF-PROV-NPI COT150 TYPE-OF-SERVICE COT186

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,281 No logic changes COT151-0001 RULE-1599 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT151 UNDER-SUPERVISION-OF-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY UNDER-SUPERVISION-OF-PROV-TAXONOMY COT151











1,282 Logic updated: string matching COT152-0001 RULE-1600 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT152 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION COT152











1,283 No logic changes COT154-0001 RULE-6318 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT154 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE COT154











1,284 Moved to R&C COT154-0004
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT154 RECORD-ID 2 If FILE-NAME = "CLAIM-OT", then the first 3 positions of RECORD-ID must = "COT" 150 Invalid or missing RECORD-ID

























1,285 No logic changes COT155-0001 RULE-1603 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT155 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE COT155











1,286 Logic updated: other COT155-0004 RULE-1604 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT155 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-OT-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-OT COT00003 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE COT155 SUBMITTING-STATE COT007









1,287 Retired: Other reasons COT156-0001
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT156 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,288 No logic changes COT156-0004 RULE-1606 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT156 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-LINE-RECORD-OT COT00003



Field RECORD-NUMBER should be unique across all records of type CLAIM-LINE-RECORD-OT RECORD-NUMBER COT156











1,289 Retired: MSIS ID checks COT157-0001
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT157 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,290 Retired: MSIS ID checks COT157-0002
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT157 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,291 No logic changes COT157-0003 RULE-1609 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT157 MSIS-IDENTIFICATION-NUM 2 If TYPE-OF-CLAIM = "4", "D", OR "X", then the first byte of MSIS-IDENTIFICATION-NUM must = "&" 2331 Relational edit between MSIS-IDENTIFICATION-NUM and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "4", "D", "X"), then fns.matches(@secondaryRecord.MSIS-IDENTIFICATION-NUM, "^&.*$")' TYPE-OF-CLAIM COT037 MSIS-IDENTIFICATION-NUM COT157

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,292 Logic updated: parent/child overlap COT157-0005 RULE-1610 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT157 MSIS-IDENTIFICATION-NUM 2 ICN-ORIG [SUBMITTING-STATE CLAIM-LINE-RECORD-OT-COT00003] must = ICN-ORIG [CLAIM-HEADER-RECORD-OT-COT00002],
and ICN-ADJ [SUBMITTING-STATE CLAIM-LINE-RECORD-OT-COT00003] must = ICN-ADJ [CLAIM-HEADER-RECORD-OT-COT00002],
and ADJUDICATION-DATE [SUBMITTING-STATE CLAIM-LINE-RECORD-OT-COT00003] must = ADJUDICATION-DATE [CLAIM-HEADER-RECORD-OT-COT00002] on any record in the file,
and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] must = SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] on the same record in the file		 2191 Edit that CLAIM-LINE-RECORD-OT-COT00003 child record has a CLAIM-HEADER-RECORD-OT-COT00002 parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

record CLAIM-LINE-RECORD-OT has corresponding parent record CLAIM-HEADER-RECORD-OT





SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,293 Logic updated: string matching COT158-0001 RULE-1611 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT158 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ORIG 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG COT158











1,294 Logic updated: string matching COT159-0001 RULE-1612 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT159 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ COT159











1,295 No logic changes COT160-0001 RULE-1613 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT160 LINE-NUM-ORIG 1 If LINE-NUM-ORIG not >=0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.LINE-NUM-ORIG), then fns.isNonNegative(@val.LINE-NUM-ORIG)' LINE-NUM-ORIG COT160











1,296 No logic changes COT161-0001 RULE-1614 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT161 LINE-NUM-ADJ 1 If LINE-NUM-ADJ not >=0. 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.isNonNegative(@val.LINE-NUM-ADJ)' LINE-NUM-ADJ COT161











1,297 No logic changes COT161-0002 RULE-1615 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT161 LINE-NUM-ADJ 2 If LINE-ADJUSTMENT-IND = "0", then LINE-NUM-ADJ must be 8-filled 2312 Relational edit between LINE-NUM-ADJ and LINE-ADJUSTMENT-IND failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.isEqual(@val.LINE-ADJUSTMENT-IND, "0"), then !fns.hasValue(@val.LINE-NUM-ADJ)' LINE-ADJUSTMENT-IND,LINE-NUM-ADJ COT162,COT161











1,298 No logic changes COT162-0001 RULE-1616 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT162 LINE-ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: LINE-ADJUSTMENT-IND LINE-ADJUSTMENT-IND COT162











1,299 No logic changes COT162-0002 RULE-1617 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT162 LINE-ADJUSTMENT-IND 2 If LINE-NUM-ADJ is not 8-filled, then LINE-ADJUSTMENT-IND must not be 8-filled 2310 Relational edit between LINE-ADJUSTMENT-IND and LINE-NUM-ADJ failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.hasValue(@val.LINE-ADJUSTMENT-IND)' LINE-NUM-ADJ,LINE-ADJUSTMENT-IND COT161,COT162











1,300 No logic changes COT163-0001 RULE-1618 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT163 LINE-ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE LINE-ADJUSTMENT-REASON-CODE COT163











1,301 No logic changes COT164-0001 RULE-6346 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT164 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported. 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID COT164











1,302 No logic changes COT165-0001 RULE-1620 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT165 CLAIM-LINE-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-LINE-STATUS COT165











1,303 Merged COT166-0001 RULE-1621 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT166 BEGINNING-DATE-OF-SERVICE 1 If BEGINNING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE COT166











1,304 Merged COT166-0002 RULE-1621 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT166 BEGINNING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD BEGINNING-DATE-OF-SERVICE COT166











1,305 Merged COT166-0003 RULE-1623 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT166 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ENDING-DATE-OF-SERVICE 2012 Relational edit between BEGINNING-DATE-OF-SERVICE and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE COT166,COT167











1,306 Logic updated: other COT166-0004 RULE-1624 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT166 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-LINE-RECORD-OT] 2011 Relational edit between BEGINNING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-LINE-RECORD-OT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' BEGINNING-DATE-OF-SERVICE,ADJUDICATION-DATE COT166,COT221











1,307 Logic updated: other COT166-0005 RULE-1625 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT166 BEGINNING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then BEGINNING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-OT-COT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3002 Relational edit between BEGINNING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.BEGINNING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.BEGINNING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 BEGINNING-DATE-OF-SERVICE COT166

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT157,COT155



1,308 Logic updated: other COT166-0009 RULE-1626 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT166 BEGINNING-DATE-OF-SERVICE 2 BEGINNING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2013 Relational edit between BEGINNING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-OT COT00003 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' BEGINNING-DATE-OF-SERVICE COT166 END-OF-TIME-PERIOD COT010









1,309 Merged COT167-0001 RULE-1627 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT167 ENDING-DATE-OF-SERVICE 1 If ENDING-DATE-OF-SERVICE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE COT167











1,310 Merged COT167-0002 RULE-1627 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT167 ENDING-DATE-OF-SERVICE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD ENDING-DATE-OF-SERVICE COT167











1,311 Merged COT167-0003 RULE-1623 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT167 ENDING-DATE-OF-SERVICE 2-M
2012
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.ENDING-DATE-OF-SERVICE)' BEGINNING-DATE-OF-SERVICE,ENDING-DATE-OF-SERVICE COT166,COT167











1,312 Logic updated: other COT167-0004 RULE-1630 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT167 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= ADJUDICATION-DATE [CLAIM-LINE-RECORD-OT] 2040 Relational edit between ENDING-DATE-OF-SERVICE and ADJUDICATION-DATE [CLAIM-LINE-RECORD-OT] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @val.ADJUDICATION-DATE)' ENDING-DATE-OF-SERVICE,ADJUDICATION-DATE COT167,COT221











1,313 Logic updated: other COT167-0005 RULE-1631 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT167 ENDING-DATE-OF-SERVICE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then ENDING-DATE-OF-SERVICE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-OT-COT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3005 Relational edit between ENDING-DATE-OF-SERVICE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@secondaryRecord.ENDING-DATE-OF-SERVICE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ENDING-DATE-OF-SERVICE COT167

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT157,COT155



1,314 Logic updated: other COT167-0008 RULE-1632 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT167 ENDING-DATE-OF-SERVICE 2 ENDING-DATE-OF-SERVICE must be <= END-OF-TIME-PERIOD 2036 Relational edit between ENDING-DATE-OF-SERVICE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-OT COT00003 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.ENDING-DATE-OF-SERVICE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ENDING-DATE-OF-SERVICE, @fileHeader.END-OF-TIME-PERIOD)' ENDING-DATE-OF-SERVICE COT167 END-OF-TIME-PERIOD COT010









1,315 No logic changes COT168-0001 RULE-1633 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT168 REVENUE-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: REVENUE-CODE REVENUE-CODE COT168











1,316 No logic changes COT169-0001 RULE-1634 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT169 PROCEDURE-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE PROCEDURE-CODE COT169











1,317 Merged COT170-0001 RULE-1635 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT170 PROCEDURE-CODE-DATE 1 If PROCEDURE-CODE-DATE-1 is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE COT170











1,318 Merged COT170-0002 RULE-1635 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT170 PROCEDURE-CODE-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD PROCEDURE-CODE-DATE COT170











1,319 Logic updated: other COT170-0004 RULE-1637 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT170 PROCEDURE-CODE-DATE 2 PROCEDURE-CODE-DATE must be <= ENDING-DATE-OF-SERVICE 2095 Relational edit between PROCEDURE-CODE-DATE and ENDING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.PROCEDURE-CODE-DATE) && fns.hasValue(@val.ENDING-DATE-OF-SERVICE), then fns.isLessThanOrEqual(@val.PROCEDURE-CODE-DATE, @val.ENDING-DATE-OF-SERVICE)' PROCEDURE-CODE-DATE,ENDING-DATE-OF-SERVICE COT170,COT167











1,320 Logic updated: other COT170-0005 RULE-1638 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT170 PROCEDURE-CODE-DATE 2 PROCEDURE-CODE-DATE must be >= BEGINNING-DATE-OF-SERVICE 2094 Relational edit between PROCEDURE-CODE-DATE and BEGINNING-DATE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.BEGINNING-DATE-OF-SERVICE) && fns.hasValue(@val.PROCEDURE-CODE-DATE), then fns.isLessThanOrEqual(@val.BEGINNING-DATE-OF-SERVICE, @val.PROCEDURE-CODE-DATE)' BEGINNING-DATE-OF-SERVICE,PROCEDURE-CODE-DATE COT166,COT170











1,321 Logic updated: other COT170-0006 RULE-1639 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT170 PROCEDURE-CODE-DATE 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then PROCEDURE-CODE-DATE must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-OT-COT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3040 Relational edit between PROCEDURE-CODE-DATE and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PROCEDURE-CODE-DATE), then fns.isLessThanOrEqual(@secondaryRecord.PROCEDURE-CODE-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PROCEDURE-CODE-DATE COT170

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT157,COT155



1,322 No logic changes COT170-0007 RULE-1640 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT170 PROCEDURE-CODE-DATE 2 If PROCEDURE-CODE is 8-filled, then PROCEDURE-CODE-DATE must be 8-filled 2548 Relational edit between PROCEDURE-CODE-DATE and PROCEDURE-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if and only if fns.hasValue(@val.PROCEDURE-CODE), then fns.hasValue(@val.PROCEDURE-CODE-DATE)' PROCEDURE-CODE,PROCEDURE-CODE-DATE COT169,COT170











1,323 No logic changes COT171-0001 RULE-1641 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT171 PROCEDURE-CODE-FLAG 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-FLAG PROCEDURE-CODE-FLAG COT171











1,324 No logic changes COT172-0001 RULE-1642 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT172 PROCEDURE-CODE-MOD-1 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-1 COT172











1,325 Retired: Other reasons COT172-0003
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT172 PROCEDURE-CODE-MOD-1 2 If PROCEDURE-CODE-1 is 8-filled, then PROCEDURE-CODE-MOD-1 must be 8-filled 2382 Relational edit between PROCEDURE-CODE-MOD-1 and PROCEDURE-CODE-1 failed

























1,326 No logic changes COT173-0001 RULE-1644 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT173 IMMUNIZATION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: IMMUNIZATION-TYPE IMMUNIZATION-TYPE COT173











1,327 No logic changes COT174-0001 RULE-1645 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT174 BILLED-AMT 1 If BILLED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BILLED-AMT COT174











1,328 No logic changes COT175-0001 RULE-1646 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT175 ALLOWED-AMT 1 If ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 ALLOWED-AMT COT175











1,329 No logic changes COT176-0001 RULE-6633 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT176 COPAY-AMT 1 If COPAY-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 COPAY-AMT COT176











1,330 No logic changes COT177-0001 RULE-1648 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT177 TPL-AMT 1 If TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TPL-AMT COT177











1,331 No logic changes COT178-0001 RULE-1649 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT178 MEDICAID-PAID-AMT 1 If MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-PAID-AMT COT178











1,332 No logic changes COT179-0001 RULE-7122 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT179 MEDICAID-FFS-EQUIVALENT-AMT 1 If MEDICAID-FFS-EQUIVALENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-FFS-EQUIVALENT-AMT COT179











1,333 No logic changes COT179-0002 RULE-1651 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT179 MEDICAID-FFS-EQUIVALENT-AMT 2 If TYPE-OF-CLAIM = "C", "3", or "W", then MEDICAID-FFS-EQUIVALENT-AMT must not be 8-filled 2443 Relational edit with MEDICAID-FFS-EQUIVALENT-AMT and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.hasValue(@secondaryRecord.MEDICAID-FFS-EQUIVALENT-AMT)' TYPE-OF-CLAIM COT037 MEDICAID-FFS-EQUIVALENT-AMT COT179

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



1,334 No logic changes COT182-0001 RULE-1652 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT182 MEDICARE-PAID-AMT 1 If MEDICARE-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICARE-PAID-AMT COT182











1,335 No logic changes COT183-0001 RULE-1653 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT183 OT-RX-CLAIM-QUANTITY-ACTUAL 1 If OT-RX-CLAIM-QUANTITY-ACTUAL is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(6)V999 OT-RX-CLAIM-QUANTITY-ACTUAL COT183











1,336 No logic changes COT184-0001 RULE-6183 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT184 OT-RX-CLAIM-QUANTITY-ALLOWED 1 If OT-RX-CLAIM-QUANTITY-ALLOWED is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(6)V999 OT-RX-CLAIM-QUANTITY-ALLOWED COT184











1,337 No logic changes COT186-0001 RULE-1655 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT186 TYPE-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-SERVICE TYPE-OF-SERVICE COT186











1,338 Logic updated: other COT186-0005 RULE-1656 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT186 TYPE-OF-SERVICE 2 If FILE-NAME = "CLAIMOT", then TYPE-OF-SERVICE must = 002, 003, 004, 005, 006, 007, 008, 010, 011, 012, 013, 014, 015, 016, 017, 018, 019, 020, 021, 022, 023, 024, 025, 026, 027, 028, 029, 030, 031, 032, 035, 036, 037, 038, 039, 040, 041, 042, 043, 049, 050,,051, 052, 053, 054, 055, 056, 057, 058, 060, 061, 062, 063, 064, 065, 066, 067, 068, 069, 070, 071, 072, 073, 074, 075, 076, 077, 078, 079, 080, 081, 082, 083, 084, 085, 087, 088, 089, 115, 119, 120, 121, 122, 131, 134, OR 135 2434 Relational edit between TYPE-OF-SERVICE and FILE-NAME failed 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'fns.isEqualToAny(@val.TYPE-OF-SERVICE, "002", "003", "004", "005", "006", "007", "008", "010", "011", "012", "013", "014", "015", "016", "017", "018", "019", "020", "021", "022", "023", "024", "025", "026", "027", "028", "029", "030", "031", "032", "035", "036", "037", "038", "039", "040", "041", "042", "043", "049", "050","051", "052", "053", "054", "055", "056", "057", "058", "060", "061", "062", "063", "064", "065", "066", "067", "068", "069", "070", "071", "072", "073", "074", "075", "076", "077", "078", "079", "080", "081", "082", "083", "084", "085", "087", "088", "089", "115", "119", "120", "121", "122", "131", "134", "135")' TYPE-OF-SERVICE COT186











1,339 No logic changes COT186-0006 RULE-1657 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT186 TYPE-OF-SERVICE 3 TYPE-OF-SERVICE must <> ("025" OR "085") where SEX = "M" [ELIGIBLE] and MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-OT-COT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3013 Relational edit between TYPE-OF-SERVICE and SEX [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqual(@primaryRecord.SEX, "M"), then !fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "025", "085")' SEX ELG023 TYPE-OF-SERVICE COT186

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT157,COT155



1,340 No logic changes COT186-0007 RULE-1658 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT186 TYPE-OF-SERVICE 2 If TOOTH-QUAD-CODE is not 8-filled, then TYPE-OF-SERVICE must = "013" or "029" 2435 Relational edit between TYPE-OF-SERVICE and TOOTH-QUAD-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.TOOTH-QUAD-CODE), then fns.isEqualToAny(@val.TYPE-OF-SERVICE, "013", "029")' TOOTH-QUAD-CODE,TYPE-OF-SERVICE COT197,COT186











1,341 No logic changes COT186-0008 RULE-1659 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT186 TYPE-OF-SERVICE 2 If TOOTH-QUAD-CODE is not 8-filled, then TYPE-OF-SERVICE must = "013" or "029" 2436 Relational edit between TYPE-OF-SERVICE and TOOTH-SURFACE-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.TOOTH-SURFACE-CODE), then fns.isEqualToAny(@val.TYPE-OF-SERVICE, "013", "029")' TOOTH-SURFACE-CODE,TYPE-OF-SERVICE COT198,COT186











1,342 No logic changes COT188-0001 RULE-1660 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT188 HCBS-TAXONOMY 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: HCBS-TAXONOMY HCBS-TAXONOMY COT188











1,343 Retired: Other reasons COT189-0001
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT189 SERVICING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























1,344 No logic changes COT189-0006 RULE-1662 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT189 SERVICING-PROV-NUM 2 If TYPE-OF-SERVICE = 119, 120, 121, or 122, then SERVICING-PROV-NUM must be 8-filled 2413 Relational edit between SERVICING-PROV-NUM and TYPE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.isEqualToAny(@val.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@val.SERVICING-PROV-NUM)' TYPE-OF-SERVICE,SERVICING-PROV-NUM COT186,COT189











1,345 Logic updated: other COT189-0007 RULE-1663 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT189 SERVICING-PROV-NUM 3 If ( SERVICING-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then SERVICING-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-OT-COT00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003 PROV-IDENTIFIERS PRV00005 For every record of type CLAIM-LINE-RECORD-OT, if fns.hasValue(@secondaryRecord.SERVICING-PROV-NUM) && !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type CLAIM-HEADER-RECORD-OT that matches on the join keys, where fns.isEqual(@tertiaryRecord.PROV-IDENTIFIER-TYPE, "1") TYPE-OF-CLAIM COT037 SERVICING-PROV-NUM COT189 PROV-IDENTIFIER-TYPE PRV077 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE COT017,COT020,COT019,COT035 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE COT155,COT159,COT158,COT221 SUBMITTING-STATE,SERVICING-PROV-NUM
SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081
1,346 Merged COT190-0001 RULE-1665 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT190 SERVICING-PROV-NPI-NUM 1 If SERVICING-PROV-NPI-NUM not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.SERVICING-PROV-NPI-NUM), then fns.isValidNPI(@val.SERVICING-PROV-NPI-NUM)' SERVICING-PROV-NPI-NUM COT190











1,347 Merged COT190-0002 RULE-1665 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT190 SERVICING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.SERVICING-PROV-NPI-NUM), then fns.isValidNPI(@val.SERVICING-PROV-NPI-NUM)' SERVICING-PROV-NPI-NUM COT190











1,348 No logic changes COT190-0004 RULE-1666 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT190 SERVICING-PROV-NPI-NUM 2 If TYPE-OF-SERVICE = 119, 120, 121, or 122, then SERVICING-PROV-NPI-NUM must be 8-filled 2412 Relational edit between SERVICING-PROV-NPI-NUM and TYPE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.isEqualToAny(@val.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@val.SERVICING-PROV-NPI-NUM)' TYPE-OF-SERVICE,SERVICING-PROV-NPI-NUM COT186,COT190











1,349 No logic changes COT190-0005 RULE-1667 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT190 SERVICING-PROV-NPI-NUM 2 If TYPE-OF-SERVICE= "121", then SERVICING-PROV-NPI must be 8-filled 2411 Relational edit between SERVICING-PROV-NPI and TYPE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.isEqual(@val.TYPE-OF-SERVICE, "121"), then !fns.hasValue(@val.SERVICING-PROV-NPI-NUM)' TYPE-OF-SERVICE,SERVICING-PROV-NPI-NUM COT186,COT190











1,350 Logic updated: other COT190-0006 RULE-1668 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT190 SERVICING-PROV-NPI-NUM 3 If ( SERVICING-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then SERVICING-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003 PROV-IDENTIFIERS PRV00005 For every record of type CLAIM-LINE-RECORD-OT, if fns.hasValue(@secondaryRecord.SERVICING-PROV-NUM) && !fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type CLAIM-HEADER-RECORD-OT that matches on the join keys, where fns.isEqual(@tertiaryRecord.PROV-IDENTIFIER-TYPE, "2") TYPE-OF-CLAIM COT037 SERVICING-PROV-NUM COT189 PROV-IDENTIFIER-TYPE PRV077 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE COT017,COT020,COT019,COT035 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE COT155,COT159,COT158,COT221 SUBMITTING-STATE,SERVICING-PROV-NPI-NUM
SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081
1,351 No logic changes COT191-0001 RULE-1669 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT191 SERVICING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY SERVICING-PROV-TAXONOMY COT191











1,352 No logic changes COT191-0002 RULE-1670 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT191 SERVICING-PROV-TAXONOMY 2 If TYPE-OF-SERVICE = 119, 120, 121, or 122, then SERVICING-PROV-TAXONOMY must be 8-filled 2414 Relational edit between SERVICING-PROV-TAXONOMY and TYPE-OF-SERVICE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.isEqualToAny(@val.TYPE-OF-SERVICE, "119", "120", "121", "122"), then !fns.hasValue(@val.SERVICING-PROV-TAXONOMY)' TYPE-OF-SERVICE,SERVICING-PROV-TAXONOMY COT186,COT191











1,353 No logic changes COT192-0001 RULE-1671 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT192 SERVICING-PROV-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE SERVICING-PROV-TYPE COT192











1,354 No logic changes COT193-0001 RULE-1672 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT193 SERVICING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY SERVICING-PROV-SPECIALTY COT193











1,355 No logic changes COT194-0001 RULE-1673 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT194 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION COT194











1,356 No logic changes COT195-0001 RULE-1674 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT195 TOOTH-DESIGNATION-SYSTEM 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: TOOTH-DESIGNATION-SYSTEM TOOTH-DESIGNATION-SYSTEM COT195











1,357 No logic changes COT196-0001 RULE-1675 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT196 TOOTH-NUM 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: TOOTH-NUM TOOTH-NUM COT196











1,358 No logic changes COT197-0001 RULE-1676 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT197 TOOTH-QUAD-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: TOOTH-QUAD-CODE TOOTH-QUAD-CODE COT197











1,359 No logic changes COT198-0001 RULE-1677 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT198 TOOTH-SURFACE-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: TOOTH-SURFACE-CODE TOOTH-SURFACE-CODE COT198











1,360 Logic updated: string matching COT199-0001 RULE-1678 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT199 ORIGINATION-ADDR-LN1 1 If ORIGINATION-ADDR-LN1 is populated, it must contains valid characters. 120 Field contains invalid characters - ORIGINATION-ADDR-LN1 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.ORIGINATION-ADDR-LN1), then fns.matches(@val.ORIGINATION-ADDR-LN1, "^[^|*]*$")' ORIGINATION-ADDR-LN1 COT199











1,361 Logic updated: string matching COT200-0001 RULE-1679 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT200 ORIGINATION-ADDR-LN2 1 If ORIGINATION-ADDR-LN2 is populated, it must contains valid characters. 120 Field contains invalid characters - ORIGINATION-ADDR-LN2 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.ORIGINATION-ADDR-LN2), then fns.matches(@val.ORIGINATION-ADDR-LN2, "^[^|*]*$")' ORIGINATION-ADDR-LN2 COT200











1,362 Logic updated: string matching COT201-0001 RULE-1680 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT201 ORIGINATION-CITY 1 If ORIGINATION-CITY is populated, it must contains valid characters. 120 Field contains invalid characters - ORIGINATION-CITY 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.ORIGINATION-CITY), then fns.matches(@val.ORIGINATION-CITY, "^[^|*]*$")' ORIGINATION-CITY COT201











1,363 No logic changes COT202-0001 RULE-1681 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT202 ORIGINATION-STATE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: STATE ORIGINATION-STATE COT202











1,364 No logic changes COT203-0001 RULE-1682 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT203 ORIGINATION-ZIP-CODE 1 If ORIGINATION-ZIP-CODE not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.ORIGINATION-ZIP-CODE), then fns.matches(@val.ORIGINATION-ZIP-CODE, "^[0-9]{5}|[0-9]{9}$")' ORIGINATION-ZIP-CODE COT203











1,365 Logic updated: string matching COT204-0001 RULE-1683 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT204 DESTINATION-ADDR-LN1 1 If DESTINATION-ADDR-LN1 is populated, it must contains valid characters. 120 Field contains invalid characters - DESTINATION-ADDR-LN1 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.DESTINATION-ADDR-LN1), then fns.matches(@val.DESTINATION-ADDR-LN1, "^[^|*]*$")' DESTINATION-ADDR-LN1 COT204











1,366 Logic updated: string matching COT205-0001 RULE-1684 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT205 DESTINATION-ADDR-LN2 1 If DESTINATION-ADDR-LN2 is populated, it must contains valid characters. 120 Field contains invalid characters - DESTINATION-ADDR-LN2 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.DESTINATION-ADDR-LN2), then fns.matches(@val.DESTINATION-ADDR-LN2, "^[^|*]*$")' DESTINATION-ADDR-LN2 COT205











1,367 No logic changes COT205-0003 RULE-1685 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT205 DESTINATION-ADDR-LN2 2 If DESTINATION-ADDR-LN2 is not 8-filled, then DESTINATION-ADDR-LN2 must <> DESTINATION-ADDR-LN1 2259 Relational edit between DESTINATION-ADDR-LN2 and DESTINATION-ADDR-LN1 failed (duplicate value entered) 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.DESTINATION-ADDR-LN2), then !fns.isEqual(@val.DESTINATION-ADDR-LN2, @val.DESTINATION-ADDR-LN1)' DESTINATION-ADDR-LN2,DESTINATION-ADDR-LN1 COT205,COT204











1,368 Logic updated: string matching COT206-0001 RULE-1686 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT206 DESTINATION-CITY 1 If DESTINATION-CITY is populated, it must contains valid characters. 120 Field contains invalid characters - DESTINATION-CITY 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.DESTINATION-CITY), then fns.matches(@val.DESTINATION-CITY, "^[^|*]*$")' DESTINATION-CITY COT206











1,369 No logic changes COT207-0001 RULE-1687 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT207 DESTINATION-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: STATE DESTINATION-STATE COT207











1,370 No logic changes COT208-0001 RULE-1688 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT208 DESTINATION-ZIP-CODE 1 If DESTINATION-ZIP-CODE not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.DESTINATION-ZIP-CODE), then fns.matches(@val.DESTINATION-ZIP-CODE, "^[0-9]{5}|[0-9]{9}$")' DESTINATION-ZIP-CODE COT208











1,371 No logic changes COT209-0001 RULE-1689 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT209 BENEFIT-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: BENEFIT-TYPE BENEFIT-TYPE COT209











1,372 No logic changes COT210-0001 RULE-1690 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT210 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT COT210











1,373 No logic changes COT210-0002 RULE-1691 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT210 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If CHIP-CODE [ELIGIBLE] = "0" , "1", or "2", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT must <> "02" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-OT-COT00003] = MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] 3034 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and CHIP-CODE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqualToAny(@primaryRecord.CHIP-CODE, "0", "1", "2"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "02")' CHIP-CODE ELG054 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT COT210

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM COT155,COT157



1,374 Logic updated: other COT210-0003 RULE-1692 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT210 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] = "0", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT must <> "01" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-OT-COT00003] = MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] 3035 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqual(@primaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "00"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "01")' MEDICAID-BASIS-OF-ELIGIBILITY ELG084 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT COT210

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG082,ELG080 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT157,COT155



1,375 No logic changes COT211-0001 RULE-1693 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT211 XIX-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: XIX-MBESCBES-CATEGORY-OF-SERVICE XIX-MBESCBES-CATEGORY-OF-SERVICE COT211











1,376 No logic changes COT211-0002 RULE-1694 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT211 XIX-MBESCBES-CATEGORY-OF-SERVICE 3 XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMOT] must <> ("14", "35", "42", or "44") where SEX = "M" [ELIGIBLE] and MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-OT-COT00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-OT-COT00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3016 Relational edit between XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMOT] and SEX [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqual(@primaryRecord.SEX, "M"), then !fns.isEqualToAny(@secondaryRecord.XIX-MBESCBES-CATEGORY-OF-SERVICE, "14", "35", "42", "44")' SEX ELG023 XIX-MBESCBES-CATEGORY-OF-SERVICE COT211

MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE COT157,COT155



1,377 Merged COT212-0001 RULE-1695 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT212 XXI-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: XXI-MBESCBES-CATEGORY-OF-SERVICE XXI-MBESCBES-CATEGORY-OF-SERVICE COT212











1,378 Merged COT212-0002 RULE-1695 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT212 XXI-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: XXI-MBESCBES-CATEGORY-OF-SERVICE XXI-MBESCBES-CATEGORY-OF-SERVICE COT212











1,379 No logic changes COT213-0001 RULE-1697 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT213 OTHER-INSURANCE-AMT 1 If OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 OTHER-INSURANCE-AMT COT213











1,380 Logic updated: string matching COT214-0001 RULE-1698 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT214 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION COT214











1,381 Moved to R&C COT216-0002
CLAIMOT FILE-HEADER-RECORD-OT-COT00001 COT216 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range

























1,382 Merged COT217-0001 RULE-1702 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT217 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE COT217











1,383 Merged COT217-0002 RULE-1702 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT217 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE COT217











1,384 Merged COT217-0003 RULE-1702 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT217 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE COT217











1,385 No logic changes COT218-0001 RULE-1703 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT218 PROCEDURE-CODE-MOD-3 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-3 COT218











1,386 Retired: Other reasons COT218-0002
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT218 PROCEDURE-CODE-MOD-3 2 If PROCEDURE-CODE-3 is 8-filled, then PROCEDURE-CODE-MOD-3 must be 8-filled 2384 Relational edit between PROCEDURE-CODE-MOD-3 and PROCEDURE-CODE-3 failed

























1,387 Retired: Other reasons COT218-0003
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT218 PROCEDURE-CODE-MOD-3 2 If PROCEDURE-CODE-3 is not 8-filled, then PROCEDURE-CODE-MOD-3 must not be 8-filled 2384 Relational edit between PROCEDURE-CODE-MOD-3 and PROCEDURE-CODE-3 failed

























1,388 No logic changes COT219-0001 RULE-1706 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT219 PROCEDURE-CODE-MOD-4 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-4 COT219











1,389 Retired: Other reasons COT219-0002
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT219 PROCEDURE-CODE-MOD-4 2 If PROCEDURE-CODE-4 is 8-filled, then PROCEDURE-CODE-MOD-4 must be 8-filled 2385 Relational edit between PROCEDURE-CODE-MOD-4 and PROCEDURE-CODE-4 failed

























1,390 Retired: Other reasons COT219-0003
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT219 PROCEDURE-CODE-MOD-4 2 If PROCEDURE-CODE-4 is not 8-filled, then PROCEDURE-CODE-MOD-4 must not be 8-filled 2385 Relational edit between PROCEDURE-CODE-MOD-4 and PROCEDURE-CODE-4 failed

























1,391 Logic updated: other COT220-0001 RULE-1709 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT220 HCPCS-RATE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.HCPCS-RATE), then fns.matches(@val.HCPCS-RATE, "^[^|*]*$")' HCPCS-RATE COT220











1,392 Merged COT221-0001 RULE-1710 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT221 ADJUDICATION-DATE 1 ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE COT221











1,393 Merged COT221-0002 RULE-1710 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT221 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE COT221











1,394 Logic updated: other COT221-0005 RULE-1712 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT221 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-OT COT00003 FILE-HEADER-RECORD-OT COT00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE COT221 END-OF-TIME-PERIOD COT010









1,395 No logic changes COT222-0001 RULE-1713 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT222 SELF-DIRECTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: SELF-DIRECTION-TYPE SELF-DIRECTION-TYPE COT222











1,396 Logic updated: string matching COT223-0001 RULE-1714 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT223 PRE-AUTHORIZATION-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PRE-AUTHORIZATION-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'if fns.hasValue(@val.PRE-AUTHORIZATION-NUM), then fns.matches(@val.PRE-AUTHORIZATION-NUM, "^[^|*]*$")' PRE-AUTHORIZATION-NUM COT223











1,397 No logic changes COT224-0001 RULE-1715 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT224 NDC-UNIT-OF-MEASURE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: NDC-UNIT-OF-MEASURE NDC-UNIT-OF-MEASURE COT224











1,398 No logic changes COT225-0001 RULE-1716 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT225 NDC-QUANTITY 1 If NDC-QUANTITY is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: S9(6)V999 NDC-QUANTITY COT225











1,399 Logic updated: string matching COT226-0001 RULE-1717 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 COT226 PROV-LOCATION-ID 1 If characters in text string are not alpha characters (A-Z), numbers (0-9) 120 Field contains invalid characters - PROV-LOCATION-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID COT226











1,400 No logic changes COT227-0001 RULE-1718 CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT227 PROCEDURE-CODE-MOD-2 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: PROCEDURE-CODE-MOD PROCEDURE-CODE-MOD-2 COT227











1,401 Retired: Other reasons COT227-0003
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT227 PROCEDURE-CODE-MOD-2 2 If PROCEDURE-CODE-2 is 8-filled, then PROCEDURE-CODE-MOD-2 must be 8-filled 2383 Relational edit between PROCEDURE-CODE-MOD-2 and PROCEDURE-CODE-2 failed

























1,402 Retired: Other reasons COT227-0004
CLAIMOT CLAIM-LINE-RECORD-OT-COT00003 COT227 PROCEDURE-CODE-MOD-2 2 If PROCEDURE-CODE-2 is not 8-filled, then PROCEDURE-CODE-MOD-2 must not be 8-filled 2383 Relational edit between PROCEDURE-CODE-MOD-2 and PROCEDURE-CODE-2 failed

























1,403 No logic changes CRX001-0001 RULE-6301 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CRX001











1,404 Moved to R&C CRX001-0004
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX001 RECORD-ID 2 If FILE-NAME = "CLAIM-RX", then the first 3 positions of RECORD-ID must = "CRX" 150 Invalid or missing RECORD-ID

























1,405 Moved to R&C CRX003-0001
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX003 SUBMISSION-TRANSACTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























1,406 Moved to R&C CRX004-0001
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX004 FILE-ENCODING-SPECIFICATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list

























1,407 Moved to R&C CRX006-0001
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX006 FILE-NAME 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,408 Moved to R&C CRX007-0001
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX007 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,409 Moved to R&C CRX007-0004
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























1,410 Merged CRX008-0001 RULE-1728 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED CRX008











1,411 Merged CRX008-0002 RULE-1728 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED CRX008











1,412 Moved to R&C CRX008-0003
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed

























1,413 Moved to R&C CRX008-0004
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























1,414 Merged CRX009-0001 RULE-1732 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD CRX009











1,415 Merged CRX009-0002 RULE-1732 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX009 START-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD CRX009











1,416 Moved to R&C CRX009-0003
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























1,417 Moved to R&C CRX009-0004
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























1,418 Merged CRX010-0001 RULE-1736 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX010 END-OF-TIME-PERIOD 1 If ENDING-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD CRX010











1,419 Merged CRX010-0002 RULE-1736 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD CRX010











1,420 Moved to R&C CRX010-0003
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX010 END-OF-TIME-PERIOD 2-M
2122


























1,421 Moved to R&C CRX010-0004
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX010 END-OF-TIME-PERIOD 2-M
2019


























1,422 Moved to R&C CRX011-0001
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX011 FILE-STATUS-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,423 Moved to R&C CRX011-0002
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























1,424 Moved to R&C CRX012-0001
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX012 SSN-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,425 Logic updated: other CRX012-0002 RULE-1743 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX012 SSN-INDICATOR 3 Value for SSN-INDICATOR [CLAIMRX] must match SSN-INDICATOR [ELIGIBLE] 3010 Relational edit between SSN-INDICATOR [CLAIMRX] and SSN-INDICATOR [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) FILE-HEADER-RECORD-RX CRX00001 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@primaryRecord.SSN-INDICATOR) && fns.hasValue(@secondaryRecord.SSN-INDICATOR), then fns.isEqual(@primaryRecord.SSN-INDICATOR, @secondaryRecord.SSN-INDICATOR)' SSN-INDICATOR CRX012 SSN-INDICATOR ELG012

SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD CRX007,CRX009,CRX010 SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD ELG007,ELG009,ELG010



1,426 No logic changes CRX013-0001 RULE-1744 CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX013 TOT-REC-CNT 1 If TOT-REC-CNT = 0. 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT CRX013











1,427 Moved to R&C CRX013-0002
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record

























1,428 Moved to R&C CRX014-0001
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























1,429 No logic changes CRX016-0001 RULE-6454 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CRX016











1,430 Moved to R&C CRX016-0004
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX016 RECORD-ID 2 If FILE-NAME = "CLAIM-RX", then the first 3 positions of RECORD-ID must = "CRX" 150 Invalid or missing RECORD-ID

























1,431 No logic changes CRX017-0001 RULE-1749 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX017 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE CRX017











1,432 Logic updated: other CRX017-0004 RULE-1750 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-RX-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 FILE-HEADER-RECORD-RX CRX00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE CRX017 SUBMITTING-STATE CRX007









1,433 Retired: Other reasons CRX018-0001
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX018 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,434 No logic changes CRX018-0004 RULE-1752 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-HEADER-RECORD-RX CRX00002



Field RECORD-NUMBER should be unique across all records of type CLAIM-HEADER-RECORD-RX RECORD-NUMBER CRX018











1,435 Logic updated: string matching CRX019-0001 RULE-1753 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX019 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG CRX019











1,436 Logic updated: string matching CRX020-0001 RULE-1754 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX020 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ CRX020











1,437 Retired: required value checks CRX021-0001
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX021 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported.

























1,438 Retired: MSIS ID checks CRX022-0001
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX022 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,439 Retired: MSIS ID checks CRX022-0002
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX022 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,440 Logic updated: other CRX022-0004 RULE-1758 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX022 MSIS-IDENTIFICATION-NUM 3 MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-RX-CRX00002] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3026 Edit that claim has matching PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 record failed 3 Relational error E3001 Missing corresponding record (multi file) (ex. missing eligibility record for claim header) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-RX CRX00002

For every record of type CLAIM-HEADER-RECORD-RX, there must be a valid record of type PRIMARY-DEMOGRAPHICS-ELIGIBILITY that matches on the join keys





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022



1,441 No logic changes CRX023-0001 RULE-1759 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX023 CROSSOVER-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CROSSOVER-INDICATOR CROSSOVER-INDICATOR CRX023











1,442 No logic changes CRX024-0001 RULE-1760 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX024 1115A-DEMONSTRATION-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: 1115A-DEMONSTRATION-IND 1115A-DEMONSTRATION-IND CRX024











1,443 No logic changes CRX024-0003 RULE-1761 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX024 1115A-DEMONSTRATION-IND 3 If 1115A-DEMONSTRATION-IND [ELIGIBLE] = 0or 8-filled, then 1115A-DEMONSTRATION-IND must = 0 or 8-filled where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-RX-CRX00002] = MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] 3055 An 1115A-DEMONSTRATION-IND does not match the 1115A-DEMONSTRATION-IND in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) 1115A-DEMONSTRATION-INFORMATION ELG00018 CLAIM-HEADER-RECORD-RX CRX00002

'if fns.isEqual(@primaryRecord.1115A-DEMONSTRATION-IND, "0") || !fns.hasValue(@primaryRecord.1115A-DEMONSTRATION-IND), then fns.isEqual(@secondaryRecord.1115A-DEMONSTRATION-IND, "0") || !fns.hasValue(@secondaryRecord.1115A-DEMONSTRATION-IND)' 1115A-DEMONSTRATION-IND ELG233 1115A-DEMONSTRATION-IND CRX024

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG230,ELG232 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022



1,444 No logic changes CRX025-0001 RULE-1762 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX025 ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-IND ADJUSTMENT-IND CRX025











1,445 No logic changes CRX026-0001 RULE-1763 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX026 ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE ADJUSTMENT-REASON-CODE CRX026











1,446 Merged CRX027-0001 RULE-1764 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX027 ADJUDICATION-DATE 1 If ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CRX027











1,447 Merged CRX027-0002 RULE-1764 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX027 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CRX027











1,448 Logic updated: other CRX027-0005 RULE-1766 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX027 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 FILE-HEADER-RECORD-RX CRX00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE CRX027 END-OF-TIME-PERIOD CRX010









1,449 Merged CRX028-0001 RULE-1767 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX028 MEDICAID-PAID-DATE 1 If MEDICAID-PAID-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE CRX028











1,450 Merged CRX028-0002 RULE-1767 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX028 MEDICAID-PAID-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD MEDICAID-PAID-DATE CRX028











1,451 No logic changes CRX029-0001 RULE-1769 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX029 TYPE-OF-CLAIM 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-CLAIM TYPE-OF-CLAIM CRX029











1,452 No logic changes CRX030-0001 RULE-1770 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX030 CLAIM-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-STATUS CRX030











1,453 No logic changes CRX031-0001 RULE-1771 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX031 CLAIM-STATUS-CATEGORY 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS-CATEGORY CLAIM-STATUS-CATEGORY CRX031











1,454 No logic changes CRX032-0001 RULE-1772 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX032 SOURCE-LOCATION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: SOURCE-LOCATION SOURCE-LOCATION CRX032











1,455 Logic updated: string matching CRX033-0001 RULE-1773 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX033 CHECK-NUM 1 If CHECK-NUM is populated, it must contains valid characters. 120 Field contains invalid characters - CHECK-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.CHECK-NUM), then fns.matches(@val.CHECK-NUM, "^[^|*]*$")' CHECK-NUM CRX033











1,456 Merged CRX034-0001 RULE-1774 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX034 CHECK-EFF-DATE 1 If CHECK-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE CRX034











1,457 Merged CRX034-0002 RULE-1774 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX034 CHECK-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD CHECK-EFF-DATE CRX034











1,458 No logic changes CRX035-0001 RULE-1776 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX035 CLAIM-PYMT-REM-CODE-1 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-1 CRX035











1,459 Merged CRX035-0002 RULE-1777 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX035 CLAIM-PYMT-REM-CODE-1 2 If CLAIM-PYMT-REM-CODE-1 is not 8-filled, then CLAIM-PYMT-REM-CODE-1 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CRX035,CRX036,CRX037,CRX038











1,460 No logic changes CRX036-0001 RULE-1778 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX036 CLAIM-PYMT-REM-CODE-2 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-2 CRX036











1,461 Merged CRX036-0002 RULE-1777 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX036 CLAIM-PYMT-REM-CODE-2 2 If CLAIM-PYMT-REM-CODE-2 is not 8-filled, then CLAIM-PYMT-REM-CODE-2 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CRX035,CRX036,CRX037,CRX038











1,462 No logic changes CRX036-0003 RULE-1780 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX036 CLAIM-PYMT-REM-CODE-2 2 CLAIM-PYMT-REM-CODE-2 must be 8-filled if value for CLAIM-PYMT-REM-CODE-1 is 8-filled 2243 Relational edit between CLAIM-PYMT-REM-CODE-2 and CLAIM-PYMT-REM-CODE-1 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-1), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2)' CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2 CRX035,CRX036











1,463 No logic changes CRX037-0001 RULE-1781 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX037 CLAIM-PYMT-REM-CODE-3 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-3 CRX037











1,464 Merged CRX037-0002 RULE-1777 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX037 CLAIM-PYMT-REM-CODE-3 2 If CLAIM-PYMT-REM-CODE-3 is not 8-filled, then CLAIM-PYMT-REM-CODE-3 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CRX035,CRX036,CRX037,CRX038











1,465 No logic changes CRX037-0003 RULE-1783 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX037 CLAIM-PYMT-REM-CODE-3 2 CLAIM-PYMT-REM-CODE-3 must be 8-filled if value for CLAIM-PYMT-REM-CODE-2 is 8-filled 2244 Relational edit between CLAIM-PYMT-REM-CODE-3 and CLAIM-PYMT-REM-CODE-2 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-2), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3)' CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3 CRX036,CRX037











1,466 No logic changes CRX038-0001 RULE-1784 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX038 CLAIM-PYMT-REM-CODE-4 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-4 CRX038











1,467 Merged CRX038-0002 RULE-1777 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX038 CLAIM-PYMT-REM-CODE-4 2 If CLAIM-PYMT-REM-CODE-4 is not 8-filled, then CLAIM-PYMT-REM-CODE-4 must <> value for the other instances of CLAIM-PYMT-REM-CODE 2144 Duplicate values of CLAIM-PYMT-REM-CODE entered 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



The values of the following fields should be unique (non-repeating) within each record: CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CLAIM-PYMT-REM-CODE-1,CLAIM-PYMT-REM-CODE-2,CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CRX035,CRX036,CRX037,CRX038











1,468 No logic changes CRX038-0003 RULE-1786 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX038 CLAIM-PYMT-REM-CODE-4 2 CLAIM-PYMT-REM-CODE-4 must be 8-filled if value for CLAIM-PYMT-REM-CODE-3 is 8-filled 2245 Relational edit between CLAIM-PYMT-REM-CODE-4 and CLAIM-PYMT-REM-CODE-3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-3), then !fns.hasValue(@val.CLAIM-PYMT-REM-CODE-4)' CLAIM-PYMT-REM-CODE-3,CLAIM-PYMT-REM-CODE-4 CRX037,CRX038











1,469 No logic changes CRX039-0001 RULE-1787 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX039 TOT-BILLED-AMT 1 if TOT-BILLED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-BILLED-AMT CRX039











1,470 No logic changes CRX039-0003 RULE-1788 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX039 TOT-BILLED-AMT 2 If TYPE-OF-CLAIM = "4", "D", or "X", then TOT-BILLED-AMT must = 0 2426 Relational edit between TOT-BILLED-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "4", "D", "X"), then fns.isEqual(@val.TOT-BILLED-AMT, "0.00")' TYPE-OF-CLAIM,TOT-BILLED-AMT CRX029,CRX039











1,471 No logic changes CRX039-0005 RULE-1789 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX039 TOT-BILLED-AMT 2 The absolute value of the sum of BILLED-AMT on each detail line record must = absolute value of TOT-BILLED-AMT 2425 Relational edit between TOT-BILLED-AMT and BILLED-AMT 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'fns.isDollarSumEqual(@primaryRecord.TOT-BILLED-AMT, @secondaryRecords.BILLED-AMT)' TOT-BILLED-AMT CRX039 BILLED-AMT CRX121

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,472 No logic changes CRX040-0001 RULE-1790 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX040 TOT-ALLOWED-AMT 1 if TOT-ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-ALLOWED-AMT CRX040











1,473 No logic changes CRX040-0002 RULE-1791 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX040 TOT-ALLOWED-AMT 2 TOT-ALLOWED-AMT must = the sum of ALLOWED-AMT at each claim line level, where SUBMITTING-STATE, ICN-ORIG, and ICN-ADJ match 2125 Relational edit between TOT-ALLOWED-AMT and ALLOWED-AMT failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'fns.isDollarSumEqual(@primaryRecord.TOT-ALLOWED-AMT, @secondaryRecords.ALLOWED-AMT)' TOT-ALLOWED-AMT CRX040 ALLOWED-AMT CRX122

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,474 No logic changes CRX041-0001 RULE-1792 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX041 TOT-MEDICAID-PAID-AMT 1 if TOT-MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICAID-PAID-AMT CRX041











1,475 No logic changes CRX042-0001 RULE-1793 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX042 TOT-COPAY-AMT 1 If TOT-COPAY-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-COPAY-AMT CRX042











1,476 No logic changes CRX043-0001 RULE-1794 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX043 TOT-MEDICARE-DEDUCTIBLE-AMT 1 If TOT-MEDICARE-DEDUCTIBLE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-DEDUCTIBLE-AMT CRX043











1,477 Logic updated: other CRX043-0003 RULE-1795 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX043 TOT-MEDICARE-DEDUCTIBLE-AMT 2 TOT-MEDICARE-DEDUCTIBLE-AMT must be <=TOT-BILLED-AMT 2127 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT) && fns.hasValue(@val.TOT-BILLED-AMT), then fns.isLessThanOrEqual(@val.TOT-MEDICARE-DEDUCTIBLE-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-BILLED-AMT CRX043,CRX039











1,478 No logic changes CRX043-0005 RULE-1796 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX043 TOT-MEDICARE-DEDUCTIBLE-AMT 2 The absolute value of the sum of MEDICARE-DEDUCTIBLE-AMT on each detail line record must = absolute value of TOT-MEDICARE-DEDUCTIBLE-AMT 2430 Relational edit between TOT-MEDICARE-DEDUCTIBLE-AMT and MEDICARE-DEDUCTIBLE-AMT 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'fns.isDollarSumEqual(@primaryRecord.TOT-MEDICARE-DEDUCTIBLE-AMT, @secondaryRecords.MEDICARE-DEDUCTIBLE-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT CRX043 MEDICARE-DEDUCTIBLE-AMT CRX127

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,479 No logic changes CRX044-0001 RULE-1797 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX044 TOT-MEDICARE-COINS-AMT 1 if TOT-MEDICARE-COINS-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-MEDICARE-COINS-AMT CRX044











1,480 Logic updated: other CRX044-0004 RULE-1798 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX044 TOT-MEDICARE-COINS-AMT 2 TOT-MEDICARE-COINS-AMT must be < TOT-BILLED-AMT 2126 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-BILLED-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-BILLED-AMT), then fns.isLessThan(@val.TOT-MEDICARE-COINS-AMT, @val.TOT-BILLED-AMT)' TOT-MEDICARE-COINS-AMT,TOT-BILLED-AMT CRX044,CRX039











1,481 No logic changes CRX044-0005 RULE-1799 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX044 TOT-MEDICARE-COINS-AMT 2 If TOT-MEDICARE-DEDUCTIBLE-AMT is 8-filled, then TOT-MEDICARE-COINS-AMT must equal 8-filled 2428 Relational edit between TOT-MEDICARE-COINS-AMT and TOT-MEDICARE-DEDUCTIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if !fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then !fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TOT-MEDICARE-DEDUCTIBLE-AMT,TOT-MEDICARE-COINS-AMT CRX043,CRX044











1,482 No logic changes CRX044-0006 RULE-1800 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX044 TOT-MEDICARE-COINS-AMT 2 If TYPE-OF-CLAIM = "3", "C", "W", then TOT-MEDICARE-COINS-AMT must be 8-filled 2429 Relational edit between TOT-MEDICARE-COINS-AMT and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then !fns.hasValue(@val.TOT-MEDICARE-COINS-AMT)' TYPE-OF-CLAIM,TOT-MEDICARE-COINS-AMT CRX029,CRX044











1,483 No logic changes CRX044-0007 RULE-1801 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX044 TOT-MEDICARE-COINS-AMT 2 If MEDICARE-COMB-DED-IND = "1", then TOT-MEDICARE-COINS-AMT must = 0 2427 Relational edit between TOT-MEDICARE-COINS-AMT and MEDICARE-COMB-DED-IND 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqual(@val.MEDICARE-COMB-DED-IND, "1"), then fns.isEqual(@val.TOT-MEDICARE-COINS-AMT, "0.00")' MEDICARE-COMB-DED-IND,TOT-MEDICARE-COINS-AMT CRX160,CRX044











1,484 No logic changes CRX045-0001 RULE-1802 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX045 TOT-TPL-AMT 1 If TOT-TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-TPL-AMT CRX045











1,485 Logic updated: other CRX045-0002 RULE-1803 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX045 TOT-TPL-AMT 2 The absolute value of TOT-TPL-AMT must be <= the absolute value of (TOT-BILLED-AMT minus TOT-MEDICARE-COINS-AMT plus TOT-MEDICARE-DEDUCIBLE-AMT) 2432 Relational edit between TOT-TPL-AMT, TOT-BILLED-AMT, MEDICARE-COINS-AMT, and TOT-MEDICARE-DEDUCIBLE-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.TOT-TPL-AMT) && fns.hasValue(@val.TOT-BILLED-AMT) && fns.hasValue(@val.TOT-MEDICARE-COINS-AMT) && fns.hasValue(@val.TOT-MEDICARE-DEDUCTIBLE-AMT), then fns.isLessThanOrEqual(@val.TOT-TPL-AMT, fns.remainingLiability(@val.TOT-BILLED-AMT, @val.TOT-MEDICARE-COINS-AMT, @val.TOT-MEDICARE-DEDUCTIBLE-AMT))' TOT-TPL-AMT,TOT-BILLED-AMT,TOT-MEDICARE-COINS-AMT,TOT-MEDICARE-DEDUCTIBLE-AMT CRX045,CRX039,CRX044,CRX043











1,486 No logic changes CRX047-0001 RULE-1804 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX047 TOT-OTHER-INSURANCE-AMT 1 If TOT-OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TOT-OTHER-INSURANCE-AMT CRX047











1,487 No logic changes CRX048-0001 RULE-1805 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX048 OTHER-INSURANCE-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-INSURANCE-IND OTHER-INSURANCE-IND CRX048











1,488 No logic changes CRX049-0001 RULE-1806 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX049 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION CRX049











1,489 No logic changes CRX050-0001 RULE-1807 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX050 SERVICE-TRACKING-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: SERVICE-TRACKING-TYPE SERVICE-TRACKING-TYPE CRX050











1,490 No logic changes CRX051-0001 RULE-1808 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX051 SERVICE-TRACKING-PAYMENT-AMT 1 If SERVICE-TRACKING-PAYMENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 SERVICE-TRACKING-PAYMENT-AMT CRX051











1,491 No logic changes CRX051-0005 RULE-1809 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX051 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE <> "00" AND (TOT-MEDICAID-PAID-AMT = 0 ), then SERVICE-TRACKING-PAYMENT-AMT must be > 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if !fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isEqual(@val.TOT-MEDICAID-PAID-AMT, "0.00"), then fns.isGreaterThanZero(@val.SERVICE-TRACKING-PAYMENT-AMT)' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT CRX050,CRX041,CRX051











1,492 No logic changes CRX051-0006 RULE-1810 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX051 SERVICE-TRACKING-PAYMENT-AMT 2 If (SERVICE-TRACKING-TYPE = "00" AND (TOT-MEDICAID-PAID-AMT > 0), then SERVICE-TRACKING-PAYMENT-AMT must = 0 2410 Relational edit between SERVICE-TRACKING-PAYMENT-AMT , SERVICE-TRACKING-TYPE, and TOT-MEDICAID-PAID-AMT failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqual(@val.SERVICE-TRACKING-TYPE, "00") && fns.isGreaterThanZero(@val.TOT-MEDICAID-PAID-AMT), then fns.isEqual(@val.SERVICE-TRACKING-PAYMENT-AMT, "0.00")' SERVICE-TRACKING-TYPE,TOT-MEDICAID-PAID-AMT,SERVICE-TRACKING-PAYMENT-AMT CRX050,CRX041,CRX051











1,493 No logic changes CRX052-0001 RULE-1811 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX052 FIXED-PAYMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: FIXED-PAYMENT-IND FIXED-PAYMENT-IND CRX052











1,494 No logic changes CRX053-0001 RULE-1812 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX053 FUNDING-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-CODE FUNDING-CODE CRX053











1,495 No logic changes CRX054-0001 RULE-1813 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX054 FUNDING-SOURCE-NONFEDERAL-SHARE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: FUNDING-SOURCE-NONFEDERAL-SHARE FUNDING-SOURCE-NONFEDERAL-SHARE CRX054











1,496 No logic changes CRX055-0001 RULE-1814 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX055 PROGRAM-TYPE 1 Valueis not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PROGRAM-TYPE PROGRAM-TYPE CRX055











1,497 No logic changes CRX055-0004 RULE-1815 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX055 PROGRAM-TYPE 3 If PROGRAM-TYPE = "13", then STATE-PLAN-OPTION-TYPE [ELIGIBLE] must = "02" where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-IP-CIP00002] = MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-IP-CIP00002] = SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] 3047 Relational edit between PROGRAM TYPE and STATE-PLAN-OPTION-TYPE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) STATE-PLAN-OPTION-PARTICIPATION ELG00011 CLAIM-HEADER-RECORD-RX CRX00002

'if fns.isEqual(@secondaryRecord.PROGRAM-TYPE, "13"), then fns.isEqual(@primaryRecord.STATE-PLAN-OPTION-TYPE, "02")' STATE-PLAN-OPTION-TYPE ELG163 PROGRAM-TYPE CRX055

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG160,ELG162 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022



1,498 No logic changes CRX055-0005 RULE-1816 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX055 PROGRAM-TYPE 2 If PROGRAM-TYPE = "07", then WAIVER-TYPE must = "06" through "20" 2388 Relational edit between PROGRAM-TYPE and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqual(@val.PROGRAM-TYPE, "07"), then fns.isEqualToAny(@val.WAIVER-TYPE, "06", "07", "08", "09", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20")' PROGRAM-TYPE,WAIVER-TYPE CRX055,CRX068











1,499 Logic updated: string matching CRX056-0001 RULE-1817 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX056 PLAN-ID-NUMBER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PLAN-ID-NUMBER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.PLAN-ID-NUMBER), then fns.matches(@val.PLAN-ID-NUMBER, "^[^|*]*$")' PLAN-ID-NUMBER CRX056











1,500 No logic changes CRX056-0004 RULE-1818 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX056 PLAN-ID-NUMBER 2 If TYPE-OF-CLAIM <> "3", "C" or "W", then PLAN-ID-NUMBER must be 8-filled 2363 Relational edit between PLAN-ID-NUM and TYPE-OF-CLAIM failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if !fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then !fns.hasValue(@val.PLAN-ID-NUMBER)' TYPE-OF-CLAIM,PLAN-ID-NUMBER CRX029,CRX056











1,501 No logic changes CRX056-0005 RULE-1819 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX056 PLAN-ID-NUMBER 2 If TYPE-OF-SERVICE = "119", "120", OR "122", then PLAN-ID-NUM must = BILLING-PROV-NUM 2364 Relational edit between PLAN-ID-NUM, BILLING-PROV-NUM, and TYPE-OF-SERVICE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-SERVICE, "119", "120", "122"), then fns.isEqual(@primaryRecord.PLAN-ID-NUMBER, @primaryRecord.BILLING-PROV-NUM)' PLAN-ID-NUMBER,BILLING-PROV-NUM CRX056,CRX070 TYPE-OF-SERVICE CRX134

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,502 Logic updated: string matching CRX057-0001 RULE-1820 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX057 NATIONAL-HEALTH-CARE-ENTITY-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-ID, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-ID CRX057











1,503 No logic changes CRX057-0003 RULE-1821 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX057 NATIONAL-HEALTH-CARE-ENTITY-ID 2 If START-OF-TIME-PERIOD >= 20151105, then NATIONAL-HEALTH-CARE-ENTITY-ID must not be (8-filled or 9-filled) 2332 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 FILE-HEADER-RECORD-RX CRX00001

'if fns.isGreaterThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, "2015-11-05"), then fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID CRX057 START-OF-TIME-PERIOD CRX009









1,504 No logic changes CRX057-0005 RULE-1822 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX057 NATIONAL-HEALTH-CARE-ENTITY-ID 3 If TYPE-OF-CLAIM = "C", "3", or "W", then NATIONAL-HEALTH-CARE-ENTITY-ID [CLAIM-HEADER-RECORD-RX-CRX00002] must = NATIONAL-HEALTH-CARE-ENTITY-ID [MANAGED-CARE-PARTICIPATION-ELG00014], where SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] and MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-RX-CRX00002] = MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014]. 3027 Edit that NATIONAL-HEALTH-CARE-ENTITY-ID matches value in MANAGED-CARE-PARTICIPATION-ELG00014 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) MANAGED-CARE-PARTICIPATION ELG00014 CLAIM-HEADER-RECORD-RX CRX00002

'if fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.isEqual(@secondaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID, @primaryRecord.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID ELG194 TYPE-OF-CLAIM,NATIONAL-HEALTH-CARE-ENTITY-ID CRX029,CRX057

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG189,ELG191 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022



1,505 No logic changes CRX058-0001 RULE-1823 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX058 PAYMENT-LEVEL-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PAYMENT-LEVEL-IND PAYMENT-LEVEL-IND CRX058











1,506 No logic changes CRX059-0001 RULE-1824 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX059 MEDICARE-REIM-TYPE 1 Value must be a valid value 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-REIM-TYPE MEDICARE-REIM-TYPE CRX059











1,507 Retired: required value checks CRX060-0001
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX060 CLAIM-LINE-COUNT 1 If CLAIM-LINE-COUNT =0 113 Required data element has not been reported.

























1,508 Logic updated: other CRX060-0002 RULE-1826 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX060 CLAIM-LINE-COUNT 2 CLAIM-LINE-COUNT must = total number of lines in the claim 2445 Value does not equal the total number of lines in the claim 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to Many) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'if fns.hasValue(@primaryRecord.CLAIM-LINE-COUNT), then fns.isValueEqualToNumberOfRecords(@primaryRecord.CLAIM-LINE-COUNT, @secondaryRecords.LINE-NUM-ORIG)' CLAIM-LINE-COUNT CRX060 LINE-NUM-ORIG CRX114

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,509 No logic changes CRX061-0001 RULE-1827 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX061 FORCED-CLAIM-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: FORCED-CLAIM-IND FORCED-CLAIM-IND CRX061











1,510 Logic updated: string matching CRX062-0001 RULE-1828 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX062 PATIENT-CONTROL-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PATIENT-CONTROL-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.PATIENT-CONTROL-NUM), then fns.matches(@val.PATIENT-CONTROL-NUM, "^[^|*]*$")' PATIENT-CONTROL-NUM CRX062











1,511 Logic updated: string matching CRX063-0001 RULE-1829 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX063 ELIGIBLE-LAST-NAME 1 ELIGIBLE-LAST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid character - ELIGIBLE-LAST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.ELIGIBLE-LAST-NAME), then fns.matches(@val.ELIGIBLE-LAST-NAME, "^[^|*]*$")' ELIGIBLE-LAST-NAME CRX063











1,512 Logic updated: string matching CRX064-0001 RULE-1830 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX064 ELIGIBLE-FIRST-NAME 1 ELIGIBLE-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - ELIGIBLE-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.ELIGIBLE-FIRST-NAME), then fns.matches(@val.ELIGIBLE-FIRST-NAME, "^[^|*]*$")' ELIGIBLE-FIRST-NAME CRX064











1,513 Logic updated: string matching CRX065-0001 RULE-1831 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX065 ELIGIBLE-MIDDLE-INIT 1 ELIGIBLE-MIDDLE-INIT must not contain non-alphabetic characters 120 Field contains invalid characters - ELIGIBLE-MIDDLE-INIT 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.ELIGIBLE-MIDDLE-INIT), then fns.matches(@val.ELIGIBLE-MIDDLE-INIT, "^[^|*]*$")' ELIGIBLE-MIDDLE-INIT CRX065











1,514 Merged CRX066-0001 RULE-1832 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX066 DATE-OF-BIRTH 1 If DATE-OF-BIRTH is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH CRX066











1,515 Merged CRX066-0002 RULE-1832 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX066 DATE-OF-BIRTH 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH CRX066











1,516 Logic updated: other CRX066-0007 RULE-1834 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX066 DATE-OF-BIRTH 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled
and
CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64",
then DATE-OF-BIRTH must be <= DATE-OF-DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-RX-CRX00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002]		 3037 Relational edit between DATE-OF-BIRTH and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-RX CRX00002 ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 'if fns.hasValue(@secondaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@secondaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64") && fns.hasValue(@primaryRecord.DATE-OF-BIRTH) && fns.hasValue(@tertiaryRecord.DATE-OF-DEATH), then fns.isLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @tertiaryRecord.DATE-OF-DEATH)' DATE-OF-BIRTH CRX066 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-DEATH ELG025 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019
1,517 Logic updated: other CRX066-0008 RULE-1835 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX066 DATE-OF-BIRTH 3 If CONCEPTION-TO-BIRTH [ELIGIBLE] <> "1" and ELIGIBILITY-GROUP [ELIGIBLE] <> "64", then DATE-OF-BIRTH must = DATE-OF-BIRTH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-RX-CRX00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3023 A DATE-OF-BIRTH does not match the DATE-OF-BIRTH in the ELIGIBLE file 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-RX CRX00002 ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 'if fns.hasValue(@secondaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@secondaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64") && fns.hasValue(@primaryRecord.DATE-OF-BIRTH) && fns.hasValue(@tertiaryRecord.DATE-OF-BIRTH), then fns.isEqual(@primaryRecord.DATE-OF-BIRTH, @tertiaryRecord.DATE-OF-BIRTH)' DATE-OF-BIRTH CRX066 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-BIRTH ELG024 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019
1,518 No logic changes CRX067-0001 RULE-1836 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX067 HEALTH-HOME-PROV-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-HOME-PROV-IND HEALTH-HOME-PROV-IND CRX067











1,519 No logic changes CRX067-0003 RULE-1837 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX067 HEALTH-HOME-PROV-IND 2 If HEALTH-HOME-ENTITY-NAME is not 8-filled, then HEALTH-HOME-PROV-IND must = "1" 2294 Relational edit between HEALTH-HOME-PROV-IND and HEALTH-HOME-ENTITY-NAME failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.isEqual(@val.HEALTH-HOME-PROV-IND, "1")' HEALTH-HOME-ENTITY-NAME,HEALTH-HOME-PROV-IND CRX096,CRX067











1,520 No logic changes CRX068-0001 RULE-1838 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX068 WAIVER-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-TYPE WAIVER-TYPE CRX068











1,521 Merged CRX069-0001 RULE-1839 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX069 WAIVER-ID 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state. 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID CRX069











1,522 Merged CRX069-0005 RULE-1840 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX069 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CRX068,CRX069











1,523 Merged CRX069-0009 RULE-1839 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX069 WAIVER-ID 3 WAIVER-ID must = waiver ID in state-provided crosswalk 3029 Edit with an external reference (state provided WAIVER-ID-/WAIVER-TYPE crosswalk) failed 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID CRX069











1,524 Merged CRX069-0010 RULE-1840 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX069 WAIVER-ID 2 If WAIVER-TYPE is 8-filled, then WAIVER-ID must be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CRX068,CRX069











1,525 Merged CRX069-0011 RULE-1840 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX069 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID CRX068,CRX069











1,526 Retired: Other reasons CRX070-0001
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX070 BILLING-PROV-NUM 1 Value is not included in the valid code list 125 Value is not included in a state supplied valid code list

























1,527 Logic updated: other CRX070-0004 RULE-1845 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX070 BILLING-PROV-NUM 3 If ( BILLING-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then BILLING-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-RX CRX00002

For every record of type CLAIM-HEADER-RECORD-RX, if fns.hasValue(@secondaryRecord.BILLING-PROV-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "1") PROV-IDENTIFIER-TYPE PRV077 BILLING-PROV-NUM,TYPE-OF-CLAIM CRX070,CRX029

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,BILLING-PROV-NUM CRX017,CRX070



1,528 Merged CRX071-0001 RULE-1846 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX071 BILLING-PROV-NPI-NUM 1 If BILLING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM CRX071











1,529 Merged CRX071-0002 RULE-1846 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX071 BILLING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.BILLING-PROV-NPI-NUM), then fns.isValidNPI(@val.BILLING-PROV-NPI-NUM)' BILLING-PROV-NPI-NUM CRX071











1,530 Logic updated: other CRX071-0006 RULE-1848 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX071 BILLING-PROV-NPI-NUM 3 If ( BILLING-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then BILLING-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-RX CRX00002

For every record of type CLAIM-HEADER-RECORD-RX, if fns.hasValue(@secondaryRecord.BILLING-PROV-NPI-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "2") PROV-IDENTIFIER-TYPE PRV077 BILLING-PROV-NPI-NUM,TYPE-OF-CLAIM CRX071,CRX029

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,BILLING-PROV-NPI-NUM CRX017,CRX071



1,531 No logic changes CRX072-0001 RULE-1849 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX072 BILLING-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY BILLING-PROV-TAXONOMY CRX072











1,532 No logic changes CRX073-0001 RULE-1850 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX073 BILLING-PROV-SPECIALTY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY BILLING-PROV-SPECIALTY CRX073











1,533 Retired: Other reasons CRX074-0001
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX074 PRESCRIBING-PROV-NUM 1 Value is not included a state supplied valid code list 125 Value is not included in a state supplied valid code list

























1,534 Merged CRX075-0001 RULE-1852 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX075 PRESCRIBING-PROV-NPI-NUM 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.PRESCRIBING-PROV-NPI-NUM), then fns.isValidNPI(@val.PRESCRIBING-PROV-NPI-NUM)' PRESCRIBING-PROV-NPI-NUM CRX075











1,535 Merged CRX075-0002 RULE-1852 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX075 PRESCRIBING-PROV-NPI-NUM 1 If PRESCRIBING-PROV-NPI-NUM not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.PRESCRIBING-PROV-NPI-NUM), then fns.isValidNPI(@val.PRESCRIBING-PROV-NPI-NUM)' PRESCRIBING-PROV-NPI-NUM CRX075











1,536 No logic changes CRX076-0001 RULE-1854 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX076 PRESCRIBING-PROV-TAXONOMY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY PRESCRIBING-PROV-TAXONOMY CRX076











1,537 No logic changes CRX077-0001 RULE-1855 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX077 PRESCRIBING-PROV-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TYPE PRESCRIBING-PROV-TYPE CRX077











1,538 No logic changes CRX078-0001 RULE-1856 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX078 PRESCRIBING-PROV-SPECIALTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-SPECIALTY PRESCRIBING-PROV-SPECIALTY CRX078











1,539 Logic updated: string matching CRX079-0001 RULE-1857 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX079 MEDICARE-HIC-NUM 1 Field contains invalid characters -MEDICARE-HIC-NUM 120 Field contains invalid characters -MEDICARE-HIC-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.matches(@val.MEDICARE-HIC-NUM, "^[^|*]*$")' MEDICARE-HIC-NUM CRX079











1,540 No logic changes CRX079-0003 RULE-1858 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX079 MEDICARE-HIC-NUM 2 If CROSSOVER-INDICATOR= "1" and MEDICARE-BENEFICIARY-IDENTIFIER is 8-filled, then MEDICARE-HIC-NUM must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.hasValue(@val.MEDICARE-HIC-NUM)' CROSSOVER-INDICATOR,MEDICARE-BENEFICIARY-IDENTIFIER,MEDICARE-HIC-NUM CRX023,CRX105,CRX079











1,541 Logic updated: string matching CRX081-0001 RULE-1859 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX081 REMITTANCE-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - REMITTANCE-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.REMITTANCE-NUM), then fns.matches(@val.REMITTANCE-NUM, "^[^|*]*$")' REMITTANCE-NUM CRX081











1,542 No logic changes CRX082-0001 RULE-1860 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX082 BORDER-STATE-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: BORDER-STATE-IND BORDER-STATE-IND CRX082











1,543 Merged CRX084-0001 RULE-1861 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX084 DATE-PRESCRIBED 1 DATE-PRESCRIBED must be in valid date format (CCYYMMDD) 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD DATE-PRESCRIBED CRX084











1,544 Merged CRX084-0002 RULE-1861 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX084 DATE-PRESCRIBED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD DATE-PRESCRIBED CRX084











1,545 Merged CRX084-0004 RULE-1863 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX084 DATE-PRESCRIBED 2 DATE-PRESCRIBED must be <= PRESCRIPTION-FILL-DATE 2022 Relational edit between DATE-PRESCRIBED and PRESCRIPTION-FILL-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.DATE-PRESCRIBED) && fns.hasValue(@val.PRESCRIPTION-FILL-DATE), then fns.isLessThanOrEqual(@val.DATE-PRESCRIBED, @val.PRESCRIPTION-FILL-DATE)' DATE-PRESCRIBED,PRESCRIPTION-FILL-DATE CRX084,CRX085











1,546 Logic updated: other CRX084-0005 RULE-1864 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX084 DATE-PRESCRIBED 2 DATE-PRESCRIBED must be <= ADJUDICATION-DATE [CLAIM-HEADER-RECORD-RX] 2020 Relational edit between DATE-PRESCRIBED and ADJUDICATION-DATE [CLAIM-HEADER-RECORD-RX] failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.DATE-PRESCRIBED) && fns.hasValue(@val.ADJUDICATION-DATE), then fns.isLessThanOrEqual(@val.DATE-PRESCRIBED, @val.ADJUDICATION-DATE)' DATE-PRESCRIBED,ADJUDICATION-DATE CRX084,CRX027











1,547 Logic updated: other CRX084-0006 RULE-1865 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX084 DATE-PRESCRIBED 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then DATE-PRESCRIBED must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-RX-CRX00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3003 Relational edit between DATE-PRESCRIBED and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-RX CRX00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.DATE-PRESCRIBED), then fns.isLessThanOrEqual(@secondaryRecord.DATE-PRESCRIBED, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 DATE-PRESCRIBED CRX084

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022



1,548 Logic updated: other CRX084-0007 RULE-1866 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX084 DATE-PRESCRIBED 2 DATE-PRESCRIBED must be <= END-OF-TIME-PERIOD 2021 Relational edit between DATE-PRESCRIBED and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 FILE-HEADER-RECORD-RX CRX00001

'if fns.hasValue(@val.DATE-PRESCRIBED) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.DATE-PRESCRIBED, @fileHeader.END-OF-TIME-PERIOD)' DATE-PRESCRIBED CRX084 END-OF-TIME-PERIOD CRX010









1,549 Merged CRX085-0001 RULE-1867 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX085 PRESCRIPTION-FILL-DATE 1 If PRESCRIPTION-FILL-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD PRESCRIPTION-FILL-DATE CRX085











1,550 Merged CRX085-0002 RULE-1867 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX085 PRESCRIPTION-FILL-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD PRESCRIPTION-FILL-DATE CRX085











1,551 Logic updated: other CRX085-0003 RULE-1869 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX085 PRESCRIPTION-FILL-DATE 2 PRESCRIPTION-FILL-DATE must be <= END-OF-TIME-PERIOD 2092 Relational edit between PRESCRIPTION-FILL-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 FILE-HEADER-RECORD-RX CRX00001

'if fns.hasValue(@val.PRESCRIPTION-FILL-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.PRESCRIPTION-FILL-DATE, @fileHeader.END-OF-TIME-PERIOD)' PRESCRIPTION-FILL-DATE CRX085 END-OF-TIME-PERIOD CRX010









1,552 Merged CRX085-0005 RULE-1863 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX085 PRESCRIPTION-FILL-DATE 2-M
2022
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.DATE-PRESCRIBED) && fns.hasValue(@val.PRESCRIPTION-FILL-DATE), then fns.isLessThanOrEqual(@val.DATE-PRESCRIBED, @val.PRESCRIPTION-FILL-DATE)' DATE-PRESCRIBED,PRESCRIPTION-FILL-DATE CRX084,CRX085











1,553 Logic updated: other CRX085-0007 RULE-1871 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX085 PRESCRIPTION-FILL-DATE 3 If DATE-OF-DEATH [ELIGIBLE] is not (8-filled or 9-filled), then PRESCRIPTION-FILL-DATE must be <= DATE OF DEATH [ELIGIBLE] where MSIS-IDENTIFICATION-NUM [CLAIM-HEADER-RECORD-RX-CRX00002] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3006 Relational edit between PRESCRIPTION-FILL-DATE and DATE OF DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-HEADER-RECORD-RX CRX00002

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.PRESCRIPTION-FILL-DATE), then fns.isLessThanOrEqual(@secondaryRecord.PRESCRIPTION-FILL-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 PRESCRIPTION-FILL-DATE CRX085

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX017,CRX022



1,554 No logic changes CRX086-0001 RULE-1872 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX086 COMPOUND-DRUG-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: COMPOUND-DRUG-IND COMPOUND-DRUG-IND CRX086











1,555 No logic changes CRX087-0001 RULE-1873 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX087 BENEFICIARY-COINSURANCE-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COINSURANCE-AMOUNT CRX087











1,556 Merged CRX088-0001 RULE-1875 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX088 BENEFICIARY-COINSURANCE-DATE-PAID 1 If BENEFICIARY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID CRX088











1,557 Merged CRX088-0002 RULE-1875 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX088 BENEFICIARY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COINSURANCE-DATE-PAID CRX088











1,558 No logic changes CRX089-0001 RULE-1876 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX089 BENEFICIARY-COPAYMENT-AMOUNT 1 If BENEFICIARY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-COPAYMENT-AMOUNT CRX089











1,559 No logic changes CRX090-0001 RULE-1877 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX090 BENEFICIARY-COPAYMENT-DATE-PAID 1 If BENEFICIARY-COPAYMENT-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-COPAYMENT-DATE-PAID CRX090











1,560 No logic changes CRX092-0001 RULE-6772 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX092 BENEFICIARY-DEDUCTIBLE-AMOUNT 1 If BENEFICIARY-DEDUCTIBLE-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BENEFICIARY-DEDUCTIBLE-AMOUNT CRX092











1,561 Merged CRX093-0001 RULE-1879 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX093 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 If BENEFICIARY-DEDUCTIBLE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID CRX093











1,562 Merged CRX093-0002 RULE-1879 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX093 BENEFICIARY-DEDUCTIBLE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD BENEFICIARY-DEDUCTIBLE-DATE-PAID CRX093











1,563 No logic changes CRX094-0001 RULE-1881 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX094 CLAIM-DENIED-INDICATOR 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-DENIED-INDICATOR CLAIM-DENIED-INDICATOR CRX094











1,564 No logic changes CRX094-0003 RULE-1882 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX094 CLAIM-DENIED-INDICATOR 2 If TYPE-OF-CLAIM = "Z", then CLAIM-DENIED-INDICATOR must = "0" 2242 Relational edit between CLAIM-DENIED-INDICATOR and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqual(@val.TYPE-OF-CLAIM, "Z"), then fns.isEqual(@val.CLAIM-DENIED-INDICATOR, "0")' TYPE-OF-CLAIM,CLAIM-DENIED-INDICATOR CRX029,CRX094











1,565 No logic changes CRX095-0001 RULE-1883 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX095 COPAY-WAIVED-IND 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: COPAY-WAIVED-IND COPAY-WAIVED-IND CRX095











1,566 Logic updated: string matching CRX096-0001 RULE-1884 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX096 HEALTH-HOME-ENTITY-NAME 1 If HEALTH-HOME-ENTITY-NAME is populated, it must contains valid characters. 120 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.matches(@val.HEALTH-HOME-ENTITY-NAME, "^[^|*]*$")' HEALTH-HOME-ENTITY-NAME CRX096











1,567 No logic changes CRX098-0001 RULE-1885 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX098 THIRD-PARTY-COINSURANCE-AMOUNT-PAID 1 If THIRD-PARTY-COINSURANCE-AMOUNT-PAID is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COINSURANCE-AMOUNT-PAID CRX098











1,568 Merged CRX099-0001 RULE-1887 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX099 THIRD-PARTY-COINSURANCE-DATE-PAID 1 If THIRD-PARTY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID CRX099











1,569 Merged CRX099-0002 RULE-1887 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX099 THIRD-PARTY-COINSURANCE-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COINSURANCE-DATE-PAID CRX099











1,570 No logic changes CRX100-0001 RULE-6974 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX100 THIRD-PARTY-COPAYMENT-AMOUNT-PAID 1 If THIRD-PARTY-COPAYMENT-AMOUNT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 THIRD-PARTY-COPAYMENT-AMOUNT-PAID CRX100











1,571 Merged CRX101-0001 RULE-1889 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX101 THIRD-PARTY-COPAYMENT-DATE-PAID 1 If THIRD-PARTY-COINSURANCE-DATE-PAID is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID CRX101











1,572 Merged CRX101-0002 RULE-1889 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX101 THIRD-PARTY-COPAYMENT-DATE-PAID 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be a valid date of the form CCYYMMDD THIRD-PARTY-COPAYMENT-DATE-PAID CRX101











1,573 Merged CRX102-0001 RULE-1891 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX102 DISPENSING-PRESCRIPTION-DRUG-PROV-NPI 1 If DISPENSING-PRESCRIPTION-DRUG-PROV-NPII not > or = 0 120 Field contains invalid characters - DISPENSING-PRESCRIPTION-DRUG-PROV-NPI 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.DISPENSING-PRESCRIPTION-DRUG-PROV-NPI), then fns.isValidNPI(@val.DISPENSING-PRESCRIPTION-DRUG-PROV-NPI)' DISPENSING-PRESCRIPTION-DRUG-PROV-NPI CRX102











1,574 Merged CRX102-0002 RULE-1891 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX102 DISPENSING-PRESCRIPTION-DRUG-PROV-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.DISPENSING-PRESCRIPTION-DRUG-PROV-NPI), then fns.isValidNPI(@val.DISPENSING-PRESCRIPTION-DRUG-PROV-NPI)' DISPENSING-PRESCRIPTION-DRUG-PROV-NPI CRX102











1,575 Logic updated: other CRX102-0004 RULE-1893 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX102 DISPENSING-PRESCRIPTION-DRUG-PROV-NPI 3 If ( DISPENSING-PRESCRIPTION-DRUG-PROV-NPI is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then DISPENSING-PRESCRIPTION-DRUG-PROV-NPI must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "2" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3028 Edit that NPI corresponds to NPI in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-RX CRX00002

For every record of type CLAIM-HEADER-RECORD-RX, if fns.hasValue(@secondaryRecord.DISPENSING-PRESCRIPTION-DRUG-PROV-NPI) && !fns.isEqualToAny(@secondaryRecord.DISPENSING-PRESCRIPTION-DRUG-PROV-NPI,"3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "2") PROV-IDENTIFIER-TYPE PRV077 DISPENSING-PRESCRIPTION-DRUG-PROV-NPI CRX102

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,DISPENSING-PRESCRIPTION-DRUG-PROV-NPI CRX017,CRX102



1,576 No logic changes CRX103-0001 RULE-1894 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX103 DISPENSING-PRESCRIPTION-DRUG-PROV-TAXONOMY 1 Value is not included in the value code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-TAXONOMY DISPENSING-PRESCRIPTION-DRUG-PROV-TAXONOMY CRX103











1,577 Merged CRX104-0001 RULE-1895 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX104 HEALTH-HOME-PROVIDER-NPI 1 If HEALTH-HOME-PROVIDER-NPI not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI CRX104











1,578 Merged CRX104-0002 RULE-1895 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX104 HEALTH-HOME-PROVIDER-NPI 1 If NPI <> 8888888888 or 9999999999 then NPI must pass NPI check digit algorithm. 103 Value is not included in the valid code list 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.HEALTH-HOME-PROVIDER-NPI), then fns.isValidNPI(@val.HEALTH-HOME-PROVIDER-NPI)' HEALTH-HOME-PROVIDER-NPI CRX104











1,579 Logic updated: string matching CRX105-0001 RULE-1897 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX105 MEDICARE-BENEFICIARY-IDENTIFIER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - MEDICARE-BENEFICIARY-IDENTIFIER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.matches(@val.MEDICARE-BENEFICIARY-IDENTIFIER, "^[^|*]*$")' MEDICARE-BENEFICIARY-IDENTIFIER CRX105











1,580 No logic changes CRX105-0003 RULE-1898 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX105 MEDICARE-BENEFICIARY-IDENTIFIER 2 If END-OF-TIME-PERIOD >= "20151110", CROSSOVER-INDICATOR= "1" and MEDICARE-HIC-NUM is 8-filled, then MEDICARE-BENEFICIARY-IDENTIFIER must not be 8-filled 2329 Relational edit between MEDICARE-HIC-NUM, CROSSOVER-INDICATOR, and MEDICARE-BENEFICIARY-IDENTIFIER failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 FILE-HEADER-RECORD-RX CRX00001

'if fns.isGreaterThanOrEqual(@fileHeader.END-OF-TIME-PERIOD, "2015-11-10") && fns.isEqual(@val.CROSSOVER-INDICATOR, "1") && !fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER)' CROSSOVER-INDICATOR,MEDICARE-HIC-NUM,MEDICARE-BENEFICIARY-IDENTIFIER CRX023,CRX079,CRX105 END-OF-TIME-PERIOD CRX010









1,581 Logic updated: string matching CRX106-0001 RULE-1899 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX106 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION CRX106











1,582 Moved to R&C CRX108-0001
CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX108 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,583 Moved to R&C CRX108-0004
CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX108 RECORD-ID 2 If FILE-NAME = "CLAIM-RX", then the first 3 positions of RECORD-ID must = "CRX" 150 Invalid or missing RECORD-ID

























1,584 No logic changes CRX109-0001 RULE-1902 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX109 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE CRX109











1,585 Logic updated: other CRX109-0004 RULE-1903 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX109 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-RX-CIP00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-RX CRX00003 FILE-HEADER-RECORD-RX CRX00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE CRX109 SUBMITTING-STATE CRX007









1,586 Retired: Other reasons CRX110-0001
CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX110 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,587 No logic changes CRX110-0004 RULE-1905 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX110 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CLAIM-LINE-RECORD-RX CRX00003



Field RECORD-NUMBER should be unique across all records of type CLAIM-LINE-RECORD-RX RECORD-NUMBER CRX110











1,588 Retired: MSIS ID checks CRX111-0001
CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX111 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,589 Retired: MSIS ID checks CRX111-0002
CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX111 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,590 No logic changes CRX111-0004 RULE-1908 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX111 MSIS-IDENTIFICATION-NUM 2 If TYPE-OF-CLAIM = "4", "D", OR "X", then the first byte of MSIS-IDENTIFICATION-NUM must = "&" 2331 Relational edit between MSIS-IDENTIFICATION-NUM and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "4", "D", "X"), then fns.matches(@secondaryRecord.MSIS-IDENTIFICATION-NUM, "^&.*$")' TYPE-OF-CLAIM CRX029 MSIS-IDENTIFICATION-NUM CRX111

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,591 Logic updated: parent/child overlap CRX111-0005 RULE-1909 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX111 MSIS-IDENTIFICATION-NUM 2 ICN-ORIG [SUBMITTING-STATE CLAIM-LINE-RECORD-RX-CRX00003] must = ICN-ORIG [CLAIM-HEADER-RECORD-RX-CRX00002],
and ICN-ADJ [SUBMITTING-STATE CLAIM-LINE-RECORD-RX-CRX00003] must = ICN-ADJ [CLAIM-HEADER-RECORD-RX-CRX00002],
and ADJUDICATION-DATE [SUBMITTING-STATE CLAIM-LINE-RECORD-RX-CRX00003] must = ADJUDICATION-DATE [CLAIM-HEADER-RECORD-RX-CRX00002] on any record in the file,
and SUBMITTING-STATE [CLAIM-LINE-RECORD-RX-CRX00003] must = SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] on the same record in the file		 2192 Edit that CLAIM-LINE-RECORD-RX-CRX00003 child record has a CLAIM-HEADER-RECORD-RX-CRX00002 parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

record CLAIM-LINE-RECORD-RX has corresponding parent record CLAIM-HEADER-RECORD-RX





SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,592 Logic updated: string matching CRX112-0001 RULE-1910 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX112 ICN-ORIG 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.ICN-ORIG), then fns.matches(@val.ICN-ORIG, "^[^|*]*$")' ICN-ORIG CRX112











1,593 Logic updated: string matching CRX113-0001 RULE-1911 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX113 ICN-ADJ 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.ICN-ADJ), then fns.matches(@val.ICN-ADJ, "^[^|*]*$")' ICN-ADJ CRX113











1,594 No logic changes CRX114-0001 RULE-1912 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX114 LINE-NUM-ORIG 1 if LINE-NUM-ORIG not >=0. 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.LINE-NUM-ORIG), then fns.isNonNegative(@val.LINE-NUM-ORIG)' LINE-NUM-ORIG CRX114











1,595 No logic changes CRX115-0001 RULE-1913 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX115 LINE-NUM-ADJ 1 if LINE-NUM-ADJ not >=0. 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.isNonNegative(@val.LINE-NUM-ADJ)' LINE-NUM-ADJ CRX115











1,596 No logic changes CRX115-0002 RULE-1914 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX115 LINE-NUM-ADJ 2 If LINE-ADJUSTMENT-IND = "0", then LINE-NUM-ADJ must be 8-filled 2312 Relational edit between LINE-NUM-ADJ and LINE-ADJUSTMENT-IND failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.isEqual(@val.LINE-ADJUSTMENT-IND, "0"), then !fns.hasValue(@val.LINE-NUM-ADJ)' LINE-ADJUSTMENT-IND,LINE-NUM-ADJ CRX116,CRX115











1,597 No logic changes CRX115-0003 RULE-1915 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX115 LINE-NUM-ADJ 2 If ADJUSTMENT-IND = "0", then LINE-NUM-ADJ must be 8-filled 2311 Relational edit between LINE-NUM-ADJ and ADJUSTMENT-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqual(@primaryRecord.ADJUSTMENT-IND, "0"), then !fns.hasValue(@secondaryRecord.LINE-NUM-ADJ)' ADJUSTMENT-IND CRX025 LINE-NUM-ADJ CRX115

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,598 No logic changes CRX116-0001 RULE-1916 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX116 LINE-ADJUSTMENT-IND 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: LINE-ADJUSTMENT-IND LINE-ADJUSTMENT-IND CRX116











1,599 No logic changes CRX116-0002 RULE-1917 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX116 LINE-ADJUSTMENT-IND 2 If LINE-NUM-ADJ is not 8-filled, then LINE-ADJUSTMENT-IND must not be 8-filled 2310 Relational edit between LINE-ADJUSTMENT-IND and LINE-NUM-ADJ failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.LINE-NUM-ADJ), then fns.hasValue(@val.LINE-ADJUSTMENT-IND)' LINE-NUM-ADJ,LINE-ADJUSTMENT-IND CRX115,CRX116











1,600 No logic changes CRX117-0001 RULE-1918 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX117 LINE-ADJUSTMENT-REASON-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: ADJUSTMENT-REASON-CODE LINE-ADJUSTMENT-REASON-CODE CRX117











1,601 Retired: required value checks CRX118-0001
CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX118 SUBMITTER-ID 1 Value must not be null 113 Required data element has not been reported.

























1,602 No logic changes CRX119-0001 RULE-1920 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX119 CLAIM-LINE-STATUS 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-STATUS CLAIM-LINE-STATUS CRX119











1,603 Merged CRX120-0001 RULE-1921 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX120 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CRX120











1,604 Merged CRX120-0002 RULE-1921 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX120 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CRX120











1,605 Merged CRX120-0003 RULE-1921 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX120 NATIONAL-DRUG-CODE 1 NATIONAL-DRUG-CODE must be in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.NATIONAL-DRUG-CODE), then fns.isValidNationalDrugCode(@val.NATIONAL-DRUG-CODE)' NATIONAL-DRUG-CODE CRX120











1,606 No logic changes CRX121-0001 RULE-1924 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX121 BILLED-AMT 1 If BILLED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 BILLED-AMT CRX121











1,607 No logic changes CRX122-0001 RULE-1925 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX122 ALLOWED-AMT 1 If ALLOWED-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 ALLOWED-AMT CRX122











1,608 No logic changes CRX123-0001 RULE-1926 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX123 COPAY-AMT 1 If COPAY-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(5)V99 COPAY-AMT CRX123











1,609 No logic changes CRX124-0001 RULE-1927 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX124 TPL-AMT 1 If TPL-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 TPL-AMT CRX124











1,610 No logic changes CRX125-0001 RULE-1928 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX125 MEDICAID-PAID-AMT 1 If MEDICAID-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-PAID-AMT CRX125











1,611 No logic changes CRX126-0001 RULE-1929 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX126 MEDICAID-FFS-EQUIVALENT-AMT 1 If MEDICAID-FFS-EQUIVALENT-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICAID-FFS-EQUIVALENT-AMT CRX126











1,612 No logic changes CRX126-0002 RULE-1930 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX126 MEDICAID-FFS-EQUIVALENT-AMT 2 If TYPE-OF-CLAIM = "C", "3", or "W", then MEDICAID-FFS-EQUIVALENT-AMT must not be 8-filled 2443 Relational edit with MEDICAID-FFS-EQUIVALENT-AMT and TYPE-OF-CLAIM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-RX CRX00002 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqualToAny(@primaryRecord.TYPE-OF-CLAIM, "C", "3", "W"), then fns.hasValue(@secondaryRecord.MEDICAID-FFS-EQUIVALENT-AMT)' TYPE-OF-CLAIM CRX029 MEDICAID-FFS-EQUIVALENT-AMT CRX126

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX017,CRX019,CRX020,CRX027 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CRX109,CRX112,CRX113,CRX157



1,613 No logic changes CRX127-0001 RULE-1931 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX127 MEDICARE-DEDUCTIBLE-AMT 1 If MEDICARE-DEDUCTIBLE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICARE-DEDUCTIBLE-AMT CRX127











1,614 No logic changes CRX128-0001 RULE-1932 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX128 MEDICARE-COINS-AMT 1 If MEDICARE-DEDUCTIBLE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICARE-COINS-AMT CRX128











1,615 No logic changes CRX129-0001 RULE-1933 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX129 MEDICARE-PAID-AMT 1 If MEDICARE-PAID-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 MEDICARE-PAID-AMT CRX129











1,616 No logic changes CRX131-0001 RULE-1934 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX131 OT-RX-CLAIM-QUANTITY-ALLOWED 1 If OT-RX-CLAIM-QUANTITY-ALLOWED is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(6)V999 OT-RX-CLAIM-QUANTITY-ALLOWED CRX131











1,617 No logic changes CRX132-0001 RULE-1935 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX132 OT-RX-CLAIM-QUANTITY-ACTUAL 1 If OT-RX-CLAIM-QUANTITY-ACTUAL is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(6)V999 OT-RX-CLAIM-QUANTITY-ACTUAL CRX132











1,618 No logic changes CRX133-0001 RULE-1936 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX133 UNIT-OF-MEASURE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: UNIT-OF-MEASURE UNIT-OF-MEASURE CRX133











1,619 No logic changes CRX134-0001 RULE-1937 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX134 TYPE-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-SERVICE TYPE-OF-SERVICE CRX134











1,620 No logic changes CRX134-0002 RULE-1938 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX134 TYPE-OF-SERVICE 2 If FILE-NAME = "CLAIMRX", then TYPE-OF-SERVICE must = 011, 033, 034, 085 , or 131 2434 Relational edit between TYPE-OF-SERVICE and FILE-NAME failed 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'fns.isEqualToAny(@val.TYPE-OF-SERVICE, "011", "033", "034", "085", "131")' TYPE-OF-SERVICE CRX134











1,621 No logic changes CRX134-0006 RULE-1939 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX134 TYPE-OF-SERVICE 3 If SEX = "M" [ELIGIBLE], then TYPE-OF-SERVICE must <> "086" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-RX-CRX00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-RX-CRX00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3013 Relational edit between TYPE-OF-SERVICE and SEX [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqual(@primaryRecord.SEX, "M"), then !fns.isEqual(@secondaryRecord.TYPE-OF-SERVICE, "086")' SEX ELG023 TYPE-OF-SERVICE CRX134

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX109,CRX111



1,622 No logic changes CRX135-0001 RULE-1940 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX135 HCBS-SERVICE-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: HCBS-SERVICE-CODE HCBS-SERVICE-CODE CRX135











1,623 No logic changes CRX136-0001 RULE-1941 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX136 HCBS-TAXONOMY 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: HCBS-TAXONOMY HCBS-TAXONOMY CRX136











1,624 No logic changes CRX137-0001 RULE-1942 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX137 OTHER-TPL-COLLECTION 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: OTHER-TPL-COLLECTION OTHER-TPL-COLLECTION CRX137











1,625 No logic changes CRX138-0001 RULE-1943 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX138 DAYS-SUPPLY 1 DAYS-SUPPLY must be >=-365 and <=365 105 Value out of range 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.DAYS-SUPPLY), then fns.inRange(@val.DAYS-SUPPLY, -365,365)' DAYS-SUPPLY CRX138











1,626 No logic changes CRX139-0001 RULE-1944 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX139 NEW-REFILL-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: NEW-REFILL-IND NEW-REFILL-IND CRX139











1,627 No logic changes CRX140-0001 RULE-1945 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX140 BRAND-GENERIC-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: BRAND-GENERIC-IND BRAND-GENERIC-IND CRX140











1,628 No logic changes CRX141-0001 RULE-1946 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX141 DISPENSE-FEE 1 If DISPENSE-FEE is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(6)V99 DISPENSE-FEE CRX141











1,629 Logic updated: string matching CRX142-0001 RULE-1947 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX142 PRESCRIPTION-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - ICN-ADJ 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.PRESCRIPTION-NUM), then fns.matches(@val.PRESCRIPTION-NUM, "^[^|*]*$")' PRESCRIPTION-NUM CRX142











1,630 No logic changes CRX143-0001 RULE-1948 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX143 DRUG-UTILIZATION-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: DRUG-UTILIZATION-CODE DRUG-UTILIZATION-CODE CRX143











1,631 No logic changes CRX144-0001 RULE-1949 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX144 DTL-METRIC-DEC-QTY 1 If DTL-METRIC-DEC-QTY is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: S9(7)V999 DTL-METRIC-DEC-QTY CRX144











1,632 No logic changes CRX145-0001 RULE-1950 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX145 COMPOUND-DOSAGE-FORM 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: COMPOUND-DOSAGE-FORM COMPOUND-DOSAGE-FORM CRX145











1,633 No logic changes CRX146-0001 RULE-1951 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX146 REBATE-ELIGIBLE-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: REBATE-ELIGIBLE-INDICATOR REBATE-ELIGIBLE-INDICATOR CRX146











1,634 No logic changes CRX147-0001 RULE-1952 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX147 IMMUNIZATION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: IMMUNIZATION-TYPE IMMUNIZATION-TYPE CRX147











1,635 No logic changes CRX148-0001 RULE-1953 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX148 BENEFIT-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: BENEFIT-TYPE BENEFIT-TYPE CRX148











1,636 No logic changes CRX149-0001 RULE-1954 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX149 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 1 Value is not inlcuded in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CRX149











1,637 No logic changes CRX149-0002 RULE-1955 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX149 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If CHIP-CODE [ELIGIBLE] = "0" , "1", or "2", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT must <> "02" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-RX-CRX00003] = MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] and SUBMITTING-STATE [CLAIM-LINE-RECORD-RX-CRX00003] = SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] 3034 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and CHIP-CODE [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqualToAny(@primaryRecord.CHIP-CODE, "0", "1", "2"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "02")' CHIP-CODE ELG054 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CRX149

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX109,CRX111



1,638 No logic changes CRX149-0003 RULE-1956 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX149 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT 3 If MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] = "0", then CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENTmust <> "01" where MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-RX-CRX00003] = MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] and SUBMITTING-STATE [CLAIM-LINE-RECORD-RX-CRX00003] = SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] 3035 Relational edit between CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT and MEDICAID-BASIS-OF-ELIGIBILITY [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqual(@primaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "00"), then !fns.isEqual(@secondaryRecord.CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT, "01")' MEDICAID-BASIS-OF-ELIGIBILITY ELG084 CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CRX149

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX109,CRX111



1,639 No logic changes CRX150-0001 RULE-1957 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX150 XIX-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: XIX-MBESCBES-CATEGORY-OF-SERVICE XIX-MBESCBES-CATEGORY-OF-SERVICE CRX150











1,640 No logic changes CRX150-0002 RULE-1958 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX150 XIX-MBESCBES-CATEGORY-OF-SERVICE 3 XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMRX] must <> ("14", "35", "42", or "44") where SEX = "M" [ELIGIBLE] and MSIS-IDENTIFICATION-NUM [CLAIM-LINE-RECORD-RX-CRX00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [CLAIM-LINE-RECORD-RX-CRX00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3017 Relational edit between XIX-MBESCBES-CATEGORY-OF-SERVICE [CLAIMRX] and SEX [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 CLAIM-LINE-RECORD-RX CRX00003

'if fns.isEqual(@primaryRecord.SEX, "M"), then !fns.isEqualToAny(@secondaryRecord.XIX-MBESCBES-CATEGORY-OF-SERVICE, "14", "35", "42", "44")' SEX ELG023 XIX-MBESCBES-CATEGORY-OF-SERVICE CRX150

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM CRX109,CRX111



1,641 No logic changes CRX151-0001 RULE-1959 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX151 XXI-MBESCBES-CATEGORY-OF-SERVICE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: XXI-MBESCBES-CATEGORY-OF-SERVICE XXI-MBESCBES-CATEGORY-OF-SERVICE CRX151











1,642 No logic changes CRX152-0001 RULE-1960 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX152 OTHER-INSURANCE-AMT 1 If OTHER-INSURANCE-AMT is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: S9(11)V99 OTHER-INSURANCE-AMT CRX152











1,643 Logic updated: string matching CRX153-0001 RULE-1961 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX153 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION CRX153











1,644 Moved to R&C CRX155-0002
CLAIMRX FILE-HEADER-RECORD-RX-CRX00001 CRX155 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range

























1,645 Retired: Other reasons CRX156-0001
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX156 DISPENSING-PRESCRIPTION-DRUG-PROV-NUM 1 Value is not included a state supplied valid code list 125 Value is not included in a state supplied valid code list

























1,646 Logic updated: other CRX156-0004 RULE-1964 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX156 DISPENSING-PRESCRIPTION-DRUG-PROV-NUM 3 If ( DISPENSING-PRESCRIPTION-DRUG-PROV-NUM is not 8-filled and TYPE-OF-CLAIM <> 3, C, W ), then DISPENSING-PRESCRIPTION-DRUG-PROV-NUM must = PROV-IDENTIFIER [PROVIDER] where PROV-IDENTIFIER-TYPE [PROVIDER] = "1" and SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002] = SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] 3058 Edit that state provider identifier corresponds to state provider identifier in PROV-IDENTIFIERS-PRV00005 failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 CLAIM-HEADER-RECORD-RX CRX00002

For every record of type CLAIM-HEADER-RECORD-RX, if fns.hasValue(@secondaryRecord.DISPENSING-PRESCRIPTION-DRUG-PROV-NUM) && !fns.isEqualToAny(@secondaryRecord.TYPE-OF-CLAIM, "3", "C", "W"), there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-IDENTIFIER-TYPE, "1") PROV-IDENTIFIER-TYPE PRV077 DISPENSING-PRESCRIPTION-DRUG-PROV-NUM,TYPE-OF-CLAIM CRX156,CRX029

SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,DISPENSING-PRESCRIPTION-DRUG-PROV-NUM CRX017,CRX156



1,647 Merged CRX157-0001 RULE-1965 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX157 ADJUDICATION-DATE 1 If ADJUDICATION-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CRX157











1,648 Merged CRX157-0002 RULE-1965 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX157 ADJUDICATION-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be a valid date of the form CCYYMMDD ADJUDICATION-DATE CRX157











1,649 Logic updated: other CRX157-0005 RULE-1967 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX157 ADJUDICATION-DATE 2 ADJUDICATION-DATE must be <= END-OF-TIME-PERIOD 2004 Relational edit between ADJUDICATION-DATE and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-LINE-RECORD-RX CRX00003 FILE-HEADER-RECORD-RX CRX00001

'if fns.hasValue(@val.ADJUDICATION-DATE) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.ADJUDICATION-DATE, @fileHeader.END-OF-TIME-PERIOD)' ADJUDICATION-DATE CRX157 END-OF-TIME-PERIOD CRX010









1,650 No logic changes CRX158-0001 RULE-1968 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX158 SELF-DIRECTION-TYPE 1 Value is not included in the valid code list. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-RX CRX00003



If the field is populated, the value must be contained in the set of valid values with id: SELF-DIRECTION-TYPE SELF-DIRECTION-TYPE CRX158











1,651 Logic updated: string matching CRX159-0001 RULE-1969 CLAIMRX CLAIM-LINE-RECORD-RX-CRX00003 CRX159 PRE-AUTHORIZATION-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - PRE-AUTHORIZATION-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-RX CRX00003



'if fns.hasValue(@val.PRE-AUTHORIZATION-NUM), then fns.matches(@val.PRE-AUTHORIZATION-NUM, "^[^|*]*$")' PRE-AUTHORIZATION-NUM CRX159











1,652 No logic changes CRX160-0001 RULE-1970 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX160 MEDICARE-COMB-DED-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-RX CRX00002



If the field is populated, the value must be contained in the set of valid values with id: MEDICARE-COMB-DED-IND MEDICARE-COMB-DED-IND CRX160











1,653 No logic changes CRX160-0002 RULE-1971 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX160 MEDICARE-COMB-DED-IND 2 If CROSSOVER-INDICATOR = "0" or TYPE-OF-CLAIM = "3", "C", or "W", then MEDICARE-COMB-DED-IND must = 0 2328 Relational edit between MEDICARE-COMB-DED-IND, CROSSOVER-INDICATOR, and TYPE-OF-CLAIM 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.isEqual(@val.CROSSOVER-INDICATOR, "0") || fns.isEqualToAny(@val.TYPE-OF-CLAIM, "3", "C", "W"), then fns.isEqual(@val.MEDICARE-COMB-DED-IND, "0")' CROSSOVER-INDICATOR,TYPE-OF-CLAIM,MEDICARE-COMB-DED-IND CRX023,CRX029,CRX160











1,654 Logic updated: string matching CRX161-0001 RULE-1972 CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX161 PROV-LOCATION-ID 1 If characters in text string are not alpha characters (A-Z), numbers (0-9) 120 Field contains invalid characters - PROV-LOCATION-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-HEADER-RECORD-RX CRX00002



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID CRX161











1,655 Retired: Other reasons CRX161-0002
CLAIMRX CLAIM-HEADER-RECORD-RX-CRX00002 CRX161 PROV-LOCATION-ID 3 PROV-LOCATION-ID [CLAIMRX] must = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] where SUBMITTING-STATE [CLAIM-HEADER-RECORD-RX-CRX00002]= SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SERVICING-PROV-NUM [CLAIMRX] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] 3051 Relational edit between PROV-LOCATION-ID [CLAIMRX] and PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] failed

























1,656 Moved to R&C ELG001-0003
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,657 Moved to R&C ELG001-0004
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG001 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,658 Moved to R&C ELG003-0001
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG003 SUBMISSION-TRANSACTION-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,659 Moved to R&C ELG004-0001
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG004 FILE-ENCODING-SPECIFICATION 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,660 Moved to R&C ELG006-0002
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG006 FILE-NAME 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,661 Moved to R&C ELG006-0003
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG006 FILE-NAME 2 FILE-NAME must = File Type in the File Name Format 2446 Value is inconsistent with File Type in File Name Format

























1,662 Moved to R&C ELG007-0002
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG007 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,663 Moved to R&C ELG007-0004
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























1,664 Merged ELG008-0001 RULE-1982 ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED ELG008











1,665 Merged ELG008-0002 RULE-1982 ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED ELG008











1,666 Moved to R&C ELG008-0003
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed

























1,667 Moved to R&C ELG008-0005
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























1,668 No logic changes ELG009-0001 RULE-1986 ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD ELG009











1,669 Moved to R&C ELG009-0002
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG009 START-OF-TIME-PERIOD 1 DD (in CCYYMMDD) for START-OF-TIME-PERIOD must = "01" 114 Invalid value in DD for START-OF-TIME-PERIOD

























1,670 Moved to R&C ELG009-0003
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























1,671 Moved to R&C ELG009-0004
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























1,672 Merged ELG010-0001 RULE-1991 ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD ELG010











1,673 Merged ELG010-0002 RULE-1991 ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG010 END-OF-TIME-PERIOD 1 If END-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD ELG010











1,674 Moved to R&C ELG010-0005
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG010 END-OF-TIME-PERIOD 2-M
2122


























1,675 Moved to R&C ELG010-0007
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG010 END-OF-TIME-PERIOD 2-M
2043


























1,676 Moved to R&C ELG011-0001
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG011 FILE-STATUS-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,677 Moved to R&C ELG011-0002
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























1,678 Moved to R&C ELG012-0005
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG012 SSN-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,679 No logic changes ELG013-0001 RULE-1997 ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG013 TOT-REC-CNT 1 If TOT-REC-CNT = 0 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT ELG013











1,680 Moved to R&C ELG013-0002
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record

























1,681 Retired: Other reasons ELG013-0003
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG013 TOT-REC-CNT 3 Absolute Value of ( (TOT-REC-CNT minus TOT-REC-CNT for prior submission) / TOT-REC-CNT for prior submission ) must be < 10% where SUBMITTING-STATE is the same and START-OF-TIME-PERIOD <= START-OF-TIME-PERIOD for prior submission + 32 days 3054 The change in the number of records for TOT-REC-CNT compared with the prior reporting period has exceeded +/- 10%

























1,682 Moved to R&C ELG014-0001
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























1,683 Moved to R&C ELG016-0003
ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,684 Moved to R&C ELG016-0004
ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG016 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,685 No logic changes ELG017-0002 RULE-2003 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG017 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG017











1,686 Logic updated: other ELG017-0003 RULE-2004 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG017 SUBMITTING-STATE ELG007









1,687 Retired: Other reasons ELG018-0002
ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG018 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,688 No logic changes ELG018-0005 RULE-2006 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Field RECORD-NUMBER should be unique across all records of type PRIMARY-DEMOGRAPHICS-ELIGIBILITY RECORD-NUMBER ELG018











1,689 Retired: MSIS ID checks ELG019-0001
ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG019 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,690 Retired: MSIS ID checks ELG019-0002
ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG019 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,691 Logic updated: string matching ELG020-0001 RULE-2009 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG020 ELIGIBLE-FIRST-NAME 1 ELIGIBLE-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - ELIGIBLE-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



'if fns.hasValue(@val.ELIGIBLE-FIRST-NAME), then fns.matches(@val.ELIGIBLE-FIRST-NAME, "^[^|*]*$")' ELIGIBLE-FIRST-NAME ELG020











1,692 Logic updated: string matching ELG021-0001 RULE-2010 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG021 ELIGIBLE-LAST-NAME 1 ELIGIBLE-LAST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid character - ELIGIBLE-LAST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



'if fns.hasValue(@val.ELIGIBLE-LAST-NAME), then fns.matches(@val.ELIGIBLE-LAST-NAME, "^[^|*]*$")' ELIGIBLE-LAST-NAME ELG021











1,693 Logic updated: string matching ELG022-0002 RULE-2011 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG022 ELIGIBLE-MIDDLE-INIT 1 ELIGIBLE-MIDDLE-INIT must not contain non-alphabetic characters 120 Field contains invalid characters - ELIGIBLE-MIDDLE-INIT 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



'if fns.hasValue(@val.ELIGIBLE-MIDDLE-INIT), then fns.matches(@val.ELIGIBLE-MIDDLE-INIT, "^[^|*]*$")' ELIGIBLE-MIDDLE-INIT ELG022











1,694 No logic changes ELG023-0001 RULE-2012 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG023 SEX 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



If the field is populated, the value must be contained in the set of valid values with id: SEX SEX ELG023











1,695 No logic changes ELG023-0002 RULE-2013 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG023 SEX 2 If PREGNANCY-IND = "1", then SEX must = "F" 2090 Relational edit between PREGNANCY-IND and SEX failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isEqual(@secondaryRecord.PREGNANCY-IND, "1"), then fns.isEqual(@primaryRecord.SEX, "F")' SEX ELG023 PREGNANCY-IND ELG049

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,696 Merged ELG024-0001 RULE-2014 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG024 DATE-OF-BIRTH 1 If DATE-OF-BIRTH is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH ELG024











1,697 Merged ELG024-0004 RULE-2014 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG024 DATE-OF-BIRTH 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH ELG024











1,698 No logic changes ELG024-0006 RULE-2016 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG024 DATE-OF-BIRTH 2 If CONCEPTION-TO-BIRTH <> "1" and ELIGIBILITY-GROUP <> "64", then DATE-OF-BIRTH must be <= END-OF-TIME-PERIOD 2248 Relational edit between DATE-OF-BIRTH and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 FILE-HEADER-RECORD-ELIGIBILITY ELG00001 'if !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64"), then fns.isLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @fileHeader.END-OF-TIME-PERIOD)' DATE-OF-BIRTH ELG024 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 END-OF-TIME-PERIOD ELG010 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,699 No logic changes ELG024-0008 RULE-2017 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG024 DATE-OF-BIRTH 2 If CONCEPTION-TO-BIRTH <> "1" and ELIGIBILITY-GROUP <> "64", then DATE-OF-BIRTH must be >= (START-OF-TIME-PERIOD minus 125 years) 2250 Relational edit between DATE-OF-BIRTH and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 FILE-HEADER-RECORD-ELIGIBILITY ELG00001 'if !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64"), then fns.isDifferenceInYearsLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @fileHeader.START-OF-TIME-PERIOD, 125)' DATE-OF-BIRTH ELG024 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 START-OF-TIME-PERIOD ELG009 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,700 Merged ELG025-0001 RULE-2018 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG025 DATE-OF-DEATH 1 If DATE-OF-DEATH is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD DATE-OF-DEATH ELG025











1,701 Merged ELG025-0004 RULE-2018 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG025 DATE-OF-DEATH 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD DATE-OF-DEATH ELG025











1,702 Logic updated: other ELG025-0006 RULE-2020 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG025 DATE-OF-DEATH 2 If DATE-OF-DEATH is not 8-filled, then DATE-OF-DEATH must be <= (DATE-OF-BIRTH plus 125 years) 2247 Relational edit between DATE-OF-BIRTH and DATE-OF-DEATH failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



'if fns.hasValue(@val.DATE-OF-DEATH) && fns.hasValue(@val.DATE-OF-BIRTH), then fns.isDifferenceInYearsLessThanOrEqual(@val.DATE-OF-BIRTH, @val.DATE-OF-DEATH, 125)' DATE-OF-DEATH,DATE-OF-BIRTH ELG025,ELG024











1,703 Logic updated: other ELG025-0009 RULE-2021 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG025 DATE-OF-DEATH 2 If DATE-OF-DEATH is not 8-filled, then DATE-OF-DEATH must be <= END-OF-TIME-PERIOD 2254 Relational edit between DATE-OF-DEATH and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.DATE-OF-DEATH) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.DATE-OF-DEATH, @fileHeader.END-OF-TIME-PERIOD)' DATE-OF-DEATH ELG025 END-OF-TIME-PERIOD ELG010









1,704 Logic updated: other ELG025-0010 RULE-2022 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG025 DATE-OF-DEATH 2 If DATE-OF-DEATH is not 8-filled and STATE-SPEC-ELIG-GROUP is 8-filled, then the DATE-OF-DEATH must be >= START-OF-TIME-PERIOD. 2258 Relational edit between DATE-OF-DEATH, START-OF-TIME-PERIOD, and STATE-SPEC-ELIG-GROUP failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 FILE-HEADER-RECORD-ELIGIBILITY ELG00001 'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && !fns.hasValue(@secondaryRecord.STATE-SPEC-ELIG-GROUP) && fns.hasValue(@fileHeader.START-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 STATE-SPEC-ELIG-GROUP ELG093 START-OF-TIME-PERIOD ELG009 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,705 No logic changes ELG025-0011 RULE-2023 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG025 DATE-OF-DEATH 2 If DATE-OF-DEATH is not 8-filled and MAINTENANCE-ASSISTANCE-STATUS = "1", "2", "3", "4", or "5", then DATE-OF-DEATH must be >= START-OF-TIME-PERIOD 2256 Relational edit between DATE-OF-DEATH, START-OF-TIME-PERIOD, and MAINTENANCE-ASSISTANCE-STATUS failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 FILE-HEADER-RECORD-ELIGIBILITY ELG00001 'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.isEqualToAny(@secondaryRecord.MAINTENANCE-ASSISTANCE-STATUS, "1", "2", "3", "4", "5"), then fns.isLessThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 MAINTENANCE-ASSISTANCE-STATUS ELG096 START-OF-TIME-PERIOD ELG009 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,706 Retired: Other reasons ELG025-0012
ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG025 DATE-OF-DEATH 2 If DATE-OF-DEATH is not 8-filled and MEDICAID-BASIS-OF-ELIGIBILITY = "01" through "08", "10" or "11", then DATE-OF-DEATH must be >= START-OF-TIME-PERIOD 2257 Relational edit between DATE-OF-DEATH, START-OF-TIME-PERIOD, and MEDICAID-BASIS-OF-ELIGIBILITY failed

























1,707 Merged ELG026-0001 RULE-2025 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG026 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE 1 If PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE ELG026











1,708 Merged ELG026-0002 RULE-2025 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG026 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE ELG026











1,709 Merged ELG026-0004 RULE-2027 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG026 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE 2 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE 2093 Relational edit between PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



'if fns.hasValue(@val.PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE) && fns.hasValue(@val.PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE), then fns.isLessThanOrEqual(@val.PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, @val.PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE)' PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE,PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE ELG026,ELG027











1,710 No logic changes ELG026-0005 RULE-2028 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG026 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE 2 If two or more PRIMARY-DEMOGRAPHICS-ELIGIBILITY record segments have the same SUBMITTING-STATE and MSIS-IDENTIFICATION-NUM
then for each pair of record segments,
(Segment 1 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE must <> Segment 2 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE)
AND
( (If Segment 1 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE < Segment 2 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE,
then
Segment 1 PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE must be < Segment 2 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE)
OR
(If Segment 2 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE < Segment 1 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE,
then
Segment 2 PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE must be < Segment 1 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE) )		 2168 Edit for overlapping coverage dates in record segments that have non-unique key fields in PRIMARY-DEMOGRAPHICS-ELIGIBILITY failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE. End date field: PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE,PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE ELG026,ELG027











1,711 Retired: Other reasons ELG026-0007
ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG026 PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE 2 If two or more PRIMARY-DEMOGRAPHICS-ELIGIBILITY record segments have the same SUBMITTING-STATE and MSIS-IDENTIFICATION-NUM and these record segments are sorted in ascending order by PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE must = Segment (N+1) PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE minus 1 day 2455 Edit for contiguous PRIMARY-DEMOGRAPHICS-ELIGIBILITY record segments failed (Exact match on all key fields except the file segment effective date)

























1,712 Merged ELG027-0001 RULE-2030 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG027 PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE 1 If PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE ELG027











1,713 Merged ELG027-0002 RULE-2030 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG027 PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be a valid date of the form CCYYMMDD PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE ELG027











1,714 Merged ELG027-0005 RULE-2027 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG027 PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE 2-M
2093
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



'if fns.hasValue(@val.PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE) && fns.hasValue(@val.PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE), then fns.isLessThanOrEqual(@val.PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, @val.PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE)' PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE,PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE ELG026,ELG027











1,715 Logic updated: string matching ELG028-0001 RULE-2033 ELIGIBLE PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ELG028 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG028











1,716 Moved to R&C ELG030-0003
ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG030 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,717 Moved to R&C ELG030-0004
ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG030 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,718 No logic changes ELG031-0002 RULE-2036 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG031 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG031











1,719 Logic updated: other ELG031-0003 RULE-2037 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG031 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG031 SUBMITTING-STATE ELG007









1,720 No logic changes ELG032-0003 RULE-2038 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG032 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Field RECORD-NUMBER should be unique across all records of type VARIABLE-DEMOGRAPHICS-ELIGIBILITY RECORD-NUMBER ELG032











1,721 Merged ELG033-0005 RULE-2039 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG033 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2226 Edit that VARIABLE-DEMOGRAPHICS-ELIGIBILITY child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

record VARIABLE-DEMOGRAPHICS-ELIGIBILITY has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,722 Logic updated: other ELG034-0003 RULE-2040 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG034 MARITAL-STATUS 2 If DATE-OF-BIRTH >= (VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE minus 12 years), then MARITAL-STATUS must = "13" or be 8-filled 2252 Relational edit between DATE-OF-BIRTH, VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, and MARITAL-STATUS failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isDifferenceInYearsLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @secondaryRecord.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, 12), then fns.isEqual(@secondaryRecord.MARITAL-STATUS, "13") || !fns.hasValue(@secondaryRecord.MARITAL-STATUS)' DATE-OF-BIRTH ELG024 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,MARITAL-STATUS ELG057,ELG034

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,723 No logic changes ELG035-0001 RULE-2041 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG035 MARITAL-STATUS-OTHER-EXPLANATION 2 If MARITAL-STATUS = "14", then MARITAL-STATUS-OTHER-EXPLANATION must not be 8-filled 2325 Relational edit between MARITAL-STATUS and MARITAL-STATUS-OTHER-EXPLANATION failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.isEqual(@val.MARITAL-STATUS, "14"), then fns.hasValue(@val.MARITAL-STATUS-OTHER-EXPLANATION)' MARITAL-STATUS,MARITAL-STATUS-OTHER-EXPLANATION ELG034,ELG035











1,724 Retired: Other reasons ELG036-0007
ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG036 SSN 2 If SSN-INDICATOR = "0", then SSN must <> MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 2417 Relational edit between SSN-INDICATOR, SSN, and MSIS-IDENTIFICATION-NUM failed

























1,725 No logic changes ELG037-0001 RULE-2043 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG037 SSN-VERIFICATION-FLAG 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: SSN-VERIFICATION-FLAG SSN-VERIFICATION-FLAG ELG037











1,726 No logic changes ELG038-0001 RULE-2044 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG038 INCOME-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: INCOME-CODE INCOME-CODE ELG038











1,727 No logic changes ELG039-0001 RULE-2045 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG039 VETERAN-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: VETERAN-IND VETERAN-IND ELG039











1,728 Logic updated: other ELG039-0002 RULE-2046 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG039 VETERAN-IND 2 If DATE-OF-BIRTH >= (VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE minus 17 years), then VETERAN-IND must = "0" or be 8-filled 2253 Relational edit between DATE-OF-BIRTH, VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, and VETERAN-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isDifferenceInYearsLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @secondaryRecord.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, 17), then fns.isEqual(@secondaryRecord.VETERAN-IND, "0") || !fns.hasValue(@secondaryRecord.VETERAN-IND)' DATE-OF-BIRTH ELG024 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,VETERAN-IND ELG057,ELG039

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,729 No logic changes ELG040-0001 RULE-2047 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG040 CITIZENSHIP-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: CITIZENSHIP-IND CITIZENSHIP-IND ELG040











1,730 No logic changes ELG040-0002 RULE-2048 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG040 CITIZENSHIP-IND 2 If IMMIGRATION-STATUS = "1", "2", or "3", then CITIZENSHIP-IND must = "0" 2050 Relational edit between IMMIGRATION-STATUS and CITIZENSHIP-IND failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.isEqualToAny(@val.IMMIGRATION-STATUS, "1", "2", "3"), then fns.isEqual(@val.CITIZENSHIP-IND, "0")' IMMIGRATION-STATUS,CITIZENSHIP-IND ELG042,ELG040











1,731 No logic changes ELG041-0001 RULE-2049 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG041 CITIZENSHIP-VERIFICATION-FLAG 1 Value is not in the valid values list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: CITIZENSHIP-VERIFICATION-FLAG CITIZENSHIP-VERIFICATION-FLAG ELG041











1,732 No logic changes ELG042-0001 RULE-2050 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG042 IMMIGRATION-STATUS 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: IMMIGRATION-STATUS IMMIGRATION-STATUS ELG042











1,733 No logic changes ELG042-0002 RULE-2051 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG042 IMMIGRATION-STATUS 2 If CITIZENSHIP-IND = "1", then IMMIGRATION-STATUS must = "8" 2016 Relational edit between CITIZENSHIP-IND and IMMIGRATION-STATUS failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.isEqual(@val.CITIZENSHIP-IND, "1"), then fns.isEqual(@val.IMMIGRATION-STATUS, "8")' CITIZENSHIP-IND,IMMIGRATION-STATUS ELG040,ELG042











1,734 No logic changes ELG043-0001 RULE-2052 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG043 IMMIGRATION-VERIFICATION-FLAG 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: IMMIGRATION-VERIFICATION-FLAG IMMIGRATION-VERIFICATION-FLAG ELG043











1,735 Merged ELG044-0001 RULE-2053 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG044 IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE 1 If IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be a valid date of the form CCYYMMDD IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE ELG044











1,736 No logic changes ELG044-0003 RULE-2054 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG044 IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE 2 If IMMIGRATION-STATUS = "8", then IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE must be 8-filled 2301 Relational edit between IMMIGRATION-STATUS and IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.isEqual(@val.IMMIGRATION-STATUS, "8"), then !fns.hasValue(@val.IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE)' IMMIGRATION-STATUS,IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE ELG042,ELG044











1,737 Merged ELG044-0005 RULE-2053 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG044 IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be a valid date of the form CCYYMMDD IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE ELG044











1,738 No logic changes ELG044-0006 RULE-2056 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG044 IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE 2 If IMMIGRATION-STATUS = "1", "2", or "3", then IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE must not be 8-filled 2301 Relational edit between IMMIGRATION-STATUS and IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.isEqualToAny(@val.IMMIGRATION-STATUS, "1", "2", "3"), then fns.hasValue(@val.IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE)' IMMIGRATION-STATUS,IMMIGRATION-STATUS-FIVE-YEAR-BAR-END-DATE ELG042,ELG044











1,739 No logic changes ELG045-0001 RULE-2057 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG045 PRIMARY-LANGUAGE-ENGL-PROF-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: PRIMARY-LANGUAGE-ENGL-PROF-CODE PRIMARY-LANGUAGE-ENGL-PROF-CODE ELG045











1,740 Logic updated: other ELG045-0002 RULE-2058 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG045 PRIMARY-LANGUAGE-ENGL-PROF-CODE 2 If DATE-OF-BIRTH > (VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE minus 5 years)
and
if CONCEPTION-TO-BIRTH <> "1" and ELIGIBILITY-GROUP <> "64",
then PRIMARY-LANGUAGE-ENGL-PROF-CODE must <> "0", "1", "2", or "3"		 2132 Relational edit between DATE-OF-BIRTH, VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-LANGUAGE-ENGL-PROF-CODE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 'if fns.hasValue(@primaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@primaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@primaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@primaryRecord.ELIGIBILITY-GROUP, "64") && fns.hasValue(@secondaryRecord.DATE-OF-BIRTH) && fns.hasValue(@tertiaryRecord.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE) && fns.isDifferenceInYearsLessThan(@secondaryRecord.DATE-OF-BIRTH, @tertiaryRecord.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, 5), then !fns.isEqualToAny(@tertiaryRecord.PRIMARY-LANGUAGE-ENGL-PROF-CODE, "0", "1", "2", "3")' CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-BIRTH ELG024 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,PRIMARY-LANGUAGE-ENGL-PROF-CODE ELG057,ELG045 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG082,ELG080 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG082,ELG080 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG033,ELG031
1,741 No logic changes ELG046-0001 RULE-2059 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG046 PRIMARY-LANGUAGE-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: PRIMARY-LANGUAGE-CODE PRIMARY-LANGUAGE-CODE ELG046











1,742 Logic updated: other ELG046-0003 RULE-2060 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG046 PRIMARY-LANGUAGE-CODE 2 If DATE-OF-BIRTH > (VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE minus 5 years)
and
if CONCEPTION-TO-BIRTH <> "1" and ELIGIBILITY-GROUP <> "64",
then PRIMARY-LANGUAGE-CODE must <> valid code from Appendix G: ISO 639 Language Codes Reference		 2131 Relational edit between DATE-OF-BIRTH, VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-LANGUAGE-CODE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule ELIGIBILITY-DETERMINANTS ELG00005 PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 'if fns.hasValue(@primaryRecord.CONCEPTION-TO-BIRTH-IND) && !fns.isEqual(@primaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && fns.hasValue(@primaryRecord.ELIGIBILITY-GROUP) && !fns.isEqual(@primaryRecord.ELIGIBILITY-GROUP, "64") && fns.hasValue(@secondaryRecord.DATE-OF-BIRTH) && fns.hasValue(@tertiaryRecord.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE) && fns.isDifferenceInYearsLessThan(@secondaryRecord.DATE-OF-BIRTH, @tertiaryRecord.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, 5), then !fns.hasValue(@tertiaryRecord.PRIMARY-LANGUAGE-CODE)' CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP ELG094,ELG087 DATE-OF-BIRTH ELG024 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,PRIMARY-LANGUAGE-CODE ELG057,ELG046 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG082,ELG080 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG082,ELG080 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG033,ELG031
1,743 No logic changes ELG047-0001 RULE-2061 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG047 HOUSEHOLD-SIZE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: HOUSEHOLD-SIZE HOUSEHOLD-SIZE ELG047











1,744 No logic changes ELG049-0001 RULE-2062 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG049 PREGNANCY-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: PREGNANCY-IND PREGNANCY-IND ELG049











1,745 Logic updated: string matching ELG050-0001 RULE-2063 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG050 MEDICARE-HIC-NUM 1 Field contains invalid characters -MEDICARE-HIC-NUM 120 Field contains invalid characters -MEDICARE-HIC-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.hasValue(@val.MEDICARE-HIC-NUM), then fns.matches(@val.MEDICARE-HIC-NUM, "^[^|*]*$")' MEDICARE-HIC-NUM ELG050











1,746 Merged ELG050-0002 RULE-2064 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG050 MEDICARE-HIC-NUM 2 If DUAL-ELIGIBLE-CODE = "00", then MEDICARE-HIC-NUM must be 8-filled 2029 Relational edit between DUAL-ELIGIBLE-CODE and MEDICARE-HIC-NUM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isEqual(@primaryRecord.DUAL-ELIGIBLE-CODE, "00"), then !fns.hasValue(@secondaryRecord.MEDICARE-HIC-NUM)' DUAL-ELIGIBLE-CODE ELG085 MEDICARE-HIC-NUM ELG050

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,747 Logic updated: string matching ELG051-0001 RULE-2065 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG051 MEDICARE-BENEFICIARY-IDENTIFIER 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters -MEDICARE-BENEFICIARY-IDENTIFIER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.hasValue(@val.MEDICARE-BENEFICIARY-IDENTIFIER), then fns.matches(@val.MEDICARE-BENEFICIARY-IDENTIFIER, "^[^|*]*$")' MEDICARE-BENEFICIARY-IDENTIFIER ELG051











1,748 No logic changes ELG051-0002 RULE-2066 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG051 MEDICARE-BENEFICIARY-IDENTIFIER 2 If END-OF-TIME-PERIOD >= "20151101" and DUAL-ELIGIBLE-CODE = "00", then MEDICARE-BENEFICIARY-IDENTIFIER must be 8-filled 2028 Relational edit between DUAL-ELIGIBLE-CODE, MEDICARE-BENEFICIARY-IDENTIFIER, and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule ELIGIBILITY-DETERMINANTS ELG00005 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003 FILE-HEADER-RECORD-ELIGIBILITY ELG00001 'if fns.isEqual(@primaryRecord.DUAL-ELIGIBLE-CODE, "00") && fns.isGreaterThanOrEqual(@fileHeader.END-OF-TIME-PERIOD, "2015-11-01"), then !fns.hasValue(@secondaryRecord.MEDICARE-BENEFICIARY-IDENTIFIER)' DUAL-ELIGIBLE-CODE ELG085 MEDICARE-BENEFICIARY-IDENTIFIER ELG051 END-OF-TIME-PERIOD ELG010 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,749 No logic changes ELG054-0001 RULE-2067 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG054 CHIP-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: CHIP-CODE CHIP-CODE ELG054











1,750 No logic changes ELG054-0004 RULE-2068 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG054 CHIP-CODE 2 If CONCEPTION-TO-BIRTH-IND = "1", then CHIP-CODE must = "3" or "4". 2240 Relational edit between CHIP-CODE and CONCEPTION-TO-BIRTH-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isEqual(@primaryRecord.CONCEPTION-TO-BIRTH-IND, "1"), then fns.isEqualToAny(@secondaryRecord.CHIP-CODE, "3", "4")' CONCEPTION-TO-BIRTH-IND ELG094 CHIP-CODE ELG054

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,751 Merged ELG057-0001 RULE-2069 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG057 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE 1 If VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be a valid date of the form CCYYMMDD VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE ELG057











1,752 Merged ELG057-0002 RULE-2069 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG057 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be a valid date of the form CCYYMMDD VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE ELG057











1,753 No logic changes ELG057-0004 RULE-2071 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG057 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE 2 If two or more VARIABLE-DEMOGRAPHICS-ELIGIBILITY record segments have the same SUBMITTING-STATE and MSIS-IDENTIFICATION-NUM
then for each pair of record segments,
(Segment 1 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE must <> Segment 2 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE)
AND
( (If Segment 1 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE < Segment 2 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,
then
Segment 1 VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE must be < Segment 2 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE)
OR
(If Segment 2 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE < Segment 1 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,
then
Segment 2 VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE must be < Segment 1 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE) )		 2185 Edit for overlapping coverage dates in record segments that have non-unique key fields in VARIABLE-DEMOGRAPHICS-ELIGIBILITY failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Records with the same primary keys must have non-overlapping date ranges. Effective date field: VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE. End date field: VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE ELG057,ELG058











1,754 Merged ELG057-0005 RULE-2039 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG057 VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE 2 ( VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2540 Relational edit between VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

record VARIABLE-DEMOGRAPHICS-ELIGIBILITY has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,755 Merged ELG058-0001 RULE-2073 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG058 VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE 1 If VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be a valid date of the form CCYYMMDD VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE ELG058











1,756 Merged ELG058-0002 RULE-2073 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG058 VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be a valid date of the form CCYYMMDD VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE ELG058











1,757 Logic updated: other ELG058-0006 RULE-2075 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG058 VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE 2-M
2129
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.hasValue(@val.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE) && fns.hasValue(@val.VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE), then fns.isLessThanOrEqual(@val.VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE, @val.VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE)' VARIABLE-DEMOGRAPHIC-ELEMENT-EFF-DATE,VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE ELG057,ELG058











1,758 Merged ELG058-0007 RULE-2039 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG058 VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE 2 ( VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2541 Relational edit between VARIABLE-DEMOGRAPHIC-ELEMENT-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

record VARIABLE-DEMOGRAPHICS-ELIGIBILITY has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,759 Logic updated: string matching ELG059-0001 RULE-2077 ELIGIBLE VARIABLE-DEMOGRAPHICS-ELIGIBILITY-ELG00003 ELG059 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG059











1,760 Moved to R&C ELG061-0003
ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG061 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,761 Moved to R&C ELG061-0004
ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG061 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,762 No logic changes ELG062-0002 RULE-2080 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG062 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBLE-CONTACT-INFORMATION ELG00004



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG062











1,763 Logic updated: other ELG062-0003 RULE-2081 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG062 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBLE-CONTACT-INFORMATION ELG00004 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG062 SUBMITTING-STATE ELG007









1,764 Retired: Other reasons ELG063-0002
ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG063 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,765 No logic changes ELG063-0003 RULE-2083 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG063 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



Field RECORD-NUMBER should be unique across all records of type ELIGIBLE-CONTACT-INFORMATION RECORD-NUMBER ELG063











1,766 Retired: MSIS ID checks ELG064-0001
ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG064 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,767 Retired: MSIS ID checks ELG064-0002
ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG064 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,768 Merged ELG064-0005 RULE-2086 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG064 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [ELIGIBILE-CONTACT-INFORMATION-ELG00004] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [ELIGIBILE-CONTACT-INFORMATION-ELG00004] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2195 Edit that ELIGIBLE-CONTACT-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBLE-CONTACT-INFORMATION ELG00004

record ELIGIBLE-CONTACT-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG062,ELG064



1,769 No logic changes ELG065-0001 RULE-2087 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG065 ADDR-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBLE-CONTACT-INFORMATION ELG00004



If the field is populated, the value must be contained in the set of valid values with id: ELIGIBLE-ADDR-TYPE ELIGIBLE-ADDR-TYPE ELG065











1,770 Retired: required value checks ELG066-0001
ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG066 ELIGIBLE-ADDR-LN1 1 Required data element has not been reported. 113 Required data element has not been reported.

























1,771 Logic updated: string matching ELG066-0003 RULE-2089 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG066 ELIGIBLE-ADDR-LN1 1 Field contains invalid characters - ELIGIBLE-ADDR-LN21 120 Field contains invalid characters - ELIGIBLE-ADDR-LN1 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-ADDR-LN1), then fns.matches(@val.ELIGIBLE-ADDR-LN1, "^[^|*]*$")' ELIGIBLE-ADDR-LN1 ELG066











1,772 Logic updated: string matching ELG067-0001 RULE-2090 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG067 ELIGIBLE-ADDR-LN2 1 Field contains invalid characters - ELIGIBLE-ADDR-LN2 120 Field contains invalid characters - ELIGIBLE-ADDR-LN2 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-ADDR-LN2), then fns.matches(@val.ELIGIBLE-ADDR-LN2, "^[^|*]*$")' ELIGIBLE-ADDR-LN2 ELG067











1,773 Merged ELG067-0002 RULE-7136 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG067 ELIGIBLE-ADDR-LN2 2 If ELIGIBLE-ADDR-LN2 is not 8-filled,
then ELIGIBLE-ADDR-LN2 must <> ELIGIBLE-ADDR-LN1		 2283 Relational edit between ELIGIBLE-ADDR-LN2 and ELIGIBLE-ADDR-LN1
failed (duplicate value entered)		 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



The values of the following fields should be unique (non-repeating) within each record: ELIGIBLE-ADDR-LN1,ELIGIBLE-ADDR-LN2,ELIGIBLE-ADDR-LN3 ELIGIBLE-ADDR-LN1,ELIGIBLE-ADDR-LN2,ELIGIBLE-ADDR-LN3 ELG066,ELG067,ELG068











1,774 Logic updated: string matching ELG068-0001 RULE-2092 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG068 ELIGIBLE-ADDR-LN3 1 Field contains invalid characters - ELIGIBLE-ADDR-LN3 120 Field contains invalid characters - ELIGIBLE-ADDR-LN3 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-ADDR-LN3), then fns.matches(@val.ELIGIBLE-ADDR-LN3, "^[^|*]*$")' ELIGIBLE-ADDR-LN3 ELG068











1,775 Merged ELG068-0003 RULE-7136 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG068 ELIGIBLE-ADDR-LN3 2 (If ELIGIBLE-ADDR-LN3 is not 8-filled,
then ELIGIBLE-ADDR-LN3 must <> ELIGIBLE-ADDR-LN1)
AND
(If ELIGIBLE-ADDR-LN2 is not 8-filled,
then ELIGIBLE-ADDR-LN3 must <> ELIGIBLE-ADDR-LN2)		 2285 Relational edit between ELIGIBLE-ADDR-LN3 and ELIGIBLE-ADDR-LN2 or ELIGIBLE-ADDR-LN1 failed (duplicate value entered) 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



The values of the following fields should be unique (non-repeating) within each record: ELIGIBLE-ADDR-LN1,ELIGIBLE-ADDR-LN2,ELIGIBLE-ADDR-LN3 ELIGIBLE-ADDR-LN1,ELIGIBLE-ADDR-LN2,ELIGIBLE-ADDR-LN3 ELG066,ELG067,ELG068











1,776 No logic changes ELG068-0004 RULE-2094 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG068 ELIGIBLE-ADDR-LN3 2 If ELIGIBLE-ADDR-LN2 is 8-filled, then ELIGIBLE-ADDR-LN3 must be 8-filled 2284 Relational edit between ELIGIBLE-ADDR-LN2 and ELIGIBLE-ADDR-LN3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if !fns.hasValue(@val.ELIGIBLE-ADDR-LN2), then !fns.hasValue(@val.ELIGIBLE-ADDR-LN3)' ELIGIBLE-ADDR-LN2,ELIGIBLE-ADDR-LN3 ELG067,ELG068











1,777 Logic updated: string matching ELG069-0002 RULE-2095 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG069 ELIGIBLE-CITY 1 Field contains invalid characters - ELIGIBLE-CITY 120 Field contains invalid characters - ELIGIBLE-CITY 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-CITY), then fns.matches(@val.ELIGIBLE-CITY, "^[^|*]*$")' ELIGIBLE-CITY ELG069











1,778 No logic changes ELG070-0003 RULE-2096 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG070 ELIGIBLE-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBLE-CONTACT-INFORMATION ELG00004



If the field is populated, the value must be contained in the set of valid values with id: STATE ELIGIBLE-STATE ELG070











1,779 No logic changes ELG071-0003 RULE-2097 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG071 ELIGIBLE-ZIP-CODE 1 If ELIGIBLE-ZIP-CODE not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-ZIP-CODE), then fns.matches(@val.ELIGIBLE-ZIP-CODE, "^[0-9]{5}|[0-9]{9}$")' ELIGIBLE-ZIP-CODE ELG071











1,780 Merged ELG072-0001 RULE-2098 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG072 ELIGIBLE-COUNTY-CODE 2 Field contains invalid characters - ELIGIBLE-COUNTY-CODE 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBLE-CONTACT-INFORMATION ELG00004



If the field is populated, the value must be contained in the set of valid values with id: COUNTY ELIGIBLE-COUNTY-CODE ELG072











1,781 Merged ELG072-0003 RULE-2098 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG072 ELIGIBLE-COUNTY-CODE 1 If ELIGIBLE-COUNTY-CODE not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBLE-CONTACT-INFORMATION ELG00004



If the field is populated, the value must be contained in the set of valid values with id: COUNTY ELIGIBLE-COUNTY-CODE ELG072











1,782 No logic changes ELG073-0002 RULE-7141 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG073 ELIGIBLE-PHONE-NUM 1 ELIGIBLE-PHONE-NUM must not contain parentheses, dashes, periods, commas, spaces 120 Field contains invalid characters - ELIGIBLE-PHONE-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-PHONE-NUM), then fns.isNumericString(@val.ELIGIBLE-PHONE-NUM)' ELIGIBLE-PHONE-NUM ELG073











1,783 Logic updated: string matching ELG074-0001 RULE-2101 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG074 TYPE-OF-LIVING-ARRANGEMENT 1 Field contains invalid characters - TYPE-OF-LIVING-ARRANGEMENT 120 Field contains invalid characters - TYPE-OF-LIVING-ARRANGEMENT 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.TYPE-OF-LIVING-ARRANGEMENT), then fns.matches(@val.TYPE-OF-LIVING-ARRANGEMENT, "^[^|*]*$")' TYPE-OF-LIVING-ARRANGEMENT ELG074











1,784 Merged ELG075-0001 RULE-2102 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG075 ELIGIBLE-ADDR-EFF-DATE 1 If ELIGIBLE-ADDR-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be a valid date of the form CCYYMMDD ELIGIBLE-ADDR-EFF-DATE ELG075











1,785 Merged ELG075-0003 RULE-2102 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG075 ELIGIBLE-ADDR-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be a valid date of the form CCYYMMDD ELIGIBLE-ADDR-EFF-DATE ELG075











1,786 Merged ELG075-0004 RULE-2104 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG075 ELIGIBLE-ADDR-EFF-DATE 2 ELIGIBLE-ADDR-EFF-DATE must be <= ELIGIBLE-ADDR-END-DATE 2031 Relational edit between ELIGIBLE-ADDR-EFF-DATE and ELIGIBLE-ADDR-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-ADDR-EFF-DATE) && fns.hasValue(@val.ELIGIBLE-ADDR-END-DATE), then fns.isLessThanOrEqual(@val.ELIGIBLE-ADDR-EFF-DATE, @val.ELIGIBLE-ADDR-END-DATE)' ELIGIBLE-ADDR-EFF-DATE,ELIGIBLE-ADDR-END-DATE ELG075,ELG076











1,787 No logic changes ELG075-0005 RULE-2105 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG075 ELIGIBLE-ADDR-EFF-DATE 2 If two or more ELIGIBLE-CONTACT-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and ADDR-TYPE
then for each pair of record segments,
(Segment 1 ELIGIBLE-ADDR-EFF-DATE must <> Segment 2 ELIGIBLE-ADDR-EFF-DATE)
AND
( (If Segment 1 ELIGIBLE-ADDR-EFF-DATE < Segment 2 ELIGIBLE-ADDR-EFF-DATE,
then
Segment 1 ELIGIBLE-ADDR-END-DATE must be < Segment 2 ELIGIBLE-ADDR-EFF-DATE)
OR
(If Segment 2 ELIGIBLE-ADDR-EFF-DATE < Segment 1 ELIGIBLE-ADDR-EFF-DATE,
then
Segment 2 ELIGIBLE-ADDR-END-DATE must be < Segment 1 ELIGIBLE-ADDR-EFF-DATE) )		 2151 Edit for overlapping coverage dates in record segments that have non-unique key fields in ELIGIBLE-CONTACT-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) ELIGIBLE-CONTACT-INFORMATION ELG00004



Records with the same primary keys must have non-overlapping date ranges. Effective date field: ELIGIBLE-ADDR-EFF-DATE. End date field: ELIGIBLE-ADDR-END-DATE ELIGIBLE-ADDR-EFF-DATE,ELIGIBLE-ADDR-END-DATE ELG075,ELG076











1,788 Merged ELG075-0006 RULE-2086 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG075 ELIGIBLE-ADDR-EFF-DATE 2 ( ELIGIBLE-ADDR-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ELIGIBLE-ADDR-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2474 Relational edit between ELIGIBLE-ADDR-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBLE-CONTACT-INFORMATION ELG00004

record ELIGIBLE-CONTACT-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG062,ELG064



1,789 Merged ELG076-0001 RULE-2107 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG076 ELIGIBLE-ADDR-END-DATE 1 If ELIGIBLE-ADDR-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be a valid date of the form CCYYMMDD ELIGIBLE-ADDR-END-DATE ELG076











1,790 Merged ELG076-0003 RULE-2107 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG076 ELIGIBLE-ADDR-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be a valid date of the form CCYYMMDD ELIGIBLE-ADDR-END-DATE ELG076











1,791 Merged ELG076-0006 RULE-2086 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG076 ELIGIBLE-ADDR-END-DATE 2 ( ELIGIBLE-ADDR-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ELIGIBLE-ADDR-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILE-CONTACT-INFORMATION-ELG00004] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2475 Relational edit between ELIGIBLE-ADDR-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBLE-CONTACT-INFORMATION ELG00004

record ELIGIBLE-CONTACT-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG062,ELG064



1,792 Merged ELG076-0007 RULE-2104 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG076 ELIGIBLE-ADDR-END-DATE 2-M
2031
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.ELIGIBLE-ADDR-EFF-DATE) && fns.hasValue(@val.ELIGIBLE-ADDR-END-DATE), then fns.isLessThanOrEqual(@val.ELIGIBLE-ADDR-EFF-DATE, @val.ELIGIBLE-ADDR-END-DATE)' ELIGIBLE-ADDR-EFF-DATE,ELIGIBLE-ADDR-END-DATE ELG075,ELG076











1,793 Logic updated: string matching ELG077-0001 RULE-2111 ELIGIBLE ELIGIBILE-CONTACT-INFORMATION-ELG00004 ELG077 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBLE-CONTACT-INFORMATION ELG00004



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG077











1,794 Moved to R&C ELG079-0003
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG079 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,795 Moved to R&C ELG079-0004
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG079 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,796 No logic changes ELG080-0002 RULE-2114 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG080 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG080











1,797 Logic updated: other ELG080-0003 RULE-2115 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG080 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG080 SUBMITTING-STATE ELG007









1,798 Retired: Other reasons ELG081-0002
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG081 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,799 No logic changes ELG081-0003 RULE-2117 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG081 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) ELIGIBILITY-DETERMINANTS ELG00005



Field RECORD-NUMBER should be unique across all records of type ELIGIBILITY-DETERMINANTS RECORD-NUMBER ELG081











1,800 Retired: MSIS ID checks ELG082-0001
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG082 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,801 Retired: MSIS ID checks ELG082-0002
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG082 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,802 Merged ELG082-0005 RULE-2120 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG082 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2194 Edit that ELIGIBILITY-DETERMINANTS child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005

record ELIGIBILITY-DETERMINANTS has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,803 Retired: Other reasons ELG083-0001
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG083 MSIS-CASE-NUM 1 Value is not in required format 101 Value is not in required format

























1,804 No logic changes ELG084-0001 RULE-2122 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG084 MEDICAID-BASIS-OF-ELIGIBILITY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: MEDICAID-BASIS-OF-ELIGIBILITY MEDICAID-BASIS-OF-ELIGIBILITY ELG084











1,805 No logic changes ELG084-0003 RULE-2123 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG084 MEDICAID-BASIS-OF-ELIGIBILITY 2 If CHIP-CODE = 3, then MEDICAID-BASIS-OF-ELIGIBILITY must = 00 2014 Relational edit between CHIP-CODE and MEDICAID-BASIS-OF-ELIGIBILITY failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isEqual(@secondaryRecord.CHIP-CODE, "3"), then fns.isEqual(@primaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "00")' MEDICAID-BASIS-OF-ELIGIBILITY ELG084 CHIP-CODE ELG054

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,806 No logic changes ELG084-0007 RULE-2124 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG084 MEDICAID-BASIS-OF-ELIGIBILITY 2 If MEDICAID-BASIS-OF-ELIGIBILITY = "01", then DATE-OF-BIRTH must be >= 64 years from START-OF-TIME-PERIOD 2065 Relational edit between MEDICAID-BASIS-OF-ELIGIBILITY, DATE-OF-BIRTH, and START-OF-TIME-PERIOD in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 FILE-HEADER-RECORD-ELIGIBILITY ELG00001 'if fns.isEqual(@secondaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "01"), then fns.isDifferenceInYearsGreaterThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @fileHeader.START-OF-TIME-PERIOD, 64)' DATE-OF-BIRTH ELG024 MEDICAID-BASIS-OF-ELIGIBILITY ELG084 START-OF-TIME-PERIOD ELG009 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,807 Logic updated: other ELG084-0008 RULE-2125 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG084 MEDICAID-BASIS-OF-ELIGIBILITY 2 If CONCEPTION-TO-BIRTH <> "1" and ELIGIBILITY-GROUP <> "64" and MEDICAID-BASIS-OF-ELIGIBILITY = "04" or "06", then DATE-OF-BIRTH must be >= (START-OF-TIME-PERIOD minus 21 years) 2326 Relational edit between MEDICAID-BASIS-OF-ELIGIBILITY, DATE-OF-BIRTH, and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Three Record Type Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005 FILE-HEADER-RECORD-ELIGIBILITY ELG00001 'if !fns.isEqual(@secondaryRecord.CONCEPTION-TO-BIRTH-IND, "1") && !fns.isEqual(@secondaryRecord.ELIGIBILITY-GROUP, "64") && fns.isEqualToAny(@secondaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "04") && fns.hasValue(@fileHeader.START-OF-TIME-PERIOD) && fns.hasValue(@primaryRecord.DATE-OF-BIRTH), then fns.isDifferenceInYearsLessThanOrEqual(@primaryRecord.DATE-OF-BIRTH, @fileHeader.START-OF-TIME-PERIOD, 21)' DATE-OF-BIRTH ELG024 CONCEPTION-TO-BIRTH-IND,ELIGIBILITY-GROUP,MEDICAID-BASIS-OF-ELIGIBILITY ELG094,ELG087,ELG084 START-OF-TIME-PERIOD ELG009 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,808 No logic changes ELG085-0001 RULE-2126 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG085 DUAL-ELIGIBLE-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: DUAL-ELIGIBLE-CODE DUAL-ELIGIBLE-CODE ELG085











1,809 Merged ELG085-0004 RULE-2064 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG085 DUAL-ELIGIBLE-CODE 2 If DUAL-ELIGIBLE-CODE = "00", then MEDICARE-HIC-NUM must be 8-filled 2029 Relational edit between DUAL-ELIGIBLE-CODE and MEDICARE-HIC-NUM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isEqual(@primaryRecord.DUAL-ELIGIBLE-CODE, "00"), then !fns.hasValue(@secondaryRecord.MEDICARE-HIC-NUM)' DUAL-ELIGIBLE-CODE ELG085 MEDICARE-HIC-NUM ELG050

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,810 Retired: Other reasons ELG085-0005
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG085 DUAL-ELIGIBLE-CODE 2 If DUAL-ELIGIBLE-CODE = "00", then MEDICARE-BENEFICIARY-IDENTIFIER must be 8-filled 2028 Relational edit between DUAL-ELIGIBLE-CODE and MEDICARE-BENEFICIARY-IDENTIFIER failed

























1,811 No logic changes ELG085-0006 RULE-2129 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG085 DUAL-ELIGIBLE-CODE 2 If DUAL-ELIGIBLE-CODE = "01" through "09", then MAINTENANCE-ASSISTANCE-STATUS must <> "00" 2027 Relational edit between DUAL-ELIGIBLE-CODE and MAINTENANCE-ASSISTANCE-STATUS failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqualToAny(@val.DUAL-ELIGIBLE-CODE, "01", "02", "03", "04", "05", "06", "07", "08", "09"), then !fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "0")' DUAL-ELIGIBLE-CODE,MAINTENANCE-ASSISTANCE-STATUS ELG085,ELG096











1,812 No logic changes ELG085-0007 RULE-2130 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG085 DUAL-ELIGIBLE-CODE 2 If DUAL-ELIGIBLE-CODE = "01" through "09", then MEDICAID-BASIS-OF-ELIGIBILITY must <> "00" 2448 Relational edit between DUAL-ELIGIBLE-CODE and MEDICAID-BASIS-OF-ELIGIBILITY failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqualToAny(@val.DUAL-ELIGIBLE-CODE, "01", "02", "03", "04", "05", "06", "07", "08", "09"), then !fns.isEqual(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "00")' DUAL-ELIGIBLE-CODE,MEDICAID-BASIS-OF-ELIGIBILITY ELG085,ELG084











1,813 No logic changes ELG085-0008 RULE-2131 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG085 DUAL-ELIGIBLE-CODE 2 If RESTRICTED-BENEFITS-CODE = "3", then DUAL-ELIGIBLE-CODE must = "01", "03", "05", or "06" 2280 Relational edit between DUAL-ELIGIBLE-CODE and RESTRICTED-BENEFITS-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqual(@val.RESTRICTED-BENEFITS-CODE, "3"), then fns.isEqualToAny(@val.DUAL-ELIGIBLE-CODE, "01", "03", "05", "06")' RESTRICTED-BENEFITS-CODE,DUAL-ELIGIBLE-CODE ELG097,ELG085











1,814 No logic changes ELG086-0001 RULE-2132 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG086 PRIMARY-ELIGIBILITY-GROUP-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: PRIMARY-ELIGIBILITY-GROUP-IND PRIMARY-ELIGIBILITY-GROUP-IND ELG086











1,815 Merged ELG086-0002 RULE-2133 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG086 PRIMARY-ELIGIBILITY-GROUP-IND 2 If there is only one ELIGIBILITY-DETERMINANTS-ELG00005 record segment identified via segment key data elements SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and MSIS-CASE-NUM,
then PRIMARY-ELIGIBILITY-GROUP-IND must = "1"		 2444 There is only one ELIGIBILITY-DETERMINANTS record segment for an individual but it is not designated as primary 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) ELIGIBILITY-DETERMINANTS ELG00005



'fns.isOnlyOneMarkedPrimary(@vals.PRIMARY-ELIGIBILITY-GROUP-IND, "1", "0")' PRIMARY-ELIGIBILITY-GROUP-IND ELG086



SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,MSIS-CASE-NUM ELG080,ELG082,ELG083





1,816 Merged ELG086-0003 RULE-2133 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG086 PRIMARY-ELIGIBILITY-GROUP-IND 2 If two or more ELIGIBILITY-DETERMINANTS-ELG00005 record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and MSIS-CASE-NUM,
then only one ELIGIBILITY-DETERMINANTS-ELG00005 record segment's PRIMARY-ELIGIBILITY-GROUP-IND must = "1" AND all other ELIGIBILITY-DETERMINANTS-ELG00005 record segments must = "0"		 2228 More than one ELIGIBILITY-DETERMINANTS record with PRIMARY-ELIGIBILITY-GROUP-IND designated as primary (Exact match on: SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, MSIS-CASE-NUM and PRIMARY-ELIGIBILITY-GROUP-IND) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) ELIGIBILITY-DETERMINANTS ELG00005



'fns.isOnlyOneMarkedPrimary(@vals.PRIMARY-ELIGIBILITY-GROUP-IND, "1", "0")' PRIMARY-ELIGIBILITY-GROUP-IND ELG086



SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,MSIS-CASE-NUM ELG080,ELG082,ELG083





1,817 Retired: Other reasons ELG086-0003
ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG086 PRIMARY-ELIGIBILITY-GROUP-IND 2 If two or more ELIGIBILITY-DETERMINANTS-ELG00005 record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and MSIS-CASE-NUM,
then only one ELIGIBILITY-DETERMINANTS-ELG00005 record segment's PRIMARY-ELIGIBILITY-GROUP-IND must = "1" AND all other ELIGIBILITY-DETERMINANTS-ELG00005 record segments must = "0"		 2228 More than one ELIGIBILITY-DETERMINANTS record with PRIMARY-ELIGIBILITY-GROUP-IND designated as primary (Exact match on: SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, MSIS-CASE-NUM and PRIMARY-ELIGIBILITY-GROUP-IND)

























1,818 No logic changes ELG087-0001 RULE-2135 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG087 ELIGIBILITY-GROUP 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: ELIGIBILITY-GROUP ELIGIBILITY-GROUP ELG087











1,819 No logic changes ELG088-0001 RULE-2136 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG088 LEVEL-OF-CARE-STATUS 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: LEVEL-OF-CARE-STATUS LEVEL-OF-CARE-STATUS ELG088











1,820 No logic changes ELG089-0001 RULE-2137 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG089 SSDI-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: SSDI-IND SSDI-IND ELG089











1,821 No logic changes ELG090-0001 RULE-2138 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG090 SSI-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: SSI-IND SSI-IND ELG090











1,822 No logic changes ELG090-0002 RULE-2139 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG090 SSI-IND 2 If SSI-IND = "1", then SSI-STATUS must not be (8-filled or 9-filled) 2118 Relational edit between SSI-IND and SSI-STATUS failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqual(@val.SSI-IND, "1"), then fns.hasValue(@val.SSI-STATUS)' SSI-IND,SSI-STATUS ELG090,ELG092











1,823 No logic changes ELG091-0001 RULE-2140 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG091 SSI-STATE-SUPPLEMENT-STATUS-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: SSI-STATE-SUPPLEMENT-STATUS-CODE SSI-STATE-SUPPLEMENT-STATUS-CODE ELG091











1,824 No logic changes ELG091-0002 RULE-2141 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG091 SSI-STATE-SUPPLEMENT-STATUS-CODE 2 If SSI-STATUS is 8-filled, then SSI-STATE-SUPPLEMENT-STATUS-CODE must be 8-filled 2416 Relational edit between SSI-STATE-SUPPLEMENT-STATUS-CODE and SSI-STATUS failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if !fns.hasValue(@val.SSI-STATUS), then !fns.hasValue(@val.SSI-STATE-SUPPLEMENT-STATUS-CODE)' SSI-STATUS,SSI-STATE-SUPPLEMENT-STATUS-CODE ELG092,ELG091











1,825 No logic changes ELG092-0001 RULE-2142 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG092 SSI-STATUS 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: SSI-STATUS SSI-STATUS ELG092











1,826 No logic changes ELG092-0002 RULE-2143 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG092 SSI-STATUS 2 If SSI-STATUS = "003" or is (8-filled or 9-filled), then SSI-IND must = "0" 2119 Relational edit between SSI-STATUS and SSI-IND failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqual(@val.SSI-STATUS, "003") || !fns.hasValue(@val.SSI-STATUS), then fns.isEqual(@val.SSI-IND, "0")' SSI-STATUS,SSI-IND ELG092,ELG090











1,827 No logic changes ELG093-0003 RULE-2144 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG093 STATE-SPEC-ELIG-GROUP 1 Value is not in the valid values list 103 Value is not included in the valid code list 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: STATE-SPEC-ELIG-GROUP STATE-SPEC-ELIG-GROUP ELG093











1,828 No logic changes ELG094-0001 RULE-2145 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG094 CONCEPTION-TO-BIRTH-IND 1 Value is not in the valid values list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: CONCEPTION-TO-BIRTH-IND CONCEPTION-TO-BIRTH-IND ELG094











1,829 No logic changes ELG095-0001 RULE-2146 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG095 ELIGIBILITY-CHANGE-REASON 1 Value is not in the valid values list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: ELIGIBILITY-CHANGE-REASON ELIGIBILITY-CHANGE-REASON ELG095











1,830 Logic updated: other ELG096-0001 RULE-7153 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG096 MAINTENANCE-ASSISTANCE-STATUS 1 Value is not in the valid values list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: MAINTENANCE-ASSISTANCE-STATUS MAINTENANCE-ASSISTANCE-STATUS ELG096











1,831 No logic changes ELG096-0004 RULE-2149 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG096 MAINTENANCE-ASSISTANCE-STATUS 2 If MAINTENANCE-ASSISTANCE-STATUS = "1" through "5", then MEDICAID-BASIS-OF-ELIGIBILITY must = "01" through "08" or "10" through "11" 2056 Relational edit between MAINTENANCE-ASSISTANCE-STATUS and MEDICAID-BASIS-OF-ELIGIBILITY failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqualToAny(@val.MAINTENANCE-ASSISTANCE-STATUS, "1", "2", "3", "4", "5"), then fns.isEqualToAny(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "01", "02", "03", "04", "05", "06", "07", "08", "10", "11")' MAINTENANCE-ASSISTANCE-STATUS,MEDICAID-BASIS-OF-ELIGIBILITY ELG096,ELG084











1,832 No logic changes ELG096-0006 RULE-2150 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG096 MAINTENANCE-ASSISTANCE-STATUS 2 If MEDICAID-BASIS-OF-ELIGIBILITY = "08", then MAINTENANCE-ASSISTANCE-STATUS must = "4" 2056 Relational edit between MAINTENANCE-ASSISTANCE-STATUS and MEDICAID-BASIS-OF-ELIGIBILITY failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqual(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "08"), then fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "4")' MEDICAID-BASIS-OF-ELIGIBILITY,MAINTENANCE-ASSISTANCE-STATUS ELG084,ELG096











1,833 No logic changes ELG096-0007 RULE-2151 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG096 MAINTENANCE-ASSISTANCE-STATUS 2 If MEDICAID-BASIS-OF-ELIGIBILITY = "06" or "07", then MAINTENANCE-ASSISTANCE-STATUS must = "1" 2056 Relational edit between MAINTENANCE-ASSISTANCE-STATUS and MEDICAID-BASIS-OF-ELIGIBILITY failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqualToAny(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "06", "07"), then fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "1")' MEDICAID-BASIS-OF-ELIGIBILITY,MAINTENANCE-ASSISTANCE-STATUS ELG084,ELG096











1,834 No logic changes ELG096-0008 RULE-2152 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG096 MAINTENANCE-ASSISTANCE-STATUS 2 If MEDICAID-BASIS-OF-ELIGIBILITY = "11", then MAINTENANCE-ASSISTANCE-STATUS must = "3" 2056 Relational edit between MAINTENANCE-ASSISTANCE-STATUS and MEDICAID-BASIS-OF-ELIGIBILITY failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqual(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "11"), then fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "3")' MEDICAID-BASIS-OF-ELIGIBILITY,MAINTENANCE-ASSISTANCE-STATUS ELG084,ELG096











1,835 No logic changes ELG096-0009 RULE-2153 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG096 MAINTENANCE-ASSISTANCE-STATUS 2 If DUAL-ELIGIBLE-CODE = "01", "03", "05", or "06", then MAINTENANCE-ASSISTANCE-STATUS must = "3" 2027 Relational edit between DUAL-ELIGIBLE-CODE and MAINTENANCE-ASSISTANCE-STATUS failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqualToAny(@val.DUAL-ELIGIBLE-CODE, "01", "03", "05", "06"), then fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "3")' DUAL-ELIGIBLE-CODE,MAINTENANCE-ASSISTANCE-STATUS ELG085,ELG096











1,836 No logic changes ELG097-0001 RULE-2154 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG097 RESTRICTED-BENEFITS-CODE 1 Value is not in the valid values list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: RESTRICTED-BENEFITS-CODE RESTRICTED-BENEFITS-CODE ELG097











1,837 No logic changes ELG097-0003 RULE-2155 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG097 RESTRICTED-BENEFITS-CODE 2 If RESTRICTED-BENEFITS-CODE = "4", then SEX must = "F" 2117 Relational edit between RESTRICTED-BENEFITS-CODE and SEX failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005

'if fns.isEqual(@secondaryRecord.RESTRICTED-BENEFITS-CODE, "4"), then fns.isEqual(@primaryRecord.SEX, "F")' SEX ELG023 RESTRICTED-BENEFITS-CODE ELG097

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,838 No logic changes ELG097-0004 RULE-2156 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG097 RESTRICTED-BENEFITS-CODE 2 If MEDICAID-BASIS-OF-ELIGIBILITY = "00" and MAINTENANCE-ASSISTANCE-STATUS = "0", then RESTRICTED-BENEFITS-CODE must = "0" 2136 Relational edit between RESTRICTED-BENEFITS-CODE, MEDICAID-BASIS-OF-ELIGIBILITY, and MAINTENANCE-ASSISTANCE-STATUS failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqual(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "00") && fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "0"), then fns.isEqual(@val.RESTRICTED-BENEFITS-CODE, "0")' MEDICAID-BASIS-OF-ELIGIBILITY,MAINTENANCE-ASSISTANCE-STATUS,RESTRICTED-BENEFITS-CODE ELG084,ELG096,ELG097











1,839 No logic changes ELG097-0005 RULE-2157 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG097 RESTRICTED-BENEFITS-CODE 2 If RESTRICTED-BENEFITS-CODE = "2", then CITIZENSHIP-IND must <> "1" 2116 Relational edit between RESTRICTED-BENEFITS-CODE and CITIZENSHIP-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003

'if fns.isEqual(@primaryRecord.RESTRICTED-BENEFITS-CODE, "2"), then !fns.isEqual(@secondaryRecord.CITIZENSHIP-IND, "1")' RESTRICTED-BENEFITS-CODE ELG097 CITIZENSHIP-IND ELG040

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG031,ELG033



1,840 No logic changes ELG097-0006 RULE-2158 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG097 RESTRICTED-BENEFITS-CODE 2 If RESTRICTED-BENEFITS-CODE = "1" through "7" or "A" through "D", then MAINTENANCE-ASSISTANCE-STATUS <> "0" and MEDICAID-BASIS-OF-ELIGIBILITY <> "0" 2135 Relational edit between RESTRICTED-BENEFITS-CODE, MAINTENANCE-ASSISTANCE-STATUS, and MEDICAID-BASIS-OF-ELIGIBILITY failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqualToAny(@val.RESTRICTED-BENEFITS-CODE, "1", "2", "3", "4", "5", "6", "7", "A", "B", "C", "D"), then !fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "0") && !fns.isEqual(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "00")' RESTRICTED-BENEFITS-CODE,MAINTENANCE-ASSISTANCE-STATUS,MEDICAID-BASIS-OF-ELIGIBILITY ELG097,ELG096,ELG084











1,841 No logic changes ELG098-0001 RULE-2159 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG098 TANF-CASH-CODE 1 Value is not in the valid values list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ELIGIBILITY-DETERMINANTS ELG00005



If the field is populated, the value must be contained in the set of valid values with id: TANF-CASH-CODE TANF-CASH-CODE ELG098











1,842 Logic updated: other ELG098-0003 RULE-2160 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG098 TANF-CASH-CODE 2 If MEDICAID-BASIS-OF-ELIGIBILITY = "00" or is 8-filled, then TANF-CASH-CODE must = "0" or be 8-filled 2420 Relational edit between TANF-CASH-CODE and MEDICAID-BASIS-OF-ELIGIBILITY failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if !fns.hasValue(@val.MEDICAID-BASIS-OF-ELIGIBILITY) || fns.isEqual(@val.MEDICAID-BASIS-OF-ELIGIBILITY, "00"), then !fns.hasValue(@val.TANF-CASH-CODE) || fns.isEqual(@val.TANF-CASH-CODE, "0")' MEDICAID-BASIS-OF-ELIGIBILITY,TANF-CASH-CODE ELG084,ELG098











1,843 Logic updated: other ELG098-0004 RULE-2161 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG098 TANF-CASH-CODE 2 If MAINTENANCE-ASSISTANCE-STATUS = "0" or is 8-filled, then TANF-CASH-CODE must = "0" or be 8-filled 2419 Relational edit between TANF-CASH-CODE and MAINTENANCE-ASSISTANCE-STATUS failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.isEqual(@val.MAINTENANCE-ASSISTANCE-STATUS, "0") || !fns.hasValue(@val.MAINTENANCE-ASSISTANCE-STATUS), then !fns.hasValue(@val.TANF-CASH-CODE) || fns.isEqual(@val.TANF-CASH-CODE, "0")' MAINTENANCE-ASSISTANCE-STATUS,TANF-CASH-CODE ELG096,ELG098











1,844 Merged ELG099-0001 RULE-2162 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG099 ELIGIBILITY-DETERMINANT-EFF-DATE 1 If ELIGIBILITY-DETERMINANT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be a valid date of the form CCYYMMDD ELIGIBILITY-DETERMINANT-EFF-DATE ELG099











1,845 Merged ELG099-0005 RULE-2162 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG099 ELIGIBILITY-DETERMINANT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be a valid date of the form CCYYMMDD ELIGIBILITY-DETERMINANT-EFF-DATE ELG099











1,846 Merged ELG099-0006 RULE-2164 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG099 ELIGIBILITY-DETERMINANT-EFF-DATE 2 ELIGIBILITY-DETERMINANT-EFF-DATE must be <= ELIGIBILITY-DETERMINANT-END-DATE 2030 Relational edit between ELIGIBILITY-DETERMINANT-EFF-DATE and ELIGIBILITY-DETERMINANT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.hasValue(@val.ELIGIBILITY-DETERMINANT-EFF-DATE) && fns.hasValue(@val.ELIGIBILITY-DETERMINANT-END-DATE), then fns.isLessThanOrEqual(@val.ELIGIBILITY-DETERMINANT-EFF-DATE, @val.ELIGIBILITY-DETERMINANT-END-DATE)' ELIGIBILITY-DETERMINANT-EFF-DATE,ELIGIBILITY-DETERMINANT-END-DATE ELG099,ELG100











1,847 No logic changes ELG099-0007 RULE-2165 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG099 ELIGIBILITY-DETERMINANT-EFF-DATE 2 If two or more ELIGIBILITY-DETERMINANTS record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and MSIS-CASE-NUM
then for each pair of record segments,
(Segment 1 ELIGIBILITY-DETERMINANT-EFF-DATE must <> Segment 2 ELIGIBILITY-DETERMINANT-EFF-DATE)
AND
( (If Segment 1 ELIGIBILITY-DETERMINANT-EFF-DATE < Segment 2 ELIGIBILITY-DETERMINANT-EFF-DATE,
then
Segment 1 ELIGIBILITY-DETERMINANT-END-DATE must be < Segment 2 ELIGIBILITY-DETERMINANT-EFF-DATE)
OR
(If Segment 2 ELIGIBILITY-DETERMINANT-EFF-DATE < Segment 1 ELIGIBILITY-DETERMINANT-EFF-DATE,
then
Segment 2 ELIGIBILITY-DETERMINANT-END-DATE must be < Segment 1 ELIGIBILITY-DETERMINANT-EFF-DATE) )		 2150 Edit for overlapping coverage dates in record segments that have non-unique key fields in ELIGIBILITY-DETERMINANTS failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) ELIGIBILITY-DETERMINANTS ELG00005



Records with the same primary keys must have non-overlapping date ranges. Effective date field: ELIGIBILITY-DETERMINANT-EFF-DATE. End date field: ELIGIBILITY-DETERMINANT-END-DATE ELIGIBILITY-DETERMINANT-EFF-DATE,ELIGIBILITY-DETERMINANT-END-DATE ELG099,ELG100











1,848 Merged ELG099-0008 RULE-2120 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG099 ELIGIBILITY-DETERMINANT-EFF-DATE 2 ( ELIGIBILITY-DETERMINANT-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ELIGIBILITY-DETERMINANT-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2472 Relational edit between ELIGIBILITY-DETERMINANT-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005

record ELIGIBILITY-DETERMINANTS has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,849 Merged ELG100-0001 RULE-2167 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG100 ELIGIBILITY-DETERMINANT-END-DATE 1 If ELIGIBILITY-DETERMINANT-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be a valid date of the form CCYYMMDD ELIGIBILITY-DETERMINANT-END-DATE ELG100











1,850 Merged ELG100-0005 RULE-2167 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG100 ELIGIBILITY-DETERMINANT-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be a valid date of the form CCYYMMDD ELIGIBILITY-DETERMINANT-END-DATE ELG100











1,851 Merged ELG100-0007 RULE-2120 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG100 ELIGIBILITY-DETERMINANT-END-DATE 2 ( ELIGIBILITY-DETERMINANT-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ELIGIBILITY-DETERMINANT-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ELIGIBILITY-DETERMINANTS-ELG00005] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ELIGIBILITY-DETERMINANTS-ELG00005] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2473 Relational edit between ELIGIBILITY-DETERMINANT-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ELIGIBILITY-DETERMINANTS ELG00005

record ELIGIBILITY-DETERMINANTS has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082



1,852 Merged ELG100-0008 RULE-2164 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG100 ELIGIBLE-DETERMINANT-END-DATE 2-M
2032
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.hasValue(@val.ELIGIBILITY-DETERMINANT-EFF-DATE) && fns.hasValue(@val.ELIGIBILITY-DETERMINANT-END-DATE), then fns.isLessThanOrEqual(@val.ELIGIBILITY-DETERMINANT-EFF-DATE, @val.ELIGIBILITY-DETERMINANT-END-DATE)' ELIGIBILITY-DETERMINANT-EFF-DATE,ELIGIBILITY-DETERMINANT-END-DATE ELG099,ELG100











1,853 Logic updated: string matching ELG101-0001 RULE-2171 ELIGIBLE ELIGIBILITY-DETERMINANTS-ELG00005 ELG101 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ELIGIBILITY-DETERMINANTS ELG00005



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG101











1,854 Moved to R&C ELG103-0003
ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG103 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,855 Moved to R&C ELG103-0004
ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG103 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,856 No logic changes ELG104-0002 RULE-2174 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG104 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG104











1,857 Logic updated: other ELG104-0003 RULE-2175 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG104 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG104 SUBMITTING-STATE ELG007









1,858 Retired: Other reasons ELG105-0002
ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG105 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,859 No logic changes ELG105-0003 RULE-2177 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG105 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Field RECORD-NUMBER should be unique across all records of type HEALTH-HOME-SPA-PARTICIPATION-INFORMATION RECORD-NUMBER ELG105











1,860 Retired: MSIS ID checks ELG106-0001
ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG106 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,861 Retired: MSIS ID checks ELG106-0002
ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG106 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,862 Merged ELG106-0005 RULE-2180 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG106 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2200 Edit that HEALTH-HOME-SPA-PARTICIPATION-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006

record HEALTH-HOME-SPA-PARTICIPATION-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG104,ELG106



1,863 Logic updated: string matching ELG107-0002 RULE-2181 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG107 HEALTH-HOME-SPA-NAME 1 Field contains invalid characters - HEALTH-HOME-SPA-NAME 120 Field contains invalid characters - HEALTH-HOME-SPA-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



'if fns.hasValue(@val.HEALTH-HOME-SPA-NAME), then fns.matches(@val.HEALTH-HOME-SPA-NAME, "^[^|*]*$")' HEALTH-HOME-SPA-NAME ELG107











1,864 Retired: required value checks ELG108-0001
ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG108 HEALTH-HOME-ENTITY-NAME 1 Required data element has not been reported. 113 Required data element has not been reported.

























1,865 Logic updated: string matching ELG108-0002 RULE-2183 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG108 HEALTH-HOME-ENTITY-NAME 1 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 120 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.matches(@val.HEALTH-HOME-ENTITY-NAME, "^[^|*]*$")' HEALTH-HOME-ENTITY-NAME ELG108











1,866 Merged ELG109-0001 RULE-2184 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG109 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE 1 If HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE ELG109











1,867 Merged ELG109-0005 RULE-2184 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG109 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE ELG109











1,868 Merged ELG109-0006 RULE-2186 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG109 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE 2 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE must be <= HEALTH-HOME-SPA-PARTICIPATION-END-DATE 2048 Relational edit between HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE and HEALTH-HOME-SPA-PARTICIPATION-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



'if fns.hasValue(@val.HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE) && fns.hasValue(@val.HEALTH-HOME-SPA-PARTICIPATION-END-DATE), then fns.isLessThanOrEqual(@val.HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE, @val.HEALTH-HOME-SPA-PARTICIPATION-END-DATE)' HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE,HEALTH-HOME-SPA-PARTICIPATION-END-DATE ELG109,ELG110











1,869 No logic changes ELG109-0007 RULE-2187 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG109 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE 2 If MAINTENANCE-ASSISTANCE-STATUS = "0" and MEDICAID-BASIS-OF-ELIGIBILITY ="0", then HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE must be 8-filled 2133 Relational edit between HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE, MAINTENANCE-ASSISTANCE-STATUS, and MEDICAID-BASIS-OF-ELIGIBILITY failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006

'if fns.isEqual(@primaryRecord.MAINTENANCE-ASSISTANCE-STATUS, "0") && fns.isEqual(@primaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "0"), then fns.hasValue(@secondaryRecord.HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE)' MAINTENANCE-ASSISTANCE-STATUS,MEDICAID-BASIS-OF-ELIGIBILITY ELG096,ELG084 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE ELG109

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG104,ELG106



1,870 No logic changes ELG109-0008 RULE-2188 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG109 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE 2 If two or more HEALTH-HOME-SPA-PARTICIPATION-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, HEALTH-HOME-SPA-NAME, and HEALTH-HOME-ENTITY-NAME
then for each pair of record segments,
(Segment 1 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE must not = Segment 2 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE)
AND
( (If Segment 1 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE < Segment 2 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE,
then
Segment 1 HEALTH-HOME-SPA-PARTICIPATION-END-DATE must be < Segment 2 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE)
OR
(If Segment 2 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE < Segment 1 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE,
then
Segment 2 HEALTH-HOME-SPA-PARTICIPATION-END-DATE must be < Segment 1 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE) )		 2155 Edit for overlapping coverage dates in record segments that have non-unique key fields in HEALTH-HOME-SPA-PARTICIPATION-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Records with the same primary keys must have non-overlapping date ranges. Effective date field: HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE. End date field: HEALTH-HOME-SPA-PARTICIPATION-END-DATE HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE,HEALTH-HOME-SPA-PARTICIPATION-END-DATE ELG109,ELG110











1,871 Merged ELG109-0009 RULE-2180 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG109 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE 2 ( HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2485 Relational edit between HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006

record HEALTH-HOME-SPA-PARTICIPATION-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG104,ELG106



1,872 Retired: Other reasons ELG109-0011
ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG109 HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE 2 If two or more HEALTH-HOME-SPA-PARTICIPATION-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, HEALTH-HOME-SPA-NAME, and HEALTH-HOME-ENTITY-NAME and these record segments are sorted in ascending order by HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N HEALTH-HOME-SPA-PARTICIPATION-END-DATE must = Segment (N+1) HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE minus 1 day 2452 Edit for contiguous HEALTH-HOME-SPA-PARTICIPATION-INFORMATION record segments failed (Exact match on all key fields except the file segment effective date)

























1,873 Merged ELG110-0001 RULE-2191 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG110 HEALTH-HOME-SPA-PARTICIPATION-END-DATE 1 If HEALTH-HOME-SPA-PARTICIPATION-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PARTICIPATION-END-DATE ELG110











1,874 Merged ELG110-0005 RULE-2191 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG110 HEALTH-HOME-SPA-PARTICIPATION-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PARTICIPATION-END-DATE ELG110











1,875 Merged ELG110-0007 RULE-2186 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG110 HEALTH-HOME-SPA-PARTICIPATION-END-DATE 2-M
2048
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



'if fns.hasValue(@val.HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE) && fns.hasValue(@val.HEALTH-HOME-SPA-PARTICIPATION-END-DATE), then fns.isLessThanOrEqual(@val.HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE, @val.HEALTH-HOME-SPA-PARTICIPATION-END-DATE)' HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE,HEALTH-HOME-SPA-PARTICIPATION-END-DATE ELG109,ELG110











1,876 Merged ELG110-0008 RULE-2180 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG110 HEALTH-HOME-SPA-PARTICIPATION-END-DATE 2 ( HEALTH-HOME-SPA-PARTICIPATION-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( HEALTH-HOME-SPA-PARTICIPATION-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2487 Relational edit between HEALTH-HOME-SPA-PARTICIPATION-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006

record HEALTH-HOME-SPA-PARTICIPATION-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG104,ELG106



1,877 Logic updated: other ELG110-0009 RULE-2195 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG110 HEALTH-HOME-SPA-PARTICIPATION-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then HEALTH-HOME-SPA-PARTICIPATION-END-DATE must be <= DATE-OF-DEATH 2486 Relational edit between HEALTH-HOME-SPA-PARTICIPATION-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.HEALTH-HOME-SPA-PARTICIPATION-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.HEALTH-HOME-SPA-PARTICIPATION-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 HEALTH-HOME-SPA-PARTICIPATION-END-DATE ELG110

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG104,ELG106



1,878 Merged ELG111-0001 RULE-2196 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG111 HEALTH-HOME-ENTITY-EFF-DATE 1 HEALTH-HOME-ENTITY-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-ENTITY-EFF-DATE ELG111











1,879 Merged ELG111-0002 RULE-2196 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG111 HEALTH-HOME-ENTITY-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-ENTITY-EFF-DATE ELG111











1,880 Logic updated: string matching ELG112-0001 RULE-2198 ELIGIBLE HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006 ELG112 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG112











1,881 Moved to R&C ELG114-0003
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG114 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,882 Moved to R&C ELG114-0004
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG114 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,883 No logic changes ELG115-0002 RULE-2201 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG115 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value HEALTH-HOME-SPA-PROVIDERS ELG00007



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG115











1,884 Logic updated: other ELG115-0003 RULE-2202 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG115 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) HEALTH-HOME-SPA-PROVIDERS ELG00007 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG115 SUBMITTING-STATE ELG007









1,885 Retired: Other reasons ELG116-0002
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG116 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,886 No logic changes ELG116-0003 RULE-2204 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG116 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) HEALTH-HOME-SPA-PROVIDERS ELG00007



Field RECORD-NUMBER should be unique across all records of type HEALTH-HOME-SPA-PROVIDERS RECORD-NUMBER ELG116











1,887 Retired: MSIS ID checks ELG117-0001
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG117 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,888 Retired: MSIS ID checks ELG117-0002
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG117 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,889 Merged ELG117-0005 RULE-2207 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG117 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PROVIDERS-ELG00007] must = MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] on any record in the file
and
HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] must = HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006]
and
HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] must = HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006]
and
SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] must = SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] on the same record in the file		 2201 Edit that HEALTH-HOME-SPA-PROVIDERS child record has a HEALTH-HOME-SPA-PARTICIPATION-INFORMATION parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006 HEALTH-HOME-SPA-PROVIDERS ELG00007

record HEALTH-HOME-SPA-PROVIDERS has corresponding parent record HEALTH-HOME-SPA-PARTICIPATION-INFORMATION





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,HEALTH-HOME-SPA-NAME,HEALTH-HOME-ENTITY-NAME ELG104,ELG106,ELG107,ELG108 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,HEALTH-HOME-SPA-NAME,HEALTH-HOME-ENTITY-NAME ELG115,ELG117,ELG118,ELG119



1,890 Logic updated: string matching ELG118-0002 RULE-2208 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG118 HEALTH-HOME-SPA-NAME 1 Field contains invalid characters - HEALTH-HOME-SPA-NAME 120 Field contains invalid characters - HEALTH-HOME-SPA-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-SPA-PROVIDERS ELG00007



'if fns.hasValue(@val.HEALTH-HOME-SPA-NAME), then fns.matches(@val.HEALTH-HOME-SPA-NAME, "^[^|*]*$")' HEALTH-HOME-SPA-NAME ELG118











1,891 Retired: required value checks ELG119-0001
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG119 HEALTH-HOME-ENTITY-NAME 1 Required data element has not been reported. 113 Required data element has not been reported.

























1,892 Logic updated: string matching ELG119-0003 RULE-2210 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG119 HEALTH-HOME-ENTITY-NAME 1 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 120 Field contains invalid characters - HEALTH-HOME-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-SPA-PROVIDERS ELG00007



'if fns.hasValue(@val.HEALTH-HOME-ENTITY-NAME), then fns.matches(@val.HEALTH-HOME-ENTITY-NAME, "^[^|*]*$")' HEALTH-HOME-ENTITY-NAME ELG119











1,893 Retired: Other reasons ELG120-0001
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG120 HEALTH-HOME-PROV-NUM 1 Value is not included a state supplied valid code list 125 Value is not included in a state supplied valid code list

























1,894 Logic updated: other ELG120-0003 RULE-2212 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG120 HEALTH-HOME-PROV-NUM 3 HEALTH-HOME-PROV-NUM must = any PROV-IDENTIFIER [PROVIDER] if SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 3020 A PROVIDER record for the HEALTH-HOME-PROV-NUM is missing 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 HEALTH-HOME-SPA-PROVIDERS ELG00007

For every record of type HEALTH-HOME-SPA-PROVIDERS, there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys





SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,HEALTH-HOME-PROV-NUM ELG115,ELG120



1,895 Merged ELG121-0001 RULE-2213 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG121 HEALTH-HOME-SPA-PROVIDER-EFF-DATE 1 If HEALTH-HOME-SPA-PROVIDER-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PROVIDER-EFF-DATE ELG121











1,896 Merged ELG121-0005 RULE-2213 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG121 HEALTH-HOME-SPA-PROVIDER-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PROVIDER-EFF-DATE ELG121











1,897 Merged ELG121-0006 RULE-2215 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG121 HEALTH-HOME-SPA-PROVIDER-EFF-DATE 2 HEALTH-HOME-SPA-PROVIDER-EFF-DATE must be <= HEALTH-HOME-SPA-PROVIDER-END-DATE 2049 Relational edit between HEALTH-HOME-SPA-PROVIDER-EFF-DATE and HEALTH-HOME-SPA-PROVIDER-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HEALTH-HOME-SPA-PROVIDERS ELG00007



'if fns.hasValue(@val.HEALTH-HOME-SPA-PROVIDER-EFF-DATE) && fns.hasValue(@val.HEALTH-HOME-SPA-PROVIDER-END-DATE), then fns.isLessThanOrEqual(@val.HEALTH-HOME-SPA-PROVIDER-EFF-DATE, @val.HEALTH-HOME-SPA-PROVIDER-END-DATE)' HEALTH-HOME-SPA-PROVIDER-EFF-DATE,HEALTH-HOME-SPA-PROVIDER-END-DATE ELG121,ELG122











1,898 Retired: Other reasons ELG121-0007
ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG121 HEALTH-HOME-SPA-PROVIDER-EFF-DATE 2 If MAINTENANCE-ASSISTANCE-STATUS = "0" and MEDICAID-BASIS-OF-ELIGIBILITY ="0", then HEALTH-HOME-SPA-PROVIDER-EFF-DATE must be 8-filled 2134 Relational edit between HEALTH-HOME-SPA-PROVIDER-EFF-DATE, MAINTENANCE-ASSISTANCE-STATUS, and MEDICAID-BASIS-OF-ELIGIBILITY failed

























1,899 No logic changes ELG121-0008 RULE-2217 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG121 HEALTH-HOME-SPA-PROVIDER-EFF-DATE 2 If two or more HEALTH-HOME-SPA-PROVIDERS record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, HEALTH-HOME-SPA-NAME, HEALTH-HOME-SPA-NAME, and HEALTH-HOME-PROV-NUM
then for each pair of record segments,
(Segment 1 HEALTH-HOME-SPA-PROVIDER-EFF-DATE must <> Segment 2 HEALTH-HOME-SPA-PROVIDER-EFF-DATE)
AND
( (If Segment 1 HEALTH-HOME-SPA-PROVIDER-EFF-DATE < Segment 2 HEALTH-HOME-SPA-PROVIDER-EFF-DATE,
then
Segment 1 HEALTH-HOME-SPA-PROVIDER-END-DATE must be < Segment 2 HEALTH-HOME-SPA-PROVIDER-EFF-DATE)
OR
(If Segment 2 HEALTH-HOME-SPA-PROVIDER-EFF-DATE < Segment 1 HEALTH-HOME-SPA-PROVIDER-EFF-DATE,
then
Segment 2 HEALTH-HOME-SPA-PROVIDER-END-DATE must be < Segment 1 HEALTH-HOME-SPA-PROVIDER-EFF-DATE) )		 2156 Edit for overlapping coverage dates in record segments that have non-unique key fields in HEALTH-HOME-SPA-PROVIDERS failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) HEALTH-HOME-SPA-PROVIDERS ELG00007



Records with the same primary keys must have non-overlapping date ranges. Effective date field: HEALTH-HOME-SPA-PROVIDER-EFF-DATE. End date field: HEALTH-HOME-SPA-PROVIDER-END-DATE HEALTH-HOME-SPA-PROVIDER-EFF-DATE,HEALTH-HOME-SPA-PROVIDER-END-DATE ELG121,ELG122











1,900 Merged ELG121-0009 RULE-2207 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG121 HEALTH-HOME-SPA-PROVIDER-EFF-DATE 2 ( HEALTH-HOME-SPA-PROVIDER-EFF-DATE must be >= HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE on any HEALTH-HOME-SPA-PARTICIPATION-INFORMATION segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PROVIDERS-ELG00007]] = MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006])
AND
( HEALTH-HOME-SPA-PROVIDER-EFF-DATE must be <= HEALTH-HOME-SPA-PARTICIPATION-END-DATE on any HEALTH-HOME-SPA-PARTICIPATION-INFORMATION segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PROVIDERS-ELG00007]] = MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006])		 2488 Relational edit between HEALTH-HOME-SPA-PROVIDER-EFF-DATE, HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE, and HEALTH-HOME-SPA-PARTICIPATION-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006 HEALTH-HOME-SPA-PROVIDERS ELG00007

record HEALTH-HOME-SPA-PROVIDERS has corresponding parent record HEALTH-HOME-SPA-PARTICIPATION-INFORMATION





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,HEALTH-HOME-SPA-NAME,HEALTH-HOME-ENTITY-NAME ELG104,ELG106,ELG107,ELG108 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,HEALTH-HOME-SPA-NAME,HEALTH-HOME-ENTITY-NAME ELG115,ELG117,ELG118,ELG119



1,901 Merged ELG122-0001 RULE-2219 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG122 HEALTH-HOME-SPA-PROVIDER-END-DATE 1 If HEALTH-HOME-SPA-PROVIDER-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PROVIDER-END-DATE ELG122











1,902 Merged ELG122-0005 RULE-2219 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG122 HEALTH-HOME-SPA-PROVIDER-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-SPA-PROVIDER-END-DATE ELG122











1,903 Merged ELG122-0007 RULE-2207 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG122 HEALTH-HOME-SPA-PROVIDER-END-DATE 2 ( HEALTH-HOME-SPA-PROVIDER-END-DATE must be <= HEALTH-HOME-SPA-PARTICIPATION-END-DATE on any HEALTH-HOME-SPA-PARTICIPATION-INFORMATION segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PROVIDERS-ELG00007]] = MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006])
AND
( HEALTH-HOME-SPA-PROVIDER-END-DATE must be >= HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE on any HEALTH-HOME-SPA-PARTICIPATION-INFORMATION segment where SUBMITTING-STATE [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = SUBMITTING-STATE [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PROVIDERS-ELG00007]] = MSIS-IDENTIFICATION-NUM [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-SPA-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006] and HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PROVIDERS-ELG00007] = HEALTH-HOME-ENTITY-NAME [HEALTH-HOME-SPA-PARTICIPATION-INFORMATION-ELG00006])		 2489 Relational edit between HEALTH-HOME-SPA-PROVIDER-END-DATE, HEALTH-HOME-SPA-PARTICIPATION-END-DATE, and HEALTH-HOME-SPA-PARTICIPATION-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006 HEALTH-HOME-SPA-PROVIDERS ELG00007

record HEALTH-HOME-SPA-PROVIDERS has corresponding parent record HEALTH-HOME-SPA-PARTICIPATION-INFORMATION





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,HEALTH-HOME-SPA-NAME,HEALTH-HOME-ENTITY-NAME ELG104,ELG106,ELG107,ELG108 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM,HEALTH-HOME-SPA-NAME,HEALTH-HOME-ENTITY-NAME ELG115,ELG117,ELG118,ELG119



1,904 Merged ELG122-0008 RULE-2215 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG122 HEALTH-HOME-SPA-PROVIDER-END-DATE 2-M
2049
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HEALTH-HOME-SPA-PROVIDERS ELG00007



'if fns.hasValue(@val.HEALTH-HOME-SPA-PROVIDER-EFF-DATE) && fns.hasValue(@val.HEALTH-HOME-SPA-PROVIDER-END-DATE), then fns.isLessThanOrEqual(@val.HEALTH-HOME-SPA-PROVIDER-EFF-DATE, @val.HEALTH-HOME-SPA-PROVIDER-END-DATE)' HEALTH-HOME-SPA-PROVIDER-EFF-DATE,HEALTH-HOME-SPA-PROVIDER-END-DATE ELG121,ELG122











1,905 Merged ELG123-0001 RULE-2223 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG123 HEALTH-HOME-ENTITY-EFF-DATE 1 HEALTH-HOME-ENTITY-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-ENTITY-EFF-DATE ELG123











1,906 Merged ELG123-0002 RULE-2223 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG123 HEALTH-HOME-ENTITY-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-ENTITY-EFF-DATE ELG123











1,907 Logic updated: string matching ELG124-0001 RULE-2225 ELIGIBLE HEALTH-HOME-SPA-PROVIDERS-ELG00007 ELG124 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-SPA-PROVIDERS ELG00007



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG124











1,908 Moved to R&C ELG126-0003
ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG126 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,909 Moved to R&C ELG126-0004
ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG126 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,910 No logic changes ELG127-0002 RULE-2228 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG127 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG127











1,911 Logic updated: other ELG127-0003 RULE-2229 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG127 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG127 SUBMITTING-STATE ELG007









1,912 Retired: Other reasons ELG128-0002
ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG128 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,913 No logic changes ELG128-0003 RULE-2231 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG128 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Field RECORD-NUMBER should be unique across all records of type HEALTH-HOME-CHRONIC-CONDITIONS RECORD-NUMBER ELG128











1,914 Retired: MSIS ID checks ELG129-0001
ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG129 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,915 Retired: MSIS ID checks ELG129-0002
ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG129 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,916 Merged ELG129-0005 RULE-2234 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG129 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2199 Edit that HEALTH-HOME-CHRONIC-CONDITIONS child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HEALTH-HOME-CHRONIC-CONDITIONS ELG00008

record HEALTH-HOME-CHRONIC-CONDITIONS has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG127,ELG129



1,917 No logic changes ELG130-0001 RULE-2235 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG130 HEALTH-HOME-CHRONIC-CONDITION 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-HOME-CHRONIC-CONDITION HEALTH-HOME-CHRONIC-CONDITION ELG130











1,918 No logic changes ELG131-0001 RULE-2236 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG131 HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION 2 If HEALTH-HOME-CHRONIC-CONDITION = "H", then HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION must not be 8-filled 2292 Relational edit between HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION and HEALTH-HOME-CHRONIC-CONDITION failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



'if fns.isEqual(@val.HEALTH-HOME-CHRONIC-CONDITION, "H"), then fns.hasValue(@val.HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION)' HEALTH-HOME-CHRONIC-CONDITION,HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION ELG130,ELG131











1,919 Logic updated: string matching ELG131-0002 RULE-2237 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG131 HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION 1 Value contains invalid characters - HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION 120 Field contains invalid characters - HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



'if fns.hasValue(@val.HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION), then fns.matches(@val.HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION, "^[^|*]*$")' HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION ELG131











1,920 Merged ELG132-0001 RULE-2238 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG132 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE 1 If HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE ELG132











1,921 Merged ELG132-0005 RULE-2238 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG132 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE ELG132











1,922 Merged ELG132-0006 RULE-2240 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG132 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE 2 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE must be <= HEALTH-HOME-CHRONIC-CONDITION-END-DATE 2047 Relational edit between HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE and HEALTH-HOME-CHRONIC-CONDITION-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



'if fns.hasValue(@val.HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE) && fns.hasValue(@val.HEALTH-HOME-CHRONIC-CONDITION-END-DATE), then fns.isLessThanOrEqual(@val.HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE, @val.HEALTH-HOME-CHRONIC-CONDITION-END-DATE)' HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE,HEALTH-HOME-CHRONIC-CONDITION-END-DATE ELG132,ELG133











1,923 No logic changes ELG132-0008 RULE-2241 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG132 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE 2 If two or more HEALTH-HOME-CHRONIC-CONDITIONS record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, HEALTH-HOME-CHRONIC-CONDITION, and HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION
then for each pair of record segments,
(Segment 1 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE must <> Segment 2 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE)
AND
( (If Segment 1 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE < Segment 2 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE,
then
Segment 1 HEALTH-HOME-CHRONIC-CONDITION-END-DATE must be < Segment 2 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE)
OR
(If Segment 2 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE < Segment 1 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE,
then
Segment 2 HEALTH-HOME-CHRONIC-CONDITION-END-DATE must be < Segment 1 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE) )		 2154 Edit for overlapping coverage dates in record segments that have non-unique key fields in HEALTH-HOME-CHRONIC-CONDITIONS failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Records with the same primary keys must have non-overlapping date ranges. Effective date field: HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE. End date field: HEALTH-HOME-CHRONIC-CONDITION-END-DATE HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE,HEALTH-HOME-CHRONIC-CONDITION-END-DATE ELG132,ELG133











1,924 Merged ELG132-0009 RULE-2234 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG132 HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE 2 ( HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2483 Relational edit between HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HEALTH-HOME-CHRONIC-CONDITIONS ELG00008

record HEALTH-HOME-CHRONIC-CONDITIONS has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG127,ELG129



1,925 Merged ELG133-0001 RULE-2243 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG133 HEALTH-HOME-CHRONIC-CONDITION-END-DATE 1 If HEALTH-HOME-CHRONIC-CONDITION-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-CHRONIC-CONDITION-END-DATE ELG133











1,926 Merged ELG133-0005 RULE-2243 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG133 HEALTH-HOME-CHRONIC-CONDITION-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be a valid date of the form CCYYMMDD HEALTH-HOME-CHRONIC-CONDITION-END-DATE ELG133











1,927 Merged ELG133-0008 RULE-2234 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG133 HEALTH-HOME-CHRONIC-CONDITION-END-DATE 2 ( HEALTH-HOME-CHRONIC-CONDITION-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( HEALTH-HOME-CHRONIC-CONDITION-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2484 Relational edit between HEALTH-HOME-CHRONIC-CONDITION-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HEALTH-HOME-CHRONIC-CONDITIONS ELG00008

record HEALTH-HOME-CHRONIC-CONDITIONS has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG127,ELG129



1,928 Merged ELG133-0009 RULE-2240 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG133 HEALTH-HOME-CHRONIC-CONDITION-END-DATE 2-M
2047
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



'if fns.hasValue(@val.HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE) && fns.hasValue(@val.HEALTH-HOME-CHRONIC-CONDITION-END-DATE), then fns.isLessThanOrEqual(@val.HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE, @val.HEALTH-HOME-CHRONIC-CONDITION-END-DATE)' HEALTH-HOME-CHRONIC-CONDITION-EFF-DATE,HEALTH-HOME-CHRONIC-CONDITION-END-DATE ELG132,ELG133











1,929 Logic updated: string matching ELG134-0001 RULE-2247 ELIGIBLE HEALTH-HOME-CHRONIC-CONDITIONS-ELG00008 ELG134 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG134











1,930 Moved to R&C ELG136-0003
ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG136 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,931 Moved to R&C ELG136-0004
ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG136 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,932 No logic changes ELG137-0002 RULE-2250 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG137 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value LOCK-IN-INFORMATION ELG00009



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG137











1,933 Logic updated: other ELG137-0003 RULE-2251 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG137 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) LOCK-IN-INFORMATION ELG00009 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG137 SUBMITTING-STATE ELG007









1,934 Retired: Other reasons ELG138-0002
ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG138 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,935 No logic changes ELG138-0003 RULE-2253 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG138 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) LOCK-IN-INFORMATION ELG00009



Field RECORD-NUMBER should be unique across all records of type LOCK-IN-INFORMATION RECORD-NUMBER ELG138











1,936 Retired: MSIS ID checks ELG139-0001
ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG139 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,937 Retired: MSIS ID checks ELG139-0002
ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG139 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,938 Merged ELG139-0005 RULE-2256 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG139 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [LOCK-IN-INFORMATION-ELG00009] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [LOCK-IN-INFORMATION-ELG00009] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2202 Edit that LOCK-IN-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LOCK-IN-INFORMATION ELG00009

record LOCK-IN-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG137,ELG139



1,939 Retired: Other reasons ELG140-0001
ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG140 LOCKIN-PROV-NUM 1 Value is not in required format 101 Value is not in required format

























1,940 Logic updated: other ELG140-0002 RULE-2258 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG140 LOCKIN-PROV-NUM 3 LOCKIN-PROV-NUM must = any PROV-IDENTIFIER [PROVIDER] if SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 3021 A PROVIDER record for the LOCKIN-PROV-NUM is missing 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 LOCK-IN-INFORMATION ELG00009

For every record of type LOCK-IN-INFORMATION, there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys





SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,LOCKIN-PROV-NUM ELG137,ELG140



1,941 Logic updated: other ELG141-0001 RULE-2259 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG141 LOCKIN-PROV-TYPE 3 LOCKIN-PROV-TYPE must = PROV-CLASSIFICATION-CODE [PROVIDER]
where
((SUBMITTING-STATE [LOCK-IN-INFORMATION-ELG00009] = SUBMITTING-STATE [PROV-TAXONOMY-CLASSIFICATION-PRV00006] )
and
PROV-CLASSIFICATION-TYPE [PROVIDER] = "3"
and
PROV-IDENTIFIER-TYPE [PROVIDER] = "1"
and
LOCKIN-PROV-NUM = PROVIDER-IDENTIFIER [PROV-IDENTIFIERS-PRV00005])		 3057 A PROVIDER record for the LOCKIN-PROV-TYPE does not correspond to a state provider identifier 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule PROV-TAXONOMY-CLASSIFICATION PRV00006 PROV-IDENTIFIERS PRV00005 LOCK-IN-INFORMATION ELG00009 For every record of type PROV-IDENTIFIERS, there must be a valid record of type PROV-TAXONOMY-CLASSIFICATION that matches on the join keys, where fns.isEqual(@primaryRecord.PROV-CLASSIFICATION-TYPE, "3") && fns.isEqual(@secondaryRecord.PROV-IDENTIFIER-TYPE, "1") PROV-CLASSIFICATION-TYPE PRV088 PROV-IDENTIFIER-TYPE PRV077

SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV085,PRV087 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV073,PRV075 SUBMITTING-STATE,PROV-IDENTIFIER
SUBMITTING-STATE,LOCKIN-PROV-NUM ELG137,ELG140
1,942 Merged ELG142-0001 RULE-2260 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG142 LOCKIN-EFF-DATE 1 If LOCKIN-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be a valid date of the form CCYYMMDD LOCKIN-EFF-DATE ELG142











1,943 Merged ELG142-0005 RULE-2260 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG142 LOCKIN-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be a valid date of the form CCYYMMDD LOCKIN-EFF-DATE ELG142











1,944 Merged ELG142-0006 RULE-2262 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG142 LOCKIN-EFF-DATE 2 LOCKIN-EFF-DATE must be <= LOCKIN-END-DATE 2054 Relational edit between LOCKIN-EFF-DATE and LOCKIN-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) LOCK-IN-INFORMATION ELG00009



'if fns.hasValue(@val.LOCKIN-EFF-DATE) && fns.hasValue(@val.LOCKIN-END-DATE), then fns.isLessThanOrEqual(@val.LOCKIN-EFF-DATE, @val.LOCKIN-END-DATE)' LOCKIN-EFF-DATE,LOCKIN-END-DATE ELG142,ELG143











1,945 No logic changes ELG142-0007 RULE-2263 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG142 LOCKIN-EFF-DATE 2 If two or more LOCK-IN-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, LOCKIN-PROV-NUM, and LOCKIN-PROV-TYPE
then for each pair of record segments,
(Segment 1 LOCKIN-EFF-DATE must <> Segment 2 LOCKIN-EFF-DATE)
AND
( (If Segment 1 LOCKIN-EFF-DATE < Segment 2 LOCKIN-EFF-DATE,
then
Segment 1 LOCKIN-END-DATE must be < Segment 2 LOCKIN-EFF-DATE)
OR
(If Segment 2 LOCKIN-EFF-DATE < Segment 1 LOCKIN-EFF-DATE,
then
Segment 2 LOCKIN-END-DATE must be < Segment 1 LOCKIN-EFF-DATE) )		 2157 Edit for overlapping coverage dates in record segments that have non-unique key fields in LOCK-IN-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) LOCK-IN-INFORMATION ELG00009



Records with the same primary keys must have non-overlapping date ranges. Effective date field: LOCKIN-EFF-DATE. End date field: LOCKIN-END-DATE LOCKIN-EFF-DATE,LOCKIN-END-DATE ELG142,ELG143











1,946 Merged ELG142-0008 RULE-2256 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG142 LOCKIN-EFF-DATE 2 ( LOCKIN-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LOCK-IN-INFORMATION-ELG00009] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LOCK-IN-INFORMATION-ELG00009] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( LOCKIN-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LOCK-IN-INFORMATION-ELG00009] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LOCK-IN-INFORMATION-ELG00009] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2496 Relational edit between LOCKIN-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LOCK-IN-INFORMATION ELG00009

record LOCK-IN-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG137,ELG139



1,947 Merged ELG143-0001 RULE-2265 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG143 LOCKIN-END-DATE 1 If LOCKIN-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be a valid date of the form CCYYMMDD LOCKIN-END-DATE ELG143











1,948 Merged ELG143-0005 RULE-2265 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG143 LOCKIN-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be a valid date of the form CCYYMMDD LOCKIN-END-DATE ELG143











1,949 Merged ELG143-0007 RULE-2256 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG143 LOCKIN-END-DATE 2 ( LOCKIN-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LOCK-IN-INFORMATION-ELG00009] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LOCK-IN-INFORMATION-ELG00009] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( LOCKIN-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LOCK-IN-INFORMATION-ELG00009] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LOCK-IN-INFORMATION-ELG00009] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2498 Relational edit between LOCKIN-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LOCK-IN-INFORMATION ELG00009

record LOCK-IN-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG137,ELG139



1,950 Logic updated: other ELG143-0008 RULE-2268 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG143 LOCKIN-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then LOCKIN-END-DATE must be <= DATE-OF-DEATH 2497 Relational edit between LOCKIN-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LOCK-IN-INFORMATION ELG00009

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.LOCKIN-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.LOCKIN-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 LOCKIN-END-DATE ELG143

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG137,ELG139



1,951 Merged ELG143-0009 RULE-2262 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG143 LOCKIN-END-DATE 2-M
2054
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) LOCK-IN-INFORMATION ELG00009



'if fns.hasValue(@val.LOCKIN-EFF-DATE) && fns.hasValue(@val.LOCKIN-END-DATE), then fns.isLessThanOrEqual(@val.LOCKIN-EFF-DATE, @val.LOCKIN-END-DATE)' LOCKIN-EFF-DATE,LOCKIN-END-DATE ELG142,ELG143











1,952 Logic updated: string matching ELG144-0001 RULE-2270 ELIGIBLE LOCK-IN-INFORMATION-ELG00009 ELG144 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) LOCK-IN-INFORMATION ELG00009



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG144











1,953 Moved to R&C ELG146-0003
ELIGIBLE MFP-INFORMATION-ELG00010 ELG146 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,954 Moved to R&C ELG146-0004
ELIGIBLE MFP-INFORMATION-ELG00010 ELG146 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,955 No logic changes ELG147-0002 RULE-2273 ELIGIBLE MFP-INFORMATION-ELG00010 ELG147 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MFP-INFORMATION ELG00010



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG147











1,956 Logic updated: other ELG147-0003 RULE-2274 ELIGIBLE MFP-INFORMATION-ELG00010 ELG147 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MFP-INFORMATION ELG00010 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG147 SUBMITTING-STATE ELG007









1,957 Retired: Other reasons ELG148-0002
ELIGIBLE MFP-INFORMATION-ELG00010 ELG148 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,958 No logic changes ELG148-0003 RULE-2276 ELIGIBLE MFP-INFORMATION-ELG00010 ELG148 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MFP-INFORMATION ELG00010



Field RECORD-NUMBER should be unique across all records of type MFP-INFORMATION RECORD-NUMBER ELG148











1,959 Retired: MSIS ID checks ELG149-0001
ELIGIBLE MFP-INFORMATION-ELG00010 ELG149 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,960 Retired: MSIS ID checks ELG149-0002
ELIGIBLE MFP-INFORMATION-ELG00010 ELG149 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,961 Merged ELG149-0005 RULE-2279 ELIGIBLE MFP-INFORMATION-ELG00010 ELG149 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [MFP-INFORMATION-ELG00010] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [MFP-INFORMATION-ELG00010] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2210 Edit that MFP-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MFP-INFORMATION ELG00010

record MFP-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG147,ELG149



1,962 No logic changes ELG150-0001 RULE-2280 ELIGIBLE MFP-INFORMATION-ELG00010 ELG150 MFP-LIVES-WITH-FAMILY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MFP-INFORMATION ELG00010



If the field is populated, the value must be contained in the set of valid values with id: MFP-LIVES-WITH-FAMILY MFP-LIVES-WITH-FAMILY ELG150











1,963 No logic changes ELG151-0001 RULE-2281 ELIGIBLE MFP-INFORMATION-ELG00010 ELG151 MFP-QUALIFIED-INSTITUTION 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MFP-INFORMATION ELG00010



If the field is populated, the value must be contained in the set of valid values with id: MFP-QUALIFIED-INSTITUTION MFP-QUALIFIED-INSTITUTION ELG151











1,964 No logic changes ELG152-0001 RULE-2282 ELIGIBLE MFP-INFORMATION-ELG00010 ELG152 MFP-QUALIFIED-RESIDENCE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MFP-INFORMATION ELG00010



If the field is populated, the value must be contained in the set of valid values with id: MFP-QUALIFIED-RESIDENCE MFP-QUALIFIED-RESIDENCE ELG152











1,965 No logic changes ELG153-0001 RULE-2283 ELIGIBLE MFP-INFORMATION-ELG00010 ELG153 MFP-REASON-PARTICIPATION-ENDED 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MFP-INFORMATION ELG00010



If the field is populated, the value must be contained in the set of valid values with id: MFP-REASON-PARTICIPATION-ENDED MFP-REASON-PARTICIPATION-ENDED ELG153











1,966 Logic updated: other ELG153-0002 RULE-2284 ELIGIBLE MFP-INFORMATION-ELG00010 ELG153 MFP-REASON-PARTICIPATION-ENDED 2 If MFP-ENROLLMENT-END-DATE = "99991231", then MFP-REASON-PARTICIPATION-ENDED must be 8-filled 2067 Relational edit between MFP-REASON-PARTICIPATION-ENDED and MFP-ENROLLMENT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MFP-INFORMATION ELG00010



'if fns.isEqual(@val.MFP-ENROLLMENT-END-DATE, "9999-12-31"), then !fns.hasValue(@val.MFP-REASON-PARTICIPATION-ENDED)' MFP-ENROLLMENT-END-DATE,MFP-REASON-PARTICIPATION-ENDED ELG156,ELG153











1,967 No logic changes ELG154-0001 RULE-2285 ELIGIBLE MFP-INFORMATION-ELG00010 ELG154 MFP-REINSTITUTIONALIZED-REASON 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MFP-INFORMATION ELG00010



If the field is populated, the value must be contained in the set of valid values with id: MFP-REINSTITUTIONALIZED-REASON MFP-REINSTITUTIONALIZED-REASON ELG154











1,968 Merged ELG155-0001 RULE-2286 ELIGIBLE MFP-INFORMATION-ELG00010 ELG155 MFP-ENROLLMENT-EFF-DATE 1 If MFP-ENROLLMENT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be a valid date of the form CCYYMMDD MFP-ENROLLMENT-EFF-DATE ELG155











1,969 Merged ELG155-0005 RULE-2286 ELIGIBLE MFP-INFORMATION-ELG00010 ELG155 MFP-ENROLLMENT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be a valid date of the form CCYYMMDD MFP-ENROLLMENT-EFF-DATE ELG155











1,970 Merged ELG155-0006 RULE-2288 ELIGIBLE MFP-INFORMATION-ELG00010 ELG155 MFP-ENROLLMENT-EFF-DATE 2 MFP-ENROLLMENT-EFF-DATE must be <= MFP-ENROLLMENT-END-DATE 2066 Relational edit between MFP-ENROLLMENT-EFF-DATE and MFP-ENROLLMENT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MFP-INFORMATION ELG00010



'if fns.hasValue(@val.MFP-ENROLLMENT-EFF-DATE) && fns.hasValue(@val.MFP-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.MFP-ENROLLMENT-EFF-DATE, @val.MFP-ENROLLMENT-END-DATE)' MFP-ENROLLMENT-EFF-DATE,MFP-ENROLLMENT-END-DATE ELG155,ELG156











1,971 No logic changes ELG155-0007 RULE-2289 ELIGIBLE MFP-INFORMATION-ELG00010 ELG155 MFP-ENROLLMENT-EFF-DATE 2 If two or more MFP-INFORMATION record segments have the same SUBMITTING-STATE and MSIS-IDENTIFICATION-NUM
then for each pair of record segments,
(Segment 1 MFP-ENROLLMENT-EFF-DATE must <> Segment 2 MFP-ENROLLMENT-EFF-DATE)
AND
( (If Segment 1 MFP-ENROLLMENT-EFF-DATE < Segment 2 MFP-ENROLLMENT-EFF-DATE,
then
Segment 1 MFP-ENROLLMENT-END-DATE must be < Segment 2 MFP-ENROLLMENT-EFF-DATE)
OR
(If Segment 2 MFP-ENROLLMENT-EFF-DATE < Segment 1 MFP-ENROLLMENT-EFF-DATE,
then
Segment 2 MFP-ENROLLMENT-END-DATE must be < Segment 1 MFP-ENROLLMENT-EFF-DATE) )		 2166 Edit for overlapping coverage dates in record segments that have non-unique key fields in MFP-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MFP-INFORMATION ELG00010



Records with the same primary keys must have non-overlapping date ranges. Effective date field: MFP-ENROLLMENT-EFF-DATE. End date field: MFP-ENROLLMENT-END-DATE MFP-ENROLLMENT-EFF-DATE,MFP-ENROLLMENT-END-DATE ELG155,ELG156











1,972 Merged ELG155-0008 RULE-2279 ELIGIBLE MFP-INFORMATION-ELG00010 ELG155 MFP-ENROLLMENT-EFF-DATE 2 ( MFP-ENROLLMENT-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MFP-INFORMATION-ELG00010] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MFP-INFORMATION-ELG00010] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( MFP-ENROLLMENT-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MFP-INFORMATION-ELG00010] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MFP-INFORMATION-ELG00010] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2513 Relational edit between MFP-ENROLLMENT-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MFP-INFORMATION ELG00010

record MFP-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG147,ELG149



1,973 Merged ELG156-0001 RULE-2291 ELIGIBLE MFP-INFORMATION-ELG00010 ELG156 MFP-ENROLLMENT-END-DATE 1 If MFP-ENROLLMENT-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be a valid date of the form CCYYMMDD MFP-ENROLLMENT-END-DATE ELG156











1,974 Merged ELG156-0005 RULE-2291 ELIGIBLE MFP-INFORMATION-ELG00010 ELG156 MFP-ENROLLMENT-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be a valid date of the form CCYYMMDD MFP-ENROLLMENT-END-DATE ELG156











1,975 Merged ELG156-0007 RULE-2279 ELIGIBLE MFP-INFORMATION-ELG00010 ELG156 MFP-ENROLLMENT-END-DATE 2 ( MFP-ENROLLMENT-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MFP-INFORMATION-ELG00010] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MFP-INFORMATION-ELG00010] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( MFP-ENROLLMENT-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MFP-INFORMATION-ELG00010] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MFP-INFORMATION-ELG00010] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2516 Relational edit between MFP-ENROLLMENT-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MFP-INFORMATION ELG00010

record MFP-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG147,ELG149



1,976 No logic changes ELG156-0008 RULE-2294 ELIGIBLE MFP-INFORMATION-ELG00010 ELG156 MFP-ENROLLMENT-END-DATE 2 If RESTRICTED-BENEFITS-CODE = "D", then MFP-ENROLLMENT-END-DATE must not be < ELIGIBILITY-DETERMINANT-EFF-DATE 2515 Relational edit between MFP-ENROLLMENT-END-DATE, ELIGIBILTIY-DETERMINANT-EFF-DATE, and RESTRICTED-BENEFITS-CODE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 MFP-INFORMATION ELG00010

'if fns.isEqual(@primaryRecord.RESTRICTED-BENEFITS-CODE, "D"), then fns.isGreaterThan(@secondaryRecord.MFP-ENROLLMENT-END-DATE, @primaryRecord.ELIGIBILITY-DETERMINANT-EFF-DATE)' RESTRICTED-BENEFITS-CODE,ELIGIBILITY-DETERMINANT-EFF-DATE ELG097,ELG099 MFP-ENROLLMENT-END-DATE ELG156

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG147,ELG149



1,977 Logic updated: other ELG156-0009 RULE-2295 ELIGIBLE MFP-INFORMATION-ELG00010 ELG156 MFP-ENROLLMENT-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then MFP-ENROLLMENT-END-DATE must be <= DATE-OF-DEATH 2514 Relational edit between MFP-ENROLLMENT-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MFP-INFORMATION ELG00010

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.MFP-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.MFP-ENROLLMENT-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 MFP-ENROLLMENT-END-DATE ELG156

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG147,ELG149



1,978 Merged ELG156-0010 RULE-2288 ELIGIBLE MFP-INFORMATION-ELG00010 ELG156 MFP-ENROLLMENT-END-DATE 2-M
2066
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MFP-INFORMATION ELG00010



'if fns.hasValue(@val.MFP-ENROLLMENT-EFF-DATE) && fns.hasValue(@val.MFP-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.MFP-ENROLLMENT-EFF-DATE, @val.MFP-ENROLLMENT-END-DATE)' MFP-ENROLLMENT-EFF-DATE,MFP-ENROLLMENT-END-DATE ELG155,ELG156











1,979 Logic updated: string matching ELG157-0001 RULE-2297 ELIGIBLE MFP-INFORMATION-ELG00010 ELG157 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MFP-INFORMATION ELG00010



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG157











1,980 Moved to R&C ELG159-0003
ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG159 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























1,981 Moved to R&C ELG159-0004
ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG159 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























1,982 No logic changes ELG160-0002 RULE-2300 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG160 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value STATE-PLAN-OPTION-PARTICIPATION ELG00011



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG160











1,983 Logic updated: other ELG160-0003 RULE-2301 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG160 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) STATE-PLAN-OPTION-PARTICIPATION ELG00011 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG160 SUBMITTING-STATE ELG007









1,984 Retired: Other reasons ELG161-0002
ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG161 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























1,985 No logic changes ELG161-0003 RULE-2303 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG161 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) STATE-PLAN-OPTION-PARTICIPATION ELG00011



Field RECORD-NUMBER should be unique across all records of type STATE-PLAN-OPTION-PARTICIPATION RECORD-NUMBER ELG161











1,986 Retired: MSIS ID checks ELG162-0001
ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG162 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























1,987 Retired: MSIS ID checks ELG162-0002
ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG162 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























1,988 Merged ELG162-0005 RULE-2306 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG162 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2221 Edit that STATE-PLAN-OPTION-PARTICIPATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 STATE-PLAN-OPTION-PARTICIPATION ELG00011

record STATE-PLAN-OPTION-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG160,ELG162



1,989 No logic changes ELG163-0001 RULE-2307 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG163 STATE-PLAN-OPTION-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value STATE-PLAN-OPTION-PARTICIPATION ELG00011



If the field is populated, the value must be contained in the set of valid values with id: STATE-PLAN-OPTION-TYPE STATE-PLAN-OPTION-TYPE ELG163











1,990 No logic changes ELG163-0002 RULE-2308 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG163 STATE-PLAN-OPTION-TYPE 2 If MAINTENANCE-ASSISTANCE-STATUS = "0" and MEDICAID-BASIS-OF-ELIGIBILITY = "0", then STATE-PLAN-OPTION-TYPE must = "00" 2138 Relational edit between STATE-PLAN-OPTION-TYPE, MAINTENANCE-ASSISTANCE-STATUS, and MEDICAID-BASIS-OF-ELIGIBILITY failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ELIGIBILITY-DETERMINANTS ELG00005 STATE-PLAN-OPTION-PARTICIPATION ELG00011

'if fns.isEqual(@primaryRecord.MAINTENANCE-ASSISTANCE-STATUS, "0") && fns.isEqual(@primaryRecord.MEDICAID-BASIS-OF-ELIGIBILITY, "00"), then fns.isEqual(@secondaryRecord.STATE-PLAN-OPTION-TYPE, "00")' MAINTENANCE-ASSISTANCE-STATUS,MEDICAID-BASIS-OF-ELIGIBILITY ELG096,ELG084 STATE-PLAN-OPTION-TYPE ELG163

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG080,ELG082 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG160,ELG162



1,991 Merged ELG164-0001 RULE-2309 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG164 STATE-PLAN-OPTION-EFF-DATE 1 If STATE-PLAN-OPTION-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be a valid date of the form CCYYMMDD STATE-PLAN-OPTION-EFF-DATE ELG164











1,992 Merged ELG164-0005 RULE-2309 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG164 STATE-PLAN-OPTION-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be a valid date of the form CCYYMMDD STATE-PLAN-OPTION-EFF-DATE ELG164











1,993 Merged ELG164-0006 RULE-2311 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG164 STATE-PLAN-OPTION-EFF-DATE 2 STATE-PLAN-OPTION-EFF-DATE must be <= STATE-PLAN-OPTION-END-DATE 2123 Relational edit between STATE-PLAN-OPTION-EFF-DATE and STATE-PLAN-OPTION-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) STATE-PLAN-OPTION-PARTICIPATION ELG00011



'if fns.hasValue(@val.STATE-PLAN-OPTION-EFF-DATE) && fns.hasValue(@val.STATE-PLAN-OPTION-END-DATE), then fns.isLessThanOrEqual(@val.STATE-PLAN-OPTION-EFF-DATE, @val.STATE-PLAN-OPTION-END-DATE)' STATE-PLAN-OPTION-EFF-DATE,STATE-PLAN-OPTION-END-DATE ELG164,ELG165











1,994 Retired: Other reasons ELG164-0007
ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG164 STATE-PLAN-OPTION-EFF-DATE 2 If MAINTENANCE-ASSISTANCE-STATUS = "0" and MEDICAID-BASIS-OF-ELIGIBILITY = "0", then STATE-PLAN-OPTION-EFF-DATE must be 8-filled 2137 Relational edit between STATE-PLAN-OPTION-EFF-DATE, MAINTENANCE-ASSISTANCE-STATUS, and MEDICAID-BASIS-OF-ELIGIBILITY failed

























1,995 No logic changes ELG164-0008 RULE-2313 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG164 STATE-PLAN-OPTION-EFF-DATE 2 If two or more STATE-PLAN-OPTION-PARTICIPATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and STATE-PLAN-OPTION-TYPE,
then for each pair of record segments,
(Segment 1 STATE-PLAN-OPTION-EFF-DATE must <> Segment 2 STATE-PLAN-OPTION-EFF-DATE)
AND
( (If Segment 1 STATE-PLAN-OPTION-EFF-DATE < Segment 2 STATE-PLAN-OPTION-EFF-DATE,
then
Segment 1 STATE-PLAN-OPTION-END-DATE must be < Segment 2 STATE-PLAN-OPTION-EFF-DATE)
OR
(If Segment 2 STATE-PLAN-OPTION-EFF-DATE < Segment 1 STATE-PLAN-OPTION-EFF-DATE,
then
Segment 2 STATE-PLAN-OPTION-END-DATE must be < Segment 1 STATE-PLAN-OPTION-EFF-DATE) )		 2179 Edit for overlapping coverage dates in record segments that have non-unique key fields in STATE-PLAN-OPTION-PARTICIPATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) STATE-PLAN-OPTION-PARTICIPATION ELG00011



Records with the same primary keys must have non-overlapping date ranges. Effective date field: STATE-PLAN-OPTION-EFF-DATE. End date field: STATE-PLAN-OPTION-END-DATE STATE-PLAN-OPTION-EFF-DATE,STATE-PLAN-OPTION-END-DATE ELG164,ELG165











1,996 Merged ELG164-0009 RULE-2306 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG164 STATE-PLAN-OPTION-EFF-DATE 2 ( STATE-PLAN-OPTION-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( STATE-PLAN-OPTION-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2537 Relational edit between STATE-PLAN-OPTION-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 STATE-PLAN-OPTION-PARTICIPATION ELG00011

record STATE-PLAN-OPTION-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG160,ELG162



1,997 Merged ELG165-0001 RULE-2315 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG165 STATE-PLAN-OPTION-END-DATE 1 If STATE-PLAN-OPTION-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be a valid date of the form CCYYMMDD STATE-PLAN-OPTION-END-DATE ELG165











1,998 Merged ELG165-0005 RULE-2315 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG165 STATE-PLAN-OPTION-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be a valid date of the form CCYYMMDD STATE-PLAN-OPTION-END-DATE ELG165











1,999 Merged ELG165-0007 RULE-2306 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG165 STATE-PLAN-OPTION-END-DATE 2 ( STATE-PLAN-OPTION-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( STATE-PLAN-OPTION-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [STATE-PLAN-OPTION-PARTICIPATION-ELG00011] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2539 Relational edit between STATE-PLAN-OPTION-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 STATE-PLAN-OPTION-PARTICIPATION ELG00011

record STATE-PLAN-OPTION-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG160,ELG162



2,000 Logic updated: other ELG165-0008 RULE-2318 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG165 STATE-PLAN-OPTION-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then STATE-PLAN-OPTION-END-DATE must be <= DATE-OF-DEATH 2538 Relational edit between STATE-PLAN-OPTION-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 STATE-PLAN-OPTION-PARTICIPATION ELG00011

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.STATE-PLAN-OPTION-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.STATE-PLAN-OPTION-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 STATE-PLAN-OPTION-END-DATE ELG165

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG160,ELG162



2,001 Merged ELG165-0009 RULE-2311 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG165 STATE-PLAN-OPTION-END-DATE 2-M
2123
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) STATE-PLAN-OPTION-PARTICIPATION ELG00011



'if fns.hasValue(@val.STATE-PLAN-OPTION-EFF-DATE) && fns.hasValue(@val.STATE-PLAN-OPTION-END-DATE), then fns.isLessThanOrEqual(@val.STATE-PLAN-OPTION-EFF-DATE, @val.STATE-PLAN-OPTION-END-DATE)' STATE-PLAN-OPTION-EFF-DATE,STATE-PLAN-OPTION-END-DATE ELG164,ELG165











2,002 Logic updated: string matching ELG166-0001 RULE-2320 ELIGIBLE STATE-PLAN-OPTION-PARTICIPATION-ELG00011 ELG166 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) STATE-PLAN-OPTION-PARTICIPATION ELG00011



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG166











2,003 Moved to R&C ELG168-0003
ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG168 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,004 Moved to R&C ELG168-0004
ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG168 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,005 No logic changes ELG169-0002 RULE-2323 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG169 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value WAIVER-PARTICIPATION ELG00012



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG169











2,006 Logic updated: other ELG169-0003 RULE-2324 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG169 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) WAIVER-PARTICIPATION ELG00012 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG169 SUBMITTING-STATE ELG007









2,007 Retired: Other reasons ELG170-0002
ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG170 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,008 No logic changes ELG170-0005 RULE-2326 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG170 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) WAIVER-PARTICIPATION ELG00012



Field RECORD-NUMBER should be unique across all records of type WAIVER-PARTICIPATION RECORD-NUMBER ELG170











2,009 Retired: MSIS ID checks ELG171-0001
ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG171 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,010 Retired: MSIS ID checks ELG171-0002
ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG171 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,011 Merged ELG171-0005 RULE-2329 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG171 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [WAIVER-PARTICIPATION-ELG00012] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [WAIVER-PARTICIPATION-ELG00012] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2227 Edit that WAIVER-PARTICIPATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 WAIVER-PARTICIPATION ELG00012

record WAIVER-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG169,ELG171



2,012 Merged ELG172-0002 RULE-2330 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG172 WAIVER-ID 1 Value is not included a state supplied valid code list 125 Value is not included in a state supplied valid code list 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value WAIVER-PARTICIPATION ELG00012



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID ELG172











2,013 Merged ELG172-0003 RULE-2331 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG172 WAIVER-ID 2 If WAIVER-TYPE is not 8-filled, then WAIVER-ID must not be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) WAIVER-PARTICIPATION ELG00012



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID ELG173,ELG172











2,014 Merged ELG172-0004 RULE-2330 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG172 WAIVER-ID 3 WAIVER-ID must = waiver ID in state-provided crosswalk 3030 Edit with an external reference (state provided WAIVER-ID-/WAIVER-TYPE crosswalk) failed 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value WAIVER-PARTICIPATION ELG00012



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID ELG172











2,015 Merged ELG172-0005 RULE-2331 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG172 WAIVER-ID 2 If WAIVER-TYPE is 8-filled, then WAIVER-ID must be 8-filled 2441 Relational edit between WAIVER-ID and WAIVER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) WAIVER-PARTICIPATION ELG00012



'if and only if fns.hasValue(@val.WAIVER-TYPE), then fns.hasValue(@val.WAIVER-ID)' WAIVER-TYPE,WAIVER-ID ELG173,ELG172











2,016 No logic changes ELG173-0002 RULE-2334 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG173 WAIVER-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value WAIVER-PARTICIPATION ELG00012



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-TYPE WAIVER-TYPE ELG173











2,017 Merged ELG174-0001 RULE-2335 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG174 WAIVER-ENROLLMENT-EFF-DATE 1 If WAIVER-ENROLLMENT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be a valid date of the form CCYYMMDD WAIVER-ENROLLMENT-EFF-DATE ELG174











2,018 Merged ELG174-0005 RULE-2335 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG174 WAIVER-ENROLLMENT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be a valid date of the form CCYYMMDD WAIVER-ENROLLMENT-EFF-DATE ELG174











2,019 Merged ELG174-0006 RULE-2337 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG174 WAIVER-ENROLLMENT-EFF-DATE 2 WAIVER-ENROLLMENT-EFF-DATE must be <= WAIVER-ENROLLMENT-END-DATE 2130 Relational edit between WAIVER-ENROLLMENT-EFF-DATE and WAIVER-ENROLLMENT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) WAIVER-PARTICIPATION ELG00012



'if fns.hasValue(@val.WAIVER-ENROLLMENT-EFF-DATE) && fns.hasValue(@val.WAIVER-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.WAIVER-ENROLLMENT-EFF-DATE, @val.WAIVER-ENROLLMENT-END-DATE)' WAIVER-ENROLLMENT-EFF-DATE,WAIVER-ENROLLMENT-END-DATE ELG174,ELG175











2,020 No logic changes ELG174-0007 RULE-2338 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG174 WAIVER-ENROLLMENT-EFF-DATE 2 If two or more WAIVER-PARTICIPATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and WAIVER-ID,
then for each pair of record segments,
(Segment 1 WAIVER-ENROLLMENT-EFF-DATE must <> Segment 2 WAIVER-ENROLLMENT-EFF-DATE)
AND
( (If Segment 1 WAIVER-ENROLLMENT-EFF-DATE < Segment 2 WAIVER-ENROLLMENT-EFF-DATE,
then
Segment 1 WAIVER-ENROLLMENT-END-DATE must be < Segment 2 WAIVER-ENROLLMENT-EFF-DATE)
OR
(If Segment 2 WAIVER-ENROLLMENT-EFF-DATE < Segment 1 WAIVER-ENROLLMENT-EFF-DATE,
then
Segment 2 WAIVER-ENROLLMENT-END-DATE must be < Segment 1 WAIVER-ENROLLMENT-EFF-DATE) )		 2186 Edit for overlapping coverage dates in record segments that have non-unique key fields in WAIVER-PARTICIPATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) WAIVER-PARTICIPATION ELG00012



Records with the same primary keys must have non-overlapping date ranges. Effective date field: WAIVER-ENROLLMENT-EFF-DATE. End date field: WAIVER-ENROLLMENT-END-DATE WAIVER-ENROLLMENT-EFF-DATE,WAIVER-ENROLLMENT-END-DATE ELG174,ELG175











2,021 Merged ELG174-0008 RULE-2329 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG174 WAIVER-ENROLLMENT-EFF-DATE 2 ( WAIVER-ENROLLMENT-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [WAIVER-PARTICIPATION-ELG00012] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [WAIVER-PARTICIPATION-ELG00012] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( WAIVER-ENROLLMENT-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [WAIVER-PARTICIPATION-ELG00012] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [WAIVER-PARTICIPATION-ELG00012] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2542 Relational edit between WAIVER-ENROLLMENT-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 WAIVER-PARTICIPATION ELG00012

record WAIVER-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG169,ELG171



2,022 Merged ELG175-0001 RULE-2340 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG175 WAIVER-ENROLLMENT-END-DATE 1 If WAIVER-ENROLLMENT-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be a valid date of the form CCYYMMDD WAIVER-ENROLLMENT-END-DATE ELG175











2,023 Merged ELG175-0005 RULE-2340 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG175 WAIVER-ENROLLMENT-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be a valid date of the form CCYYMMDD WAIVER-ENROLLMENT-END-DATE ELG175











2,024 Merged ELG175-0007 RULE-2329 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG175 WAIVER-ENROLLMENT-END-DATE 2 ( WAIVER-ENROLLMENT-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [WAIVER-PARTICIPATION-ELG00012] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [WAIVER-PARTICIPATION-ELG00012] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( WAIVER-ENROLLMENT-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [WAIVER-PARTICIPATION-ELG00012] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [WAIVER-PARTICIPATION-ELG00012] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2544 Relational edit between WAIVER-ENROLLMENT-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 WAIVER-PARTICIPATION ELG00012

record WAIVER-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG169,ELG171



2,025 Logic updated: other ELG175-0008 RULE-2343 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG175 WAIVER-ENROLLMENT-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then WAIVER-ENROLLMENT-END-DATE must be <= DATE-OF-DEATH 2543 Relational edit between WAIVER-ENROLLMENT-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 WAIVER-PARTICIPATION ELG00012

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.WAIVER-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.WAIVER-ENROLLMENT-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 WAIVER-ENROLLMENT-END-DATE ELG175

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG169,ELG171



2,026 Merged ELG175-0009 RULE-2337 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG175 WAIVER-ENROLLMENT-END-DATE 2-M
2130
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) WAIVER-PARTICIPATION ELG00012



'if fns.hasValue(@val.WAIVER-ENROLLMENT-EFF-DATE) && fns.hasValue(@val.WAIVER-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.WAIVER-ENROLLMENT-EFF-DATE, @val.WAIVER-ENROLLMENT-END-DATE)' WAIVER-ENROLLMENT-EFF-DATE,WAIVER-ENROLLMENT-END-DATE ELG174,ELG175











2,027 Logic updated: string matching ELG176-0001 RULE-2345 ELIGIBLE WAIVER-PARTICIPATION-ELG00012 ELG176 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) WAIVER-PARTICIPATION ELG00012



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG176











2,028 Moved to R&C ELG178-0003
ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG178 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,029 Moved to R&C ELG178-0004
ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG178 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,030 No logic changes ELG179-0002 RULE-2348 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG179 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value LTSS-PARTICIPATION ELG00013



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG179











2,031 Logic updated: other ELG179-0003 RULE-2349 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG179 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) LTSS-PARTICIPATION ELG00013 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG179 SUBMITTING-STATE ELG007









2,032 Retired: Other reasons ELG180-0002
ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG180 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,033 No logic changes ELG180-0003 RULE-2351 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG180 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) LTSS-PARTICIPATION ELG00013



Field RECORD-NUMBER should be unique across all records of type LTSS-PARTICIPATION RECORD-NUMBER ELG180











2,034 Retired: MSIS ID checks ELG181-0001
ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG181 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,035 Retired: MSIS ID checks ELG181-0002
ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG181 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,036 Merged ELG181-0005 RULE-2354 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG181 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [LTSS-PARTICIPATION-ELG00013] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [LTSS-PARTICIPATION-ELG00013] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2203 Edit that LTSS-PARTICIPATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LTSS-PARTICIPATION ELG00013

record LTSS-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG179,ELG181



2,037 No logic changes ELG182-0001 RULE-2355 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG182 LTSS-LEVEL-CARE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value LTSS-PARTICIPATION ELG00013



If the field is populated, the value must be contained in the set of valid values with id: LTSS-LEVEL-CARE LTSS-LEVEL-CARE ELG182











2,038 Retired: Other reasons ELG183-0001
ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG183 LTSS-PROV-NUM 1 Value is not included a state supplied valid code list 125 Value is not included in a state supplied valid code list

























2,039 Logic updated: other ELG183-0002 RULE-2357 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG183 LTSS-PROV-NUM 3 LTSS-PROV-NUM must = any PROV-IDENTIFIER [PROVIDER] if SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 3022 A PROVIDER record for the LTSS-PROV-NUM is missing 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 LTSS-PARTICIPATION ELG00013

For every record of type LTSS-PARTICIPATION, there must be a valid record of type PROV-IDENTIFIERS that matches on the join keys





SUBMITTING-STATE,PROV-IDENTIFIER PRV073,PRV081 SUBMITTING-STATE,LTSS-PROV-NUM ELG179,ELG183



2,040 Merged ELG184-0001 RULE-2358 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG184 LTSS-ELIGIBILITY-EFF-DATE 1 If LTSS-ELIGIBILITY-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be a valid date of the form CCYYMMDD LTSS-ELIGIBILITY-EFF-DATE ELG184











2,041 Merged ELG184-0005 RULE-2358 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG184 LTSS-ELIGIBILITY-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be a valid date of the form CCYYMMDD LTSS-ELIGIBILITY-EFF-DATE ELG184











2,042 Merged ELG184-0006 RULE-2360 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG184 LTSS-ELIGIBILITY-EFF-DATE 2 LTSS-ELIGIBILITY-EFF-DATE must be <= LTSS-ELIGIBILITY-END-DATE 2055 Relational edit between LTSS-ELIGIBILITY-EFF-DATE and LTSS-ELIGIBILITY-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) LTSS-PARTICIPATION ELG00013



'if fns.hasValue(@val.LTSS-ELIGIBILITY-EFF-DATE) && fns.hasValue(@val.LTSS-ELIGIBILITY-END-DATE), then fns.isLessThanOrEqual(@val.LTSS-ELIGIBILITY-EFF-DATE, @val.LTSS-ELIGIBILITY-END-DATE)' LTSS-ELIGIBILITY-EFF-DATE,LTSS-ELIGIBILITY-END-DATE ELG184,ELG185











2,043 No logic changes ELG184-0007 RULE-2361 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG184 LTSS-ELIGIBILITY-EFF-DATE 2 If two or more LTSS-PARTICIPATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, LTSS-LEVEL-CARE, and LTSS-PROV-NUM,
then for each pair of record segments,
(Segment 1 LTSS-ELIGIBILITY-EFF-DATE must <> Segment 2 LTSS-ELIGIBILITY-EFF-DATE)
AND
( (If Segment 1 LTSS-ELIGIBILITY-EFF-DATE < Segment 2 LTSS-ELIGIBILITY-EFF-DATE,
then
Segment 1 LTSS-ELIGIBILITY-END-DATE must be < Segment 2 LTSS-ELIGIBILITY-EFF-DATE)
OR
(If Segment 2 LTSS-ELIGIBILITY-EFF-DATE < Segment 1 LTSS-ELIGIBILITY-EFF-DATE,
then
Segment 2 LTSS-ELIGIBILITY-END-DATE must be < Segment 1 LTSS-ELIGIBILITY-EFF-DATE) )		 2158 Edit for overlapping coverage dates in record segments that have non-unique key fields in LTSS-PARTICIPATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) LTSS-PARTICIPATION ELG00013



Records with the same primary keys must have non-overlapping date ranges. Effective date field: LTSS-ELIGIBILITY-EFF-DATE. End date field: LTSS-ELIGIBILITY-END-DATE LTSS-ELIGIBILITY-EFF-DATE,LTSS-ELIGIBILITY-END-DATE ELG184,ELG185











2,044 Merged ELG184-0008 RULE-2354 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG184 LTSS-ELIGIBILITY-EFF-DATE 2 ( LTSS-ELIGIBILITY-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LTSS-PARTICIPATION-ELG00013] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LTSS-PARTICIPATION-ELG00013] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( LTSS-ELIGIBILITY-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LTSS-PARTICIPATION-ELG00013] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LTSS-PARTICIPATION-ELG00013] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2499 Relational edit between LTSS-ELIGIBILITY-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LTSS-PARTICIPATION ELG00013

record LTSS-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG179,ELG181



2,045 Merged ELG185-0001 RULE-2363 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG185 LTSS-ELIGIBILITY-END-DATE 1 If LTSS-ELIGIBILITY-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be a valid date of the form CCYYMMDD LTSS-ELIGIBILITY-END-DATE ELG185











2,046 Merged ELG185-0005 RULE-2363 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG185 LTSS-ELIGIBILITY-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be a valid date of the form CCYYMMDD LTSS-ELIGIBILITY-END-DATE ELG185











2,047 Merged ELG185-0007 RULE-2354 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG185 LTSS-ELIGIBILITY-END-DATE 2 ( LTSS-ELIGIBILITY-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LTSS-PARTICIPATION-ELG00013] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LTSS-PARTICIPATION-ELG00013] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( LTSS-ELIGIBILITY-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [LTSS-PARTICIPATION-ELG00013] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [LTSS-PARTICIPATION-ELG00013] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2501 Relational edit between LTSS-ELIGIBILITY-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LTSS-PARTICIPATION ELG00013

record LTSS-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG179,ELG181



2,048 Logic updated: other ELG185-0008 RULE-2366 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG185 LTSS-ELIGIBILITY-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then LTSS-ELIGIBILITY-END-DATE must be <= DATE-OF-DEATH 2500 Relational edit between LTSS-ELIGIBILITY-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 LTSS-PARTICIPATION ELG00013

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.LTSS-ELIGIBILITY-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.LTSS-ELIGIBILITY-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 LTSS-ELIGIBILITY-END-DATE ELG185

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG179,ELG181



2,049 Merged ELG185-0009 RULE-2360 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG185 LTSS-ELIGIBILITY-END-DATE 2-M
2055
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) LTSS-PARTICIPATION ELG00013



'if fns.hasValue(@val.LTSS-ELIGIBILITY-EFF-DATE) && fns.hasValue(@val.LTSS-ELIGIBILITY-END-DATE), then fns.isLessThanOrEqual(@val.LTSS-ELIGIBILITY-EFF-DATE, @val.LTSS-ELIGIBILITY-END-DATE)' LTSS-ELIGIBILITY-EFF-DATE,LTSS-ELIGIBILITY-END-DATE ELG184,ELG185











2,050 Logic updated: string matching ELG186-0001 RULE-2368 ELIGIBLE LTSS-PARTICIPATION-ELG00013 ELG186 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) LTSS-PARTICIPATION ELG00013



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG186











2,051 Moved to R&C ELG188-0003
ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG188 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,052 Moved to R&C ELG188-0004
ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG188 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,053 No logic changes ELG189-0002 RULE-2371 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG189 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-PARTICIPATION ELG00014



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG189











2,054 Logic updated: other ELG189-0003 RULE-2372 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG189 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-PARTICIPATION ELG00014 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG189 SUBMITTING-STATE ELG007









2,055 Retired: Other reasons ELG190-0002
ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG190 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,056 No logic changes ELG190-0003 RULE-2374 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG190 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MANAGED-CARE-PARTICIPATION ELG00014



Field RECORD-NUMBER should be unique across all records of type MANAGED-CARE-PARTICIPATION RECORD-NUMBER ELG190











2,057 Retired: MSIS ID checks ELG191-0001
ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG191 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,058 Retired: MSIS ID checks ELG191-0002
ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG191 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,059 Merged ELG191-0005 RULE-2377 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG191 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2207 Edit that MANAGED-CARE-PARTICIPATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MANAGED-CARE-PARTICIPATION ELG00014

record MANAGED-CARE-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG189,ELG191



2,060 Retired: required value checks ELG192-0001
ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG192 MANAGED-CARE-PLAN-ID 1 If MANAGED-CARE-PLAN-ID = spaces 113 Required data element has not been reported.

























2,061 Logic updated: string matching ELG192-0002 RULE-2379 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG192 MANAGED-CARE-PLAN-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - MANAGED-CARE-PLAN-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-PARTICIPATION ELG00014



'if fns.hasValue(@val.MANAGED-CARE-PLAN-ID), then fns.matches(@val.MANAGED-CARE-PLAN-ID, "^[^|*]*$")' MANAGED-CARE-PLAN-ID ELG192











2,062 No logic changes ELG192-0004 RULE-2380 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG192 MANAGED-CARE-PLAN-ID 2 If MANAGED-CARE-PLAN-ID be 8-filled, then MANAGED-CARE-PLAN-TYPE must be 8-filled 2061 Relational edit between MANAGED-CARE-PLAN-ID and MANAGED-CARE-PLAN-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-PARTICIPATION ELG00014



'if !fns.hasValue(@val.MANAGED-CARE-PLAN-ID), then !fns.hasValue(@val.ENROLLED-MANAGED-CARE-PLAN-TYPE)' MANAGED-CARE-PLAN-ID,ENROLLED-MANAGED-CARE-PLAN-TYPE ELG192,ELG193











2,063 No logic changes ELG192-0005 RULE-6564 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG192 MANAGED-CARE-PLAN-ID 3 MANAGED-CARE-PLAN-ID must = managed care plan ID in state-provided crosswalk 3030 Edit with an external reference failed 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(12) MANAGED-CARE-PLAN-ID ELG192











2,064 Logic updated: other ELG192-0006 RULE-2382 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG192 MANAGED-CARE-PLAN-ID 3 MANAGED-CARE-PLAN-ID must = any STATE-PLAN-ID [MANAGED-CARE-MAIN-MCR00002] if SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 3018 A MNGDCARE record for the MANAGED-CARE-PLAN-ID is missing 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-PARTICIPATION ELG00014

For every record of type MANAGED-CARE-PARTICIPATION, there must be a valid record of type MANAGED-CARE-MAIN that matches on the join keys





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,MANAGED-CARE-PLAN-ID ELG189,ELG192



2,065 Merged ELG193-0002 RULE-2385 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG193 MANAGED-CARE-PLAN-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-PARTICIPATION ELG00014



If the field is populated, the value must be contained in the set of valid values with id: MANAGED-CARE-PLAN-TYPE ENROLLED-MANAGED-CARE-PLAN-TYPE ELG193











2,066 Logic updated: other ELG193-0003 RULE-2384 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG193 MANAGED-CARE-PLAN-TYPE 3 MANAGED-CARE-PLAN-TYPE must = MANAGED-CARE-PLAN-TYPE [MANAGED-CARE-MAIN-MCR00002] where SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] ] and MANAGED-CARE-PLAN -ID [MANAGED-CARE-PARTICIPATION-ELG00014] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] 3056 A MANAGED CARE record for the MANAGED-CARE-PLAN-TYPE does not correspond to a state managed care plan ID 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-PARTICIPATION ELG00014

'if fns.hasValue(@secondaryRecord.ENROLLED-MANAGED-CARE-PLAN-TYPE) && fns.hasValue(@primaryRecord.MANAGED-CARE-PLAN-TYPE), then fns.isEqual(@secondaryRecord.ENROLLED-MANAGED-CARE-PLAN-TYPE, @primaryRecord.MANAGED-CARE-PLAN-TYPE)' MANAGED-CARE-PLAN-TYPE MCR024 ENROLLED-MANAGED-CARE-PLAN-TYPE ELG193

SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,MANAGED-CARE-PLAN-ID ELG189,ELG192



2,067 Merged ELG193-0005 RULE-2385 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG193 MANAGED-CARE-PLAN-TYPE 1 Value is not included a state supplied valid code list 125 Value is not included in a state supplied valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-PARTICIPATION ELG00014



If the field is populated, the value must be contained in the set of valid values with id: MANAGED-CARE-PLAN-TYPE ENROLLED-MANAGED-CARE-PLAN-TYPE ELG193











2,068 Logic updated: string matching ELG194-0003 RULE-2386 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG194 NATIONAL-HEALTH-CARE-ENTITY-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-PARTICIPATION ELG00014



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-ID, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-ID ELG194











2,069 No logic changes ELG194-0005 RULE-2387 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG194 NATIONAL-HEALTH-CARE-ENTITY-ID 2 If MANAGED-CARE-PLAN-TYPE is not 8-filled AND START-OF-TIME-PERIOD >= 20151105, then NATIONAL-HEALTH-CARE-ENTITY-ID must not be 8-filled 2333 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID, START-OF-TIME-PERIOD, and MANAGED-CARE-PLAN-TYPE failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-PARTICIPATION ELG00014 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.isGreaterThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, "2015-11-05") && fns.hasValue(@val.ENROLLED-MANAGED-CARE-PLAN-TYPE), then fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID)' ENROLLED-MANAGED-CARE-PLAN-TYPE,NATIONAL-HEALTH-CARE-ENTITY-ID ELG193,ELG194 START-OF-TIME-PERIOD ELG009









2,070 No logic changes ELG195-0003 RULE-2388 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG195 NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-PARTICIPATION ELG00014



If the field is populated, the value must be contained in the set of valid values with id: NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE ELG195











2,071 Merged ELG196-0001 RULE-2389 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG196 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE 1 If MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE ELG196











2,072 Merged ELG196-0002 RULE-2389 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG196 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE ELG196











2,073 Merged ELG196-0005 RULE-2391 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG196 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE 2 MANAGED-CARE-ENROLLMENT-EFF-DATE must be <= MANAGED-CARE-ENROLLMENT-END-DATE 2060 Relational edit between MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE and MANAGED-CARE-PLAN-ENROLLMENT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-PARTICIPATION ELG00014



'if fns.hasValue(@val.MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-PLAN-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE, @val.MANAGED-CARE-PLAN-ENROLLMENT-END-DATE)' MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE,MANAGED-CARE-PLAN-ENROLLMENT-END-DATE ELG196,ELG197











2,074 No logic changes ELG196-0006 RULE-2392 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG196 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE 2 If two or more MANAGED-CARE-PARTICIPATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and MANAGED-CARE-PLAN-ID,
then for each pair of record segments,
(Segment 1 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE must <> Segment 2 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE)
AND
( (If Segment 1 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE < Segment 2 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE,
then
Segment 1 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE must be < Segment 2 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE)
OR
(If Segment 2 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE < Segment 1 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE,
then
Segment 2 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE must be < Segment 1 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE) )		 2163 Edit for overlapping coverage dates in record segments that have non-unique key fields in MANAGED-CARE-PARTICIPATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MANAGED-CARE-PARTICIPATION ELG00014



Records with the same primary keys must have non-overlapping date ranges. Effective date field: MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE. End date field: MANAGED-CARE-PLAN-ENROLLMENT-END-DATE MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE,MANAGED-CARE-PLAN-ENROLLMENT-END-DATE ELG196,ELG197











2,075 Merged ELG196-0007 RULE-2377 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG196 MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE 2 ( MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2506 Relational edit between MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MANAGED-CARE-PARTICIPATION ELG00014

record MANAGED-CARE-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG189,ELG191



2,076 Merged ELG197-0001 RULE-2394 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG197 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE 1 If MANAGED-CARE-PLAN-ENROLLMENT-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-ENROLLMENT-END-DATE ELG197











2,077 Merged ELG197-0002 RULE-2394 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG197 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-ENROLLMENT-END-DATE ELG197











2,078 Merged ELG197-0007 RULE-2377 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG197 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE 2 ( MANAGED-CARE-PLAN-ENROLLMENT-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( MANAGED-CARE-PLAN-ENROLLMENT-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [MANAGED-CARE-PARTICIPATION-ELG00014] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [MANAGED-CARE-PARTICIPATION-ELG00014] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2508 Relational edit between MANAGED-CARE-PLAN-ENROLLMENT-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MANAGED-CARE-PARTICIPATION ELG00014

record MANAGED-CARE-PARTICIPATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG189,ELG191



2,079 Logic updated: other ELG197-0008 RULE-2397 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG197 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then MANAGED-CARE-PLAN-ENROLLMENT-END-DATE must be <= DATE-OF-DEATH 2507 Relational edit between MANAGED-CARE-PLAN-ENROLLMENT-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 MANAGED-CARE-PARTICIPATION ELG00014

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.MANAGED-CARE-PLAN-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.MANAGED-CARE-PLAN-ENROLLMENT-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE ELG197

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG189,ELG191



2,080 Merged ELG197-0009 RULE-2391 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG197 MANAGED-CARE-PLAN-ENROLLMENT-END-DATE 2-M
2060
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-PARTICIPATION ELG00014



'if fns.hasValue(@val.MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-PLAN-ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE, @val.MANAGED-CARE-PLAN-ENROLLMENT-END-DATE)' MANAGED-CARE-PLAN-ENROLLMENT-EFF-DATE,MANAGED-CARE-PLAN-ENROLLMENT-END-DATE ELG196,ELG197











2,081 Logic updated: string matching ELG198-0001 RULE-2399 ELIGIBLE MANAGED-CARE-PARTICIPATION-ELG00014 ELG198 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-PARTICIPATION ELG00014



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG198











2,082 Moved to R&C ELG200-0003
ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG200 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,083 Moved to R&C ELG200-0004
ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG200 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,084 No logic changes ELG201-0002 RULE-2402 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG201 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ETHNICITY-INFORMATION ELG00015



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG201











2,085 Logic updated: other ELG201-0003 RULE-2403 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG201 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ETHNICITY-INFORMATION ELG00015 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG201 SUBMITTING-STATE ELG007









2,086 Retired: Other reasons ELG202-0002
ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG202 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,087 No logic changes ELG202-0003 RULE-2405 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG202 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) ETHNICITY-INFORMATION ELG00015



Field RECORD-NUMBER should be unique across all records of type ETHNICITY-INFORMATION RECORD-NUMBER ELG202











2,088 Retired: MSIS ID checks ELG203-0001
ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG203 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,089 Retired: MSIS ID checks ELG203-0002
ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG203 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,090 Merged ELG203-0005 RULE-2408 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG203 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [ETHNICITY-INFORMATION-ELG00015] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [ETHNICITY-INFORMATION-ELG00015] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2197 Edit that ETHNICITY-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ETHNICITY-INFORMATION ELG00015

record ETHNICITY-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG201,ELG203



2,091 No logic changes ELG204-0001 RULE-2409 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG204 ETHNICITY-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ETHNICITY-INFORMATION ELG00015



If the field is populated, the value must be contained in the set of valid values with id: ETHNICITY-CODE ETHNICITY-CODE ELG204











2,092 Merged ELG205-0001 RULE-2410 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG205 ETHNICITY-DECLARATION-EFF-DATE 1 If ETHNICITY-DECLARATION-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be a valid date of the form CCYYMMDD ETHNICITY-DECLARATION-EFF-DATE ELG205











2,093 Merged ELG205-0005 RULE-2410 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG205 ETHNICITY-DECLARATION-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be a valid date of the form CCYYMMDD ETHNICITY-DECLARATION-EFF-DATE ELG205











2,094 Merged ELG205-0006 RULE-2412 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG205 ETHNICITY-DECLARATION-EFF-DATE 2 ETHNICITY-DECLARATION-EFF-DATE must be <= ETHNICITY-DECLARATION-END-DATE 2045 Relational edit between ETHNICITY-DECLARATION-EFF-DATE and ETHNICITY-DECLARATION-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ETHNICITY-INFORMATION ELG00015



'if fns.hasValue(@val.ETHNICITY-DECLARATION-EFF-DATE) && fns.hasValue(@val.ETHNICITY-DECLARATION-END-DATE), then fns.isLessThanOrEqual(@val.ETHNICITY-DECLARATION-EFF-DATE, @val.ETHNICITY-DECLARATION-END-DATE)' ETHNICITY-DECLARATION-EFF-DATE,ETHNICITY-DECLARATION-END-DATE ELG205,ELG206











2,095 No logic changes ELG205-0008 RULE-2413 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG205 ETHNICITY-DECLARATION-EFF-DATE 2 If two or more ETHNICITY-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and ETHNICITY-CODE,
then for each pair of record segments,
(Segment 1 ETHNICITY-DECLARATION-EFF-DATE must <> Segment 2 ETHNICITY-DECLARATION-EFF-DATE)
AND
( (If Segment 1 ETHNICITY-DECLARATION-EFF-DATE < Segment 2 ETHNICITY-DECLARATION-EFF-DATE,
then
Segment 1 ETHNICITY-DECLARATION-END-DATE must be < Segment 2 ETHNICITY-DECLARATION-EFF-DATE)
OR
(If Segment 2 ETHNICITY-DECLARATION-EFF-DATE < Segment 1 ETHNICITY-DECLARATION-EFF-DATE,
then
Segment 2 ETHNICITY-DECLARATION-END-DATE must be < Segment 1 ETHNICITY-DECLARATION-EFF-DATE) )		 2152 Edit for overlapping coverage dates in record segments that have non-unique key fields in ETHNICITY-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) ETHNICITY-INFORMATION ELG00015



Records with the same primary keys must have non-overlapping date ranges. Effective date field: ETHNICITY-DECLARATION-EFF-DATE. End date field: ETHNICITY-DECLARATION-END-DATE ETHNICITY-DECLARATION-EFF-DATE,ETHNICITY-DECLARATION-END-DATE ELG205,ELG206











2,096 Merged ELG205-0009 RULE-2408 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG205 ETHNICITY-DECLARATION-EFF-DATE 2 ( ETHNICITY-DECLARATION-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ETHNICITY-INFORMATION-ELG00015] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ETHNICITY-INFORMATION-ELG00015] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ETHNICITY-DECLARATION-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ETHNICITY-INFORMATION-ELG00015] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ETHNICITY-INFORMATION-ELG00015] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2479 Relational edit between ETHNICITY-DECLARATION-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ETHNICITY-INFORMATION ELG00015

record ETHNICITY-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG201,ELG203



2,097 Merged ELG206-0001 RULE-2415 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG206 ETHNICITY-DECLARATION-END-DATE 1 If ETHNICITY-DECLARATION-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be a valid date of the form CCYYMMDD ETHNICITY-DECLARATION-END-DATE ELG206











2,098 Merged ELG206-0005 RULE-2415 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG206 ETHNICITY-DECLARATION-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be a valid date of the form CCYYMMDD ETHNICITY-DECLARATION-END-DATE ELG206











2,099 Merged ELG206-0008 RULE-2408 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG206 ETHNICITY-DECLARATION-END-DATE 2 ( ETHNICITY-DECLARATION-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ETHNICITY-INFORMATION-ELG00015] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ETHNICITY-INFORMATION-ELG00015] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ETHNICITY-DECLARATION-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ETHNICITY-INFORMATION-ELG00015] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ETHNICITY-INFORMATION-ELG00015] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2480 Relational edit between ETHNICITY-DECLARATION-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ETHNICITY-INFORMATION ELG00015

record ETHNICITY-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG201,ELG203



2,100 Merged ELG206-0009 RULE-2412 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG206 ETHNICITY-DECLARATION-END-DATE 2-M
2045
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ETHNICITY-INFORMATION ELG00015



'if fns.hasValue(@val.ETHNICITY-DECLARATION-EFF-DATE) && fns.hasValue(@val.ETHNICITY-DECLARATION-END-DATE), then fns.isLessThanOrEqual(@val.ETHNICITY-DECLARATION-EFF-DATE, @val.ETHNICITY-DECLARATION-END-DATE)' ETHNICITY-DECLARATION-EFF-DATE,ETHNICITY-DECLARATION-END-DATE ELG205,ELG206











2,101 Logic updated: string matching ELG207-0001 RULE-2419 ELIGIBLE ETHNICITY-INFORMATION-ELG00015 ELG207 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ETHNICITY-INFORMATION ELG00015



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG207











2,102 Moved to R&C ELG209-0003
ELIGIBLE RACE-INFORMATION-ELG00016 ELG209 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,103 Moved to R&C ELG209-0004
ELIGIBLE RACE-INFORMATION-ELG00016 ELG209 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,104 No logic changes ELG210-0002 RULE-2424 ELIGIBLE RACE-INFORMATION-ELG00016 ELG210 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value RACE-INFORMATION ELG00016



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG210











2,105 Logic updated: other ELG210-0003 RULE-2425 ELIGIBLE RACE-INFORMATION-ELG00016 ELG210 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) RACE-INFORMATION ELG00016 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG210 SUBMITTING-STATE ELG007









2,106 Retired: Other reasons ELG211-0002
ELIGIBLE RACE-INFORMATION-ELG00016 ELG211 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,107 No logic changes ELG211-0005 RULE-2427 ELIGIBLE RACE-INFORMATION-ELG00016 ELG211 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) RACE-INFORMATION ELG00016



Field RECORD-NUMBER should be unique across all records of type RACE-INFORMATION RECORD-NUMBER ELG211











2,108 Retired: MSIS ID checks ELG212-0001
ELIGIBLE RACE-INFORMATION-ELG00016 ELG212 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,109 Retired: MSIS ID checks ELG212-0002
ELIGIBLE RACE-INFORMATION-ELG00016 ELG212 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,110 Merged ELG212-0005 RULE-2430 ELIGIBLE RACE-INFORMATION-ELG00016 ELG212 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [RACE-INFORMATION-ELG00016] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [RACE-INFORMATION-ELG00016] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2220 Edit that RACE-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 RACE-INFORMATION ELG00016

record RACE-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG210,ELG212



2,111 No logic changes ELG213-0001 RULE-2431 ELIGIBLE RACE-INFORMATION-ELG00016 ELG213 RACE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value RACE-INFORMATION ELG00016



If the field is populated, the value must be contained in the set of valid values with id: RACE RACE ELG213











2,112 No logic changes ELG214-0001 RULE-2432 ELIGIBLE RACE-INFORMATION-ELG00016 ELG214 RACE-OTHER 2 If RACE = "010" or "015", then RACE-OTHER must not be 8-filled 2404 Relational edit between RACE-OTHER and RACE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) RACE-INFORMATION ELG00016



'if fns.isEqualToAny(@val.RACE, "010", "015"), then fns.hasValue(@val.RACE-OTHER)' RACE,RACE-OTHER ELG213,ELG214











2,113 Logic updated: string matching ELG214-0002 RULE-2433 ELIGIBLE RACE-INFORMATION-ELG00016 ELG214 RACE-OTHER 1 If RACE-OTHER is populated, it must contains valid characters. 120 Field contains invalid characters - RACE-OTHER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) RACE-INFORMATION ELG00016



'if fns.hasValue(@val.RACE-OTHER), then fns.matches(@val.RACE-OTHER, "^[^|*]*$")' RACE-OTHER ELG214











2,114 No logic changes ELG215-0001 RULE-2434 ELIGIBLE RACE-INFORMATION-ELG00016 ELG215 CERTIFIED-AMERICAN-INDIAN-ALASKAN-NATIVE-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value RACE-INFORMATION ELG00016



If the field is populated, the value must be contained in the set of valid values with id: CERTIFIED-AMERICAN-INDIAN-ALASKAN-NATIVE-INDICATOR CERTIFIED-AMERICAN-INDIAN-ALASKAN-NATIVE-INDICATOR ELG215











2,115 Merged ELG216-0001 RULE-2435 ELIGIBLE RACE-INFORMATION-ELG00016 ELG216 RACE-DECLARATION-EFF-DATE 1 If RACE-DECLARATION-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be a valid date of the form CCYYMMDD RACE-DECLARATION-EFF-DATE ELG216











2,116 Merged ELG216-0005 RULE-2435 ELIGIBLE RACE-INFORMATION-ELG00016 ELG216 RACE-DECLARATION-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be a valid date of the form CCYYMMDD RACE-DECLARATION-EFF-DATE ELG216











2,117 Merged ELG216-0006 RULE-2437 ELIGIBLE RACE-INFORMATION-ELG00016 ELG216 RACE-DECLARATION-EFF-DATE 2 RACE-DECLARATION-EFF-DATE must be <= RACE-DECLARATION-END-DATE 2114 Relational edit between RACE-DECLARATION-EFF-DATE and RACE-DECLARATION-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) RACE-INFORMATION ELG00016



'if fns.hasValue(@val.RACE-DECLARATION-EFF-DATE) && fns.hasValue(@val.RACE-DECLARATION-END-DATE), then fns.isLessThanOrEqual(@val.RACE-DECLARATION-EFF-DATE, @val.RACE-DECLARATION-END-DATE)' RACE-DECLARATION-EFF-DATE,RACE-DECLARATION-END-DATE ELG216,ELG217











2,118 No logic changes ELG216-0008 RULE-2438 ELIGIBLE RACE-INFORMATION-ELG00016 ELG216 RACE-DECLARATION-EFF-DATE 2 If two or more RACE-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, RACE, and RACE-OTHER,
then for each pair of record segments,
(Segment 1 RACE-DECLARATION-EFF-DATE must <> Segment 2 RACE-DECLARATION-EFF-DATE)
AND
( (If Segment 1 RACE-DECLARATION-EFF-DATE < Segment 2 RACE-DECLARATION-EFF-DATE,
then
Segment 1 RACE-DECLARATION-END-DATE must be < Segment 2 RACE-DECLARATION-EFF-DATE)
OR
(If Segment 2 RACE-DECLARATION-EFF-DATE < Segment 1 RACE-DECLARATION-EFF-DATE,
then
Segment 2 RACE-DECLARATION-END-DATE must be < Segment 1 RACE-DECLARATION-EFF-DATE) )		 2178 Edit for overlapping coverage dates in record segments that have non-unique key fields in RACE-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) RACE-INFORMATION ELG00016



Records with the same primary keys must have non-overlapping date ranges. Effective date field: RACE-DECLARATION-EFF-DATE. End date field: RACE-DECLARATION-END-DATE RACE-DECLARATION-EFF-DATE,RACE-DECLARATION-END-DATE ELG216,ELG217











2,119 Merged ELG216-0009 RULE-2430 ELIGIBLE RACE-INFORMATION-ELG00016 ELG216 RACE-DECLARATION-EFF-DATE 2 ( RACE-DECLARATION-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [RACE-INFORMATION-ELG00016] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [RACE-INFORMATION-ELG00016] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( RACE-DECLARATION-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [RACE-INFORMATION-ELG00016] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [RACE-INFORMATION-ELG00016] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2535 Relational edit between RACE-DECLARATION-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 RACE-INFORMATION ELG00016

record RACE-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG210,ELG212



2,120 Merged ELG217-0001 RULE-2440 ELIGIBLE RACE-INFORMATION-ELG00016 ELG217 RACE-DECLARATION-END-DATE 1 If RACE-DECLARATION-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be a valid date of the form CCYYMMDD RACE-DECLARATION-END-DATE ELG217











2,121 Merged ELG217-0005 RULE-2440 ELIGIBLE RACE-INFORMATION-ELG00016 ELG217 RACE-DECLARATION-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be a valid date of the form CCYYMMDD RACE-DECLARATION-END-DATE ELG217











2,122 Merged ELG217-0008 RULE-2430 ELIGIBLE RACE-INFORMATION-ELG00016 ELG217 RACE-DECLARATION-END-DATE 2 ( RACE-DECLARATION-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [RACE-INFORMATION-ELG00016] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [RACE-INFORMATION-ELG00016] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( RACE-DECLARATION-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [RACE-INFORMATION-ELG00016] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [RACE-INFORMATION-ELG00016] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2536 Relational edit between RACE-DECLARATION-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 RACE-INFORMATION ELG00016

record RACE-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG210,ELG212



2,123 Merged ELG217-0009 RULE-2437 ELIGIBLE RACE-INFORMATION-ELG00016 ELG217 RACE-DECLARATION-END-DATE 2-M
2114
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) RACE-INFORMATION ELG00016



'if fns.hasValue(@val.RACE-DECLARATION-EFF-DATE) && fns.hasValue(@val.RACE-DECLARATION-END-DATE), then fns.isLessThanOrEqual(@val.RACE-DECLARATION-EFF-DATE, @val.RACE-DECLARATION-END-DATE)' RACE-DECLARATION-EFF-DATE,RACE-DECLARATION-END-DATE ELG216,ELG217











2,124 Logic updated: string matching ELG218-0001 RULE-2444 ELIGIBLE RACE-INFORMATION-ELG00016 ELG218 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) RACE-INFORMATION ELG00016



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG218











2,125 Moved to R&C ELG220-0003
ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG220 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,126 Moved to R&C ELG220-0004
ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG220 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,127 No logic changes ELG221-0002 RULE-2447 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG221 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value DISABILITY-INFORMATION ELG00017



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG221











2,128 Logic updated: other ELG221-0003 RULE-2448 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG221 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) DISABILITY-INFORMATION ELG00017 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG221 SUBMITTING-STATE ELG007









2,129 Retired: Other reasons ELG222-0002
ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG222 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,130 No logic changes ELG222-0003 RULE-2450 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG222 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) DISABILITY-INFORMATION ELG00017



Field RECORD-NUMBER should be unique across all records of type DISABILITY-INFORMATION RECORD-NUMBER ELG222











2,131 Retired: MSIS ID checks ELG223-0001
ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG223 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,132 Retired: MSIS ID checks ELG223-0002
ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG223 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,133 Merged ELG223-0005 RULE-2453 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG223 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [DISABILITY-INFORMATION-ELG00017] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [DISABILITY-INFORMATION-ELG00017] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2193 Edit that DISABILITY-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 DISABILITY-INFORMATION ELG00017

record DISABILITY-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG221,ELG223



2,134 No logic changes ELG224-0002 RULE-2454 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG224 DISABILITY-TYPE-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value DISABILITY-INFORMATION ELG00017



If the field is populated, the value must be contained in the set of valid values with id: DISABILITY-TYPE-CODE DISABILITY-TYPE-CODE ELG224











2,135 Merged ELG225-0001 RULE-2455 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG225 DISABILITY-TYPE-EFF-DATE 1 If DISABILITY-TYPE-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be a valid date of the form CCYYMMDD DISABILITY-TYPE-EFF-DATE ELG225











2,136 Merged ELG225-0005 RULE-2455 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG225 DISABILITY-TYPE-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be a valid date of the form CCYYMMDD DISABILITY-TYPE-EFF-DATE ELG225











2,137 Merged ELG225-0006 RULE-2457 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG225 DISABILITY-TYPE-EFF-DATE 2 DISABILITY-TYPE-EFF-DATE must be <= DISABILITY-TYPE-END-DATE 2023 Relational edit between DISABILITY-TYPE-EFF-DATE and DISABILITY-TYPE-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) DISABILITY-INFORMATION ELG00017



'if fns.hasValue(@val.DISABILITY-TYPE-EFF-DATE) && fns.hasValue(@val.DISABILITY-TYPE-END-DATE), then fns.isLessThanOrEqual(@val.DISABILITY-TYPE-EFF-DATE, @val.DISABILITY-TYPE-END-DATE)' DISABILITY-TYPE-EFF-DATE,DISABILITY-TYPE-END-DATE ELG225,ELG226











2,138 No logic changes ELG225-0008 RULE-2458 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG225 DISABILITY-TYPE-EFF-DATE 2 If two or more DISABILITY-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and DISABILITY-TYPE-CODE,
then for each pair of record segments,
(Segment 1 DISABILITY-TYPE-EFF-DATE must <> Segment 2 DISABILITY-TYPE-EFF-DATE)
AND
( (If Segment 1 DISABILITY-TYPE-EFF-DATE < Segment 2 DISABILITY-TYPE-EFF-DATE,
then
Segment 1 DISABILITY-TYPE-END-DATE must be < Segment 2 DISABILITY-TYPE-EFF-DATE)
OR
(If Segment 2 DISABILITY-TYPE-EFF-DATE < Segment 1 DISABILITY-TYPE-EFF-DATE,
then
Segment 2 DISABILITY-TYPE-END-DATE must be < Segment 1 DISABILITY-TYPE-EFF-DATE) )		 2149 Edit for overlapping coverage dates in record segments that have non-unique key fields in DISABILITY-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) DISABILITY-INFORMATION ELG00017



Records with the same primary keys must have non-overlapping date ranges. Effective date field: DISABILITY-TYPE-EFF-DATE. End date field: DISABILITY-TYPE-END-DATE DISABILITY-TYPE-EFF-DATE,DISABILITY-TYPE-END-DATE ELG225,ELG226











2,139 Merged ELG225-0009 RULE-2453 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG225 DISABILITY-TYPE-EFF-DATE 2 ( DISABILITY-TYPE-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [DISABILITY-INFORMATION-ELG00017] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [DISABILITY-INFORMATION-ELG00017] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( DISABILITY-TYPE-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [DISABILITY-INFORMATION-ELG00017] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [DISABILITY-INFORMATION-ELG00017] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2470 Relational edit between DISABILITY-TYPE-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 DISABILITY-INFORMATION ELG00017

record DISABILITY-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG221,ELG223



2,140 Merged ELG226-0001 RULE-2460 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG226 DISABILITY-TYPE-END-DATE 1 If DISABILITY-TYPE-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be a valid date of the form CCYYMMDD DISABILITY-TYPE-END-DATE ELG226











2,141 Merged ELG226-0005 RULE-2460 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG226 DISABILITY-TYPE-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be a valid date of the form CCYYMMDD DISABILITY-TYPE-END-DATE ELG226











2,142 Merged ELG226-0008 RULE-2453 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG226 DISABILITY-TYPE-END-DATE 2 ( DISABILITY-TYPE-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [DISABILITY-INFORMATION-ELG00017] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [DISABILITY-INFORMATION-ELG00017] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( DISABILITY-TYPE-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [DISABILITY-INFORMATION-ELG00017] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [DISABILITY-INFORMATION-ELG00017] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2471 Relational edit between DISABILITY-TYPE-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 DISABILITY-INFORMATION ELG00017

record DISABILITY-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG221,ELG223



2,143 Merged ELG226-0009 RULE-2457 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG226 DISABILITY-TYPE-END-DATE 2-M
2023
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) DISABILITY-INFORMATION ELG00017



'if fns.hasValue(@val.DISABILITY-TYPE-EFF-DATE) && fns.hasValue(@val.DISABILITY-TYPE-END-DATE), then fns.isLessThanOrEqual(@val.DISABILITY-TYPE-EFF-DATE, @val.DISABILITY-TYPE-END-DATE)' DISABILITY-TYPE-EFF-DATE,DISABILITY-TYPE-END-DATE ELG225,ELG226











2,144 Logic updated: string matching ELG227-0001 RULE-2464 ELIGIBLE DISABILITY-INFORMATION-ELG00017 ELG227 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) DISABILITY-INFORMATION ELG00017



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG227











2,145 Moved to R&C ELG229-0003
ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG229 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,146 Moved to R&C ELG229-0004
ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG229 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,147 No logic changes ELG230-0002 RULE-2467 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG230 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value 1115A-DEMONSTRATION-INFORMATION ELG00018



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG230











2,148 Logic updated: other ELG230-0003 RULE-2468 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG230 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) 1115A-DEMONSTRATION-INFORMATION ELG00018 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG230 SUBMITTING-STATE ELG007









2,149 Retired: Other reasons ELG231-0002
ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG231 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,150 No logic changes ELG231-0003 RULE-2470 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG231 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) 1115A-DEMONSTRATION-INFORMATION ELG00018



Field RECORD-NUMBER should be unique across all records of type 1115A-DEMONSTRATION-INFORMATION RECORD-NUMBER ELG231











2,151 Retired: MSIS ID checks ELG232-0001
ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG232 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,152 Retired: MSIS ID checks ELG232-0002
ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG232 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,153 Merged ELG232-0005 RULE-2473 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG232 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2187 Edit that 1115A-DEMONSTRATION-INFORMATION child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 1115A-DEMONSTRATION-INFORMATION ELG00018

record 1115A-DEMONSTRATION-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG230,ELG232



2,154 No logic changes ELG233-0002 RULE-2474 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG233 1115A-DEMONSTRATION-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value 1115A-DEMONSTRATION-INFORMATION ELG00018



If the field is populated, the value must be contained in the set of valid values with id: 1115A-DEMONSTRATION-IND 1115A-DEMONSTRATION-IND ELG233











2,155 Merged ELG234-0001 RULE-2475 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG234 1115A-EFF-DATE 1 If 1115A-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be a valid date of the form CCYYMMDD 1115A-EFF-DATE ELG234











2,156 Merged ELG234-0002 RULE-2475 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG234 1115A-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be a valid date of the form CCYYMMDD 1115A-EFF-DATE ELG234











2,157 Merged ELG234-0006 RULE-2477 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG234 1115A-EFF-DATE 2 1115A-EFF-DATE must be <= 1115A-END-DATE 2001 Relational edit between 1115A-EFF-DATE and 1115A-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) 1115A-DEMONSTRATION-INFORMATION ELG00018



'if fns.hasValue(@val.1115A-EFF-DATE) && fns.hasValue(@val.1115A-END-DATE), then fns.isLessThanOrEqual(@val.1115A-EFF-DATE, @val.1115A-END-DATE)' 1115A-EFF-DATE,1115A-END-DATE ELG234,ELG235











2,158 No logic changes ELG234-0007 RULE-2478 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG234 1115A-EFF-DATE 2 If two or more 1115A-DEMONSTRATION-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and 1115A-DEMONSTRATION-IND,
then for each pair of record segments,
(Segment 1 1115A-EFF-DATE must <> Segment 2 1115A-EFF-DATE)
AND
( (If Segment 1 1115A-EFF-DATE < Segment 2 1115A-EFF-DATE,
then
Segment 1 1115A-END-DATE must be < Segment 2 1115A-EFF-DATE)
OR
(If Segment 2 1115A-EFF-DATE < Segment 1 1115A-EFF-DATE,
then
Segment 2 1115A-END-DATE must be < Segment 1 1115A-EFF-DATE) )		 2147 Edit for overlapping coverage dates in record segments that have non-unique key fields in 1115A-DEMONSTRATION-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) 1115A-DEMONSTRATION-INFORMATION ELG00018



Records with the same primary keys must have non-overlapping date ranges. Effective date field: 1115A-EFF-DATE. End date field: 1115A-END-DATE 1115A-EFF-DATE,1115A-END-DATE ELG234,ELG235











2,159 Merged ELG234-0008 RULE-2473 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG234 1115A-EFF-DATE 2 ( 1115A-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( 1115A-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2461 Relational edit between 1115A-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 1115A-DEMONSTRATION-INFORMATION ELG00018

record 1115A-DEMONSTRATION-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG230,ELG232



2,160 Merged ELG235-0001 RULE-2480 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG235 1115A-END-DATE 1 If 1115A-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be a valid date of the form CCYYMMDD 1115A-END-DATE ELG235











2,161 Merged ELG235-0002 RULE-2480 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG235 1115A-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be a valid date of the form CCYYMMDD 1115A-END-DATE ELG235











2,162 Merged ELG235-0008 RULE-2473 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG235 1115A-END-DATE 2 ( 1115A-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( 1115A-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [1115A-DEMONSTRATION-INFORMATION-ELG00018] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [1115A-DEMONSTRATION-INFORMATION-ELG00018] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2463 Relational edit between 1115A-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 1115A-DEMONSTRATION-INFORMATION ELG00018

record 1115A-DEMONSTRATION-INFORMATION has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG230,ELG232



2,163 Logic updated: other ELG235-0009 RULE-2483 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG235 1115A-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then 1115A-END-DATE must be <= DATE-OF-DEATH 2462 Relational edit between 1115A-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 1115A-DEMONSTRATION-INFORMATION ELG00018

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.1115A-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.1115A-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 1115A-END-DATE ELG235

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG230,ELG232



2,164 Merged ELG235-0010 RULE-2477 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG235 1115A-END-DATE 2-M
2001
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) 1115A-DEMONSTRATION-INFORMATION ELG00018



'if fns.hasValue(@val.1115A-EFF-DATE) && fns.hasValue(@val.1115A-END-DATE), then fns.isLessThanOrEqual(@val.1115A-EFF-DATE, @val.1115A-END-DATE)' 1115A-EFF-DATE,1115A-END-DATE ELG234,ELG235











2,165 Logic updated: string matching ELG236-0001 RULE-2485 ELIGIBLE 1115A-DEMONSTRATION-INFORMATION-ELG00018 ELG236 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) 1115A-DEMONSTRATION-INFORMATION ELG00018



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG236











2,166 Moved to R&C ELG238-0003
ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG238 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,167 Moved to R&C ELG238-0004
ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG238 RECORD-ID 2 If FILE-NAME = "ELIGIBLE", then the first 3 positions of RECORD-ID must = "ELG" 150 Invalid or missing RECORD-ID

























2,168 No logic changes ELG239-0002 RULE-2488 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG239 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG239











2,169 Logic updated: other ELG239-0003 RULE-2489 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG239 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG239 SUBMITTING-STATE ELG007









2,170 Retired: Other reasons ELG240-0002
ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG240 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,171 No logic changes ELG240-0003 RULE-2491 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG240 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Field RECORD-NUMBER should be unique across all records of type HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME RECORD-NUMBER ELG240











2,172 Retired: MSIS ID checks ELG241-0001
ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG241 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,173 Retired: MSIS ID checks ELG241-0002
ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG241 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,174 Merged ELG241-0005 RULE-2494 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG241 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2198 Edit that HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020

record HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG239,ELG241



2,175 No logic changes ELG242-0001 RULE-2495 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG242 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



If the field is populated, the value must be contained in the set of valid values with id: HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-CODE HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-CODE ELG242











2,176 Merged ELG243-0001 RULE-2496 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG243 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE 1 If HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be a valid date of the form CCYYMMDD HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE ELG243











2,177 Merged ELG243-0002 RULE-2496 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG243 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be a valid date of the form CCYYMMDD HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE ELG243











2,178 No logic changes ELG243-0003 RULE-2498 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG243 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE 2 If two or more HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-CODE,
then for each pair of record segments,
(Segment 1 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE must <> Segment 2 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE)
AND
( (If Segment 1 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE < Segment 2 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE,
then
Segment 1 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE must be < Segment 2 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE)
OR
(If Segment 2 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE < Segment 1 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE,
then
Segment 2 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE must be < Segment 1 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE) )		 2153 Edit for overlapping coverage dates in record segments that have non-unique key fields in HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Records with the same primary keys must have non-overlapping date ranges. Effective date field: HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE. End date field: HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE,HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE ELG243,ELG244











2,179 Merged ELG243-0004 RULE-2494 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG243 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE 2 ( HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2481 Relational edit between HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020

record HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG239,ELG241



2,180 Merged ELG244-0001 RULE-2500 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG244 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE 1 If HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be a valid date of the form CCYYMMDD HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE ELG244











2,181 Merged ELG244-0002 RULE-2500 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG244 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be a valid date of the form CCYYMMDD HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE ELG244











2,182 Merged ELG244-0003 RULE-2494 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG244 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE 2 ( HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2482 Relational edit between HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020

record HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG239,ELG241



2,183 Logic updated: other ELG244-0004 RULE-2503 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG244 HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE 2-M
2046
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



'if fns.hasValue(@val.HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE) && fns.hasValue(@val.HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE), then fns.isLessThanOrEqual(@val.HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE, @val.HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE)' HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-EFF-DATE,HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-END-DATE ELG243,ELG244











2,184 Logic updated: string matching ELG245-0001 RULE-2504 ELIGIBLE HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME-ELG00020 ELG245 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG245











2,185 Moved to R&C ELG247-0002
ELIGIBLE FILE-HEADER-RECORD-ELIGIBILITY-ELG00001 ELG247 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range

























2,186 Moved to R&C ELG248-0003
ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG248 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,187 No logic changes ELG249-0001 RULE-2507 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG249 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE ELG249











2,188 Logic updated: other ELG249-0004 RULE-2508 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG249 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-ELIGIBILITY-ELG00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) ENROLLMENT-TIME-SPAN-SEGMENT ELG00021 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE ELG249 SUBMITTING-STATE ELG007









2,189 Retired: Other reasons ELG250-0001
ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG250 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,190 No logic changes ELG250-0004 RULE-2510 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG250 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Field RECORD-NUMBER should be unique across all records of type ENROLLMENT-TIME-SPAN-SEGMENT RECORD-NUMBER ELG250











2,191 Retired: MSIS ID checks ELG251-0001
ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG251 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























2,192 Retired: MSIS ID checks ELG251-0002
ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG251 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























2,193 Merged ELG251-0005 RULE-2513 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG251 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] must = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on any record in the file and SUBMITTING-STATE [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] must = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] on the same record in the file 2196 Edit that ENROLLMENT-TIME-SPAN-SEGMENT child record has a PRIMARY-DEMOGRAPHICS-ELIGIBILITY parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ENROLLMENT-TIME-SPAN-SEGMENT ELG00021

record ENROLLMENT-TIME-SPAN-SEGMENT has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG249,ELG251



2,194 No logic changes ELG252-0001 RULE-2514 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG252 ENROLLMENT-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



If the field is populated, the value must be contained in the set of valid values with id: ENROLLMENT-TYPE ENROLLMENT-TYPE ELG252











2,195 Merged ELG253-0001 RULE-2515 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG253 ENROLLMENT-EFF-DATE 1 If ENROLLMENT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be a valid date of the form CCYYMMDD ENROLLMENT-EFF-DATE ELG253











2,196 Merged ELG253-0003 RULE-2515 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG253 ENROLLMENT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be a valid date of the form CCYYMMDD ENROLLMENT-EFF-DATE ELG253











2,197 Merged ELG253-0005 RULE-2517 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG253 ENROLLMENT-EFF-DATE 2 ENROLLMENT-EFF-DATE must be <= ENROLLMENT-END-DATE 2044 Relational edit between ENROLLMENT-EFF-DATE and ENROLLMENT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



'if fns.hasValue(@val.ENROLLMENT-EFF-DATE) && fns.hasValue(@val.ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.ENROLLMENT-EFF-DATE, @val.ENROLLMENT-END-DATE)' ENROLLMENT-EFF-DATE,ENROLLMENT-END-DATE ELG253,ELG254











2,198 Merged ELG253-0007 RULE-2513 ELIGIBLE Enrollment-Time-Span-Segment-ELG00021 ELG253 ENROLLMENT-EFF-DATE 2 ( ENROLLMENT-EFF-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ENROLLMENT-EFF-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2476 Relational edit between ENROLLMENT-EFF-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ENROLLMENT-TIME-SPAN-SEGMENT ELG00021

record ENROLLMENT-TIME-SPAN-SEGMENT has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG249,ELG251



2,199 No logic changes ELG253-0008 RULE-2519 ELIGIBLE Enrollment-Time-Span-Segment-ELG00021 ELG253 ENROLLMENT-EFF-DATE 2 If two or more ENROLLMENT-TIME-SPAN-SEGMENT record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and ENROLLMENT-TYPE
then for each pair of record segments,
(Segment 1 ENROLLMENT-EFF-DATE must <> Segment 2 ENROLLMENT-EFF-DATE)
AND
( (If Segment 1 ENROLLMENT-EFF-DATE < Segment 2 ENROLLMENT-EFF-DATE,
then
Segment 1 ENROLLMENT-END-DATE must be < Segment 2 ENROLLMENT-EFF-DATE)
OR
(If Segment 2 ENROLLMENT-EFF-DATE < Segment 1 ENROLLMENT-EFF-DATE,
then
Segment 2 ENROLLMENT-END-DATE must be < Segment 1 ENROLLMENT-EFF-DATE) )		 2546 Edit for overlapping coverage dates in record segments that have non-unique key fields in ENROLLMENT-TIME-SPAN-SEGMENT failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Records with the same primary keys must have non-overlapping date ranges. Effective date field: ENROLLMENT-EFF-DATE. End date field: ENROLLMENT-END-DATE ENROLLMENT-EFF-DATE,ENROLLMENT-END-DATE ELG253,ELG254











2,200 No logic changes ELG254-0003 RULE-6586 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG254 ENROLLMENT-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be a valid date of the form CCYYMMDD ENROLLMENT-END-DATE ELG254











2,201 Merged ELG254-0005 RULE-2513 ELIGIBLE Enrollment-Time-Span-Segment-ELG00021 ELG254 ENROLLMENT-END-DATE 2 ( ENROLLMENT-END-DATE must be <= PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )
AND
( ENROLLMENT-END-DATE must be >= PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE on any PRIMARY-DEMOGRAPHICS-ELIGIBILITY segment where SUBMITTING-STATE [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] and MSIS-IDENTIFICATION-NUM [ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002 ] )		 2478 Relational edit between ENROLLMENT-END-DATE, PRIMARY-DEMOGRAPHIC-ELEMENT-END-DATE, and PRIMARY-DEMOGRAPHIC-ELEMENT-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ENROLLMENT-TIME-SPAN-SEGMENT ELG00021

record ENROLLMENT-TIME-SPAN-SEGMENT has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG249,ELG251



2,202 Logic updated: other ELG254-0006 RULE-2522 ELIGIBLE Enrollment-Time-Span-Segment-ELG00021 ELG254 ENROLLMENT-END-DATE 2 If DATE-OF-DEATH is not 8-filled, then ENROLLMENT-END-DATE must be <= DATE-OF-DEATH 2477 Relational edit between ENROLLMENT-END-DATE and DATE-OF-DEATH failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 ENROLLMENT-TIME-SPAN-SEGMENT ELG00021

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.ENROLLMENT-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 ENROLLMENT-END-DATE ELG254

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG249,ELG251



2,203 Logic updated: string matching ELG255-0001 RULE-2523 ELIGIBLE ENROLLMENT-TIME-SPAN-SEGMENT-ELG00021 ELG255 STATE-NOTATION 1 If STATE-NOTATIION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION ELG255











2,204 Merged ELG255-0003 RULE-2517 ELIGIBLE Enrollment-Time-Span-Segment-ELG00021 ELG255 ENROLLMENT-END-DATE 2-M
2044
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



'if fns.hasValue(@val.ENROLLMENT-EFF-DATE) && fns.hasValue(@val.ENROLLMENT-END-DATE), then fns.isLessThanOrEqual(@val.ENROLLMENT-EFF-DATE, @val.ENROLLMENT-END-DATE)' ENROLLMENT-EFF-DATE,ENROLLMENT-END-DATE ELG253,ELG254











2,205 Moved to R&C MCR001-0003
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,206 Moved to R&C MCR001-0004
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR001 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,207 Moved to R&C MCR003-0002
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR003 SUBMISSION-TRANSACTION-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,208 Moved to R&C MCR004-0002
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR004 FILE-ENCODING-SPECIFICATION 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,209 Moved to R&C MCR006-0002
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR006 FILE-NAME 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,210 Moved to R&C MCR007-0002
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR007 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,211 Moved to R&C MCR007-0004
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























2,212 Merged MCR008-0002 RULE-2532 MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED MCR008











2,213 Merged MCR008-0003 RULE-2532 MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED MCR008











2,214 Moved to R&C MCR008-0004
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed

























2,215 Moved to R&C MCR008-0005
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























2,216 No logic changes MCR009-0002 RULE-2536 MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD MCR009











2,217 Moved to R&C MCR009-0004
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD DD is not equal to the first day of the month 114 Invalid value in DD for START-OF-TIME-PERIOD

























2,218 Moved to R&C MCR009-0005
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























2,219 Moved to R&C MCR009-0006
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























2,220 No logic changes MCR010-0003 RULE-2540 MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR010 END-OF-TIME-PERIOD 1 If END-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD MCR010











2,221 Moved to R&C MCR010-0004
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR010 END-OF-TIME-PERIOD 1 If END-OF-TIME-PERIOD DD is not equal to last day of the month 115 Invalid value within END-OF-TIME-PERIOD

























2,222 Moved to R&C MCR010-0005
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR010 END-OF-TIME-PERIOD 2-M
2019


























2,223 Moved to R&C MCR010-0006
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR010 END-OF-TIME-PERIOD 2-M
2122


























2,224 Moved to R&C MCR010-0007
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date

























2,225 Retired: required value checks MCR011-0001
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR011 FILE-STATUS-INDICATOR 1 Required data element has not been reported 113 Required data element has not been reported.

























2,226 Moved to R&C MCR011-0002
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR011 FILE-STATUS-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,227 Moved to R&C MCR011-0003
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























2,228 Merged MCR013-0001 RULE-2548 MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR013 TOT-REC-CNT 1 If TOT-REC-CNT = 0 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT MCR013











2,229 Merged MCR013-0002 RULE-2548 MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT MCR013











2,230 Moved to R&C MCR014-0001
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























2,231 Moved to R&C MCR016-0003
MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,232 Moved to R&C MCR016-0004
MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR016 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,233 No logic changes MCR017-0002 RULE-2553 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR017 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-MAIN MCR00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR017











2,234 Logic updated: other MCR017-0004 RULE-2554 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-MAIN MCR00002 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR017 SUBMITTING-STATE MCR007









2,235 Retired: Other reasons MCR018-0001
MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR018 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,236 No logic changes MCR018-0003 RULE-2556 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MANAGED-CARE-MAIN MCR00002



Field RECORD-NUMBER should be unique across all records of type MANAGED-CARE-MAIN RECORD-NUMBER MCR018











2,237 Retired: required value checks MCR019-0001
MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR019 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,238 Logic updated: string matching MCR019-0002 RULE-2558 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR019 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR019











2,239 Merged MCR020-0002 RULE-2559 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR020 MANAGED-CARE-CONTRACT-EFF-DATE 1 If MANAGED-CARE-CONTRACT-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-CONTRACT-EFF-DATE MCR020











2,240 Merged MCR020-0003 RULE-2559 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR020 MANAGED-CARE-CONTRACT-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-CONTRACT-EFF-DATE MCR020











2,241 Merged MCR020-0004 RULE-2561 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR020 MANAGED-CARE-CONTRACT-EFF-DATE 2 MANAGED-CARE-CONTRACT-EFF-DATE must be <= MANAGED-CARE-CONTRACT-END-DATE 2057 Relational edit between MANAGED-CARE-CONTRACT-EFF-DATE and MANAGED-CARE-CONTRACT-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.MANAGED-CARE-CONTRACT-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-CONTRACT-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-CONTRACT-EFF-DATE, @val.MANAGED-CARE-CONTRACT-END-DATE)' MANAGED-CARE-CONTRACT-EFF-DATE,MANAGED-CARE-CONTRACT-END-DATE MCR020,MCR021











2,242 Merged MCR021-0003 RULE-2562 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR021 MANAGED-CARE-CONTRACT-END-DATE 1 If MANAGED-CARE-CONTRACT-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-CONTRACT-END-DATE MCR021











2,243 Merged MCR021-0004 RULE-2562 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR021 MANAGED-CARE-CONTRACT-END-DATE 1 If date is not in CCYYMMDD format 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-CONTRACT-END-DATE MCR021











2,244 Merged MCR021-0005 RULE-2561 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR021 MANAGED-CARE-CONTRACT-END-DATE 2-M
2057
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.MANAGED-CARE-CONTRACT-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-CONTRACT-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-CONTRACT-EFF-DATE, @val.MANAGED-CARE-CONTRACT-END-DATE)' MANAGED-CARE-CONTRACT-EFF-DATE,MANAGED-CARE-CONTRACT-END-DATE MCR020,MCR021











2,245 Retired: required value checks MCR022-0001
MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR022 MANAGED-CARE-NAME 1 If MANAGED-CARE-NAME = spaces 113 Required data element has not been reported.

























2,246 Logic updated: string matching MCR022-0002 RULE-2566 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR022 MANAGED-CARE-NAME 1 MANAGED-CARE-NAME contains must contains valid characters. 120 Field contains invalid characters -MANAGED-CARE-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.MANAGED-CARE-NAME), then fns.matches(@val.MANAGED-CARE-NAME, "^[^|*]*$")' MANAGED-CARE-NAME MCR022











2,247 No logic changes MCR023-0002 RULE-2567 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR023 MANAGED-CARE-PROGRAM 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-MAIN MCR00002



If the field is populated, the value must be contained in the set of valid values with id: MANAGED-CARE-PROGRAM MANAGED-CARE-PROGRAM MCR023











2,248 No logic changes MCR024-0002 RULE-2568 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR024 MANAGED-CARE-PLAN-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-MAIN MCR00002



If the field is populated, the value must be contained in the set of valid values with id: MANAGED-CARE-PLAN-TYPE MANAGED-CARE-PLAN-TYPE MCR024











2,249 No logic changes MCR025-0002 RULE-2569 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR025 REIMBURSEMENT-ARRANGEMENT 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-MAIN MCR00002



If the field is populated, the value must be contained in the set of valid values with id: REIMBURSEMENT-ARRANGEMENT REIMBURSEMENT-ARRANGEMENT MCR025











2,250 No logic changes MCR026-0002 RULE-2570 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR026 MANAGED-CARE-PROFIT-STATUS 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-MAIN MCR00002



If the field is populated, the value must be contained in the set of valid values with id: MANAGED-CARE-PROFIT-STATUS MANAGED-CARE-PROFIT-STATUS MCR026











2,251 No logic changes MCR027-0002 RULE-2571 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR027 CORE-BASED-STATISTICAL-AREA-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-MAIN MCR00002



If the field is populated, the value must be contained in the set of valid values with id: CORE-BASED-STATISTICAL-AREA-CODE CORE-BASED-STATISTICAL-AREA-CODE MCR027











2,252 No logic changes MCR028-0001 RULE-2572 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR028 PERCENT-BUSINESS 1 If PERCENT-BUSINESS not > or = 0 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.PERCENT-BUSINESS), then fns.inRange(@val.PERCENT-BUSINESS, 0,100)' PERCENT-BUSINESS MCR028











2,253 No logic changes MCR028-0002 RULE-2573 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR028 PERCENT-BUSINESS 1 Non-Numeric Value Provided 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: 9(3) PERCENT-BUSINESS MCR028











2,254 No logic changes MCR029-0002 RULE-2574 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR029 MANAGED-CARE-SERVICE-AREA 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-MAIN MCR00002



If the field is populated, the value must be contained in the set of valid values with id: MANAGED-CARE-SERVICE-AREA MANAGED-CARE-SERVICE-AREA MCR029











2,255 Merged MCR030-0002 RULE-2575 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR030 MANAGED-CARE-MAIN-REC-EFF-DATE 1 If MANAGED-CARE-MAIN-REC-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-MAIN-REC-EFF-DATE MCR030











2,256 Merged MCR030-0003 RULE-2575 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR030 MANAGED-CARE-MAIN-REC-EFF-DATE 1 If date is not in CCYYMMDD format 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-MAIN-REC-EFF-DATE MCR030











2,257 Merged MCR030-0004 RULE-2577 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR030 MANAGED-CARE-MAIN-REC-EFF-DATE 2 MANAGED-CARE-MAIN-REC-EFF-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE 2058 Relational edit between MANAGED-CARE-MAIN-REC-EFF-DATE and MANAGED-CARE-MAIN-REC-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.MANAGED-CARE-MAIN-REC-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-MAIN-REC-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-MAIN-REC-EFF-DATE, @val.MANAGED-CARE-MAIN-REC-END-DATE)' MANAGED-CARE-MAIN-REC-EFF-DATE,MANAGED-CARE-MAIN-REC-END-DATE MCR030,MCR031











2,258 No logic changes MCR030-0005 RULE-2578 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR030 MANAGED-CARE-MAIN-REC-EFF-DATE 2 If two or more MANAGED-CARE-MAIN record segments have the same SUBMITTING-STATE and STATE-PLAN-ID-NUM
then for each pair of record segments,
(Segment 1 MANAGED-CARE-MAIN-EFF-DATE must <> Segment 2 MANAGED-CARE-MAIN-EFF-DATE)
AND
( (If Segment 1 MANAGED-CARE-MAIN-EFF-DATE < Segment 2 MANAGED-CARE-MAIN-EFF-DATE,
then
Segment 1 MANAGED-CARE-MAIN-END-DATE must be < Segment 2 MANAGED-CARE-MAIN-EFF-DATE)
OR
(If Segment 2 MANAGED-CARE-MAIN-EFF-DATE < Segment 1 MANAGED-CARE-MAIN-EFF-DATE,
then
Segment 2 MANAGED-CARE-MAIN-END-DATE must be < Segment 1 MANAGED-CARE-MAIN-EFF-DATE) )		 2161 Edit for overlapping coverage dates in record segments that have non-unique key fields in MANAGED-CARE-MAIN failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MANAGED-CARE-MAIN MCR00002



Records with the same primary keys must have non-overlapping date ranges. Effective date field: MANAGED-CARE-MAIN-REC-EFF-DATE. End date field: MANAGED-CARE-MAIN-REC-END-DATE MANAGED-CARE-MAIN-REC-EFF-DATE,MANAGED-CARE-MAIN-REC-END-DATE MCR030,MCR031











2,259 Retired: Other reasons MCR030-0007
MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR030 MANAGED-CARE-MAIN-REC-EFF-DATE 2 If two or more MANAGED-CARE-MAIN record segments have the same SUBMITTING-STATE and STATE-PLAN-ID-NUM and these record segments are sorted in ascending order by MANAGED-CARE-MAIN-REC-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N MANAGED-CARE-MAIN-REC-END-DATE must = Segment (N+1) MANAGED-CARE-MAIN-REC-EFF-DATE minus 1 day 2453 Edit for contiguous MANAGED-CARE-MAIN record segments failed (Exact match on all key fields except the file segment effective date)

























2,260 Merged MCR031-0002 RULE-2580 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR031 MANAGED-CARE-MAIN-REC-END-DATE 1 If MANAGED-CARE-MAIN-REC-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-MAIN-REC-END-DATE MCR031











2,261 Merged MCR031-0003 RULE-2580 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR031 MANAGED-CARE-MAIN-REC-END-DATE 1 If date is not in CCYYMMDD format 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-MAIN-REC-END-DATE MCR031











2,262 Merged MCR031-0004 RULE-2577 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR031 MANAGED-CARE-MAIN-REC-END-DATE 2-M
2058
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.MANAGED-CARE-MAIN-REC-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-MAIN-REC-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-MAIN-REC-EFF-DATE, @val.MANAGED-CARE-MAIN-REC-END-DATE)' MANAGED-CARE-MAIN-REC-EFF-DATE,MANAGED-CARE-MAIN-REC-END-DATE MCR030,MCR031











2,263 Logic updated: string matching MCR032-0001 RULE-2583 MNGDCARE MANAGED-CARE-MAIN-MCR00002 MCR032 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-MAIN MCR00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR032











2,264 Moved to R&C MCR034-0003
MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR034 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,265 Moved to R&C MCR034-0004
MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR034 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,266 No logic changes MCR035-0002 RULE-2586 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR035 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR035











2,267 Logic updated: other MCR035-0004 RULE-2587 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR035 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR035 SUBMITTING-STATE MCR007









2,268 Retired: Other reasons MCR036-0001
MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR036 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,269 No logic changes MCR036-0002 RULE-2589 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR036 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR036











2,270 No logic changes MCR036-0003 RULE-2590 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR036 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Field RECORD-NUMBER should be unique across all records of type MANAGED-CARE-LOCATION-AND-CONTACT-INFO RECORD-NUMBER MCR036











2,271 Retired: required value checks MCR037-0001
MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR037 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,272 No logic changes MCR037-0002 RULE-7116 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR037 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR037











2,273 Merged MCR037-0003 RULE-2593 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR037 STATE-PLAN-ID-NUM 2 STATE-PLAN-ID-NUM [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] must = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] on any record in the file and SUBMITTING-STATE [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] must = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] on the same record in the file 2205 Edit that MANAGED-CARE-LOCATION-AND-CONTACT-INFO child record has a MANAGED-CARE-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003

record MANAGED-CARE-LOCATION-AND-CONTACT-INFO has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR035,MCR037



2,274 Retired: required value checks MCR038-0001
MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR038 MANAGED-CARE-LOCATION-ID 1 If MCO-LOCATION-ID = spaces 113 Required data element has not been reported.

























2,275 Merged MCR039-0002 RULE-2595 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR039 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE 1 If MCO-LOCATION-AND-CONTACT-INFO-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE MCR039











2,276 Merged MCR039-0004 RULE-2595 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR039 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE MCR039











2,277 Merged MCR039-0006 RULE-2597 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR039 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE 2 MCO-LOCATION-AND-CONTACT-INFO-EFF-DATE must be <= MCO-LOCATION-AND-CONTACT-INFO-END-DATE 2064 Relational edit between MCO-LOCATION-AND-CONTACT-INFO-EFF-DATE and MCO-LOCATION-AND-CONTACT-INFO-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE , @val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE)' MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE,MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE MCR039,MCR040











2,278 No logic changes MCR039-0007 RULE-2598 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR039 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE 2 If two or more MANAGED-CARE-LOCATION-AND-CONTACT-INFO record segments have the same SUBMITTING-STATE, RECORD-NUMBER, STATE-PLAN-ID-NUM, MANAGED-CARE-LOCATION-ID, and MANAGED-CARE-ADDR-TYPE
then for each pair of record segments,
(Segment 1 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE must <> Segment 2 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE)
AND
( (If Segment 1 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE < Segment 2 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE,
then
Segment 1 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE must be < Segment 2 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE)
OR
(If Segment 2 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE < Segment 1 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE,
then
Segment 2 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE must be < Segment 1 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE) )		 2160 Edit for overlapping coverage dates in record segments that have non-unique key fields in MANAGED-CARE-LOCATION-AND-CONTACT-INFO failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Records with the same primary keys must have non-overlapping date ranges. Effective date field: MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE. End date field: MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE,MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE MCR039,MCR040











2,279 Merged MCR039-0009 RULE-2593 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR039 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE 2 ( MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2502 Relational edit between MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE, MANAGED-CARE-MAIN-REC-EFF-DATE, and MANAGED-CARE-MAIN-REC-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003

record MANAGED-CARE-LOCATION-AND-CONTACT-INFO has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR035,MCR037



2,280 Merged MCR040-0002 RULE-2600 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR040 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE 1 If MCO-LOCATION-AND-CONTACT-INFO-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE MCR040











2,281 Merged MCR040-0004 RULE-2600 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR040 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE MCR040











2,282 Merged MCR040-0005 RULE-2597 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR040 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE 2-M
2064
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE , @val.MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE)' MANAGED-CARE-LOCATION-AND-CONTACT-INFO-EFF-DATE,MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE MCR039,MCR040











2,283 Merged MCR040-0007 RULE-2593 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR040 MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE 2 ( MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2503 Relational edit between MANAGED-CARE-LOCATION-AND-CONTACT-INFO-END-DATE, MANAGED-CARE-MAIN-REC-END-DATE, and MANAGED-CARE-MAIN-REC-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003

record MANAGED-CARE-LOCATION-AND-CONTACT-INFO has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR035,MCR037



2,284 No logic changes MCR041-0002 RULE-2604 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR041 MANAGED-CARE-ADDR-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



If the field is populated, the value must be contained in the set of valid values with id: MANAGED-CARE-ADDR-TYPE MANAGED-CARE-ADDR-TYPE MCR041











2,285 Retired: required value checks MCR042-0001
MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR042 MANAGED-CARE-ADDR-LN1 1 If MANAGED-CARE-ADDR-LN1 = spaces 113 Required data element has not been reported.

























2,286 Logic updated: string matching MCR042-0002 RULE-2606 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR042 MANAGED-CARE-ADDR-LN1 1 If MANAGED-CARE-ADDR-LN1 is populated, it must contains valid characters. 120 Field contains invalid characters - MANAGED-CARE-ADDR-LN1 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-ADDR-LN1), then fns.matches(@val.MANAGED-CARE-ADDR-LN1, "^[^|*]*$")' MANAGED-CARE-ADDR-LN1 MCR042











2,287 Logic updated: string matching MCR043-0001 RULE-2607 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR043 MANAGED-CARE-ADDR-LN2 1 If MANAGED-CARE-ADDR-LN2 is populated, it must contains valid characters. 120 Field contains invalid characters - MANAGED-CARE-ADDR-LN2 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-ADDR-LN2), then fns.matches(@val.MANAGED-CARE-ADDR-LN2, "^[^|*]*$")' MANAGED-CARE-ADDR-LN2 MCR043











2,288 Merged MCR043-0003 RULE-2608 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR043 MANAGED-CARE-ADDR-LN2 2 If MANAGED-CARE-ADDR-LN2 is not 8-filled,
then MANAGED-CARE-ADDR-LN2 must <> MANAGED-CARE-ADDR-LN1		 2316 Relational edit between MANAGED-CARE-ADDR-LN2 and MANAGED-CARE-ADDR-LN1
failed (duplicate value entered)		 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



The values of the following fields should be unique (non-repeating) within each record: MANAGED-CARE-ADDR-LN1,MANAGED-CARE-ADDR-LN2,MANAGED-CARE-ADDR-LN3 MANAGED-CARE-ADDR-LN1,MANAGED-CARE-ADDR-LN2,MANAGED-CARE-ADDR-LN3 MCR042,MCR043,MCR044











2,289 Logic updated: string matching MCR044-0001 RULE-2609 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR044 MANAGED-CARE-ADDR-LN3 1 If MANAGED-CARE-ADDR-LN3 is populated, it must contains valid characters. 120 Field contains invalid characters - MANAGED-CARE-ADDR-LN3 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-ADDR-LN3), then fns.matches(@val.MANAGED-CARE-ADDR-LN3, "^[^|*]*$")' MANAGED-CARE-ADDR-LN3 MCR044











2,290 Merged MCR044-0003 RULE-2608 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR044 MANAGED-CARE-ADDR-LN3 2 (If MANAGED-CARE-ADDR-LN3 is not 8-filled,
then MANAGED-CARE-ADDR-LN3 must <> MANAGED-CARE-ADDR-LN1)
AND
(If MANAGED-CARE-ADDR-LN2 is not 8-filled
then MANAGED-CARE-ADDR-LN3 must <> MANAGED-CARE-ADDR-LN2)		 2318 Relational edit between MANAGED-CARE-ADDR-LN3 and MANAGED-CARE-ADDR-LN2 or MANAGED-CARE-ADDR-LN1 failed (duplicate value entered) 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



The values of the following fields should be unique (non-repeating) within each record: MANAGED-CARE-ADDR-LN1,MANAGED-CARE-ADDR-LN2,MANAGED-CARE-ADDR-LN3 MANAGED-CARE-ADDR-LN1,MANAGED-CARE-ADDR-LN2,MANAGED-CARE-ADDR-LN3 MCR042,MCR043,MCR044











2,291 No logic changes MCR044-0004 RULE-2611 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR044 MANAGED-CARE-ADDR-LN3 2 If MANAGED-CARE-ADDR-LN2 is 8-filled, then MANAGED-CARE-ADDR-LN3 must be 8-filled 2317 Relational edit between MANAGED-CARE-ADDR-LN2 and MANAGED-CARE-ADDR-LN3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if !fns.hasValue(@val.MANAGED-CARE-ADDR-LN2), then !fns.hasValue(@val.MANAGED-CARE-ADDR-LN3)' MANAGED-CARE-ADDR-LN2,MANAGED-CARE-ADDR-LN3 MCR043,MCR044











2,292 Retired: required value checks MCR045-0001
MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR045 MANAGED-CARE-CITY 1 If MANAGED-CARE-CITY = spaces 113 Required data element has not been reported.

























2,293 Logic updated: string matching MCR045-0002 RULE-2613 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR045 MANAGED-CARE-CITY 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9), dashes (-), commas (,), periods (.), and spaces. 120 Field contains invalid characters - MANAGED-CARE-CITY 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-CITY), then fns.matches(@val.MANAGED-CARE-CITY, "^[^|*]*$")' MANAGED-CARE-CITY MCR045











2,294 No logic changes MCR046-0003 RULE-2614 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR046 MANAGED-CARE-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



If the field is populated, the value must be contained in the set of valid values with id: STATE MANAGED-CARE-STATE MCR046











2,295 No logic changes MCR047-0002 RULE-2615 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR047 MANAGED-CARE-ZIP-CODE 1 If MANAGED-CARE-ZIP-CODE not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-ZIP-CODE), then fns.matches(@val.MANAGED-CARE-ZIP-CODE, "^[0-9]{5}|[0-9]{9}$")' MANAGED-CARE-ZIP-CODE MCR047











2,296 No logic changes MCR048-0002 RULE-2616 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR048 MANAGED-CARE-COUNTY 1 If MANAGED-CARE-COUNTY not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



If the field is populated, the value must be contained in the set of valid values with id: COUNTY MANAGED-CARE-COUNTY MCR048











2,297 No logic changes MCR049-0003 RULE-7140 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR049 MANAGED-CARE-TELEPHONE 1 MANAGED-CARE-TELEPHONE must not contain parentheses, dashes, periods, commas, spaces 120 Field contains invalid characters - MANAGED-CARE-TELEPHONE 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-TELEPHONE), then fns.isNumericString(@val.MANAGED-CARE-TELEPHONE)' MANAGED-CARE-TELEPHONE MCR049











2,298 No logic changes MCR050-0002 RULE-2618 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR050 MANAGED-CARE-EMAIL 1 If MANAGED-CARE-EMAIL does not contain @ 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-EMAIL), then fns.matches(@val.MANAGED-CARE-EMAIL, "^.*@.*$")' MANAGED-CARE-EMAIL MCR050











2,299 No logic changes MCR051-0003 RULE-7148 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR051 MANAGED-CARE-FAX-NUMBER 1 MANAGED-CARE-FAX-NUMBER must not contain parentheses, dashes, periods, commas, spaces 120 Field contains invalid characters - MANAGED-CARE-FAX-NUMBER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.MANAGED-CARE-FAX-NUMBER), then fns.isNumericString(@val.MANAGED-CARE-FAX-NUMBER)' MANAGED-CARE-FAX-NUMBER MCR051











2,300 Logic updated: string matching MCR052-0001 RULE-2620 MNGDCARE MANAGED-CARE-LOCATION-AND-CONTACT-INFO-MCR00003 MCR052 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR052











2,301 Moved to R&C MCR054-0003
MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR054 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,302 Moved to R&C MCR054-0004
MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR054 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,303 No logic changes MCR055-0002 RULE-2623 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR055 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-SERVICE-AREA MCR00004



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR055











2,304 Logic updated: other MCR055-0004 RULE-2624 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR055 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-SERVICE-AREA MCR00004 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR055 SUBMITTING-STATE MCR007









2,305 Retired: Other reasons MCR056-0001
MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR056 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,306 No logic changes MCR056-0002 RULE-2626 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR056 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR056











2,307 No logic changes MCR056-0003 RULE-2627 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR056 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MANAGED-CARE-SERVICE-AREA MCR00004



Field RECORD-NUMBER should be unique across all records of type MANAGED-CARE-SERVICE-AREA RECORD-NUMBER MCR056











2,308 Retired: required value checks MCR057-0001
MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR057 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,309 Logic updated: string matching MCR057-0002 RULE-2629 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR057 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-SERVICE-AREA MCR00004



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR057











2,310 Merged MCR057-0003 RULE-2630 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR057 STATE-PLAN-ID-NUM 2 STATE-PLAN-ID-NUM [MANAGED-CARE-SERVICE-AREA-MCR00004] must = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] on any record in the file and SUBMITTING-STATE [MANAGED-CARE-SERVICE-AREA-MCR00004] must = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] on the same record in the file 2209 Edit that MANAGED-CARE-SERVICE-AREA child record has a MANAGED-CARE-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-SERVICE-AREA MCR00004

record MANAGED-CARE-SERVICE-AREA has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR055,MCR057



2,311 Retired: required value checks MCR058-0001
MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR058 MANAGED-CARE-SERVICE-AREA-NAME 1 If MANAGE-CARE-SERVICE-AREA-NAME = spaces 113 Required data element has not been reported.

























2,312 Logic updated: string matching MCR058-0006 RULE-2632 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR058 MANAGED-CARE-SERVICE-AREA-NAME 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9), dashes (-), commas (,), periods (.), single quotes ('),and spaces. 120 Field contains invalid characters - MANAGE-CARE-SERVICE-AREA-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-SERVICE-AREA MCR00004



'if fns.hasValue(@val.MANAGED-CARE-SERVICE-AREA-NAME), then fns.matches(@val.MANAGED-CARE-SERVICE-AREA-NAME, "^[^|*]*$")' MANAGED-CARE-SERVICE-AREA-NAME MCR058











2,313 Merged MCR059-0002 RULE-2633 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR059 MANAGED-CARE-SERVICE-AREA-EFF-DATE 1 If MANAGED-CARE-SERVICE-AREA-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-SERVICE-AREA-EFF-DATE MCR059











2,314 Merged MCR059-0004 RULE-2633 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR059 MANAGED-CARE-SERVICE-AREA-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-SERVICE-AREA-EFF-DATE MCR059











2,315 Merged MCR059-0006 RULE-2635 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR059 MANAGED-CARE-SERVICE-AREA-EFF-DATE 2 MANAGED-CARE-SERVICE-AREA-EFF-DATE must be <= MANAGED-CARE-SERVICE-AREA-END-DATE 2063 Relational edit between MANAGED-CARE-SERVICE-AREA-EFF-DATE and MANAGED-CARE-SERVICE-AREA-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-SERVICE-AREA MCR00004



'if fns.hasValue(@val.MANAGED-CARE-SERVICE-AREA-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-SERVICE-AREA-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-SERVICE-AREA-EFF-DATE , @val.MANAGED-CARE-SERVICE-AREA-END-DATE)' MANAGED-CARE-SERVICE-AREA-EFF-DATE,MANAGED-CARE-SERVICE-AREA-END-DATE MCR059,MCR060











2,316 No logic changes MCR059-0007 RULE-2636 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR059 MANAGED-CARE-SERVICE-AREA-EFF-DATE 2 If two or more MANAGED-CARE-SERVICE-AREA record segments have the same SUBMITTING-STATE, STATE-PLAN-ID-NUM, and MANAGED-CARE-SERVICE-AREA-NAME;
then for each pair of record segments,;(Segment 1 MANAGED-CARE-SERVICE-AREA-EFF-DATE must <> Segment 2 MANAGED-CARE-SERVICE-AREA-EFF-DATE);AND;( (If Segment 1 MANAGED-CARE-SERVICE-AREA-EFF-DATE < Segment 2 MANAGED-CARE-SERVICE-AREA-EFF-DATE, ;then;Segment 1 MANAGED-CARE-SERVICE-AREA-END-DATE must be < Segment 2 MANAGED-CARE-SERVICE-AREA-EFF-DATE);OR;(If Segment 2 MANAGED-CARE-SERVICE-AREA-EFF-DATE < Segment 1 MANAGED-CARE-SERVICE-AREA-EFF-DATE, ;then;Segment 2 MANAGED-CARE-SERVICE-AREA-END-DATE must be < Segment 1 MANAGED-CARE-SERVICE-AREA-EFF-DATE) )		 2165 Edit for overlapping coverage dates in record segments that have non-unique key fields in MANAGED-CARE-SERVICE-AREA failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MANAGED-CARE-SERVICE-AREA MCR00004



Records with the same primary keys must have non-overlapping date ranges. Effective date field: MANAGED-CARE-SERVICE-AREA-EFF-DATE. End date field: MANAGED-CARE-SERVICE-AREA-END-DATE MANAGED-CARE-SERVICE-AREA-EFF-DATE,MANAGED-CARE-SERVICE-AREA-END-DATE MCR059,MCR060











2,317 Merged MCR059-0009 RULE-2630 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR059 MANAGED-CARE-SERVICE-AREA-EFF-DATE 2 ( MANAGED-CARE-SERVICE-AREA-EFF-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-SERVICE-AREA-MCR00004] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-SERVICE-AREA-MCR00004] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-SERVICE-AREA-EFF-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-SERVICE-AREA-MCR00004] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-SERVICE-AREA-MCR00004] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2511 Relational edit between MANAGED-CARE-SERVICE-AREA-EFF-DATE, MANAGED-CARE-MAIN-REC-EFF-DATE, and MANAGED-CARE-MAIN-REC-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-SERVICE-AREA MCR00004

record MANAGED-CARE-SERVICE-AREA has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR055,MCR057



2,318 Merged MCR060-0002 RULE-2638 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR060 MANAGED-CARE-SERVICE-AREA-END-DATE 1 If MANAGED-CARE-SERVICE-AREA-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-SERVICE-AREA-END-DATE MCR060











2,319 Merged MCR060-0004 RULE-2638 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR060 MANAGED-CARE-SERVICE-AREA-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-SERVICE-AREA-END-DATE MCR060











2,320 Merged MCR060-0005 RULE-2635 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR060 MANAGED-CARE-SERVICE-AREA-END-DATE 2-M
2063
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-SERVICE-AREA MCR00004



'if fns.hasValue(@val.MANAGED-CARE-SERVICE-AREA-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-SERVICE-AREA-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-SERVICE-AREA-EFF-DATE , @val.MANAGED-CARE-SERVICE-AREA-END-DATE)' MANAGED-CARE-SERVICE-AREA-EFF-DATE,MANAGED-CARE-SERVICE-AREA-END-DATE MCR059,MCR060











2,321 Merged MCR060-0007 RULE-2630 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR060 MANAGED-CARE-SERVICE-AREA-END-DATE 2 ( MANAGED-CARE-SERVICE-AREA-END-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-SERVICE-AREA-MCR00004] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-SERVICE-AREA-MCR00004] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-SERVICE-AREA-END-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-SERVICE-AREA-MCR00004] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-SERVICE-AREA-MCR00004] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2512 Relational edit between MANAGED-CARE-SERVICE-AREA-END-DATE, MANAGED-CARE-MAIN-REC-END-DATE, and MANAGED-CARE-MAIN-REC-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-SERVICE-AREA MCR00004

record MANAGED-CARE-SERVICE-AREA has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR055,MCR057



2,322 Logic updated: string matching MCR061-0001 RULE-2642 MNGDCARE MANAGED-CARE-SERVICE-AREA-MCR00004 MCR061 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-SERVICE-AREA MCR00004



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR061











2,323 Moved to R&C MCR063-0003
MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR063 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,324 Moved to R&C MCR063-0004
MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR063 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,325 No logic changes MCR064-0002 RULE-2645 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR064 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-OPERATING-AUTHORITY MCR00005



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR064











2,326 Logic updated: other MCR064-0004 RULE-2646 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR064 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-OPERATING-AUTHORITY MCR00005 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR064 SUBMITTING-STATE MCR007









2,327 Retired: Other reasons MCR065-0001
MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR065 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,328 No logic changes MCR065-0002 RULE-2648 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR065 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR065











2,329 No logic changes MCR065-0003 RULE-2649 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR065 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Field RECORD-NUMBER should be unique across all records of type MANAGED-CARE-OPERATING-AUTHORITY RECORD-NUMBER MCR065











2,330 Retired: required value checks MCR066-0001
MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR066 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,331 Logic updated: string matching MCR066-0002 RULE-2651 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR066 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-OPERATING-AUTHORITY MCR00005



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR066











2,332 Merged MCR066-0003 RULE-2652 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR066 STATE-PLAN-ID-NUM 2 STATE-PLAN-ID-NUM [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] must = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] on any record in the file and SUBMITTING-STATE [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] must = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] on the same record in the file 2206 Edit that MANAGED-CARE-OPERATING-AUTHORITY child record has a MANAGED-CARE-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-OPERATING-AUTHORITY MCR00005

record MANAGED-CARE-OPERATING-AUTHORITY has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR064,MCR066



2,333 No logic changes MCR067-0002 RULE-2653 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR067 OPERATING-AUTHORITY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-OPERATING-AUTHORITY MCR00005



If the field is populated, the value must be contained in the set of valid values with id: OPERATING-AUTHORITY OPERATING-AUTHORITY MCR067











2,334 Merged MCR068-0001 RULE-2654 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR068 WAIVER-ID 1 Value is not included a state supplied valid code list 125 Value is not included in a state supplied valid code list 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value MANAGED-CARE-OPERATING-AUTHORITY MCR00005



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID MCR068











2,335 Merged MCR068-0002 RULE-2654 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR068 WAIVER-ID 3 WAIVER-ID must = waiver ID in state-provided crosswalk 3030 Edit with an external reference (state provided WAIVER-ID-/WAIVER-TYPE crosswalk) failed 1.1 Value Error E1104 Value not valid for state-supplied format (format or valid values) Valid Value MANAGED-CARE-OPERATING-AUTHORITY MCR00005



If the field is populated, the value must be contained in the set of valid values with id: WAIVER-ID WAIVER-ID MCR068











2,336 Merged MCR069-0002 RULE-2656 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR069 MANAGED-CARE-OP-AUTHORITY-EFF-DATE 1 If MANAGED-CARE-OP-AUTHORITY-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-OP-AUTHORITY-EFF-DATE MCR069











2,337 Merged MCR069-0004 RULE-2656 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR069 MANAGED-CARE-OP-AUTHORITY-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-OP-AUTHORITY-EFF-DATE MCR069











2,338 Merged MCR069-0005 RULE-2658 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR069 MANAGED-CARE-OP-AUTHORITY-EFF-DATE 2 MANAGED-CARE-OP-AUTHORITY-EFF-DATE must be <= MANAGED-CARE-OP-AUTHORITY-END-DATE 2059 Relational edit between MANAGED-CARE-OP-AUTHORITY-EFF-DATE and MANAGED-CARE-OP-AUTHORITY-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-OPERATING-AUTHORITY MCR00005



'if fns.hasValue(@val.MANAGED-CARE-OP-AUTHORITY-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-OP-AUTHORITY-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-OP-AUTHORITY-EFF-DATE, @val.MANAGED-CARE-OP-AUTHORITY-END-DATE)' MANAGED-CARE-OP-AUTHORITY-EFF-DATE,MANAGED-CARE-OP-AUTHORITY-END-DATE MCR069,MCR070











2,339 No logic changes MCR069-0007 RULE-2659 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR069 MANAGED-CARE-OP-AUTHORITY-EFF-DATE 2 If two or more MANAGED-CARE-OPERATING-AUTHORITY record segments have the same SUBMITTING-STATE, STATE-PLAN-ID-NUM, and OPERATING-AUTHORITY
then for each pair of record segments,
(Segment 1 MANAGED-CARE-OP-AUTHORITY-EFF-DATE must <> Segment 2 MANAGED-CARE-OP-AUTHORITY-EFF-DATE)
AND
( (If Segment 1 MANAGED-CARE-OP-AUTHORITY-EFF-DATE < Segment 2 MANAGED-CARE-OP-AUTHORITY-EFF-DATE,
then
Segment 1 MANAGED-CARE-OP-AUTHORITY-END-DATE must be < Segment 2 MANAGED-CARE-OP-AUTHORITY-EFF-DATE)
OR
(If Segment 2 MANAGED-CARE-OP-AUTHORITY-EFF-DATE < Segment 1 MANAGED-CARE-OP-AUTHORITY-EFF-DATE,
then
Segment 2 MANAGED-CARE-OP-AUTHORITY-END-DATE must be < Segment 1 MANAGED-CARE-OP-AUTHORITY-EFF-DATE) )		 2162 Edit for overlapping coverage dates in record segments that have non-unique key fields in MANAGED-CARE-OPERATING-AUTHORITY failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Records with the same primary keys must have non-overlapping date ranges. Effective date field: MANAGED-CARE-OP-AUTHORITY-EFF-DATE. End date field: MANAGED-CARE-OP-AUTHORITY-END-DATE MANAGED-CARE-OP-AUTHORITY-EFF-DATE,MANAGED-CARE-OP-AUTHORITY-END-DATE MCR069,MCR070











2,340 Merged MCR069-0009 RULE-2652 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR069 MANAGED-CARE-OP-AUTHORITY-EFF-DATE 2 ( MANAGED-CARE-OP-AUTHORITY-EFF-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-OP-AUTHORITY-EFF-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2504 Relational edit between MANAGED-CARE-OP-AUTHORITY-EFF-DATE, MANAGED-CARE-MAIN-REC-EFF-DATE, and MANAGED-CARE-MAIN-REC-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-OPERATING-AUTHORITY MCR00005

record MANAGED-CARE-OPERATING-AUTHORITY has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR064,MCR066



2,341 Merged MCR070-0002 RULE-2661 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR070 MANAGED-CARE-OP-AUTHORITY-END-DATE 1 If MANAGED-CARE-OP-AUTHORITY-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-OP-AUTHORITY-END-DATE MCR070











2,342 Merged MCR070-0004 RULE-2661 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR070 MANAGED-CARE-OP-AUTHORITY-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-OP-AUTHORITY-END-DATE MCR070











2,343 Merged MCR070-0005 RULE-2658 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR070 MANAGED-CARE-OP-AUTHORITY-END-DATE 2-M
2059
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-OPERATING-AUTHORITY MCR00005



'if fns.hasValue(@val.MANAGED-CARE-OP-AUTHORITY-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-OP-AUTHORITY-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-OP-AUTHORITY-EFF-DATE, @val.MANAGED-CARE-OP-AUTHORITY-END-DATE)' MANAGED-CARE-OP-AUTHORITY-EFF-DATE,MANAGED-CARE-OP-AUTHORITY-END-DATE MCR069,MCR070











2,344 Merged MCR070-0007 RULE-2652 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR070 MANAGED-CARE-OP-AUTHORITY-END-DATE 2 ( MANAGED-CARE-OP-AUTHORITY-END-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-OP-AUTHORITY-END-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-OPERATING-AUTHORITY-MCR00005] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2505 Relational edit between MANAGED-CARE-OP-AUTHORITY-END-DATE, MANAGED-CARE-MAIN-REC-END-DATE, and MANAGED-CARE-MAIN-REC-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-OPERATING-AUTHORITY MCR00005

record MANAGED-CARE-OPERATING-AUTHORITY has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR064,MCR066



2,345 Logic updated: string matching MCR071-0001 RULE-2665 MNGDCARE MANAGED-CARE-OPERATING-AUTHORITY-MCR00005 MCR071 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-OPERATING-AUTHORITY MCR00005



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR071











2,346 Moved to R&C MCR073-0003
MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR073 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,347 Moved to R&C MCR073-0004
MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR073 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,348 No logic changes MCR074-0002 RULE-2668 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR074 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR074











2,349 Logic updated: other MCR074-0004 RULE-2669 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR074 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR074 SUBMITTING-STATE MCR007









2,350 Retired: Other reasons MCR075-0001
MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR075 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,351 No logic changes MCR075-0002 RULE-2671 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR075 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR075











2,352 No logic changes MCR075-0003 RULE-2672 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR075 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Field RECORD-NUMBER should be unique across all records of type MANAGED-CARE-PLAN-POPULATION-ENROLLED RECORD-NUMBER MCR075











2,353 Retired: required value checks MCR076-0001
MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR076 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,354 Logic updated: string matching MCR076-0002 RULE-2674 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR076 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR076











2,355 Merged MCR076-0003 RULE-2675 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR076 STATE-PLAN-ID-NUM 2 STATE-PLAN-ID-NUM [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] must = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] on any record in the file and SUBMITTING-STATE [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] must = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] on the same record in the file 2208 Edit that MANAGED-CARE-PLAN-POPULATION-ENROLLED child record has a MANAGED-CARE-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006

record MANAGED-CARE-PLAN-POPULATION-ENROLLED has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR074,MCR076



2,356 No logic changes MCR077-0002 RULE-2676 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR077 MANAGED-CARE-PLAN-POP 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



If the field is populated, the value must be contained in the set of valid values with id: ELIGIBILITY-GROUP MANAGED-CARE-PLAN-POP MCR077











2,357 Merged MCR078-0002 RULE-2677 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR078 MANAGED-CARE-PLAN-POP-EFF-DATE 1 If MANAGED-CARE-PLAN-POP-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-POP-EFF-DATE MCR078











2,358 Merged MCR078-0004 RULE-2677 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR078 MANAGED-CARE-PLAN-POP-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-POP-EFF-DATE MCR078











2,359 Merged MCR078-0006 RULE-2679 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR078 MANAGED-CARE-PLAN-POP-EFF-DATE 2 MANAGED-CARE-PLAN-POP-EFF-DATE must be <= MANAGED-CARE-POP-END-DATE 2062 Relational edit between MANAGED-CARE-PLAN-POP-EFF-DATE and MANAGED-CARE-PLAN-POP-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



'if fns.hasValue(@val.MANAGED-CARE-PLAN-POP-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-PLAN-POP-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-PLAN-POP-EFF-DATE, @val.MANAGED-CARE-PLAN-POP-END-DATE)' MANAGED-CARE-PLAN-POP-EFF-DATE,MANAGED-CARE-PLAN-POP-END-DATE MCR078,MCR079











2,360 No logic changes MCR078-0007 RULE-2680 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR078 MANAGED-CARE-PLAN-POP-EFF-DATE 2 If two or more MANAGED-CARE-PLAN-POPULATION-ENROLLED record segments have the same SUBMITTING-STATE, STATE-PLAN-ID-NUM, and MANAGED-CARE-PLAN-POP
then for each pair of record segments,
(Segment 1 MANAGED-CARE-PLAN-POP-EFF-DATE must <> Segment 2 MANAGED-CARE-PLAN-POP-EFF-DATE)
AND
( (If Segment 1 MANAGED-CARE-PLAN-POP-EFF-DATE < Segment 2 MANAGED-CARE-PLAN-POP-EFF-DATE,
then
Segment 1 MANAGED-CARE-PLAN-POP-END-DATE must be < Segment 2 MANAGED-CARE-PLAN-POP-EFF-DATE)
OR
(If Segment 2 MANAGED-CARE-PLAN-POP-EFF-DATE < Segment 1 MANAGED-CARE-PLAN-POP-EFF-DATE,
then
Segment 2 MANAGED-CARE-PLAN-POP-END-DATE must be < Segment 1 MANAGED-CARE-PLAN-POP-EFF-DATE) )		 2164 Edit for overlapping coverage dates in record segments that have non-unique key fields in MANAGED-CARE-PLAN-POPULATION-ENROLLED failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Records with the same primary keys must have non-overlapping date ranges. Effective date field: MANAGED-CARE-PLAN-POP-EFF-DATE. End date field: MANAGED-CARE-PLAN-POP-END-DATE MANAGED-CARE-PLAN-POP-EFF-DATE,MANAGED-CARE-PLAN-POP-END-DATE MCR078,MCR079











2,361 Merged MCR078-0009 RULE-2675 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR078 MANAGED-CARE-PLAN-POP-EFF-DATE 2 ( MANAGED-CARE-PLAN-POP-EFF-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-PLAN-POP-EFF-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2509 Relational edit between MANAGED-CARE-PLAN-POP-EFF-DATE, MANAGED-CARE-MAIN-REC-EFF-DATE, and MANAGED-CARE-MAIN-REC-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006

record MANAGED-CARE-PLAN-POPULATION-ENROLLED has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR074,MCR076



2,362 Merged MCR079-0002 RULE-2682 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR079 MANAGED-CARE-PLAN-POP-END-DATE 1 If MANAGED-CARE-PLAN-POP-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-POP-END-DATE MCR079











2,363 Merged MCR079-0004 RULE-2682 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR079 MANAGED-CARE-PLAN-POP-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be a valid date of the form CCYYMMDD MANAGED-CARE-PLAN-POP-END-DATE MCR079











2,364 Merged MCR079-0005 RULE-2679 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR079 MANAGED-CARE-PLAN-POP-END-DATE 2-M
2062
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



'if fns.hasValue(@val.MANAGED-CARE-PLAN-POP-EFF-DATE) && fns.hasValue(@val.MANAGED-CARE-PLAN-POP-END-DATE), then fns.isLessThanOrEqual(@val.MANAGED-CARE-PLAN-POP-EFF-DATE, @val.MANAGED-CARE-PLAN-POP-END-DATE)' MANAGED-CARE-PLAN-POP-EFF-DATE,MANAGED-CARE-PLAN-POP-END-DATE MCR078,MCR079











2,365 Merged MCR079-0007 RULE-2675 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR079 MANAGED-CARE-PLAN-POP-END-DATE 2 ( MANAGED-CARE-PLAN-POP-END-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( MANAGED-CARE-PLAN-POP-END-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2510 Relational edit between MANAGED-CARE-PLAN-POP-END-DATE, MANAGED-CARE-MAIN-REC-END-DATE, and MANAGED-CARE-MAIN-REC-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006

record MANAGED-CARE-PLAN-POPULATION-ENROLLED has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR074,MCR076



2,366 Logic updated: string matching MCR080-0001 RULE-2686 MNGDCARE MANAGED-CARE-PLAN-POPULATION-ENROLLED-MCR00006 MCR080 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR080











2,367 Moved to R&C MCR082-0003
MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR082 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,368 Moved to R&C MCR082-0004
MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR082 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,369 No logic changes MCR083-0002 RULE-2689 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR083 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR083











2,370 Logic updated: other MCR083-0004 RULE-2690 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR083 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR083 SUBMITTING-STATE MCR007









2,371 Retired: Other reasons MCR084-0001
MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR084 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,372 No logic changes MCR084-0002 RULE-2692 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR084 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR084











2,373 No logic changes MCR084-0003 RULE-2693 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR084 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Field RECORD-NUMBER should be unique across all records of type MANAGED-CARE-ACCREDITATION-ORGANIZATION RECORD-NUMBER MCR084











2,374 Retired: required value checks MCR085-0001
MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR085 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,375 Logic updated: string matching MCR085-0002 RULE-2695 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR085 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR085











2,376 Merged MCR085-0003 RULE-2696 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR085 STATE-PLAN-ID-NUM 2 STATE-PLAN-ID-NUM [MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007] must = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] on any record in the file and SUBMITTING-STATE [MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007] must = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] on the same record in the file 2204 Edit that MANAGED- CARE-ACCREDITATION-ORGANIZATION child record has a MANAGED-CARE-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007

record MANAGED-CARE-ACCREDITATION-ORGANIZATION has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR083,MCR085



2,377 No logic changes MCR086-0002 RULE-2697 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR086 ACCREDITATION-ORGANIZATION 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



If the field is populated, the value must be contained in the set of valid values with id: ACCREDITATION-ORGANIZATION ACCREDITATION-ORGANIZATION MCR086











2,378 Merged MCR087-0002 RULE-2698 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR087 DATE-ACCREDITATION-ACHIEVED 1 If DATE-ACCREDITATION-ACHIEVED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be a valid date of the form CCYYMMDD DATE-ACCREDITATION-ACHIEVED MCR087











2,379 Merged MCR087-0003 RULE-2698 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR087 DATE-ACCREDITATION-ACHIEVED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be a valid date of the form CCYYMMDD DATE-ACCREDITATION-ACHIEVED MCR087











2,380 Merged MCR087-0005 RULE-2700 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR087 DATE-ACCREDITATION-ACHIEVED 2 DATE-ACCREDITATION-ACHIEVED must be <= DATE-ACCREDITATION-END 2017 Relational edit between DATE-ACCREDITATION-ACHIEVED and DATE-ACCREDITATION-END failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



'if fns.hasValue(@val.DATE-ACCREDITATION-ACHIEVED) && fns.hasValue(@val.DATE-ACCREDITATION-END), then fns.isLessThanOrEqual(@val.DATE-ACCREDITATION-ACHIEVED, @val.DATE-ACCREDITATION-END)' DATE-ACCREDITATION-ACHIEVED,DATE-ACCREDITATION-END MCR087,MCR088











2,381 No logic changes MCR087-0006 RULE-2701 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR087 DATE-ACCREDITATION-ACHIEVED 2 If two or more MANAGED- CARE-ACCREDITATION-ORGANIZATION record segments have the same SUBMITTING-STATE, STATE-PLAN-ID-NUM, and ACCREDITATION-ORGANIZATION
then for each pair of record segments,
(Segment 1 DATE-ACCREDITATION-ACHIEVED must <> Segment 2 DATE-ACCREDITATION-ACHIEVED)
AND
( (If Segment 1 DATE-ACCREDITATION-ACHIEVED < Segment 2 DATE-ACCREDITATION-ACHIEVED,
then
Segment 1 DATE-ACCREDITATION-END must be < Segment 2 DATE-ACCREDITATION-ACHIEVED)
OR
(If Segment 2 DATE-ACCREDITATION-ACHIEVED < Segment 1 DATE-ACCREDITATION-ACHIEVED,
then
Segment 2 DATE-ACCREDITATION-END must be < Segment 1 DATE-ACCREDITATION-ACHIEVED) )		 2159 Edit for overlapping coverage dates in record segments that have non-unique key fields in MANAGED- CARE-ACCREDITATION-ORGANIZATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Records with the same primary keys must have non-overlapping date ranges. Effective date field: DATE-ACCREDITATION-ACHIEVED. End date field: DATE-ACCREDITATION-END DATE-ACCREDITATION-ACHIEVED,DATE-ACCREDITATION-END MCR087,MCR088











2,382 Merged MCR087-0008 RULE-2696 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR087 DATE-ACCREDITATION-ACHIEVED 2 ( DATE-ACCREDITATION-ACHIEVED must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( DATE-ACCREDITATION-ACHIEVED must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-ACCREDITATION-ORGANIZATION-MCR00007] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-ACCREDITATION-ORGANIZATION-MCR00007] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2468 Relational edit between DATE-ACCREDITATION-ACHIEVED, MANAGED-CARE-MAIN-REC-EFF-DATE, and MANAGED-CARE-MAIN-REC-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007

record MANAGED-CARE-ACCREDITATION-ORGANIZATION has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR083,MCR085



2,383 Merged MCR088-0002 RULE-2703 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR088 DATE-ACCREDITATION-END 1 If DATE-ACCREDITATION-END is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be a valid date of the form CCYYMMDD DATE-ACCREDITATION-END MCR088











2,384 Merged MCR088-0003 RULE-2703 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR088 DATE-ACCREDITATION-END 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be a valid date of the form CCYYMMDD DATE-ACCREDITATION-END MCR088











2,385 Merged MCR088-0004 RULE-2700 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR088 DATE-ACCREDITATION-END 2-M
2017
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



'if fns.hasValue(@val.DATE-ACCREDITATION-ACHIEVED) && fns.hasValue(@val.DATE-ACCREDITATION-END), then fns.isLessThanOrEqual(@val.DATE-ACCREDITATION-ACHIEVED, @val.DATE-ACCREDITATION-END)' DATE-ACCREDITATION-ACHIEVED,DATE-ACCREDITATION-END MCR087,MCR088











2,386 Merged MCR088-0006 RULE-2696 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR088 DATE-ACCREDITATION-END 2 ( DATE-ACCREDITATION-END must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( DATE-ACCREDITATION-END must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [MANAGED-CARE-ACCREDITATION-ORGANIZATION-MCR00007] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [MANAGED-CARE-ACCREDITATION-ORGANIZATION-MCR00007] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2469 Relational edit between DATE-ACCREDITATION-END, MANAGED-CARE-MAIN-REC-END-DATE, and MANAGED-CARE-MAIN-REC-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007

record MANAGED-CARE-ACCREDITATION-ORGANIZATION has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR083,MCR085



2,387 Logic updated: string matching MCR089-0001 RULE-2707 MNGDCARE MANAGED- CARE-ACCREDITATION-ORGANIZATION-MCR00007 MCR089 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR089











2,388 Moved to R&C MCR091-0003
MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR091 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,389 Moved to R&C MCR091-0004
MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR091 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,390 No logic changes MCR092-0002 RULE-2710 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR092 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR092











2,391 Logic updated: other MCR092-0004 RULE-2711 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR092 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR092 SUBMITTING-STATE MCR007









2,392 Retired: Other reasons MCR093-0001
MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR093 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,393 No logic changes MCR093-0002 RULE-2713 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR093 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR093











2,394 No logic changes MCR093-0003 RULE-2714 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR093 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Field RECORD-NUMBER should be unique across all records of type NATIONAL-HEALTH-CARE-ENTITY-ID-INFO RECORD-NUMBER MCR093











2,395 Retired: required value checks MCR094-0001
MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR094 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,396 Logic updated: string matching MCR094-0002 RULE-2716 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR094 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR094











2,397 Merged MCR094-0003 RULE-2717 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR094 STATE-PLAN-ID-NUM 2 STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] must = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] on any record in the file and SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] must = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] on the same record in the file 2211 Edit that NATIONAL-HEALTH-CARE-ENTITY-ID-INFO child record has a MANAGED-CARE-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008

record NATIONAL-HEALTH-CARE-ENTITY-ID-INFO has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR092,MCR094



2,398 Logic updated: string matching MCR095-0002 RULE-2718 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR095 NATIONAL-HEALTH-CARE-ENTITY-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-ID, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-ID MCR095











2,399 No logic changes MCR095-0007 RULE-2719 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR095 NATIONAL-HEALTH-CARE-ENTITY-ID 2 If START-OF-TIME-PERIOD >= 20151105, then NATIONAL-HEALTH-CARE-ENTITY-ID must not be 8-filled 2332 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.isGreaterThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, "2015-11-05"), then fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID MCR095 START-OF-TIME-PERIOD MCR009









2,400 No logic changes MCR096-0001 RULE-2720 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR096 NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



If the field is populated, the value must be contained in the set of valid values with id: NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE MCR096











2,401 Retired: required value checks MCR097-0001
MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR097 NATIONAL-HEALTH-CARE-ENTITY-NAME 1 If NATIONAL-HEALTH-CARE-ENTITY-NAME = spaces 113 Required data element has not been reported.

























2,402 Logic updated: string matching MCR097-0002 RULE-2722 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR097 NATIONAL-HEALTH-CARE-ENTITY-NAME 1 NATIIONAL-HEALTH-CARE-ENTITY-NAME must contains valid characters. 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-NAME), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-NAME, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-NAME MCR097











2,403 Merged MCR098-0002 RULE-2723 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR098 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE 1 If NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE s not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be a valid date of the form CCYYMMDD NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE MCR098











2,404 Merged MCR098-0004 RULE-2723 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR098 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be a valid date of the form CCYYMMDD NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE MCR098











2,405 Merged MCR098-0006 RULE-2725 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR098 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE 2 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE must be <= NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE 2068 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE and NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE) && fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE), then fns.isLessThanOrEqual(@val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE, @val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE)' NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE,NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE MCR098,MCR099











2,406 No logic changes MCR098-0008 RULE-2726 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR098 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE 2 If two or more NATIONAL-HEALTH-CARE-ENTITY-ID-INFO record segments have the same SUBMITTING-STATE, STATE-PLAN-ID-NUM, NATIONAL-HEALTH-CARE-ENTITY-ID, and NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE
then for each pair of record segments,
(Segment 1 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE must <> Segment 2 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE)
AND
( (If Segment 1 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE < Segment 2 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE,
then
Segment 1 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE must be < Segment 2 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE)
OR
(If Segment 2 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE < Segment 1 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE,
then
Segment 2 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE must be < Segment 1 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE) )		 2167 Edit for overlapping coverage dates in record segments that have non-unique key fields in NATIONAL-HEALTH-CARE-ENTITY-ID-INFO failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Records with the same primary keys must have non-overlapping date ranges. Effective date field: NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE. End date field: NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE,NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE MCR098,MCR099











2,407 Retired: Other reasons MCR098-0010
MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR098 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE 2 If two or more NATIONAL-HEALTH-CARE-ENTITY-ID-INFO record segments have the same SUBMITTING-STATE, STATE-PLAN-ID-NUM, NATIONAL-HEALTH-CARE-ENTITY-ID, and NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE and these record segments are sorted in ascending order by NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE must = Segment (N+1) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE minus 1 day 2454 Edit for contiguous NATIONAL-HEALTH-CARE-ENTITY-ID-INFO record segments failed (Exact match on all key fields except the file segment effective date)

























2,408 Merged MCR098-0011 RULE-2717 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR098 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE 2 ( NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2517 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE, MANAGED-CARE-MAIN-REC-EFF-DATE, and MANAGED-CARE-MAIN-REC-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008

record NATIONAL-HEALTH-CARE-ENTITY-ID-INFO has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR092,MCR094



2,409 Merged MCR099-0002 RULE-2729 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR099 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE 1 If NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE s not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be a valid date of the form CCYYMMDD NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE MCR099











2,410 Merged MCR099-0004 RULE-2729 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR099 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be a valid date of the form CCYYMMDD NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE MCR099











2,411 Merged MCR099-0005 RULE-2725 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR099 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE 2-M
2068
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE) && fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE), then fns.isLessThanOrEqual(@val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE, @val.NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE)' NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE,NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE MCR098,MCR099











2,412 Merged MCR099-0007 RULE-2717 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR099 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE 2 ( NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE must be <= MANAGED-CARE-MAIN-REC-END-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] ) AND
( NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE must be >= MANAGED-CARE-MAIN-REC-EFF-DATE on any MANAGED-CARE-MAIN segment
where SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] and STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] = STATE-PLAN-ID-NUM [MANAGED-CARE-MAIN-MCR00002] )		 2518 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE, MANAGED-CARE-MAIN-REC-END-DATE, and MANAGED-CARE-MAIN-REC-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule MANAGED-CARE-MAIN MCR00002 NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008

record NATIONAL-HEALTH-CARE-ENTITY-ID-INFO has corresponding parent record MANAGED-CARE-MAIN





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR092,MCR094



2,413 Logic updated: string matching MCR100-0001 RULE-2733 MNGDCARE NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008 MCR100 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR100











2,414 Moved to R&C MCR102-0003
MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR102 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























2,415 Moved to R&C MCR102-0004
MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR102 RECORD-ID 2 If FILE-NAME = "MNGDCARE", then the first 3 positions of RECORD-ID must = "MCR" 150 Invalid or missing RECORD-ID

























2,416 Merged MCR103-0002 RULE-2736 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR103 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value CHPID-SHPID-RELATIONSHIPS MCR00009



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR103











2,417 Merged MCR103-0003 RULE-2736 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR103 SUBMITTING-STATE 1 If SUBMITTING-STATE not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1103 Value not in specified valid value set Valid Value CHPID-SHPID-RELATIONSHIPS MCR00009



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE MCR103











2,418 Logic updated: other MCR103-0004 RULE-2738 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR103 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-MANAGED-CARE-MCR00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CHPID-SHPID-RELATIONSHIPS MCR00009 FILE-HEADER-RECORD-MANAGED-CARE MCR00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE MCR103 SUBMITTING-STATE MCR007









2,419 Retired: Other reasons MCR104-0001
MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR104 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























2,420 No logic changes MCR104-0002 RULE-2740 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR104 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR104











2,421 No logic changes MCR104-0003 RULE-2741 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR104 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) CHPID-SHPID-RELATIONSHIPS MCR00009



Field RECORD-NUMBER should be unique across all records of type CHPID-SHPID-RELATIONSHIPS RECORD-NUMBER MCR104











2,422 Retired: required value checks MCR105-0001
MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR105 STATE-PLAN-ID-NUM 1 If STATE-PLAN-ID-NUM = spaces 113 Required data element has not been reported.

























2,423 Logic updated: string matching MCR105-0002 RULE-2743 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR105 STATE-PLAN-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - STATE-PLAN-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CHPID-SHPID-RELATIONSHIPS MCR00009



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR105











2,424 Merged MCR105-0003 RULE-2744 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR105 STATE-PLAN-ID-NUM 2 STATE-PLAN-ID-NUM [CHPID-SHPID-RELATIONSHIPS-MCR00009] must = STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] on any record in the file and SUBMITTING-STATE [CHPID-SHPID-RELATIONSHIPS-MCR00009] must = SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] on the same record in the file 2188 Edit that CHPID-SHPID-RELATIONSHIPS child record has a NATIONAL-HEALTH-CARE-ENTITY-ID-INFO parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008 CHPID-SHPID-RELATIONSHIPS MCR00009

record CHPID-SHPID-RELATIONSHIPS has corresponding parent record NATIONAL-HEALTH-CARE-ENTITY-ID-INFO





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR092,MCR094 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR103,MCR105



2,425 Retired: required value checks MCR106-0001
MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR106 CHPID 1 If CHPID = spaces 113 Required data element has not been reported.

























2,426 Retired: required value checks MCR107-0001
MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR107 SHPID 1 If SHPID = spaces 113 Required data element has not been reported.

























2,427 Merged MCR108-0002 RULE-2747 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR108 CHPID-SHPID-RELATIONSHIP-EFF-DATE 1 Value is out of range if CHPID-SHPID-RELATIONSHIP-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be a valid date of the form CCYYMMDD CHPID-SHPID-RELATIONSHIP-EFF-DATE MCR108











2,428 Merged MCR108-0004 RULE-2747 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR108 CHPID-SHPID-RELATIONSHIP-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be a valid date of the form CCYYMMDD CHPID-SHPID-RELATIONSHIP-EFF-DATE MCR108











2,429 Merged MCR108-0006 RULE-2749 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR108 CHPID-SHPID-RELATIONSHIP-EFF-DATE 2 CHPID-SHPID-RELATIONSHIP-EFF-DATE must be <= CHPID-SHPID-RELATIONSHIP-END-DATE 2015 Relational edit between CHPID-SHPID-RELATIONSHIP-EFF-DATE and CHPID-SHPID-RELATIONSHIP-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CHPID-SHPID-RELATIONSHIPS MCR00009



'if fns.hasValue(@val.CHPID-SHPID-RELATIONSHIP-EFF-DATE) && fns.hasValue(@val.CHPID-SHPID-RELATIONSHIP-END-DATE), then fns.isLessThanOrEqual(@val.CHPID-SHPID-RELATIONSHIP-EFF-DATE, @val.CHPID-SHPID-RELATIONSHIP-END-DATE)' CHPID-SHPID-RELATIONSHIP-EFF-DATE,CHPID-SHPID-RELATIONSHIP-END-DATE MCR108,MCR109











2,430 No logic changes MCR108-0007 RULE-2750 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR108 CHPID-SHPID-RELATIONSHIP-EFF-DATE 2 If two or more CHPID-SHPID-RELATIONSHIPS record segments have the same SUBMITTING-STATE, STATE-PLAN-ID-NUM, CHPID, and SHPID
then for each pair of record segments,
(Segment 1 CHPID-SHPID-RELATIONSHIP-EFF-DATE must <> Segment 2 CHPID-SHPID-RELATIONSHIP-EFF-DATE)
AND
( (If Segment 1 CHPID-SHPID-RELATIONSHIP-EFF-DATE < Segment 2 CHPID-SHPID-RELATIONSHIP-EFF-DATE,
then
Segment 1 CHPID-SHPID-RELATIONSHIP-END-DATE must be < Segment 2 CHPID-SHPID-RELATIONSHIP-EFF-DATE)
OR
(If Segment 2 CHPID-SHPID-RELATIONSHIP-EFF-DATE < Segment 1 CHPID-SHPID-RELATIONSHIP-EFF-DATE,
then
Segment 2 CHPID-SHPID-RELATIONSHIP-END-DATE must be < Segment 1 CHPID-SHPID-RELATIONSHIP-EFF-DATE) )		 2148 Edit for overlapping coverage dates in record segments that have non-unique key fields in CHPID-SHPID-RELATIONSHIPS failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) CHPID-SHPID-RELATIONSHIPS MCR00009



Records with the same primary keys must have non-overlapping date ranges. Effective date field: CHPID-SHPID-RELATIONSHIP-EFF-DATE. End date field: CHPID-SHPID-RELATIONSHIP-END-DATE CHPID-SHPID-RELATIONSHIP-EFF-DATE,CHPID-SHPID-RELATIONSHIP-END-DATE MCR108,MCR109











2,431 Merged MCR108-0009 RULE-2744 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR108 CHPID-SHPID-RELATIONSHIP-EFF-DATE 2 ( CHPID-SHPID-RELATIONSHIP-EFF-DATE must be >= NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE on any NATIONAL-HEALTH-CARE-ENTITY-ID-INFO segment
where SUBMITTING-STATE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and STATE-PLAN-ID-NUM [CHPID-SHPID-RELATIONSHIPS-MCR00009] = STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] ) AND
( CHPID-SHPID-RELATIONSHIP-EFF-DATE must be <= NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE on any NATIONAL-HEALTH-CARE-ENTITY-ID-INFO segment
where SUBMITTING-STATE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and STATE-PLAN-ID-NUM [CHPID-SHPID-RELATIONSHIPS-MCR00009] = STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] )		 2466 Relational edit between CHPID-SHPID-RELATIONSHIP-EFF-DATE, NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE, and NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008 CHPID-SHPID-RELATIONSHIPS MCR00009

record CHPID-SHPID-RELATIONSHIPS has corresponding parent record NATIONAL-HEALTH-CARE-ENTITY-ID-INFO





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR092,MCR094 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR103,MCR105



2,432 Merged MCR109-0002 RULE-2752 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR109 CHPID-SHPID-RELATIONSHIP-END-DATE 1 Value is out of range if CHPID-SHPID-RELATIONSHIP-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be a valid date of the form CCYYMMDD CHPID-SHPID-RELATIONSHIP-END-DATE MCR109











2,433 Merged MCR109-0004 RULE-2752 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR109 CHPID-SHPID-RELATIONSHIP-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be a valid date of the form CCYYMMDD CHPID-SHPID-RELATIONSHIP-END-DATE MCR109











2,434 Merged MCR109-0005 RULE-2749 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR109 CHPID-SHPID-RELATIONSHIP-END-DATE 2-M
2015
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CHPID-SHPID-RELATIONSHIPS MCR00009



'if fns.hasValue(@val.CHPID-SHPID-RELATIONSHIP-EFF-DATE) && fns.hasValue(@val.CHPID-SHPID-RELATIONSHIP-END-DATE), then fns.isLessThanOrEqual(@val.CHPID-SHPID-RELATIONSHIP-EFF-DATE, @val.CHPID-SHPID-RELATIONSHIP-END-DATE)' CHPID-SHPID-RELATIONSHIP-EFF-DATE,CHPID-SHPID-RELATIONSHIP-END-DATE MCR108,MCR109











2,435 Merged MCR109-0007 RULE-2744 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR109 CHPID-SHPID-RELATIONSHIP-END-DATE 2 ( CHPID-SHPID-RELATIONSHIP-END-DATE must be <= NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE on any NATIONAL-HEALTH-CARE-ENTITY-ID-INFO segment
where SUBMITTING-STATE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and STATE-PLAN-ID-NUM [CHPID-SHPID-RELATIONSHIPS-MCR00009] = STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] ) AND
( CHPID-SHPID-RELATIONSHIP-END-DATE must be >= NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE on any NATIONAL-HEALTH-CARE-ENTITY-ID-INFO segment
where SUBMITTING-STATE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = SUBMITTING-STATE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and STATE-PLAN-ID-NUM [CHPID-SHPID-RELATIONSHIPS-MCR00009] = STATE-PLAN-ID-NUM [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] and NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [CHPID-SHPID-RELATIONSHIPS-MCR00009] = NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE [NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-MCR00008] )		 2467 Relational edit between CHPID-SHPID-RELATIONSHIP-END-DATE, NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-END-DATE, and NATIONAL-HEALTH-CARE-ENTITY-ID-INFO-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008 CHPID-SHPID-RELATIONSHIPS MCR00009

record CHPID-SHPID-RELATIONSHIPS has corresponding parent record NATIONAL-HEALTH-CARE-ENTITY-ID-INFO





SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR092,MCR094 SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR103,MCR105



2,436 Logic updated: string matching MCR110-0001 RULE-2756 MNGDCARE CHPID-SHPID-RELATIONSHIPS-MCR00009 MCR110 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CHPID-SHPID-RELATIONSHIPS MCR00009



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION MCR110











2,437 Moved to R&C MCR112-0002
MNGDCARE FILE-HEADER-RECORD-MANAGED-CARE-MCR00001 MCR112 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range

























2,438 No logic changes MCR112-0003 RULE-2758 CLAIMOT CLAIM-HEADER-RECORD-OT-COT00002 MCR112 DATE-OF-BIRTH 2 If DATE-OF-BIRTH is not 8-filled; and; if the first character of TOOTH-NUM = "A" through "T",; then END-DATE-OF-SERVICE - (minus) DATE-OF-BIRTH must be < 15 years 2545 Relational edit between DATE-OF-BIRTH and TOOTH-NUM failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.hasValue(@primaryRecord.DATE-OF-BIRTH) && fns.matches(@secondaryRecord.TOOTH-NUM, "[A-T]+.*"), then fns.isDifferenceInYearsLessThan(@primaryRecord.DATE-OF-BIRTH, @primaryRecord.ENDING-DATE-OF-SERVICE, 15)' DATE-OF-BIRTH,ENDING-DATE-OF-SERVICE COT108,COT034 TOOTH-NUM COT196

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



2,439 Added: format rule NA RULE-1128







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(10) BILLING-PROV-NPI-NUM CLT131











2,440 Added: format rule NA RULE-1135







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(10) REFERRING-PROV-NPI-NUM CLT136











2,441 Added: format rule NA RULE-1178







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) HEALTH-HOME-PROVIDER-NPI CLT167











2,442 Added: format rule NA RULE-1185







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-SUPERVISION-OF-PROV-NPI CLT171











2,443 Added: format rule NA RULE-1188







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(10) ADMITTING-PROV-NPI-NUM CLT174











2,444 Added: format rule NA RULE-1247







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(10) SERVICING-PROV-NPI-NUM CLT213











2,445 Added: format rule NA RULE-1269







1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) CLAIM-LINE-RECORD-LT CLT00003



'if fns.hasValue(@val.HCPCS-RATE), then fns.matches(@val.HCPCS-RATE, "^[^|*]*$")' HCPCS-RATE CLT231











2,446 Added: consistency NA RULE-1531







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-OT COT00002



If the field is populated, the value must be contained in the set of valid values with id: HEALTH-HOME-PROV-IND HEALTH-HOME-PROV-IND COT109











2,447 Added: format rule NA RULE-1542







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(10) BILLING-PROV-NPI-NUM COT113











2,448 Added: format rule NA RULE-1551







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(10) REFERRING-PROV-NPI-NUM COT118











2,449 Added: format rule NA RULE-1589







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(10) HEALTH-HOME-PROVIDER-NPI COT146











2,450 Added: format rule NA RULE-1597







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(10) UNDER-SUPERVISION-OF-PROV-NPI COT150











2,451 Added: format rule NA RULE-1664







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(10) SERVICING-PROV-NPI-NUM COT190











2,452 Added: format rule NA RULE-2099







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(3) ELIGIBLE-COUNTY-CODE ELG072











2,453 Added: format rule NA RULE-2100







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(10) ELIGIBLE-PHONE-NUM ELG073











2,454 Added: format rule NA RULE-2592







1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



'if fns.hasValue(@val.STATE-PLAN-ID-NUM), then fns.matches(@val.STATE-PLAN-ID-NUM, "^[^|*]*$")' STATE-PLAN-ID-NUM MCR037











2,455 Added: format rule NA RULE-2617







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(10) MANAGED-CARE-TELEPHONE MCR049











2,456 Added: format rule NA RULE-2619







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(10) MANAGED-CARE-FAX-NUMBER MCR051











2,457 Added: format rule NA RULE-2860







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(10) ADDR-FAX-NUM PRV055











2,458 Added: format rule NA RULE-2864







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(3) ADDR-COUNTY PRV057











2,459 Added: format rule NA RULE-3049







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT TPL013











2,460 Added: format rule NA RULE-3082







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM TPL032











2,461 Added: format rule NA RULE-3172







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(10) INSURANCE-CARRIER-PHONE-NUM TPL083











2,462 Added: format rule NA RULE-327







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER CIP018











2,463 Added: consistency NA RULE-520







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: CLAIM-PYMT-REM-CODE CLAIM-PYMT-REM-CODE-1 CIP108











2,464 Added: consistency NA RULE-6067







2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-IP CIP00002 CLAIM-LINE-RECORD-IP CIP00003

'if fns.isEqual(@primaryRecord.ADJUSTMENT-IND, "0"), then !fns.hasValue(@secondaryRecord.LINE-NUM-ADJ)' ADJUSTMENT-IND CIP026 LINE-NUM-ADJ CIP238

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP017,CIP019,CIP020,CIP098 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE CIP232,CIP235,CIP236,CIP286



2,465 Added: consistency NA RULE-6068







2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-LT CLT00002



'if fns.hasValue(@val.DISCHARGE-HOUR), then fns.hasValue(@val.DISCHARGE-DATE)' DISCHARGE-HOUR,DISCHARGE-DATE CLT047,CLT046











2,466 Added: consistency NA RULE-6069







3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-LT CLT00002 CLAIM-LINE-RECORD-LT CLT00003 PROV-LOCATION-AND-CONTACT-INFO PRV00003 'fns.isEqual(@primaryRecord.PROV-LOCATION-ID, @tertiaryRecord.PROV-LOCATION-ID)' PROV-LOCATION-ID CLT237

PROV-LOCATION-ID PRV043 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CLT017,CLT020,CLT019,CLT050 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE CLT185,CLT189,CLT188,CLT233 SUBMITTING-STATE,SERVICING-PROV-NUM
SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV040,PRV042
2,467 Added: consistency NA RULE-6071







2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-HEADER-RECORD-OT COT00002



'if !fns.hasValue(@val.DIAGNOSIS-CODE-1), then !fns.hasValue(@val.DIAGNOSIS-CODE-2)' DIAGNOSIS-CODE-1,DIAGNOSIS-CODE-2 COT027,COT030











2,468 Added: consistency NA RULE-6072







2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003

'if fns.isEqual(@primaryRecord.ADJUSTMENT-IND, "0"), then !fns.hasValue(@secondaryRecord.LINE-NUM-ADJ)' ADJUSTMENT-IND COT025 LINE-NUM-ADJ COT161

SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT017,COT019,COT020,COT035 SUBMITTING-STATE,ICN-ORIG,ICN-ADJ,ADJUDICATION-DATE COT155,COT158,COT159,COT221



2,469 Added: consistency NA RULE-6074







2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) CLAIM-LINE-RECORD-OT COT00003



'!fns.isEqual(@val.ORIGINATION-ADDR-LN1, @val.ORIGINATION-ADDR-LN2)' ORIGINATION-ADDR-LN1,ORIGINATION-ADDR-LN2 COT199,COT200











2,470 Added: consistency NA RULE-6075







3 Relational error E3002 Values inconsistently specified (multi record, multi file) Three Record Type Rule CLAIM-HEADER-RECORD-OT COT00002 CLAIM-LINE-RECORD-OT COT00003 PROV-LOCATION-AND-CONTACT-INFO PRV00003 'fns.isEqual(@primaryRecord.PROV-LOCATION-ID, @tertiaryRecord.PROV-LOCATION-ID)' PROV-LOCATION-ID COT226

PROV-LOCATION-ID PRV043 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE COT017,COT020,COT019,COT035 SUBMITTING-STATE,ICN-ADJ,ICN-ORIG,ADJUDICATION-DATE COT155,COT159,COT158,COT221 SUBMITTING-STATE,SERVICING-PROV-NUM
SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV040,PRV042
2,471 Added: format rule NA RULE-6112







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(10) OPERATING-PROV-NPI-NUM CIP265











2,472 Added: format rule NA RULE-6113







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CIP016











2,473 Added: format rule NA RULE-6114







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be compatible with specified T-MSIS picture format: X(10) CHPID MCR106











2,474 Added: format rule NA RULE-6115







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-2 CIP037











2,475 Added: format rule NA RULE-6116







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-1 CIP034











2,476 Added: format rule NA RULE-6117







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-4 CIP043











2,477 Added: format rule NA RULE-6118







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-3 CIP040











2,478 Added: format rule NA RULE-6119







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) OPERATING-PROV-TAXONOMY CIP223











2,479 Added: format rule NA RULE-6120







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-LAST-NAME COT105











2,480 Added: format rule NA RULE-6121







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(12) PLAN-ID-NUMBER CRX056











2,481 Added: format rule NA RULE-6122







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(1) PROV-MIDDLE-INITIAL PRV029











2,482 Added: format rule NA RULE-6123







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-9 CIP058











2,483 Added: format rule NA RULE-6124







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-6 CIP049











2,484 Added: format rule NA RULE-6125







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-5 CIP046











2,485 Added: format rule NA RULE-6126







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-8 CIP055











2,486 Added: format rule NA RULE-6127







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-7 CIP052











2,487 Added: format rule NA RULE-6128







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID PRV043











2,488 Added: format rule NA RULE-6129







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV014











2,489 Added: format rule NA RULE-6130







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(1) NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE TPL092











2,490 Added: format rule NA RULE-6132







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) SERVICING-PROV-SPECIALTY COT193











2,491 Added: format rule NA RULE-6133







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) XXI-MBESCBES-CATEGORY-OF-SERVICE COT212











2,492 Added: format rule NA RULE-6134







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-FIRST-NAME COT106











2,493 Added: format rule NA RULE-6135







1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: X(10) NATIONAL-HEALTH-CARE-ENTITY-ID MCR095











2,494 Added: format rule NA RULE-6136







1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG171











2,495 Added: format rule NA RULE-6137







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) PROCEDURE-CODE-4 CIP082











2,496 Added: format rule NA RULE-6138







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) MEDICARE-REIM-TYPE CIP133











2,497 Added: format rule NA RULE-6139







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE COT155











2,498 Added: format rule NA RULE-6140







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) PROCEDURE-CODE-3 CIP078











2,499 Added: format rule NA RULE-6141







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) PROCEDURE-CODE-2 CIP074











2,500 Added: format rule NA RULE-6142







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) PROCEDURE-CODE-1 CIP070











2,501 Added: format rule NA RULE-6143







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(30) PROV-FIRST-NAME PRV028











2,502 Added: format rule NA RULE-6144







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) PROCEDURE-CODE-6 CIP090











2,503 Added: format rule NA RULE-6145







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) PROCEDURE-CODE-5 CIP086











2,504 Added: format rule NA RULE-6146







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be compatible with specified T-MSIS picture format: X(2) LOCKIN-PROV-TYPE ELG141











2,505 Added: format rule NA RULE-6147







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) ADMITTING-DIAGNOSIS-CODE-FLAG CLT028











2,506 Added: format rule NA RULE-6148







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER CLT227











2,507 Added: format rule NA RULE-6149







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) COPAY-WAIVED-IND CLT160











2,508 Added: format rule NA RULE-6150







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-DIRECTION-OF-PROV-TAXONOMY CIP225











2,509 Added: format rule NA RULE-6151







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be compatible with specified T-MSIS picture format: 9(2) MANAGED-CARE-PLAN-POP MCR077











2,510 Added: format rule NA RULE-6152







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(4) XIX-MBESCBES-CATEGORY-OF-SERVICE CLT224











2,511 Added: format rule NA RULE-6153







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG114











2,512 Added: format rule NA RULE-6154







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG134











2,513 Added: format rule NA RULE-6155







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG019











2,514 Added: format rule NA RULE-6156







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV019











2,515 Added: format rule NA RULE-6158







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM TPL019











2,516 Added: format rule NA RULE-6159







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(1) BRAND-GENERIC-IND CRX140











2,517 Added: format rule NA RULE-6160







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(3) SSI-STATUS ELG092











2,518 Added: format rule NA RULE-6161







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR105











2,519 Added: format rule NA RULE-6162







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV128











2,520 Added: format rule NA RULE-6163







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) CLAIM-DENIED-INDICATOR COT136











2,521 Added: format rule NA RULE-6164







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) ORIGINATION-STATE COT202











2,522 Added: format rule NA RULE-6165







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR ELG011











2,523 Added: format rule NA RULE-6166







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-LINE-STATUS COT165











2,524 Added: format rule NA RULE-6168







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG207











2,525 Added: format rule NA RULE-6169







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(30) INSURANCE-CARRIER-NAME TPL091











2,526 Added: format rule NA RULE-6170







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG063











2,527 Added: format rule NA RULE-6171







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(10) NATIONAL-HEALTH-CARE-ENTITY-ID CRX057











2,528 Added: format rule NA RULE-6172







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-HIC-NUM CLT140











2,529 Added: format rule NA RULE-6173







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(2) IMMUNIZATION-TYPE CLT201











2,530 Added: format rule NA RULE-6174







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR019











2,531 Added: format rule NA RULE-6175







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(12) PRESCRIPTION-NUM CRX142











2,532 Added: format rule NA RULE-6176







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(30) BILLING-PROV-NUM CRX070











2,533 Added: format rule NA RULE-6177







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(9) ORIGINATION-ZIP-CODE COT203











2,534 Added: format rule NA RULE-6178







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR055











2,535 Added: format rule NA RULE-6179







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-ADJUSTMENT-REASON-CODE COT163











2,536 Added: format rule NA RULE-6180







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) REFERRING-PROV-TAXONOMY CLT137











2,537 Added: format rule NA RULE-6181







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(60) PROV-ORGANIZATION-NAME PRV024











2,538 Added: format rule NA RULE-6182







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(1) TANF-CASH-CODE ELG098











2,539 Added: format rule NA RULE-6184







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-FIRST-NAME TPL022











2,540 Added: format rule NA RULE-6185







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(9) INSURANCE-CARRIER-ZIP-CODE TPL082











2,541 Added: format rule NA RULE-6186







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG061











2,542 Added: format rule NA RULE-6187







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(5) HCBS-TAXONOMY COT188











2,543 Added: format rule NA RULE-6188







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(1) PROV-ADDR-TYPE PRV046











2,544 Added: format rule NA RULE-6189







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) FORCED-CLAIM-IND CLT090











2,545 Added: format rule NA RULE-6190







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG190











2,546 Added: format rule NA RULE-6191







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) ADJUSTMENT-IND CLT025











2,547 Added: format rule NA RULE-6192







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(18) PRE-AUTHORIZATION-NUM CIP288











2,548 Added: format rule NA RULE-6193







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) SOURCE-LOCATION CIP104











2,549 Added: format rule NA RULE-6194







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) SERVICING-PROV-TYPE COT192











2,550 Added: format rule NA RULE-6195







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION ELG005











2,551 Added: format rule NA RULE-6196







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ADJ COT161











2,552 Added: format rule NA RULE-6197







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(50) HEALTH-HOME-ENTITY-NAME CLT161











2,553 Added: format rule NA RULE-6198







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-2 COT031











2,554 Added: format rule NA RULE-6199







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-1 COT028











2,555 Added: format rule NA RULE-6200







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(10) NATIONAL-HEALTH-CARE-ENTITY-ID TPL093











2,556 Added: format rule NA RULE-6201







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG198











2,557 Added: format rule NA RULE-6202







1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG231











2,558 Added: format rule NA RULE-6203







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG251











2,559 Added: format rule NA RULE-6204







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(30) SERVICING-PROV-NUM CLT212











2,560 Added: format rule NA RULE-6205







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(28) ELIGIBLE-CITY ELG069











2,561 Added: format rule NA RULE-6206







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION CLT004











2,562 Added: format rule NA RULE-6207







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(2) OWNERSHIP-CODE PRV032











2,563 Added: format rule NA RULE-6208







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR057











2,564 Added: format rule NA RULE-6209







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) SERVICE-TRACKING-TYPE COT059











2,565 Added: format rule NA RULE-6210







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) DISCHARGE-HOUR CIP097











2,566 Added: format rule NA RULE-6211







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION CIP122











2,567 Added: format rule NA RULE-6212







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(1) CORE-BASED-STATISTICAL-AREA-CODE MCR027











2,568 Added: format rule NA RULE-6213







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(2) DUAL-ELIGIBLE-CODE ELG085











2,569 Added: format rule NA RULE-6214







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR014











2,570 Added: format rule NA RULE-6215







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV136











2,571 Added: format rule NA RULE-6216







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM CRX111











2,572 Added: format rule NA RULE-6217







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG112











2,573 Added: format rule NA RULE-6218







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) REFERRING-PROV-SPECIALTY COT121











2,574 Added: format rule NA RULE-6219







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(1) LINE-ADJUSTMENT-IND CIP239











2,575 Added: format rule NA RULE-6220







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-UNIT CLT210











2,576 Added: format rule NA RULE-6221







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) PROGRAM-TYPE CRX055











2,577 Added: format rule NA RULE-6222







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION CIP005











2,578 Added: format rule NA RULE-6223







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION TPL050











2,579 Added: format rule NA RULE-6224







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-11 CIP063











2,580 Added: format rule NA RULE-6225







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-12 CIP066











2,581 Added: format rule NA RULE-6226







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-10 CIP060











2,582 Added: format rule NA RULE-6227







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE TPL001











2,583 Added: format rule NA RULE-6228







1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR091











2,584 Added: format rule NA RULE-6229







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be compatible with specified T-MSIS picture format: X(1) LTSS-LEVEL-CARE ELG182











2,585 Added: format rule NA RULE-6230







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG CRX112











2,586 Added: format rule NA RULE-6231







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) PAYMENT-LEVEL-IND CLT082











2,587 Added: format rule NA RULE-6232







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG116











2,588 Added: format rule NA RULE-6233







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION CRX049











2,589 Added: format rule NA RULE-6234







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ORIG CIP237











2,590 Added: format rule NA RULE-6235







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-DIRECTION-OF-PROV-NPI CLT169











2,591 Added: format rule NA RULE-6236







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) COPAY-WAIVED-IND COT137











2,592 Added: format rule NA RULE-6238







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM CLT187











2,593 Added: format rule NA RULE-6239







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID CRX118











2,594 Added: format rule NA RULE-6240







1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: X(1) NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE MCR096











2,595 Added: format rule NA RULE-6241







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-FLAG-6 CIP092











2,596 Added: format rule NA RULE-6242







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) PATIENT-STATUS CLT141











2,597 Added: format rule NA RULE-6243







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME CLT006











2,598 Added: format rule NA RULE-6244







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-FLAG-2 CIP076











2,599 Added: format rule NA RULE-6245







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-FLAG-3 CIP080











2,600 Added: format rule NA RULE-6246







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-FLAG-4 CIP084











2,601 Added: format rule NA RULE-6247







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-FLAG-5 CIP088











2,602 Added: format rule NA RULE-6248







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-FLAG-1 CIP072











2,603 Added: format rule NA RULE-6249







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(2) MFP-QUALIFIED-INSTITUTION ELG151











2,604 Added: format rule NA RULE-6250







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG147











2,605 Added: format rule NA RULE-6251







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-HIC-NUM CRX079











2,606 Added: format rule NA RULE-6252







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR016











2,607 Added: format rule NA RULE-6253







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE MCR003











2,608 Added: format rule NA RULE-6254







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-PROV-TYPE CIP182











2,609 Added: format rule NA RULE-6255







1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG232











2,610 Added: format rule NA RULE-6256







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(2) ADDR-STATE PRV051











2,611 Added: format rule NA RULE-6257







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(12) NATIONAL-DRUG-CODE CLT228











2,612 Added: format rule NA RULE-6258







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV094











2,613 Added: format rule NA RULE-6259







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR034











2,614 Added: format rule NA RULE-6260







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG104











2,615 Added: format rule NA RULE-6261







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(1) ELIGIBLE-MIDDLE-INIT ELG022











2,616 Added: format rule NA RULE-6262







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) TYPE-OF-HOSPITAL CIP024











2,617 Added: format rule NA RULE-6263







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR061











2,618 Added: format rule NA RULE-6264







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-LINE-STATUS CRX119











2,619 Added: format rule NA RULE-6265







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER TPL031











2,620 Added: format rule NA RULE-6266







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR089











2,621 Added: format rule NA RULE-6267







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG117











2,622 Added: format rule NA RULE-6268







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(60) INSURANCE-CARRIER-ADDR-LN3 TPL079











2,623 Added: format rule NA RULE-6269







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: 9(4) CLAIM-LINE-COUNT CRX060











2,624 Added: format rule NA RULE-6270







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-BENEFICIARY-IDENTIFIER CRX105











2,625 Added: format rule NA RULE-6271







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-FIRST-NAME CLT124











2,626 Added: format rule NA RULE-6272







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(30) BILLING-PROV-NUM COT112











2,627 Added: format rule NA RULE-6273







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(30) PRESCRIBING-PROV-NUM CRX074











2,628 Added: format rule NA RULE-6274







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(10) HEALTH-HOME-PROVIDER-NPI CIP221











2,629 Added: format rule NA RULE-6275







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG139











2,630 Added: format rule NA RULE-6276







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(2) ELIGIBILITY-GROUP ELG087











2,631 Added: format rule NA RULE-6277







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION CRX137











2,632 Added: format rule NA RULE-6278







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR CLT011











2,633 Added: format rule NA RULE-6279







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(4) TYPE-OF-BILL CIP101











2,634 Added: format rule NA RULE-6280







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) FORCED-CLAIM-IND CIP138











2,635 Added: format rule NA RULE-6281







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-CARE-ACQUIRED-CONDITION-IND CIP139











2,636 Added: format rule NA RULE-6282







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(20) MEMBER-ID TPL036











2,637 Added: format rule NA RULE-6283







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(30) DISPENSING-PRESCRIPTION-DRUG-PROV-NUM CRX156











2,638 Added: format rule NA RULE-6284







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-2 CIP075











2,639 Added: format rule NA RULE-6285







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(30) ADMITTING-PROV-NUM CLT175











2,640 Added: format rule NA RULE-6286







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-3 CIP079











2,641 Added: format rule NA RULE-6287







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-1 CIP071











2,642 Added: format rule NA RULE-6288







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG126











2,643 Added: format rule NA RULE-6289







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(1) SSN-INDICATOR TPL012











2,644 Added: format rule NA RULE-6290







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be compatible with specified T-MSIS picture format: X(30) LTSS-PROV-NUM ELG183











2,645 Added: format rule NA RULE-6291







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG146











2,646 Added: format rule NA RULE-6292







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(1) TPL-HEALTH-INSURANCE-COVERAGE-IND TPL020











2,647 Added: format rule NA RULE-6293







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG249











2,648 Added: format rule NA RULE-6294







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) FIXED-PAYMENT-IND CRX052











2,649 Added: format rule NA RULE-6295







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(1) ELIGIBLE-MIDDLE-INIT TPL023











2,650 Added: format rule NA RULE-6296







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(20) WAIVER-ID CIP178











2,651 Added: format rule NA RULE-6297







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(1) SSN-INDICATOR CRX012











2,652 Added: format rule NA RULE-6298







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION TPL061











2,653 Added: format rule NA RULE-6299







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION MCR002











2,654 Added: format rule NA RULE-6300







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) PLAN-ID-NUMBER CLT080











2,655 Added: format rule NA RULE-6302







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-6 CIP091











2,656 Added: format rule NA RULE-6303







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-5 CIP087











2,657 Added: format rule NA RULE-6304







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-4 CIP083











2,658 Added: format rule NA RULE-6305







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG079











2,659 Added: format rule NA RULE-6306







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG018











2,660 Added: format rule NA RULE-6307







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(20) LICENSE-OR-ACCREDITATION-NUMBER PRV069











2,661 Added: format rule NA RULE-6309







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) ELIGIBLE-MIDDLE-INIT COT107











2,662 Added: format rule NA RULE-6310







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV072











2,663 Added: format rule NA RULE-6311







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(10) HEALTH-HOME-PROVIDER-NPI CRX104











2,664 Added: format rule NA RULE-6312







1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG223











2,665 Added: format rule NA RULE-6313







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG007











2,666 Added: format rule NA RULE-6314







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) CROSSOVER-INDICATOR COT023











2,667 Added: format rule NA RULE-6315







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(1) SEX ELG023











2,668 Added: format rule NA RULE-6316







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) BENEFIT-TYPE COT209











2,669 Added: format rule NA RULE-6317







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(30) REMITTANCE-NUM CIP202











2,670 Added: format rule NA RULE-6319







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ADJ CIP238











2,671 Added: format rule NA RULE-6320







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CIP229











2,672 Added: format rule NA RULE-6321







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-3 CLT061











2,673 Added: format rule NA RULE-6322







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-4 CLT062











2,674 Added: format rule NA RULE-6323







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(60) ELIGIBLE-ADDR-LN2 ELG067











2,675 Added: format rule NA RULE-6324







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-1 CLT059











2,676 Added: format rule NA RULE-6325







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(60) ELIGIBLE-ADDR-LN3 ELG068











2,677 Added: format rule NA RULE-6326







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-2 CLT060











2,678 Added: format rule NA RULE-6327







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(2) POLICY-OWNER-CODE TPL047











2,679 Added: format rule NA RULE-6328







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) TOOTH-NUM COT196











2,680 Added: format rule NA RULE-6329







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG016











2,681 Added: format rule NA RULE-6330







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) BORDER-STATE-IND CIP204











2,682 Added: format rule NA RULE-6331







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG188











2,683 Added: format rule NA RULE-6332







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR007











2,684 Added: format rule NA RULE-6333







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(1) SEX PRV031











2,685 Added: format rule NA RULE-6334







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) NDC-UNIT-OF-MEASURE COT224











2,686 Added: format rule NA RULE-6335







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) REFERRING-PROV-TYPE CLT138











2,687 Added: format rule NA RULE-6336







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(14) HCPCS-RATE COT220











2,688 Added: format rule NA RULE-6337







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be compatible with specified T-MSIS picture format: X(1) ENROLLMENT-TYPE ELG252











2,689 Added: format rule NA RULE-6338







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(2) MARITAL-STATUS ELG034











2,690 Added: format rule NA RULE-6339







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(1) MANAGED-CARE-ADDR-TYPE MCR041











2,691 Added: format rule NA RULE-6340







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG180











2,692 Added: format rule NA RULE-6341







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) BILLING-PROV-TAXONOMY CIP181











2,693 Added: format rule NA RULE-6342







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(18) PROV-IDENTIFIER-ISSUING-ENTITY-ID PRV078











2,694 Added: format rule NA RULE-6343







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG191











2,695 Added: format rule NA RULE-6344







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(2) INCOME-CODE ELG038











2,696 Added: format rule NA RULE-6345







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be compatible with specified T-MSIS picture format: X(30) LOCKIN-PROV-NUM ELG140











2,697 Added: format rule NA RULE-6347







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(2) SERVICING-PROV-TYPE CLT215











2,698 Added: format rule NA RULE-6348







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV126











2,699 Added: format rule NA RULE-6349







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(18) PRE-AUTHORIZATION-NUM CLT235











2,700 Added: format rule NA RULE-6350







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS-CATEGORY CIP103











2,701 Added: format rule NA RULE-6351







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) MEDICARE-REIM-TYPE CLT083











2,702 Added: format rule NA RULE-6352







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) TYPE-OF-CLAIM COT037











2,703 Added: format rule NA RULE-6353







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) 1115A-DEMONSTRATION-IND CLT024











2,704 Added: format rule NA RULE-6354







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(4) REVENUE-CODE CLT198











2,705 Added: format rule NA RULE-6355







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(30) REFERRING-PROV-NUM CIP189











2,706 Added: format rule NA RULE-6356







1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG166











2,707 Added: format rule NA RULE-6357







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(1) SSN-INDICATOR ELG012











2,708 Added: format rule NA RULE-6358







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(15) CHECK-NUM CRX033











2,709 Added: format rule NA RULE-6359







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(60) INSURANCE-CARRIER-ADDR-LN2 TPL078











2,710 Added: format rule NA RULE-6360







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(60) INSURANCE-CARRIER-ADDR-LN1 TPL077











2,711 Added: format rule NA RULE-6361







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(1) TPL-OTHER-COVERAGE-IND TPL021











2,712 Added: format rule NA RULE-6362







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-HOME-PROV-IND CIP176











2,713 Added: format rule NA RULE-6363







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(2) IMMUNIZATION-TYPE CRX147











2,714 Added: format rule NA RULE-6364







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(30) SERVICING-PROV-NUM CIP260











2,715 Added: format rule NA RULE-6365







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) FIXED-PAYMENT-IND CLT075











2,716 Added: format rule NA RULE-6366







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(60) ADDR-EMAIL PRV054











2,717 Added: format rule NA RULE-6367







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG238











2,718 Added: format rule NA RULE-6368







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(1) SSN-INDICATOR CIP012











2,719 Added: format rule NA RULE-6369







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: X(2) INSURANCE-PLAN-TYPE TPL057











2,720 Added: format rule NA RULE-6370







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR080











2,721 Added: format rule NA RULE-6371







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(28) ORIGINATION-CITY COT201











2,722 Added: format rule NA RULE-6372







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) TYPE-OF-SERVICE CRX134











2,723 Added: format rule NA RULE-6373







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-3 COT218











2,724 Added: format rule NA RULE-6374







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) SPLIT-CLAIM-IND CIP203











2,725 Added: format rule NA RULE-6375







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-4 COT219











2,726 Added: format rule NA RULE-6376







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR064











2,727 Added: format rule NA RULE-6377







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) DESTINATION-STATE COT207











2,728 Added: format rule NA RULE-6378







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(1) HCBS-SERVICE-CODE CRX135











2,729 Added: format rule NA RULE-6379







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) BORDER-STATE-IND CRX082











2,730 Added: format rule NA RULE-6380







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ COT020











2,731 Added: format rule NA RULE-6381







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CLT185











2,732 Added: format rule NA RULE-6382







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) PAYMENT-LEVEL-IND COT068











2,733 Added: format rule NA RULE-6383







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE TPL072











2,734 Added: format rule NA RULE-6384







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(60) ELIGIBLE-ADDR-LN1 ELG066











2,735 Added: format rule NA RULE-6385







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(1) CONCEPTION-TO-BIRTH-IND ELG094











2,736 Added: format rule NA RULE-6386







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-1 COT172











2,737 Added: format rule NA RULE-6387







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-MOD-2 COT227











2,738 Added: format rule NA RULE-6388







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID CRX161











2,739 Added: format rule NA RULE-6389







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) MEDICARE-COMB-DED-IND CLT078











2,740 Added: format rule NA RULE-6390







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG101











2,741 Added: format rule NA RULE-6391







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be compatible with specified T-MSIS picture format: X(100) HEALTH-HOME-SPA-NAME ELG107











2,742 Added: format rule NA RULE-6392







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) SOURCE-LOCATION COT041











2,743 Added: format rule NA RULE-6393







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(9) MANAGED-CARE-ZIP-CODE MCR047











2,744 Added: format rule NA RULE-6394







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION COT014











2,745 Added: format rule NA RULE-6395







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-PROV-TYPE COT115











2,746 Added: format rule NA RULE-6396







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS COT039











2,747 Added: format rule NA RULE-6397







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV073











2,748 Added: format rule NA RULE-6398







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(2) COVERAGE-TYPE TPL089











2,749 Added: format rule NA RULE-6399







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV092











2,750 Added: format rule NA RULE-6400







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(2) ELIGIBLE-ADDR-TYPE ELG065











2,751 Added: format rule NA RULE-6401







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) REFERRING-PROV-TYPE COT120











2,752 Added: format rule NA RULE-6402







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE PRV003











2,753 Added: format rule NA RULE-6403







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION PRV002











2,754 Added: format rule NA RULE-6404







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG211











2,755 Added: format rule NA RULE-6405







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ CLT189











2,756 Added: format rule NA RULE-6406







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG128











2,757 Added: format rule NA RULE-6407







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-2 CIP035











2,758 Added: format rule NA RULE-6408







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(2) UNIT-OF-MEASURE CRX133











2,759 Added: format rule NA RULE-6409







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-1 CIP032











2,760 Added: format rule NA RULE-6410







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) CLAIM-DENIED-INDICATOR CLT159











2,761 Added: format rule NA RULE-6411







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV017











2,762 Added: format rule NA RULE-6412







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-6 CIP047











2,763 Added: format rule NA RULE-6413







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-SUPERVISION-OF-PROV-TAXONOMY CLT172











2,764 Added: format rule NA RULE-6414







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-5 CIP044











2,765 Added: format rule NA RULE-6415







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-CARE-ACQUIRED-CONDITION-IND CLT091











2,766 Added: format rule NA RULE-6416







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-4 CIP041











2,767 Added: format rule NA RULE-6417







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-3 CIP038











2,768 Added: format rule NA RULE-6418







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG218











2,769 Added: format rule NA RULE-6419







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(3) ADJUSTMENT-REASON-CODE CLT026











2,770 Added: format rule NA RULE-6420







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-FIRST-NAME CIP173











2,771 Added: format rule NA RULE-6421







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION COT214











2,772 Added: format rule NA RULE-6422







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(30) ADMITTING-PROV-NUM CIP185











2,773 Added: format rule NA RULE-6423







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CIP017











2,774 Added: format rule NA RULE-6424







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV040











2,775 Added: format rule NA RULE-6425







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION COT194











2,776 Added: format rule NA RULE-6426







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT COT210











2,777 Added: format rule NA RULE-6427







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG181











2,778 Added: format rule NA RULE-6428







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE CIP003











2,779 Added: format rule NA RULE-6429







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) OTHER-INSURANCE-IND COT057











2,780 Added: format rule NA RULE-6430







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION TPL002











2,781 Added: format rule NA RULE-6431







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) TOOTH-DESIGNATION-SYSTEM COT195











2,782 Added: format rule NA RULE-6432







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(20) DRG-DESCRIPTION CIP029











2,783 Added: format rule NA RULE-6433







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(1) SSN-INDICATOR COT012











2,784 Added: format rule NA RULE-6434







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG014











2,785 Added: format rule NA RULE-6435







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(2) NDC-UNIT-OF-MEASURE CLT229











2,786 Added: format rule NA RULE-6436







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-ADJUSTMENT-REASON-CODE CIP240











2,787 Added: format rule NA RULE-6437







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(50) NATIONAL-HEALTH-CARE-ENTITY-NAME TPL094











2,788 Added: format rule NA RULE-6439







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) SERVICE-TRACKING-TYPE CIP123











2,789 Added: format rule NA RULE-6440







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ORIG COT160











2,790 Added: format rule NA RULE-6441







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG186











2,791 Added: format rule NA RULE-6442







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(100) TYPE-OF-LIVING-ARRANGEMENT ELG074











2,792 Added: format rule NA RULE-6443







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(30) REMITTANCE-NUM CLT144











2,793 Added: format rule NA RULE-6444







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) FORCED-CLAIM-IND CRX061











2,794 Added: format rule NA RULE-6445







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER CRX155











2,795 Added: format rule NA RULE-6446







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(7) ADMITTING-DIAGNOSIS-CODE CLT027











2,796 Added: format rule NA RULE-6447







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be compatible with specified T-MSIS picture format: X(30) MANAGED-CARE-SERVICE-AREA-NAME MCR058











2,797 Added: format rule NA RULE-6448







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR074











2,798 Added: format rule NA RULE-6449







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG115











2,799 Added: format rule NA RULE-6450







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ADJ CLT191











2,800 Added: format rule NA RULE-6451







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(12) NATIONAL-DRUG-CODE COT217











2,801 Added: format rule NA RULE-6452







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-LAST-NAME CIP172











2,802 Added: format rule NA RULE-6453







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(2) INSURANCE-CARRIER-STATE TPL081











2,803 Added: format rule NA RULE-6455







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER MCR112











2,804 Added: format rule NA RULE-6456







1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG227











2,805 Added: format rule NA RULE-6457







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) WAIVER-TYPE CLT128











2,806 Added: format rule NA RULE-6458







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG103











2,807 Added: format rule NA RULE-6459







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CLT173











2,808 Added: format rule NA RULE-6460







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) 1115A-DEMONSTRATION-IND CRX024











2,809 Added: format rule NA RULE-6461







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(1) REBATE-ELIGIBLE-INDICATOR CRX146











2,810 Added: format rule NA RULE-6462







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR COT011











2,811 Added: format rule NA RULE-6463







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: S9(5) DAYS-SUPPLY CRX138











2,812 Added: format rule NA RULE-6464







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) BILLING-PROV-TAXONOMY CLT132











2,813 Added: format rule NA RULE-6465







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(30) POLICY-OWNER-FIRST-NAME TPL044











2,814 Added: format rule NA RULE-6466







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(28) ADDR-CITY PRV050











2,815 Added: format rule NA RULE-6467







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) CITIZENSHIP-VERIFICATION-FLAG ELG041











2,816 Added: format rule NA RULE-6468







1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR100











2,817 Added: format rule NA RULE-6469







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE TPL003











2,818 Added: format rule NA RULE-6470







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CLT007











2,819 Added: format rule NA RULE-6471







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-8 CIP053











2,820 Added: format rule NA RULE-6472







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-7 CIP050











2,821 Added: format rule NA RULE-6473







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR017











2,822 Added: format rule NA RULE-6474







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-9 CIP056











2,823 Added: format rule NA RULE-6475







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(15) CHECK-NUM COT042











2,824 Added: format rule NA RULE-6476







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG248











2,825 Added: format rule NA RULE-6477







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID CRX021











2,826 Added: format rule NA RULE-6478







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(2) ENROLLED-MANAGED-CARE-PLAN-TYPE ELG193











2,827 Added: format rule NA RULE-6479







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) PRESCRIBING-PROV-TYPE CRX077











2,828 Added: format rule NA RULE-6480







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS-CATEGORY CLT055











2,829 Added: format rule NA RULE-6481







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(30) REFERRING-PROV-NUM COT117











2,830 Added: format rule NA RULE-6482







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) SELF-DIRECTION-TYPE CRX158











2,831 Added: format rule NA RULE-6483







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(2) PROV-PROFIT-STATUS PRV033











2,832 Added: format rule NA RULE-6484







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION ELG002











2,833 Added: format rule NA RULE-6485







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(3) ADJUSTMENT-REASON-CODE COT026











2,834 Added: format rule NA RULE-6486







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-SOURCE-NONFEDERAL-SHARE CIP127











2,835 Added: format rule NA RULE-6487







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE CLT003











2,836 Added: format rule NA RULE-6488







1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be compatible with specified T-MSIS picture format: X(2) STATE-PLAN-OPTION-TYPE ELG163











2,837 Added: format rule NA RULE-6489







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(8) PROCEDURE-CODE COT169











2,838 Added: format rule NA RULE-6490







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(1) RESTRICTED-BENEFITS-CODE ELG097











2,839 Added: format rule NA RULE-6491







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(10) NATIONAL-HEALTH-CARE-ENTITY-ID CLT081











2,840 Added: format rule NA RULE-6492







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(2) HOUSEHOLD-SIZE ELG047











2,841 Added: format rule NA RULE-6493







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER COT156











2,842 Added: format rule NA RULE-6494







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(55) MANAGED-CARE-NAME MCR022











2,843 Added: format rule NA RULE-6495







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(1) HCBS-SERVICE-CODE COT187











2,844 Added: format rule NA RULE-6496







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) TYPE-OF-SERVICE COT186











2,845 Added: format rule NA RULE-6497







1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be compatible with specified T-MSIS picture format: X(2) WAIVER-TYPE ELG173











2,846 Added: format rule NA RULE-6498







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) ADJUSTMENT-IND COT025











2,847 Added: format rule NA RULE-6499







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(1) PROV-IDENTIFIER-TYPE PRV077











2,848 Added: format rule NA RULE-6500







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ CRX020











2,849 Added: format rule NA RULE-6501







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG189











2,850 Added: format rule NA RULE-6502







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) PAYMENT-LEVEL-IND CRX058











2,851 Added: format rule NA RULE-6503







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG138











2,852 Added: format rule NA RULE-6504







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG202











2,853 Added: format rule NA RULE-6505







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-8 CIP054











2,854 Added: format rule NA RULE-6506







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-9 CIP057











2,855 Added: format rule NA RULE-6507







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-2 CIP036











2,856 Added: format rule NA RULE-6508







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-3 CIP039











2,857 Added: format rule NA RULE-6509







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PROGRAM-TYPE CIP129











2,858 Added: format rule NA RULE-6510







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(12) NATIONAL-DRUG-CODE CIP284











2,859 Added: format rule NA RULE-6511







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-1 CIP033











2,860 Added: format rule NA RULE-6512







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-6 CIP048











2,861 Added: format rule NA RULE-6513







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG240











2,862 Added: format rule NA RULE-6514







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-7 CIP051











2,863 Added: format rule NA RULE-6515







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-4 CIP042











2,864 Added: format rule NA RULE-6516







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-5 CIP045











2,865 Added: format rule NA RULE-6517







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(1) SSI-IND ELG090











2,866 Added: format rule NA RULE-6518







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-BENEFICIARY-IDENTIFIER CLT168











2,867 Added: format rule NA RULE-6519







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) OTHER-INSURANCE-IND CRX048











2,868 Added: format rule NA RULE-6520







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) PLAN-ID-NUMBER COT066











2,869 Added: format rule NA RULE-6521







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CRX017











2,870 Added: format rule NA RULE-6522







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-1 CLT031











2,871 Added: format rule NA RULE-6523







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-2 CLT034











2,872 Added: format rule NA RULE-6524







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-3 CLT037











2,873 Added: format rule NA RULE-6525







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV037











2,874 Added: format rule NA RULE-6526







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-4 CLT040











2,875 Added: format rule NA RULE-6527







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE COT007











2,876 Added: format rule NA RULE-6528







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-5 CLT043











2,877 Added: format rule NA RULE-6529







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(20) PATIENT-CONTROL-NUM CIP171











2,878 Added: format rule NA RULE-6530







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG017











2,879 Added: format rule NA RULE-6531







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(30) REMITTANCE-NUM CRX081











2,880 Added: format rule NA RULE-6532







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-FIRST-NAME CRX064











2,881 Added: format rule NA RULE-6533







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(1) LICENSE-TYPE PRV067











2,882 Added: format rule NA RULE-6534







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV116











2,883 Added: format rule NA RULE-6535







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be compatible with specified T-MSIS picture format: X(50) HEALTH-HOME-CHRONIC-CONDITION-OTHER-EXPLANATION ELG131











2,884 Added: format rule NA RULE-6536







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER TPL018











2,885 Added: format rule NA RULE-6537







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID CIP289











2,886 Added: format rule NA RULE-6538







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) WAIVER-TYPE COT110











2,887 Added: format rule NA RULE-6539







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(20) WAIVER-ID COT111











2,888 Added: format rule NA RULE-6540







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID COT226











2,889 Added: format rule NA RULE-6541







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be compatible with specified T-MSIS picture format: X(50) AFFILIATED-PROGRAM-ID PRV120











2,890 Added: format rule NA RULE-6542







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(12) DISPENSING-PRESCRIPTION-DRUG-PROV-TAXONOMY CRX103











2,891 Added: format rule NA RULE-6543







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION CLT002











2,892 Added: format rule NA RULE-6544







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) BENEFIT-TYPE CIP268











2,893 Added: format rule NA RULE-6545







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) SOURCE-LOCATION CRX032











2,894 Added: format rule NA RULE-6546







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) IMMIGRATION-STATUS ELG042











2,895 Added: format rule NA RULE-6547







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS CRX030











2,896 Added: format rule NA RULE-6548







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-1 COT027











2,897 Added: format rule NA RULE-6549







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-10 COT083











2,898 Added: format rule NA RULE-6550







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-2 COT030











2,899 Added: format rule NA RULE-6551







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(60) MANAGED-CARE-ADDR-LN1 MCR042











2,900 Added: format rule NA RULE-6552







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(60) MANAGED-CARE-ADDR-LN2 MCR043











2,901 Added: format rule NA RULE-6553







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-DIRECTION-OF-PROV-TAXONOMY CLT170











2,902 Added: format rule NA RULE-6554







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(60) MANAGED-CARE-ADDR-LN3 MCR044











2,903 Added: format rule NA RULE-6555







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(1) MANAGED-CARE-PROGRAM MCR023











2,904 Added: format rule NA RULE-6556







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(9) POLICY-OWNER-SSN TPL046











2,905 Added: format rule NA RULE-6557







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: X(2) PROV-MEDICAID-ENROLLMENT-STATUS-CODE PRV100











2,906 Added: format rule NA RULE-6558







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-PROV-SPECIALTY COT116











2,907 Added: format rule NA RULE-6559







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-HIC-NUM CIP196











2,908 Added: format rule NA RULE-6560







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) ELIGIBLE-MIDDLE-INIT CIP174











2,909 Added: format rule NA RULE-6561







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) REFERRING-PROV-TAXONOMY CIP191











2,910 Added: format rule NA RULE-6562







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-09 COT082











2,911 Added: format rule NA RULE-6563







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) SPLIT-CLAIM-IND CLT150











2,912 Added: format rule NA RULE-6565







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(2) CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CIP269











2,913 Added: format rule NA RULE-6566







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(2) IMMUNIZATION-TYPE CIP248











2,914 Added: format rule NA RULE-6567







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME TPL006











2,915 Added: format rule NA RULE-6568







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV042











2,916 Added: format rule NA RULE-6569







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-03 COT076











2,917 Added: format rule NA RULE-6570







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-04 COT077











2,918 Added: format rule NA RULE-6571







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION PRV004











2,919 Added: format rule NA RULE-6572







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-01 COT074











2,920 Added: format rule NA RULE-6573







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-02 COT075











2,921 Added: format rule NA RULE-6574







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-07 COT080











2,922 Added: format rule NA RULE-6575







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-08 COT081











2,923 Added: format rule NA RULE-6576







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-05 COT078











2,924 Added: format rule NA RULE-6577







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-06 COT079











2,925 Added: format rule NA RULE-6578







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: X(30) HEALTH-HOME-PROV-NUM ELG120











2,926 Added: format rule NA RULE-6579







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) SELF-DIRECTION-TYPE CIP287











2,927 Added: format rule NA RULE-6580







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM CRX022











2,928 Added: format rule NA RULE-6581







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-LAST-NAME CLT123











2,929 Added: format rule NA RULE-6582







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(50) HEALTH-HOME-ENTITY-NAME CIP214











2,930 Added: format rule NA RULE-6583







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE TPL064











2,931 Added: format rule NA RULE-6584







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(10) NATIONAL-HEALTH-CARE-ENTITY-ID ELG194











2,932 Added: format rule NA RULE-6585







1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG169











2,933 Added: format rule NA RULE-6587







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER MCR018











2,934 Added: format rule NA RULE-6588







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ COT159











2,935 Added: format rule NA RULE-6589







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) XXI-MBESCBES-CATEGORY-OF-SERVICE CIP271











2,936 Added: format rule NA RULE-6590







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV075











2,937 Added: format rule NA RULE-6591







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG250











2,938 Added: format rule NA RULE-6592







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(2) MANAGED-CARE-STATE MCR046











2,939 Added: format rule NA RULE-6593







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ADJ CRX115











2,940 Added: format rule NA RULE-6594







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(16) GROUP-NUM TPL035











2,941 Added: format rule NA RULE-6595







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-CODE CRX053











2,942 Added: format rule NA RULE-6596







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) ADMITTING-PROV-TAXONOMY CIP187











2,943 Added: format rule NA RULE-6597







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS-CATEGORY CRX031











2,944 Added: format rule NA RULE-6599







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(1) MAINTENANCE-ASSISTANCE-STATUS ELG096











2,945 Added: format rule NA RULE-6600







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-BENEFICIARY-IDENTIFIER ELG051











2,946 Added: format rule NA RULE-6601







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) PROGRAM-TYPE COT065











2,947 Added: format rule NA RULE-6602







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID CLT021











2,948 Added: format rule NA RULE-6603







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG178











2,949 Added: format rule NA RULE-6604







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: 9(9) SSN ELG036











2,950 Added: format rule NA RULE-6605







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID CIP241











2,951 Added: format rule NA RULE-6606







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) TYPE-OF-SERVICE CIP257











2,952 Added: format rule NA RULE-6607







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(10) NATIONAL-HEALTH-CARE-ENTITY-ID CIP131











2,953 Added: format rule NA RULE-6608







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER ELG247











2,954 Added: format rule NA RULE-6609







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(60) ORIGINATION-ADDR-LN1 COT199











2,955 Added: format rule NA RULE-6610







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER TPL054











2,956 Added: format rule NA RULE-6611







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(18) PRE-AUTHORIZATION-NUM CRX159











2,957 Added: format rule NA RULE-6612







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR035











2,958 Added: format rule NA RULE-6613







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR052











2,959 Added: format rule NA RULE-6614







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE TPL016











2,960 Added: format rule NA RULE-6615







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(60) ORIGINATION-ADDR-LN2 COT200











2,961 Added: format rule NA RULE-6617







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG CLT188











2,962 Added: format rule NA RULE-6618







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CLT014











2,963 Added: format rule NA RULE-6619







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG082











2,964 Added: format rule NA RULE-6620







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-CODE CIP126











2,965 Added: format rule NA RULE-6621







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(2) MEDICAID-BASIS-OF-ELIGIBILITY ELG084











2,966 Added: format rule NA RULE-6622







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) COMPOUND-DRUG-IND CRX086











2,967 Added: format rule NA RULE-6623







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(1) TOOTH-SURFACE-CODE COT198











2,968 Added: format rule NA RULE-6624







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV115











2,969 Added: format rule NA RULE-6625







1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG168











2,970 Added: format rule NA RULE-6626







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(30) POLICY-OWNER-LAST-NAME TPL045











2,971 Added: format rule NA RULE-6627







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) ADMITTING-PROV-SPECIALTY CLT176











2,972 Added: format rule NA RULE-6628







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CLT226











2,973 Added: format rule NA RULE-6629







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM CIP022











2,974 Added: format rule NA RULE-6630







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(4) REVENUE-CODE COT168











2,975 Added: format rule NA RULE-6631







1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR092











2,976 Added: format rule NA RULE-6632







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-SUPERVISION-OF-PROV-TAXONOMY COT151











2,977 Added: format rule NA RULE-6634







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: X(1) STATE-PLAN-ENROLLMENT PRV101











2,978 Added: format rule NA RULE-6635







1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR094











2,979 Added: format rule NA RULE-6636







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER COT216











2,980 Added: format rule NA RULE-6637







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR073











2,981 Added: format rule NA RULE-6638







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM CIP234











2,982 Added: format rule NA RULE-6639







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME CIP006











2,983 Added: format rule NA RULE-6640







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(12) INSURANCE-CARRIER-ID-NUM TPL075











2,984 Added: format rule NA RULE-6641







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG081











2,985 Added: format rule NA RULE-6642







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) BENEFIT-TYPE CLT218











2,986 Added: format rule NA RULE-6643







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG212











2,987 Added: format rule NA RULE-6644







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: X(100) HEALTH-HOME-SPA-NAME ELG118











2,988 Added: format rule NA RULE-6645







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG CIP235











2,989 Added: format rule NA RULE-6646







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CRX106











2,990 Added: format rule NA RULE-6647







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(30) REFERRING-PROV-NUM CLT135











2,991 Added: format rule NA RULE-6648







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) MEDICARE-REIM-TYPE CRX059











2,992 Added: format rule NA RULE-6649







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV104











2,993 Added: format rule NA RULE-6650







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(1) SSN-INDICATOR CLT012











2,994 Added: format rule NA RULE-6651







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER CLT186











2,995 Added: format rule NA RULE-6652







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) ALLOWED-CHARGE-SRC CIP107











2,996 Added: format rule NA RULE-6653







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER TPL074











2,997 Added: format rule NA RULE-6654







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION CIP266











2,998 Added: format rule NA RULE-6655







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: X(2) COVERAGE-TYPE TPL058











2,999 Added: format rule NA RULE-6656







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV058











3,000 Added: format rule NA RULE-6657







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME ELG006











3,001 Added: format rule NA RULE-6658







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV061











3,002 Added: format rule NA RULE-6659







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(28) DESTINATION-CITY COT206











3,003 Added: format rule NA RULE-6660







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) CLAIM-DENIED-INDICATOR CIP212











3,004 Added: format rule NA RULE-6662







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV039











3,005 Added: format rule NA RULE-6663







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: 9(4) CLAIM-LINE-COUNT CLT087











3,006 Added: format rule NA RULE-6664







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG136











3,007 Added: format rule NA RULE-6665







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) XXI-MBESCBES-CATEGORY-OF-SERVICE CLT225











3,008 Added: format rule NA RULE-6666







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be compatible with specified T-MSIS picture format: X(1) PROV-CLASSIFICATION-TYPE PRV088











3,009 Added: format rule NA RULE-6667







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) CHIP-CODE ELG054











3,010 Added: format rule NA RULE-6668







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR110











3,011 Added: format rule NA RULE-6669







1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG222











3,012 Added: format rule NA RULE-6670







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG COT019











3,013 Added: format rule NA RULE-6671







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-SOURCE-NONFEDERAL-SHARE CRX054











3,014 Added: format rule NA RULE-6672







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG148











3,015 Added: format rule NA RULE-6673







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CRX007











3,016 Added: format rule NA RULE-6674







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG077











3,017 Added: format rule NA RULE-6675







1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG236











3,018 Added: format rule NA RULE-6676







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-02 CIP141











3,019 Added: format rule NA RULE-6677







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-01 CIP140











3,020 Added: format rule NA RULE-6678







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE TPL017











3,021 Added: format rule NA RULE-6679







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) OTHER-INSURANCE-IND CLT071











3,022 Added: format rule NA RULE-6680







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-04 CIP143











3,023 Added: format rule NA RULE-6681







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-03 CIP142











3,024 Added: format rule NA RULE-6682







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV063











3,025 Added: format rule NA RULE-6683







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-06 CIP145











3,026 Added: format rule NA RULE-6684







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) CROSSOVER-INDICATOR CLT023











3,027 Added: format rule NA RULE-6685







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-05 CIP144











3,028 Added: format rule NA RULE-6686







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-08 CIP147











3,029 Added: format rule NA RULE-6687







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-07 CIP146











3,030 Added: format rule NA RULE-6688







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-09 CIP148











3,031 Added: format rule NA RULE-6689







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) TYPE-OF-SERVICE CLT211











3,032 Added: format rule NA RULE-6690







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(1) SSDI-IND ELG089











3,033 Added: format rule NA RULE-6691







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(30) REMITTANCE-NUM COT126











3,034 Added: format rule NA RULE-6692







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(4) DIAGNOSIS-RELATED-GROUP CIP068











3,035 Added: format rule NA RULE-6693







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(30) BILLING-PROV-NUM CIP179











3,036 Added: format rule NA RULE-6694







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) 1115A-DEMONSTRATION-IND COT024











3,037 Added: format rule NA RULE-6695







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION TPL086











3,038 Added: format rule NA RULE-6696







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-10 CIP149











3,039 Added: format rule NA RULE-6697







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-CARE-ACQUIRED-CONDITION-IND COT073











3,040 Added: format rule NA RULE-6698







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: X(20) INSURANCE-PLAN-ID TPL056











3,041 Added: format rule NA RULE-6699







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER CLT018











3,042 Added: format rule NA RULE-6700







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) ADMITTING-DIAGNOSIS-CODE-FLAG CIP031











3,043 Added: format rule NA RULE-6701







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CIP014











3,044 Added: format rule NA RULE-6702







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(2) TPL-ENTITY-ADDR-TYPE TPL076











3,045 Added: format rule NA RULE-6703







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(4) XIX-MBESCBES-CATEGORY-OF-SERVICE CIP270











3,046 Added: format rule NA RULE-6704







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) FIXED-PAYMENT-IND COT061











3,047 Added: format rule NA RULE-6705







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(20) PATIENT-CONTROL-NUM CRX062











3,048 Added: format rule NA RULE-6706







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-PROV-SPECIALTY CLT134











3,049 Added: format rule NA RULE-6707







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(12) SERVICING-PROV-TAXONOMY CIP262











3,050 Added: format rule NA RULE-6708







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) WAIVER-TYPE CRX068











3,051 Added: format rule NA RULE-6709







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE TPL052











3,052 Added: format rule NA RULE-6710







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID PRV064











3,053 Added: format rule NA RULE-6711







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION CIP002











3,054 Added: format rule NA RULE-6712







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME COT006











3,055 Added: format rule NA RULE-6713







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(20) WAIVER-ID CRX069











3,056 Added: format rule NA RULE-6714







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION CRX004











3,057 Added: format rule NA RULE-6715







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) BORDER-STATE-IND CLT151











3,058 Added: format rule NA RULE-6716







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(2) COMPOUND-DOSAGE-FORM CRX145











3,059 Added: format rule NA RULE-6717







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER TPL065











3,060 Added: format rule NA RULE-6718







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV001











3,061 Added: format rule NA RULE-6719







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(12) BILLING-PROV-TAXONOMY CRX072











3,062 Added: format rule NA RULE-6720







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-ADJUSTMENT-REASON-CODE CRX117











3,063 Added: format rule NA RULE-6721







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(15) CHECK-NUM CLT057











3,064 Added: format rule NA RULE-6722







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: X(12) INSURANCE-CARRIER-ID-NUM TPL055











3,065 Added: format rule NA RULE-6723







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM CLT022











3,066 Added: format rule NA RULE-6724







1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG170











3,067 Added: format rule NA RULE-6725







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(3) PRIMARY-LANGUAGE-CODE ELG046











3,068 Added: format rule NA RULE-6726







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(9) PROV-FACILITY-TYPE CIP267











3,069 Added: format rule NA RULE-6728







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV082











3,070 Added: format rule NA RULE-6729







1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG220











3,071 Added: format rule NA RULE-6730







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-LINE-STATUS CIP242











3,072 Added: format rule NA RULE-6731







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(9) ADDR-ZIP-CODE PRV052











3,073 Added: format rule NA RULE-6732







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CIP273











3,074 Added: format rule NA RULE-6733







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(28) INSURANCE-CARRIER-CITY TPL080











3,075 Added: format rule NA RULE-6734







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(2) CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CRX149











3,076 Added: format rule NA RULE-6735







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be compatible with specified T-MSIS picture format: X(1) AFFILIATED-PROGRAM-TYPE PRV119











3,077 Added: format rule NA RULE-6736







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(20) INSURANCE-PLAN-ID TPL034











3,078 Added: format rule NA RULE-6737







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE TPL029











3,079 Added: format rule NA RULE-6738







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG032











3,080 Added: format rule NA RULE-6739







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG106











3,081 Added: format rule NA RULE-6740







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) SELF-DIRECTION-TYPE CLT234











3,082 Added: format rule NA RULE-6741







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CRX153











3,083 Added: format rule NA RULE-6742







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be a valid date of the form CCYYMMDD DATE-OF-DEATH PRV035











3,084 Added: format rule NA RULE-6743







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(3) ADJUSTMENT-REASON-CODE CIP027











3,085 Added: format rule NA RULE-6744







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CLT184











3,086 Added: format rule NA RULE-6745







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) PRESCRIBING-PROV-SPECIALTY CRX078











3,087 Added: format rule NA RULE-6746







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-HOME-PROV-IND CLT127











3,088 Added: format rule NA RULE-6747







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION TPL070











3,089 Added: format rule NA RULE-6748







1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG162











3,090 Added: format rule NA RULE-6749







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR103











3,091 Added: format rule NA RULE-6750







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE MCR083











3,092 Added: format rule NA RULE-6751







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE COT017











3,093 Added: format rule NA RULE-6752







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG149











3,094 Added: format rule NA RULE-6753







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION TPL004











3,095 Added: format rule NA RULE-6754







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(100) PROV-LEGAL-NAME PRV023











3,096 Added: format rule NA RULE-6755







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) TYPE-OF-CLAIM CRX029











3,097 Added: format rule NA RULE-6756







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be compatible with specified T-MSIS picture format: X(20) WAIVER-ID MCR068











3,098 Added: format rule NA RULE-6757







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(60) LICENSE-ISSUING-ENTITY-ID PRV068











3,099 Added: format rule NA RULE-6758







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-CODE COT062











3,100 Added: format rule NA RULE-6759







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) FORCED-CLAIM-IND COT072











3,101 Added: format rule NA RULE-6760







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be compatible with specified T-MSIS picture format: X(1) TYPE-OF-OTHER-THIRD-PARTY-LIABILITY TPL067











3,102 Added: format rule NA RULE-6761







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(2) REIMBURSEMENT-ARRANGEMENT MCR025











3,103 Added: format rule NA RULE-6762







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION CRX014











3,104 Added: format rule NA RULE-6763







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE ELG003











3,105 Added: format rule NA RULE-6764







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) ADMISSION-HOUR CLT045











3,106 Added: format rule NA RULE-6765







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-HIC-NUM ELG050











3,107 Added: format rule NA RULE-6766







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS-CATEGORY COT040











3,108 Added: format rule NA RULE-6767







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG059











3,109 Added: format rule NA RULE-6768







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-LAST-NAME CRX063











3,110 Added: format rule NA RULE-6769







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG245











3,111 Added: format rule NA RULE-6770







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-FIRST-NAME ELG020











3,112 Added: format rule NA RULE-6771







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CLT017











3,113 Added: format rule NA RULE-6773







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR PRV011











3,114 Added: format rule NA RULE-6774







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(8) DRG-REL-WEIGHT CIP195











3,115 Added: format rule NA RULE-6775







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG137











3,116 Added: format rule NA RULE-6776







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(2) ELIGIBILITY-CHANGE-REASON ELG095











3,117 Added: format rule NA RULE-6777







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-3 CRX037











3,118 Added: format rule NA RULE-6778







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-01 CLT092











3,119 Added: format rule NA RULE-6779







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-4 CRX038











3,120 Added: format rule NA RULE-6780







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-1 CRX035











3,121 Added: format rule NA RULE-6781







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-2 CRX036











3,122 Added: format rule NA RULE-6782







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CIP007











3,123 Added: format rule NA RULE-6783







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG031











3,124 Added: format rule NA RULE-6784







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(3) SELF-DIRECTION-TYPE COT222











3,125 Added: format rule NA RULE-6785







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE TPL030











3,126 Added: format rule NA RULE-6786







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-08 CLT099











3,127 Added: format rule NA RULE-6787







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ CIP236











3,128 Added: format rule NA RULE-6788







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-09 CLT100











3,129 Added: format rule NA RULE-6789







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) ADMITTING-PROV-TYPE CLT178











3,130 Added: format rule NA RULE-6790







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) REFERRING-PROV-TAXONOMY COT119











3,131 Added: format rule NA RULE-6791







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-06 CLT097











3,132 Added: format rule NA RULE-6792







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-07 CLT098











3,133 Added: format rule NA RULE-6793







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: X(100) HEALTH-HOME-ENTITY-NAME ELG119











3,134 Added: format rule NA RULE-6794







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-04 CLT095











3,135 Added: format rule NA RULE-6795







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG241











3,136 Added: format rule NA RULE-6796







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-05 CLT096











3,137 Added: format rule NA RULE-6797







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-02 CLT093











3,138 Added: format rule NA RULE-6798







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-03 CLT094











3,139 Added: format rule NA RULE-6799







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(10) SERVICING-PROV-NPI-NUM CIP261











3,140 Added: format rule NA RULE-6800







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(18) PRE-AUTHORIZATION-NUM COT223











3,141 Added: format rule NA RULE-6801







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID PRV076











3,142 Added: format rule NA RULE-6802







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE TPL053











3,143 Added: format rule NA RULE-6803







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION TPL014











3,144 Added: format rule NA RULE-6804







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-UNIT CIP256











3,145 Added: format rule NA RULE-6805







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-CODE CLT076











3,146 Added: format rule NA RULE-6806







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) OCCURRENCE-CODE-10 CLT101











3,147 Added: format rule NA RULE-6807







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be compatible with specified T-MSIS picture format: X(100) HEALTH-HOME-ENTITY-NAME ELG108











3,148 Added: format rule NA RULE-6808







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) SERVICE-TRACKING-TYPE CLT073











3,149 Added: format rule NA RULE-6809







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION ELG004











3,150 Added: format rule NA RULE-6810







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ORIG CRX114











3,151 Added: format rule NA RULE-6811







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION TPL005











3,152 Added: format rule NA RULE-6812







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG239











3,153 Added: format rule NA RULE-6813







1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG229











3,154 Added: format rule NA RULE-6814







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) MEDICARE-COMB-DED-IND CIP128











3,155 Added: format rule NA RULE-6815







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) IMMIGRATION-VERIFICATION-FLAG ELG043











3,156 Added: format rule NA RULE-6816







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) SOURCE-LOCATION CLT056











3,157 Added: format rule NA RULE-6817







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ CLT020











3,158 Added: format rule NA RULE-6818







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(10) UNDER-DIRECTION-OF-PROV-NPI COT148











3,159 Added: format rule NA RULE-6820







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) MEDICARE-REIM-TYPE COT069











3,160 Added: format rule NA RULE-6821







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION TPL027











3,161 Added: format rule NA RULE-6822







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) CLAIM-DENIED-INDICATOR CRX094











3,162 Added: format rule NA RULE-6823







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) TYPE-OF-CLAIM CIP100











3,163 Added: format rule NA RULE-6824







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ CRX113











3,164 Added: format rule NA RULE-6825







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: X(1) CERTIFIED-AMERICAN-INDIAN-ALASKAN-NATIVE-INDICATOR ELG215











3,165 Added: format rule NA RULE-6826







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-SUPERVISION-OF-PROV-TAXONOMY CIP227











3,166 Added: format rule NA RULE-6827







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(2) SERVICING-PROV-SPECIALTY CIP264











3,167 Added: format rule NA RULE-6828







1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG176











3,168 Added: format rule NA RULE-6829







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CLT001











3,169 Added: format rule NA RULE-6830







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER CIP233











3,170 Added: format rule NA RULE-6831







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID CLT237











3,171 Added: format rule NA RULE-6832







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) UNDER-DIRECTION-OF-PROV-TAXONOMY COT149











3,172 Added: format rule NA RULE-6833







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM COT022











3,173 Added: format rule NA RULE-6834







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV109











3,174 Added: format rule NA RULE-6835







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME MCR006











3,175 Added: format rule NA RULE-6836







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-1 CLT029











3,176 Added: format rule NA RULE-6837







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: X(3) RACE ELG213











3,177 Added: format rule NA RULE-6838







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be compatible with specified T-MSIS picture format: X(10) SHPID MCR107











3,178 Added: format rule NA RULE-6839







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(2) MANAGED-CARE-PROFIT-STATUS MCR026











3,179 Added: format rule NA RULE-6840







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(10) BILLING-PROV-NPI-NUM CRX071











3,180 Added: format rule NA RULE-6841







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR066











3,181 Added: format rule NA RULE-6842







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) SSN-VERIFICATION-FLAG ELG037











3,182 Added: format rule NA RULE-6843







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-2 CLT032











3,183 Added: format rule NA RULE-6844







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-3 CLT035











3,184 Added: format rule NA RULE-6845







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-4 CLT038











3,185 Added: format rule NA RULE-6846







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-5 CLT041











3,186 Added: format rule NA RULE-6847







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM TPL066











3,187 Added: format rule NA RULE-6848







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-11 CIP062











3,188 Added: format rule NA RULE-6849







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-10 CIP059











3,189 Added: format rule NA RULE-6850







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) DIAGNOSIS-CODE-12 CIP065











3,190 Added: format rule NA RULE-6851







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(20) PATIENT-CONTROL-NUM COT104











3,191 Added: format rule NA RULE-6852







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(3) ADJUSTMENT-REASON-CODE CRX026











3,192 Added: format rule NA RULE-6853







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM COT157











3,193 Added: format rule NA RULE-6854







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(10) NATIONAL-HEALTH-CARE-ENTITY-ID COT067











3,194 Added: format rule NA RULE-6855







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR032











3,195 Added: format rule NA RULE-6856







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV087











3,196 Added: format rule NA RULE-6857







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(5) HCBS-TAXONOMY CRX136











3,197 Added: format rule NA RULE-6859







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) PREGNANCY-IND ELG049











3,198 Added: format rule NA RULE-6860







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ENROLLMENT-TIME-SPAN-SEGMENT ELG00021



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG255











3,199 Added: format rule NA RULE-6861







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-LT CLT00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION CLT005











3,200 Added: format rule NA RULE-6862







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(1) LINE-ADJUSTMENT-IND CLT192











3,201 Added: format rule NA RULE-6863







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be compatible with specified T-MSIS picture format: X(20) PROV-CLASSIFICATION-CODE PRV089











3,202 Added: format rule NA RULE-6864







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(4) TYPE-OF-BILL COT038











3,203 Added: format rule NA RULE-6865







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-PROV-TYPE CLT133











3,204 Added: format rule NA RULE-6866







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: 9(4) CLAIM-LINE-COUNT CIP137











3,205 Added: format rule NA RULE-6867







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) ELIGIBLE-MIDDLE-INIT CLT125











3,206 Added: format rule NA RULE-6868







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-PROV-SPECIALTY CIP183











3,207 Added: format rule NA RULE-6869







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) VETERAN-IND ELG039











3,208 Added: format rule NA RULE-6870







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-SOURCE-NONFEDERAL-SHARE COT063











3,209 Added: format rule NA RULE-6871







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: X(5) PROV-LOCATION-ID PRV129











3,210 Added: format rule NA RULE-6872







1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG161











3,211 Added: format rule NA RULE-6873







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) WAIVER-TYPE CIP177











3,212 Added: format rule NA RULE-6874







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) PROGRAM-TYPE CLT079











3,213 Added: format rule NA RULE-6875







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV125











3,214 Added: format rule NA RULE-6876







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER CIP275











3,215 Added: format rule NA RULE-6877







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV095











3,216 Added: format rule NA RULE-6878







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: X(1) BED-TYPE-CODE PRV134











3,217 Added: format rule NA RULE-6879







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PARTICIPATION-INFORMATION ELG00006



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER ELG105











3,218 Added: format rule NA RULE-6880







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-ADJUSTMENT-REASON-CODE CLT193











3,219 Added: format rule NA RULE-6882







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-2 COT032











3,220 Added: format rule NA RULE-6883







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-1 COT029











3,221 Added: format rule NA RULE-6884







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(4) DIAGNOSIS-RELATED-GROUP-IND CIP069











3,222 Added: format rule NA RULE-6885







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION COT004











3,223 Added: format rule NA RULE-6886







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(60) MANAGED-CARE-EMAIL MCR050











3,224 Added: format rule NA RULE-6887







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION COT002











3,225 Added: format rule NA RULE-6888







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG CLT019











3,226 Added: format rule NA RULE-6889







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV106











3,227 Added: format rule NA RULE-6890







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(10) BILLING-PROV-NPI-NUM CIP180











3,228 Added: format rule NA RULE-6891







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG064











3,229 Added: format rule NA RULE-6892







1 Formatting Error E1001 Value illegal for specified data type Parse Rule WAIVER-PARTICIPATION ELG00012



Value must be compatible with specified T-MSIS picture format: X(20) WAIVER-ID ELG172











3,230 Added: format rule NA RULE-6893







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) REFERRING-PROV-SPECIALTY CIP193











3,231 Added: format rule NA RULE-6894







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV070











3,232 Added: format rule NA RULE-6895







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) CITIZENSHIP-IND ELG040











3,233 Added: format rule NA RULE-6896







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(1) MFP-LIVES-WITH-FAMILY ELG150











3,234 Added: format rule NA RULE-6897







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) PATIENT-STATUS CIP199











3,235 Added: format rule NA RULE-6898







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(9) DESTINATION-ZIP-CODE COT208











3,236 Added: format rule NA RULE-6899







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(1) PRIMARY-ELIGIBILITY-GROUP-IND ELG086











3,237 Added: format rule NA RULE-6900







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTING-STATE-PROV-ID-OF-AFFILIATED-ENTITY PRV110











3,238 Added: format rule NA RULE-6901







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(4) REVENUE-CODE CIP245











3,239 Added: format rule NA RULE-6902







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(3) SSI-STATE-SUPPLEMENT-STATUS-CODE ELG091











3,240 Added: format rule NA RULE-6903







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(12) INSURANCE-CARRIER-ID-NUM TPL033











3,241 Added: format rule NA RULE-6904







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) MEDICARE-COMB-DED-IND CRX160











3,242 Added: format rule NA RULE-6905







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(2) MFP-QUALIFIED-RESIDENCE ELG152











3,243 Added: format rule NA RULE-6906







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(30) PROV-LAST-NAME PRV030











3,244 Added: format rule NA RULE-6907







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG200











3,245 Added: format rule NA RULE-6908







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-4 COT047











3,246 Added: format rule NA RULE-6909







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-3 COT046











3,247 Added: format rule NA RULE-6910







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) ADMITTING-PROV-TYPE CIP188











3,248 Added: format rule NA RULE-6911







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(20) WAIVER-ID CLT129











3,249 Added: format rule NA RULE-6912







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-2 COT045











3,250 Added: format rule NA RULE-6913







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(100) PROV-DOING-BUSINESS-AS-NAME PRV022











3,251 Added: format rule NA RULE-6914







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-1 COT044











3,252 Added: format rule NA RULE-6915







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV097











3,253 Added: format rule NA RULE-6916







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(10) REFERRING-PROV-NPI-NUM CIP190











3,254 Added: format rule NA RULE-6917







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CIP232











3,255 Added: format rule NA RULE-6918







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) PAYMENT-LEVEL-IND CIP132











3,256 Added: format rule NA RULE-6919







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION COT005











3,257 Added: format rule NA RULE-6920







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(20) PATIENT-CONTROL-NUM CLT122











3,258 Added: format rule NA RULE-6921







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR001











3,259 Added: format rule NA RULE-6922







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-HIC-NUM COT122











3,260 Added: format rule NA RULE-6923







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(2) FACILITY-GROUP-INDIVIDUAL-CODE PRV026











3,261 Added: format rule NA RULE-6924







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(12) PRESCRIBING-PROV-TAXONOMY CRX076











3,262 Added: format rule NA RULE-6925







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(1) LINE-ADJUSTMENT-IND CRX116











3,263 Added: format rule NA RULE-6926







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV085











3,264 Added: format rule NA RULE-6927







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION MCR071











3,265 Added: format rule NA RULE-6928







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) CROSSOVER-INDICATOR CRX023











3,266 Added: format rule NA RULE-6929







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(15) CHECK-NUM CIP105











3,267 Added: format rule NA RULE-6931







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: X(12) PROV-IDENTIFIER PRV081











3,268 Added: format rule NA RULE-6932







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-HOME-PROV-IND CRX067











3,269 Added: format rule NA RULE-6933







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(3) MANAGED-CARE-COUNTY MCR048











3,270 Added: format rule NA RULE-6934







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-SERVICE-AREA MCR00004



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR054











3,271 Added: format rule NA RULE-6935







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(4) XIX-MBESCBES-CATEGORY-OF-SERVICE CRX150











3,272 Added: format rule NA RULE-6936







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-11 CIP064











3,273 Added: format rule NA RULE-6937







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-10 CIP061











3,274 Added: format rule NA RULE-6938







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(28) MANAGED-CARE-CITY MCR045











3,275 Added: format rule NA RULE-6939







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) TYPE-OF-CLAIM CLT052











3,276 Added: format rule NA RULE-6940







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(10) DISPENSING-PRESCRIPTION-DRUG-PROV-NPI CRX102











3,277 Added: format rule NA RULE-6941







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-POA-FLAG-12 CIP067











3,278 Added: format rule NA RULE-6942







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG062











3,279 Added: format rule NA RULE-6943







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER CRX018











3,280 Added: format rule NA RULE-6944







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(1) ACCEPTING-NEW-PATIENTS-IND PRV036











3,281 Added: format rule NA RULE-6945







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LOCK-IN-INFORMATION ELG00009



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG144











3,282 Added: format rule NA RULE-6946







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CIP001











3,283 Added: format rule NA RULE-6947







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(2) SERVICING-PROV-TYPE CIP263











3,284 Added: format rule NA RULE-6948







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS CLT054











3,285 Added: format rule NA RULE-6949







1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG230











3,286 Added: format rule NA RULE-6950







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID CIP021











3,287 Added: format rule NA RULE-6951







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ADJ CIP020











3,288 Added: format rule NA RULE-6952







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(2) SERVICING-PROV-SPECIALTY CLT216











3,289 Added: format rule NA RULE-6953







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(12) SUBMITTER-ID CLT194











3,290 Added: format rule NA RULE-6954







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV016











3,291 Added: format rule NA RULE-6955







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG030











3,292 Added: format rule NA RULE-6956







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) 1115A-DEMONSTRATION-IND CIP025











3,293 Added: format rule NA RULE-6957







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(60) DESTINATION-ADDR-LN1 COT204











3,294 Added: format rule NA RULE-6958







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(60) DESTINATION-ADDR-LN2 COT205











3,295 Added: format rule NA RULE-6959







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be compatible with specified T-MSIS picture format: X(2) INSURANCE-PLAN-TYPE TPL037











3,296 Added: format rule NA RULE-6960







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR082











3,297 Added: format rule NA RULE-6961







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(3) LEVEL-OF-CARE-STATUS ELG088











3,298 Added: format rule NA RULE-6962







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION PRV005











3,299 Added: format rule NA RULE-6963







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be compatible with specified T-MSIS picture format: X(2) ACCREDITATION-ORGANIZATION MCR086











3,300 Added: format rule NA RULE-6964







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) ADMITTING-PROV-SPECIALTY CIP186











3,301 Added: format rule NA RULE-6965







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be a valid date of the form CCYYMMDD DATE-OF-BIRTH PRV034











3,302 Added: format rule NA RULE-6966







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PARTICIPATION ELG00014



Value must be compatible with specified T-MSIS picture format: X(1) NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE ELG195











3,303 Added: format rule NA RULE-6967







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) PLAN-ID-NUMBER CIP130











3,304 Added: format rule NA RULE-6968







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(10) INSURANCE-CARRIER-NAIC-CODE TPL090











3,305 Added: format rule NA RULE-6969







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION MCR005











3,306 Added: format rule NA RULE-6970







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) FIXED-PAYMENT-IND CIP125











3,307 Added: format rule NA RULE-6971







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(60) ADDR-LN1 PRV047











3,308 Added: format rule NA RULE-6972







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(60) ADDR-LN3 PRV049











3,309 Added: format rule NA RULE-6973







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(60) ADDR-LN2 PRV048











3,310 Added: format rule NA RULE-6975







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION MCR004











3,311 Added: format rule NA RULE-6976







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) SERVICE-TRACKING-TYPE CRX050











3,312 Added: format rule NA RULE-6977







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be compatible with specified T-MSIS picture format: X(1) ETHNICITY-CODE ELG204











3,313 Added: format rule NA RULE-6978







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) ADJUSTMENT-IND CIP026











3,314 Added: format rule NA RULE-6979







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) BENEFIT-TYPE CRX148











3,315 Added: format rule NA RULE-6980







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR TPL011











3,316 Added: format rule NA RULE-6981







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(50) HEALTH-HOME-ENTITY-NAME CRX096











3,317 Added: format rule NA RULE-6982







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG210











3,318 Added: format rule NA RULE-6983







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(2) CMS-64-CATEGORY-FOR-FEDERAL-REIMBURSEMENT CLT219











3,319 Added: format rule NA RULE-6984







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-OT COT00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE COT003











3,320 Added: format rule NA RULE-6986







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) ELIGIBLE-MIDDLE-INIT CRX065











3,321 Added: format rule NA RULE-6987







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-4 CLT039











3,322 Added: format rule NA RULE-6988







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR063











3,323 Added: format rule NA RULE-6989







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-3 CLT036











3,324 Added: format rule NA RULE-6990







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG201











3,325 Added: format rule NA RULE-6991







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-5 CLT042











3,326 Added: format rule NA RULE-6992







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-LAST-NAME ELG021











3,327 Added: format rule NA RULE-6993







1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG160











3,328 Added: format rule NA RULE-6994







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG080











3,329 Added: format rule NA RULE-6995







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-2 CLT033











3,330 Added: format rule NA RULE-6996







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(1) DIAGNOSIS-CODE-FLAG-1 CLT030











3,331 Added: format rule NA RULE-6997







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: S9(6)V999 BIRTH-WEIGHT-GRAMS CIP170











3,332 Added: format rule NA RULE-6998







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(2) MFP-REINSTITUTIONALIZED-REASON ELG154











3,333 Added: format rule NA RULE-6999







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME PRV006











3,334 Added: format rule NA RULE-7000







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-MANAGED-CARE MCR00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR MCR011











3,335 Added: format rule NA RULE-7001







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG CIP019











3,336 Added: format rule NA RULE-7003







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(10) DATA-DICTIONARY-VERSION CRX002











3,337 Added: format rule NA RULE-7004







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(12) MSIS-CASE-NUM ELG083











3,338 Added: format rule NA RULE-7005







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(4) TYPE-OF-BILL CLT053











3,339 Added: format rule NA RULE-7006







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-BENEFICIARY-IDENTIFIER CIP222











3,340 Added: format rule NA RULE-7008







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-STATUS CIP102











3,341 Added: format rule NA RULE-7009







1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG221











3,342 Added: format rule NA RULE-7010







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE TPL007











3,343 Added: format rule NA RULE-7011







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-SPA-PROVIDERS ELG00007



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG124











3,344 Added: format rule NA RULE-7012







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(2) NEW-REFILL-IND CRX139











3,345 Added: format rule NA RULE-7013







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) REFERRING-PROV-SPECIALTY CLT139











3,346 Added: format rule NA RULE-7014







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(2) MANAGED-CARE-PLAN-TYPE MCR024











3,347 Added: format rule NA RULE-7015







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBILITY-DETERMINANTS ELG00005



Value must be compatible with specified T-MSIS picture format: X(6) STATE-SPEC-ELIG-GROUP ELG093











3,348 Added: format rule NA RULE-7016







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) BORDER-STATE-IND COT128











3,349 Added: format rule NA RULE-7017







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION COT152











3,350 Added: format rule NA RULE-7018







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION COT058











3,351 Added: format rule NA RULE-7019







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(1) LINE-ADJUSTMENT-IND COT162











3,352 Added: format rule NA RULE-7020







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) IMMUNIZATION-TYPE COT173











3,353 Added: format rule NA RULE-7021







1 Formatting Error E1001 Value illegal for specified data type Parse Rule NATIONAL-HEALTH-CARE-ENTITY-ID-INFO MCR00008



Value must be compatible with specified T-MSIS picture format: X(50) NATIONAL-HEALTH-CARE-ENTITY-NAME MCR097











3,354 Added: format rule NA RULE-7022







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(9) DATA-MAPPING-DOCUMENT-VERSION CRX005











3,355 Added: format rule NA RULE-7024







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION CLT217











3,356 Added: format rule NA RULE-7025







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) OTHER-INSURANCE-IND CIP121











3,357 Added: format rule NA RULE-7026







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) OUTLIER-CODE CIP197











3,358 Added: format rule NA RULE-7027







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(4) XIX-MBESCBES-CATEGORY-OF-SERVICE COT211











3,359 Added: format rule NA RULE-7028







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) LINE-NUM-ORIG CLT190











3,360 Added: format rule NA RULE-7029







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-PLAN-POPULATION-ENROLLED MCR00006



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR076











3,361 Added: format rule NA RULE-7030







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER TPL088











3,362 Added: format rule NA RULE-7031







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER CRX110











3,363 Added: format rule NA RULE-7032







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(10) ADMITTING-PROV-NPI-NUM CIP184











3,364 Added: format rule NA RULE-7033







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) FUNDING-SOURCE-NONFEDERAL-SHARE CLT077











3,365 Added: format rule NA RULE-7034







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(2) PLACE-OF-SERVICE COT123











3,366 Added: format rule NA RULE-7035







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CHPID-SHPID-RELATIONSHIPS MCR00009



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE MCR102











3,367 Added: format rule NA RULE-7036







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(1) TEACHING-IND PRV027











3,368 Added: format rule NA RULE-7037







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(1) MEDICARE-COMB-DED-IND COT064











3,369 Added: format rule NA RULE-7038







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(3) XXI-MBESCBES-CATEGORY-OF-SERVICE CRX151











3,370 Added: format rule NA RULE-7039







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) CROSSOVER-INDICATOR CIP023











3,371 Added: format rule NA RULE-7040







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-4 CIP111











3,372 Added: format rule NA RULE-7041







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(1) ADDR-BORDER-STATE-IND PRV056











3,373 Added: format rule NA RULE-7042







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV113











3,374 Added: format rule NA RULE-7043







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: X(25) RACE-OTHER ELG214











3,375 Added: format rule NA RULE-7044







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(8) FILE-NAME CRX006











3,376 Added: format rule NA RULE-7045







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-MAIN MCR00002



Value must be compatible with specified T-MSIS picture format: X(1) MANAGED-CARE-SERVICE-AREA MCR029











3,377 Added: format rule NA RULE-7046







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(10) UNDER-SUPERVISION-OF-PROV-NPI CIP226











3,378 Added: format rule NA RULE-7047







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(2) NDC-UNIT-OF-MEASURE CIP285











3,379 Added: format rule NA RULE-7048







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(12) ADMITTING-PROV-TAXONOMY CLT177











3,380 Added: format rule NA RULE-7049







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(6) DRUG-UTILIZATION-CODE CRX143











3,381 Added: format rule NA RULE-7050







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(30) BILLING-PROV-NUM CLT130











3,382 Added: format rule NA RULE-7051







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: X(100) PROV-TAX-NAME PRV025











3,383 Added: format rule NA RULE-7052







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE CRX109











3,384 Added: format rule NA RULE-7053







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG127











3,385 Added: format rule NA RULE-7054







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG CRX019











3,386 Added: format rule NA RULE-7055







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) REFERRING-PROV-TYPE CIP192











3,387 Added: format rule NA RULE-7056







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be compatible with specified T-MSIS picture format: X(1) HEALTH-HOME-CHRONIC-CONDITION ELG130











3,388 Added: format rule NA RULE-7057







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(50) ICN-ORIG COT158











3,389 Added: format rule NA RULE-7058







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(7) ADMITTING-DIAGNOSIS-CODE CIP030











3,390 Added: format rule NA RULE-7059







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(12) SERVICING-PROV-TAXONOMY COT191











3,391 Added: format rule NA RULE-7060







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(12) NATIONAL-DRUG-CODE CRX120











3,392 Added: format rule NA RULE-7061







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(2) BILLING-PROV-SPECIALTY CRX073











3,393 Added: format rule NA RULE-7062







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(12) SERVICING-PROV-TAXONOMY CLT214











3,394 Added: format rule NA RULE-7063







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ETHNICITY-INFORMATION ELG00015



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG203











3,395 Added: format rule NA RULE-7064







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV084











3,396 Added: format rule NA RULE-7065







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(3) CLAIM-LINE-STATUS CLT195











3,397 Added: format rule NA RULE-7066







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE TPL073











3,398 Added: format rule NA RULE-7067







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-LOCATION-AND-CONTACT-INFO MCR00003



Value must be compatible with specified T-MSIS picture format: X(15) MANAGED-CARE-LOCATION-ID MCR038











3,399 Added: format rule NA RULE-7068







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) COPAY-WAIVED-IND CIP213











3,400 Added: format rule NA RULE-7069







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) PROCEDURE-CODE-FLAG COT171











3,401 Added: format rule NA RULE-7070







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV107











3,402 Added: format rule NA RULE-7071







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(50) HEALTH-HOME-ENTITY-NAME COT138











3,403 Added: format rule NA RULE-7072







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(2) ELIGIBLE-STATE ELG070











3,404 Added: format rule NA RULE-7073







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION PRV123











3,405 Added: format rule NA RULE-7074







1 Formatting Error E1001 Value illegal for specified data type Parse Rule DISABILITY-INFORMATION ELG00017



Value must be compatible with specified T-MSIS picture format: X(2) DISABILITY-TYPE-CODE ELG224











3,406 Added: format rule NA RULE-7075







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR CRX011











3,407 Added: format rule NA RULE-7077







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(14) HCPCS-RATE CIP279











3,408 Added: format rule NA RULE-7078







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(1) PRIMARY-LANGUAGE-ENGL-PROF-CODE ELG045











3,409 Added: format rule NA RULE-7079







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(10) UNDER-DIRECTION-OF-PROV-NPI CIP224











3,410 Added: format rule NA RULE-7080







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) BILLING-PROV-TAXONOMY COT114











3,411 Added: format rule NA RULE-7081







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(10) PRESCRIBING-PROV-NPI-NUM CRX075











3,412 Added: format rule NA RULE-7082







1 Formatting Error E1001 Value illegal for specified data type Parse Rule ELIGIBLE-CONTACT-INFORMATION ELG00004



Value must be compatible with specified T-MSIS picture format: X(9) ELIGIBLE-ZIP-CODE ELG071











3,413 Added: format rule NA RULE-7083







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-2 CIP109











3,414 Added: format rule NA RULE-7084







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(5) CLAIM-PYMT-REM-CODE-3 CIP110











3,415 Added: format rule NA RULE-7085







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG033











3,416 Added: format rule NA RULE-7087







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-LT CLT00003



Value must be compatible with specified T-MSIS picture format: X(9) PROV-FACILITY-TYPE CLT221











3,417 Added: format rule NA RULE-7088







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-OPERATING-AUTHORITY MCR00005



Value must be compatible with specified T-MSIS picture format: X(2) OPERATING-AUTHORITY MCR067











3,418 Added: format rule NA RULE-7089







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE PRV060











3,419 Added: format rule NA RULE-7090







1 Formatting Error E1001 Value illegal for specified data type Parse Rule RACE-INFORMATION ELG00016



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG209











3,420 Added: format rule NA RULE-7092







1 Formatting Error E1001 Value illegal for specified data type Parse Rule 1115A-DEMONSTRATION-INFORMATION ELG00018



Value must be compatible with specified T-MSIS picture format: X(1) 1115A-DEMONSTRATION-IND ELG233











3,421 Added: format rule NA RULE-7093







1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be compatible with specified T-MSIS picture format: X(30) ELIGIBLE-LAST-NAME TPL024











3,422 Added: format rule NA RULE-7094







1 Formatting Error E1001 Value illegal for specified data type Parse Rule VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



Value must be compatible with specified T-MSIS picture format: X(50) MARITAL-STATUS-OTHER-EXPLANATION ELG035











3,423 Added: format rule NA RULE-7095







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(1) FILE-STATUS-INDICATOR CIP011











3,424 Added: format rule NA RULE-7097







1 Formatting Error E1001 Value illegal for specified data type Parse Rule STATE-PLAN-OPTION-PARTICIPATION ELG00011



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG159











3,425 Added: format rule NA RULE-7098







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-IP CIP00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CIP231











3,426 Added: format rule NA RULE-7099







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG157











3,427 Added: format rule NA RULE-7100







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE PRV007











3,428 Added: format rule NA RULE-7101







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MANAGED-CARE-ACCREDITATION-ORGANIZATION MCR00007



Value must be compatible with specified T-MSIS picture format: X(12) STATE-PLAN-ID-NUM MCR085











3,429 Added: format rule NA RULE-7102







1 Formatting Error E1001 Value illegal for specified data type Parse Rule LTSS-PARTICIPATION ELG00013



Value must be compatible with specified T-MSIS picture format: X(2) SUBMITTING-STATE ELG179











3,430 Added: format rule NA RULE-7103







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-ELIGIBILITY ELG00001



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE ELG001











3,431 Added: format rule NA RULE-7104







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HCBS-CHRONIC-CONDITIONS-NON-HEALTH-HOME ELG00020



Value must be compatible with specified T-MSIS picture format: X(3) HCBS-CHRONIC-CONDITION-NON-HEALTH-HOME-CODE ELG242











3,432 Added: format rule NA RULE-7105







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: X(12) MEDICARE-BENEFICIARY-IDENTIFIER COT147











3,433 Added: format rule NA RULE-7106







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-IP CIP00001



Value must be compatible with specified T-MSIS picture format: X(3) FILE-ENCODING-SPECIFICATION CIP004











3,434 Added: format rule NA RULE-7107







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) COPAY-WAIVED-IND CRX095











3,435 Added: format rule NA RULE-7108







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be compatible with specified T-MSIS picture format: X(30) SUBMITTING-STATE-PROV-ID PRV118











3,436 Added: format rule NA RULE-7109







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CLT016











3,437 Added: format rule NA RULE-7110







1 Formatting Error E1001 Value illegal for specified data type Parse Rule MFP-INFORMATION ELG00010



Value must be compatible with specified T-MSIS picture format: X(2) MFP-REASON-PARTICIPATION-ENDED ELG153











3,438 Added: format rule NA RULE-7111







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002



Value must be compatible with specified T-MSIS picture format: X(500) STATE-NOTATION ELG028











3,439 Added: format rule NA RULE-7112







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(1) ADMISSION-TYPE CIP028











3,440 Added: format rule NA RULE-7113







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: 9(4) CLAIM-LINE-COUNT COT070











3,441 Added: format rule NA RULE-7114







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(3) OTHER-TPL-COLLECTION CLT072











3,442 Added: format rule NA RULE-7115







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(2) TOOTH-QUAD-CODE COT197











3,443 Added: format rule NA RULE-7117







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-LT CLT00002



Value must be compatible with specified T-MSIS picture format: X(2) DISCHARGE-HOUR CLT047











3,444 Added: format rule NA RULE-7118







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-OT COT00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER COT018











3,445 Added: format rule NA RULE-7119







1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-RX CRX00001



Value must be compatible with specified T-MSIS picture format: X(1) SUBMISSION-TRANSACTION-TYPE CRX003











3,446 Added: format rule NA RULE-7120







1 Formatting Error E1001 Value illegal for specified data type Parse Rule HEALTH-HOME-CHRONIC-CONDITIONS ELG00008



Value must be compatible with specified T-MSIS picture format: X(20) MSIS-IDENTIFICATION-NUM ELG129











3,447 Added: format rule NA RULE-7121







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-IP CIP00002



Value must be compatible with specified T-MSIS picture format: X(2) ADMISSION-HOUR CIP095











3,448 Added: format rule NA RULE-7123







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-OT COT00003



Value must be compatible with specified T-MSIS picture format: X(30) SERVICING-PROV-NUM COT189











3,449 Added: format rule NA RULE-7124







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-LINE-RECORD-RX CRX00003



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE CRX108











3,450 Added: format rule NA RULE-7125







1 Formatting Error E1001 Value illegal for specified data type Parse Rule CLAIM-HEADER-RECORD-RX CRX00002



Value must be compatible with specified T-MSIS picture format: X(1) ADJUSTMENT-IND CRX025











3,451 Added: format rule NA RULE-7126







1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: X(1) PROV-ENROLLMENT-METHOD PRV102











3,452 Added: consistency NA RULE-7127







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-6 CIP049











3,453 Added: consistency NA RULE-7128







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-7 CIP052











3,454 Added: consistency NA RULE-7129







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-8 CIP055











3,455 Added: consistency NA RULE-7130







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-9 CIP058











3,456 Added: consistency NA RULE-7131







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-10 CIP061











3,457 Added: consistency NA RULE-7132







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-11 CIP064











3,458 Added: consistency NA RULE-7133







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-HEADER-RECORD-IP CIP00002



If the field is populated, the value must be contained in the set of valid values with id: DIAGNOSIS-POA-FLAG DIAGNOSIS-POA-FLAG-12 CIP067











3,459 Added: consistency NA RULE-7134







1.1 Value Error E1103 Value not in specified valid value set Valid Value CLAIM-LINE-RECORD-OT COT00003



If the field is populated, the value must be contained in the set of valid values with id: HCBS-SERVICE-CODE HCBS-SERVICE-CODE COT187











3,460 Added: consistency NA RULE-7142







1.1 Value Error E1103 Value not in specified valid value set Valid Value VARIABLE-DEMOGRAPHICS-ELIGIBILITY ELG00003



If the field is populated, the value must be contained in the set of valid values with id: MARITAL-STATUS MARITAL-STATUS ELG034











3,461 Added: format rule NA RULE-7143







1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-LAST-NAME), then fns.matches(@val.PROV-LAST-NAME, "^[^|*]*$")' PROV-LAST-NAME PRV030











3,462 Added: format rule NA RULE-7144







1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV082











3,463 Added: format rule NA RULE-7149







1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.ADDR-TELEPHONE), then fns.isNumericString(@val.ADDR-TELEPHONE)' ADDR-TELEPHONE PRV053











3,464 Moved to R&C PRV001-0001
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,465 Moved to R&C PRV001-0004
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV001 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,466 Moved to R&C PRV003-0001
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV003 SUBMISSION-TRANSACTION-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,467 Moved to R&C PRV004-0001
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV004 FILE-ENCODING-SPECIFICATION 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,468 Moved to R&C PRV006-0002
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV006 FILE-NAME 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,469 Moved to R&C PRV007-0001
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV007 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,470 Moved to R&C PRV007-0005
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























3,471 Merged PRV008-0001 RULE-2766 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED PRV008











3,472 Merged PRV008-0002 RULE-2766 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED PRV008











3,473 Moved to R&C PRV008-0004
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed

























3,474 Moved to R&C PRV008-0005
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























3,475 Merged PRV009-0001 RULE-2770 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD PRV009











3,476 Merged PRV009-0002 RULE-2770 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV009 START-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD PRV009











3,477 Moved to R&C PRV009-0005
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























3,478 Moved to R&C PRV009-0006
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























3,479 Merged PRV010-0001 RULE-2774 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD PRV010











3,480 Merged PRV010-0002 RULE-2774 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV010 END-OF-TIME-PERIOD 1 If END-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD PRV010











3,481 Moved to R&C PRV010-0004
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV010 END-OF-TIME-PERIOD 2-M
2019


























3,482 Moved to R&C PRV010-0005
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV010 END-OF-TIME-PERIOD 2-M
2122


























3,483 Moved to R&C PRV011-0001
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV011 FILE-STATUS-INDICATOR 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,484 Moved to R&C PRV011-0003
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























3,485 No logic changes PRV013-0001 RULE-6727 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV013 TOT-REC-CNT 1 If TOT-REC-CNT = 0 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: 9(11) TOT-REC-CNT PRV013











3,486 Moved to R&C PRV013-0002
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record

























3,487 Moved to R&C PRV014-0001
PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























3,488 Moved to R&C PRV016-0001
PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,489 Moved to R&C PRV016-0004
PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV016 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,490 No logic changes PRV017-0001 RULE-2785 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV017 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-ATTRIBUTES-MAIN PRV00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV017











3,491 Logic updated: other PRV017-0004 RULE-2786 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-ATTRIBUTES-MAIN PRV00002 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV017 SUBMITTING-STATE PRV007









3,492 No logic changes PRV018-0001 RULE-6858 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV018 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV018











3,493 No logic changes PRV018-0003 RULE-2788 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-ATTRIBUTES-MAIN PRV00002



Field RECORD-NUMBER should be unique across all records of type PROV-ATTRIBUTES-MAIN RECORD-NUMBER PRV018











3,494 Retired: required value checks PRV019-0001
PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV019 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,495 Merged PRV020-0001 RULE-2790 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV020 PROV-ATTRIBUTES-EFF-DATE 1 If PROV-ATTRIBUTES-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be a valid date of the form CCYYMMDD PROV-ATTRIBUTES-EFF-DATE PRV020











3,496 Merged PRV020-0002 RULE-2790 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV020 PROV-ATTRIBUTES-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be a valid date of the form CCYYMMDD PROV-ATTRIBUTES-EFF-DATE PRV020











3,497 Merged PRV020-0006 RULE-2792 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV020 PROV-ATTRIBUTES-EFF-DATE 2 PROV-ATTRIBUTES-EFF-DATE must be <= PROV-ATTRIBUTES-END-DATE 2108 Relational edit between PROV-ATTRIBUTES-EFF-DATE and PROV-ATTRIBUTES-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-ATTRIBUTES-EFF-DATE) && fns.hasValue(@val.PROV-ATTRIBUTES-END-DATE), then fns.isLessThanOrEqual(@val.PROV-ATTRIBUTES-EFF-DATE, @val.PROV-ATTRIBUTES-END-DATE)' PROV-ATTRIBUTES-EFF-DATE,PROV-ATTRIBUTES-END-DATE PRV020,PRV021











3,498 No logic changes PRV020-0007 RULE-2793 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV020 PROV-ATTRIBUTES-EFF-DATE 2 If two or more PROV-ATTRIBUTES-MAIN record segments have the same SUBMITTING-STATE and SUBMITTING-STATE-PROV-ID
then for each pair of record segments,
(Segment 1 PROV-ATTRIBUTES-EFF-DATE must <> Segment 2 PROV-ATTRIBUTES-EFF-DATE)
AND
( (If Segment 1 PROV-ATTRIBUTES-EFF-DATE < Segment 2 PROV-ATTRIBUTES-EFF-DATE,
then
Segment 1 PROV-ATTRIBUTES-END-DATE must be < Segment 2 PROV-ATTRIBUTES-EFF-DATE)
OR
(If Segment 2 PROV-ATTRIBUTES-EFF-DATE < Segment 1 PROV-ATTRIBUTES-EFF-DATE,
then
Segment 2 PROV-ATTRIBUTES-END-DATE must be < Segment 1 PROV-ATTRIBUTES-EFF-DATE) )		 2171 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-ATTRIBUTES-MAIN failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-ATTRIBUTES-MAIN PRV00002



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-ATTRIBUTES-EFF-DATE. End date field: PROV-ATTRIBUTES-END-DATE PROV-ATTRIBUTES-EFF-DATE,PROV-ATTRIBUTES-END-DATE PRV020,PRV021











3,499 Retired: Other reasons PRV020-0009
PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV020 PROV-ATTRIBUTES-EFF-DATE 2 If two or more PROV-ATTRIBUTES-MAIN record segments have the same SUBMITTING-STATE and SUBMITTING-STATE-PROV-ID and these record segments are sorted in ascending order by PROV-ATTRIBUTES-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N PROV-ATTRIBUTES-END-DATE must = Segment (N+1) PROV-ATTRIBUTES-EFF-DATE minus 1 day 2456 Edit for contiguous PROV-ATTRIBUTES-MAIN record segments failed (Exact match on all key fields except the file segment effective date)

























3,500 Merged PRV021-0001 RULE-2795 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV021 PROV-ATTRIBUTES-END-DATE 1 If PROV-ATTRIBUTES-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be a valid date of the form CCYYMMDD PROV-ATTRIBUTES-END-DATE PRV021











3,501 Merged PRV021-0002 RULE-2795 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV021 PROV-ATTRIBUTES-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-ATTRIBUTES-MAIN PRV00002



Value must be a valid date of the form CCYYMMDD PROV-ATTRIBUTES-END-DATE PRV021











3,502 Merged PRV021-0004 RULE-2792 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV021 PROV-ATTRIBUTES-END-DATE 2-M
2108
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-ATTRIBUTES-EFF-DATE) && fns.hasValue(@val.PROV-ATTRIBUTES-END-DATE), then fns.isLessThanOrEqual(@val.PROV-ATTRIBUTES-EFF-DATE, @val.PROV-ATTRIBUTES-END-DATE)' PROV-ATTRIBUTES-EFF-DATE,PROV-ATTRIBUTES-END-DATE PRV020,PRV021











3,503 Logic updated: string matching PRV022-0001 RULE-2798 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV022 PROV-DOING-BUSINESS-AS-NAME 1 Field contains invalid characters - PROV-DOING-BUSINESS-AS-NAME 120 Field contains invalid characters - PROV-DOING-BUSINESS-AS-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-DOING-BUSINESS-AS-NAME), then fns.matches(@val.PROV-DOING-BUSINESS-AS-NAME, "^[^|*]*$")' PROV-DOING-BUSINESS-AS-NAME PRV022











3,504 Logic updated: string matching PRV023-0002 RULE-2799 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV023 PROV-LEGAL-NAME 1 Field contains invalid characters - PROV-LEGAL-NAME 120 Field contains invalid characters - PROV-LEGAL-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-LEGAL-NAME), then fns.matches(@val.PROV-LEGAL-NAME, "^[^|*]*$")' PROV-LEGAL-NAME PRV023











3,505 Logic updated: string matching PRV024-0002 RULE-2800 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV024 PROV-ORGANIZATION-NAME 1 Field contains invalid characters - PROV-ORGANIZATION-NAME 120 Field contains invalid characters - PROV-ORGANIZATION-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-ORGANIZATION-NAME), then fns.matches(@val.PROV-ORGANIZATION-NAME, "^[^|*]*$")' PROV-ORGANIZATION-NAME PRV024











3,506 Retired: required value checks PRV025-0001
PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV025 PROV-TAX-NAME 1 If PROV-TAX-NAME = spaces 113 Required data element has not been reported.

























3,507 Logic updated: string matching PRV025-0002 RULE-2802 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV025 PROV-TAX-NAME 1 Field contains invalid characters - PROV-TAX-NAME 120 Field contains invalid characters - PROV-TAX-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-TAX-NAME), then fns.matches(@val.PROV-TAX-NAME, "^[^|*]*$")' PROV-TAX-NAME PRV025











3,508 No logic changes PRV026-0001 RULE-2803 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV026 FACILITY-GROUP-INDIVIDUAL-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-ATTRIBUTES-MAIN PRV00002



If the field is populated, the value must be contained in the set of valid values with id: FACILITY-GROUP-INDIVIDUAL-CODE FACILITY-GROUP-INDIVIDUAL-CODE PRV026











3,509 No logic changes PRV027-0001 RULE-2804 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV027 TEACHING-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-ATTRIBUTES-MAIN PRV00002



If the field is populated, the value must be contained in the set of valid values with id: TEACHING-IND TEACHING-IND PRV027











3,510 Logic updated: string matching PRV028-0001 RULE-2805 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV028 PROV-FIRST-NAME 1 PROV-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid character - PROV-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-FIRST-NAME), then fns.matches(@val.PROV-FIRST-NAME, "^[^|*]*$")' PROV-FIRST-NAME PRV028











3,511 Merged PRV028-0002 RULE-2806 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV028 PROV-FIRST-NAME 2 If FACILITY-GROUP-INDIVIDUAL-CODE <> "03" , then PROV-FIRST-NAME must be 8-filled 2392 Relational edit between PROV-FIRST-NAME and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.PROV-FIRST-NAME)' FACILITY-GROUP-INDIVIDUAL-CODE,PROV-FIRST-NAME PRV026,PRV028











3,512 Merged PRV028-0004 RULE-2806 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV028 PROV-FIRST-NAME 2 If FACILITY-GROUP-INDIVIDUAL-CODE = "03" , then PROV-FIRST-NAME must not be 8-filled 2392 Relational edit between PROV-FIRST-NAME and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.PROV-FIRST-NAME)' FACILITY-GROUP-INDIVIDUAL-CODE,PROV-FIRST-NAME PRV026,PRV028











3,513 Logic updated: string matching PRV029-0001 RULE-2808 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV029 PROV-MIDDLE-INITIAL 1 PROV-MIDDLE-INITIAL must not contain non-alphabetic characters 120 Field contains invalid characters - PROV-MIDDLE-INITIAL 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.PROV-MIDDLE-INITIAL), then fns.matches(@val.PROV-MIDDLE-INITIAL, "^[^|*]*$")' PROV-MIDDLE-INITIAL PRV029











3,514 No logic changes PRV029-0003 RULE-2809 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV029 PROV-MIDDLE-INITIAL 2 If FACILITY-GROUP-INDIVIDUAL-CODE <> "03", then PROV-MIDDLE-INITIAL must be 8-filled 2401 Relational edit between PROV-MIDDLE-INITIAL and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if !fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then !fns.hasValue(@val.PROV-MIDDLE-INITIAL)' FACILITY-GROUP-INDIVIDUAL-CODE,PROV-MIDDLE-INITIAL PRV026,PRV029











3,515 Merged PRV030-0002 RULE-2810 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV030 PROV-LAST-NAME 2 If FACILITY-GROUP-INDIVIDUAL-CODE <> "03" , then PROV-LAST-NAME must be 8-filled 2397 Relational edit between PROV-LAST-NAME and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.PROV-LAST-NAME)' FACILITY-GROUP-INDIVIDUAL-CODE,PROV-LAST-NAME PRV026,PRV030











3,516 Merged PRV030-0005 RULE-2810 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV030 PROV-LAST-NAME 2 If FACILITY-GROUP-INDIVIDUAL-CODE = "03" , then PROV-LAST-NAME must not be 8-filled 2397 Relational edit between PROV-LAST-NAME and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.PROV-LAST-NAME)' FACILITY-GROUP-INDIVIDUAL-CODE,PROV-LAST-NAME PRV026,PRV030











3,517 No logic changes PRV031-0001 RULE-2812 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV031 SEX 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-ATTRIBUTES-MAIN PRV00002



If the field is populated, the value must be contained in the set of valid values with id: SEX SEX PRV031











3,518 Merged PRV031-0002 RULE-2813 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV031 SEX 2 If FACILITY-GROUP-INDIVIDUAL-CODE = "03", then SEX must not be 8-filled 2415 Relational edit between SEX and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.SEX)' FACILITY-GROUP-INDIVIDUAL-CODE,SEX PRV026,PRV031











3,519 Merged PRV031-0003 RULE-2813 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV031 SEX 2 If FACILITY-GROUP-INDIVIDUAL-CODE <>"03", then SEX must be 8-filled 2415 Relational edit between SEX and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.SEX)' FACILITY-GROUP-INDIVIDUAL-CODE,SEX PRV026,PRV031











3,520 No logic changes PRV032-0001 RULE-2815 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV032 OWNERSHIP-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-ATTRIBUTES-MAIN PRV00002



If the field is populated, the value must be contained in the set of valid values with id: OWNERSHIP-CODE OWNERSHIP-CODE PRV032











3,521 No logic changes PRV033-0001 RULE-2816 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV033 PROV-PROFIT-STATUS 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-ATTRIBUTES-MAIN PRV00002



If the field is populated, the value must be contained in the set of valid values with id: PROV-PROFIT-STATUS PROV-PROFIT-STATUS PRV033











3,522 Merged PRV034-0001 RULE-2817 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV034 DATE-OF-BIRTH 2 If FACILITY-GROUP-INDIVIDUAL-CODE = "03", then DATE-OF-BIRTH must not be 8-filled 2249 Relational edit between DATE-OF-BIRTH and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.DATE-OF-BIRTH)' FACILITY-GROUP-INDIVIDUAL-CODE,DATE-OF-BIRTH PRV026,PRV034











3,523 Logic updated: other PRV034-0003 RULE-2818 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV034 DATE-OF-BIRTH 2 DATE-OF-BIRTH must be <= END-OF-TIME-PERIOD 2248 Relational edit between DATE-OF-BIRTH and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-ATTRIBUTES-MAIN PRV00002 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.DATE-OF-BIRTH) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.DATE-OF-BIRTH, @fileHeader.END-OF-TIME-PERIOD)' DATE-OF-BIRTH PRV034 END-OF-TIME-PERIOD PRV010









3,524 Merged PRV034-0004 RULE-2817 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV034 DATE-OF-BIRTH 2 If FACILITY-GROUP-INDIVIDUAL-CODE <> "03", then DATE-OF-BIRTH must be 8-filled 2249 Relational edit between DATE-OF-BIRTH and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if and only if fns.isEqual(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "03"), then fns.hasValue(@val.DATE-OF-BIRTH)' FACILITY-GROUP-INDIVIDUAL-CODE,DATE-OF-BIRTH PRV026,PRV034











3,525 Logic updated: other PRV034-0005 RULE-2820 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV034 DATE-OF-BIRTH 2 DATE-OF-BIRTH must be >= (START-OF-TIME-PERIOD minus 85 years) and DATE-OF-BIRTH <= (START-OF-TIME-PERIOD minus 18 years) 2250 Relational edit between DATE-OF-BIRTH and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-ATTRIBUTES-MAIN PRV00002 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.DATE-OF-BIRTH) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD) && fns.hasValue(@fileHeader.START-OF-TIME-PERIOD), then fns.isDifferenceInYearsLessThanOrEqual(@val.DATE-OF-BIRTH, @fileHeader.START-OF-TIME-PERIOD, 85) && !fns.isDifferenceInYearsLessThan(@val.DATE-OF-BIRTH, @fileHeader.START-OF-TIME-PERIOD, 18)' DATE-OF-BIRTH PRV034 END-OF-TIME-PERIOD,START-OF-TIME-PERIOD PRV010,PRV009









3,526 Merged PRV034-0006 RULE-2821 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV034 DATE-OF-BIRTH 2 If DATE-OF-DEATH is not 8-filled, DATE-OF-BIRTH must be <= DATE-OF-DEATH minus 18 years 2247 Relational edit between DATE-OF-BIRTH and DATE-OF-DEATH failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.DATE-OF-DEATH) && fns.hasValue(@val.DATE-OF-BIRTH), then !fns.isDifferenceInYearsLessThan(@val.DATE-OF-BIRTH, @val.DATE-OF-DEATH, 18)' DATE-OF-DEATH,DATE-OF-BIRTH PRV035,PRV034











3,527 No logic changes PRV035-0003 RULE-2822 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV035 DATE-OF-DEATH 2 If FACILITY-GROUP-INDIVIDUAL-CODE = 01 or 02, then DATE-OF-DEATH must be 8-filled 2255 Relational edit between DATE-OF-DEATH and FACILITY-GROUP-INDIVIDUAL-CODE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.isEqualToAny(@val.FACILITY-GROUP-INDIVIDUAL-CODE, "01", "02"), then !fns.hasValue(@val.DATE-OF-DEATH)' FACILITY-GROUP-INDIVIDUAL-CODE,DATE-OF-DEATH PRV026,PRV035











3,528 Logic updated: other PRV035-0004 RULE-2823 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV035 DATE-OF-DEATH 2 If DATE-OF-DEATH is not 8-filled, DATE-OF-DEATH must be <= END-OF-TIME-PERIOD 2254 Relational edit between DATE-OF-DEATH and END-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-ATTRIBUTES-MAIN PRV00002 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.DATE-OF-DEATH) && fns.hasValue(@fileHeader.END-OF-TIME-PERIOD), then fns.isLessThanOrEqual(@val.DATE-OF-DEATH, @fileHeader.END-OF-TIME-PERIOD)' DATE-OF-DEATH PRV035 END-OF-TIME-PERIOD PRV010









3,529 Merged PRV035-0005 RULE-2821 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV035 DATE-OF-DEATH 2-M
2247
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.DATE-OF-DEATH) && fns.hasValue(@val.DATE-OF-BIRTH), then !fns.isDifferenceInYearsLessThan(@val.DATE-OF-BIRTH, @val.DATE-OF-DEATH, 18)' DATE-OF-DEATH,DATE-OF-BIRTH PRV035,PRV034











3,530 No logic changes PRV036-0001 RULE-2825 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV036 ACCEPTING-NEW-PATIENTS-IND 1 The value must be in the list of valid values. 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-ATTRIBUTES-MAIN PRV00002



If the field is populated, the value must be contained in the set of valid values with id: ACCEPTING-NEW-PATIENTS-IND ACCEPTING-NEW-PATIENTS-IND PRV036











3,531 Logic updated: string matching PRV037-0001 RULE-2826 PROVIDER PROV-ATTRIBUTES-MAIN-PRV00002 PRV037 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-ATTRIBUTES-MAIN PRV00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV037











3,532 Moved to R&C PRV039-0001
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV039 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,533 Moved to R&C PRV039-0004
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV039 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,534 No logic changes PRV040-0001 RULE-2829 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV040 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LOCATION-AND-CONTACT-INFO PRV00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV040











3,535 Logic updated: other PRV040-0004 RULE-2830 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV040 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-LOCATION-AND-CONTACT-INFO PRV00003 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV040 SUBMITTING-STATE PRV007









3,536 No logic changes PRV041-0001 RULE-6616 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV041 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV041











3,537 No logic changes PRV041-0002 RULE-2832 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV041 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



Field RECORD-NUMBER should be unique across all records of type PROV-LOCATION-AND-CONTACT-INFO RECORD-NUMBER PRV041











3,538 Retired: required value checks PRV042-0001
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV042 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,539 Merged PRV042-0002 RULE-2834 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV042 SUBMITTING-STATE-PROV-ID 2 SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] must = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] on any record in the file and SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] must = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] on the same record in the file 2217 Edit that PROV-LOCATION-AND-CONTACT-INFO child record has a PROV-ATTRIBUTES-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-LOCATION-AND-CONTACT-INFO PRV00003

record PROV-LOCATION-AND-CONTACT-INFO has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV040,PRV042



3,540 Logic updated: string matching PRV043-0001 RULE-2835 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV043 PROV-LOCATION-ID 1 PROV-LOCATION-ID not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID PRV043











3,541 Retired: required value checks PRV043-0002
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV043 PROV-LOCATION-ID 1 PROV-LOCATION-ID = 0 113 Required data element has not been reported.

























3,542 Merged PRV044-0001 RULE-2837 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV044 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE 1 If PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be a valid date of the form CCYYMMDD PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE PRV044











3,543 Merged PRV044-0002 RULE-2837 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV044 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be a valid date of the form CCYYMMDD PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE PRV044











3,544 Retired: required value checks PRV044-0003
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV044 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE 1 If PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE = 0 113 Required data element has not been reported.

























3,545 Merged PRV044-0005 RULE-2840 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV044 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE 2 Value for PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE must be <= PROV-LOCATION-AND-CONTACT-INFO-END-DATE 2111 Relational edit between PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE and PROV-LOCATION-AND-CONTACT-INFO-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE) && fns.hasValue(@val.PROV-LOCATION-AND-CONTACT-INFO-END-DATE), then fns.isLessThanOrEqual(@val.PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE, @val.PROV-LOCATION-AND-CONTACT-INFO-END-DATE)' PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE,PROV-LOCATION-AND-CONTACT-INFO-END-DATE PRV044,PRV045











3,546 No logic changes PRV044-0007 RULE-2841 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV044 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE 2 If two or more PROV-LOCATION-AND-CONTACT-INFO record segments have the same SUBMITTING-STATE, RECORD-NUMBER, SUBMITTING-STATE-PROV-ID, PROV-LOCATION-ID, and ADDR-TYPE
then for each pair of record segments,
(Segment 1 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE must <> Segment 2 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE)
AND
( (If Segment 1 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE < Segment 2 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE,
then
Segment 1 PROV-LOCATION-AND-CONTACT-INFO-END-DATE must be < Segment 2 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE)
OR
(If Segment 2 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE < Segment 1 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE,
then
Segment 2 PROV-LOCATION-AND-CONTACT-INFO-END-DATE must be < Segment 1 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE) )		 2175 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-LOCATION-AND-CONTACT-INFO failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-LOCATION-AND-CONTACT-INFO PRV00003



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE. End date field: PROV-LOCATION-AND-CONTACT-INFO-END-DATE PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE,PROV-LOCATION-AND-CONTACT-INFO-END-DATE PRV044,PRV045











3,547 Retired: Other reasons PRV044-0009
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV044 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE 2 If two or more PROV-LOCATION-AND-CONTACT-INFO record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, PROV-LOCATION-ID, and RECORD-NUMBER and these record segments are sorted in ascending order by PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N PROV-LOCATION-AND-CONTACT-INFO-END-DATE must = Segment (N+1) PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE minus 1 day 2457 Edit for contiguous PROV-LOCATION-AND-CONTACT-INFO record segments failed (Exact match on all key fields except the file segment effective date)

























3,548 Merged PRV044-0010 RULE-2834 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV044 PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE 2 ( PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2529 Relational edit between PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE, PROV-ATTRIBUTES-EFF-DATE, and PROV-ATTRIBUTES-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-LOCATION-AND-CONTACT-INFO PRV00003

record PROV-LOCATION-AND-CONTACT-INFO has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV040,PRV042



3,549 Merged PRV045-0001 RULE-2844 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV045 PROV-LOCATION-AND-CONTACT-INFO-END-DATE 1 If PROV-LOCATION-AND-CONTACT-INFO-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be a valid date of the form CCYYMMDD PROV-LOCATION-AND-CONTACT-INFO-END-DATE PRV045











3,550 Merged PRV045-0002 RULE-2844 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV045 PROV-LOCATION-AND-CONTACT-INFO-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be a valid date of the form CCYYMMDD PROV-LOCATION-AND-CONTACT-INFO-END-DATE PRV045











3,551 Merged PRV045-0006 RULE-2840 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV045 PROV-LOCATION-AND-CONTACT-INFO-END-DATE 2-M
2111
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE) && fns.hasValue(@val.PROV-LOCATION-AND-CONTACT-INFO-END-DATE), then fns.isLessThanOrEqual(@val.PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE, @val.PROV-LOCATION-AND-CONTACT-INFO-END-DATE)' PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE,PROV-LOCATION-AND-CONTACT-INFO-END-DATE PRV044,PRV045











3,552 Merged PRV045-0009 RULE-2834 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV045 PROV-LOCATION-AND-CONTACT-INFO-END-DATE 2 ( PROV-LOCATION-AND-CONTACT-INFO-END-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-LOCATION-AND-CONTACT-INFO-END-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2530 Relational edit between PROV-LOCATION-AND-CONTACT-INFO-END-DATE, PROV-ATTRIBUTES-END-DATE, and PROV-ATTRIBUTES-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-LOCATION-AND-CONTACT-INFO PRV00003

record PROV-LOCATION-AND-CONTACT-INFO has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV040,PRV042



3,553 No logic changes PRV046-0001 RULE-2848 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV046 ADDR-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LOCATION-AND-CONTACT-INFO PRV00003



If the field is populated, the value must be contained in the set of valid values with id: PROV-ADDR-TYPE PROV-ADDR-TYPE PRV046











3,554 Logic updated: string matching PRV048-0001 RULE-2849 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV048 ADDR-LN2 1 If ADDR-LN2 is populated, it must contains valid characters. 120 Field contains invalid characters - ADDR-LN2 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.ADDR-LN2), then fns.matches(@val.ADDR-LN2, "^[^|*]*$")' ADDR-LN2 PRV048











3,555 Merged PRV048-0005 RULE-7137 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV048 ADDR-LN2 2 If ADDR-LN2 is not 8-filled then ADDR-LN2 must <> ADDR-LN1 2230 Relational edit between ADDR-LN2 and ADDR-LN1
failed (duplicate value entered)		 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



The values of the following fields should be unique (non-repeating) within each record: ADDR-LN1,ADDR-LN2,ADDR-LN3 ADDR-LN1,ADDR-LN2,ADDR-LN3 PRV047,PRV048,PRV049











3,556 Logic updated: string matching PRV049-0001 RULE-2851 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV049 ADDR-LN3 1 If ADDR-LN3 is populated, it must contains valid characters. 120 Field contains invalid characters - ADDR-LN3 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.ADDR-LN3), then fns.matches(@val.ADDR-LN3, "^[^|*]*$")' ADDR-LN3 PRV049











3,557 Merged PRV049-0002 RULE-7137 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV049 ADDR-LN3 2 (If ADDR-LN3 is not 8-filled,
then ADDR-LN3 must <> ADDR-LN1)
AND
(If ADDR-LN2 is not 8-filled),
then ADDR-LN3 must <> ADDR-LN2)		 2232 Relational edit between ADDR-LN3 and ADDR-LN2 or ADDR-LN1 failed (duplicate value entered) 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



The values of the following fields should be unique (non-repeating) within each record: ADDR-LN1,ADDR-LN2,ADDR-LN3 ADDR-LN1,ADDR-LN2,ADDR-LN3 PRV047,PRV048,PRV049











3,558 No logic changes PRV049-0006 RULE-2853 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV049 ADDR-LN3 2 If ADDR-LN2 is 8-filled, then ADDR-LN3 must be 8-filled 2231 Relational edit between ADDR-LN2 and ADDR-LN3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if !fns.hasValue(@val.ADDR-LN2), then !fns.hasValue(@val.ADDR-LN3)' ADDR-LN2,ADDR-LN3 PRV048,PRV049











3,559 Retired: required value checks PRV050-0001
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV050 ADDR-CITY 1 If ADDR-CITY = spaces 113 Required data element has not been reported.

























3,560 Logic updated: string matching PRV050-0002 RULE-2855 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV050 ADDR-CITY 1 If ADDR-CITY is populated, it must contains valid characters. 120 Field contains invalid characters - ADDR-CITY 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.ADDR-CITY), then fns.matches(@val.ADDR-CITY, "^[^|*]*$")' ADDR-CITY PRV050











3,561 No logic changes PRV051-0002 RULE-2856 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV051 ADDR-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LOCATION-AND-CONTACT-INFO PRV00003



If the field is populated, the value must be contained in the set of valid values with id: STATE ADDR-STATE PRV051











3,562 No logic changes PRV052-0001 RULE-2857 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV052 ADDR-ZIP-CODE 1 If ADDR-ZIP-CODE not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.ADDR-ZIP-CODE), then fns.matches(@val.ADDR-ZIP-CODE, "^[0-9]{5}|[0-9]{9}$")' ADDR-ZIP-CODE PRV052











3,563 No logic changes PRV053-0003 RULE-2858 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV053 ADDR-TELEPHONE 1 If ADDR-TELEPHONE not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003



Value must be compatible with specified T-MSIS picture format: X(10) ADDR-TELEPHONE PRV053











3,564 No logic changes PRV054-0001 RULE-2859 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV054 ADDR-EMAIL 1 If ADDR-EMAIL does not contain @ 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.ADDR-EMAIL), then fns.matches(@val.ADDR-EMAIL, "^.*@.*$")' ADDR-EMAIL PRV054











3,565 No logic changes PRV055-0001 RULE-7151 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV055 ADDR-FAX-NUM 1 ADDR-FAX-NUM must not contain parentheses, dashes, periods, commas, spaces 120 Field contains invalid characters - ADDR-FAX-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.ADDR-FAX-NUM), then fns.isNumericString(@val.ADDR-FAX-NUM)' ADDR-FAX-NUM PRV055











3,566 No logic changes PRV056-0001 RULE-2861 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV056 ADDR-BORDER-STATE-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LOCATION-AND-CONTACT-INFO PRV00003



If the field is populated, the value must be contained in the set of valid values with id: ADDR-BORDER-STATE-IND ADDR-BORDER-STATE-IND PRV056











3,567 Retired: required value checks PRV056-0002
PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV056 ADDR-BORDER-STATE-IND 1 If ADDR-BORDER-STATE-IND = spaces 113 Required data element has not been reported.

























3,568 Merged PRV057-0001 RULE-2863 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV057 ADDR-COUNTY 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LOCATION-AND-CONTACT-INFO PRV00003



If the field is populated, the value must be contained in the set of valid values with id: COUNTY ADDR-COUNTY PRV057











3,569 Merged PRV057-0003 RULE-2863 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV057 ADDR-COUNTY 1 If ADDR-COUNTY not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LOCATION-AND-CONTACT-INFO PRV00003



If the field is populated, the value must be contained in the set of valid values with id: COUNTY ADDR-COUNTY PRV057











3,570 Logic updated: string matching PRV058-0001 RULE-2865 PROVIDER PROV-LOCATION-AND-CONTACT-INFO-PRV00003 PRV058 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LOCATION-AND-CONTACT-INFO PRV00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV058











3,571 Moved to R&C PRV060-0001
PROVIDER PROV-LICENSING-INFO-PRV00004 PRV060 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,572 Moved to R&C PRV060-0004
PROVIDER PROV-LICENSING-INFO-PRV00004 PRV060 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,573 No logic changes PRV061-0001 RULE-2868 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV061 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LICENSING-INFO PRV00004



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV061











3,574 Logic updated: other PRV061-0004 RULE-2869 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV061 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-LICENSING-INFO PRV00004 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV061 SUBMITTING-STATE PRV007









3,575 No logic changes PRV062-0001 RULE-7023 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV062 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV062











3,576 No logic changes PRV062-0003 RULE-2871 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV062 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-LICENSING-INFO PRV00004



Field RECORD-NUMBER should be unique across all records of type PROV-LICENSING-INFO RECORD-NUMBER PRV062











3,577 Retired: required value checks PRV063-0001
PROVIDER PROV-LICENSING-INFO-PRV00004 PRV063 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,578 Merged PRV063-0002 RULE-2873 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV063 SUBMITTING-STATE-PROV-ID 2 PROV-LOCATION-ID [PROV-LICENSING-INFO-PRV00004] must = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] on any record in the file and
SUBMITTING-STATE-PROV-ID [PROV-LICENSING-INFO-PRV00004] must = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE [PROV-LICENSING-INFO-PRV00004] must = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] on the same record in the file		 2216 Edit that PROV-LICENSING-INFO child record has a PROV-LOCATION-AND-CONTACT-INFO parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-LICENSING-INFO PRV00004

record PROV-LICENSING-INFO has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





PROV-LOCATION-ID,SUBMITTING-STATE-PROV-ID,SUBMITTING-STATE PRV043,PRV042,PRV040 PROV-LOCATION-ID,SUBMITTING-STATE-PROV-ID,SUBMITTING-STATE PRV064,PRV063,PRV061



3,579 Logic updated: string matching PRV064-0001 RULE-2874 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV064 PROV-LOCATION-ID 1 PROV-LOCATION-ID not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID PRV064











3,580 Merged PRV065-0001 RULE-2875 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV065 PROV-LICENSE-EFF-DATE 1 If PROV-LICENSE-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be a valid date of the form CCYYMMDD PROV-LICENSE-EFF-DATE PRV065











3,581 Merged PRV065-0002 RULE-2875 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV065 PROV-LICENSE-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be a valid date of the form CCYYMMDD PROV-LICENSE-EFF-DATE PRV065











3,582 Merged PRV065-0005 RULE-2877 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV065 PROV-LICENSE-EFF-DATE 2 PROV-LICENSE-EFF-DATE must be <= PROV-LICENSE-END-DATE 2110 Relational edit between PROV-LICENSE-EFF-DATE and PROV-LICENSE-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.PROV-LICENSE-EFF-DATE) && fns.hasValue(@val.PROV-LICENSE-END-DATE), then fns.isLessThanOrEqual(@val.PROV-LICENSE-EFF-DATE, @val.PROV-LICENSE-END-DATE)' PROV-LICENSE-EFF-DATE,PROV-LICENSE-END-DATE PRV065,PRV066











3,583 No logic changes PRV065-0007 RULE-2878 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV065 PROV-LICENSE-EFF-DATE 2 If two or more PROV-LICENSING-INFO record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, PROV-LOCATION-ID, LICENSE-TYPE, and LICENSE-ISSUING-ENTITY-ID
then for each pair of record segments,
(Segment 1 PROV-LICENSE-EFF-DATE must <> Segment 2 PROV-LICENSE-EFF-DATE)
AND
( (If Segment 1 PROV-LICENSE-EFF-DATE < Segment 2 PROV-LICENSE-EFF-DATE,
then
Segment 1 PROV-LICENSE-END-DATE must be < Segment 2 PROV-LICENSE-EFF-DATE)
OR
(If Segment 2 PROV-LICENSE-EFF-DATE < Segment 1 PROV-LICENSE-EFF-DATE,
then
Segment 2 PROV-LICENSE-END-DATE must be < Segment 1 PROV-LICENSE-EFF-DATE) )		 2174 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-LICENSING-INFO failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-LICENSING-INFO PRV00004



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-LICENSE-EFF-DATE. End date field: PROV-LICENSE-END-DATE PROV-LICENSE-EFF-DATE,PROV-LICENSE-END-DATE PRV065,PRV066











3,584 Merged PRV065-0009 RULE-2873 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV065 PROV-LICENSE-EFF-DATE 2 ( PROV-LICENSE-EFF-DATE must be >= PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-LICENSING-INFO-PRV00004] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] ) AND
( PROV-LICENSE-EFF-DATE must be <= PROV-LOCATION-AND-CONTACT-INFO-END-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-LICENSING-INFO-PRV00004] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] )		 2527 Relational edit between PROV-LICENSE-EFF-DATE, PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE, and PROV-LOCATION-AND-CONTACT-INFO-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-LICENSING-INFO PRV00004

record PROV-LICENSING-INFO has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





PROV-LOCATION-ID,SUBMITTING-STATE-PROV-ID,SUBMITTING-STATE PRV043,PRV042,PRV040 PROV-LOCATION-ID,SUBMITTING-STATE-PROV-ID,SUBMITTING-STATE PRV064,PRV063,PRV061



3,585 Merged PRV066-0001 RULE-2880 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV066 PROV-LICENSE-END-DATE 1 If PROV-LICENSE-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be a valid date of the form CCYYMMDD PROV-LICENSE-END-DATE PRV066











3,586 Merged PRV066-0002 RULE-2880 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV066 PROV-LICENSE-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-LICENSING-INFO PRV00004



Value must be a valid date of the form CCYYMMDD PROV-LICENSE-END-DATE PRV066











3,587 Merged PRV066-0005 RULE-2877 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV066 PROV-LICENSE-END-DATE 2-M
2110
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.PROV-LICENSE-EFF-DATE) && fns.hasValue(@val.PROV-LICENSE-END-DATE), then fns.isLessThanOrEqual(@val.PROV-LICENSE-EFF-DATE, @val.PROV-LICENSE-END-DATE)' PROV-LICENSE-EFF-DATE,PROV-LICENSE-END-DATE PRV065,PRV066











3,588 Merged PRV066-0007 RULE-2873 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV066 PROV-LICENSE-END-DATE 2 ( PROV-LICENSE-END-DATE must be <= PROV-LOCATION-AND-CONTACT-INFO-END-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-LICENSING-INFO-PRV00004] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] ) AND
( PROV-LICENSE-END-DATE must be >= PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-LICENSING-INFO-PRV00004] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-LICENSING-INFO-PRV00004] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] )		 2528 Relational edit between PROV-LICENSE-END-DATE, PROV-LOCATION-AND-CONTACT-INFO-END-DATE, and PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-LICENSING-INFO PRV00004

record PROV-LICENSING-INFO has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





PROV-LOCATION-ID,SUBMITTING-STATE-PROV-ID,SUBMITTING-STATE PRV043,PRV042,PRV040 PROV-LOCATION-ID,SUBMITTING-STATE-PROV-ID,SUBMITTING-STATE PRV064,PRV063,PRV061



3,589 No logic changes PRV067-0001 RULE-2884 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV067 LICENSE-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-LICENSING-INFO PRV00004



If the field is populated, the value must be contained in the set of valid values with id: LICENSE-TYPE LICENSE-TYPE PRV067











3,590 Logic updated: string matching PRV068-0001 RULE-2885 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV068 LICENSE-ISSUING-ENTITY-ID 1 If LICENSE-ISSUING-ENTITY-ID is populated, it must contains valid characters. 120 Field contains invalid characters - LICENSE-ISSUING-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.LICENSE-ISSUING-ENTITY-ID), then fns.matches(@val.LICENSE-ISSUING-ENTITY-ID, "^[^|*]*$")' LICENSE-ISSUING-ENTITY-ID PRV068











3,591 No logic changes PRV068-0003 RULE-2886 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV068 LICENSE-ISSUING-ENTITY-ID 2 If LICENSE-OR-ACCREDITATION-NUMBER is not 8-filled then LICENSE-ISSUING-ENTITY-ID must not be 8-filled 2308 Relational edit between LICENSE-ISSUING-ENTITY-ID and LICENSE-OR-ACCREDITATION-NUMBER failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.LICENSE-OR-ACCREDITATION-NUMBER), then fns.hasValue(@val.LICENSE-ISSUING-ENTITY-ID)' LICENSE-OR-ACCREDITATION-NUMBER,LICENSE-ISSUING-ENTITY-ID PRV069,PRV068











3,592 No logic changes PRV068-0008 RULE-2887 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV068 LICENSE-ISSUING-ENTITY-ID 2 If LICENSE-TYPE = "2" then LICENSE-ISSUING-ENTITY-ID must = "DEA" 2053 Relational edit between LICENSE-ISSUING-ENTITY-ID and LICENSE-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.isEqual(@val.LICENSE-TYPE, "2"), then fns.isEqual(@val.LICENSE-ISSUING-ENTITY-ID, "DEA")' LICENSE-TYPE,LICENSE-ISSUING-ENTITY-ID PRV067,PRV068











3,593 No logic changes PRV069-0001 RULE-2888 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV069 LICENSE-OR-ACCREDITATION-NUMBER 2 If LICENSE-TYPE is not 8-filled, then LICENSE-OR-ACCREDITATION-NUMBER must not be 8-filled 2309 Relational edit between LICENSE-OR-ACCREDITATION-NUMBER and LICENSE-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.LICENSE-TYPE), then fns.hasValue(@val.LICENSE-OR-ACCREDITATION-NUMBER)' LICENSE-TYPE,LICENSE-OR-ACCREDITATION-NUMBER PRV067,PRV069











3,594 Logic updated: string matching PRV069-0002 RULE-2889 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV069 LICENSE-OR-ACCREDITATION-NUMBER 1 If LICENSE-OR-ACCREDITATION-NUMBER is populated, it must contains valid characters. 120 Field contains invalid characters - LICENSE-OR-ACCREDITATION-NUMBER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.LICENSE-OR-ACCREDITATION-NUMBER), then fns.matches(@val.LICENSE-OR-ACCREDITATION-NUMBER, "^[^|*]*$")' LICENSE-OR-ACCREDITATION-NUMBER PRV069











3,595 Logic updated: string matching PRV070-0001 RULE-2890 PROVIDER PROV-LICENSING-INFO-PRV00004 PRV070 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-LICENSING-INFO PRV00004



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV070











3,596 Moved to R&C PRV072-0001
PROVIDER PROV-IDENTIFIERS-PRV00005 PRV072 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,597 Moved to R&C PRV072-0004
PROVIDER PROV-IDENTIFIERS-PRV00005 PRV072 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,598 No logic changes PRV073-0001 RULE-2893 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV073 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-IDENTIFIERS PRV00005



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV073











3,599 Logic updated: other PRV073-0004 RULE-2894 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV073 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-IDENTIFIERS PRV00005 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV073 SUBMITTING-STATE PRV007









3,600 No logic changes PRV074-0001 RULE-7007 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV074 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV074











3,601 No logic changes PRV074-0003 RULE-2896 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV074 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-IDENTIFIERS PRV00005



Field RECORD-NUMBER should be unique across all records of type PROV-IDENTIFIERS RECORD-NUMBER PRV074











3,602 Retired: required value checks PRV075-0001
PROVIDER PROV-IDENTIFIERS-PRV00005 PRV075 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,603 Merged PRV075-0002 RULE-2898 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV075 SUBMITTING-STATE-PROV-ID 2 PROV-LOCATION-ID [PROV-IDENTIFIERS-PRV00005] must = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] on any record in the file and SUBMITTING-STATE-PROV-ID [PROV-IDENTIFIERS-PRV00005] must = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] must = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] on the same record in the file 2215 Edit that PROV-IDENTIFIERS child record has a PROV-LOCATION-AND-CONTACT-INFO parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-IDENTIFIERS PRV00005

record PROV-IDENTIFIERS has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV040,PRV042,PRV043 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV073,PRV075,PRV076



3,604 Logic updated: string matching PRV076-0001 RULE-2899 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV076 PROV-LOCATION-ID 1 PROV-LOCATION-ID not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID PRV076











3,605 No logic changes PRV077-0001 RULE-2900 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV077 PROV-IDENTIFIER-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-IDENTIFIERS PRV00005



If the field is populated, the value must be contained in the set of valid values with id: PROV-IDENTIFIER-TYPE PROV-IDENTIFIER-TYPE PRV077











3,606 No logic changes PRV077-0002 RULE-2901 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV077 PROV-IDENTIFIER-TYPE 2 If PROVIDER-IDENTIFIER is not 8-filled, then PROV-IDENTIFIER-TYPE must not be 8-filled 2396 Relational edit between PROV-IDENTIFIER-TYPE and PROVIDER-IDENTIFIER failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.PROV-IDENTIFIER), then fns.hasValue(@val.PROV-IDENTIFIER-TYPE)' PROV-IDENTIFIER,PROV-IDENTIFIER-TYPE PRV081,PRV077











3,607 Logic updated: string matching PRV078-0001 RULE-2902 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV078 PROV-IDENTIFIER-ISSUING-ENTITY-ID 1 If PROV-IDENTIFIER-ISSUING-ENTITY-ID is populated, it must contains valid characters. 120 Field contains invalid characters - PROV-IDENTIFIER-ISSUING-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.PROV-IDENTIFIER-ISSUING-ENTITY-ID), then fns.matches(@val.PROV-IDENTIFIER-ISSUING-ENTITY-ID, "^[^|*]*$")' PROV-IDENTIFIER-ISSUING-ENTITY-ID PRV078











3,608 No logic changes PRV078-0003 RULE-2903 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV078 PROV-IDENTIFIER-ISSUING-ENTITY-ID 2 PROV-IDENTIFIER-ISSUING-ENTITY-ID must contain SUBMITTING STATE [PROV-IDENTIFIERS-PRV00005] when PROV-IDENTIFIER-TYPE = "1" 2395 Relational edit between PROV-IDENTIFIER-ISSUING-ENTITY-ID and PROV-IDENTIFIER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.isEqual(@val.PROV-IDENTIFIER-TYPE, "1"), then fns.isEqual(@val.PROV-IDENTIFIER-ISSUING-ENTITY-ID, @val.SUBMITTING-STATE)' PROV-IDENTIFIER-TYPE,PROV-IDENTIFIER-ISSUING-ENTITY-ID,SUBMITTING-STATE PRV077,PRV078,PRV073











3,609 No logic changes PRV078-0004 RULE-2904 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV078 PROV-IDENTIFIER-ISSUING-ENTITY-ID 2 PROV-IDENTIFIER-ISSUING-ENTITY-ID must = "NPI" when PROV-IDENTIFIER-TYPE = "2" 2395 Relational edit between PROV-IDENTIFIER-ISSUING-ENTITY-ID and PROV-IDENTIFIER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.isEqual(@val.PROV-IDENTIFIER-TYPE, "2"), then fns.isEqual(@val.PROV-IDENTIFIER-ISSUING-ENTITY-ID, "NPI")' PROV-IDENTIFIER-TYPE,PROV-IDENTIFIER-ISSUING-ENTITY-ID PRV077,PRV078











3,610 No logic changes PRV078-0005 RULE-2905 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV078 PROV-IDENTIFIER-ISSUING-ENTITY-ID 2 PROV-IDENTIFIER-ISSUING-ENTITY-ID must = "CMS" when PROV-IDENTIFIER-TYPE = "3" 2395 Relational edit between PROV-IDENTIFIER-ISSUING-ENTITY-ID and PROV-IDENTIFIER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.isEqual(@val.PROV-IDENTIFIER-TYPE, "3"), then fns.isEqual(@val.PROV-IDENTIFIER-ISSUING-ENTITY-ID, "CMS")' PROV-IDENTIFIER-TYPE,PROV-IDENTIFIER-ISSUING-ENTITY-ID PRV077,PRV078











3,611 No logic changes PRV078-0006 RULE-2906 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV078 PROV-IDENTIFIER-ISSUING-ENTITY-ID 2 PROV-IDENTIFIER-ISSUING-ENTITY-ID must = "NCPDP" when PROV-IDENTIFIER-TYPE = "4" 2395 Relational edit between PROV-IDENTIFIER-ISSUING-ENTITY-ID and PROV-IDENTIFIER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.isEqual(@val.PROV-IDENTIFIER-TYPE, "4"), then fns.isEqual(@val.PROV-IDENTIFIER-ISSUING-ENTITY-ID, "NCPDP")' PROV-IDENTIFIER-TYPE,PROV-IDENTIFIER-ISSUING-ENTITY-ID PRV077,PRV078











3,612 No logic changes PRV078-0007 RULE-2907 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV078 PROV-IDENTIFIER-ISSUING-ENTITY-ID 2 PROV-IDENTIFIER-ISSUING-ENTITY-ID must = "IRS" when PROV-IDENTIFIER-TYPE = "5" 2395 Relational edit between PROV-IDENTIFIER-ISSUING-ENTITY-ID and PROV-IDENTIFIER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.isEqual(@val.PROV-IDENTIFIER-TYPE, "5"), then fns.isEqual(@val.PROV-IDENTIFIER-ISSUING-ENTITY-ID, "IRS")' PROV-IDENTIFIER-TYPE,PROV-IDENTIFIER-ISSUING-ENTITY-ID PRV077,PRV078











3,613 Merged PRV079-0001 RULE-2908 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV079 PROV-IDENTIFIER-EFF-DATE 1 If PROV-IDENTIFIER-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be a valid date of the form CCYYMMDD PROV-IDENTIFIER-EFF-DATE PRV079











3,614 Merged PRV079-0002 RULE-2908 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV079 PROV-IDENTIFIER-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be a valid date of the form CCYYMMDD PROV-IDENTIFIER-EFF-DATE PRV079











3,615 Merged PRV079-0006 RULE-2910 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV079 PROV-IDENTIFIER-EFF-DATE 2 PROV-IDENTIFIER-EFF-DATE must be <= PROV-IDENTIFIER-END-DATE 2109 Relational edit between PROV-IDENTIFIER-EFF-DATE and PROV-IDENTIFIER-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.PROV-IDENTIFIER-EFF-DATE) && fns.hasValue(@val.PROV-IDENTIFIER-END-DATE), then fns.isLessThanOrEqual(@val.PROV-IDENTIFIER-EFF-DATE, @val.PROV-IDENTIFIER-END-DATE)' PROV-IDENTIFIER-EFF-DATE,PROV-IDENTIFIER-END-DATE PRV079,PRV080











3,616 No logic changes PRV079-0007 RULE-2911 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV079 PROV-IDENTIFIER-EFF-DATE 2 If two or more PROV-LICENSING-INFO record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, PROV-LOCATION-ID, PROV-IDENTIFIER-TYPE, PROV-IDENTIFIER-ISSUING-ENTITY-ID, and PROV-IDENTIFIER
then for each pair of record segments,
(Segment 1 PROV-IDENTIFIER-EFF-DATE must <> Segment 2 PROV-IDENTIFIER-EFF-DATE)
AND
( (If Segment 1 PROV-IDENTIFIER-EFF-DATE < Segment 2 PROV-IDENTIFIER-EFF-DATE,
then
Segment 1 PROV-IDENTIFIER-END-DATE must be < Segment 2 PROV-IDENTIFIER-EFF-DATE)
OR
(If Segment 2 PROV-IDENTIFIER-EFF-DATE < Segment 1 PROV-IDENTIFIER-EFF-DATE,
then
Segment 2 PROV-IDENTIFIER-END-DATE must be < Segment 1 PROV-IDENTIFIER-EFF-DATE) )		 2173 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-IDENTIFIERS failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-IDENTIFIERS PRV00005



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-IDENTIFIER-EFF-DATE. End date field: PROV-IDENTIFIER-END-DATE PROV-IDENTIFIER-EFF-DATE,PROV-IDENTIFIER-END-DATE PRV079,PRV080











3,617 Merged PRV079-0009 RULE-2898 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV079 PROV-IDENTIFIER-EFF-DATE 2 ( PROV-IDENTIFIER-EFF-DATE must be >= PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-IDENTIFIERS-PRV00005] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] ) AND
( PROV-IDENTIFIER-EFF-DATE must be <= PROV-LOCATION-AND-CONTACT-INFO-END-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-IDENTIFIERS-PRV00005] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] )		 2525 Relational edit between PROV-IDENTIFIER-EFF-DATE, PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE, and PROV-LOCATION-AND-CONTACT-INFO-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-IDENTIFIERS PRV00005

record PROV-IDENTIFIERS has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV040,PRV042,PRV043 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV073,PRV075,PRV076



3,618 Merged PRV080-0001 RULE-2913 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV080 PROV-IDENTIFIER-END-DATE 1 If PROV-IDENTIFIER-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be a valid date of the form CCYYMMDD PROV-IDENTIFIER-END-DATE PRV080











3,619 Merged PRV080-0002 RULE-2913 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV080 PROV-IDENTIFIER-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-IDENTIFIERS PRV00005



Value must be a valid date of the form CCYYMMDD PROV-IDENTIFIER-END-DATE PRV080











3,620 Merged PRV080-0006 RULE-2910 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV080 PROV-IDENTIFIER-END-DATE 2-M
2109
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.PROV-IDENTIFIER-EFF-DATE) && fns.hasValue(@val.PROV-IDENTIFIER-END-DATE), then fns.isLessThanOrEqual(@val.PROV-IDENTIFIER-EFF-DATE, @val.PROV-IDENTIFIER-END-DATE)' PROV-IDENTIFIER-EFF-DATE,PROV-IDENTIFIER-END-DATE PRV079,PRV080











3,621 Merged PRV080-0008 RULE-2898 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV080 PROV-IDENTIFIER-END-DATE 2 ( PROV-IDENTIFIER-END-DATE must be <= PROV-LOCATION-AND-CONTACT-INFO-END-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-IDENTIFIERS-PRV00005] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] ) AND
( PROV-IDENTIFIER-END-DATE must be >= PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-IDENTIFIERS-PRV00005] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-IDENTIFIERS-PRV00005] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] )		 2526 Relational edit between PROV-IDENTIFIER-END-DATE, PROV-LOCATION-AND-CONTACT-INFO-END-DATE, and PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-IDENTIFIERS PRV00005

record PROV-IDENTIFIERS has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV040,PRV042,PRV043 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV073,PRV075,PRV076



3,622 Logic updated: string matching PRV081-0001 RULE-2917 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV081 PROV-IDENTIFIER 1 IF PROV-IDENTIFER is populated, it must contains valid characters. 120 Field contains invalid characters -PROV-IDENTIFER 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.PROV-IDENTIFIER), then fns.matches(@val.PROV-IDENTIFIER, "^[^|*]*$")' PROV-IDENTIFIER PRV081











3,623 No logic changes PRV081-0005 RULE-2918 PROVIDER PROV-IDENTIFIERS-PRV00005 PRV081 PROV-IDENTIFIER 2 If PROV-IDENTIFIER-TYPE is not 8-filled, then PROV-IDENTIFIER must not be 8-filled 2393 Relational edit between PROV-IDENTIFIER and PROV-IDENTIFIER-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-IDENTIFIERS PRV00005



'if fns.hasValue(@val.PROV-IDENTIFIER-TYPE), then fns.hasValue(@val.PROV-IDENTIFIER)' PROV-IDENTIFIER-TYPE,PROV-IDENTIFIER PRV077,PRV081











3,624 Moved to R&C PRV084-0001
PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV084 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,625 Moved to R&C PRV084-0004
PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV084 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,626 No logic changes PRV085-0001 RULE-2921 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV085 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-TAXONOMY-CLASSIFICATION PRV00006



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV085











3,627 Logic updated: other PRV085-0004 RULE-2922 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV085 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-TAXONOMY-CLASSIFICATION PRV00006 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV085 SUBMITTING-STATE PRV007









3,628 No logic changes PRV086-0001 RULE-6167 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV086 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV086











3,629 No logic changes PRV086-0003 RULE-2924 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV086 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-TAXONOMY-CLASSIFICATION PRV00006



Field RECORD-NUMBER should be unique across all records of type PROV-TAXONOMY-CLASSIFICATION RECORD-NUMBER PRV086











3,630 Retired: required value checks PRV087-0001
PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV087 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,631 Merged PRV087-0002 RULE-2926 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV087 SUBMITTING-STATE-PROV-ID 2 SUBMITTING-STATE-PROV-ID [PROV-TAXONOMY-CLASSIFICATION-PRV00006] must = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] on any record in the file and SUBMITTING-STATE [PROV-TAXONOMY-CLASSIFICATION-PRV00006] must = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] on the same record in the file 2219 Edit that PROV-TAXONOMY-CLASSIFICATION child record has a PROV-ATTRIBUTES-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-TAXONOMY-CLASSIFICATION PRV00006

record PROV-TAXONOMY-CLASSIFICATION has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV085,PRV087



3,632 No logic changes PRV088-0001 RULE-2927 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV088 PROV-CLASSIFICATION-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-TAXONOMY-CLASSIFICATION PRV00006



If the field is populated, the value must be contained in the set of valid values with id: PROV-CLASSIFICATION-TYPE PROV-CLASSIFICATION-TYPE PRV088











3,633 No logic changes PRV089-0001 RULE-2928 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV089 PROV-CLASSIFICATION-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set One Record Type (Single Record) PROV-TAXONOMY-CLASSIFICATION PRV00006



'if fns.hasValue(@val.PROV-CLASSIFICATION-TYPE) && fns.hasValue(@val.PROV-CLASSIFICATION-CODE), then fns.isValidProviderClassificationCode(@val.PROV-TAXONOMY-CLASSIFICATION-EFF-DATE, @val.PROV-CLASSIFICATION-TYPE, @val.PROV-CLASSIFICATION-CODE)' PROV-CLASSIFICATION-TYPE,PROV-CLASSIFICATION-CODE,PROV-TAXONOMY-CLASSIFICATION-EFF-DATE PRV088,PRV089,PRV090











3,634 Merged PRV090-0001 RULE-2929 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV090 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE 1 If PROV-IDENTIFIER-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be a valid date of the form CCYYMMDD PROV-TAXONOMY-CLASSIFICATION-EFF-DATE PRV090











3,635 Merged PRV090-0002 RULE-2929 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV090 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be a valid date of the form CCYYMMDD PROV-TAXONOMY-CLASSIFICATION-EFF-DATE PRV090











3,636 Merged PRV090-0006 RULE-2931 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV090 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE 2 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE must be <= PROV-TAXONOMY-CLASSIFICATION-END-DATE 2113 Relational edit between PROV-TAXONOMY-CLASSIFICATION-EFF-DATE and PROV-TAXONOMY-CLASSIFICATION-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-TAXONOMY-CLASSIFICATION PRV00006



'if fns.hasValue(@val.PROV-TAXONOMY-CLASSIFICATION-EFF-DATE) && fns.hasValue(@val.PROV-TAXONOMY-CLASSIFICATION-END-DATE), then fns.isLessThanOrEqual(@val.PROV-TAXONOMY-CLASSIFICATION-EFF-DATE, @val.PROV-TAXONOMY-CLASSIFICATION-END-DATE)' PROV-TAXONOMY-CLASSIFICATION-EFF-DATE,PROV-TAXONOMY-CLASSIFICATION-END-DATE PRV090,PRV091











3,637 No logic changes PRV090-0007 RULE-2932 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV090 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE 2 If two or more PROV-TAXONOMY-CLASSIFICATION record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, PROV-CLASSIFICATION-TYPE, and PROV-CLASSIFICATION-CODE
then for each pair of record segments,
(Segment 1 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE must <> Segment 2 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE)
AND
( (If Segment 1 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE < Segment 2 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE,
then
Segment 1 PROV-TAXONOMY-CLASSIFICATION-END-DATE must be < Segment 2 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE)
OR
(If Segment 2 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE < Segment 1 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE,
then
Segment 2 PROV-TAXONOMY-CLASSIFICATION-END-DATE must be < Segment 1 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE) )		 2177 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-TAXONOMY-CLASSIFICATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-TAXONOMY-CLASSIFICATION PRV00006



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-TAXONOMY-CLASSIFICATION-EFF-DATE. End date field: PROV-TAXONOMY-CLASSIFICATION-END-DATE PROV-TAXONOMY-CLASSIFICATION-EFF-DATE,PROV-TAXONOMY-CLASSIFICATION-END-DATE PRV090,PRV091











3,638 Merged PRV090-0009 RULE-2926 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV090 PROV-TAXONOMY-CLASSIFICATION-EFF-DATE 2 ( PROV-TAXONOMY-CLASSIFICATION-EFF-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-TAXONOMY-CLASSIFICATION-EFF-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2533 Relational edit between PROV-TAXONOMY-CLASSIFICATION-EFF-DATE, PROV-ATTRIBUTES-EFF-DATE, and PROV-ATTRIBUTES-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-TAXONOMY-CLASSIFICATION PRV00006

record PROV-TAXONOMY-CLASSIFICATION has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV085,PRV087



3,639 Merged PRV091-0001 RULE-2934 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV091 PROV-TAXONOMY-CLASSIFICATION-END-DATE 1 If PROV-IDENTIFIER-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be a valid date of the form CCYYMMDD PROV-TAXONOMY-CLASSIFICATION-END-DATE PRV091











3,640 Merged PRV091-0002 RULE-2934 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV091 PROV-TAXONOMY-CLASSIFICATION-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-TAXONOMY-CLASSIFICATION PRV00006



Value must be a valid date of the form CCYYMMDD PROV-TAXONOMY-CLASSIFICATION-END-DATE PRV091











3,641 Merged PRV091-0006 RULE-2931 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV091 PROV-TAXONOMY-CLASSIFICATION-END-DATE 2-M
2113
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-TAXONOMY-CLASSIFICATION PRV00006



'if fns.hasValue(@val.PROV-TAXONOMY-CLASSIFICATION-EFF-DATE) && fns.hasValue(@val.PROV-TAXONOMY-CLASSIFICATION-END-DATE), then fns.isLessThanOrEqual(@val.PROV-TAXONOMY-CLASSIFICATION-EFF-DATE, @val.PROV-TAXONOMY-CLASSIFICATION-END-DATE)' PROV-TAXONOMY-CLASSIFICATION-EFF-DATE,PROV-TAXONOMY-CLASSIFICATION-END-DATE PRV090,PRV091











3,642 Merged PRV091-0008 RULE-2926 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV091 PROV-TAXONOMY-CLASSIFICATION-END-DATE 2 ( PROV-TAXONOMY-CLASSIFICATION-END-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-TAXONOMY-CLASSIFICATION-END-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-TAXONOMY-CLASSIFICATION-PRV00006] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2534 Relational edit between PROV-TAXONOMY-CLASSIFICATION-END-DATE, PROV-ATTRIBUTES-END-DATE, and PROV-ATTRIBUTES-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-TAXONOMY-CLASSIFICATION PRV00006

record PROV-TAXONOMY-CLASSIFICATION has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV085,PRV087



3,643 Logic updated: string matching PRV092-0001 RULE-2938 PROVIDER PROV-TAXONOMY-CLASSIFICATION-PRV00006 PRV092 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-TAXONOMY-CLASSIFICATION PRV00006



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV092











3,644 Moved to R&C PRV094-0001
PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV094 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,645 Moved to R&C PRV094-0004
PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV094 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,646 No logic changes PRV095-0001 RULE-2941 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV095 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-MEDICAID-ENROLLMENT PRV00007



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV095











3,647 Logic updated: other PRV095-0004 RULE-2942 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV095 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-MEDICAID-ENROLLMENT PRV00007 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV095 SUBMITTING-STATE PRV007









3,648 No logic changes PRV096-0001 RULE-6930 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV096 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV096











3,649 No logic changes PRV096-0003 RULE-2944 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV096 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-MEDICAID-ENROLLMENT PRV00007



Field RECORD-NUMBER should be unique across all records of type PROV-MEDICAID-ENROLLMENT RECORD-NUMBER PRV096











3,650 Retired: required value checks PRV097-0001
PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV097 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,651 Merged PRV097-0002 RULE-2946 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV097 SUBMITTING-STATE-PROV-ID 2 SUBMITTING-STATE-PROV-ID [PROV-MEDICAID-ENROLLMENT-PRV00007] must = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] on any record in the file and SUBMITTING-STATE [PROV-MEDICAID-ENROLLMENT-PRV00007] must = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] on the same record in the file 2218 Edit that PROV-MEDICAID-ENROLLMENT child record has a PROV-ATTRIBUTES-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-MEDICAID-ENROLLMENT PRV00007

record PROV-MEDICAID-ENROLLMENT has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV095,PRV097



3,652 Merged PRV098-0001 RULE-2947 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV098 PROV-MEDICAID-EFF-DATE 1 If PROV-MEDICAID-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be a valid date of the form CCYYMMDD PROV-MEDICAID-EFF-DATE PRV098











3,653 Merged PRV098-0002 RULE-2947 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV098 PROV-MEDICAID-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be a valid date of the form CCYYMMDD PROV-MEDICAID-EFF-DATE PRV098











3,654 Merged PRV098-0005 RULE-2949 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV098 PROV-MEDICAID-EFF-DATE 2 PROV-MEDICAID-EFF-DATE must be <= PROV-MEDICAID-END-DATE 2112 Relational edit between PROV-MEDICAID-EFF-DATE and PROV-MEDICAID-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-MEDICAID-ENROLLMENT PRV00007



'if fns.hasValue(@val.PROV-MEDICAID-EFF-DATE) && fns.hasValue(@val.PROV-MEDICAID-END-DATE), then fns.isLessThanOrEqual(@val.PROV-MEDICAID-EFF-DATE, @val.PROV-MEDICAID-END-DATE)' PROV-MEDICAID-EFF-DATE,PROV-MEDICAID-END-DATE PRV098,PRV099











3,655 No logic changes PRV098-0006 RULE-2950 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV098 PROV-MEDICAID-EFF-DATE 2 If two or more PROV-MEDICAID-ENROLLMENT record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, and PROV-MEDICAID-ENROLLMENT-STATUS-CODE
then for each pair of record segments,
(Segment 1 PROV-MEDICAID-EFF-DATE must <> Segment 2 PROV-MEDICAID-EFF-DATE)
AND
( (If Segment 1 PROV-MEDICAID-EFF-DATE < Segment 2 PROV-MEDICAID-EFF-DATE,
then
Segment 1 PROV-MEDICAID-END-DATE must be < Segment 2 PROV-MEDICAID-EFF-DATE)
OR
(If Segment 2 PROV-MEDICAID-EFF-DATE < Segment 1 PROV-MEDICAID-EFF-DATE,
then
Segment 2 PROV-MEDICAID-END-DATE must be < Segment 1 PROV-MEDICAID-EFF-DATE) )		 2176 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-MEDICAID-ENROLLMENT failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-MEDICAID-ENROLLMENT PRV00007



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-MEDICAID-EFF-DATE. End date field: PROV-MEDICAID-END-DATE PROV-MEDICAID-EFF-DATE,PROV-MEDICAID-END-DATE PRV098,PRV099











3,656 Merged PRV098-0008 RULE-2946 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV098 PROV-MEDICAID-EFF-DATE 2 ( PROV-MEDICAID-EFF-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-MEDICAID-EFF-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2531 Relational edit between PROV-MEDICAID-EFF-DATE, PROV-ATTRIBUTES-EFF-DATE, and PROV-ATTRIBUTES-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-MEDICAID-ENROLLMENT PRV00007

record PROV-MEDICAID-ENROLLMENT has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV095,PRV097



3,657 Merged PRV099-0001 RULE-2952 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV099 PROV-MEDICAID-END-DATE 1 If PROV-MEDICAID-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be a valid date of the form CCYYMMDD PROV-MEDICAID-END-DATE PRV099











3,658 Merged PRV099-0002 RULE-2952 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV099 PROV-MEDICAID-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be a valid date of the form CCYYMMDD PROV-MEDICAID-END-DATE PRV099











3,659 Merged PRV099-0005 RULE-2949 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV099 PROV-MEDICAID-END-DATE 2-M
2112
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-MEDICAID-ENROLLMENT PRV00007



'if fns.hasValue(@val.PROV-MEDICAID-EFF-DATE) && fns.hasValue(@val.PROV-MEDICAID-END-DATE), then fns.isLessThanOrEqual(@val.PROV-MEDICAID-EFF-DATE, @val.PROV-MEDICAID-END-DATE)' PROV-MEDICAID-EFF-DATE,PROV-MEDICAID-END-DATE PRV098,PRV099











3,660 Merged PRV099-0007 RULE-2946 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV099 PROV-MEDICAID-END-DATE 2 ( PROV-MEDICAID-END-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-MEDICAID-END-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-MEDICAID-ENROLLMENT-PRV00007] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2532 Relational edit between PROV-MEDICAID-END-DATE, PROV-ATTRIBUTES-END-DATE, and PROV-ATTRIBUTES-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-MEDICAID-ENROLLMENT PRV00007

record PROV-MEDICAID-ENROLLMENT has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV095,PRV097



3,661 No logic changes PRV100-0001 RULE-2956 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV100 PROV-MEDICAID-ENROLLMENT-STATUS-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-MEDICAID-ENROLLMENT PRV00007



If the field is populated, the value must be contained in the set of valid values with id: PROV-MEDICAID-ENROLLMENT-STATUS-CODE PROV-MEDICAID-ENROLLMENT-STATUS-CODE PRV100











3,662 No logic changes PRV101-0001 RULE-2957 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV101 STATE-PLAN-ENROLLMENT 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-MEDICAID-ENROLLMENT PRV00007



If the field is populated, the value must be contained in the set of valid values with id: STATE-PLAN-ENROLLMENT STATE-PLAN-ENROLLMENT PRV101











3,663 No logic changes PRV102-0001 RULE-2958 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV102 PROV-ENROLLMENT-METHOD 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-MEDICAID-ENROLLMENT PRV00007



If the field is populated, the value must be contained in the set of valid values with id: PROV-ENROLLMENT-METHOD PROV-ENROLLMENT-METHOD PRV102











3,664 Merged PRV103-0001 RULE-2959 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV103 APPL-DATE 1 If APPL-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be a valid date of the form CCYYMMDD APPL-DATE PRV103











3,665 Merged PRV103-0002 RULE-2959 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV103 APPL-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-MEDICAID-ENROLLMENT PRV00007



Value must be a valid date of the form CCYYMMDD APPL-DATE PRV103











3,666 Logic updated: string matching PRV104-0001 RULE-2961 PROVIDER PROV-MEDICAID-ENROLLMENT-PRV00007 PRV104 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-MEDICAID-ENROLLMENT PRV00007



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV104











3,667 Moved to R&C PRV106-0001
PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV106 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,668 Moved to R&C PRV106-0004
PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV106 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,669 No logic changes PRV107-0001 RULE-2964 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV107 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-AFFILIATED-GROUPS PRV00008



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV107











3,670 Logic updated: other PRV107-0004 RULE-2965 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV107 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-AFFILIATED-GROUPS PRV00008 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV107 SUBMITTING-STATE PRV007









3,671 No logic changes PRV108-0002 RULE-6131 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV108 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV108











3,672 No logic changes PRV108-0003 RULE-2967 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV108 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-AFFILIATED-GROUPS PRV00008



Field RECORD-NUMBER should be unique across all records of type PROV-AFFILIATED-GROUPS RECORD-NUMBER PRV108











3,673 Retired: required value checks PRV109-0001
PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV109 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,674 Merged PRV109-0002 RULE-2969 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV109 SUBMITTING-STATE-PROV-ID 2 SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-GROUPS-PRV00008] must = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] on any record in the file and SUBMITTING-STATE [PROV-AFFILIATED-GROUPS-PRV00008] must = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] on the same record in the file 2212 Edit that PROV-AFFILIATED-GROUPS child record has a PROV-ATTRIBUTES-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-AFFILIATED-GROUPS PRV00008

record PROV-AFFILIATED-GROUPS has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV107,PRV109



3,675 Retired: required value checks PRV110-0001
PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV110 SUBMITTING-STATE-PROV-ID-OF-AFFILIATED-ENTITY 1 If SUBMITTING-STATE-PROV-ID-OF-AFFILIATED-ENTITY = spaces 113 Required data element has not been reported.

























3,676 Merged PRV111-0001 RULE-2971 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV111 PROV-AFFILIATED-GROUP-EFF-DATE 1 If PROV-AFFILIATED-GROUP-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-GROUP-EFF-DATE PRV111











3,677 Merged PRV111-0002 RULE-2971 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV111 PROV-AFFILIATED-GROUP-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-GROUP-EFF-DATE PRV111











3,678 Merged PRV111-0006 RULE-2973 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV111 PROV-AFFILIATED-GROUP-EFF-DATE 2 PROV-AFFILIATED-GROUP-EFF-DATE must be <= PROV-AFFILIATED-GROUP-END-DATE 2106 Relational edit between PROV-AFFILIATED-GROUP-EFF-DATE and PROV-AFFILIATED-GROUP-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-AFFILIATED-GROUPS PRV00008



'if fns.hasValue(@val.PROV-AFFILIATED-GROUP-EFF-DATE) && fns.hasValue(@val.PROV-AFFILIATED-GROUP-END-DATE), then fns.isLessThanOrEqual(@val.PROV-AFFILIATED-GROUP-EFF-DATE, @val.PROV-AFFILIATED-GROUP-END-DATE)' PROV-AFFILIATED-GROUP-EFF-DATE,PROV-AFFILIATED-GROUP-END-DATE PRV111,PRV112











3,679 No logic changes PRV111-0007 RULE-2974 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV111 PROV-AFFILIATED-GROUP-EFF-DATE 2 If two or more PROV-AFFILIATED-GROUPS record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, and SUBMITTING-STATE-PROV-ID-OF-AFFILIATED-ENTITY
then for each pair of record segments,
(Segment 1 PROV-AFFILIATED-GROUP-EFF-DATE must <> Segment 2 PROV-AFFILIATED-GROUP-EFF-DATE)
AND
( (If Segment 1 PROV-AFFILIATED-GROUP-EFF-DATE < Segment 2 PROV-AFFILIATED-GROUP-EFF-DATE,
then
Segment 1 PROV-AFFILIATED-GROUP-END-DATE must be < Segment 2 PROV-AFFILIATED-GROUP-EFF-DATE)
OR
(If Segment 2 PROV-AFFILIATED-GROUP-EFF-DATE < Segment 1 PROV-AFFILIATED-GROUP-EFF-DATE,
then
Segment 2 PROV-AFFILIATED-GROUP-END-DATE must be < Segment 1 PROV-AFFILIATED-GROUP-EFF-DATE) )		 2169 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-AFFILIATED-GROUPS failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-AFFILIATED-GROUPS PRV00008



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-AFFILIATED-GROUP-EFF-DATE. End date field: PROV-AFFILIATED-GROUP-END-DATE PROV-AFFILIATED-GROUP-EFF-DATE,PROV-AFFILIATED-GROUP-END-DATE PRV111,PRV112











3,680 Merged PRV111-0009 RULE-2969 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV111 PROV-AFFILIATED-GROUP-EFF-DATE 2 ( PROV-AFFILIATED-GROUP-EFF-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-AFFILIATED-GROUP-EFF-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2521 Relational edit between PROV-AFFILIATED-GROUP-EFF-DATE, PROV-ATTRIBUTES-EFF-DATE, and PROV-ATTRIBUTES-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-AFFILIATED-GROUPS PRV00008

record PROV-AFFILIATED-GROUPS has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV107,PRV109



3,681 Merged PRV112-0001 RULE-2976 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV112 PROV-AFFILIATED-GROUP-END-DATE 1 If PROV-AFFILIATED-GROUP-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-GROUP-END-DATE PRV112











3,682 Merged PRV112-0002 RULE-2976 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV112 PROV-AFFILIATED-GROUP-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-GROUPS PRV00008



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-GROUP-END-DATE PRV112











3,683 Merged PRV112-0006 RULE-2973 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV112 PROV-AFFILIATED-GROUP-END-DATE 2-M
2106
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-AFFILIATED-GROUPS PRV00008



'if fns.hasValue(@val.PROV-AFFILIATED-GROUP-EFF-DATE) && fns.hasValue(@val.PROV-AFFILIATED-GROUP-END-DATE), then fns.isLessThanOrEqual(@val.PROV-AFFILIATED-GROUP-EFF-DATE, @val.PROV-AFFILIATED-GROUP-END-DATE)' PROV-AFFILIATED-GROUP-EFF-DATE,PROV-AFFILIATED-GROUP-END-DATE PRV111,PRV112











3,684 Merged PRV112-0008 RULE-2969 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV112 PROV-AFFILIATED-GROUP-END-DATE 2 ( PROV-AFFILIATED-GROUP-END-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-AFFILIATED-GROUP-END-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-GROUPS-PRV00008] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2522 Relational edit between PROV-AFFILIATED-GROUP-END-DATE, PROV-ATTRIBUTES-END-DATE, and PROV-ATTRIBUTES-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-AFFILIATED-GROUPS PRV00008

record PROV-AFFILIATED-GROUPS has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV107,PRV109



3,685 Logic updated: string matching PRV113-0001 RULE-2980 PROVIDER PROV-AFFILIATED-GROUPS-PRV00008 PRV113 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-AFFILIATED-GROUPS PRV00008



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV113











3,686 Moved to R&C PRV115-0001
PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV115 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,687 Moved to R&C PRV115-0004
PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV115 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,688 No logic changes PRV116-0001 RULE-2983 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV116 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-AFFILIATED-PROGRAMS PRV00009



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV116











3,689 Logic updated: other PRV116-0004 RULE-2984 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV116 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-AFFILIATED-PROGRAMS PRV00009 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV116 SUBMITTING-STATE PRV007









3,690 No logic changes PRV117-0001 RULE-6308 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV117 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV117











3,691 No logic changes PRV117-0003 RULE-2986 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV117 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-AFFILIATED-PROGRAMS PRV00009



Field RECORD-NUMBER should be unique across all records of type PROV-AFFILIATED-PROGRAMS RECORD-NUMBER PRV117











3,692 Retired: required value checks PRV118-0001
PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV118 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,693 Merged PRV118-0002 RULE-2988 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV118 SUBMITTING-STATE-PROV-ID 2 SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-PROGRAMS-PRV00009] must = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] on any record in the file and SUBMITTING-STATE [PROV-AFFILIATED-PROGRAMS-PRV00009] must = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] on the same record in the file 2213 Edit that PROV-AFFILIATED-PROGRAMS child record has a PROV-ATTRIBUTES-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-AFFILIATED-PROGRAMS PRV00009

record PROV-AFFILIATED-PROGRAMS has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV116,PRV118



3,694 No logic changes PRV119-0001 RULE-2989 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV119 AFFILIATED-PROGRAM-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-AFFILIATED-PROGRAMS PRV00009



If the field is populated, the value must be contained in the set of valid values with id: AFFILIATED-PROGRAM-TYPE AFFILIATED-PROGRAM-TYPE PRV119











3,695 Logic updated: other PRV119-0003 RULE-2990 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV119 AFFILIATED-PROGRAM-ID 3 If AFFILIATED-PROGRAM-TYPE = "2", then AFFILIATED-PROGRAM-ID must = any STATE-PLAN-ID [MANAGED-CARE-MAIN-MCR00002] where SUBMITTING-STATE [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE [MANAGED-CARE-MAIN-MCR00002] 3061 A MNGDCARE record for the AFFILIATED-PROGRAM-ID is missing 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) MANAGED-CARE-MAIN MCR00002 PROV-AFFILIATED-PROGRAMS PRV00009

For every record of type PROV-AFFILIATED-PROGRAMS, if fns.isEqual(@secondaryRecord.AFFILIATED-PROGRAM-TYPE, "2"), there must be a valid record of type MANAGED-CARE-MAIN that matches on the join keys

AFFILIATED-PROGRAM-TYPE PRV119

SUBMITTING-STATE,STATE-PLAN-ID-NUM MCR017,MCR019 SUBMITTING-STATE,AFFILIATED-PROGRAM-ID PRV116,PRV120



3,696 No logic changes PRV120-0001 RULE-2991 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV120 AFFILIATED-PROGRAM-ID 2 AFFILIATED-PROGRAM-ID must not be 8-filled when AFFILIATED-PROGRAM-TYPE is not 8-filled 2235 Relational edit between AFFILIATED-PROGRAM-ID and AFFILIATED-PROGRAM-TYPE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-AFFILIATED-PROGRAMS PRV00009



'if fns.hasValue(@val.AFFILIATED-PROGRAM-TYPE), then fns.hasValue(@val.AFFILIATED-PROGRAM-ID)' AFFILIATED-PROGRAM-TYPE,AFFILIATED-PROGRAM-ID PRV119,PRV120











3,697 Logic updated: string matching PRV120-0002 RULE-2992 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV120 AFFILIATED-PROGRAM-ID 1 If AFFILIATED-PROGRAM-ID is populated, it must contains valid characters. 120 Field contains invalid characters - AFFILIATED-PROGRAM-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-AFFILIATED-PROGRAMS PRV00009



'if fns.hasValue(@val.AFFILIATED-PROGRAM-ID), then fns.matches(@val.AFFILIATED-PROGRAM-ID, "^[^|*]*$")' AFFILIATED-PROGRAM-ID PRV120











3,698 Merged PRV121-0001 RULE-2993 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV121 PROV-AFFILIATED-PROGRAM-EFF-DATE 1 If PROV-AFFILIATED-PROGRAM-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-PROGRAM-EFF-DATE PRV121











3,699 Merged PRV121-0002 RULE-2993 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV121 PROV-AFFILIATED-PROGRAM-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-PROGRAM-EFF-DATE PRV121











3,700 Merged PRV121-0006 RULE-2995 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV121 PROV-AFFILIATED-PROGRAM-EFF-DATE 2 PROV-AFFILIATED-PROGRAM-EFF-DATE must be <= PROV-AFFILIATED-PROGRAM-END-DATE 2107 Relational edit between PROV-AFFILIATED-PROGRAM-EFF-DATE and PROV-AFFILIATED-PROGRAM-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-AFFILIATED-PROGRAMS PRV00009



'if fns.hasValue(@val.PROV-AFFILIATED-PROGRAM-EFF-DATE) && fns.hasValue(@val.PROV-AFFILIATED-PROGRAM-END-DATE), then fns.isLessThanOrEqual(@val.PROV-AFFILIATED-PROGRAM-EFF-DATE, @val.PROV-AFFILIATED-PROGRAM-END-DATE)' PROV-AFFILIATED-PROGRAM-EFF-DATE,PROV-AFFILIATED-PROGRAM-END-DATE PRV121,PRV122











3,701 No logic changes PRV121-0007 RULE-2996 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV121 PROV-AFFILIATED-PROGRAM-EFF-DATE 2 If two or more PROV-AFFILIATED-PROGRAMS record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, AFFILIATED-PROGRAM-TYPE, and AFFILIATED-PROGRAM-ID
then for each pair of record segments,
(Segment 1 PROV-AFFILIATED-PROGRAM-EFF-DATE must <> Segment 2 PROV-AFFILIATED-PROGRAM-EFF-DATE)
AND
( (If Segment 1 PROV-AFFILIATED-PROGRAM-EFF-DATE < Segment 2 PROV-AFFILIATED-PROGRAM-EFF-DATE,
then
Segment 1 PROV-AFFILIATED-PROGRAM-END-DATE must be < Segment 2 PROV-AFFILIATED-PROGRAM-EFF-DATE)
OR
(If Segment 2 PROV-AFFILIATED-PROGRAM-EFF-DATE < Segment 1 PROV-AFFILIATED-PROGRAM-EFF-DATE,
then
Segment 2 PROV-AFFILIATED-PROGRAM-END-DATE must be < Segment 1 PROV-AFFILIATED-PROGRAM-EFF-DATE) )		 2170 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-AFFILIATED-PROGRAMS failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-AFFILIATED-PROGRAMS PRV00009



Records with the same primary keys must have non-overlapping date ranges. Effective date field: PROV-AFFILIATED-PROGRAM-EFF-DATE. End date field: PROV-AFFILIATED-PROGRAM-END-DATE PROV-AFFILIATED-PROGRAM-EFF-DATE,PROV-AFFILIATED-PROGRAM-END-DATE PRV121,PRV122











3,702 Merged PRV121-0009 RULE-2988 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV121 PROV-AFFILIATED-PROGRAM-EFF-DATE 2 ( PROV-AFFILIATED-PROGRAM-EFF-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-AFFILIATED-PROGRAM-EFF-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2523 Relational edit between PROV-AFFILIATED-PROGRAM-EFF-DATE, PROV-ATTRIBUTES-EFF-DATE, and PROV-ATTRIBUTES-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-AFFILIATED-PROGRAMS PRV00009

record PROV-AFFILIATED-PROGRAMS has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV116,PRV118



3,703 Merged PRV122-0001 RULE-2998 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV122 PROV-AFFILIATED-PROGRAM-END-DATE 1 If PROV-AFFILIATED-PROGRAM-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-PROGRAM-END-DATE PRV122











3,704 Merged PRV122-0002 RULE-2998 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV122 PROV-AFFILIATED-PROGRAM-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-AFFILIATED-PROGRAMS PRV00009



Value must be a valid date of the form CCYYMMDD PROV-AFFILIATED-PROGRAM-END-DATE PRV122











3,705 Merged PRV122-0006 RULE-2995 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV122 PROV-AFFILIATED-PROGRAM-END-DATE 2-M
2107
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-AFFILIATED-PROGRAMS PRV00009



'if fns.hasValue(@val.PROV-AFFILIATED-PROGRAM-EFF-DATE) && fns.hasValue(@val.PROV-AFFILIATED-PROGRAM-END-DATE), then fns.isLessThanOrEqual(@val.PROV-AFFILIATED-PROGRAM-EFF-DATE, @val.PROV-AFFILIATED-PROGRAM-END-DATE)' PROV-AFFILIATED-PROGRAM-EFF-DATE,PROV-AFFILIATED-PROGRAM-END-DATE PRV121,PRV122











3,706 Merged PRV122-0008 RULE-2988 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV122 PROV-AFFILIATED-PROGRAM-END-DATE 2 ( PROV-AFFILIATED-PROGRAM-END-DATE must be <= PROV-ATTRIBUTES-END-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] ) AND
( PROV-AFFILIATED-PROGRAM-END-DATE must be >= PROV-ATTRIBUTES-EFF-DATE on any PROV-ATTRIBUTES-MAIN segment
where SUBMITTING-STATE [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE [PROV-ATTRIBUTES-MAIN-PRV00002] and SUBMITTING-STATE-PROV-ID [PROV-AFFILIATED-PROGRAMS-PRV00009] = SUBMITTING-STATE-PROV-ID [PROV-ATTRIBUTES-MAIN-PRV00002] )		 2524 Relational edit between PROV-AFFILIATED-PROGRAM-END-DATE, PROV-ATTRIBUTES-END-DATE, and PROV-ATTRIBUTES-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-ATTRIBUTES-MAIN PRV00002 PROV-AFFILIATED-PROGRAMS PRV00009

record PROV-AFFILIATED-PROGRAMS has corresponding parent record PROV-ATTRIBUTES-MAIN





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV017,PRV019 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID PRV116,PRV118



3,707 Logic updated: string matching PRV123-0001 RULE-3002 PROVIDER PROV-AFFILIATED-PROGRAMS-PRV00009 PRV123 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-AFFILIATED-PROGRAMS PRV00009



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV123











3,708 Moved to R&C PRV125-0001
PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV125 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,709 Moved to R&C PRV125-0004
PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV125 RECORD-ID 2 If FILE-NAME = "PROVIDER", then the first 3 positions of RECORD-ID must = "PRV" 150 Invalid or missing RECORD-ID

























3,710 No logic changes PRV126-0001 RULE-3005 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV126 SUBMITTING-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-BED-TYPE-INFO PRV00010



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE PRV126











3,711 Logic updated: other PRV126-0004 RULE-3006 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV126 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-PROVIDER-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) PROV-BED-TYPE-INFO PRV00010 FILE-HEADER-RECORD-PROVIDER PRV00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE PRV126 SUBMITTING-STATE PRV007









3,712 No logic changes PRV127-0001 RULE-7091 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV127 RECORD-NUMBER 1 If RECORD-NUMBER is not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: 9(11) RECORD-NUMBER PRV127











3,713 No logic changes PRV127-0003 RULE-3008 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV127 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) PROV-BED-TYPE-INFO PRV00010



Field RECORD-NUMBER should be unique across all records of type PROV-BED-TYPE-INFO RECORD-NUMBER PRV127











3,714 Retired: required value checks PRV128-0001
PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV128 SUBMITTING-STATE-PROV-ID 1 If SUBMITTING-STATE-PROV-ID = spaces 113 Required data element has not been reported.

























3,715 Merged PRV128-0002 RULE-3010 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV128 SUBMITTING-STATE-PROV-ID 2 PROV-LOCATION-ID [PROV-BED-TYPE-INFO-PRV00010] must = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] on any record in the file and SUBMITTING-STATE-PROV-ID [PROV-BED-TYPE-INFO-PRV00010] must = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE [PROV-BED-TYPE-INFO-PRV00010] must = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] on the same record in the file 2214 Edit that PROV-BED-TYPE-INFO child record has a PROV-LOCATION-AND-CONTACT-INFO parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-BED-TYPE-INFO PRV00010

record PROV-BED-TYPE-INFO has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV040,PRV042,PRV043 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV126,PRV128,PRV129



3,716 Logic updated: string matching PRV129-0001 RULE-3011 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV129 PROV-LOCATION-ID 1 PROV-LOCATION-ID not numeric 109 Non-Numeric Value Provided 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-BED-TYPE-INFO PRV00010



'if fns.hasValue(@val.PROV-LOCATION-ID), then fns.matches(@val.PROV-LOCATION-ID, "^[^|*]*$")' PROV-LOCATION-ID PRV129











3,717 Retired: required value checks PRV129-0002
PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV129 PROV-LOCATION-ID 1 PROV-LOCATION-ID = 0 113 Required data element has not been reported.

























3,718 Merged PRV130-0001 RULE-3013 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV130 BED-TYPE-EFF-DATE 1 If BED-TYPE-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be a valid date of the form CCYYMMDD BED-TYPE-EFF-DATE PRV130











3,719 Merged PRV130-0002 RULE-3013 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV130 BED-TYPE-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be a valid date of the form CCYYMMDD BED-TYPE-EFF-DATE PRV130











3,720 Merged PRV130-0004 RULE-3015 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV130 BED-TYPE-EFF-DATE 2 BED-TYPE-EFF-DATE must be <= BED-TYPE-END-DATE 2236 Relational edit between BED-TYPE-EFF-DATE and BED-TYPE-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-BED-TYPE-INFO PRV00010



'if fns.hasValue(@val.BED-TYPE-EFF-DATE) && fns.hasValue(@val.BED-TYPE-END-DATE), then fns.isLessThanOrEqual(@val.BED-TYPE-EFF-DATE, @val.BED-TYPE-END-DATE)' BED-TYPE-EFF-DATE,BED-TYPE-END-DATE PRV130,PRV131











3,721 No logic changes PRV130-0007 RULE-3016 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV130 BED-TYPE-EFF-DATE 2 If two or more PROV-BED-TYPE-INFO record segments have the same SUBMITTING-STATE, SUBMITTING-STATE-PROV-ID, PROV-LOCATION-ID, and BED-TYPE-CODE
then for each pair of record segments,
(Segment 1 BED-TYPE-EFF-DATE must <> Segment 2 BED-TYPE-EFF-DATE)
AND
( (If Segment 1 BED-TYPE-EFF-DATE < Segment 2 BED-TYPE-EFF-DATE,
then
Segment 1 BED-TYPE-END-DATE must be < Segment 2 BED-TYPE-EFF-DATE)
OR
(If Segment 2 BED-TYPE-EFF-DATE < Segment 1 BED-TYPE-EFF-DATE,
then
Segment 2 BED-TYPE-END-DATE must be < Segment 1 BED-TYPE-EFF-DATE) )		 2172 Edit for overlapping coverage dates in record segments that have non-unique key fields in PROV-BED-TYPE-INFO failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) PROV-BED-TYPE-INFO PRV00010



Records with the same primary keys must have non-overlapping date ranges. Effective date field: BED-TYPE-EFF-DATE. End date field: BED-TYPE-END-DATE BED-TYPE-EFF-DATE,BED-TYPE-END-DATE PRV130,PRV131











3,722 Merged PRV130-0009 RULE-3010 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV130 BED-TYPE-EFF-DATE 2 ( BED-TYPE-EFF-DATE must be >= PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-BED-TYPE-INFO-PRV00010] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] ) AND
( BED-TYPE-EFF-DATE must be <= PROV-LOCATION-AND-CONTACT-INFO-END-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-BED-TYPE-INFO-PRV00010] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] )		 2464 Relational edit between BED-TYPE-EFF-DATE, PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE, and PROV-LOCATION-AND-CONTACT-INFO-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-BED-TYPE-INFO PRV00010

record PROV-BED-TYPE-INFO has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV040,PRV042,PRV043 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV126,PRV128,PRV129



3,723 Merged PRV131-0001 RULE-3018 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV131 BED-TYPE-END-DATE 1 If BED-TYPE-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be a valid date of the form CCYYMMDD BED-TYPE-END-DATE PRV131











3,724 Merged PRV131-0002 RULE-3018 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV131 BED-TYPE-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be a valid date of the form CCYYMMDD BED-TYPE-END-DATE PRV131











3,725 Merged PRV131-0004 RULE-3015 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV131 BED-TYPE-END-DATE 2-M
2236
2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) PROV-BED-TYPE-INFO PRV00010



'if fns.hasValue(@val.BED-TYPE-EFF-DATE) && fns.hasValue(@val.BED-TYPE-END-DATE), then fns.isLessThanOrEqual(@val.BED-TYPE-EFF-DATE, @val.BED-TYPE-END-DATE)' BED-TYPE-EFF-DATE,BED-TYPE-END-DATE PRV130,PRV131











3,726 Merged PRV131-0007 RULE-3010 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV131 BED-TYPE-END-DATE 2 ( BED-TYPE-END-DATE must be <= PROV-LOCATION-AND-CONTACT-INFO-END-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-BED-TYPE-INFO-PRV00010] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] ) AND
( BED-TYPE-END-DATE must be >= PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE on any PROV-LOCATION-AND-CONTACT-INFO segment
where SUBMITTING-STATE [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and SUBMITTING-STATE-PROV-ID [PROV-BED-TYPE-INFO-PRV00010] = SUBMITTING-STATE-PROV-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] and PROV-LOCATION-ID [PROV-BED-TYPE-INFO-PRV00010] = PROV-LOCATION-ID [PROV-LOCATION-AND-CONTACT-INFO-PRV00003] )		 2465 Relational edit between BED-TYPE-END-DATE, PROV-LOCATION-AND-CONTACT-INFO-END-DATE, and PROV-LOCATION-AND-CONTACT-INFO-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule PROV-LOCATION-AND-CONTACT-INFO PRV00003 PROV-BED-TYPE-INFO PRV00010

record PROV-BED-TYPE-INFO has corresponding parent record PROV-LOCATION-AND-CONTACT-INFO





SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV040,PRV042,PRV043 SUBMITTING-STATE,SUBMITTING-STATE-PROV-ID,PROV-LOCATION-ID PRV126,PRV128,PRV129



3,727 No logic changes PRV134-0001 RULE-3022 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV134 BED-TYPE-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value PROV-BED-TYPE-INFO PRV00010



If the field is populated, the value must be contained in the set of valid values with id: BED-TYPE-CODE BED-TYPE-CODE PRV134











3,728 No logic changes PRV135-0001 RULE-3023 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV135 BED-COUNT 1 If BED-COUNT not numeric 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule PROV-BED-TYPE-INFO PRV00010



Value must be compatible with specified T-MSIS picture format: 9(5) BED-COUNT PRV135











3,729 Logic updated: string matching PRV136-0001 RULE-3024 PROVIDER PROV-BED-TYPE-INFO-PRV00010 PRV136 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) PROV-BED-TYPE-INFO PRV00010



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION PRV136











3,730 No logic changes PRV138-0002 RULE-6985 PROVIDER FILE-HEADER-RECORD-PROVIDER-PRV00001 PRV138 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-PROVIDER PRV00001



Value must be compatible with specified T-MSIS picture format: X(4) SEQUENCE-NUMBER PRV138











3,731 Retired: Other reasons TPL001-0001
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL001 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,732 Moved to R&C TPL001-0004
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL001 RECORD-ID 2 If FILE-NAME = "TPL-FILE", then the first 3 positions of RECORD-ID must = "TPL" 150 Invalid or missing RECORD-ID

























3,733 Moved to R&C TPL003-0001
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL003 SUBMISSION-TRANSACTION-TYPE 1 Value must be in the set of valid values. 103 Value is not included in the valid code list

























3,734 Moved to R&C TPL004-0001
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL004 FILE-ENCODING-SPECIFICATION 1 Value must be in the set of valid values 103 Value is not included in the valid code list

























3,735 Moved to R&C TPL006-0002
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL006 FILE-NAME 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,736 Moved to R&C TPL007-0002
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL007 SUBMITTING-STATE 1 Value must be in the set of valid values 103 Value is not included in the valid code list

























3,737 Moved to R&C TPL007-0003
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL007 SUBMITTING-STATE 2 SUBMITTING-STATE must = State ID in the File Name Format 2141 Value is inconsistent with State ID in File Name Format

























3,738 Merged TPL008-0001 RULE-3033 TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL008 DATE-FILE-CREATED 1 If DATE-FILE-CREATED is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED TPL008











3,739 Merged TPL008-0002 RULE-3033 TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL008 DATE-FILE-CREATED 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be a valid date of the form CCYYMMDD DATE-FILE-CREATED TPL008











3,740 Moved to R&C TPL008-0003
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be >= END-OF-TIME-PERIOD 2019 Relational edit between DATE-FILE-CREATED and END-OF-TIME-PERIOD in the Header Record failed

























3,741 Moved to R&C TPL008-0005
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL008 DATE-FILE-CREATED 2 DATE-FILE-CREATED must be <= Current Date 2018 Relational edit between DATE-FILE-CREATED and Current Date failed

























3,742 No logic changes TPL009-0001 RULE-3037 TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL009 START-OF-TIME-PERIOD 1 If START-OF-TIME-PERIOD is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be a valid date of the form CCYYMMDD START-OF-TIME-PERIOD TPL009











3,743 Moved to R&C TPL009-0002
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL009 START-OF-TIME-PERIOD 1 Value in CCYY must = reporting century/year, MM must = 01 - 12 and DD must = 01 102 Value is not a valid date

























3,744 Moved to R&C TPL009-0003
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL009 START-OF-TIME-PERIOD 1 DD (in CCYYMMDD) for START-OF-TIME-PERIOD must = "01" 114 Invalid value in DD for START-OF-TIME-PERIOD

























3,745 Moved to R&C TPL009-0004
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= END-OF-TIME-PERIOD 2122 Relational edit between START-OF-TIME-PERIOD and END-OF-TIME-PERIOD failed

























3,746 Moved to R&C TPL009-0005
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL009 START-OF-TIME-PERIOD 2 START-OF-TIME-PERIOD must be <= DATE-FILE-CREATED 2120 Relational edit between START-OF-TIME-PERIOD and DATE-FILE-CREATED failed

























3,747 Merged TPL010-0001 RULE-3042 TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL010 END-OF-TIME-PERIOD 1 If END-OF-TIME-PERIOD is not in CCYYMMDD format 113 Required data element has not been reported. 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD TPL010











3,748 Merged TPL010-0002 RULE-3042 TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL010 END-OF-TIME-PERIOD 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule FILE-HEADER-RECORD-TPL TPL00001



Value must be a valid date of the form CCYYMMDD END-OF-TIME-PERIOD TPL010











3,749 Moved to R&C TPL010-0004
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL010 END-OF-TIME-PERIOD 2-M
2019


























3,750 Moved to R&C TPL010-0005
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL010 END-OF-TIME-PERIOD 2-M
2122


























3,751 Moved to R&C TPL011-0001
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL011 FILE-STATUS-INDICATOR 1 Value must be in the set of valid values 103 Value is not included in the valid code list

























3,752 Moved to R&C TPL011-0002
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL011 FILE-STATUS-INDICATOR 2 FILE-STATUS-INDICATOR must = File Status Indicator in the File Name Format 2140 Value is inconsistent with File Status Indicator in File Name Format

























3,753 Logic updated: other TPL012-0003 RULE-3048 TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL012 SSN-INDICATOR 3 Value for SSN-INDICATOR [THIRD-PARTY LIABILITY] must match SSN-INDICATOR [ELIGIBLE] 3011 Relational edit between SSN-INDICATOR [THIRD-PARTY LIABILITY] and SSN-INDICATOR [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) FILE-HEADER-RECORD-TPL TPL00001 FILE-HEADER-RECORD-ELIGIBILITY ELG00001

'if fns.hasValue(@primaryRecord.SSN-INDICATOR) && fns.hasValue(@secondaryRecord.SSN-INDICATOR), then fns.isEqual(@primaryRecord.SSN-INDICATOR, @secondaryRecord.SSN-INDICATOR)' SSN-INDICATOR TPL012 SSN-INDICATOR ELG012

SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD TPL007,TPL009,TPL010 SUBMITTING-STATE,START-OF-TIME-PERIOD,END-OF-TIME-PERIOD ELG007,ELG009,ELG010



3,754 Moved to R&C TPL013-0001
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL013 TOT-REC-CNT 1 If TOT-REC-CNT = 0 109 Non-Numeric Value Provided

























3,755 Moved to R&C TPL013-0002
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL013 TOT-REC-CNT 2 TOT-REC-CNT must = total number of all records minus the header record 2142 Value does not equal the total number of records in the file excluding the header record

























3,756 Moved to R&C TPL014-0001
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL014 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION

























3,757 Moved to R&C TPL016-0001
TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL016 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,758 Moved to R&C TPL016-0004
TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL016 RECORD-ID 2 If FILE-NAME = "TPL-FILE", then the first 3 positions of RECORD-ID must = "TPL" 150 Invalid or missing RECORD-ID

























3,759 No logic changes TPL017-0002 RULE-3054 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL017 SUBMITTING-STATE 1 Value must be in the set of valid values 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE TPL017











3,760 Logic updated: other TPL017-0003 RULE-3055 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL017 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-TPL-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 FILE-HEADER-RECORD-TPL TPL00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE TPL017 SUBMITTING-STATE TPL007









3,761 Retired: Other reasons TPL018-0001
TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL018 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























3,762 No logic changes TPL018-0003 RULE-3057 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL018 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Field RECORD-NUMBER should be unique across all records of type TPL-MEDICAID-ELIGIBLE-PERSON-MAIN RECORD-NUMBER TPL018











3,763 Retired: MSIS ID checks TPL019-0001
TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL019 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























3,764 Retired: MSIS ID checks TPL019-0002
TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL019 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























3,765 No logic changes TPL019-0003 RULE-3060 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL019 MSIS-IDENTIFICATION-NUM 3 MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] = any MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY--TPL00002] where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] 3019 A PRIMARY-DEMOGRAPHICS-ELIGIBILITY record for the MSIS-IDENTIFICATION-NUM is missing 3 Relational error E3001 Missing corresponding record (multi file) (ex. missing eligibility record for claim header) Child Parent Rule PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002

record TPL-MEDICAID-ELIGIBLE-PERSON-MAIN has corresponding parent record PRIMARY-DEMOGRAPHICS-ELIGIBILITY





MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE ELG019,ELG017 MSIS-IDENTIFICATION-NUM,SUBMITTING-STATE TPL019,TPL017



3,766 Retired: MSIS ID checks TPL019-0005
TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL019 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























3,767 No logic changes TPL020-0001 RULE-3062 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL020 TPL-HEALTH-INSURANCE-COVERAGE-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



If the field is populated, the value must be contained in the set of valid values with id: TPL-HEALTH-INSURANCE-COVERAGE-IND TPL-HEALTH-INSURANCE-COVERAGE-IND TPL020











3,768 No logic changes TPL021-0001 RULE-3063 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL021 TPL-OTHER-COVERAGE-IND 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



If the field is populated, the value must be contained in the set of valid values with id: TPL-OTHER-COVERAGE-IND TPL-OTHER-COVERAGE-IND TPL021











3,769 Logic updated: string matching TPL022-0001 RULE-3064 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL022 ELIGIBLE-FIRST-NAME 1 ELIGIBLE-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - ELIGIBLE-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



'if fns.hasValue(@val.ELIGIBLE-FIRST-NAME), then fns.matches(@val.ELIGIBLE-FIRST-NAME, "^[^|*]*$")' ELIGIBLE-FIRST-NAME TPL022











3,770 Logic updated: string matching TPL023-0001 RULE-3065 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL023 ELIGIBLE-MIDDLE-INIT 1 ELIGIBLE-MIDDLE-INIT must not contain non-alphabetic characters 120 Field contains invalid characters - ELIGIBLE-MIDDLE-INIT 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



'if fns.hasValue(@val.ELIGIBLE-MIDDLE-INIT), then fns.matches(@val.ELIGIBLE-MIDDLE-INIT, "^[^|*]*$")' ELIGIBLE-MIDDLE-INIT TPL023











3,771 Logic updated: string matching TPL024-0001 RULE-3066 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL024 ELIGIBLE-LAST-NAME 1 ELIGIBLE-LAST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - ELIGIBLE-LAST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



'if fns.hasValue(@val.ELIGIBLE-LAST-NAME), then fns.matches(@val.ELIGIBLE-LAST-NAME, "^[^|*]*$")' ELIGIBLE-LAST-NAME TPL024











3,772 Merged TPL025-0001 RULE-3067 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL025 ELIG-PRSN-MAIN-EFF-DATE 1 If ELIG-PRSN-MAIN-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be a valid date of the form CCYYMMDD ELIG-PRSN-MAIN-EFF-DATE TPL025











3,773 Merged TPL025-0003 RULE-3067 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL025 ELIG-PRSN-MAIN-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be a valid date of the form CCYYMMDD ELIG-PRSN-MAIN-EFF-DATE TPL025











3,774 Logic updated: other TPL025-0005 RULE-3069 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL025 ELIG-PRSN-MAIN-EFF-DATE 2 ELIG-PRSN-MAIN-EFF-DATE must be <= ELIG-PRSN-MAIN-END-DATE 2033 Relational edit between ELIG-PRSN-MAIN-EFF-DATE and ELIG-PRSN-MAIN-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



'if fns.hasValue(@val.ELIG-PRSN-MAIN-EFF-DATE) && fns.hasValue(@val.ELIG-PRSN-MAIN-END-DATE), then fns.isLessThanOrEqual(@val.ELIG-PRSN-MAIN-EFF-DATE, @val.ELIG-PRSN-MAIN-END-DATE)' ELIG-PRSN-MAIN-EFF-DATE,ELIG-PRSN-MAIN-END-DATE TPL025,TPL026











3,775 No logic changes TPL025-0007 RULE-3070 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL025 ELIG-PRSN-MAIN-EFF-DATE 2 If two or more TPL-MEDICAID-ELIGIBLE-PERSON-MAIN record segments have the same SUBMITTING-STATE and MSIS-IDENTIFICATION-NUM
then for each pair of record segments,
(Segment 1 ELIG-PRSN-MAIN-EFF-DATE must <> Segment 2 ELIG-PRSN-MAIN-EFF-DATE)
AND
( (If Segment 1 ELIG-PRSN-MAIN-EFF-DATE < Segment 2 ELIG-PRSN-MAIN-EFF-DATE,
then
Segment 1 ELIG-PRSN-MAIN-END-DATE must be < Segment 2 ELIG-PRSN-MAIN-EFF-DATE)
OR
(If Segment 2 ELIG-PRSN-MAIN-EFF-DATE < Segment 1 ELIG-PRSN-MAIN-EFF-DATE,
then
Segment 2 ELIG-PRSN-MAIN-END-DATE must be < Segment 1 ELIG-PRSN-MAIN-EFF-DATE) )		 2184 Edit for overlapping coverage dates in record segments that have non-unique key fields in TPL-MEDICAID-ELIGIBLE-PERSON-MAIN failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Records with the same primary keys must have non-overlapping date ranges. Effective date field: ELIG-PRSN-MAIN-EFF-DATE. End date field: ELIG-PRSN-MAIN-END-DATE ELIG-PRSN-MAIN-EFF-DATE,ELIG-PRSN-MAIN-END-DATE TPL025,TPL026











3,776 Retired: Other reasons TPL025-0009
TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL025 ELIG-PRSN-MAIN-EFF-DATE 2 If two or more TPL-MEDICAID-ELIGIBLE-PERSON-MAIN record segments have the same SUBMITTING-STATE and MSIS-IDENTIFICATION-NUM and these record segments are sorted in ascending order by ELIG-PRSN-MAIN-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N ELIG-PRSN-MAIN-END-DATE must = Segment (N+1) ELIG-PRSN-MAIN-EFF-DATE minus 1 day 2460 Edit for contiguous TPL-MEDICAID-ELIGIBLE-PERSON-MAIN record segments failed (Exact match on all key fields except the file segment effective date)

























3,777 Merged TPL026-0001 RULE-3072 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL026 ELIG-PRSN-MAIN-END-DATE 1 If ELIG-PRSN-MAIN-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be a valid date of the form CCYYMMDD ELIG-PRSN-MAIN-END-DATE TPL026











3,778 Merged TPL026-0002 RULE-3072 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL026 ELIG-PRSN-MAIN-END-DATE 1 Value can only contain numerics. 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be a valid date of the form CCYYMMDD ELIG-PRSN-MAIN-END-DATE TPL026











3,779 Merged TPL026-0003 RULE-3072 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL026 ELIG-PRSN-MAIN-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



Value must be a valid date of the form CCYYMMDD ELIG-PRSN-MAIN-END-DATE TPL026











3,780 Logic updated: string matching TPL027-0001 RULE-3075 TPL TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002 TPL027 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION TPL027











3,781 Moved to R&C TPL029-0003
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL029 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,782 Moved to R&C TPL029-0004
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL029 RECORD-ID 2 If FILE-NAME = "TPL-FILE", then the first 3 positions of RECORD-ID must = "TPL" 150 Invalid or missing RECORD-ID

























3,783 No logic changes TPL030-0002 RULE-3078 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL030 SUBMITTING-STATE 1 Value must be in the set of valid values 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE TPL030











3,784 Logic updated: other TPL030-0003 RULE-3079 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL030 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-TPL-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003 FILE-HEADER-RECORD-TPL TPL00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE TPL030 SUBMITTING-STATE TPL007









3,785 Retired: Other reasons TPL031-0001
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL031 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























3,786 No logic changes TPL031-0003 RULE-3081 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL031 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Field RECORD-NUMBER should be unique across all records of type TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO RECORD-NUMBER TPL031











3,787 Retired: MSIS ID checks TPL032-0001
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL032 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























3,788 Retired: MSIS ID checks TPL032-0002
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL032 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























3,789 Retired: MSIS ID checks TPL032-0005
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL032 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























3,790 Merged TPL032-0006 RULE-3085 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL032 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] must = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] on any record in the file and SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] must = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] on the same record in the file 2225 Edit that TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO child record has a TPL-MEDICAID-ELIGIBLE-PERSON-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003

record TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO has corresponding parent record TPL-MEDICAID-ELIGIBLE-PERSON-MAIN





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL030,TPL032



3,791 Logic updated: string matching TPL033-0001 RULE-3086 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL033 INSURANCE-CARRIER-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - INSURANCE-CARRIER-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.INSURANCE-CARRIER-ID-NUM), then fns.matches(@val.INSURANCE-CARRIER-ID-NUM, "^[^|*]*$")' INSURANCE-CARRIER-ID-NUM TPL033











3,792 Retired: Other reasons TPL033-0003
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL033 INSURANCE-CARRIER-ID-NUM 2 COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] must = COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] on any record in the file and
INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] must = INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and
INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] must = INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and
SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] must = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] on the same record in the file		 2224 Edit that TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO child record has a TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES parent record failed

























3,793 Logic updated: string matching TPL034-0002 RULE-3088 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL034 INSURANCE-PLAN-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - INSURANCE-PLAN-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.INSURANCE-PLAN-ID), then fns.matches(@val.INSURANCE-PLAN-ID, "^[^|*]*$")' INSURANCE-PLAN-ID TPL034











3,794 Logic updated: string matching TPL035-0002 RULE-3089 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL035 GROUP-NUM 1 If GROUP-NUM is populated, it must contains valid characters. 120 Field contains invalid characters - GROUP-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.GROUP-NUM), then fns.matches(@val.GROUP-NUM, "^[^|*]*$")' GROUP-NUM TPL035











3,795 Logic updated: string matching TPL036-0001 RULE-3090 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL036 MEMBER-ID 1 Value can only contain alpha characters (A-Z, a-z), numerials (0-9), spaces ( ), dashes (-), periods (.), forward slash (/), or single quote ('). 120 Field contains invalid characters - MEMBER-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.MEMBER-ID), then fns.matches(@val.MEMBER-ID, "^[^|*]*$")' MEMBER-ID TPL036











3,796 No logic changes TPL037-0002 RULE-3091 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL037 INSURANCE-PLAN-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



If the field is populated, the value must be contained in the set of valid values with id: INSURANCE-PLAN-TYPE INSURANCE-PLAN-TYPE TPL037











3,797 No logic changes TPL038-0001 RULE-3092 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL038 ANNUAL-DEDUCTIBLE-AMT 1 Non-Numeric Value Provided 109 Non-Numeric Value Provided 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be a valid dollar amount that matches the specified T-MSIS picture format: 9(11)V99 ANNUAL-DEDUCTIBLE-AMT TPL038











3,798 No logic changes TPL044-0002 RULE-3093 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL044 POLICY-OWNER-FIRST-NAME 2 If HEALTH-INSURANCE-COVERAGE-IND = "1", then POLICY-OWNER-FIRST-NAME must not be 8-filled 2366 Relational edit between POLICY-OWNER-FIRST-NAME and HEALTH-INSURANCE-COVERAGE-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003

'if fns.isEqual(@primaryRecord.TPL-HEALTH-INSURANCE-COVERAGE-IND, "1"), then fns.hasValue(@secondaryRecord.POLICY-OWNER-FIRST-NAME)' TPL-HEALTH-INSURANCE-COVERAGE-IND TPL020 POLICY-OWNER-FIRST-NAME TPL044

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL030,TPL032



3,799 Logic updated: string matching TPL044-0003 RULE-3094 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL044 POLICY-OWNER-FIRST-NAME 1 POLICY-OWNER-FIRST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - POLICY-OWNER-FIRST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.POLICY-OWNER-FIRST-NAME), then fns.matches(@val.POLICY-OWNER-FIRST-NAME, "^[^|*]*$")' POLICY-OWNER-FIRST-NAME TPL044











3,800 Logic updated: string matching TPL045-0001 RULE-3095 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL045 POLICY-OWNER-LAST-NAME 1 POLICY-OWNER-LAST-NAME must contain alpha characters (A-Z, a-z), dashes (-), periods (.), single quote ('), and spaces. 120 Field contains invalid characters - POLICY-OWNER-LAST-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.POLICY-OWNER-LAST-NAME), then fns.matches(@val.POLICY-OWNER-LAST-NAME, "^[^|*]*$")' POLICY-OWNER-LAST-NAME TPL045











3,801 No logic changes TPL045-0004 RULE-3096 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL045 POLICY-OWNER-LAST-NAME 2 If HEALTH-INSURANCE-COVERAGE-IND = "1", then POLICY-OWNER-LAST-NAME must not be 8-filled 2367 Relational edit between POLICY-OWNER-LAST-NAME and HEALTH-INSURANCE-COVERAGE-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003

'if fns.isEqual(@primaryRecord.TPL-HEALTH-INSURANCE-COVERAGE-IND, "1"), then fns.hasValue(@secondaryRecord.POLICY-OWNER-LAST-NAME)' TPL-HEALTH-INSURANCE-COVERAGE-IND TPL020 POLICY-OWNER-LAST-NAME TPL045

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL030,TPL032



3,802 No logic changes TPL046-0001 RULE-3097 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL046 POLICY-OWNER-SSN 1 Value is not in required format 101 Value is not in required format 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.POLICY-OWNER-SSN), then fns.matches(@val.POLICY-OWNER-SSN, "^[0-9]{9}$")' POLICY-OWNER-SSN TPL046











3,803 No logic changes TPL046-0002 RULE-3098 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL046 POLICY-OWNER-SSN 2 If HEALTH-INSURANCE-COVERAGE-IND = "1", then POLICY-OWNER-SSN must not be 8-filled 2368 Relational edit between POLICY-OWNER-SSN and HEALTH-INSURANCE-COVERAGE-IND failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003

'if fns.isEqual(@primaryRecord.TPL-HEALTH-INSURANCE-COVERAGE-IND, "1"), then fns.hasValue(@secondaryRecord.POLICY-OWNER-SSN)' TPL-HEALTH-INSURANCE-COVERAGE-IND TPL020 POLICY-OWNER-SSN TPL046

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL030,TPL032



3,804 No logic changes TPL047-0002 RULE-3099 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL047 POLICY-OWNER-CODE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



If the field is populated, the value must be contained in the set of valid values with id: POLICY-OWNER-CODE POLICY-OWNER-CODE TPL047











3,805 Merged TPL048-0001 RULE-3100 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL048 INSURANCE-COVERAGE-EFF-DATE 1 If INSURANCE-COVERAGE-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be a valid date of the form CCYYMMDD INSURANCE-COVERAGE-EFF-DATE TPL048











3,806 Merged TPL048-0003 RULE-3100 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL048 INSURANCE-COVERAGE-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be a valid date of the form CCYYMMDD INSURANCE-COVERAGE-EFF-DATE TPL048











3,807 Logic updated: other TPL048-0005 RULE-3102 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL048 INSURANCE-COVERAGE-EFF-DATE 2 INSURANCE-COVERAGE-EFF-DATE must be <= INSURANCE-COVERAGE-END-DATE 2052 Relational edit between INSURANCE-COVERAGE-EFF-DATE and INSURANCE-COVERAGE-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.INSURANCE-COVERAGE-EFF-DATE) && fns.hasValue(@val.INSURANCE-COVERAGE-END-DATE), then fns.isLessThanOrEqual(@val.INSURANCE-COVERAGE-EFF-DATE, @val.INSURANCE-COVERAGE-END-DATE)' INSURANCE-COVERAGE-EFF-DATE,INSURANCE-COVERAGE-END-DATE TPL048,TPL049











3,808 No logic changes TPL048-0008 RULE-3103 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL048 INSURANCE-COVERAGE-EFF-DATE 2 If two or more TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, INSURANCE-CARRIER-ID-NUM, INSURANCE-PLAN-ID, GROUP-NUM, MEMBER-ID, and COVERAGE-TYPE
then for each pair of record segments,
(Segment 1 INSURANCE-COVERAGE-EFF-DATE must <> Segment 2 INSURANCE-COVERAGE-EFF-DATE)
AND
( (If Segment 1 INSURANCE-COVERAGE-EFF-DATE < Segment 2 INSURANCE-COVERAGE-EFF-DATE,
then
Segment 1 INSURANCE-COVERAGE-END-DATE must be < Segment 2 INSURANCE-COVERAGE-EFF-DATE)
OR
(If Segment 2 INSURANCE-COVERAGE-EFF-DATE < Segment 1 INSURANCE-COVERAGE-EFF-DATE,
then
Segment 2 INSURANCE-COVERAGE-END-DATE must be < Segment 1 INSURANCE-COVERAGE-EFF-DATE) )		 2183 Edit for overlapping coverage dates in record segments that have non-unique key fields in TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Records with the same primary keys must have non-overlapping date ranges. Effective date field: INSURANCE-COVERAGE-EFF-DATE. End date field: INSURANCE-COVERAGE-END-DATE INSURANCE-COVERAGE-EFF-DATE,INSURANCE-COVERAGE-END-DATE TPL048,TPL049











3,809 Merged TPL048-0010 RULE-3085 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL048 INSURANCE-COVERAGE-EFF-DATE 2 ( INSURANCE-COVERAGE-EFF-DATE must be >= ELIG-PRSN-MAIN-EFF-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] ) AND
( INSURANCE-COVERAGE-EFF-DATE must be<= ELIG-PRSN-MAIN-END-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] )		 2492 Relational edit between INSURANCE-COVERAGE-EFF-DATE, ELIG-PRSN-MAIN-EFF-DATE, and ELIG-PRSN-MAIN-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003

record TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO has corresponding parent record TPL-MEDICAID-ELIGIBLE-PERSON-MAIN





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL030,TPL032



3,810 Retired: Other reasons TPL048-0011
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL048 INSURANCE-COVERAGE-EFF-DATE 2 ( INSURANCE-COVERAGE-EFF-DATE must be >= INSURANCE-CATEGORIES-EFF-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] ) AND
( INSURANCE-COVERAGE-EFF-DATE must be <= INSURANCE-CATEGORIES-END-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] )		 2493 Relational edit between INSURANCE-COVERAGE-EFF-DATE, INSURANCE-CATEGORIES-EFF-DATE, and INSURANCE-CATEGORIES-END-DATE failed

























3,811 Logic updated: other TPL048-0012 RULE-3106 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL048 INSURANCE-COVERAGE-END-DATE 3 If DATE-OF-DEATH [ELIGIBLE] is not 8-filled, then INSURANCE-COVERAGE-END-DATE must be <= DATE-OF-DEATH [ELIGIBLE] where ( SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = MSIS-IDENTIFICATION-NUM [PRIMARY-DEMOGRAPHICS-ELIGIBILITY-ELG00002] ) 3059 Relational edit between INSURANCE-COVERAGE-END-DATE and DATE-OF-DEATH [ELIGIBLE] failed 3 Relational error E3002 Values inconsistently specified (multi record, multi file) Two Record Type (1 to 1) PRIMARY-DEMOGRAPHICS-ELIGIBILITY ELG00002 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003

'if fns.hasValue(@primaryRecord.DATE-OF-DEATH) && fns.hasValue(@secondaryRecord.INSURANCE-COVERAGE-END-DATE), then fns.isLessThanOrEqual(@secondaryRecord.INSURANCE-COVERAGE-END-DATE, @primaryRecord.DATE-OF-DEATH)' DATE-OF-DEATH ELG025 INSURANCE-COVERAGE-END-DATE TPL049

SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM ELG017,ELG019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL030,TPL032



3,812 Merged TPL049-0001 RULE-3107 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL049 INSURANCE-COVERAGE-END-DATE 1 If INSURANCE-COVERAGE-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be a valid date of the form CCYYMMDD INSURANCE-COVERAGE-END-DATE TPL049











3,813 Merged TPL049-0003 RULE-3107 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL049 INSURANCE-COVERAGE-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



Value must be a valid date of the form CCYYMMDD INSURANCE-COVERAGE-END-DATE TPL049











3,814 Retired: Other reasons TPL049-0007
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL049 INSURANCE-COVERAGE-END-DATE 2 If HEALTH-INSURANCE-COVERAGE-IND = "1", then INSURANCE-COVERAGE-END-DATE must not be 8-filled 2307 Relational edit between INSURANCE-COVERAGE-END-DATE and HEALTH-INSURANCE-COVERAGE-IND failed

























3,815 Merged TPL049-0010 RULE-3085 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL049 INSURANCE-COVERAGE-END-DATE 2 ( INSURANCE-COVERAGE-END-DATE must be <= ELIG-PRSN-MAIN-END-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] ) AND
( INSURANCE-COVERAGE-END-DATE must be >= ELIG-PRSN-MAIN-EFF-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] )		 2494 Relational edit between INSURANCE-COVERAGE-END-DATE, ELIG-PRSN-MAIN-END-DATE, and ELIG-PRSN-MAIN-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003

record TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO has corresponding parent record TPL-MEDICAID-ELIGIBLE-PERSON-MAIN





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL030,TPL032



3,816 Retired: Other reasons TPL049-0011
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL049 INSURANCE-COVERAGE-END-DATE 2 ( INSURANCE-COVERAGE-END-DATE must be <= INSURANCE-CATEGORIES-END-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] ) AND
( INSURANCE-COVERAGE-END-DATE must be >= INSURANCE-CATEGORIES-EFF-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = INSURANCE-PLAN-ID [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] and COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003] = COVERAGE-TYPE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] )		 2495 Relational edit between INSURANCE-COVERAGE-END-DATE, INSURANCE-CATEGORIES-END-DATE, and INSURANCE-CATEGORIES-EFF-DATE failed

























3,817 Logic updated: string matching TPL050-0001 RULE-3112 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL050 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION TPL050











3,818 Moved to R&C TPL052-0003
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL052 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,819 Moved to R&C TPL052-0004
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL052 RECORD-ID 2 If FILE-NAME = "TPL-FILE", then the first 3 positions of RECORD-ID must = "TPL" 150 Invalid or missing RECORD-ID

























3,820 No logic changes TPL053-0002 RULE-3115 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL053 SUBMITTING-STATE 1 Value must be in the set of valid values 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE TPL053











3,821 Logic updated: other TPL053-0003 RULE-3116 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL053 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-TPL-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004 FILE-HEADER-RECORD-TPL TPL00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE TPL053 SUBMITTING-STATE TPL007









3,822 Retired: Other reasons TPL054-0001
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL054 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























3,823 No logic changes TPL054-0003 RULE-3118 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL054 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Field RECORD-NUMBER should be unique across all records of type TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES RECORD-NUMBER TPL054











3,824 Logic updated: string matching TPL055-0001 RULE-3119 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL055 INSURANCE-CARRIER-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - INSURANCE-CARRIER-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



'if fns.hasValue(@val.INSURANCE-CARRIER-ID-NUM), then fns.matches(@val.INSURANCE-CARRIER-ID-NUM, "^[^|*]*$")' INSURANCE-CARRIER-ID-NUM TPL055











3,825 Merged TPL055-0003 RULE-3120 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL055 INSURANCE-CARRIER-ID-NUM 2 INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] must = INSURANCE-CARRIER-ID-NUM [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] on any record in the file and SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] must = SUBMITTING-STATE [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] on the same record in the file 2223 Edit that TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES child record has a TPL-ENTITY-CONTACT-INFORMATION parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004

record TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES has corresponding parent record TPL-ENTITY-CONTACT-INFORMATION





SUBMITTING-STATE,INSURANCE-CARRIER-ID-NUM TPL073,TPL075 SUBMITTING-STATE,INSURANCE-CARRIER-ID-NUM TPL053,TPL055



3,826 Logic updated: string matching TPL056-0002 RULE-3121 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL056 INSURANCE-PLAN-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - INSURANCE-PLAN-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



'if fns.hasValue(@val.INSURANCE-PLAN-ID), then fns.matches(@val.INSURANCE-PLAN-ID, "^[^|*]*$")' INSURANCE-PLAN-ID TPL056











3,827 No logic changes TPL057-0002 RULE-3122 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL057 INSURANCE-PLAN-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



If the field is populated, the value must be contained in the set of valid values with id: INSURANCE-PLAN-TYPE INSURANCE-PLAN-TYPE TPL057











3,828 No logic changes TPL058-0001 RULE-3123 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL058 COVERAGE-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



If the field is populated, the value must be contained in the set of valid values with id: COVERAGE-TYPE COVERAGE-TYPE TPL058











3,829 Merged TPL059-0001 RULE-3124 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL059 INSURANCE-CATEGORIES-EFF-DATE 1 If INSURANCE-CATEGORIES-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be a valid date of the form CCYYMMDD INSURANCE-CATEGORIES-EFF-DATE TPL059











3,830 Merged TPL059-0003 RULE-3124 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL059 INSURANCE-CATEGORIES-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be a valid date of the form CCYYMMDD INSURANCE-CATEGORIES-EFF-DATE TPL059











3,831 Logic updated: other TPL059-0005 RULE-3126 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL059 INSURANCE-CATEGORIES-EFF-DATE 2 INSURANCE-CATEGORIES-EFF-DATE must be <= INSURANCE-CATEGORIES-END-DATE 2051 Relational edit between INSURANCE-CATEGORIES-EFF-DATE and INSURANCE-CATEGORIES-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



'if fns.hasValue(@val.INSURANCE-CATEGORIES-EFF-DATE) && fns.hasValue(@val.INSURANCE-CATEGORIES-END-DATE), then fns.isLessThanOrEqual(@val.INSURANCE-CATEGORIES-EFF-DATE, @val.INSURANCE-CATEGORIES-END-DATE)' INSURANCE-CATEGORIES-EFF-DATE,INSURANCE-CATEGORIES-END-DATE TPL059,TPL060











3,832 No logic changes TPL059-0007 RULE-3127 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL059 INSURANCE-CATEGORIES-EFF-DATE 2 If two or more TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES record segments have the same SUBMITTING-STATE, INSURANCE-CARRIER-ID-NUM, INSURANCE-PLAN-ID, and COVERAGE-TYPE
then for each pair of record segments,
(Segment 1 INSURANCE-CATEGORIES-EFF-DATE must <> Segment 2 INSURANCE-CATEGORIES-EFF-DATE)
AND
( (If Segment 1 INSURANCE-CATEGORIES-EFF-DATE < Segment 2 INSURANCE-CATEGORIES-EFF-DATE,
then
Segment 1 INSURANCE-CATEGORIES-END-DATE must be < Segment 2 INSURANCE-CATEGORIES-EFF-DATE)
OR
(If Segment 2 INSURANCE-CATEGORIES-EFF-DATE < Segment 1 INSURANCE-CATEGORIES-EFF-DATE,
then
Segment 2 INSURANCE-CATEGORIES-END-DATE must be < Segment 1 INSURANCE-CATEGORIES-EFF-DATE) )		 2182 Edit for overlapping coverage dates in record segments that have non-unique key fields in TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Records with the same primary keys must have non-overlapping date ranges. Effective date field: INSURANCE-CATEGORIES-EFF-DATE. End date field: INSURANCE-CATEGORIES-END-DATE INSURANCE-CATEGORIES-EFF-DATE,INSURANCE-CATEGORIES-END-DATE TPL059,TPL060











3,833 Retired: Other reasons TPL059-0009
TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL059 INSURANCE-CATEGORIES-EFF-DATE 2 If two or more TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES record segments have the same SUBMITTING-STATE, INSURANCE-CARRIER-ID-NUM, INSURANCE-PLAN-ID, and COVERAGE-TYPE and these record segments are sorted in ascending order by INSURANCE-CATEGORIES-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N INSURANCE-CATEGORIES-END-DATE must = Segment (N+1) INSURANCE-CATEGORIES-EFF-DATE minus 1 day 2459 Edit for contiguous TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES record segments failed (Exact match on all key fields except the file segment effective date)

























3,834 Merged TPL059-0010 RULE-3120 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL059 INSURANCE-CATEGORIES-EFF-DATE 2 ( INSURANCE-CATEGORIES-EFF-DATE must be >= TPL-ENTITY-CONTACT-INFO-EFF-DATE on any TPL-ENTITY-CONTACT-INFORMATION segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = SUBMITTING-STATE [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = INSURANCE-CARRIER-ID-NUM [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] ) AND
( INSURANCE-CATEGORIES-EFF-DATE must be <= TPL-ENTITY-CONTACT-INFO-END-DATE on any TPL-ENTITY-CONTACT-INFORMATION segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = SUBMITTING-STATE [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = INSURANCE-CARRIER-ID-NUM [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] )		 2490 Relational edit between INSURANCE-CATEGORIES-EFF-DATE, TPL-ENTITY-CONTACT-INFO-EFF-DATE, and TPL-ENTITY-CONTACT-INFO-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004

record TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES has corresponding parent record TPL-ENTITY-CONTACT-INFORMATION





SUBMITTING-STATE,INSURANCE-CARRIER-ID-NUM TPL073,TPL075 SUBMITTING-STATE,INSURANCE-CARRIER-ID-NUM TPL053,TPL055



3,835 Merged TPL060-0001 RULE-3130 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL060 INSURANCE-CATEGORIES-END-DATE 1 If INSURANCE-CATEGORIES-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be a valid date of the form CCYYMMDD INSURANCE-CATEGORIES-END-DATE TPL060











3,836 Merged TPL060-0003 RULE-3130 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL060 INSURANCE-CATEGORIES-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



Value must be a valid date of the form CCYYMMDD INSURANCE-CATEGORIES-END-DATE TPL060











3,837 Merged TPL060-0010 RULE-3120 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL060 INSURANCE-CATEGORIES-END-DATE 2 ( INSURANCE-CATEGORIES-END-DATE must be <= TPL-ENTITY-CONTACT-INFO-END-DATE on any TPL-ENTITY-CONTACT-INFORMATION segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = SUBMITTING-STATE [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = INSURANCE-CARRIER-ID-NUM [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] ) AND
( INSURANCE-CATEGORIES-END-DATE must be >= TPL-ENTITY-CONTACT-INFO-EFF-DATE on any TPL-ENTITY-CONTACT-INFORMATION segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = SUBMITTING-STATE [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] and INSURANCE-CARRIER-ID-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004] = INSURANCE-CARRIER-ID-NUM [TPL-ENTITY-CONTACT-INFORMATION-TPL00006] )		 2491 Relational edit between INSURANCE-CATEGORIES-END-DATE, TPL-ENTITY-CONTACT-INFO-END-DATE, and TPL-ENTITY-CONTACT-INFO-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006 TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004

record TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES has corresponding parent record TPL-ENTITY-CONTACT-INFORMATION





SUBMITTING-STATE,INSURANCE-CARRIER-ID-NUM TPL073,TPL075 SUBMITTING-STATE,INSURANCE-CARRIER-ID-NUM TPL053,TPL055



3,838 Logic updated: string matching TPL061-0001 RULE-3133 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES-TPL00004 TPL061 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-CATEGORIES TPL00004



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION TPL061











3,839 No logic changes TPL063-0003 RULE-6598 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL063 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be compatible with specified T-MSIS picture format: X(8) RECORD-TYPE TPL063











3,840 Moved to R&C TPL063-0004
TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL063 RECORD-ID 2 If FILE-NAME = "TPL-FILE", then the first 3 positions of RECORD-ID must = "TPL" 150 Invalid or missing RECORD-ID

























3,841 No logic changes TPL064-0002 RULE-3136 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL064 SUBMITTING-STATE 1 Value must be in the set of valid values 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE TPL064











3,842 Logic updated: other TPL064-0003 RULE-3137 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL064 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-TPL-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005 FILE-HEADER-RECORD-TPL TPL00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE TPL064 SUBMITTING-STATE TPL007









3,843 Retired: Other reasons TPL065-0001
TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL065 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























3,844 No logic changes TPL065-0003 RULE-3139 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL065 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Field RECORD-NUMBER should be unique across all records of type TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION RECORD-NUMBER TPL065











3,845 Retired: MSIS ID checks TPL066-0001
TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL066 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























3,846 Retired: MSIS ID checks TPL066-0002
TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL066 MSIS-IDENTIFICATION-NUM 1 Value supplied does not comply with the valid format provided by the state. 126 Value supplied does not comply with the valid format provided by the state.

























3,847 Retired: MSIS ID checks TPL066-0005
TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL066 MSIS-IDENTIFICATION-NUM 1 If MSIS-IDENTIFICATION-NUM=spaces 113 Required data element has not been reported.

























3,848 Merged TPL066-0006 RULE-3143 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL066 MSIS-IDENTIFICATION-NUM 2 MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] must = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] on any record in the file and SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] must = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] on the same record in the file 2222 Edit that TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION child record has a TPL-MEDICAID-ELIGIBLE-PERSON-MAIN parent record failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005

record TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION has corresponding parent record TPL-MEDICAID-ELIGIBLE-PERSON-MAIN





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL064,TPL066



3,849 No logic changes TPL067-0002 RULE-3144 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL067 TYPE-OF-OTHER-THIRD-PARTY-LIABILITY 1 Value must be in the set of valid values 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



If the field is populated, the value must be contained in the set of valid values with id: TYPE-OF-OTHER-THIRD-PARTY-LIABILITY TYPE-OF-OTHER-THIRD-PARTY-LIABILITY TPL067











3,850 Merged TPL068-0001 RULE-3145 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL068 OTHER-TPL-EFF-DATE 1 If OTHER-TPL-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be a valid date of the form CCYYMMDD OTHER-TPL-EFF-DATE TPL068











3,851 Merged TPL068-0003 RULE-3145 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL068 OTHER-TPL-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be a valid date of the form CCYYMMDD OTHER-TPL-EFF-DATE TPL068











3,852 Logic updated: other TPL068-0005 RULE-3147 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL068 OTHER-TPL-EFF-DATE 2 OTHER-TPL-EFF-DATE must be <= OTHER-TPL-END-DATE 2089 Relational edit between OTHER-TPL-EFF-DATE and OTHER-TPL-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



'if fns.hasValue(@val.OTHER-TPL-EFF-DATE) && fns.hasValue(@val.OTHER-TPL-END-DATE), then fns.isLessThanOrEqual(@val.OTHER-TPL-EFF-DATE, @val.OTHER-TPL-END-DATE)' OTHER-TPL-EFF-DATE,OTHER-TPL-END-DATE TPL068,TPL069











3,853 No logic changes TPL068-0008 RULE-3148 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL068 OTHER-TPL-EFF-DATE 2 If two or more TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION record segments have the same SUBMITTING-STATE, MSIS-IDENTIFICATION-NUM, and TYPE-OF-OTHER-THIRD-PARTY-LIABILITY
then for each pair of record segments,
(Segment 1 OTHER-TPL-EFF-DATE must <> Segment 2 OTHER-TPL-EFF-DATE)
AND
( (If Segment 1 OTHER-TPL-EFF-DATE < Segment 2 OTHER-TPL-EFF-DATE,
then
Segment 1 OTHER-TPL-END-DATE must be < Segment 2 OTHER-TPL-EFF-DATE)
OR
(If Segment 2 OTHER-TPL-EFF-DATE < Segment 1 OTHER-TPL-EFF-DATE,
then
Segment 2 OTHER-TPL-END-DATE must be < Segment 1 OTHER-TPL-EFF-DATE) )		 2181 Edit for overlapping coverage dates in record segments that have non-unique key fields in TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Records with the same primary keys must have non-overlapping date ranges. Effective date field: OTHER-TPL-EFF-DATE. End date field: OTHER-TPL-END-DATE OTHER-TPL-EFF-DATE,OTHER-TPL-END-DATE TPL068,TPL069











3,854 Merged TPL068-0010 RULE-3143 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL068 OTHER-TPL-EFF-DATE 2 ( OTHER-TPL-EFF-DATE must be >= ELIG-PRSN-MAIN-EFF-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] ) AND
( OTHER-TPL-EFF-DATE must be <= ELIG-PRSN-MAIN-END-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] )		 2519 Relational edit between OTHER-TPL-EFF-DATE, ELIG-PRSN-MAIN-EFF-DATE, and ELIG-PRSN-MAIN-END-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005

record TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION has corresponding parent record TPL-MEDICAID-ELIGIBLE-PERSON-MAIN





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL064,TPL066



3,855 Merged TPL069-0001 RULE-3150 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL069 OTHER-TPL-END-DATE 1 If OTHER-TPL-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be a valid date of the form CCYYMMDD OTHER-TPL-END-DATE TPL069











3,856 Merged TPL069-0003 RULE-3150 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL069 OTHER-TPL-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



Value must be a valid date of the form CCYYMMDD OTHER-TPL-END-DATE TPL069











3,857 Retired: Other reasons TPL069-0007
TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL069 OTHER-TPL-END-DATE 2 If HEALTH-INSURANCE-COVERAGE-IND = "1", then OTHER-TPL-END-DATE must not be 8-filled 2359 Relational edit between OTHER-TPL-END-DATE and HEALTH-INSURANCE-COVERAGE-IND failed

























3,858 Merged TPL069-0010 RULE-3143 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL069 OTHER-TPL-END-DATE 2 ( OTHER-TPL-END-DATE must be <= ELIG-PRSN-MAIN-END-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] ) AND
( OTHER-TPL-END-DATE must be >= ELIG-PRSN-MAIN-EFF-DATE on any TPL-MEDICAID-ELIGIBLE-PERSON-MAIN segment
where SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = SUBMITTING-STATE [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] and MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005] = MSIS-IDENTIFICATION-NUM [TPL-MEDICAID-ELIGIBLE-PERSON-MAIN-TPL00002] )		 2520 Relational edit between OTHER-TPL-END-DATE, ELIG-PRSN-MAIN-END-DATE, and ELIG-PRSN-MAIN-EFF-DATE failed 2.1 Relational error E2101 Missing parent record (single file) Child Parent Rule TPL-MEDICAID-ELIGIBLE-PERSON-MAIN TPL00002 TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005

record TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION has corresponding parent record TPL-MEDICAID-ELIGIBLE-PERSON-MAIN





SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL017,TPL019 SUBMITTING-STATE,MSIS-IDENTIFICATION-NUM TPL064,TPL066



3,859 Logic updated: string matching TPL070-0001 RULE-3154 TPL TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION-TPL00005 TPL070 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-MEDICAID-ELIGIBLE-OTHER-THIRD-PARTY-COVERAGE-INFORMATION TPL00005



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION TPL070











3,860 Moved to R&C TPL072-0003
TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL072 RECORD-ID 1 Value is not included in the valid code list 103 Value is not included in the valid code list

























3,861 Moved to R&C TPL072-0004
TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL072 RECORD-ID 2 If FILE-NAME = "TPL-FILE", then the first 3 positions of RECORD-ID must = "TPL" 150 Invalid or missing RECORD-ID

























3,862 No logic changes TPL073-0002 RULE-3157 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL073 SUBMITTING-STATE 1 Value must be in the set of valid values 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-ENTITY-CONTACT-INFORMATION TPL00006



If the field is populated, the value must be contained in the set of valid values with id: STATE SUBMITTING-STATE TPL073











3,863 Logic updated: other TPL073-0003 RULE-3158 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL073 SUBMITTING-STATE 2 SUBMITTING-STATE in this file segment must = SUBMITTING-STATE [FILE-HEADER-RECORD-TPL-PRV00001] 2124 Relational edit between SUBMITTING-STATE and SUBMITTING-STATE in the Header Record failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-ENTITY-CONTACT-INFORMATION TPL00006 FILE-HEADER-RECORD-TPL TPL00001

'if fns.hasValue(@val.SUBMITTING-STATE) && fns.hasValue(@fileHeader.SUBMITTING-STATE), then fns.isStateEqual(@val.SUBMITTING-STATE, @fileHeader.SUBMITTING-STATE)' SUBMITTING-STATE TPL073 SUBMITTING-STATE TPL007









3,864 Retired: Other reasons TPL074-0001
TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL074 RECORD-NUMBER 1 If RECORD-NUMBER =0 109 Non-Numeric Value Provided

























3,865 No logic changes TPL074-0003 RULE-3160 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL074 RECORD-NUMBER 2 RECORD-NUMBER must <> RECORD-NUMBER from any other record segment that has the same RECORD-ID 2139 Duplicate RECORD-NUMBER across records within the same segment 0 File specification error E0003 Duplicate record identifier (RECORD-NUM or primary key values) One Record Type (Multi Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



Field RECORD-NUMBER should be unique across all records of type TPL-ENTITY-CONTACT-INFORMATION RECORD-NUMBER TPL074











3,866 Logic updated: string matching TPL075-0001 RULE-3161 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL075 INSURANCE-CARRIER-ID-NUM 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - INSURANCE-CARRIER-ID-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-ID-NUM), then fns.matches(@val.INSURANCE-CARRIER-ID-NUM, "^[^|*]*$")' INSURANCE-CARRIER-ID-NUM TPL075











3,867 No logic changes TPL076-0002 RULE-3162 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL076 TPL-ENTITY-ADDR-TYPE 1 Value must be in the set of valid values 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-ENTITY-CONTACT-INFORMATION TPL00006



If the field is populated, the value must be contained in the set of valid values with id: TPL-ENTITY-ADDR-TYPE TPL-ENTITY-ADDR-TYPE TPL076











3,868 Logic updated: string matching TPL077-0003 RULE-3163 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL077 INSURANCE-CARRIER-ADDR-LN1 1 If INSURANCE-CARRIER-ADDR-LN1 is populated, it must contains valid characters. 120 Field contains invalid characters - INSURANCE-CARRIER-ADDR-LN1 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-ADDR-LN1), then fns.matches(@val.INSURANCE-CARRIER-ADDR-LN1, "^[^|*]*$")' INSURANCE-CARRIER-ADDR-LN1 TPL077











3,869 Logic updated: string matching TPL078-0001 RULE-3164 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL078 INSURANCE-CARRIER-ADDR-LN2 1 If INSURANCE-CARRIER-ADDR-LN2 is populated, it must contains valid characters. 120 Field contains invalid characters - INSURANCE-CARRIER-ADDR-LN2 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-ADDR-LN2), then fns.matches(@val.INSURANCE-CARRIER-ADDR-LN2, "^[^|*]*$")' INSURANCE-CARRIER-ADDR-LN2 TPL078











3,870 Merged TPL078-0002 RULE-7138 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL078 INSURANCE-CARRIER-ADDR-LN2 2 If INSURANCE-CARRIER-ADDR-LN2 is not 8-filled,
then INSURANCE-CARRIER-ADDR-LN2 must <> INSURANCE-CARRIER-ADDR-LN1		 2302 Relational edit between INSURANCE-CARRIER-ADDR-LN2 and INSURANCE-CARRIER-ADDR-LN1
failed (duplicate value entered)		 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



The values of the following fields should be unique (non-repeating) within each record: INSURANCE-CARRIER-ADDR-LN1,INSURANCE-CARRIER-ADDR-LN2,INSURANCE-CARRIER-ADDR-LN3 INSURANCE-CARRIER-ADDR-LN1,INSURANCE-CARRIER-ADDR-LN2,INSURANCE-CARRIER-ADDR-LN3 TPL077,TPL078,TPL079











3,871 Logic updated: string matching TPL079-0001 RULE-3166 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL079 INSURANCE-CARRIER-ADDR-LN3 1 If INSURANCE-CARRIER-ADDR-LN3 is populated, it must contains valid characters. 120 Field contains invalid characters - INSURANCE-CARRIER-ADDR-LN3 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-ADDR-LN3), then fns.matches(@val.INSURANCE-CARRIER-ADDR-LN3, "^[^|*]*$")' INSURANCE-CARRIER-ADDR-LN3 TPL079











3,872 Merged TPL079-0002 RULE-7138 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL079 INSURANCE-CARRIER-ADDR-LN3 2 (If INSURANCE-CARRIER-ADDR-LN3 is not 8-filled
then INSURANCE-CARRIER-ADDR-LN3 must <> INSURANCE-CARRIER-ADDR-LN1)
AND
(If INSURANCE-CARRIER-ADDR-LN2 is not 8-filled,
then INSURANCE-CARRIER-ADDR-LN3 must <> INSURANCE-CARRIER-ADDR-LN2)		 2304 Relational edit between INSURANCE-CARRIER-ADDR-LN3 and INSURANCE-CARRIER-ADDR-LN2 or INSURANCE-CARRIER-ADDR-LN1 failed (duplicate value entered) 2 Relational error E2002 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



The values of the following fields should be unique (non-repeating) within each record: INSURANCE-CARRIER-ADDR-LN1,INSURANCE-CARRIER-ADDR-LN2,INSURANCE-CARRIER-ADDR-LN3 INSURANCE-CARRIER-ADDR-LN1,INSURANCE-CARRIER-ADDR-LN2,INSURANCE-CARRIER-ADDR-LN3 TPL077,TPL078,TPL079











3,873 No logic changes TPL079-0003 RULE-3168 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL079 INSURANCE-CARRIER-ADDR-LN3 2 If INSURANCE-CARRIER-ADDR-LN2 is 8-filled, then INSURANCE-CARRIER-ADDR-LN3 must be 8-filled 2303 Relational edit between INSURANCE-CARRIER-ADDR-LN2 and INSURANCE-CARRIER-ADDR-LN3 failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if !fns.hasValue(@val.INSURANCE-CARRIER-ADDR-LN2), then !fns.hasValue(@val.INSURANCE-CARRIER-ADDR-LN3)' INSURANCE-CARRIER-ADDR-LN2,INSURANCE-CARRIER-ADDR-LN3 TPL078,TPL079











3,874 Logic updated: string matching TPL080-0001 RULE-3169 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL080 INSURANCE-CARRIER-CITY 1 Field contains invalid characters - INSURANCE-CARRIER-CITY 120 Field contains invalid characters - INSURANCE-CARRIER-CITY 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-CITY), then fns.matches(@val.INSURANCE-CARRIER-CITY, "^[^|*]*$")' INSURANCE-CARRIER-CITY TPL080











3,875 No logic changes TPL081-0001 RULE-3170 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL081 INSURANCE-CARRIER-STATE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-ENTITY-CONTACT-INFORMATION TPL00006



If the field is populated, the value must be contained in the set of valid values with id: STATE INSURANCE-CARRIER-STATE TPL081











3,876 No logic changes TPL082-0002 RULE-3171 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL082 INSURANCE-CARRIER-ZIP-CODE 1 Value must be > zeros. 113 Required data element has not been reported. 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-ZIP-CODE), then fns.matches(@val.INSURANCE-CARRIER-ZIP-CODE, "^[0-9]{5}|[0-9]{9}$")' INSURANCE-CARRIER-ZIP-CODE TPL082











3,877 No logic changes TPL083-0001 RULE-7150 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL083 INSURANCE-CARRIER-PHONE-NUM 1 INSURANCE-CARRIER-PHONE-NUM must not contain parentheses, dashes, periods, commas, spaces 120 Field contains invalid characters - INSURANCE-CARRIER-PHONE-NUM 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-PHONE-NUM), then fns.isNumericString(@val.INSURANCE-CARRIER-PHONE-NUM)' INSURANCE-CARRIER-PHONE-NUM TPL083











3,878 Merged TPL084-0001 RULE-3173 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL084 TPL-ENTITY-CONTACT-INFO-EFF-DATE 1 If TPL-ENTITY-CONTACT-INFO-EFF-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be a valid date of the form CCYYMMDD TPL-ENTITY-CONTACT-INFO-EFF-DATE TPL084











3,879 Merged TPL084-0003 RULE-3173 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL084 TPL-ENTITY-CONTACT-INFO-EFF-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be a valid date of the form CCYYMMDD TPL-ENTITY-CONTACT-INFO-EFF-DATE TPL084











3,880 Logic updated: other TPL084-0005 RULE-3175 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL084 TPL-ENTITY-CONTACT-INFO-EFF-DATE 2 TPL-ENTITY-CONTACT-INFO-EFF-DATE must be <= TPL-ENTITY-CONTACT-INFO-END-DATE 2128 Relational edit between TPL-ENTITY-CONTACT-INFO-EFF-DATE and TPL-ENTITY-CONTACT-INFO-END-DATE failed 2 Relational error E2001 Values inconsistently specified (single record type, single record) One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.TPL-ENTITY-CONTACT-INFO-EFF-DATE) && fns.hasValue(@val.TPL-ENTITY-CONTACT-INFO-END-DATE), then fns.isLessThanOrEqual(@val.TPL-ENTITY-CONTACT-INFO-EFF-DATE, @val.TPL-ENTITY-CONTACT-INFO-END-DATE)' TPL-ENTITY-CONTACT-INFO-EFF-DATE,TPL-ENTITY-CONTACT-INFO-END-DATE TPL084,TPL085











3,881 No logic changes TPL084-0006 RULE-3176 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL084 TPL-ENTITY-CONTACT-INFO-EFF-DATE 2 If two or more TPL-ENTITY-CONTACT-INFORMATION record segments have the same SUBMITTING-STATE, INSURANCE-CARRIER-ID-NUM, and TPL-ENTITY-ADDR-TYPE
then for each pair of record segments,
(Segment 1 TPL-ENTITY-CONTACT-INFO-EFF-DATE must <> Segment 2 TPL-ENTITY-CONTACT-INFO-EFF-DATE)
AND
( (If Segment 1 TPL-ENTITY-CONTACT-INFO-EFF-DATE < Segment 2 TPL-ENTITY-CONTACT-INFO-EFF-DATE,
then
Segment 1 TPL-ENTITY-CONTACT-INFO-END-DATE must be < Segment 2 TPL-ENTITY-CONTACT-INFO-EFF-DATE)
OR
(If Segment 2 TPL-ENTITY-CONTACT-INFO-EFF-DATE < Segment 1 TPL-ENTITY-CONTACT-INFO-EFF-DATE,
then
Segment 2 TPL-ENTITY-CONTACT-INFO-END-DATE must be < Segment 1 TPL-ENTITY-CONTACT-INFO-EFF-DATE) )		 2180 Edit for overlapping coverage dates in record segments that have non-unique key fields in TPL-ENTITY-CONTACT-INFORMATION failed (Exact match on all key fields except the file segment effective date) 2 Relational error E2002 Values inconsistently specified (single record type, multiple records) One Record Type (Multiple Records) TPL-ENTITY-CONTACT-INFORMATION TPL00006



Records with the same primary keys must have non-overlapping date ranges. Effective date field: TPL-ENTITY-CONTACT-INFO-EFF-DATE. End date field: TPL-ENTITY-CONTACT-INFO-END-DATE TPL-ENTITY-CONTACT-INFO-EFF-DATE,TPL-ENTITY-CONTACT-INFO-END-DATE TPL084,TPL085











3,882 Retired: Other reasons TPL084-0008
TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL084 TPL-ENTITY-CONTACT-INFO-EFF-DATE 2 If two or more TPL-ENTITY-CONTACT-INFORMATION record segments have the same SUBMITTING-STATE and INSURANCE-CARRIER-ID-NUM and these record segments are sorted in ascending order by TPL-ENTITY-CONTACT-INFO-EFF-DATE, then for each consecutive pair (1,2; 2,3; 3,4; etc.) of record segments, Segment N TPL-ENTITY-CONTACT-INFO-END-DATE must = Segment (N+1) TPL-ENTITY-CONTACT-INFO-EFF-DATE minus 1 day 2458 Edit for contiguous TPL-ENTITY-CONTACT-INFORMATION record segments failed (Exact match on all key fields except the file segment effective date)

























3,883 Merged TPL085-0001 RULE-3178 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL085 TPL-ENTITY-CONTACT-INFO-END-DATE 1 If TPL-ENTITY-CONTACT-INFO-END-DATE is not in CCYYMMDD format 101 Value is not in required format 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be a valid date of the form CCYYMMDD TPL-ENTITY-CONTACT-INFO-END-DATE TPL085











3,884 Merged TPL085-0003 RULE-3178 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL085 TPL-ENTITY-CONTACT-INFO-END-DATE 1 Value is not a valid date 102 Value is not a valid date 1 Formatting Error E1001 Value illegal for specified data type Parse Rule TPL-ENTITY-CONTACT-INFORMATION TPL00006



Value must be a valid date of the form CCYYMMDD TPL-ENTITY-CONTACT-INFO-END-DATE TPL085











3,885 Logic updated: string matching TPL086-0001 RULE-3180 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL086 STATE-NOTATION 1 If STATE-NOTATION is populated, it must contains valid characters. 120 Field contains invalid characters - STATE-NOTATION 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.STATE-NOTATION), then fns.matches(@val.STATE-NOTATION, "^[^|*]*$")' STATE-NOTATION TPL086











3,886 Moved to R&C TPL088-0002
TPL FILE-HEADER-RECORD-TPL-TPL00001 TPL088 SEQUENCE-NUMBER 1 If SEQUENCE-NUMBER not > 0 105 Value out of range

























3,887 No logic changes TPL089-0001 RULE-3182 TPL TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO-TPL00003 TPL089 COVERAGE-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-MEDICAID-ELIGIBLE-PERSON-HEALTH-INSURANCE-COVERAGE-INFO TPL00003



If the field is populated, the value must be contained in the set of valid values with id: COVERAGE-TYPE COVERAGE-TYPE TPL089











3,888 Logic updated: string matching TPL090-0001 RULE-3183 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL090 INSURANCE-CARRIER-NAIC-CODE 1 Value can only contain spaces, alpha characters (A-Z, a-z), numerals (0-9), parentheses (), forward slash (/), dashes (-), periods (.), or commas (,). 120 Field contains invalid characters - INSURANCE-CARRIER-NAIC-CODE 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-NAIC-CODE), then fns.matches(@val.INSURANCE-CARRIER-NAIC-CODE, "^[^|*]*$")' INSURANCE-CARRIER-NAIC-CODE TPL090











3,889 Logic updated: string matching TPL091-0002 RULE-3184 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL091 INSURANCE-CARRIER-NAME 1 Value can only contain spaces, alpha characters (A-Z, a-z), numerals (0-9), parentheses (), forward slash (/), dashes (-), periods (.), or commas (,). 120 Field contains invalid characters - INSURANCE-CARRIER-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.INSURANCE-CARRIER-NAME), then fns.matches(@val.INSURANCE-CARRIER-NAME, "^[^|*]*$")' INSURANCE-CARRIER-NAME TPL091











3,890 No logic changes TPL092-0003 RULE-3185 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL092 NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE 1 Value is not included in the valid code list 103 Value is not included in the valid code list 1.1 Value Error E1103 Value not in specified valid value set Valid Value TPL-ENTITY-CONTACT-INFORMATION TPL00006



If the field is populated, the value must be contained in the set of valid values with id: NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE NATIONAL-HEALTH-CARE-ENTITY-ID-TYPE TPL092











3,891 Logic updated: string matching TPL093-0004 RULE-3186 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL093 NATIONAL-HEALTH-CARE-ENTITY-ID 1 If characters in text string are not alpha characters (A-Z, a-z), numbers (0-9) 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-ID 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-ID, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-ID TPL093











3,892 No logic changes TPL093-0006 RULE-3187 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL093 NATIONAL-HEALTH-CARE-ENTITY-ID 2 If START-OF-TIME-PERIOD >= 20151105, then NATIONAL-HEALTH-CARE-ENTITY-ID must not be 8-filled 2332 Relational edit between NATIONAL-HEALTH-CARE-ENTITY-ID and START-OF-TIME-PERIOD failed 2.1 Relational error E2102 Values inconsistently specified (multi record, single file) Two Record Type (1 to 1) TPL-ENTITY-CONTACT-INFORMATION TPL00006 FILE-HEADER-RECORD-TPL TPL00001

'if fns.isGreaterThanOrEqual(@fileHeader.START-OF-TIME-PERIOD, "2015-11-05"), then fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-ID)' NATIONAL-HEALTH-CARE-ENTITY-ID TPL093 START-OF-TIME-PERIOD TPL009









3,893 Logic updated: string matching TPL094-0002 RULE-3188 TPL TPL-ENTITY-CONTACT-INFORMATION-TPL00006 TPL094 NATIONAL-HEALTH-CARE-ENTITY-NAME 1 Value can only contain alpha characters (A-Z, a-z), numerals (0-9), spaces ( ), dashes (-), periods (.), forward slash (/), or single quote ('). 120 Field contains invalid characters - NATIONAL-HEALTH-CARE-ENTITY-NAME 1.1 Value Error E1102 Value does not match specification One Record Type (Single Record) TPL-ENTITY-CONTACT-INFORMATION TPL00006



'if fns.hasValue(@val.NATIONAL-HEALTH-CARE-ENTITY-NAME), then fns.matches(@val.NATIONAL-HEALTH-CARE-ENTITY-NAME, "^[^|*]*$")' NATIONAL-HEALTH-CARE-ENTITY-NAME TPL094











Sheet 3: Reading the Validation Logic
Key to Understanding the Nomenclature of the V2.0 Validation Rules

What does ‘!’ mean in the business rules?
The exclamation point is the “not” operator. So if you see something like:
ex 1: !fns.isLessThanZero(@val.DOLLAR-AMT)
This would be read as “DOLLAR-AMT is *NOT* less than zero.”
ex 2: !fns.hasValue(@val.DATE)
This is read as “DATE does *NOT* have a value.”

What does ‘fns’ mean?
“fns” appears in front of function names like “fns.isGreaterThan(@val.START-DATE, @val.END-DATE).” “fns” stands for “functions.” So “fns.isGreaterThan(@val.START-DATE, @val.END-DATE)” is translated as “apply the isGreaterThan function to START-DATE and END-DATE” or in other words, "Evaluate whether the START-DATE is greater than the END-DATE."

What does ‘@‘symbol mean?
Throughout the business rules you will see “@val”, “@primaryRecord”, “@secondaryRecord”, “@vals" etc. These will always be followed by the name of a field, like “@val.DIAGNOSIS-CODE” or “@primaryRecord.DATE-OF-BIRTH” or “@vals.DOLLAR-AMT”. These symbols represent the records. So if you see “fns.hasValue(@val.DATE-OF-BIRTH)” this should be read as DATE-OF-BIRTH on each record should have a value. If you see “fns.isGreaterThanOrEqual(@primaryRecord.ADJUDICATION-DATE, @secondaryRecord.ADMISSION-DATE)” this should be read as: ADJUDICATION-DATE in the primary type record should be greater than or equal to ADMISSION-DATE in the secondary type record.

What is the 'fns.matches' function?
"fns.matches(@val.ICN-ADJ, "^[^|*]*$”)” can be read as “The ICN-ADJ field of each record should match the pattern "^[^|*]*$”. This particular pattern represents any character, any number of times EXCEPT for the “|” character or the "*" character.
File Typeapplication/vnd.openxmlformats-officedocument.spreadsheetml.sheet
File Modified0000-00-00
File Created0000-00-00
© 2024 OMB.report | Privacy Policy