My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2021/06/30 Council Agenda Packet
>
Council Agenda Packets
>
2021
>
2021/06/30 Council Agenda Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/2/2021 3:31:31 PM
Creation date
7/2/2021 2:58:48 PM
Metadata
Fields
Template:
Council Agenda Packet
Date
6/30/2021
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
243
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Entity determines it needs to include in notifications to the individual(s) under 45 <br />C.F.R. §164.404(c). <br />3.12.2. After receipt of notice, from any source, of a Breach involving Unsecured Protected <br />Health Information used, disclosed, maintained, accessed or otherwise possessed by <br />Business Associate, or of a Breach involving Unsecured Protected Health Information <br />for which the Business Associate is otherwise responsible, Covered Entity may in its <br />sole discretion (i) require Business Associate, at Business Associate's sole expense, to <br />use a mutually agreed upon written notice to notify, on Covered Entity's behalf, the <br />individual(s) affected by the Breach, in accordance with the notification requirements <br />set forth in 45 C.F.R. § 164.404, without unreasonable delay, but in no case later than <br />sixty (60) days after discovery of the Breach; or (ii) elect to provide notice to the <br />individual(s) affected by the Breach. <br />3.13. Remuneration in Exchange for PHI. Business Associate shall not directly or indirectly receive <br />remuneration in exchange for any PHI unless Covered Entity notifies Business Associate that <br />it obtained a valid authorization from the Individual specifying that the Individual's PHI may <br />be exchanged for remuneration by the entity receiving such Individual's PHI. <br />3.14. Marketing. Business Associate must obtain or confirm that Covered Entity has obtained an <br />authorization for any use or disclosure of PHI for marketing, as defined in 45 C.F.R. § 164.501. <br />3.15. Exporting Information. Business Associate shall ensure that any agent or subcontractor to <br />whom Business Associate provides PHI, as well as Business Associate, not export PHI beyond <br />the borders of the United States of America. <br />4. Obligations of Covered Entity. <br />4.1. Limited Disclosure Obligations. Covered Entity will limit the PHI provided to Business <br />Associate to only that necessary to the business needs of Covered Entity. Prior to the <br />transmission of PHI to Business Associate, Covered Entity will notify Business Associate of <br />the need to transmit PHI and will arrange with Business Associate for the proper and secure <br />transmission of such PHI. <br />4.2. Requested Restrictions. Covered Entity shall notify Business Associate, in writing, of any <br />restriction on the use or disclosure of PHI that Covered Entity has agreed to in accordance with <br />45 C.F.R. § 164.522, which permits an Individual to request certain restrictions or uses and <br />disclosures, to the extent that such restriction may affect Business Associate's use or disclosure <br />of PHI. <br />4.3. Changes in or Revocation of Permission. Covered Entity will notify Business Associate in <br />writing of any changes in, or revocation of, permission by an Individual to use or disclose PHI, <br />to the extent that such changes or revocation may affect Business Associate's use or disclosure <br />of PHI. <br />4.4. Permissible Requests by Covered Entity. Covered Entity shall not request Business Associate <br />use or disclose PHI in any manner that would not be permissible under the HIPAA Privacy <br />Regulations and the HIPAA Security Regulations if done by Covered Entity, except to the <br />Page 5 of 9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.