Medicare Advantage and Prescription Drug Plans December 28 ...

More documents

Recommendations

Info

Plan Communications User Guide Appendices, Version 6.3 I.10 BEQ Response File Error Condition Table I.10.1 Request File Error Conditions The following table contains File Level Error information. File Level Errors represent conditions in which a BEQ Request File is rejected and not processed. Table I-8: File Level Error information SOURCE OF ERROR Header Record Header Record Trailer Record Trailer Record File Content ERROR MESSAGE The Header Record is missing. The Header Record is Invalid. The Trailer Record is missing. The Trailer Record is invalid. The File has no Transactions. ERROR CONDITION ● The Header Record is not provided on the file. ● The Header Record is unreadable. ● More than one Header Record is provided on the file. ● The Header Record is incorrectly formatted. ● The Header Record contains invalid values. ● The Header Record contains Critical Fields that are not provided. ● The Trailer Record is not provided on the file. ● The Trailer Record is unreadable. ● More than one Trailer Record is provided on the file. ● The Trailer Record is incorrectly formatted. ● The Trailer Record contains invalid values. ● The Trailer Record contains Critical Fields that are not populated. ● The Record Count in the Trailer Record is more than 2 different from the actual number of Detail Records (Transactions) in the file. ● There are no Transactions (Detail Records) found in the file. December 28, 2012 I-111 BEQ Response File Error Condition Table
Plan Communications User Guide Appendices, Version 6.3 I.10.2 Request Transaction Detail Record Error Conditions The following Flag fields are provided in the Response File Detail Record. Flag fields represent the successful or unsuccessful result of processing data within a Transaction Detail Record of the input file. Table I-9: Error Conditions FLAG FLAG CODE FLAG CODE RESULT FLAG RESULT CONDITION Processed Flag Y The Transaction is accepted for processing. All critical fields on the Transaction are populated with valid values. Processed Flag N The Transaction is not accepted for processing. At least one critical field on the Transaction is populated with a value other than the prescribed valid values. Beneficiary Match Flag Y The beneficiary on the Transaction is successfully located in the MBD. The beneficiary is successfully located by the combination of the HICN or RRB, SSN; date of birth, and gender. Beneficiary Match Flag N The beneficiary on the Transaction is not successfully located in the MBD. The beneficiary is not successfully located by the combination of the HICN or RRB, SSN; date of birth, and gender. Beneficiary Match Flag SPACE No attempt made to locate the beneficiary on the MBD. An invalid condition exists in the Transaction Detail Record such as an unexpected, absent, or invalid value in a Critical Field. December 28, 2012 I-112 BEQ Response File Error Condition Table
Page 1 and 2:
Medicare Advantage and Prescription
Page 3 and 4:
Plan Communications User Guide Appe
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
F.10.3 Trailer Record Plan Communic
Page 79 and 80:
F.11.2 Record Type 2 Plan Communica
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
F.21.2 Detail Record (Transaction)
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
F.23.2 Detail Record (Transaction)
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Item # Plan Communications User Gui
Page 171 and 172:
F.28.3 Trailer Record Plan Communic
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246: Plan Communications User Guide Appe
Page 269 and 270: I.3 Obsolete Transaction Reply Code
Page 295: Plan Communications User Guide Appe
Page 341 and 342: CMS Transmittals to the Plans Plan
Page 345 and 346: ID# Transmittal Monthly Transmittal
Page 347 and 348:
ID# Transmittal Monthly Transmittal
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
show all

Medicare Advantage and Prescription Drug Plans December 28 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?