Dental Injury Dental Emergency Treatment
Dental Injury Dental Emergency Treatment Sample Clauses
Related to Dental Injury Dental Emergency Treatment
Emergency Medical Treatment I grant the Releasees permission to authorize emergency medical treatment as they deem appropriate, and agree that such action by the Releasees shall be subject to the terms of this Agreement. I understand and agree that the Releasees assume no responsibility for any injury or damage that might result from such emergency medical treatment.
Musculoskeletal Injury Prevention and Control The hospital in consultation with the Joint Health and Safety Committee (JHSC) shall develop, establish and put into effect, musculoskeletal prevention and control measures, procedures, practices and training for the health and safety of employees.
Emergency Transition Registry Operator agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <xxxx://xxx.xxxxx.xxx/en/resources/registries/transition-‐processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such Emergency Operator. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.
Contingent Emergency Response 1. In order to ensure the proper implementation of contingent emergency response activities under Part 4 of the Project (“Contingent Emergency Response Part”), the Recipient shall ensure that: (a) a manual (“CERC Manual”) is prepared and adopted in form and substance acceptable to the Association, which shall set forth detailed implementation arrangements for the Contingent Emergency Response Part, including: (i) any structures or institutional arrangements for coordinating and implementing the Contingent Emergency Response Part;
Medical Treatment Undersigned understands that the Released Parties do not have medical personnel available at the location of the activities. Undersigned hereby grants the Released Parties permission to administer first aid or to authorize emergency medical treatment, if necessary. Undersigned understands and agrees that any such action by the Released Parties shall be subject to the terms of this agreement and release, including any liability arising from the negligence of the Released Parties when administering first aid or authorizing others to do so. Undersigned understands and agrees that the Released Parties do not assume responsibility for any injury or damage which might arise out of or in connection with such authorized emergency medical treatment.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.
Iran Divestment Act Certification The Contractor certifies that, if it submitted a successful bid for this contract, then as of the date it submitted the bid, the Contractor was not identified on the Iran List. If it did not submit a bid for this contract, the Contractor certifies that as of the date that this contract is entered into, the Contractor is not identified on the Iran List. It is a material breach of contract for the Contractor to be identified on the Iran List during the term of this contract or to utilize on this contract any subcontractor that is identified on the Iran List. In this Iran Divestment Act Certification section -- “Contractor” means the person entering into this contract with the City of Durham; and “Iran List” means the Final Divestment List – Iran, the Parent and Subsidiary Guidance– Iran list, and all other lists issued from time to time by the N.C. State Treasurer to comply with G. S. 147-86.58 of the N.C. Iran Divestment Act.
Completion of Concrete Pours and Emergency Work (a) Except as provided in this sub-clause an Employee shall nor work or be required to work in the rain. (b) Employees shall not be required to start a concrete pour in Inclement Weather. (c) Where a concrete pour has been commenced prior to the commencement of a period of Inclement Weather Employees may be required to complete such concrete pour to a practical stage and for such work shall be paid at the rate of double time calculated to the next hour, and in the case of wet weather shall be provided with adequate wet weather gear. (d) If an Employee’s clothes become wet as a result of working in the rain during a concrete pour the Employee shall, unless the Employee has a change of dry working clothes available, be allowed to go home without loss of pay. (e) The provisions of clauses 32.7(c) and 32.7(d) hereof shall also apply in the case of emergency work where the Employees concerned and their delegates agree that the work is of an emergency nature and can start and/or proceed.
Substance Abuse Treatment Information Substance abuse treatment information shall be maintained in compliance with 42 C.F.R. Part 2 if the Party or subcontractor(s) are Part 2 covered programs, or if substance abuse treatment information is received from a Part 2 covered program by the Party or subcontractor(s).
Emergency Thresholds The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.
