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

Difference between revisions of "May 31, 2016 CBCC Conference Call"

From HL7Wiki
Jump to navigation Jump to search
Line 16: Line 16:
 
||  .|| [mailto:Max.Walker@health.vic.gov.au Max Walker]  
 
||  .|| [mailto:Max.Walker@health.vic.gov.au Max Walker]  
 
||||x|| [mailto:mike.davis@va.gov Mike Davis]  
 
||||x|| [mailto:mike.davis@va.gov Mike Davis]  
||||x|| [mailto:jmoehrke@ge.med.com John Moehrke] Security Co-Chair
+
||||x|| [mailto: John Moehrke] Security Co-Chair
 
|-
 
|-
  
 
|| x|| [mailto:Kathleen_Connor@comcast.net Kathleen Connor] Security Co-Chair
 
|| x|| [mailto:Kathleen_Connor@comcast.net Kathleen Connor] Security Co-Chair
|||||| [mailto:kenneth.salyards@samhsa.hhs.gov Ken Salyards]  
+
||||x|| [mailto:kenneth.salyards@samhsa.hhs.gov Ken Salyards]  
|||||| [mailto:LoriR.Simon@gmail Lori Simon] CBCC Interim Co-Chair
+
|||||| [mailto:LoriR.Simon@gmail Lori Simon]  
 
|-
 
|-
  
Line 34: Line 34:
 
|-
 
|-
 
||.|| [mailto:Steve.Eichner@dshs.state.tx.us Steve Eichner]
 
||.|| [mailto:Steve.Eichner@dshs.state.tx.us Steve Eichner]
||||.|| [mailto:neelimaj70@gmail.com Neelima Chennamaraja]
+
||||x|| [mailto:neelimaj70@gmail.com Neelima Chennamaraja]
 
||||.|| [mailto:Mlardieri@NSHS.edu Mike Lardiere]
 
||||.|| [mailto:Mlardieri@NSHS.edu Mike Lardiere]
 
|-
 
|-
Line 48: Line 48:
  
 
|-
 
|-
||  .|| [mailto:pknapp@pknapp.com Paul Knapp]
+
||  x|| [mailto:pknapp@pknapp.com Paul Knapp]
 
||||.|| [mailto:matt.peeling@mosaicinc.org Matt Peeling]
 
||||.|| [mailto:matt.peeling@mosaicinc.org Matt Peeling]
 
||||||  [mailto:bnewton@humecenter.org Brian Newton]
 
||||||  [mailto:bnewton@humecenter.org Brian Newton]
 
|-
 
|-
||||  [mailto:Oliver@lawless.co Oliver Lawless]
+
||x||  [mailto:Oliver@lawless.co Oliver Lawless]
 
|||||| [mailto:lisa.nelson@lantanagroup.com Lisa Nelson]
 
|||||| [mailto:lisa.nelson@lantanagroup.com Lisa Nelson]
 
||||.||[mailto:amanda.j.nash@accenturefederal.com Amanda Nash]
 
||||.||[mailto:amanda.j.nash@accenturefederal.com Amanda Nash]
Line 69: Line 69:
 
|||| [mailto:keith.boone@ge.com Keith Boone]
 
|||| [mailto:keith.boone@ge.com Keith Boone]
 
|||||| [mailto:Lori.mcneiltolley@childrens.harvard.edu Lori McNeil Tolley]
 
|||||| [mailto:Lori.mcneiltolley@childrens.harvard.edu Lori McNeil Tolley]
|||||| [
+
||||x|| [mailto: Duane DeCouteau]
  
 
|-
 
|-
.||  [mailto:mjafari@edmondsci.com Mohammed Jafari]
+
x||  [mailto:mjafari@edmondsci.com Mohammed Jafari]
 
|||||| [mailto:robert.horn@agfa.com Rob Horn]
 
|||||| [mailto:robert.horn@agfa.com Rob Horn]
 
|||||  [mailto:gary.dickinson@ehr-standards.com Gary Dickinson ]   
 
|||||  [mailto:gary.dickinson@ehr-standards.com Gary Dickinson ]   
 +
 +
x [mailto:kensinn@gmail.com Ken Sinn]
 +
x [mailto:davidpyke@readycomputing.com David Pyke]
 +
  
 
|}
 
|}

Revision as of 18:59, 31 May 2016

Community-Based Collaborative Care Working Group Meeting

