Identification of Ill Employees Sample Clauses

Identification of Ill Employees. Employees affected by a communicable or life-threatening disease or illness may be identified through self-report, or on the basis of the District having a reasonable belief that a staff member is ill. Reasonable belief would exist in, but is not limited to, situations where the employee’s health is observed to be deteriorating to the point of interfering with the performance of his/her duties, the employee displays persistent physical symptoms of illness, where the District becomes aware of a diagnosis of such an illness or disease, or where there is other reasonable evidence of the existence of such disease. If a supervisor has been informed or has reasonable cause to believe that an employee is affected by a communicable or life-threatening disease or illness, the supervisor will immediately notify the Assistant Superintendent of Human Resources. The Assistant Superintendent of Human Resources or his/her designee may confer with, but not limited to, the supervisor, the Executive Director of Instruction for that school, the staff member, and the Superintendent of Schools for determination of fitness as provided in Section D below.
AutoNDA by SimpleDocs

Related to Identification of Ill Employees

  • Identification When performing work on District property, Contractor shall be in appropriate work attire (or uniform, if applicable) at all times. If Contractor does not have a specific uniform, then Contractor shall provide identification tags and/or any other mechanism the District in its sole discretion determines is required to easily identify Contractor. Contractor and its employees shall (i) display on their clothes the above-mentioned identifying information and (ii) carry photo identification and present it to any District personnel upon request. If Contractor cannot produce such identification or if the identification is unacceptable to District, District may provide at its sole discretion, District-produced identification tags to Contractor, costs to be borne by Contractor.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Identification Cards Identification (“ID”) cards are issued by Us for identification purposes only. Possession of any ID card confers no right to services or benefits under this Contract. To be entitled to such services or benefits, Your Premiums must be paid in full at the time that the services are sought to be received.

  • Employer Identification Number The Administrator shall have and use its own Employer Identification Number for purposes of calculating payroll tax withholdings and providing reports state and federal tax authorities.

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • T1 IDENTIFICATION PROCEDURES During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.

Time is Money Join Law Insider Premium to draft better contracts faster.