# HIPAA (45 CFR Part 164) 164.520(c)(2) — Provisions of Notice - Certain Covered Health Care Providers - Source: https://support.icompaas.com/compliance/hipaa/164-520-c-2-provisions-of-notice-certain-covered-health-care-providers - Section: [Compliance](https://support.icompaas.com/compliance) › [HIPAA Security, Privacy & Breach-Notification Rules](https://support.icompaas.com/compliance/hipaa) › Privacy Rule — §164.520 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **HIPAA (45 CFR Part 164)**·§ `164.520(c)(2)`·medium·Component: **Privacy Rule** ## What this control requires > Specific requirements for certain covered health care providers. A covered health care provider that has a direct treatment relationship with an individual must: (i) Provide the notice: (A) No later than the date of the first service delivery, including service delivered electronically, to such individual after the compliance date for the covered health care provider; or (B) In an emergency treatment situation, as soon as reasonably practicable after the emergency treatment situation. (ii) Except in an emergency treatment situation, make a good faith effort to obtain a written acknowledgment of receipt of the notice provided in accordance with paragraph (c)(2)(i) of this section, and if not obtained, document its good faith efforts to obtain such acknowledgment and the reason why the acknowledgment was not obtained; (iii) If the covered health care provider maintains a physical service delivery site: (A) Have the notice available at the service delivery site for individuals to request to take with them; and (B) Post the notice in a clear and prominent location where it is reasonable to expect individuals seeking service from the covered health care provider to be able to read the notice. (iv) Whenever the notice is revised, make the notice available upon request on or after the effective date of the revision and promptly comply with the requirements of paragraph (c)(2)(iii) of this section, if applicable. > > — HIPAA (45 CFR Part 164), § 164.520(c)(2) ### In plain English Specific requirements for certain covered health care providers. In practice, this means you can prove you requirements requirements-level controls on a defined cadence. ## Why it matters HIPAA non-compliance is a strict-liability matter: OCR civil monetary penalties are assessed per-record per-violation (up to USD 1.9 million per identical-violation calendar year as of 2024), and willful neglect can trigger criminal referral. ## What an auditor looks for HHS OCR investigators and SOC-2+HIPAA auditors look for the specific 45 CFR § citation, whether the safeguard is required vs addressable (and if addressable, the documented decision), the implementation specification, the workforce member responsible, and the records that show it runs. Within **Privacy Rule**, the assessor will trace your implementation back to the catalogue reference (§ 164.520(c)(2)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Requirements.** Document the trigger, the owner and the cadence. - **Policy.** Document the trigger, the owner and the cadence. - **Notice.** Document the trigger, the owner and the cadence. - **Provisions.** Document the trigger, the owner and the cadence. - **Scope:** requirements, management, revision, individuals, notice, policy, i, obtain. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Provisions of Notice - Certain Covered Health Care Providers. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-53 Rev. 5 PS-4(1)** — Post-Employment Requirements](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ps-4-1-post-employment-requirements) ## Related controls in HIPAA (45 CFR Part 164) - [**§ 164.520(e)** — Documentation](https://support.icompaas.com/compliance/hipaa/164-520-e-documentation) - [**§ 164.520(c)(1)** — Provisions of Notice - Health Plans](https://support.icompaas.com/compliance/hipaa/164-520-c-1-provisions-of-notice-health-plans) - [**§ 164.520(c)(3)** — Provision of Notice - Electronic Notice](https://support.icompaas.com/compliance/hipaa/164-520-c-3-provision-of-notice-electronic-notice) - [**§ 164.524(a)(1)** — Right of access](https://support.icompaas.com/compliance/hipaa/164-524-a-1-right-of-access) - [**§ 164.524(b)(1)** — Individual request for access](https://support.icompaas.com/compliance/hipaa/164-524-b-1-individual-request-for-access) - [**§ 164.524(b)(2)** — Timely action](https://support.icompaas.com/compliance/hipaa/164-524-b-2-timely-action) ## References - [U.S. HHS Office for Civil Rights — HIPAA (45 CFR Part 164)](https://www.hhs.gov/hipaa/for-professionals/index.html) - Catalogue identifier: `§ 164.520(c)(2)` Topics: governance riskpolicy management ## Related compliance guidance - [HIPAA compliance for SaaS: a practical implementation guide](https://support.icompaas.com/compliance/hipaa): Start with the full HIPAA implementation guide — scope, roadmap, evidence and how the assessment runs. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most covered-entity customers accept a SOC 2 Type II report as the independent evidence that your HIPAA controls operate, since no HIPAA attestation exists. - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): NIST publishes mappings of the Security Rule standards and implementation specifications to SP 800-53 Rev. 5 controls alongside SP 800-66 Rev. 2, so an 800-53 control set doubles as a HIPAA crosswalk.