Fetal mortality Sample Clauses

Fetal mortality. While my results demonstrate that in utero exposure to tropical cyclones can affect mortal- ity post-birth, the relationship between exposure and fetal losses is more difficult to identify because I do not have information regarding fetal deaths as only live births are reported. To investigate the possibility of tropical cyclones causing increased loss during pregnancy, I adopt the methodology used by Xxxxxxx and Xia (2018) by examining the effect of tropical cyclone exposure on the fraction of males in a given birth cohort. I use the model outlined in equation (5) and results are presented in Table 9. Though not precisely estimated, these negative effects are consistent with the fragile male hypothesis, which argues that the biolog- ical fragility of the male fetus makes it such that males are more susceptible to negative early life shocks than females in the womb (Xxxxxxx, 2000). Thus, any unobserved effects on fetal mortality would be disproportionately present in male fetuses, thus reducing the fraction of males in the birth cohort. Xxxxxxx and Xia (2018) also find that in utero exposure to typhoons in the Philippines reduces the fraction of males in the birth cohort, though their estimated effect sizes are larger.‌
AutoNDA by SimpleDocs

Related to Fetal mortality

  • 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.

  • Department Head A. Within ten (10) business days from his/her receipt of the decision resulting from the previous level, the employee may appeal to the Department Head using the original copy of the grievance. B. Within ten (10) business days from the receipt of the employee's grievance, the Department Head or his/her designated representative who has not been involved in the grievance in prior levels shall make a thorough review of the grievance, meet with the parties involved and give a written decision and the reasons therefore to the employee and the Union representative. However, the Department Head or designate is not limited to denying a grievance for the reasons stated at any previous level in the procedure. Upon request, a copy of the decision will be given to the Union representative. C. If the Department Head or his/her designated representative fails to give a decision within the specified time limit, the Union shall have the option of referring a grievance alleging a violation of the negotiated agreement between the parties to arbitration. D. On matters that are not subject to arbitration pursuant to Section 8 hereafter, the written decision of the Department Head or his/her designated representative shall be final.

  • Department Heads Department heads shall normally be tenured and hold the rank of Associate Professor or Professor in one of the departments to be served, unless mutually agreed to by the departmental faculty and administration. 3.1.2.1 When it becomes known that a department head position will become vacant, or if the department head position has already become vacant, or if a new department is created, the xxxx of the college shall meet with the department faculty within two (2) weeks to discuss qualifications and expectations for the position. Specific guidelines will be formulated which may include: a. Whether internal and/or external candidates shall be considered b. Desired qualifications, including rank c. Budgetary considerations d. The target number of recommended candidates that will be submitted to the xxxx for consideration 3.1.2.1.1 Following the discussion described in 3.1.2.1, the department faculty shall communicate their recommendations within two (2) weeks to the xxxx. The xxxx shall promptly confirm or modify the department faculty’s recommendations and communicate the guidelines and procedures in choosing the new department head. 3.1.2.2 The department faculty will formulate its recommendation(s) among all candidates and forward same to the xxxx, with supporting rationale. When the department faculty is able to find more than one (1) acceptable candidate, the department may rank order its list of acceptable candidates and give reasons for its ranking. If the department is able to find only one (1) acceptable candidate, it shall recommend that candidate. If the department faculty does not find an acceptable candidate, the search will be ended. The xxxx will review the departmental recommendation(s) with the PVPAA. If the department’s recommendation(s) is approved by the PVPAA, the PVPAA shall recommend the appointment of the candidate to the President of the University. If the University does not accept the recommended candidate(s), the University has the right to declare the search process has ended. 3.1.2.3 In the event a department head position is not filled in a timely fashion through the preceding procedures, the Board may appoint a department head for a period not to exceed one (1) year. During this year the procedures specified in sections 3.1.2.1 and 3.

  • Contract Use by State Agencies To the extent applicable, the Contract does not prohibit state agencies from using their delegated purchasing authority to procure similar goods and services from other sources.

  • Data Security Requirements Without limiting Contractor’s obligation of confidentiality as further described in this Contract, Contractor must establish, maintain, and enforce a data privacy program and an information and cyber security program, including safety, physical, and technical security and resiliency policies and procedures, that comply with the requirements set forth in this Contract and, to the extent such programs are consistent with and not less protective than the requirements set forth in this Contract and are at least equal to applicable best industry practices and standards (NIST 800-53).

  • OF CLEAN AIR ACT AND FEDERAL WATER POLLUTION CONTROL ACT This provision is applicable to all Federal-aid construction contracts and to all related subcontracts. By submission of this bid/proposal or the execution of this contract, or subcontract, as appropriate, the bidder, proposer, Federal-aid construction contractor, or subcontractor, as appropriate, will be deemed to have stipulated as follows: 1. That any person who is or will be utilized in the performance of this contract is not prohibited from receiving an award due to a violation of Section 508 of the Clean Water Act or Section 306 of the Clean Air Act. 2. That the contractor agrees to include or cause to be included the requirements of paragraph (1) of this Section X in every subcontract, and further agrees to take such action as the contracting agency may direct as a means of enforcing such requirements.

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of-way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections 4, 6(a), 6(b), 6(c), and 7 of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra- State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C.

  • Clean Air Act and Federal Water Pollution Control Act The contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Clean Air Act, as amended, 42 U.S.C. § 7401 et seq.

  • CLEAN AIR ACT AND THE FEDERAL WATER POLLUTION CONTROL ACT (a) If the Sub-Recipient, with the funds authorized by this Agreement, enters into a contract that exceeds $150,000, then any such contract must include the following provision: Contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Clean Air Act (42 U.S.C. 7401-7671q) and the Federal Water Pollution Control Act as amended (33 U.S.C. 1251-1387), and will report violations to FEMA and the Regional Office of the Environmental Protection Agency (EPA).

  • Science The content in the sequence of BSC 1010C and BSC 1011C is comparable to the standards for Biology 1 and therefore if both are completed may be used as preparation for the associated EOC.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!