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

October 14, 2014 CBCC Conference Call

From HL7Wiki
Jump to navigation Jump to search

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
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 . Kathy Odorow
x 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 x 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 October 07
  2. (10 min) Doodle Poll - New Meeting Time -
  3. (05 min) Data Provenance - Update HL7 DPROV Ballot Dispositions
  4. (10 min) Patient Friendly Natural Language - Update
  5. (05 min) Privacy Consent Directives - Ballot Reconciliation
  6. (05 min) Patient Friendly Natural Language - Ontology briefing

Meeting Minutes

Meeting Minutes from October 07.

Data Provenance - Update

Kathleen Connor shared her presentation on the Data Provenance Implementation Guide (IG) design principles. They are as follows:

  1. Maximum flexibility and modularity to support the widest array of Provenance use cases.
  2. Leverage current HL7 Provenance Patterns, in particular v2/v3 ControlAct, which conveys LifeCycle Events.
  3. Support foundational business requirements and align to the extent permitted by Clinical Document Architecture (CDA) with recommended solutions proposed by current and prospective implementers such as the NY HIE CDA Provenance Proposal.
  4. Optimize CDA R2 representation of Provenance Metadata without extension.
    1. Anticipate migrating to CDA R2.1 for increased ability to represent Provenance Metadata – e.g., Section Participant, ability to use all ActRelationshipType and ParticipationType codes available in Normative Edition 2005, additional attributes, e.g., ParticipationFunction throughout.
  5. Constrain only those CDA classes/associations minimally required to ensure capture of Provenance metadata that is otherwise supported by CDA.
    1. E.g., Custodian is already required so no need to constrain or explain further.
    2. Constrains must be testable – i.e., no indirect constraints.
    3. Templates only where the differences in the use case specific constraints require them.
    4. Each Document Template has unique constraints.
    5. Use Exemplar Templates rather than articulating every permutation or using untestable conformance statements – e.g., Observation Authored by Assembler/Device/Patient/Provider.
  6. Where CDA does not support conditional clauses, recommend Template use (SHOULD).
    1. Scoping Organization for Device as secondary Author or for Patient Generated Document.
    2. Section Assigned Author (p. 53) – Conditional = SHALL contain one or the other, and perhaps both, but not necessarily both.
  7. Minimize implementation burden while meeting use case requirements.
    1. Mandatory conformance only where minimum necessary.
    2. Recommend conformance where inclusion of the data is likely to add useful but not sufficient Provenance information.
    3. Scoping Organization Template for Patient/Device as secondary Author => SHOULD.
    4. Scoping Organization address (SHOULD).
    5. Organization ID/Name/Telecom (SHALL).
    6. Monitor DSTU comments for indications that conformance levels need adjustment.
  8. Minimize reiteration of base CDA documentation.
  9. Limit non-normative documentation to that needed for implementation.
  10. Publish introductory, background and business requirement documentation outside of the core IG in the most appropriate venue.
    1. ONC Data Provenance IG or additional HL7 Introductory Material to be published with HL7 Data Provenance CDA IG.