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

July 30, 2013 DS4P Joint Project

From HL7Wiki
Jump to navigation Jump to search

Data Segmentation for Privacy

Meeting Information

Back to Security Main Page

Back to HL7 DS4P Project Main Page

Attendees


Back to Security Main Page

Agenda

  1. Roll Call, Agenda, Meeting Minutes
  2. Continue review and update of the DS4P IG
    1. individual responsibilities, assignments

DRAFT Minutes

Role Call, Agenda updated and accepted

This is due on Sunday!

Note: If we have information that everyone is comfortable with the available information. We should continue with the work and submit for ballot. Additional comments can be submitted during the ballot. If we have Ioana is looking for additional constructive feedback to be added to the current document

Commenced reviewing of document: CDAR2_IG_DS4P_EXCHANGE_R1_n1_2013SEPT.pdf


Please note that the coversheet is subject to change - I'm using the default DSTU for now. per Ioana


The reference to US-domain centric information is very small the facility code is one of them. In making this an exemplar (risk of making it an exemplar…) it occurs to Mike that we can take the US-realm stuff and put them in their own section, because they reference law if would be helpful to make the document more internally useful.

The document is already in this format. Ioana left the document in a dynamic form. Because the coding system may yet change…this is already possible as an exemplar as a use/international realm

Looking at the restricted type code… the value set is dynamically linked—meaning that the link is likely to change over time. In a different jurisdiction they may define a different set (and is not fixed)


We should attempt to excise out the few references of US-law or things of that nature, to make it easier for other realms to incorporate per Mike D

High Water mark discussion/comment: