This wiki has undergone a migration to Confluence found Here
Difference between revisions of "September 2008 WGM Agenda CBCC Monday Q3"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
* [mailto:david.staggs@va.gov David Staggs] | * [mailto:david.staggs@va.gov David Staggs] | ||
* [mailto:manuel.metz@sante.gouv.fr Manuel Metz] | * [mailto:manuel.metz@sante.gouv.fr Manuel Metz] | ||
− | * [mailto:Max.Walker@dhs.vic.gov.au Max Walker | + | * [mailto:Max.Walker@dhs.vic.gov.au Max Walker] |
* [mailto:Laura.Bright@bell.ca Laura Bright] | * [mailto:Laura.Bright@bell.ca Laura Bright] | ||
* [mailto:SUZANNE.L.GONZALES-WEBB@saic.com Suzanne Gonzales-Web] Chair | * [mailto:SUZANNE.L.GONZALES-WEBB@saic.com Suzanne Gonzales-Web] Chair |
Revision as of 23:49, 15 September 2008
Contents
Community-Based Collaborative Care Working Group Meeting
Attendees
- Stan Ratajczak
- Gyla Pyke
- David Staggs
- Manuel Metz
- Max Walker
- Laura Bright
- Suzanne Gonzales-Web Chair
- Bernd Blobel
- Paul Knapp
- Rob McClure
- Ioana Singureanu Scribe
- Patrick Pyette
- Mike Davis
- John Moehrke
- Marshall glen.f.marshall@siemens.com
- Kathleen Connor
- Heather Grain
- Neale Page
Updates
- CBCC documented suggested changes for reusing the common terminology including operations, document types (CDA R2), etc.Permissions Catalog: Recommendations for Reuse
- Voting closed on Composite Privacy Consent Directive
Agenda
- (05 min) Roll Call
- (05 min) Approved Minutes from September 9th, 2008 Conference Call unanimous& Accept Agenda
- (25 min) Update on the Permissions Catalog Project update
- Draft framework document was reviewed by Mike Davis - LINK TO DOCUMENT
- Project Space on HL7 Homebase: Security WG Project Space
- We cannot use the SNOMED ontology to allow a security system to infer that if an object identified by its SNOMED code is present in a permission {operation, SNOMED}, that is child object are also inculded in that permission. This would put terminology inference in the security system. The SNOMED codes are not organized based on how restricted or sensitive the information is but by how clinicians relate to it.
- (25 min)
- Consent Directive Use Cases (CBCC) - prioritize use cases. Currently the use cases focus on the the consumer but they also include the need for jurisdictions to exchange consent policy specifications.
- We will use "eConsent" as user-friendly term that will have detailed analysis and design concepts behind.
- All 8 Consent Directive Use Cases will be included in the analysis model targeted for January Ballot as follows:
- Update the Composite Privacy Consent Directive "draft for comment" based on reconciliation comments based on current use cases
- Analysis Model based on the relevant Consent Directive Use Cases
Action Item
- Ballot reconciliation
- Project Scope Statement for eConsent Project (will create a CMET to be exchanged both as messages and structured documents and can be used to describe the consent directive rules). We need to provide some deployment alternatives for consent directives relative to document and messages.
- We need further definition for the last use case in the Consent Directive Use Cases
(20 min) Consent Directive Domain Analysis Approach Deferred - Domain Analysis Approach for eConsent
--Ioana13 14:03, 9 September 2008 (UTC)