May 2016 CBCC Working Group Meeting - Montreal, Canada

From HL7Wiki
Revision as of 23:51, 17 May 2016 by Suzannegw (talk | contribs) (→‎Agenda and Meeting Minutes])
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

2016 May Working Group Meeting - Montreal, Canada - CBCC WORKING GROUP

Community Based Collaborative Care (CBCC) WORKING GROUP SESSIONS

Back to CBCC Wiki: Meetings

Agenda and Meeting Minutes]

Day Date Qtr Time AGENDA ITEMS Session Leader Room
SUN MAY 08 Q1 9:00-10:30 No Meeting .
Q2 11:00-12:30 No Meeting .
Q3 1:45 -3:00 No Meeting .
Q4 3:30 -5:00 No Meeting .
MON MAY 09 Q1 9:00-10:30 No Meeting .
Q2 11:00-12:30 No Meeting .
Q3/ Q4 1:45 -3:00 / 3:30-5:00 Joint CBCC - Security
  • Welcome and Introductions
  • Agenda Review
  1. Joint Project report out
  2. International Report out
  3. New Joint Project review
  • Security and Privacy advancements since last WGM, informal/around the room

NEW discussion items; NEW projects

  • FHIR Connect-a-thon Report Out/Demo(Duane DeCouteau, Mohammad Jafari): Security WG is providing a VA hosted DSTU3 FHIR Server with SLS/PPS supported natively. The servers labels out-going data on a dynamic per-request basis labeling at resource level and providing high-water mark to resource bundle. It uses a limited set of clinical sensitivity and organizational policy set. Security WG FHIR DSTU3 Server http://vha.edmondsci.com:8080/hapi15

  • Privacy Impact Assessment Project update - Suzanne
  • FHIR Consent Directive work, resolution and IG creation (report out)
  • Implementing FHIR based privacy consent using the Contract resource - Ioana
  • Address lack of US representation at Montreal WGM
CBCC Salon 5
TUE MAY 10 Q1 9:00-10:30 No Meeting . .
Q2 11:00-12:30 Privacy Impact Assessment review CBCC (tentative) Salon Garcia Lorca
Q3 1:45-3:00 FHIR Consent Directive work, resolution and IG creation (Suzanne @Security, Jim @CBCC) CBCC Salon Garcia Lorca
Q4 3:30 - 5:00 Discussion: Gap Analyss, BHS DAM vs C-CDA and FHI -Ioana

Privacy Impact Assessment continued (tentative)

. Salon Garcia Lorca
Q5 5:15-6:15 Birds of a Feather: Adding Patients and Caregivers to the Flock . Salon Drummond West
Q5 5:15-6:15 Birds of a Feather: Enterprise Architect . Salon Drummond Centre
. . . .
WED MAY 11 Q1 9:00-10:30 split-meeting Joint w/EHR, Security, CBCC, SOA, FHIR

See EHR Agenda for topics Electronic Health Records Hosting

FHIR Connect-a-thon - Security WG is providing a VA hosted DSTU3 FHIR Server with SLS/PPS supported natively. The servers labels out-going data on a dynamic per-request basis labeling at resource level and providing high-water mark to resource bundle. It uses a limited set of clinical sensitivity and organizational policyset.

Security WG FHIR DSTU3 Server http://vha.edmondsci.com:8080/hapi15

EHR Hosting Salon Drummond East
Q2 11:00-12:30
  • Co-chair administrative
  • next WGM agenda prep
CBCC Salon Garcia Lorca
Q3 1:45 -3:00
  • EHR/Vocab alignment sub-group (EHR Hosting)
EHR Hosting Salon 5
Q4 3:30 -5:00
  • Not Meeting
CBCC Room TBD
THU MAY 12 Q1 9:00-10:30 tentative FHIR Consent Profile - Discussion (CBCC-Security) see Wiki: HL7 FHIR Consent Directive Project Salon Drummond East
Q2 11:00-12:30 No Meeting .
Q3 1:45 - 3:00 No Meeting .
Q4 3:30 - 5:00 No Meeting .
FRI MAY 13 Q1 9:00-10:30 No Meeting .
Q2 11:00-12:30 No Meeting .
Q3 1:45 -3:00 No Meeting .
Q4 3:30 -5:00 No Meeting .

Back to CBCC Wiki: Meetings

Q1=9:00 – 10:30 am; Q2=11:00 – 12:30 pm; Q3=1:45 – 3:00 pm; Q4=3:30 – 5:00 pm

Back to CBCC Wiki Meetings

Business Meeting
Technical Meeting

Meeting Minutes Draft

Back to CBCC Wiki: Meetings


