Difference between revisions of "FHIR Consent March 18, 2016"
| Line 1: | Line 1: | ||
| − | ==HL7 CBCC FHIR Consent Working Meeting | + | ==HL7 CBCC FHIR Consent Working Meeting== |
==Attendees== | ==Attendees== | ||
| Line 27: | Line 27: | ||
||||x||[mailto:bkinsley@nextgen.com William Kinsley] | ||||x||[mailto:bkinsley@nextgen.com William Kinsley] | ||
|- | |- | ||
| − | || | + | || x||[mailto:serafina.versaggi@gmail.com Serafina Versaggi] |
||||.||[mailto:russell.mcdonell@c-cost.com Russell McDonell] | ||||.||[mailto:russell.mcdonell@c-cost.com Russell McDonell] | ||
| − | |||| | + | ||||x||[mailto:ken.sinn@ehealthontario.on.ca Ken Sinn (Canada)] |
|- | |- | ||
| − | || | + | || x||[mailto:igor.sirkovich@rogers.com Igor Sirkovich] |
| − | |||| | + | ||||x||[mailto: Andrew Rampolla (SSA)] |
||||.||[mailto: | ||||.||[mailto: | ||
|- | |- | ||
Revision as of 20:42, 21 March 2016
HL7 CBCC FHIR Consent Working Meeting
Attendees
| Member Name | Member Name | Member Name | ||||||
|---|---|---|---|---|---|---|---|---|
| x | Johnathan ColemanCBCC Co-Chair | x | Kathleen Connor FM Co-Chair | x | John MoehrkeSecurity Co-Chair | |||
| x | Alexander Mense Security Co-Chair | . | Marty Prahl | x | Tarik Idris | |||
| x | Suzanne Gonzales-Webb CBCC Co-Chair | . | Diana Proud-Madruga | . | Pat Pyette | |||
| x | M'Lynda Owens | x | David Staggs | x | Glen Marshall | |||
| . | Rob Horn | . | Beth Pumo | x | William Kinsley | |||
| x | Serafina Versaggi | . | Russell McDonell | x | Ken Sinn (Canada) | |||
| x | Igor Sirkovich | x | [mailto: Andrew Rampolla (SSA)] | . | [mailto: |
Agenda
- (05 minutes) Agenda Review, Attendance, Approve Meeting Minutes
- (05 minutes) Review evolving document
- (05 minutes) Discuss change proposal
FHIR Consent WiKi
Review Abstract Data Model (written by David)
- David not on call to walk through
Issue of item approved by financial management
- Need to revisit
- The topic is City of Milwaukee, consent directive
- The subject is the patient or context situation child to be adopted third party interest that is being bargained over
This allows you to narrow to narrow the bounds of the consent directive
Topic is 0…many
CP - Change the name from subject to topic
- The subject: the entity impacted by the contract of intrest to the parties to the contract
- The topic: who and/or what this contract is about. The matter of consideration abot which an agreement is made which includes an offer or promise of future actions that is accepted
- Contract.subject.Defintion: The entity impacted by the contract or of interest to the parties to the contract.
We can further clarify these, without changing the words. Our clarifications have to fit in the wording found in contract.
Using the word context? we need a word that will be clear to everyone.
Context is subject of the contract. As a cleaner way of describing
Patient identifier the other holds the list of data objects (two buckets) per John.
The resource types are cues, if you want to say that this code is all medication resources the resource type medication is a value set.
Type says this term and exclude this stuff
Motion: we’re not going to worry about the …. Kathleen Motion We will come up with definitions, to be pre-applied (but--we can update in the future if needed) Topic is the subject of this contract with the caveat of we will revisit the names for clarification.
The definition of what is currently named topic… the context of the contract (Serafina / Glen) 1 abstentions, no objections motion carries with 12
Context is going to point to a set of resource or resource types. Recommend that instead of finidng the perfect word not found anywhere else, we should expand on the definition and clarify (with examples) the current word. Craft a better definition.
Pre-applied, we will not have to completelyment remove everything if we change the word
Meeting adjourned at 1300 AZT
