Passcode Requirements i. Must be at least eight (8) characters long.
Passcode Requirements Sample Clauses
Related to Passcode Requirements
Interface Requirements 9.3.1 BellSouth shall offer LIDB in accordance with the requirements of this subsection.
DBE Requirements A. Notice is hereby given to the CONSULTANT and any SUB-CONSULTANT, and both agree, that failure to carry out the requirements set forth in 49 CFR Sec. 26.13(b) shall constitute a breach of this Contract and, after notification and failure to promptly cure such breach, may result in termination of this Contract or such remedy as INDOT deems appropriate. The referenced section requires the following assurance to be included in all subsequent contracts between the CONSULTANT and any SUB-CONSULTANT: The CONSULTANT, sub recipient or SUB-CONSULTANT shall not discriminate on the basis of race, color, national origin, or sex in the performance of this Contract. The CONSULTANT shall carry out applicable requirements of 49 CFR Part 26 in the award and administration of DOT-assisted contracts. Failure by the CONSULTANT to carry out these requirements is a material breach of this Contract, which may result in the termination of this Contract or such other remedy, as INDOT, as the recipient, deems appropriate.
LABOR CODE REQUIREMENTS Provided that the Contract Price is more than $1,000, and the Work is a “public works” under the Labor Code, the parties agree as follows: The Work is subject to compliance monitoring and enforcement by the Department of Industrial Relations.
Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
VEHICLE REQUIREMENTS The following shall be considered minimum Vehicle requirements. The Authorized User shall include supplemental required specifications for Vehicles specified in a Mini-Bid. Unless otherwise indicated, all items specified which are listed on the OEM Pricelist as standard or optional equipment shall be factory installed and operative. Vehicles delivered to an Authorized User in a condition considered to be below retail customer acceptance levels will not be accepted. Items which determine this acceptance level shall include, but not be limited to, the general appearance of the interior and exterior of the vehicle for completeness and quality of workmanship, lubrication and fluid levels, with any leaks corrected, mechanical operation of the vehicle and all electrical components operational. Product specified to be furnished and installed which is not available through the OEM shall conform to the standards known to that particular industry, both product and installation.
Contractor Requirements The Contractor shall—
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.
HIPAA Requirements The Parties agree that the provisions under HIPAA Rules that are required by law to be incorporated into this Amendment are hereby incorporated into this Agreement.
Subcontractor Requirements The Supplier must ensure that any subcontract entered into for the purpose of this Agreement contains an equivalent clause granting the rights specified in this clause.
