This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "October 28th 2008 Security Conference Call"

From HL7Wiki
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 23: Line 23:
 
:Notes from Presentation
 
:Notes from Presentation
 
:* Group is agreed in using only 'consent directive' rather than both 'consent directive and personal preference' as shown in presentation.
 
:* Group is agreed in using only 'consent directive' rather than both 'consent directive and personal preference' as shown in presentation.
:* Create a 'value set' from vocabulary
+
:* Discussion of a 'value set' from vocabulary but no decision made
:* Extend current RBAC Vocabulary with respect to semantic interoperability, wherein the model can be defined and is context
+
:* Extend current RBAC Vocabulary with respect to semantic interoperability, wherein the model can be defined and be in context
 
#''(15 min)'' [http://hl7projects.hl7.nscee.edu/docman/view.php/59/411/Copy%20of%20Constraint%20Catalog%20Example.%20-%20DRAFT.xlsx Constraint Catalog Example]
 
#''(15 min)'' [http://hl7projects.hl7.nscee.edu/docman/view.php/59/411/Copy%20of%20Constraint%20Catalog%20Example.%20-%20DRAFT.xlsx Constraint Catalog Example]
  
  
 
[[Security|Back to Meetings]]
 
[[Security|Back to Meetings]]

Latest revision as of 17:24, 18 November 2008

Attendees

Agenda & Meeting Minutes

  1. (05 min) Roll Call
  2. (05 min) Approve Minutes & Accept Agenda (10-0-0 Mike D/John M)
  3. (35 min) Deliverable Goal - Updating the HL7 RBAC Permission Catalog - addition of Privacy and Consent vocabulary as Constraints Role Engineering Process to create a Constraint Catalog
Notes from Presentation
  • Group is agreed in using only 'consent directive' rather than both 'consent directive and personal preference' as shown in presentation.
  • Discussion of a 'value set' from vocabulary but no decision made
  • Extend current RBAC Vocabulary with respect to semantic interoperability, wherein the model can be defined and be in context
  1. (15 min) Constraint Catalog Example


Back to Meetings