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

Difference between revisions of "October 07, 2014 CBCC Conference Call"

From HL7Wiki
Jump to navigation Jump to search
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
 
 
 
=Community-Based Collaborative Care Working Group Meeting=
 
=Community-Based Collaborative Care Working Group Meeting=
 
   
 
   
Line 88: Line 85:
 
==Meeting Minutes==
 
==Meeting Minutes==
  
Meeting Minutes from [http://wiki.hl7.org/index.php?title=September_09,_2014_CBCC_Conference_Call September 30] .
+
Meeting Minutes from [http://wiki.hl7.org/index.php?title=September_09,_2014_CBCC_Conference_Call September 30].
  
 
'''Privacy Consent Directives''' - Ballot Reconciliation
 
'''Privacy Consent Directives''' - Ballot Reconciliation
 +
'''MOTION (Kathleen/Diana): Proposing a Data Provenance vocabulary (Christmas hook and ornament analogy); "Provenance Assigned Device"'''
  
 
+
''ProvenanceAssignedDevice'' concept domain, codes, value set for November Harmonization
proposing (Kathleen/Diana) a Data Provenance vocabulary (Christmas hook and ornament analogy); "Provenance Assigned Device"
+
* Currently, there is no known code system outside of HL7 that does this.
ProvenanceAssignedDevice concept domain, codes, value set for November Harmonization
+
* Proposal needs to be submitted to HL7 in two weeks, leaving a few weeks for the Vocabulary WG to fine-tune/review.
* currently there is no currently known code system outside of HL7 that does--for purposes
+
* Final proposal is due in December.
* proposal needs to be submitted to HL7 in two weeks) , with a few two weeks to fine tune/reviw by Vocabulary WG
 
* final proposal by December  
 
 
Objections: 0; Abstentions: none Pass: 6
 
Objections: 0; Abstentions: none Pass: 6
  
 +
'''Patient Friendly Language''' - Kathleen
 +
Presented on the idea of a CBCC FHIR consent directive suite, explaining four things that need to happen:
 +
* FHIR PFL/Consent2Share Questionnaire Resource Profile
 +
* FHIR PFL/Consent2Share Questionnaire Answer Resource Profile
 +
* FHIR Consent Directive Resource Profile (FHIR Contract Resource)
 +
* FHIR Privacy/Security/Trust Policy Resource Profile (FHIR Contract Resource)
  
''Patient Friendly Language" - Kathleen
+
The patient part is more than just a patient friendly vocabulary GUI. It includes both detailed and high-medium-low privacy pieces. There is the notion of the pre-negotiated policies that the patient can select.
Idea of CBCC FHIR consent directive Suite, four things that need to happen = "profile suite" ; suite to support PFL project, including 'Consent2Share questionnaire Resource profile' - current FHIR Questionnaire Resource
+
   
## there are templates offered by different (21:30)... i.e. where patients are authorizing or not authorzing (consent / dissent) items to be shared. or HIPAA - implied consent
+
# '''FHIR PFL/Consent2Share 'Questionnaire Resource Profile' ''' (FHIR Questionnaire Resource): This is the basis for developing template Consent2Share forms based on FHIR Privacy Policy Resource Profile.
xxx# 'FHIR PFL/Consent2Share questionnaire answer': shows the selected answer the patient has selected (also in PFL)
+
# '''FHIR PFL/Consent2Share 'Questionnaire Answer Resource Profile' ''' (FHIR Questionnaire Answer Resource): Currently, there is a Questionnaire Resource Proposal and Patient Care decided at May 2014 WGM to create a Questionnaire Answer Resource although there is no formal proposal for it yet.  Presumably, the questionnaire is the template with the questions and possible answers while the Questionnaire Answers is an instance of the template with selected responses, which are captured in or referenced by other Resources.
xxx# FHIR Consent Directive Resource Profile
+
# '''FHIR 'Consent Directive' Resource Profile''' (FHIR Contract Resource): This is populated with Security Label encoding of a FHIR PFL/Consent2Share Questionnaire Answer instance.
xxx# FHIR Cnsent Directive Resource Profile (FHIR Contract Resourse)
+
# '''FHIR 'Privacy/Security/Trust Policy' Resource Profile''' (FHIR Contract Resource): This is an encoded policy. In the case of the FHIR CD Suite - a FHIR Privacy Policy is encoded using Security Labels, which are the basis for a FHIR PFL/Consent2Share Questionnaire Resource Profile instance.
xxx# FHIR Privacy/Security/Trust POlic Resource Profile Resource (FHIR ... Resource)
 
 
 
# Consent 2Share 'Question'
 
# FHIR PFL/Consent2Share 'Questionaire Answer' resource profile
 
# FHIR 'Consent Directive' resource profile
 
# FHIR 'Privacy/Security/Trust policy' Resource Profile
 
  
Consent as a Contract: both Bernd, MikeD in PMAC it was highly influencial in the Security/Privacy DAM  
+
* Patient Health Ecosystem where patient privacy preferences may be stipulated without parameters that are set up by HIPAA, 42 CFR Part2, Title 38 Section 7332, state privacy laws more restrictive than HIPAA and enterprise privacy policy domains to which providers and other covered entities must comply.
 +
* Enterprise Health Ecosystem where patient privacy preferences are restricted to those permissible under enterprise privacy policy domains.
 +
* CD Questionnaire questions and answers should be formulated using PFL - i.e., terms recommended for communicating health concepts to patients (e.g., Group Health Patient Health Education Resources, which has tools and PFL Word Lists).
 +
Consent as a Contract: Both Bernd, MikeD in PMAC; it was highly influential in the Security/Privacy DAM  
 
Consent will be a constraint on 'PrivacyPolicy'
 
Consent will be a constraint on 'PrivacyPolicy'
  
 +
===Doodle Poll (new meeting time options): https://doodle.com/q8f9zwmsnfpu926i Consensus reached on new time: 2 p.m. Eastern on Tuesdays. The new meeting time will go into effect next week (Tuesday, October 14).===
  
Doodle Poll (new meeting time options): https://doodle.com/q8f9zwmsnfpu926i
+
Meeting Adjourned at 1103 PDT

Latest revision as of 14:30, 14 October 2014

Community-Based Collaborative Care Working Group Meeting

Back to CBCC Main Page

Meeting Information

Attendees

x Member Name x Member Name x Member Name x Member Name
. Johnathan ColemanCBCC Interim Co-Chair x Suzanne Gonzales-Webb CBCC Co-Chair x Jim KretzCBCC Interim Co-Chair . Max WalkerCBCC Co-Chair
. Wende Baker . Bill Braithwaite, MD x Kathleen Connor . Kathy Odorow
. Steve Eichner x Rick Grow . Paul Knapp . Mohammed Jafari
. Lisa Nelson . Mike Lardiere x Diana Proud-Madruga . Harry Rhodes
x Lori Simon . Ioana Singureanu . Tony Weida . Tim McKay, Kaiser
. Maryann Juurlink . Steve Daviss . Kate Wetherby . Neelima Chennamaraja
. Dina Passman x Serafina Versaggi . Marlowe Greenberg . Chris Clark, WV
. Ken Ortbals . Matt Peeling . Tracy Leeper . Brian Newton
. Hady Khorasani . Amanda Nash . Ken Salyards . _Bob Yencha
x Rita Torkzadeh . . . _ . _


Agenda

  1. (05 min) Roll Call, Approve Meeting Minutes from Sept 30
  2. (05 min) Data Provenance - Update
  3. (10 min) Doodle Poll - New Meeting Time -
  4. (10 min) Patient Friendly Natural Language - Update
  5. (10 min) CBCC WGM September Agenda Meeting Minutes
  6. (05 min) Privacy Consent Directives - Ballot Reconciliation
  7. (05 min) Patient Friendly Natural Language - Ontology briefing

Meeting Minutes

Meeting Minutes from September 30.

Privacy Consent Directives - Ballot Reconciliation MOTION (Kathleen/Diana): Proposing a Data Provenance vocabulary (Christmas hook and ornament analogy); "Provenance Assigned Device"

ProvenanceAssignedDevice concept domain, codes, value set for November Harmonization

  • Currently, there is no known code system outside of HL7 that does this.
  • Proposal needs to be submitted to HL7 in two weeks, leaving a few weeks for the Vocabulary WG to fine-tune/review.
  • Final proposal is due in December.

Objections: 0; Abstentions: none Pass: 6

Patient Friendly Language - Kathleen Presented on the idea of a CBCC FHIR consent directive suite, explaining four things that need to happen:

  • FHIR PFL/Consent2Share Questionnaire Resource Profile
  • FHIR PFL/Consent2Share Questionnaire Answer Resource Profile
  • FHIR Consent Directive Resource Profile (FHIR Contract Resource)
  • FHIR Privacy/Security/Trust Policy Resource Profile (FHIR Contract Resource)

The patient part is more than just a patient friendly vocabulary GUI. It includes both detailed and high-medium-low privacy pieces. There is the notion of the pre-negotiated policies that the patient can select.

  1. FHIR PFL/Consent2Share 'Questionnaire Resource Profile' (FHIR Questionnaire Resource): This is the basis for developing template Consent2Share forms based on FHIR Privacy Policy Resource Profile.
  2. FHIR PFL/Consent2Share 'Questionnaire Answer Resource Profile' (FHIR Questionnaire Answer Resource): Currently, there is a Questionnaire Resource Proposal and Patient Care decided at May 2014 WGM to create a Questionnaire Answer Resource although there is no formal proposal for it yet. Presumably, the questionnaire is the template with the questions and possible answers while the Questionnaire Answers is an instance of the template with selected responses, which are captured in or referenced by other Resources.
  3. FHIR 'Consent Directive' Resource Profile (FHIR Contract Resource): This is populated with Security Label encoding of a FHIR PFL/Consent2Share Questionnaire Answer instance.
  4. FHIR 'Privacy/Security/Trust Policy' Resource Profile (FHIR Contract Resource): This is an encoded policy. In the case of the FHIR CD Suite - a FHIR Privacy Policy is encoded using Security Labels, which are the basis for a FHIR PFL/Consent2Share Questionnaire Resource Profile instance.
  • Patient Health Ecosystem where patient privacy preferences may be stipulated without parameters that are set up by HIPAA, 42 CFR Part2, Title 38 Section 7332, state privacy laws more restrictive than HIPAA and enterprise privacy policy domains to which providers and other covered entities must comply.
  • Enterprise Health Ecosystem where patient privacy preferences are restricted to those permissible under enterprise privacy policy domains.
  • CD Questionnaire questions and answers should be formulated using PFL - i.e., terms recommended for communicating health concepts to patients (e.g., Group Health Patient Health Education Resources, which has tools and PFL Word Lists).

Consent as a Contract: Both Bernd, MikeD in PMAC; it was highly influential in the Security/Privacy DAM Consent will be a constraint on 'PrivacyPolicy'

Doodle Poll (new meeting time options): https://doodle.com/q8f9zwmsnfpu926i Consensus reached on new time: 2 p.m. Eastern on Tuesdays. The new meeting time will go into effect next week (Tuesday, October 14).

Meeting Adjourned at 1103 PDT