2016-10-20 Meeting Notes (CR)

• Roll call
• Agenda bashing
• Minutes approval

• • Prior minutes requiring approval
    2016-10-13 Meeting Notes (CR)
    

    2016-10-06 Meeting Notes (CR)

    DRAFT 2016-09-29 Meeting Notes (CR)

    2016-09-22 Meeting Notes (Consent Receipts)

    2016-09-15 Meeting Notes (Consent Receipts)

    2016-09-08 Meeting Notes (Consent Receipts)

    "Move to approve listed meeting notes previously circulated"

    Motion: John W.

    Second: Jim

    Discussion: none.

    Result: Motion passes

• Funding requests to LC/Board

• This is the time of year to submit funding requests to LC and Board
• John W.
  • The CR Reader tool is needed
    • A web page script?
    • node.js ? Angular ?
    • A mobile app?
    • Other?
    • Add in some UX to the display
  • Q: Can we create a viewer that is also a conformance test?
  • A: possibly
  • A: Keeping a viewer distinct from a conformance test tool (Rule of interoperability: "Be strict in what you send and generous in what you accept")
  • ACTION: John W. to draft a proposal for discussion
• Mark
  • Also Purpose Lists
  • Also Guidance Text
  • ACTION: Mark to draft some proposal text for discussion

• Discussion on current version of CR
• Consent Receipt Specification wiki page

• David has come to terms with the term "Human Readable" - "in a form that can be naturally or easily read by a person" (dictionary)
• "Machine Readable" doesn't work - it should be "Other Encodings"
• Goal this week to make the information consumable and understandable for readers that are new to the text
• The KI-CR09.2 draft - should be ok for presentation at IIW 
• Still needs some specific information from this WG - David as Editor is unable to provide the content - it must come from WG participants
  • Consent Type: it is broken, must be addressed by the group
  • Considerations
  • Appendix A
• Note: that the ISO work has been approved as a New Work Item - so it begins the path at the Working Draft stage this week
• Note that User Submitted Terms has to feed into the content of the receipt
• Consent Type
  • The text is not a description of the Consent Receipt evidence - it's a description of the nature of the process that was used to arrive at the evidence
    • This is a frequent issue with Consent type discussions
  • Would "Consent Strength" be a useful field here? Yes, but maybe not called that - some attribute indicating the process used
  • Note: when sensitive data is involved, most laws state that the consent must be explicit.
    • For non-sensitive data other notice types and consent types could be added
  • What happens when there is an implicit consent - by the action of participating becomes implicit consent

• Discussion on IIW plans and activities

Motion: John W. circulate the 'clean' v9.2 at IIW seeking feedback and discussion.

Second: John M.

Discussion: The standalone document needs preamble for context. Who owns the responsibility for running the IIW Session? (John W.) Consider having multiple sessions for different topics. e.g. purpose lists for HIPPA from HEART WG etc.

Result: Motion carries.

• Discussion on future structure of the WG

Final draft for WG review