PAP File Processing Sample Clauses

PAP File Processing. On a monthly basis, PAPs will transmit full file submissions in the format specified in this agreement. Full file processing requires the PAP to submit a complete file of enrollees every month. Each month‟s transmitted file will fully replace the previous month‟s file. Field 14 in the PAP Input File is labeled "Telephone Contact Number." This is the field that the PAP will use to enter the telephone number to be called if a PAP enrollee's Medicare Part D Plan wishes to contact the PAP for information about medications the enrollee/beneficiary is being provided. This contact number should be one that can take incoming calls from PDP administrative or technical staff, and provide the PDP with information about the drug(s) provided by the PAP and about any out-of-pocket payments made by the beneficiary. This is a required field. Upon the COBC's receipt of the PAP Input File, high-level file edits are performed to verify the format and validity of the Input File. High-level editing verifies Header and Trailer data and record counts. The size of the PAP Input File (the number of records contained in the file) is compared to the size of the previous monthly file submitted. The method for deleting enrollees in full file replacement processing is to not include enrollee files previously submitted. If the current file size is less then 70% of the previous month's file, the current Input File will be placed on hold and the PAP partner will be notified. The PAP partner will be asked to verify the high number of delete records in the current submission. The Input File is then processed at the record level to determine if an incoming enrollee record is an add, update, delete, or if no action will be taken on it. The system initially attempts to convert an SSN to a HICN if a HICN is not submitted on the input file. (The HICN – Health Insurance Claim Number – is the Medicare ID Number.) If a Medicare beneficiary is identified through an SSN and other data the beneficiary‟s HICN will be returned to the PAP, and the PAP is then required to use the HICN in any future data exchanges with the COBC. The COBC will only create a response record if a record has been added, or an existing record has been updated or deleted. An input record that has already been applied in a previous full file submission and is contained in the current submission unchanged (i.e., with no updates or errors) will not generate a response record. However, the COBC and CMS work to ensure that PAPs will ...
AutoNDA by SimpleDocs
PAP File Processing. ‌ On a monthly basis, PAPs will transmit full file submissions in the format specified in this agreement. Full file processing requires the PAP to submit a complete file of enrollees every month. Each month’s transmitted file will fully replace the previous month’s file.

