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

Difference between revisions of "March 13, 2018 CBCP Conference Call"

From HL7Wiki
Jump to navigation Jump to search
Line 50: Line 50:
 
|-
 
|-
 
||  x|| [mailto:irina.connolly@gtri.gatech.edu Irina Connelly]
 
||  x|| [mailto:irina.connolly@gtri.gatech.edu Irina Connelly]
−
||||.|| [mailto:saurav.chowdhury@esacinc.com Saurav Chowdhury]
+
||||x|| [mailto:saurav.chowdhury@esacinc.com Saurav Chowdhury]
−
||||.|| [mailto:dave.silver@electrosoft.com Dave Silver]
+
||||x|| [mailto:dave.silver@electrosoft.com Dave Silver]
 
||||x|| [mailto:fjauregui@electrosoft.com Francisco Jauregui]
 
||||x|| [mailto:fjauregui@electrosoft.com Francisco Jauregui]
 
|-
 
|-
Line 57: Line 57:
 
||||x|| [mailto:ayp@securityrs.com Amber Patel]
 
||||x|| [mailto:ayp@securityrs.com Amber Patel]
 
||||.|| [mailto:becky.angeles@carradora.com Becky Angeles]
 
||||.|| [mailto:becky.angeles@carradora.com Becky Angeles]
−
||||.||  
+
||||.|| Jennifer.brush@esacinc.com; patricia.peretz@gmail.com patricia.peretz@gmail, Saurav, beth
 
|}
 
|}
  
Line 76: Line 76:
  
 
===Minutes===
 
===Minutes===
 +
CBCP FHIr Thursday
 +
* cancelled FHIR consent weekly meetings
 +
** System is in QA lock
 +
** the number of issues have been small; we have been getting started on Release 4
 +
* Current issues in GForge
 +
** from Patient Care #
 +
* After the release, PC would like to add link to Consent Resource where consent was captures; we would add an element to the top level where "consent.context" where consent was captured
 +
** we have avoided being a part of the signing ceremony - 'that's not our thing' bu tthis is a specific request
 +
** how do people feel about that?
 +
*** what if the consent isnt' captured - it would be an optional field, or insome other way (for their workflow idea - we have time
 +
*** if we don't do that--where is consent located now?  is it a separate entitiy; if we don't require consent to be part of the encounter; this may cause confsion where the dating is backwards
 +
**** - the encounter can point to consent; if we want to permit/denty to the data--then that's lower down; this is specific to the workflow of having a way to linking back to the consent (where it was granted) it would also be in the source document/signed document 'questionnaire document' we do have a way of where the dating is captured--but still specific to the encounter
 +
**This is very specific to wanted to be a part of a workflow
 +
* rESULT : David will leave this alone for now--more questions are necessary
 +
 +
# 15645 fromPC above
 +
# 15693 - john moehrke
 +
* dave will talk to him about this one related to his blog entry
 +
 +
currently on hold for FHIR changes - some severe changes; do not want to map something if there are additional changes
 +
 +
 +
FHIR
 +
At the Security WG - ONC Report
 +
Key privacy considereation for API's - posted to CBCC workgroup
 +
* contained recommendations , publics related to sync for scinec project; where SFS were able to participation in privacy assessment and best practices for S&P using Api mechanisms for access their healthcare; this is update and update the best best practices and review data received; which have not been updated for a white... bsed on real world findings , we feel these are high level and general in natioante.. discussion will
 +
 +
5PM easter using the same dial Security information 0
 +
 +
No questions.
 +
 +
Mini Dam - BH
 +
TF4FA -
 +
some changes made during the PSAF call - to better align with the pass acs; call out
 +
changes to the model on PSAF on SecurityWG call; we will need to go forward with what we have - we haven't receive dany negative
 +
its
 +
looking at basic policy
 +
 +
Meeting adjourned at 9:26 Arizona Time --[[User:Suzannegw|Suzannegw]] ([[User talk:Suzannegw|talk]]) 12:24, 13 March 2018 (EDT)

Revision as of 16:24, 13 March 2018

Community-Based Care and Privacy (CBCP) Working Group Meeting

Back to CBCP Main Page

Meeting Information

