Difference between revisions of "July 01, 2014 CBCC Conference Call"
(→Agenda) |
|||
Line 78: | Line 78: | ||
==Meeting Minutes== | ==Meeting Minutes== | ||
− | + | '''Johnathan Coleman announced plans to form a CBCC sub-work group to continue work on Data Provenance''' | |
+ | * CBCC sub-work group would essentially be a re-branding of the S&I Framework Data Provenance Tiger Team | ||
+ | * Possibility of using the HL7 (toll free) number for the Monday S&I Framework/HL7 CBCC Joint Data Provenance Meeting at 3 p.m. Eastern | ||
− | + | '''Johnathan also announced that the PSS for Data Provenance was approved by the TSC and is undergoing review by the DESD Steering Division''' | |
− | |||
− | |||
− | This has been reviewed by the vocabulary working group | + | '''Presentation given by Kathleen Connor on four Data Provenance harmonization proposals. CBCC attendees voted to approve all four of the proposals''' |
− | final approval; there were | + | * One proposal was to add two new codes (assembler, reviewer (person) - verifier that has specific responsibility to make sure that CDA artifact meets requirements) |
+ | ** This has been reviewed by the vocabulary working group and given final approval; there were no changes made | ||
− | + | * Another proposal was the DPROV CDA harmonizaton proposal | |
− | ** | + | ** Two additional codes for talking about the relationship for one document to another preceding document |
− | **SUCC - succeed | + | ** The two codes are two future permissible relationships (COMO/component, XCRPT/excerpts) ''approved recently'' |
− | + | ** SUCC - succeed and UPDT - update; both are not currently used in CDA but may be used in future for FHIR | |
− | + | * Kathleen advised the CBCC WG to accept recommendations from vocabulary working group | |
− | * | + | ** Keep certain ActStatus codes; they are active and not a ''state'' |
− | * | ||
− | MOTION: CBCC approve final submission of the presented | + | '''MOTION:''' CBCC approve final submission of the presented proposals--having been vetted by vocabulary (Kathleen/Johnathan) |
− | Objections: none; Abstentions: none; Motion approved: 10 | + | * Objections: none; Abstentions: none; Motion approved: 10 |
− | Discussion: | + | Discussion: How do you identify reviewer? (Jim) concern is that assembler/reviewer--how are they identified...''its this person over here'' are we looking at a name? NPI number? |
− | * | + | * The assembler is unrelated to the reviewer; they have to be in the same code system. This is a person (providers are represented by an NPI number); ideally a personal, individual provider |
+ | '''Behavioral Health Vendor Meeting''' | ||
+ | * Majority of questions were on adopting DSM-5 and what the future holds with SAMHSA | ||
+ | '''Action Items''' | ||
− | + | 20140701 Work out the logistics and finalize the dial-in and presentation information for the Monday 3 p.m. S&I Framework/HL7 CBCC Joint Data Provenance Meeting | |
− | + | '''Assigned to:''' Johnathan | |
− | |||
− | + | --[[User:Rgrow|Rgrow]] ([[User talk:Rgrow|talk]]) 15:21, 3 July 2014 (UTC) |
Revision as of 15:21, 3 July 2014
Contents
Community-Based Collaborative Care Working Group Meeting
Meeting Information
Attendees
x | Member Name | x | Member Name | x | Member Name | x | Member Name | ||||
---|---|---|---|---|---|---|---|---|---|---|---|
x | 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 | . | Daniel Crough | ||||
x | Steve Eichner | x | Rick Grow | . | Mohammed Jafari | . | Tracy Leeper | ||||
. | Lisa Nelson | x | Mike Lardiere | x | Diana Proud-Madruga | . | Harry Rhodes | ||||
. | Lori Simon | x | Ioana Singureanu | . | Tony Weida | ||||||
. | Maryann Juurlink | . | Steve Daviss | . | Kate Wetherby | x | Neelima Chennamaraja | ||||
. | Dina Passman | . | Serafina Versaggi | . | Marlowe Greenberg | . | Chris Clark, WV | ||||
. | Ken Ortbals | x | Matt Peeling | . | Nathan Botts | . | Aja Williams | ||||
. | Hady Khorasani | x | David Henkel | . | _Amanda Nash | . | Craig Winter | ||||
x | Bob Yencha |
Agenda
- (05 min) Roll Call, Approve [June 24, 2014 CBCC Conference Call]
- (15 min) Review and Request approval of Data Provenance harmonization proposals
- (15 min) Vendor Meeting - Lori Jim or Ioana
- (15 min) Formation of CBCC WG sub-work group to continue work on Data Provenance
Meeting Minutes
Johnathan Coleman announced plans to form a CBCC sub-work group to continue work on Data Provenance
- CBCC sub-work group would essentially be a re-branding of the S&I Framework Data Provenance Tiger Team
- Possibility of using the HL7 (toll free) number for the Monday S&I Framework/HL7 CBCC Joint Data Provenance Meeting at 3 p.m. Eastern
Johnathan also announced that the PSS for Data Provenance was approved by the TSC and is undergoing review by the DESD Steering Division
Presentation given by Kathleen Connor on four Data Provenance harmonization proposals. CBCC attendees voted to approve all four of the proposals
- One proposal was to add two new codes (assembler, reviewer (person) - verifier that has specific responsibility to make sure that CDA artifact meets requirements)
- This has been reviewed by the vocabulary working group and given final approval; there were no changes made
- Another proposal was the DPROV CDA harmonizaton proposal
- Two additional codes for talking about the relationship for one document to another preceding document
- The two codes are two future permissible relationships (COMO/component, XCRPT/excerpts) approved recently
- SUCC - succeed and UPDT - update; both are not currently used in CDA but may be used in future for FHIR
- Kathleen advised the CBCC WG to accept recommendations from vocabulary working group
- Keep certain ActStatus codes; they are active and not a state
MOTION: CBCC approve final submission of the presented proposals--having been vetted by vocabulary (Kathleen/Johnathan)
- Objections: none; Abstentions: none; Motion approved: 10
Discussion: How do you identify reviewer? (Jim) concern is that assembler/reviewer--how are they identified...its this person over here are we looking at a name? NPI number?
- The assembler is unrelated to the reviewer; they have to be in the same code system. This is a person (providers are represented by an NPI number); ideally a personal, individual provider
Behavioral Health Vendor Meeting
- Majority of questions were on adopting DSM-5 and what the future holds with SAMHSA
Action Items
20140701 Work out the logistics and finalize the dial-in and presentation information for the Monday 3 p.m. S&I Framework/HL7 CBCC Joint Data Provenance Meeting Assigned to: Johnathan