This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Consent April 29, 2016"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 37: | Line 37: | ||
||||.||[mailto:jafarim@gmail.com Mohammad Jafari (VA/ESC)] | ||||.||[mailto:jafarim@gmail.com Mohammad Jafari (VA/ESC)] | ||
|- | |- | ||
| − | || ||[mailto: ] | + | || x||[mailto:Kenneth.salyards@samhsa.hhs.gov Ken Salyards] |
||||||[mailto:] | ||||||[mailto:] | ||
||||.||[mailto: ] | ||||.||[mailto: ] | ||
| Line 60: | Line 60: | ||
*John explained how Narrative works, and noted the precautions about not including text related to referenced Resources, as these may change independently. So guidance is to keep Narrative text high level and of a nature that a user could locate a ConsentDirective of interest by viewing a Narrative description in e.g., a drop-down box. | *John explained how Narrative works, and noted the precautions about not including text related to referenced Resources, as these may change independently. So guidance is to keep Narrative text high level and of a nature that a user could locate a ConsentDirective of interest by viewing a Narrative description in e.g., a drop-down box. | ||
*Kathleen reviewed updates to description on use of ConsentDirective.topic datatypes. In particular, the effort to provide guidance about the need to ensure aligned conceptual space if using more than one ConsentDirective.topic datatype, e.g., both a Resource reference and a string name for the topic. | *Kathleen reviewed updates to description on use of ConsentDirective.topic datatypes. In particular, the effort to provide guidance about the need to ensure aligned conceptual space if using more than one ConsentDirective.topic datatype, e.g., both a Resource reference and a string name for the topic. | ||
| + | * Two instances of of a consent under contract created by Ioana (per Ken), | ||
| + | ** Share-All Consent and Segmented Consent. Information will be sent to Kathleen/John for review/confirmation they are going in the right direction. | ||
*Call schedule changes discussed: No meetings from May 6 - May 20. Calls resume on May 27. | *Call schedule changes discussed: No meetings from May 6 - May 20. Calls resume on May 27. | ||
*CBCC WGM agenda: Plan is to include an opportunity during Thursday May 12 Q 1 to review the entire spreadsheet for approval to include in the ballot build. | *CBCC WGM agenda: Plan is to include an opportunity during Thursday May 12 Q 1 to review the entire spreadsheet for approval to include in the ballot build. | ||
Latest revision as of 20:31, 29 April 2016
Contents
HL7 CBCC FHIR Consent Working Meeting
Back to FHIR Consent Directive Project Main Page
Attendees
| Member Name | Member Name | Member Name | ||||||
|---|---|---|---|---|---|---|---|---|
| . | Johnathan ColemanCBCC Co-Chair | x | Kathleen Connor FM Co-Chair | x | John MoehrkeSecurity Co-Chair | |||
| . | Alexander Mense Security Co-Chair | . | Jim Kretz | . | Tarik Idris | |||
| x | Suzanne Gonzales-Webb CBCC Co-Chair | . | Diana Proud-Madruga | . | Pat Pyette | |||
| . | M'Lynda Owens | x | David Staggs | . | Glen Marshall | |||
| Rob Horn | Beth Pumo | William Kinsley | ||||||
| . | Serafina Versaggi | . | Russell McDonell | x | Ken Sinn (Canada) | |||
| x | Igor Sirkovich | . | [mailto: Andrew Rampolla (SSA)] | . | Mohammad Jafari (VA/ESC) | |||
| x | Ken Salyards | [mailto:] | . | [mailto: ] |
Back to FHIR Consent Directive Project Main Page
Agenda
- Agenda Review, Attendance, Approve FHIR CD April 22 Meeting Minutes
- Whether and How to add Narrative to Contract/ConsentDirective
- Updates to the FHIR Consent Directive per earlier decisions See Tab 1] in FHIR Contract Consent Directive spreadsheet
For Discussion
- ISO TS 17975 Principles and data requirements for consent in the Collection, Use or Disclosure of PHI Annex A for Consent Framework Diagrams. Extremely useful for discussing generic consent topics.
- Tarik asked for example of how a CD instance would look with Consent Directive Types. See Kathleen's strawcritter for how FHIR ConsentDirective profile could support Ioana's list of requirements.
- An earlier BPPC FHIR CD instance - see Spreadsheet Tab 17.
Meeting Minutes DRAFT
- Suzanne cochaired. Agenda approved by consenus. April 22 Minutes approved 5-0-0 [John moved, Ken Salyards seconded]
- John explained how Narrative works, and noted the precautions about not including text related to referenced Resources, as these may change independently. So guidance is to keep Narrative text high level and of a nature that a user could locate a ConsentDirective of interest by viewing a Narrative description in e.g., a drop-down box.
- Kathleen reviewed updates to description on use of ConsentDirective.topic datatypes. In particular, the effort to provide guidance about the need to ensure aligned conceptual space if using more than one ConsentDirective.topic datatype, e.g., both a Resource reference and a string name for the topic.
- Two instances of of a consent under contract created by Ioana (per Ken),
- Share-All Consent and Segmented Consent. Information will be sent to Kathleen/John for review/confirmation they are going in the right direction.
- Call schedule changes discussed: No meetings from May 6 - May 20. Calls resume on May 27.
- CBCC WGM agenda: Plan is to include an opportunity during Thursday May 12 Q 1 to review the entire spreadsheet for approval to include in the ballot build.
