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

HL7 FHIR Security 2018-07-03

From HL7Wiki
Jump to navigation Jump to search

Call Logistics

Weekly: Tuesday at 02:00 pm EST

Web conference desktop and VOIP 
Online Meeting ID: security36
Phone: +1 515-604-9567, Participant Code: 880898
 Please be aware that teleconference meetings are recorded to assist with creating the meeting minutes 

Back to HL7 FHIR security topics


Member Name Member Name Member Name
x John Moehrke Security Co-Chair x Kathleen Connor Security Co-Chair . Alexander Mense Security Co-chair
. Suzanne Gonzales-Webb CBCC Co-Chair . Johnathan Coleman CBCC co-chair . Chris Shawn Security co-chair
. Jim Kretz x Kenneth Salyards . Nathan Botts Mobile co-chair
. Diana Proud-Madruga x Joe Lamy AEGIS x Beth Pumo
. Irina Connelly . Matt Blackman Sequoia . Mark Underwood NIST
. Peter Bachman . Grahame Greve FHIR Program Director . Kevin Shekleton (Cerner, CDS Hooks)
x Luis Maas . Julie Maas . Francisco Jauregui
. Gary Dickinson . Dave Silver . Foo Bar




Block Vote

  • 14027 enhance+current+disclosure+AuditEvent+so+that+it+explains+what+is+being+recorded+and+why (John Moehrke) Not Related
  • 15659 Provenance+still+has+both+identifier+and+reference+elements (Simone Heckmann) Persuasive
  • 16345 Link+to+obsoleted+version+of+HTTP+specification (Luis Maas) Persuasive
  • 17412 AuditEvent+still+has+both+Identifier+and+Reference (John Moehrke) Persuasive
  • 17413 AuditEvent.source+should+be+a+Reference+not+just+an+Identifier (John Moehrke) Persuasive

Current Open issues in gForge


  • John Chaired
  • Agenda
    • Kathleen would like to review a proposal for the Safety Checklist
  • approval of HL7 FHIR Security 2018-06-05 and HL7 FHIR Security 2018-06-12 and HL7 FHIR Security 2018-06-26 Minutes
    • Motion to approve all three: Kathleen Connor/Ken Salyards: 5-0-0
  • Review Block Vote
    • Motion to approve the block vote: Ken Salyards/Kathleen Connor: 5-0-0
  • Kathleen review of proposal for Safety Checklist
    • arrange them into logical groups
    • adding a few security and privacy items
    • ACTION to the group to review her proposal
    • We will discuss next week, and forward to FHIR-I as a consensus recommendation from Security WG
    • We should expect that FHIR-I will take it as advice, but they have the final say.
    • *Feedback for Safety Checklist