This wiki has undergone a migration to Confluence found Here
Difference between revisions of "July 24, 2018 CBCP Conference Call"
Jump to navigation
Jump to search
| Line 63: | Line 63: | ||
==Meeting Minutes DRAFT== | ==Meeting Minutes DRAFT== | ||
| + | Chair - Dave Pyke | ||
| + | eLTSS | ||
| + | * Lynne - publishing folks - any other that we need to do | ||
| + | ** they frown upon ballotable material publicly; so items will not be posted on the CBCP wiki | ||
| + | ** no other specific instructions were given to get ready for ballot | ||
| − | additional e-mail discussion: | + | * uploading items to the wiki; need to delete some information |
| − | David Pyke been asked to put forward this statement for voting as a motion to the group clarifying our stance on consent in FHIR | + | ** hesitating to upload spreadsheet; until |
| − | <quote> | + | * owed to CBCP a final version with executive summary; once ready Irina will provide once ready |
| − | * The Consent resource is the correct (and best) way to store and exchange computable consent agreements in a FHIR environment | + | |
| − | * Formal consent documents are contracts and you may use the Contract resource to capture that aspect of them for attachment to the Consent resource as a source document. | + | FHIR Consent |
| − | * While Consent information may sometimes be found in DocumentReference, Binary, Contract and other resources, Consent is the principle resource for representing consent-related information and is the endpoint where systems should expect to find this information | + | |
| − | <endquote> | + | CPs items to vote on |
| + | |||
| + | four have been dealt with one way or another; | ||
| + | # CP 15581 - Motion: Suzanne / Jim Vote on disposition as displayed | ||
| + | #* vote: abstentions: none; against: none; approval: 11 | ||
| + | # CP 15641 | ||
| + | #* followed up with Michelle with no response | ||
| + | #* wish to close as not persuasive Motion made: Jim / Suzanne | ||
| + | #* Abstention: none; Against: none; Approval: 11 | ||
| + | # 17154 Search parameters | ||
| + | #* Securitylabel to security-label (must have dash) Motion: Jim/Suzanne | ||
| + | #* Vote: abstentions: none; against: none; Approval: 11 | ||
| + | # CP 14181 | ||
| + | #* items have been elimated - could not be mapped to v3 RIM (they are not found in v3 RIM | ||
| + | #* | ||
| + | # CP 11069 (already resolved) | ||
| + | #* suggest to close as this is based on an older version | ||
| + | |||
| + | ''' ''NEW DISCUSSION:'' ''' | ||
| + | additional e-mail discussion: | ||
| + | David Pyke been asked to put forward this statement for voting as a motion to the group clarifying our stance on consent in FHIR | ||
| + | <quote> | ||
| + | * The Consent resource is the correct (and best) way to store and exchange computable consent agreements in a FHIR environment | ||
| + | * Formal consent documents are contracts and you may use the Contract resource to capture that aspect of them for attachment to the Consent resource as a source document. | ||
| + | * While Consent information may sometimes be found in DocumentReference, Binary, Contract and other resources, Consent is the principle resource for representing consent-related information and is the endpoint where systems should expect to find this information | ||
| + | <endquote> | ||
| + | |||
| + | |||
| + | Given to DAvid by Grahame and Lloyed on FHIR Resource - usage of various resources and their use in FHIR | ||
Revision as of 16:21, 24 July 2018
Attendees
| Member Name | x | Member Name | x | Member Name | x | Member Name | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| . | 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 | x | Mike Davis | . | John Moehrke Security Co-Chair | . | Diana Proud-Madruga | ||||
| x | Chris Shawn | . | Neelima Chennamaraja | . | Joe Lamy | . | Greg Linden | ||||
| . | Irina Connelly | . | Saurav Chowdhury | . | Dave Silver | x | Francisco Jauregui | ||||
| x | Mark Meadows | . | Amber Patel | x | Becky Angeles | . | Jennifer Brush | ||||
| . | Mohammad Jafari | . | Ali Khan | . | Ken Salyards | . | Michael Gu | ||||
| . | David Staggs | . | Bonnie Young | . | Ioana Singureanu | x | Beth Pumo |
Agenda
- Roll Call, Agenda Review
- Meeting Minutes approval: none to approve at this time
- eLTSS Update - Irina / Becky
- eLTSS NIB submitted before Sunday deadline
- PSS - CBCP Approval (Ken Lord)
- Privacy - Is privacy Obsolete update - Mike Davis
- FHIR Consent
- FHIR CPs for review
- FHIR Consent CPs are located: link to ALL Consent Change requests
Meeting Minutes DRAFT
Chair - Dave Pyke
eLTSS
- Lynne - publishing folks - any other that we need to do
- they frown upon ballotable material publicly; so items will not be posted on the CBCP wiki
- no other specific instructions were given to get ready for ballot
- uploading items to the wiki; need to delete some information
- hesitating to upload spreadsheet; until
- owed to CBCP a final version with executive summary; once ready Irina will provide once ready
FHIR Consent
CPs items to vote on
four have been dealt with one way or another;
- CP 15581 - Motion: Suzanne / Jim Vote on disposition as displayed
- vote: abstentions: none; against: none; approval: 11
- CP 15641
- followed up with Michelle with no response
- wish to close as not persuasive Motion made: Jim / Suzanne
- Abstention: none; Against: none; Approval: 11
- 17154 Search parameters
- Securitylabel to security-label (must have dash) Motion: Jim/Suzanne
- Vote: abstentions: none; against: none; Approval: 11
- CP 14181
- items have been elimated - could not be mapped to v3 RIM (they are not found in v3 RIM
- CP 11069 (already resolved)
- suggest to close as this is based on an older version
NEW DISCUSSION:
additional e-mail discussion: David Pyke been asked to put forward this statement for voting as a motion to the group clarifying our stance on consent in FHIR <quote> * The Consent resource is the correct (and best) way to store and exchange computable consent agreements in a FHIR environment * Formal consent documents are contracts and you may use the Contract resource to capture that aspect of them for attachment to the Consent resource as a source document. * While Consent information may sometimes be found in DocumentReference, Binary, Contract and other resources, Consent is the principle resource for representing consent-related information and is the endpoint where systems should expect to find this information <endquote>
Given to DAvid by Grahame and Lloyed on FHIR Resource - usage of various resources and their use in FHIR
