Medicare Claims Processing Manual (Pub. 100-04), Ch. 27 § 80.3

Beneficiary Other Insurance Information (HUBO) Maintenance

Last amended: 2018Year: 2018Length: 212 wordsOfficial source
80.3 - Beneficiary Other Insurance Information (HUBO) Maintenance Transaction Error Codes (Rev. 4009, Issued: 03-23-18, Effective: 04-23-18, Implementation: 04-23-18) Effective January 2, 2007, the CWF shall accept and process a HUBO transaction that either updates an existing Beneficiary Other Insurance (BOI) auxiliary record or adds a new BOI auxiliary record occurrence. If the CWF receives an incoming HUBO transaction whose COBA identification number (ID) and ‘beneficiary supplemental eligibility-from date’ (CCYYMMDD) match the equivalent elements within an existing BOI auxiliary record, it shall overlay the existing record with the incoming record. However, if the CWF receives an incoming HUBO transaction whereby the COBA ID and ‘beneficiary supplemental-from date’ do not match the equivalent elements within an existing BOI auxiliary record, it shall create a new BOI auxiliary record occurrence. For purposes of applying COBA eligibility files to the BOI auxiliary file, the CWF maintainer shall redefine Action Type ‘0- Add’ as ‘1-Add/Update.’ For purposes of applying COBA eligibility files to the BOI auxiliary record, the CWF shall now accept and process only two Action Types—‘1 - Add/Update’ and ‘2 – Delete’—from the BCRC as part of the COBA crossover process. The CWF shall continue to apply the applicable ‘BO’ edits that would relate to add/update or delete actions accomplished via the HUBO transaction.
Medicare Claims Processing Manual (Pub. 100-04), Ch. 27 § 80.3: Beneficiary Other Insurance Information (HUBO) Maintenance | Justis AI