New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:
Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.
HOT LIST PRICING At any time during this Contract, Supplier may offer a specific selection of Equipment, Products, or Services at discounts greater than those listed in the Contract. When Supplier determines it will offer Hot List Pricing, it must be submitted electronically to Sourcewell in a line-item format. Equipment, Products, or Services may be added or removed from the Hot List at any time through a Sourcewell Price and Product Change Form as defined in Article 4 below. Hot List program and pricing may also be used to discount and liquidate close-out and discontinued Equipment and Products as long as those close-out and discontinued items are clearly identified as such. Current ordering process and administrative fees apply. Hot List Pricing must be published and made available to all Participating Entities.
Information Correct and Current No information, report, Advance Request, financial statement, exhibit or schedule furnished, by or on behalf of Borrower to Lender in connection with any Loan Document or included therein or delivered pursuant thereto contained, contains or will contain any material misstatement of fact or omitted, omits or will omit to state any material fact necessary to make the statements therein, in the light of the circumstances under which they were, are or will be made, not misleading at the time such statement was made or deemed made. Additionally, any and all financial or business projections provided by Borrower to Lender shall be (i) provided in good faith and based on the most current data and information available to Borrower, and (ii) the most current of such projections approved by Borrower’s Board of Directors.
Project Number The project number has been assigned by the Commission as the unique identifier for your project, and it cannot be changed. The project number should appear on each page of the grant agreement preparation documents to prevent errors during its handling.
FALSE STATEMENTS CONCERNING HIGHWAY PROJECTS T h i s p r o v i s i o n i s applicable to all Federal-aid construction contracts and to all related subcontracts. In order to assure high quality and durable construction in conformity with approved plans and specifications and a high degree of reliability on statements and representations made by engineers, contractors, suppliers, and workers on Federal- aid highway projects, it is essential that all persons concerned with the project perform their functions as carefully, thoroughly, and honestly as possible. Willful falsification, distortion, or misrepresentation with respect to any facts related to the project is a violation of Federal law. To prevent any misunderstanding regarding the seriousness of these and similar acts, Form FHWA-1022 shall be posted on each Federal-aid highway project (23 CFR 635) in one or more places where it is readily available to all persons concerned with the project: 18 U.S.C. 1020 reads as follows: "Whoever, being an officer, agent, or employee of the United States, or of any State or Territory, or whoever, whether a person, association, firm, or corporation, knowingly makes any false statement, false representation, or false report as to the character, quality, quantity, or cost of the material used or to be used, or the quantity or quality of the work performed or to be performed, or the cost thereof in connection with the submission of plans, maps, specifications, contracts, or costs of construction on any highway or related project submitted for approval to the Secretary of Transportation; or Whoever knowingly makes any false statement, false representation, false report or false claim with respect to the character, quality, quantity, or cost of any work performed or to be performed, or materials furnished or to be furnished, in connection with the construction of any highway or related project approved by the Secretary of Transportation; or Whoever knowingly makes any false statement or false representation as to material fact in any statement, certificate, or report submitted pursuant to provisions of the Federal-aid Roads Act approved July 1, 1916, (39 Stat. 355), as amended and supplemented; Shall be fined under this title or imprisoned not more than 5 years or both."
TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order.
White Pages Listings 5.1 BellSouth shall provide <<customer_name>> and their customers access to white pages directory listings under the following terms:
Most-Favoured-Nation Treatment 1. Each Party shall accord to investors of the other Party treatment no less favourable than that it accords, in like circumstances, to investors of any third State with respect to the establishment, acquisition, expansion, management, conduct, operation, and sale or other disposition of investments in its territory. 2. Each Party shall accord to investments of investors of the other Party treatment no less favourable than that it accords, in like circumstances, to investments in its territory of investors of any third State with respect to the establishment, acquisition, expansion, management, conduct, operation, and sale or other disposition of investments (13). 3. Notwithstanding paragraphs 1 and 2, the Parties reserve the right to adopt or maintain any measure that accords differential treatment: (a) to socially or economically disadvantaged minorities and ethnic groups (14); or (b) involving cultural industries related to the production of books, magazines, periodical publications, or printed or electronic newspapers and music scores. 4. The treatment and protection as mentioned in paragraphs 1 to 2 of this Article shall not include any preferential treament accorded by the other Party to investments of investors of any third State based on free trade agreement, free trade zone, custom union, economic union, or agreement relating to avoidance of double taxation or for facilitating frontier trade.
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
