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

Difference between revisions of "June 24, 2014 Security WG Conference Call"

From HL7Wiki
Jump to navigation Jump to search
Line 76: Line 76:
 
* looking at persistence, changing labels that have been signed before--new capabilities
 
* looking at persistence, changing labels that have been signed before--new capabilities
  
* need to produce an ongoing catalog,  
+
* need to produce an ongoing catalog of these issues and discussion, guidance
* Security-FHIR page to document these items (
+
* Security-FHIR page to document these items
 +
** our position is to no use the http headers because of the white noise in the headers
 +
** if you only have a single resource and don't have an ?atom feed, then you cant...(16:00)
  
 
'''Update: Way with Verbs'''  
 
'''Update: Way with Verbs'''  
 
No feedback received
 
No feedback received

Revision as of 21:19, 24 June 2014

Meeting Information

Back to Security Main Page

Attendees

x Member Name x Member Name x Member Name x Member Name
x Mike DavisSecurity Co-chair . John MoehrkeSecurity Co-chair . Trish WilliamsSecurity Co-chair . Bernd BlobelSecurity Co-chair
. Chris Clark . Johnathan ColemanCBCC Co-Chair x Kathleen Connor x Duane DeCouteau
. Reed Gelzer x Suzanne Gonzales-WebbCBCC Co-chair . Rick Grow x David Henkel
. Mohammed Jafari . Don Jorgenson . Alexander Mense . Amanda Nash
. Paul PetronelliMobile Health Security Co-chair x Diana Proud-Madruga . Harry Rhodes , Aaron Seib
. Ioana Singureanu . Walter Suarez x Tony Weida . Paul PetronellimHealth Co-chair
. . . . . . . .


Back to Security Main Page

Agenda

  1. (05 min) Roll Call, Approval of Meeting Minutes
  2. (05 min) PSS Patient Friendly Security and Privacy
  3. (10 min) Update: Way with Verbs - Tony
  4. (10 min FHIR - Security Labeling Discussions issues
  5. (05 min) Other business, action items, and adjournment

Minutes Summary

  • Meeting Minutes from 6/17 meeting were unanimously approved by attendees. (0-0-5)


FHIR - Security Labeling Discussions issues How does Security WG weigh in on the conversation

  • make sure that John brings the conversation from FHIR into the Security WG
  • from there the Security WG can produce, define a some guidelines with respect to FHIR to preclude some of the issues (such as the http headers and that type of item)
  • consider the risk with some alternatives
  • looking at persistence, changing labels that have been signed before--new capabilities
  • need to produce an ongoing catalog of these issues and discussion, guidance
  • Security-FHIR page to document these items
    • our position is to no use the http headers because of the white noise in the headers
    • if you only have a single resource and don't have an ?atom feed, then you cant...(16:00)

Update: Way with Verbs No feedback received