Food Service Waste Reduction Requirements Contractor shall comply with the Food Service Waste Reduction Ordinance, as set forth in San Francisco Environment Code Chapter 16, including but not limited to the remedies for noncompliance provided therein.
GRADUATION REQUIREMENTS I understand that in order to graduate from the program and to receive a certificate of completion, diploma or degree I must successfully complete the required number of scheduled clock hours as specified in the catalog and on the Enrollment Agreement, pass all written and practical examinations with a minimum score of 80%, and complete all required clinical hours and satisfy all financial obligations to the College.
CERTIFICATION REGARDING DRUG-FREE WORKPLACE REQUIREMENTS 1. The Contractor certifies that it will provide a drug-free workplace by:
a. Publishing a statement notifying employees that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Contractor’s workplace and specifying the actions that will be taken against employees for violation of such prohibition;
Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave.
2. If the event necessitating the Family Leave becomes known to the employee less than thirty (30) calendar days prior to the employee's need for Family Leave, the employee must provide as much notice as possible. In no case shall the employee provide notice later than five (5) calendar days after he or she learns of the need for Family Leave.
3. For foreseeable leave due to a qualifying exigency, an employee must provide notice of the need for leave as soon as practicable, regardless of how far in advance such leave is foreseeable.
4. When the Family Leave is for the purpose of the scheduled medical treatment or planned medical care of a child, parent, spouse or registered domestic partner, the employee shall, to the extent practicable, schedule treatment and/or care in a way that minimizes disruption to agency/department operations.
Certification Requirements The hospice program certifies and attaches hereto documentation that:
(a) it is Medicare approved and meets all Medicare conditions of participation (42 CFR 418); and
(b) is licensed pursuant to any applicable state or local law.
Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.
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.
Notification Requirement Through and up to the conclusion of the Non-Competition Period, Executive shall give notice to the Company of each new business activity he plans to undertake, at least seven (7) days prior to beginning any such activity. Such notice shall state the name and address of the Person for whom such activity is undertaken and the nature of Executive’s business relationship(s) and position(s) with such Person.
Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED) 200. OPERATIONAL AGREEMENT.
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
