Common use of Business Rules for Processing Clause in Contracts

Business Rules for Processing. ‌ 1. The monthly Input File submitted by the partner is a full-file-replacement file. The partner’s entire file (participation record) of enrollees must be submitted each month on this file, and it must include any corrections to errors found in the previous month’s file. Each month’s Input File will fully replace the previous month’s Input File. 2. Data-sharing partners are required to continue to include coverage records for 3 years after the termination date of the coverage. 3. A Response File will be returned to each partner, containing a response record for each input record received. This Response File will also contain a response record for each deleted record (i.e., records that were in the previous Input File that are not in the current Input File). The disposition of the input record will be provided on its corresponding response record, including whether the record was accepted. 4. The BCRC will attempt to create one record for each enrollee record received. 5. The BCRC will not send incomplete records to the MBD. Consequently, incomplete drug records will also not get sent to the Transaction Facilitation Contractor (ADAPs and SPAPs only). 6. On all ADAP input files, the fields required are Medicare ID (HICN or MBI) or SSN, Surname, First Initial, Date of Birth, Sex Code, Network Indicator, Effective Date, Termination Date, Coverage Type Indicator, Insurance Type Indicator, and ADAP ID (in both the Header and Trailer). 7. If a new Input File is received by the BCRC, it is compared with the previously submitted Input File. If it is detected that processing the new Input File will delete at least 30% of the records that were accepted in the previous submission, a “threshold error” will be generated and the file will not be processed without additional confirmation from the data-sharing partner. The ADAP will be asked to verify the high number of delete records in the current submission. 8. LIS information will be returned for all qualified ADAP records. Qualified ADAPs are indicated by an Insurance Types of S. 9. Non-qualified ADAP records will not receive LIS information. Non-qualified ADAPS are indicated by an Insurance Type of N. 10. Responses will be returned with enrollment and LIS information regardless of whether this information has changed since the last submission. 11. If the record cannot be matched in the MBD, the BCRC will return a disposition code of “51”: Not Found, without any enrollment or LIS data, even if that record is matched on the BCRC’s database. 12. When a Response File is created that includes records that have responses still pending from the MBD, those records will be returned with the enrollment and LIS information, but with a disposition code of “50.” Chapter 4: Working with the Data‌

Appears in 2 contracts

Samples: Data Sharing Agreement, Data Sharing Agreement

AutoNDA by SimpleDocs

Business Rules for Processing. ‌ 1. The monthly Input File submitted by the partner is a full-file-replacement file. The partner’s entire file (participation record) of enrollees must be submitted each month on this file, and it must include any corrections to errors found in the previous month’s file. Each month’s Input File will fully replace the previous month’s Input File. 2. Data-sharing partners are required to continue to include coverage records for 3 years after the termination date of the coverage. 3. A Response File will be returned to each partner, containing a response record for each input record received. This Response File will also contain a response record for each deleted record (i.e., records that were in the previous Input File that are not in the current Input File). The disposition of the input record will be provided on its corresponding response record, including whether the record was accepted. 4. The BCRC will attempt to create one record for each enrollee record received. 5. The BCRC will not send incomplete records to the MBD. Consequently, incomplete drug records will also not get sent to the Transaction Facilitation Contractor (ADAPs and SPAPs only). 6. On all ADAP input files, the fields required are Medicare ID (HICN or MBI) or SSN, Surname, First Initial, Date of Birth, Sex Code, Network Indicator, Effective Date, Termination Date, Coverage Type Indicator, Insurance Type Indicator, and ADAP ID (in both the Header and Trailer). 7. If a new Input File is received by the BCRC, it is compared with the previously submitted Input File. If it is detected that processing the new Input File will delete at least 30% of the records that were accepted in the previous submission, a “threshold error” will be generated and the file will not be processed without additional confirmation from the data-sharing partner. The ADAP will be asked to verify the high number of delete records in the current submission. 8. LIS information will be returned for all qualified ADAP records. Qualified ADAPs are indicated by an Insurance Types of S. 9. Non-qualified ADAP records will not receive LIS information. Non-qualified ADAPS are indicated by an Insurance Type of N. 10. Responses will be returned with enrollment and LIS information regardless of whether this information has changed since the last submission. 11. If the record cannot be matched in the MBD, the BCRC will return a disposition code of “51”: Not Found, without any enrollment or LIS data, even if that record is matched on the BCRC’s database. 12. When a Response File is created that includes records that have responses still pending from the MBD, those records will be returned with the enrollment and LIS information, but with a disposition code of “50.” Chapter 4: Working with the Data‌Data ‌

Appears in 2 contracts

Samples: Data Sharing Agreement, Data Sharing Agreement

AutoNDA by SimpleDocs

Business Rules for Processing. ‌ 1. The monthly Input File submitted by the partner is a full-file-replacement file. The partner’s entire file (participation record) of enrollees must be submitted each month on this file, and it must include any corrections to errors found in the previous month’s file. Each month’s Input File will fully replace the previous month’s Input File. 2. Data-sharing partners are required to continue to include coverage records for 3 years after the termination date of the coverage. 3. A Response File will be returned to each partner, containing a response record for each input record received. This Response File will also contain a response record for each deleted record (i.e., records that were in the previous Input File that are not in the current Input File). The disposition of the input record will be provided on its corresponding response record, including whether the record was accepted. 4. The BCRC will attempt to create one record for each enrollee record received. 5. The BCRC will not send incomplete records to the MBD. Consequently, incomplete drug records will also not get sent to the Transaction Facilitation Contractor (ADAPs and SPAPs only). 6. On all ADAP partner input files, the fields required are Medicare ID (HICN or MBI) or SSN, Surname, First Initial, Date of Birth, Sex Code, Network Indicator, Effective Date, Termination Date, Coverage Type Indicator, Insurance Type Indicator, and ADAP SPAP ID (in both the Header and Trailer). 7. If a new Input File is received by the BCRC, it is compared with the previously submitted Input File. If it is detected that processing the new Input File will delete at least 30% of the records that were accepted in the previous submission, a “threshold error” will be generated and the file will not be processed without additional confirmation from the data-sharing partner. The ADAP partner will be asked to verify the high number of delete records in the current submission. 8. LIS information will be returned for all qualified ADAP SPAP records. Qualified ADAPs SPAPs are indicated by an Insurance Types of S.Q. 9. Non-qualified ADAP SPAP records will not receive LIS information. Non-qualified ADAPS SPAPS are indicated by an Insurance Type of N. 10. Responses will be returned with enrollment and LIS information regardless of whether this information has changed since the last submission. 11. If the record cannot be matched in the MBD, the BCRC will return a disposition code of “51”: Not Found, without any enrollment or LIS data, even if that record is matched on the BCRC’s database. 12. When a Response File is created that includes records that have responses still pending from the MBD, those records will be returned with the enrollment and LIS information, but with a disposition code of “50.” Chapter 4: Working with the Data‌

Appears in 2 contracts

Samples: Data Sharing Agreement, Data Sharing Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!