Medicare Secondary Payer Manual (Pub. 100-05), Ch. 6 § 20

MSP Maintenance Transaction Record Processing

Last amended: 2023Year: 2023Length: 170 wordsOfficial source
20 - MSP Maintenance Transaction Record Processing (Rev. 12078; Issued:06-14-23; Effective: 05-29-23; Implementation: 05-29-23) The MSP Contractor shall submit an MSP maintenance transaction to establish an MSP auxiliary record within 10 calendar days of receipt of notice that another payer is primary to Medicare. The CWF applies extensive editing to the maintenance transaction. If an MSP maintenance transaction does not meet all edit criteria, error codes specific to the failed edit(s) will be returned via the CWF MSP Maintenance Transaction Response. A complete record layout and field descriptions are contained in CWF Systems Documentation, Record Name: CWF, MSP Maintenance Transaction Response. For Out- of-Service (OSA) Area transactions, the CWF OSA Maintenance Transaction Response is used. Its complete record layout and field descriptions are contained in CWF Systems Documentation, Record Name: CWF, MSP Maintenance Transaction Response. The consistency edit error codes and edit definitions are contained in CWF Systems Documentation Record Name: MSP Maintenance Transaction Error Codes. MSP transactions that pass all edits are applied to the CWF, MSP auxiliary file.
Medicare Secondary Payer Manual (Pub. 100-05), Ch. 6 § 20: MSP Maintenance Transaction Record Processing | Justis AI