Back to CBCC Main Page

Meeting Information

Attendees

Member Name x Member Name x Member Name
x Johnathan ColemanCBCC Co-Chair x Suzanne Gonzales-Webb CBCC Co-Chair x Jim Kretz CBCC Co-Chair
. Max Walker x Mike Davis x [mailto: John Moehrke] Security Co-Chair
x Kathleen Connor Security Co-Chair x Ken Salyards Lori Simon
x Diana Proud-Madruga SOA Co-Chair x Rick Grow . Harry Rhodes
. Serafina Versaggi x Ioana Singureanu x Glen Marshall
. Steve Eichner x Neelima Chennamaraja . Mike Lardiere
x Beth Pumo x M'Lynda Owens x Lee Wise
William Kinsley . Marlowe Greenberg Chris Clark, WV
x Paul Knapp . Matt Peeling Brian Newton
x Oliver Lawless Lisa Nelson . Amanda Nash
Russell McDonell Susan Litton David Bergman
. Linda Bailey-Woods Debbie Bucci Chirag Bhatt
Keith Boone Lori McNeil Tolley x [mailto: Duane DeCouteau]
x Mohammed Jafari Rob Horn Gary Dickinson

x Ken Sinn x David Pyke


Back to CBCC Main Page

Agenda

  1. (05 min) Roll Call, Approve Meeting Minutes from May 24, 2016 CBCC Conference Call
  2. (15 min) CDA R2 Implementation Guide: Privacy Consent Directives R1 (PID 553) Publication update
  3. (10 min) Behavioral Health Data Exchange CrossParadigm IG: Project 800) update Ioana (no update)
  4. (15 min) Consent Tracker Resource - request for approval to commit to build
  5. (05 min) Standards Privacy Impact Assessment (SPIA) Cookbook Update - Rick
  6. (05 min) Pass Audit Service Conceptual Model
  7. (05 min) PASS Access Control Services Conceptual Model - (Standing agenda item) update (Diana)
  8. ( min) CBCC FHIR Consent Directive
  9. next week - WGM Meeting Minutes

Consent Tracker Resource Description

Scope and Usage

  • Important decisions that patients and their personal representative make about activities or information, which concern their health and well-being, are typically captured as contractually binding permissions, obligations, and prohibitions known as Consent Directives. Consent Directives memorialize these decisions as rules specifying rights that the patient, as grantor, conveys to a grantee, such as a provider, a health app, a health plan, HIE, or clinical trial.
  • When patients and providers create and manage privacy and medical Consent Directives, including clinical trial, research, and advanced directives, three components are typically required:
  1. Paper or electronic forms in which a patient documents permissions granted or restriction limiting activities related to e.g.: patient care [aka medical consent directive], participation in clinical trials [aka research consent directive], or collection, access, use, and disclosure of information [aka privacy consent directive]
  2. The legally binding recording of a Consent Directive contract for which both the patient grantor and the data controller or processor grantee are held accountable once executed. A legally binding Consent Directive may transition a series of lifecycle stages or 'status', which may indicate e.g., whether the Consent Directive form has been signed by the patient and accepted by the grantee, whether the patient has revoked or renewed it.
  3. A means for managing or "tracking" Consent Directives at all stages in their lifecycle, from the patient, institutional, or jurisdictional policy, to an offered Consent Directive form, and on to the executed Consent Directive, which may be pended, disputed, revoked, terminated, or renewed.
  • The FHIR Consent Tracker Resource supports the third requirement by providing a flexible means for tracking and conveying intra-and inter-enterprise the lifecycle, provenance, privacy, and security metadata used for Consent Directive management workflows, such as obtaining patient authorizations and restrictions, and Consent Directive enforcement using security labeling and privacy protective services to comply with access control decisions.
  • The Consent Tracker Resource is agnostic to the media used to capture the Consent Directive. I.e., it can track the location from which an authorized user may retrieve a copy of or verification of the existence of a legally binding Consent Directive regardless of whether it is captured as a paper, scanned or otherwise unstructured representation; IHE Basic and Advanced Patient Privacy Consents; HL7 CDA Consent Directives, a FHIR Consent Directives, or the patient friendly FHIR Consent Directive form and completed instance, i.e., a FHIR Consent Directive Questionnaire and Questionnaire Response.

Meeting Minutes (DRAFT)

Meeting chaired by