Computer Program Requirements. The computer program requirements shall be the same as that specified in Subsection 105.15 subpart 1.e. of these Special Provisions.
Computer Program Requirements Sample Clauses
Related to Computer Program Requirements
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
PayPal's Seller Protection Program What’s eligible
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.
PayPal’s Buyer Protection Program When you buy something from a seller who accepts PayPal, you may be eligible for a refund under PayPal’s Buyer Protection program. When applicable, PayPal’s Buyer Protection program entitles you to reimbursement for the full purchase price of the item plus the original shipping costs you paid, if any. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Buyer Protection program. PayPal’s original determination is considered final, but you may be able to file an appeal of the decision with PayPal if you have new or compelling information not available at the time of the original determination or you believe there was an error in the decision-making process. The program terms and conditions are set out in PayPal’s Buyer Protection program page and form part of this user agreement.
Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.
Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.
Mentor Program a. Each new Bargaining Unit Member (first year employee) shall be assigned a mentor. An exception may be made, as determined by the Superintendent, for new part-time Bargaining unit Members of whom have prior service in the same program operated by the Board. The mentor shall assist the new Bargaining Unit Member in general teaching procedures, techniques, classroom planning and organization, school functions and regulations and other areas of professional growth and development. The Association President in collaboration with the Lead Mentor/Resident Educator Coordinator and appropriate Directors shall submit nominations of three (3) qualified staff members to the Superintendent, after obtaining the candidates’ permission. The Superintendent may elect to nominate one of the candidates to the Board of Education for assignment, or ask the Association President and Lead Mentor/Resident Educator Coordinator for additional nominations. b. No mentor shall be assigned more than one new Bargaining Unit Member per year. The mentor shall not be involved in any way in the formal evaluation of the new Bargaining Unit Member, but shall confer with the assigned Supervisor on the strengths and weaknesses of the new unit member and his or her overall performance and progress. In order to be assigned, mentors must possess the following qualifications: i. At least two (2) years of successful teaching experience at Tolles. ii. A variety of teaching experience. iii. An ability and willingness to help improve another teacher. c. Mentors shall attend one or two (2) training seminars held outside the regular workday. The Association President in collaboration with the Lead Mentor/Resident Educator Coordinator and appropriate Directors will draft a list of tasks which mentors are to perform. d. Mentor teachers shall certify that they have spent a minimum of 15 hours during the school year in mentor training and working with their assigned new Bargaining Unit Member. The new Bargaining Unit Member may make written application to the Superintendent for up to 15 hours additional mentor service. The mentor teacher, the new Bargaining Unit Member, and the Superintendent or Superintendent’s designee, will meet to discuss a plan of action for additional hours requested. Mentor teachers shall be paid for the documented work hours at the hourly rate of $30. The payment shall be in a one-time lump sum at the end of the school year. e. If there are teachers who are new to the District, the Lead Mentor will receive two (2) days extended time to work with new teachers and the administration before the regular instructional year for the purpose of training new staff members in the successful use of the teacher handbook, school regulations, and operational procedures.
Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.
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.
