This wiki has undergone a migration to Confluence found Here
Difference between revisions of "October 14th 2008 CBCC Conference Call"
Jump to navigation
Jump to search
(→Agenda) |
(→Agenda) |
||
| Line 22: | Line 22: | ||
* We may need to revisit the Reason terminology in the future but the [http://hl7projects.hl7.nscee.edu/docman/view.php/57/273/Data%20Consent%20Vocabulary%201.2.pdf Vocabulary proposal was approved in August 2008]. | * We may need to revisit the Reason terminology in the future but the [http://hl7projects.hl7.nscee.edu/docman/view.php/57/273/Data%20Consent%20Vocabulary%201.2.pdf Vocabulary proposal was approved in August 2008]. | ||
* The concept domain for '''Overrider.functionCode''' should refer to the functional role in an enterprise not the provider taxonomy code | * The concept domain for '''Overrider.functionCode''' should refer to the functional role in an enterprise not the provider taxonomy code | ||
| + | * Functional roles are dependent on how a user is involved in a certain clinical act. A structural role may be connected to licensure and may be specified for a end-user in the context of an organization. | ||
| + | |||
[[Community-Based_Collaborative_Care|Back to Meetings]] | [[Community-Based_Collaborative_Care|Back to Meetings]] | ||
Latest revision as of 19:04, 14 October 2008
Contents
Community-Based Collaborative Care Working Group Meeting
Meeting Information
Attendees
- Suzanne Gonzales-Webb Chair
- Richard Thoreson
- Rob McClure
- Frank Din
- Ioana Singureanu Scribe
- John Moehrke
- Kathleen Connor
- Dave Carlson
Agenda
- (05 min) Roll Call
- (05 min) Approve Minutes 8-0-0 & Accept Agenda (Ioana/Richard) 8-0-0
- Frank Din has analyzed Vocabulary Domains used in the normative Data Consent R1. These vocabulary domains and their associated bindings wll be reused by the Composite Privacy Consent Specification
- We may need to revisit the Reason terminology in the future but the Vocabulary proposal was approved in August 2008.
- The concept domain for Overrider.functionCode should refer to the functional role in an enterprise not the provider taxonomy code
- Functional roles are dependent on how a user is involved in a certain clinical act. A structural role may be connected to licensure and may be specified for a end-user in the context of an organization.
