This wiki has undergone a migration to Confluence found Here

October 08, 2013 Security WG Conference Call

From HL7Wiki
Jump to navigation Jump to search

Security Working Group Meeting

Back to Security Main Page

Attendees


Back to Security Main Page

Agenda

  1. (05 min) Roll Call, Approve Minutes & Accept Agenda
  2. (15 min) Ballot Reconciliation HCS - review of latest
  3. (15 min) FTSD approval link
  1. (10 min) Other Business

Meeting Minutes

Roll Call, Approve Minutes & Accept Agenda - No Security Chair present, meeting minutes not approved.

Ballot Reconciliation review

HCS - review of latest resolutions posted to [ADD LINK: Latest HCS ballot reconciliation spreadsheet]

  • for negative minors
  • 10,
  • 13 (verbiage added),
  • 12 (verbiage added),
  • 14 (explanation added to commenter);
  • 15, 16,
  • 17 (discussion of break glass)
  • 18 (comment author referred to specs)
  • 19 (question answered)
  • 20 (question answered)
  • 21 (question answered) - reuse
  • 22 (question answered)
  • 23 (question answered) custodian, not subject
  • 24 new examples will be brought over from DS4P with the correct new code

Remaining to do on reconciliation:

  • two questions from David Stumpf have not yet been answered
  • items from John Moehrke are suggestions; have been reviewed (will attempt to do via e-mail)
  • need to review with group new verbiage developed at the WGM for Clem

Ballot Reconciliation Vote has been postponed until next week when a Security Co-Chair is present

Linking FTSD approval of SLS SOA PSS Note: October 8,2013 FTSD conference call have been posted

Approved at FTSD ConCall for SLS---Next steps in SLS effort. This is the next steps to take the HCS to the next level; HCS describes the syntax/semantics of the label but it does not describe how it is to be implemented. We are coming up with a functional standard in where to pass for audit and access control that would cover the SLS and in addition the use of the reasoner to decide what the clinical back part is and which labels need to placed on per policy. How to package and do the privacy protective mechanism. That's the next step in the effort and we have a great interest on the value sets (what Ioana is doing) (and also show value of the ontology) and which labels to use.

for Ioana: We will be placing the request to understand the scope and approvals of the application and confirm our cross-references between DS4P and HCS.

Meeting adjourned at 1435

--Suzannegw 21:37, 8 October 2013 (UTC)