This wiki has undergone a migration to Confluence found Here
July 24, 2018 CBCP Conference Call
Jump to navigation
Jump to search
Attendees
| Member Name | x | Member Name | x | Member Name | x | Member Name | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| . | Johnathan ColemanCBCP Co-Chair | x | Suzanne Gonzales-Webb CBCP Co-Chair | . | 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 | . | 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
- eLTSS gForge folder: https://gforge.hl7.org/gf/project/cbcc/docman/eLTSS%20-%20%20ONC%20Electronic%20Long-Term%20Services%20and%20Supports
- Latest PSS posted to gForge [
- FHIR Consent
- FHIR CPs for review
- FHIR Consent CPs are located: link to ALL Consent Change requests
- FHIR Security Project Update - Johnathan / John Moehrke
- Weekly meeting on Tuesday - 2 PM Eastern
- https://www.freeconferencecall.com/join/security36; Phone Number: +1 515-604-9567. Participant Passcode: 880898
Meeting Minutes DRAFT
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>
