My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res-2017-127
>
Meetings
>
2017
>
08. August
>
2017-08-01 10:00 AM - Commissioners' Agenda
>
Res-2017-127
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/13/2018 12:20:08 PM
Creation date
6/13/2018 12:17:34 PM
Metadata
Fields
Template:
Meeting
Date
8/1/2017
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Fully Executed Version
Supplemental fields
Alpha Order
q
Item
Request to Approve a Resolution to Authorize an Amendment to the Child Death Reporting System Data Use Agreement between the Kittitas County Public Health Department and the Michigan Public Health Institute
Order
17
Placement
Consent Agenda
Row ID
38579
Type
Agreement
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
41
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
DATA USE ADDENDUM TO MASTER AGREEMENT BETWEEN <br />THE MICHIGAN PUBLIC HEALTH INSTITUTE AND THE <br />Kittitas County Public Health <br />This Data Use Addendum ("Addendum") is made and entered into as of this 1st day of May <br />2017 by and between the Michigan Public Health Institute (known as "Receiver") and the <br />Kittitas County Public Health (known as "Holder") both to be referred to herein as "parties ". <br />WHEREAS, the Receiver and the Holder entered into a Master Agreement dated AprilS, 2016 <br />for establishing the terms and conditions for the collection, storage and use of data obtained from <br />the case reviews of child deaths submitted by the Child Death Review (CDR) team in Kittitas <br />County and entrusted to the Receiver as the Child Death Review Case Reporting System. <br />WHEREAS, the Receiver seeks to amend Appendix B to clarify the HIP AA Required Elements <br />to De-Identify Case Data by specifically listing all elements or categories of elements that <br />HIPAA law considers to be identifiers (45 CFR 164.514) and to clarify the Holder's <br />responsibility to remove identifying information in preparation for de-identified downloads; <br />NOW, THEREFORE, in consideration of the above account the parties agree as follows: <br />Appendix B <br />HIPAA Required Elements to De-Identify Case Data· <br />The CDR-CRS supports two types of data downloads: identified and de-identified. NCFRP staff <br />and researchers who have been approved by the NCFRP will receive only de-identified data. <br />The CDR-CRS variables that will be removed in de-identified downloads are listed below. <br />The CDR-CRS contains many free text fields (most often in the 'specify' or 'describe' text <br />fields). The CDR-CRS also provides users the opportunity to provide more detail surrounding <br />the circumstances of the death in Section N: Narrative text field. When the Narrative, <br />'specify,' and/or 'describe' text fields are included in a de-identified download, the <br />Narrative, 'describe,' and 'specify' text fields SHOULD NOT contain any HIPAA <br />Identifiers. <br />HIP AA Identifiers include names; all geographical subdivisions smaller than a state; all elements <br />of dates (except ye ar) for dates directly related to an individual; phone numbers; fax numbers; <br />electronic mail addresses; social security numbers; medical record numbers; health plan <br />beneficiary numbers; account numbers; certificate/license numbers; vehicle identifiers and serial <br />numbers; device identifiers and serial numbers; web universal resource locators; internet <br />protocol address numbers; biometric identifiers; full face photographic images; and any other <br />unique identifying number, characteristic or code. <br />* Source: Code of Federal Regulations Section 164 .514(b)(2)(i). <br />1
The URL can be used to link to this page
Your browser does not support the video tag.