Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.
Sxxxxxxx-Xxxxx Compliance As soon as it is legally required to do so, the Company shall take all actions necessary to obtain and thereafter maintain material compliance with each applicable provision of the Sxxxxxxx-Xxxxx Act of 2002 and the rules and regulations promulgated thereunder and related or similar rules and regulations promulgated by any other governmental or self-regulatory entity or agency with jurisdiction over the Company.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Xxxxxxxx-Xxxxx Compliance As soon as it is legally required to do so, the Company shall take all actions necessary to obtain and thereafter maintain material compliance with each applicable provision of the Xxxxxxxx-Xxxxx Act of 2002 and the rules and regulations promulgated thereunder and related or similar rules and regulations promulgated by any other governmental or self-regulatory entity or agency with jurisdiction over the Company.
W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.
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.
Student Evaluation a. The President of the College or the President’s designee shall be responsible for administering the student evaluation process.
b. Student evaluation packets for each class containing instruments and instructions shall be distributed to each faculty member by the first week of December during the fall semester and by the last week in April during the spring semester.
c. It is expressly agreed that the faculty member being evaluated shall not be present in the classroom when the student evaluation is being administered and that all instruction to students with regard to such student evaluation shall be included in writing on the instrument, provided further that the designated unit or non-unit professional shall return the student evaluation directly to the President of the College or the President’s designee. The administering of the student evaluation shall be the responsibility of the President of the College or the President’s designee who shall determine who among unit or non-unit professionals shall administer such student evaluation. Student evaluations shall be valid only if signed by the student; provided, however, that faculty members shall not be entitled to the identity of the student responding unless such student evaluation is used as a basis for dismissal or other disciplinary action and such will be communicated to the students.
d. The data from the student evaluation shall be tabulated and copies sent to the President of the College or the President’s designee. The raw data shall be retained by the College for a period of one (1) year during which time the faculty member shall have access thereto upon written request.
e. The President of the College or the President’s designee shall review the tabulated data and shall forward a data summary to the faculty member by January 23 for the fall semester and by June 15 for the spring semester.
f. The faculty member shall have seven (7) working days in which to respond to such data.
Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”
Xxxxxxxx-Xxxxx Act Requirements To the extent any documents are required to be filed or any certification is required to be made with respect to the Issuer or the Notes pursuant to the Xxxxxxxx-Xxxxx Act, the Issuer hereby authorizes the Servicer and the Seller, or either of them, to prepare, sign, certify and file any such documents or certifications on behalf of the Issuer.
Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.
