File Level Editing Sample Clauses
The File Level Editing clause grants specific rights or permissions to modify, update, or otherwise alter individual files within a larger system or project. In practice, this means that authorized users can make changes to particular files without affecting the entire project or repository, allowing for targeted updates or corrections. This clause is essential for maintaining version control and ensuring that edits are precise and limited in scope, thereby reducing the risk of unintended changes to unrelated parts of the project.
File Level Editing. Upon receipt of the PAP’s Input File, the BCRC first performs high-level file edits to verify the format and validity of the Input File, including Header and Trailer data and record counts. The new Input File 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 PAP. The PAP will be asked to verify the high number of delete records in the current submission. With a full file replacement, the method for deleting enrollee records is to not include previously submitted enrollee records in the current Input File. (Note: PAPs are required to continue to include coverage records for 3 years after the termination date of the coverage.) The Input File is then processed at the record level. The system initially attempts to use an SSN to match to a Medicare ID (HICN or MBI) if a Medicare ID is not submitted on the input file. The system will also determine if an incoming enrollee record is an Add, Update, or Delete, or if no action will be taken.
File Level Editing. Upon receipt of the ADAP’s Input File, the BCRC first performs high-level file edits to verify the format and validity of the Input File, including Header and Trailer data and record counts. The new Input File 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 ADAP. The ADAP will be asked to verify the high number of delete records in the current submission. With a full file replacement, the method for deleting enrollee records is to not include previously submitted enrollee records in the current Input File. (Note: ADAPs are required to continue to include coverage records for 3 years after the termination date of the coverage.) The Input File is then processed at the record level. The system initially attempts to use an SSN to match to a Medicare ID (HICN or MBI) if a Medicare ID is not submitted on the input file. The system will also determine if an incoming enrollee record is an Add, Update, or Delete, or if no action will be taken.
File Level Editing. Upon the BCRC’s receipt of the SPAP Input File, high-level file edits are performed to verify the Input File’s format and validity. Header and Trailer data and record counts are verified. The size of the SPAP Input File (number of records contained in the file) is compared to the size of the previous monthly file submitted. If the new file size is less than 70% of the previous month’s file, a “severe error” will be produced, processing of the current Input File will be placed on hold, and the SPAP partner will be notified. Since the method for deleting existing enrollees in full file replacement processing is to not include them in a newly submitted file, if a new file is less than 70% of the size of the previous file the SPAP partner will be asked to verify what appear to be the high number of “delete” records in the new submission. The new Input File is then processed at the record level to determine if each incoming enrollee record is an add, update, or delete, or if no action will be taken. The system also initially attempts to convert any SSN to a Medicare ID (HICN or MBI) if a Medicare ID is not submitted on the input record.