Difference between revisions of "July 16, 2013 DS4P Joint Project"
| (3 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
==Attendees== | ==Attendees== | ||
(expected) | (expected) | ||
| − | * [mailto: Wendy Baker | + | * [mailto:wbaker@ebhin.org Wendy Baker] |
| − | |||
* [mailto:kathleen_connor@comcast.net Kathleen Connor] | * [mailto:kathleen_connor@comcast.net Kathleen Connor] | ||
* [mailto:Mike.davis@va.gov Mike Davis], Security Co-Chair | * [mailto:Mike.davis@va.gov Mike Davis], Security Co-Chair | ||
* [mailto:duane.decouteau@gmail.com Duane DeCouteau] | * [mailto:duane.decouteau@gmail.com Duane DeCouteau] | ||
| − | * [mailto: | + | * [mailto:slwebb@drc.com Suzanne Gonzales-Webb] |
| − | |||
* [mailto:Brian.Handspicker@its.ny.gov Brian Handspicker] | * [mailto:Brian.Handspicker@its.ny.gov Brian Handspicker] | ||
| − | |||
| − | |||
| − | |||
| − | |||
* [mailto:Richard.Thoreson@samhsa.hhs.gov Richard Thoreson], CBCC Co-Chair | * [mailto:Richard.Thoreson@samhsa.hhs.gov Richard Thoreson], CBCC Co-Chair | ||
| Line 29: | Line 23: | ||
==Agenda:== | ==Agenda:== | ||
| + | # Roll Call, Agenda, Meeting Minutes | ||
| + | # Implementation Guide Update - IG Front matter submitted | ||
| − | |||
| − | |||
| − | |||
==DRAFT Minutes== | ==DRAFT Minutes== | ||
| − | IG Front matter submitted by Richard Thoreson via e-mail: | + | Role Call, Agenda reviewed |
| + | |||
| + | IG Front matter: | ||
| + | IG Front matter submitted by Richard Thoreson via e-mail: // Kathleen and Richard will be discussing updates to the statement below offline. | ||
'' This Guide is about segmenting clinical records, so that personally identified information (PII) can be selectively shared. It mainly specifies an interoperable, standards-based privacy policy document. Policy execution is largely left up to EHRs, PHRs and HIE venders. This specification conveys policy information that venders can import, export, and execute, without human hands.'' | '' This Guide is about segmenting clinical records, so that personally identified information (PII) can be selectively shared. It mainly specifies an interoperable, standards-based privacy policy document. Policy execution is largely left up to EHRs, PHRs and HIE venders. This specification conveys policy information that venders can import, export, and execute, without human hands.'' | ||
'' The following analysis also considers and illustrates how privacy policies can be incorporated as clinical records are shared for care coordination, quality and public health reporting, and research. The idea is that patients are more likely to consent to sharing sensitive PII, and providers are more likely to share valuable business records, if both are given meaningful opportunities to select who can see and use what data, and for what purpose. '' | '' The following analysis also considers and illustrates how privacy policies can be incorporated as clinical records are shared for care coordination, quality and public health reporting, and research. The idea is that patients are more likely to consent to sharing sensitive PII, and providers are more likely to share valuable business records, if both are given meaningful opportunities to select who can see and use what data, and for what purpose. '' | ||
Latest revision as of 20:52, 16 July 2013
Data Segmentation for Privacy
Back to HL7 DS4P Project Main Page
Attendees
(expected)
- Wendy Baker
- Kathleen Connor
- Mike Davis, Security Co-Chair
- Duane DeCouteau
- Suzanne Gonzales-Webb
- Brian Handspicker
- Richard Thoreson, CBCC Co-Chair
Agenda:
- Roll Call, Agenda, Meeting Minutes
- Implementation Guide Update - IG Front matter submitted
DRAFT Minutes
Role Call, Agenda reviewed
IG Front matter: IG Front matter submitted by Richard Thoreson via e-mail: // Kathleen and Richard will be discussing updates to the statement below offline.
This Guide is about segmenting clinical records, so that personally identified information (PII) can be selectively shared. It mainly specifies an interoperable, standards-based privacy policy document. Policy execution is largely left up to EHRs, PHRs and HIE venders. This specification conveys policy information that venders can import, export, and execute, without human hands.
The following analysis also considers and illustrates how privacy policies can be incorporated as clinical records are shared for care coordination, quality and public health reporting, and research. The idea is that patients are more likely to consent to sharing sensitive PII, and providers are more likely to share valuable business records, if both are given meaningful opportunities to select who can see and use what data, and for what purpose.