Dial-in Number:  (515) 604-9861;  Access Code: 429554
* Online Meeting Link: http://join.freeconferencecall.com/cbhs  
* Click on Join an Online Meeting Enter Online Meeting ID:  cbhs 
* Follow prompts if not automatically connected

Please be aware that teleconference meetings are recorded to assist with creating meeting minutes

Back to CBCP Main Page

Attendees

Member Name x Member Name x Member Name x Member Name
x Johnathan ColemanCBCP Co-Chair x Suzanne Gonzales-Webb CBCP Co-Chair x Jim Kretz CBCP Co-Chair x David Pyke CBCP Co-Chair
x Kathleen Connor Security Co-Chair . Mike Davis . John Moehrke Security Co-Chair . Diana Proud-Madruga
. Mohammed Jafari . Ali Khan . Ken Salyards . Ken Sinn
x David Staggs . Steve Eichner . Ioana Singureanu x Beth Pumo
. Chris Shawn x Neelima Chennamaraja . Joe Lamy . Greg Linden
x Irina Connelly x Saurav Chowdhury x Dave Silver x Francisco Jauregui
. x Amber Patel . Becky Angeles . Jennifer.brush@esacinc.com; patricia.peretz@gmail.com patricia.peretz@gmail, Saurav, beth

Back to CBCP Main Page

Agenda

  1. Roll Call, Agenda Review
  2. (5 min) CBCP FHIR THURSDAY call at 1:00 ET // FHIR Consent Directive Project Wiki, Main page
  3. FHIR Security Project Update - Johnathan
  4. (10 min) Security and Privacy DAM - update, discussion Meeting weekly on Thursdays 11:00 AM ET Meeting Link: http://www.hl7.org/concalls/CallDetails.aspx?concall=38423
  5. January 2018 CBCP Working Group Meeting - New Orleans, Louisiana, USA
    • Approve Meeting Minutes for February 27 NOT COMPLETE, (move to next week)
    • Approve Meeting Minutes for February 20 NOT COMPLETE, (move to next week)
    • Approve Meeting Minutes for February 13 NOT COMPLETE, (move to next week)

Minutes

CBCP FHIr Thursday

  • cancelled FHIR consent weekly meetings
    • System is in QA lock
    • the number of issues have been small; we have been getting started on Release 4
  • Current issues in GForge
    • from Patient Care #
  • After the release, PC would like to add link to Consent Resource where consent was captures; we would add an element to the top level where "consent.context" where consent was captured
    • we have avoided being a part of the signing ceremony - 'that's not our thing' bu tthis is a specific request
    • how do people feel about that?
      • what if the consent isnt' captured - it would be an optional field, or insome other way (for their workflow idea - we have time
      • if we don't do that--where is consent located now? is it a separate entitiy; if we don't require consent to be part of the encounter; this may cause confsion where the dating is backwards
        • - the encounter can point to consent; if we want to permit/denty to the data--then that's lower down; this is specific to the workflow of having a way to linking back to the consent (where it was granted) it would also be in the source document/signed document 'questionnaire document' we do have a way of where the dating is captured--but still specific to the encounter
    • This is very specific to wanted to be a part of a workflow
  • rESULT : David will leave this alone for now--more questions are necessary
  1. 15645 fromPC above
  2. 15693 - john moehrke
  • dave will talk to him about this one related to his blog entry

currently on hold for FHIR changes - some severe changes; do not want to map something if there are additional changes


FHIR At the Security WG - ONC Report Key privacy considereation for API's - posted to CBCC workgroup

  • contained recommendations , publics related to sync for scinec project; where SFS were able to participation in privacy assessment and best practices for S&P using Api mechanisms for access their healthcare; this is update and update the best best practices and review data received; which have not been updated for a white... bsed on real world findings , we feel these are high level and general in natioante.. discussion will

5PM easter using the same dial Security information 0

No questions.

Mini Dam - BH TF4FA - some changes made during the PSAF call - to better align with the pass acs; call out changes to the model on PSAF on SecurityWG call; we will need to go forward with what we have - we haven't receive dany negative its looking at basic policy

Meeting adjourned at 9:26 Arizona Time --Suzannegw (talk) 12:24, 13 March 2018 (EDT)

Retrieved from "https://wiki.hl7.org/w/index.php?title=March_13,_2018_CBCP_Conference_Call&oldid=154496"