Privacy Compliance Requirements Sample Clauses

Privacy Compliance Requirements. The Health Insurance Portability and Accountability Act (HIPAA) Privacy Regulations at 45 CFR 164.502(e) and 164.504(e) require ODM to enter into agreements with the MCOP as a means of obtaining satisfactory assurance that the MCOP will appropriately safeguard all protected health information (PHI), which means information received from or on behalf of ODM that meets the definition of PHI as defined by HIPAA and the regulations promulgated by the United States Department of Health and Human Services, specifically 45 CFR 160.103, 45 CFR 164.501, and any amendments thereto. In addition to the HIPAA requirements, the MCOP shall comply with any other applicable Federal and State laws regarding privacy and confidentiality, including Title VI of the Civil Rights Act of 1964, and ORC Sections 5101.26, 5101.27, and 5160.45 through 5160.481, as applicable. The MCOP acknowledges that ODM is a Covered Entity under HIPAA. A Covered Entity means a health plan, a health care clearinghouse, or health care provider under 45 CFR 160.103. The MCOP further acknowledges it is a Business Associate of ODM. A Business Associate means a person or entity that, on behalf of the Covered Entity, maintains, performs, or assists in the performance of a function or activity that involves the use or disclosure of “Protected Health Information” under 45 CFR 160.103. The MCOP, as a Business Associate agrees to comply with all of the following provisions:
Sample 1Sample 2Sample 3See All (45)
AutoNDA by SimpleDocs
Privacy Compliance Requirements. The Health Insurance Portability and Accountability Act (HIPAA) Privacy Regulations at 45 CFR.164.502(e) and 164.504(e) require ODM to enter into agreements with MCPs as a means of obtaining satisfactory assurance that the MCPs will appropriately safeguard all “protected health information” (PHI), which means information received from or on behalf of ODM that meets the definition of PHI as defined by HIPAA and the regulations promulgated by the United States Department of Health and Human Services, specifically 45 C.F.R. 160.103, 45 CFR 164.501 and any amendments thereto. In addition to the HIPAA requirements, the MCP must comply with any other applicable Federal and State laws regarding privacy and confidentiality, including Title VI of the Civil Rights Act of 1964, O.R.C. 5101.26, 5101.27, and 5160.45 through 5160.481, as applicable. The MCP acknowledges that ODM is a Covered Entity under HIPAA. A Covered Entity means a health plan, a health care clearinghouse, or health care provider under 45 CFR 160.103. The MCP further acknowledges that it is a Business Associate of ODM. A Business Associate means a person or entity that, on behalf of the Covered Entity, maintains, performs, or assists in the performance of a function or activity that involves the use or disclosure of “Protected Health Information” under 45 CFR 160.103. The MCP, as a Business Associate agrees to comply with all of the following provisions:
Sample 1Sample 2Sample 3See All (6)
Privacy Compliance Requirements. The Health Insurance Portability and Accountability Act (HIPAA) Privacy Regulations at 45 CFR. Section 164.502(e) and Section 164.504(e) require ODJFS to have agreements with MCPs as a means of obtaining satisfactory assurance that the MCPs will appropriately safeguard all personal identified health information. Protected Health Information (PHI) is information received from or on behalf of ODJFS that meets the definition of PHI as defined by HIPAA and the regulations promulgated by the United States Department of Health and Human Services, specifically 45 CFR 164.501, and any amendments thereto. MCPs must agree to the following: a. MCPs shall not use or disclose PHI other than is permitted by this agreement or required by law. b. MCPs shall use appropriate safeguards to prevent unauthorized use or disclosure of PHI. c. MCPs shall report to ODJFS any unauthorized use or disclosure of PHI of which it becomes aware. Any breach by the MCP or its representatives of protected health information (PHI) standards shall be immediately reported to the State HIPAA Compliance Officer through the Bureau of Managed Health Care. MCPs must provide documentation of the breach and complete all actions ordered by the HIPAA Compliance Officer. d. MCPs shall ensure that all its agents and subcontractors agree to these same PHI conditions and restrictions. e. MCPs shall make PHI available for access as required by law. f. MCP shall make PHI available for amendment, and incorporate amendments as Appendix C Covered Families and Children (CFC) population Page 10 appropriate as required by law. g. MCPs shall make PHI disclosure information available for accounting as required by law. h. MCPs shall make its internal PHI practices, books and records available to the Secretary of Health and Human Services (HHS) to determine compliance. i. Upon termination of their agreement with ODJFS, the MCPs, at ODJFS' option, shall return to ODJFS, or destroy, all PHI in its possession, and keep no copies of the information, except as requested by ODJFS or required by law. j. ODJFS will propose termination of the MCP's provider agreement if ODJFS determines that the MCP has violated a material breach under this section of the agreement, unless inconsistent with statutory obligations of ODJFS or the MCP.
Sample 1
Privacy Compliance Requirements. Consent of Principals in order for the Board to collect, use and Disclose the listing, sale/lease and purchase information… 17 Proof of consent 17 Failure to comply with Rules and Regulations 18 14.01 Definitions 18 14.02 Deposits 19 14.03 Delivery of agreement 19 14.04 Disbursement 19 14.05 Retention of agreements… 20 14.06 Provisions of the ACT re proper books and records 20 14.07 Terms deemed to be included in all agreements 20
Sample 1
Privacy Compliance Requirements. (a) In addition to all other requirements contained in these MLS rules and regulations, when dealing with any property that is subject of an MLS Listing, all Listing Brokers and Co-operating Brokers must obtain the consent of their Principals and/or customers that is required by the national Privacy Code or is otherwise required by law in order for the Board to collect, use and disclose the listing, sale/lease and purchase information regarding the property and the transaction on the Board's Multiple Listing Service and within the Board's MLS Database (b) Immediately upon request by the Board, a Member shall provide the Board with proof of the consent described in paragraph (a) from the Member's Principal or customer in regard to any property that is the subject of an MLS Listing for which the Member's Principal or customer is the Seller or Buyer (or landlord or tenant, if the MLS Listing is for the lease of the property). Failure to comply with these rules and regulations shall be deemed to be a breach of the Board by-law and shall be dealt with in accordance with the provisions of Article 9 of the Board by-law as well as any other remedies available to the Board as set out in these rules.
Sample 1
Privacy Compliance Requirements 
Sample 1

