Conditions File vs Sample Clauses

Conditions File vs. Priority Conditions It should be noted that priority conditions reported in the Priority Conditions (PC) section of the MEPS questionnaire in Panel 11 do not directly relate to those listed as priority conditions on the Medical Conditions PUF. Unlike those on this file, the conditions identified in the PC section of the instrument in Panel 11 were not added to the condition roster. Chronic conditions asked about in the PC section were asked in the context of “has person ever been told by a doctor or other health care professional that they have (condition)?”, while the priority conditions on the Conditions PUF refer to those experienced by the respondent during a specific reference period. Some of those round-specific conditions were then determined to be a priority due to their prevalence, expense, or relevance to policy. There may be logical inconsistencies between items in the Panel 11 version of PC section and conditions on the Conditions PUF because they were asked in reference to different time periods. Researchers should use their judgment in using this variable and related information, keeping in mind that the Panel 11 PRIOLIST flag is a manual process and due to human error some information may be missing or inaccurately reported. Panel 12 priority conditions created in the Priority Condition Enumeration (PE) section were also asked in the context of “has person ever been told by a doctor or other health care professional that they have (condition)?” If the response is Yes (1), then a condition record is generated. Note that priority conditions are included in the Conditions PUF only if the condition is current. A current condition is defined as a condition linked to an event or disability day or a condition the person is currently experiencing (i.e., a condition selected in the CE section). These changes are reflected in Appendix 3.
Sample 1
AutoNDA by SimpleDocs

Related to Conditions File vs

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

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

  • Court Ordered Requests for Call Detail Records and Other Subscriber Information 7.1 To the extent technically feasible, BellSouth maintains call detail records for Mpower end users for limited time periods and can respond to subpoenas and court ordered requests for this information. BellSouth shall maintain such information for Mpower end users for the same length of time it maintains such information for its own end users.

  • TIME AND WAGES RECORDS Particulars of details of payment to each Employee must be included on the envelope including the payment or in a statement handed to the Employee at the time payment is made and will contain the following information:

  • Accurate and Timely Submission of Reports a) The reports and administrative fees shall be accurate and timely and submitted in accordance with the due dates specified in this section. Vendor shall correct any inaccurate reports or administrative fee payments within three (3) business days upon written notification by DIR. Vendor shall deliver any late reports or late administrative fee payments within three (3) business days upon written notification by DIR. If Vendor is unable to correct inaccurate reports or administrative fee payments or deliver late reports and fee payments within three

  • DES Filing Requirement Under RCW 39.26, sole source contracts and amendments must be filed with the State of Washington Department of Enterprise Services (DES). If this Contract is one that must be filed, it shall not be effective nor shall work commence or payment be made until the tenth (10th) working day following the date of filing subject to DES approval. In the event DES fails to approve the Contract or any amendment hereto, the Contract or amendment shall be null and void.

  • Public Records Requests If the Department receives a public records request for materials designated by the Contractor as trade secret or otherwise confidential under Florida or federal law, the Contractor will be responsible for taking the appropriate legal action in response to the request. If the Contractor fails to take appropriate and timely action to protect the materials designated as trade secret or otherwise confidential, the Department will provide the materials to the requester.

  • Public Records Request (09/17) Contractor acknowledges that the City of Portland is subject to the Oregon Public Records Act and Federal law. Third persons may claim that the Confidential Information Contractor submitted to the City hereunder may be, by virtue of its possession by the City, a public record and subject to disclosure pursuant to the Oregon Public Records Act. The City’s commitments to maintain certain information confidential under this Contract are all subject to the constraints of Oregon and federal laws. All information submitted by Contractor is public record and subject to disclosure pursuant to the Oregon Public Records Act, except such portions for which Contractor requests and meets an exemption from disclosure consistent with federal or Oregon law. Within the limits and discretion allowed by those laws, the City will maintain the confidentiality of information.

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Seller’s Conditions The obligations of Seller at the Closing are subject, at the option of Seller, to the satisfaction or waiver at or prior to the Closing of the following conditions precedent:

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