Difference between revisions of "March 10,2015 CBCC Conference Call"
| Line 84: | Line 84: | ||
* Review and vote on [http://gforge.hl7.org/gf/download/docmanfileversion/8604/12934/Lisa%20Nelson%20comment%20dispositions.xlsx Proposed ballot dispositions for Lisa Nelson's comments] | * Review and vote on [http://gforge.hl7.org/gf/download/docmanfileversion/8604/12934/Lisa%20Nelson%20comment%20dispositions.xlsx Proposed ballot dispositions for Lisa Nelson's comments] | ||
* Keith Boone's comments are only remaining comments requiring "in person" reconciliation. | * Keith Boone's comments are only remaining comments requiring "in person" reconciliation. | ||
| − | 4. Discussion on CP 5525 - Lloyd asserts that several CA systems only store the following data elements: Patient, type, applicable period, signed date, signer, organization, text. Since FHIR 80% Guideline is (1) a Guideline and not a "rule" for FHIR Resources, and NOT FHIR Profiles, such as the FHIR Consent Directive profile, (2) is about the data elements "exchanged", and not about the data elements persisted in several databases, is CBCC comfortable with a FHIR Consent Directive Profile that includes the data elements used in ''exchange'' that have historically been captured by HL7 v.2, v.3, CDA Consent Directive, HITSP TP 30, and which are now used for "exchange" in multiple jurisdictions? | + | 4. Discussion on CP 5525 - Lloyd asserts that several CA systems only store the following data elements: Patient, type, applicable period, signed date, signer, organization, text. Since FHIR 80% Guideline is (1) a Guideline and not a "rule" for FHIR Resources, and NOT FHIR Profiles, such as the FHIR Consent Directive profile, (2) is about the data elements "exchanged", and not about the data elements persisted in several databases (such as those Lloyd asserts are in several CA EHRs), is CBCC comfortable with a FHIR Consent Directive Profile that includes the data elements used in ''exchange'' that have historically been captured by HL7 v.2, v.3, CDA Consent Directive, HITSP TP 30, and which are now used for "exchange" in multiple jurisdictions? |
To see all the open items for Security/CBCC | To see all the open items for Security/CBCC | ||
http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677&tracker_query_id=4968 | http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677&tracker_query_id=4968 | ||
Revision as of 17:50, 10 March 2015
Contents
Community-Based Collaborative Care Working Group Meeting
Meeting Information
Attendees
| Member Name | x | Member Name | x | Member Name | ||||
|---|---|---|---|---|---|---|---|---|
| x | Johnathan ColemanCBCC Co-Chair | . | Mike Davis Security Co-Chair | . | Steve Eichner | |||
| x | Suzanne Gonzales-Webb CBCC Co-Chair | . | John Moehrke | . | Rita Torkzadeh | |||
| . | Jim Kretz CBCC Co-Chair | . | Lori Simon | . | Paul Knapp | |||
| . | Max Walker CBCC Co-Chair | . | Mohammed Jafari | . | Harry Rhodes | |||
| x | Kathleen Connor | . | Ioana Singureanu | . | Tony Weida | |||
| Diana Proud-Madruga | . | Steve Daviss | . | Wende Baker | ||||
| . | Serafina Versaggi | . | Marlowe Greenberg | . | Chris Clark, WV | |||
| x | Rick Grow | . | Matt Peeling | . | Brian Newton | |||
| x | Lisa Nelson | . | Mike Lardiere | . | Amanda Nash | |||
| . | Ken Salyards | . | Oliver Lawless | . | ||||
| . | Neelima Chennamaraja | . | Susan Litton | . | [mailto: Bill Kinsley] | |||
| . | [. Lloyd McKenzie] | . | [ .] | . | [. |
Agenda DRAFT
- (05 min) Roll Call, Approve Meeting Minutes from 03,_2015_CBCC_Conference_Call March 03 ]
- (25 min) Security and Privacy Patient Friendly Natural Language for Consent Directives - Update
- Review of example consent flow diagram, updates to IG
- Name Change: tentative alternative proposed for NIB: Patient Friendly Language for Healthcare Privacy and Security User Interfaces (propose that CBCC members vote on new name next CBCC meeting)
3.(20 min) Data Provenance -
- Review Proposed DPROV Informant Template
- Review and vote on Proposed ballot dispositions for Lisa Nelson's comments
- Keith Boone's comments are only remaining comments requiring "in person" reconciliation.
4. Discussion on CP 5525 - Lloyd asserts that several CA systems only store the following data elements: Patient, type, applicable period, signed date, signer, organization, text. Since FHIR 80% Guideline is (1) a Guideline and not a "rule" for FHIR Resources, and NOT FHIR Profiles, such as the FHIR Consent Directive profile, (2) is about the data elements "exchanged", and not about the data elements persisted in several databases (such as those Lloyd asserts are in several CA EHRs), is CBCC comfortable with a FHIR Consent Directive Profile that includes the data elements used in exchange that have historically been captured by HL7 v.2, v.3, CDA Consent Directive, HITSP TP 30, and which are now used for "exchange" in multiple jurisdictions? To see all the open items for Security/CBCC http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677&tracker_query_id=4968
5. (05 min) Action Item Review Should CBCC defer discusion on Lloyd's objections to FHIR Consent Directive profile (Note: this is not the one approved previously by CBCC), until the approved profile has been submitted to the continuous integration build.
6. (05 min) HL7 Implementation Guide for CDA Release 2: Privacy Consent Directives, Release 1 - Ballot Reconciliation Update
Meeting Minutes (DRAFT)
Meeting Minutes and Agenda
