This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "July 09, 2013 DS4P Joint Project"

From HL7Wiki
Jump to navigation Jump to search
Line 56: Line 56:
  
 
[[Security|Back to Security Main Page]]
 
[[Security|Back to Security Main Page]]
 
==Action Items==
 
1. Send all work involving the implementation guide to Ioana in word format. She is going to lead the process by transposing the information into the main document.
 
 
2. The group must determine if it is feasible to publish the document as two or possibly three documents based on Ioana’s initial draft(listed in the minutes).
 
 
3. John Moehkre says that we should be aware of changes that may be different and incorporate lessons learned from the pilot. In the front matter we must describe what we are doing and that is from the original ONC work and has been informed by information gained from onlging poilot sicne the orignal IG was developed.
 
 
4. Add wording to the front matter of the guide concerning CDA. Anything that is required from the CDA perspective, we should put a cart blanche statement saying that any differences from the implementation guide to this document includes changes that require CDA certification or passing tests are still required. These are the enhancements specific to this document. Any CDA consolidated templates that we provide would be required as specific to exchange and direct and these are the requirements that you would do anyway for exchange or direct.
 
  
 
==Meeting Minutes==
 
==Meeting Minutes==

Revision as of 15:27, 15 July 2013

Data Segmentation for Privacy

Meeting Information

Back to Security Main Page

Back to HL7 DS4P Project Main Page

Attendees:

expected

Back to Security Main Page

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.


Back to Security Main Page

Meeting Minutes

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.

Back to Security Main Page