Difference between revisions of "July 09, 2013 DS4P Joint Project"
| Line 33: | Line 33: | ||
==Agenda:== | ==Agenda:== | ||
| − | |||
| − | 1. Implementation Guide: | + | 1. Implementation Guide: - |
| − | + | ||
| − | + | The meeting started with Ioana providing an update on the implementation guide. Following issues/recommendations were discussed: | |
| − | + | ||
| − | + | Jonathan Coleman was asked to help with the Overview. | |
| − | + | Ioana volunteered to integrate the process and will put the sections together as members of the group send work to her. – Send her text in word and she will transpose the information into the document. | |
| − | + | ||
| − | + | Chapter 2 – Templates – If anyone has a better way of presenting or producing templates, please let everyone know and send the information to Ioana. They have already added constraint and provenance templates. It is clickable directly to the website that contains the template documents. | |
| + | |||
| + | Note concerning the ways to implement the non-re-disclosure entry. There are optional ways to implement this: | ||
| + | 1. Create a sub section on confidentiality of non-re-disclosure entry | ||
| + | 2. Interpret these as other options and display them as a clickable acknowledge on the screen. That way you know that you are fulfilling the requirements of the privacy policies. | ||
| + | |||
| + | We will start with three modules and if necessary we can go with two using one of the two suggestions below from Ioana. | ||
| + | 1. The two transport as standalone modules and; | ||
| + | 2. Option of clearly merging them into two IGS that have the content profile that have the direct and exchange transports respectively. | ||
| + | |||
| + | Note: Feedback received on this issue is as follows: One colossal document was difficult and two many fragmented documents would be too cumbersome. | ||
| + | |||
[[Security|Back to Security Main Page]] | [[Security|Back to Security Main Page]] | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ==Action Items== | ||
==Meeting Minutes== | ==Meeting Minutes== | ||
Revision as of 15:07, 15 July 2013
Contents
Data Segmentation for Privacy
Back to HL7 DS4P Project Main Page
Attendees:
expected
- [mailto: Wendy Baker]
- Johnathan Coleman
- Kathleen Connor
- Mike Davis, Security Co-Chair
- Duane DeCouteau
- Mike Dufel
- Suzanne Gonzales-Webb, CBCC Co-Chair
- Adrianne James
- Brian Handspicker
- Adrianne James
- Holly Miller
- Harry Rhodes
- David Staggs
- Richard Thoreson, CBCC Co-Chair
- Serafina Versaggi
- Kate Weatherby
Agenda:
1. Implementation Guide: -
The meeting started with Ioana providing an update on the implementation guide. Following issues/recommendations were discussed:
Jonathan Coleman was asked to help with the Overview. Ioana volunteered to integrate the process and will put the sections together as members of the group send work to her. – Send her text in word and she will transpose the information into the document.
Chapter 2 – Templates – If anyone has a better way of presenting or producing templates, please let everyone know and send the information to Ioana. They have already added constraint and provenance templates. It is clickable directly to the website that contains the template documents.
Note concerning the ways to implement the non-re-disclosure entry. There are optional ways to implement this: 1. Create a sub section on confidentiality of non-re-disclosure entry 2. Interpret these as other options and display them as a clickable acknowledge on the screen. That way you know that you are fulfilling the requirements of the privacy policies.
We will start with three modules and if necessary we can go with two using one of the two suggestions below from Ioana. 1. The two transport as standalone modules and; 2. Option of clearly merging them into two IGS that have the content profile that have the direct and exchange transports respectively.
Note: Feedback received on this issue is as follows: One colossal document was difficult and two many fragmented documents would be too cumbersome.