Related to Privacy Compliance Requirements

  • Compliance Requirements A. Nondiscrimination. The Contractor agrees to comply, and to require its subcontractor(s) to comply, with the nondiscrimination provisions of MCL 37.2209. The Contractor further agrees to comply with the provisions of Section 9:158 of Chapter 112 of the Xxx Arbor City Code and to assure that applicants are employed and that employees are treated during employment in a manner which provides equal employment opportunity.

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations. B. The Acquiring Bank will ensure that The Merchant is kept informed of any relevant new, or changes to, PCI PED and/or DSS compliance rules and regulations. C. The Merchant will comply with PCI PED and/or DSS, and resulting obligations, in respect of establishing, and maintaining, the required security controls. D. The Merchant will ensure that all its appropriate staff (existing and new) are knowledgeable in their responsibilities with respect to PCI PED and/or DSS compliance. E. The Merchant must be able to demonstrate compliance with PCI PED and/or DSS and maintain measures necessary to successfully pass regular compliance certification checks. F. The Merchant will notify The Acquiring Bank immediately should it become evident that data security standards have been compromised. The Merchant will also provide all assistance necessary to assist The Acquiring Bank and its agents to investigate and obtain any required evidence of a security breach. G. The Merchant hereby agrees and undertakes to fully indemnify The Acquiring Bank from and against all actions, claims, losses, charges, costs and damages which The Acquiring Bank may suffer or incur as a result of The Merchants failure to comply with PCI PED and/or DSS. H. Further to the conditions set out in Section 34 below, The Acquiring Bank reserves the right to terminate this agreement with The Merchant if The Merchant: i. Refuses to accept, or commence, any remedial action(s) required under its obligation to PCI PED and/or DSS. ii. Fails to maintain its PCI PED and/or DSS obligations and/or consistently fails compliance certification checks. iii. Receives continuing penalties Fraud notifications or alerts of in any case where the Acquiring bank may be asked by the schemes to take action against the Merchant. اهيلع ةقداصملا تمت دق هنأ نم ةيلمع يأ ذيفنت دعب دكأتلا رجاتلا ىلع بجي .10 لمحتب هرارقإ متو ةقاطبلا لماح ةطساوب بولطملا وحنلا ىلعو ةرشابم .ةيلمعلا كلت ذيفنت نع هتيلوؤسم لماك يأ تحت ةيلمع نم رثكأ ىلإ ةيلمعلا ةميق ميسقتب موقي لاأب رجاتلا دهعتي .11 لاير )500( ةميقب نيتيلمع ذفني نأ لاثملا ليبس ىلعف ،قلاطلإا ىلع فرظ ةعباتلا عفدلا ةقاطب سفن مادختساب لاير )1000( يلامجلإا اهغلبم عئاضبل اذه ربتعي ثيحب ؛ىرخأ عفد تاقاطب ةيأ وأ تاعوفدملل ةيدوعسلا ةكبشلل ءاغلإ و زاهجلا فاقيا ةلاحلا هذه يف كنبلل قحيو ،اًمامت ًاروظحم فرصتلا .ةيقافتلاا ةكبشلا ةقاطبب لقأ وأ رثكأ وأ لايرب ةرركم تايلمع ءارجإ رجاتلل قحي لا .12 غلابم وأ تايلمع ددع قيقحت ضرغب هب ةصاخلا نامتئلاا ةقاطب وأ ةيدوعسلا ءاغلإ و زاهجلا فاقيا كنبلل قحيو .هيلع ةررقملا موسرلا عفد بنجتل تايلمع .رجاتلا باسح نم ةررقملا موسرلا مصخ يف قحلاب ظافتحلاا عم ةيقافتلاا لمحُي نل هلاعأ ةحضوملا تامازتللااو تاءارجلإاب ديقتلا مدعو هقافخإ نأ رجاتلا رقي وأ فيلاكت وأ تابلاطم وأ ىوعد ةيأ نع اهريغ وأ تناك ةينوناق ،ةيلوؤسم ةيأ كنبلا ةراسخ وأ ةيمكارتلا رارضلأا وأ رئاسخلا كلذ يف امب رئاسخ وأ رارضأ وأ فيراصم مازتللااب رجاتلا للاخإ ببسب رجاتلا كنب اهدبكتي وأ اهل ضرعتي دق يتلا ،حابرلأا مدع ببسب ركذ امم يلأ رجاتلا كنب ضرعت لاح يفو .ةدراولا تابلطتملاو تاميلعتلاب ىوعد نم هيلع بترتي دق ام عيمج رجاتلا لمحتي ،ةروكذملا تاءارجلإاب رجاتلا مازتلا مدع ةجيتن رجاتلا كنب قحلت دق رئاسخ وأ رارضأ وأ فيراصم وأ فيلاكت وأ تابلاطم وأ .تاءارجلإاو طورشلاو تابلطتملا هذهب رجاتلا مازتلا عفدلا تاقاطب ةعانص رايعم عم قفاوتلا .9 PCI Compliance مادختساب ةصاخلا دعاوقلا ىلع بسانملا بيردتلا رجاتلل رجاتلا كنب مدقي .أ ،عفدلا تاقاطب ةعانصب قلعتت يتلاو ةيرسلا ةيصخشلا ماقرلأا لاخدإ زاهج تامازتلاب قلعتي اميف عفدلا تاقاطب ةعانص تانايب ةيامح رايعم ىلع اًضيأو تارييغت يأ ىلع وأ ديدج وه ام ىلع رجاتلا علاطإ ماود نم رجاتلا كنب دكأتي .ب ماقرلأا لاخدإ زاهج مادختساب ةصاخلا مازتللاا دعاوقو تاعيرشتلاب ةقلاع تاذ تانايب ةيامح رايعمب وأ ،عفدلا تاقاطبب قلعتي ام لك وأ ةيرسلا ةيصخشلا .عفدلا تاقاطب ةعانص ،عفدلا تاقاطبل ةيرسلا ةيصخشلا ماقرلأا لاخدإ ئدابمو ريياعمب رجاتلا مزتلي .ج قلعتي اميف ةرداصلا اهتاعيرشتو ،عفدلا تاقاطب تانايب نمأ ريياعمب اًضيأو .ةبولطملا ةيامحلا طباوض قيبطتو سيسأتب )نيدجتسملاو نييلاحلا( نيصتخملا نيفظوملا علاطإ نم رجاتلا دكأتي .د ةيصخشلا ماقرلأا لاخدإب ةصاخلا مازتللاا دعاوقب قلعتي اميف مهتايلوؤسمب .عفدلا تاقاطب تانايب نمأ ريياعمو ،عفدلا تاقاطبل ةيرسلا ةيصخشلا ماقرلأا لاخدإب ةصاخلا مازتللاا دعاوق حضوي نأ رجاتلا ىلع بجي .ـه ةظفاحملاو ،عفدلا تاقاطب تانايب نمأ ريياعم كلذكو عفدلا تاقاطبل ةيرسلا مازتللاا ىدمل ةيرودلا تارابتخلاا ةداهش زايتجلا ةيرورضلا ريياعملا ىلع .حاجنب ريياعم كاهتنا نم ققحتلا روف رجاتلا كنب راعشإب رجاتلا موقي نأ بجي .و كنب ةدعاسمل يرورض وه ام لك ميدقت رجاتلا ىلع بجي اًضيأو ،ةيامحلا ةبولطملا نيهاربلاو ةلدلأا يف قيقحتلا نم نيصتخملا هيفظومو رجاتلا .ةيامحلا قارتخا تابثلإ رجاتلا كنبل ةلماكلا ةيامحلاب ةيقافتلاا هذه بجومب رجاتلا مزتليو دهعتي .ز تابلاطم وأ ىوعد ةيأ نع ،اهريغ وأ تناك ةينوناق ،ةيلوؤسم ةيأ هليمحت مدعو رارضلأا وأ رئاسخلا كلذ يف امب رئاسخ وأ رارضأ وأ فيراصم وأ فيلاكت وأ ببسب رجاتلا كنب اهدبكتي وأ اهل ضرعتي دق يتلا ،حابرلأا ةراسخ وأ ةيمكارتلا كنب ظفتحي ،هاندأ 34 مقر ةداملا يف اهعضو مت يتلا طورشلا ىلإ ةفاضإ .ح :يتلآاب رجاتلا مايق ةلاح يف رجاتلا عم ةيقافتلاا هذه ءاهنإ قحب رجاتلا هتامازتلا هيلع هيلمت بولطم يزارتحا ءارجإ يأ ذاختا وأ لوبق هضفر .i وأ عفدلا تاقاطبل ةيرسلا ةيصخشلا ماقرلأا لاخدإ ئدابمو ريياعمب .عفدلا تاقاطب تانايب نمأ ريياعمب ماقرلأا لاخدإ ئدابمو ريياعمو دعاوقب مازتللااو ةظفاحملا يف هقافخإ .ii ،عفدلا تاقاطب تانايب نمأ ريياعمب وأ عفدلا تاقاطبل ةيرسلا ةيصخشلا .مازتللاا تارابتخا زايتجا يف لشفلا و/وأ تاريذحتلاو تاهيبنتلا هملاتسا وأ هيلع ةرمتسملا تامارغلا ضرف .iii تاعوفدملا ماظن لبق نم ةيلمع يأ صوصخب ريوزتلاب ةقلعتملا مزلالا ءارجلإا ذاختا رجاتلا كنب نم بلطي دق اهللاخ نم يتلاو ،يملاعلا 10. Transaction(s) to be in Saudi Riyals: All MADA-POS transactions must be denominated in Saudi Riyals (SR).

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • E-Verify Compliance The contractor represents and covenants that the contractor and its subcontractors comply with the requirements of Article 2 of Chapter 64 of the North Carolina General Statutes (NCGS). The City is relying on this E-Verify Compliance section in entering into this contract. The parties agree to this section only to the extent authorized by law. If this section is held to be unenforceable or invalid in whole or in part, it shall be deemed amended to the extent necessary to make this contract comply with NCGS 160A-20.1(b).

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

  • Compliance With Insurance Requirements Borrower will comply with all Insurance requirements and will not permit any condition to exist on the Mortgaged Property that would invalidate any part of any Insurance coverage required under this Loan Agreement.

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