Adds. Once a Medicare ID (HICN or MBI) is identified, the incoming record is compared to the CMS database to attempt to match it against previously submitted records. The initial matching criteria data set consists of the Medicare ID, Effective Date, Insurance Type, and a PAP ID. If a match of these fields cannot be made on the CMS database, the incoming record is considered an Add – a new record.
Adds. “Adds” means additions to Services.
Adds. Using the beneficiary's HICN, the incoming record is compared to the database to attempt to match on previously submitted records. The data elements comprising the set of initial matching criteria consist of the HICN, Effective Date, Insurance Type, and PAP ID. If a match of these fields cannot be made on the existing database, the incoming record is considered an "add" (a new record). If incoming field matches indicate a record is not an Add, additional fields are compared to determine if the incoming record should be considered an update. These fields include Toll-Free Number, Coverage Type, and Termination Date. If any of these fields have changed from the previous month's submission the record is considered an update. If the incoming record matches exactly on these additional fields, no action is taken and the PAP does not receive a response for this record. Any records previously added, but not now included in the PAP's current Input File submission will be deleted from the COBC‟s PAP records. Note: During the course of production data exchange involving current PAP clients this delete process should only be used to remove a record that never should have been sent to CMS, one that should not have been added to our database originally. A beneficiary record that has been correctly added is required to be kept active for the entire period that the Medicare beneficiary continues to be receiving services from the PAP. Periods of "continuous enrollment" may include PAP disenrollment/re-enrollment activity that doesn't result in actual termination from PAP services (for example, periodic automatic reenrollment). Once a Medicare beneficiary's PAP enrollment ends and after the PAP sends CMS an accepted "Termination Date" in a subsequent Input File (see the Input File, Field #8), we do not require the PAP to continue to include that beneficiary's information on later Input Files. However, we recommend that a PAP consider continuing to include former PAP enrollee data on later Input Files for a period of time determined to be of value to the PAP. Previous PAP enrollee data that is omitted from a later Input File will be a "Delete," and will cause all evidence of PAP enrollment to disappear from the beneficiary's record on the CMS database. Because such deleted data cannot be recovered there will no longer be any record of PAP – CMS data sharing at CMS. If a PAP determines there is value in keeping the record of a Medicare beneficiary's PAP activity available on ...
Adds. Using the beneficiary’s HICN, the incoming record is compared to the database to attempt to match on previously submitted records. The data elements comprising the set of initial matching criteria consist of the Medicare ID (HICN or MBI), Effective Date, Insurance Type, and PAP ID. If a match of these fields cannot be made on the existing database, the incoming record is considered an "add" (a new record).
Adds. A Flight Attendant may “Add” trip(s) to her line from Open Time, as provided in Paragraph G. above. A selected trip must not conflict with any existing assignments and all FAR and contractual legalities must be observed.
Adds. Adds are permitted in form of a Service Order, each Subscribing Entity’s Service Order will carry its own selected Minimum Payment Period.
Adds. Attachment 1: Revisions to Category 1.2, Volume 2, Response to Unique Subcategory Requirements, (325 pages) • Attachment 2: Revisions to Category 1.3, Volume 2, Response to Unique Subcategory Requirements, (165 pages) • Attachment 3: Revisions to IFB-STPD 12-001-A, Part 1 - General Instructions. (102 pages) • Attachment 4: Revisions to IFB-STPD 12-001-A, Statement of Work - Business Requirements, (100 pages)
Adds. During the 50 days after the end of the FRD Approval Period (or, if earlier, the date on which Newco approves the last Detailed FRD) (the “AD&D Approval Period”), Xxxxx Systems shall develop, for Newco’s review and approval, which review and approval shall not be unreasonably withheld, an analysis and design documents (“AD&D”) for each Detailed FRD that describes the specific design requirements for the Legacy Customizations and any other activities required by such Detailed FRD. Xxxxx Systems shall submit the AD&Ds to Newco as and when they are completed. As soon as reasonably possible (but not later than ten (10) days) after the delivery date, Newco shall complete its review of the submitted AD&D and give written notice to Xxxxx Systems either (i) approving the AD&D or (ii) withholding such approval, which notice shall specify in all reasonable detail Newco’s reasons for withholding such approval. The description of any capabilities, features and functionality of the Legacy Customizations as well as any associated business rules, inputs and outputs for and from the Legacy Customizations contained in each AD&D approved by the Parties will reflect the Parties’ mutual interpretation of the scope of the VRS Project with respect to the applicable Detailed FRD. An AD&D may not expand or contract the unambiguous scope of the VRS Project set forth in the applicable Detailed FRD. For example, if a particular function is referred to in the Detailed FRD, but omitted from the applicable AD&D, the function shall remain in the scope of the VRS Project unless a Change Order removes the function from the Detailed FRD. However, the description of any capabilities, features and functionality of the Legacy Customizations as well as any associated business rules, inputs and outputs for and from the Legacy Customizations contained in an AD&D will control the interpretation of the Detailed FRD with respect to the implementation of such capability, feature or function unless the details in the AD&D clearly and unambiguously contradict the Detailed FRD. Xxxxx Systems shall not be required to provide the VRS Project Proposal (defined in Section 3.1) or begin coding for any Legacy Customization before receiving Newco’s approval of the AD&Ds. While developing the AD&Ds, Xxxxx Systems will provide periodic progress reports, not less frequently than every thirty (30) days, which reports will include Xxxxx Systems’ then-current estimate of the level of effort required and schedule fo...
Adds. If Spectra fails to perform its undertakings, the customer is also permitted to suspend the performance of its undertakings.
Adds. Install additional telephones/cards to telephone systems and/or associated telephone equipment.