Related to PAP File Processing

  • Sub-processing 11.1 The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub- processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement. 11.2 The prior written contract between the data importer and the sub-processor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the sub-processor shall be limited to its own processing operations under the Clauses. 11.3 The provisions relating to data protection aspects for sub-processing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established, namely ........................................ 11.4 The data exporter shall keep a list of sub-processing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5(j), which shall be updated at least once a year. The list shall be available to the data exporter’s data protection supervisory authority.

  • Data Collection, Processing and Usage The Company collects, processes and uses the International Participant’s personal data, including the International Participant’s name, home address, email address, and telephone number, date of birth, social insurance number or other identification number, salary, citizenship, job title, any shares of Common Stock or directorships held in the Company, and details of all Equity Awards or any other equity compensation awards granted, canceled, exercised, vested, or outstanding in the International Participant’s favor, which the Company receives from the International Participant or the Employer. In granting the Equity Award under the Plan, the Company will collect the International Participant’s personal data for purposes of allocating shares of Common Stock and implementing, administering and managing the Plan. The Company’s legal basis for the collection, processing and usage of the International Participant’s personal data is the International Participant’s consent.

  • Grievance Processing Union stewards or Union officials shall be permitted to have time off without loss of pay for the investigation and processing of grievances and arbitrations. Requests for such time off shall be made in advance and shall not be unreasonably denied. The Union will furnish the Employer with a list of Union stewards and their jurisdictions. The Union shall delineate the jurisdiction of Union stewards so that no xxxxxxx need travel between work locations or sub-divisions thereof while investigating grievances. Grievants shall be permitted to have time off without loss of pay for processing their grievances through the contractual grievance procedure, except that for class action grievances no more than three (3) grievants shall be granted such leave.

  • Claims Processing BCBSM will process Provider's Clean Claims submitted in accordance with this Agreement in a timely fashion.

  • Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -­‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-­‐key cryptography, Symmetric-­‐key cryptography, Hash and Compression are those enumerated in XXX 0000, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-­‐free. The process to follow for the data file in original text format is: (1) The XML file of the deposit as described in Part A, Section 9, reference 1 of this Specification must be named as the containing file as specified in Section 5 but with the extension xml. (2) The data file(s) are aggregated in a tarball file named the same as (1) but with extension tar. (3) A compressed and encrypted OpenPGP Message is created using the tarball file as sole input. The suggested algorithm for compression is ZIP as per XXX 0000. The compressed data will be encrypted using the escrow agent’s public key. The suggested algorithms for Public-­‐key encryption are Elgamal and RSA as per XXX 0000. The suggested algorithms for Symmetric-­‐key encryption are TripleDES, AES128 and CAST5 as per XXX 0000. (4) The file may be split as necessary if, once compressed and encrypted, it is larger than the file size limit agreed with the escrow agent. Every part of a split file, or the whole file if not split, will be called a processed file in this section. (5) A digital signature file will be generated for every processed file using the Registry Operator’s private key. The digital signature file will be in binary OpenPGP format as per RFC 4880 Section 9, reference 3, and will not be compressed or encrypted. The suggested algorithms for Digital signatures are DSA and RSA as per XXX 0000. The suggested algorithm for Hashes in Digital signatures is SHA256. (6) The processed files and digital signature files will then be transferred to the Escrow Agent through secure electronic mechanisms, such as, SFTP, SCP, HTTPS file upload, etc. as agreed between the Escrow Agent and the Registry Operator. Non-­‐electronic delivery through a physical medium such as CD-­‐ROMs, DVD-­‐ROMs, or USB storage devices may be used if authorized by ICANN. (7) The Escrow Agent will then validate every (processed) transferred data file using the procedure described in Part A, Section 8 of this Specification.

  • Authorized Sub-processors Customer agrees that MailChimp may engage Sub-processors to process Customer Data on Customer's behalf. The Sub-processors currently engaged by MailChimp and authorized by Customer are listed in Annex A.

  • WARRANTY PROCEDURES You need proof of purchase for warranty service.

  • Transaction Processing All orders are subject to acceptance by us and by the Fund or its transfer agent, and become effective only upon confirmation by us. If required by law, each transaction shall be confirmed in writing on a fully disclosed basis and if confirmed by us, a copy of each confirmation shall be sent to you if you so request. All sales are made subject to receipt of shares by us from the Funds. We reserve the right in our discretion, without notice, to suspend the sale of shares of the Funds or withdraw the offering of shares of the Funds entirely. Orders will be effected at the price(s) next computed on the day they are received if, as set forth in the applicable Fund’s current Prospectus, the orders are received by us or an agent appointed by us or the Fund prior to the close of trading on the New York Stock Exchange, generally 4:00 p.m. eastern time (“Close of Trading”). Orders received after that time will be effected at the price(s) computed on the next business day. All orders must be accompanied by payment in U.S. Dollars. Orders payable by check must be drawn payable in U.S. Dollars on a U.S. bank, for the full amount of the investment. If you have entered into a FundSERV Agreement with us to effect transactions in Fund shares through FundSERV, you are hereby authorized to act on our behalf for the limited purpose of receiving purchase, exchange and redemption orders for Fund shares executed through FundSERV. You represent and warrant that all orders for the purchase, exchange or redemption of Fund shares transmitted to FundSERV for processing on or as of a given business day (Day 1) shall have been received by you prior to the Close of Trading on Day 1. Such orders shall receive the share price next calculated following the Close of Trading on Day 1 .You represent and warrant that orders received by you after the Close of Trading on Day 1 shall be treated by you and transmitted to FundSERV as if received on the next business day (Day 2). Such orders shall receive the share price next calculated following the Close of Trading on Day 2. You represent that you have systems in place reasonably designed to prevent orders received after the Close of Trading on Day 1 from being executed with orders received before the Close of Trading on Day 1.

  • Collection Procedures (a) On or before the Closing Date, the Seller and the Purchaser shall have established and shall maintain thereafter the system of collecting and processing Collections of Receivables in accordance with Section 2.02 of the Servicing Agreement. (b) The Seller shall cause all in-store payments to be (i) processed as soon as possible after such payments are received by the Seller but in no event later than the Business Day after such receipt, and (ii) delivered to the Servicer or, if a Daily Payment Event has occurred, deposited in the Collection Account no later than the second Business Day following the date of such receipt. (c) The Seller and the Purchaser shall deliver to the Servicer or, if a Daily Payment Event has occurred, deposit into the Collection Account all Recoveries received by it within two Business Days after the Date of Processing for such Recovery. (d) Any funds held by the Seller representing Collections of Receivables shall, until delivered to the Servicer or deposited in the Collection Account, be held in trust by the Seller on behalf of the Trustee as part of the Trust Estate. (e) The Seller hereby irrevocably waives any right to set off against, or otherwise deduct from, any Collections. (f) The Seller acknowledges that Seller shall not have any right, title or interest in and to any Trust Account.

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.

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