MON Q3 and Q4 Joint CBCC - Security

  1. Welcome and Introductions
  2. Agenda Review, approval
  3. Joint Project report out - skipped
  4. International Report out -
    • Europe
    • Japan
    • US
      • Ioana
      • Kathleen
  5. New Joint Project review
  6. Security and Privacy advancements since last WGM, informal/around the room
  7. NEW discussion items; NEW projects
    • FHIR Connect-a-thon Report Out/Demo(Duane DeCouteau, Mohammad Jafari): Security WG is providing a VA hosted DSTU3 FHIR Server with SLS/PPS supported natively. The servers labels out-going data on a dynamic per-request basis labeling at resource level and providing high-water mark to resource bundle. It uses a limited set of clinical sensitivity and organizational policy set. Security WG FHIR DSTU3 Server
    • Privacy Impact Assessment Project update - Suzanne
    • FHIR Consent Directive work, resolution and IG creation (report out)
    • Implementing FHIR based privacy consent using the Contract resource - Ioana
    • Address lack of US representation at Montreal WGM



TUE Q2

- attendees: Jim Kretz, Ken Salyards, David Pyke, Suzanne Gonzales-Webb (chair)

Privacy Impact Assessment review

TUE Q3

TUE Q4

- attendees: Jim Kretz, Ken Salyards, David Pyke, Suzanne Gonzales-Webb (chair) Ioana Singureneau, Lori Simon

FHIR Consent Directive work, resolution and IG creation (Suzanne @Security, Jim @CBCC) **confirm in minutes

Review, discussion of Draft Gap Analysts – BH DAM vs C-CDA and FHIR If we can avoid making new templates...create companion guides to use the current templates. Decision to be BH summary CDA R2 IG...to create a companion guide. How to tell implementers how use. FHIR DAF profile, our requirements (if any), there aren't anything new... if I were a BH vendor and I'm new to this, i.e. allergies--are there need for additional guidance? We want to include an example. This is how we would prove an allergy tolerance.

If there no additional guidance or new requirements in BH, we want to include an example. In some cases i.e. laboratory results. We have toxicology (in substance abuse); is it valuable to include a data set? Would there be value in the companion guide to point to a value set. Enter reference value sets (first version of toxicology observation identifiers...added/maintained as needed) LOINC has an exhaustive list that is broken down by substance being detected (in preliminary research)

  • To what extent in BH is this helpful (Lori question)
    • Presence vs absence
    • Clinical pathway of test (urine, blood, saliva, etc.)
    • LOINC code, Component, property (i.e. threshold), system method

Result: No new creation of new value set recommended by attendees, rather direct implantation to LOINC/Regenstreif, via link to toxicology

<38:00> <<link to document>> to include examples observation to gender identity and sexual orientation

WED Q1 Joint w/EHR, Security, CBCC, SOA, FHIR

WED Q2

Attendees: Ken Salyards, Jim Kretz, Ioana Singureau, David Pyke, Lori Simon, Suzanne Gonzales-Webb

MOTION: To approve the Decision Making Process (DMP) Document, 3-year Project Spreadsheet, Mission Statement, SWOT (Ioana/Jim) Opposed: none / abstain: none / approve: 5

Approved Documents have been uploaded to gForge under CBCC Administrative Folder

WED Q3 – joint with EHR

Original agenda item was to discuss the EHR Vocabulary alignment Noted confusion on whether the project is complete per Reed’s email. (see email string) <<add link to document>>, <<EHR Meeting minutes for WEDQ3>> The players for this project were not in attendance

ISO/HL7 107 1 EHRS FM Release 2 – anticipated or in progress


Attendees

CBCC Attendee MON Q3 MON Q4 Co-Chair DESD SD TUE Q1 TUE Q2 TUE Q3 TUE Q4 WED Q1 at EHR WED Q2 WED Q3 WED Q4 THU Q1
Suzanne Gonzales-WebbCBCC Co-Chair x x x x @Security x x x x x x x . . .
[mailto: Jim Kretz] CBCC Co-Chair x x . . x . . . . . . . . .
Paul Knapp FHIR . x . . . . . . . . . . . .
[mailto: MaryKay McDaniel] . x . . . .
[mailto: Hideyuki Miyohara] Mitsubishi, HL7 Japan x x . . x x x x . . .
[mailto: John Moehrke]Security Co-Chair . . . . .
[mailto: Lisa Nelson] . . . x . . .
[mailto: . . . . . . . . . . . . . .
Paul Knapp FHIR . x . . . . . . . . . . . .
[mailto: Harry Rhodes], AHIMA . . . . . .
[mailto: Ioana Singureanu] . . x . x . .
[mailto: Leslie Sistla] Microsoft . x . . . .
[mailto: Duane DeCouteau x x . . x x x x . . .
Mohammad Jafari x x . . x x x x . . .
[mailto: MON Q3 MON Q4 TUE Q1. . . . . . . . . . . .
[mailto: . . . . . . . . . . . . . .
[mailto: . . . . . . . . . . . . . .
[mailto: . . . . . . . . . . . . . .
[mailto: . . . . . . . . . . . . . .