This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Consent Apr 21, 2017"
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 | ||
| − | |||| | + | ||||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 | ||
|- | |- | ||
| Line 41: | Line 41: | ||
|- | |- | ||
|| .||[mailto:joe.lamy@aegis.net Joe Lamy, Aegis] | || .||[mailto:joe.lamy@aegis.net Joe Lamy, Aegis] | ||
| − | |||| | + | ||||X||[mailto:Joseph.Quinn@optum.com Joseph Quinn] |
| − | |||| | + | ||||X||[mailto:ithraen@utah.gov Iona Thraen] |
||||.||[mailto:serafina.versaggi@gmail.com Serafina Versaggi] | ||||.||[mailto:serafina.versaggi@gmail.com Serafina Versaggi] | ||
|- | |- | ||
| Line 50: | Line 50: | ||
||||.||Linda Michaelson | ||||.||Linda Michaelson | ||
|- | |- | ||
| − | || | + | || X||[mailto:Lisa.Nelson@LantanGroup.com Lisa Nelson] |
||||.||[mailto:hank.mayers@reliatechconsulting.com Hank Mayers]PCWG Representative | ||||.||[mailto:hank.mayers@reliatechconsulting.com Hank Mayers]PCWG Representative | ||
||||.||[mailto:Laura.Heermann@imail.org Laura Heermann Langford] PCWG Co-chair | ||||.||[mailto:Laura.Heermann@imail.org Laura Heermann Langford] PCWG Co-chair | ||
Latest revision as of 19:07, 21 April 2017
Contents
HL7 CBCC FHIR Consent Working Meeting
Weekly Meeting Logistics
Weekly meeting; Fridays 2:00 - 3: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 | ||||
| . | Glen Marshall | . | Tarik Idris | . | Ken Salyards | . | Diana Proud-Madruga | ||||
| . | Mike Davis | . | Neelima Chennamaraja | . | Ken Sinn | . | Beth Pumo | ||||
| . | Joe Lamy, Aegis | X | Joseph Quinn | X | Iona Thraen | . | Serafina Versaggi | ||||
| . | Igor Sirkovich | . | M'Lynda Owens | . | Mohammad Jafari | . | Linda Michaelson | ||||
| X | Lisa Nelson | . | Hank MayersPCWG Representative | . | Laura Heermann Langford PCWG Co-chair | . | Steve Eichner |
Back to FHIR Consent Directive Project Main Page
Agenda
- Roll-call
- Review Mappings to Workflow Event
Minutes
- Roll Call
- The concepts of the workflow of consent were the sole focus of discussion
- The issue was brought forward that a consent request resource may be needed. A body of work shows a need for a consentRequest resource. A person has an advanced directive. Third party request, no consent, requests consent, registry procures consent. Currently handled within the real world in an advance directive registry (MyDirective.com) via Communication Request/Communication.
- Mappings to the Event pattern should look at Consent as when gained, not when applicable
- Workflow needs to be modelled to allow completion the reasoncode/reference
- Currently, no Element showing Why consent was gained exists, to show workflow, who asked?
- In the Event pattern, the context, for consent, is that equivalent to the Policy it was executed under or the source document or the request for consent.
- While at Madrid, Ask FHIR-I, what is workflow and how would we document it? -- Comm/Req, Quest/Resp
