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

Difference between revisions of "FHIR Consent November 9, 2017"

From HL7Wiki
Jump to navigation Jump to search
Line 27: Line 27:
 
||  .||[mailto:mense@technikum-wien.at Alexander Mense] Security Co-Chair
 
||  .||[mailto:mense@technikum-wien.at Alexander Mense] Security Co-Chair
 
||||.||[mailto:Kathleen_Connor@comcast.net Kathleen Connor] Security Co-Chair
 
||||.||[mailto:Kathleen_Connor@comcast.net Kathleen Connor] Security Co-Chair
||||.||[mailto:johnmoehrke@gmail.com John Moehrke]Security Co-Chair
+
||||X||[mailto:johnmoehrke@gmail.com John Moehrke]Security Co-Chair
 
||||.||[mailto:jkretz@samhsa.hhs.gov Jim Kretz] CBCC Co-Chair
 
||||.||[mailto:jkretz@samhsa.hhs.gov Jim Kretz] CBCC Co-Chair
 
|-
 
|-
 
||  .||Peter Branson
 
||  .||Peter Branson
||||.||[mailto:david.staggs@securityrs.com David Staggs]
+
||||X||[mailto:david.staggs@securityrs.com David Staggs]
 
||||.||[mailto:ksalyards@samhsa.hhs.gov Ken Salyards]
 
||||.||[mailto:ksalyards@samhsa.hhs.gov Ken Salyards]
 
||||.||[mailto:Diana.Proud-Madruga@engilitycorp.com Diana Proud-Madruga]
 
||||.||[mailto:Diana.Proud-Madruga@engilitycorp.com Diana Proud-Madruga]
Line 47: Line 47:
 
||  .||[mailto:igor.sirkovich@rogers.com Igor Sirkovich]  
 
||  .||[mailto:igor.sirkovich@rogers.com Igor Sirkovich]  
 
||||.||[mailto:ali.khan@esacinc.com Ali Khan ONC Patient Choice Project rep]
 
||||.||[mailto:ali.khan@esacinc.com Ali Khan ONC Patient Choice Project rep]
||||.||[mailto:saurav.chowdhury@esacinc.com Saurav.Chowdhury]
+
||||X||[mailto:saurav.chowdhury@esacinc.com Saurav Chowdhury]
 
||||.||[mailto:glinden@lindentechadvisors.com Greg Linden]
 
||||.||[mailto:glinden@lindentechadvisors.com Greg Linden]
 
|-
 
|-
Line 69: Line 69:
 
==Minutes==
 
==Minutes==
 
* Roll-call
 
* Roll-call
*
+
* Saurav, KC and Ali met to discuss the research use case.  Further discussions with all stakeholders forthcoming.
 +
* Aaron Seib and Graham ran a consent track last CTON.  This year focus on the technology choice (OAuth) for decisions and ceremony outputting Consent resource as documentation but not decisions.  This is not a final design. The consent resource will show the relationship that has been made but no Consent.provision would be required.

Revision as of 18:13, 9 November 2017

HL7 CBCP FHIR Consent Working Meeting

Weekly Meeting Logistics

Weekly meeting; Thursday 1:00 - 2:00 PM Eastern Time

Dial-in Number: (515) 604-9861

International Dial-in Numbers are provided

Access Code: 429554

Online Meeting Link: http://join.freeconferencecall.com/cbhs

Back to FHIR Consent Directive Project Main Page

Attendees

Member Name x Member Name x Member Name x Member Name
X David Pyke CBCC co-Chair . Johnathan Coleman CBCC Co-Chair . Suzanne Gonzales-Webb CBCC Co-Chair . Grahame Grieve FHIR Director
. Alexander Mense Security Co-Chair . Kathleen Connor Security Co-Chair X John MoehrkeSecurity Co-Chair . Jim Kretz CBCC Co-Chair
. Peter Branson X David Staggs . Ken Salyards . Diana Proud-Madruga
. Mike Davis . Neelima Chennamaraja . Ken Sinn . Beth Pumo
. Joe Lamy, Aegis . Joseph Quinn . Iona Thraen . Serafina Versaggi
. Igor Sirkovich . Ali Khan ONC Patient Choice Project rep X Saurav Chowdhury . Greg Linden
. Lisa Nelson . Hank MayersPCWG Representative . Laura Heermann Langford PCWG Co-chair . Steve Eichner


Back to FHIR Consent Directive Project Main Page

Agenda

  • Roll-call
  • Feedback on Research Use Case with ONC project
  • Consent Track for FHIR Connectathon
  • Australian Organ donation use case review
  • Review open CRs as time allows

Minutes

  • Roll-call
  • Saurav, KC and Ali met to discuss the research use case. Further discussions with all stakeholders forthcoming.
  • Aaron Seib and Graham ran a consent track last CTON. This year focus on the technology choice (OAuth) for decisions and ceremony outputting Consent resource as documentation but not decisions. This is not a final design. The consent resource will show the relationship that has been made but no Consent.provision would be required.