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

March 30th, 2010 Security Conference Call

From HL7Wiki
Revision as of 17:31, 30 March 2010 by Suzannegw (talk | contribs)
Jump to navigation Jump to search

Security Working Group Meeting

Back to Security Main Page

Attendees

Back to Security Main Page


Agenda

  1. (05 min) Roll Call, Approve Minutes (To Be Posted Soon) & Accept Agenda
  2. (45 min) Update of Ongoing Projects
    1. Security and Privacy Ontology Project - (Mike) true version can be found on GForge. Will be discussed at next TSC meeting. Discussion at TSC meeting on which ontology to use. Some termoniolgy models in the current DAM that might provide discussion. The terminologists may propose a process to move forward to include Berndt and Cecil and develop the requirements for the ontology effort.

(Steve) have been listenting to the SOA ontology and they have been favoring Protege ontology tool (as well as BFO Basic Formal Ontology www.ifomif.org/bfo as upper level ontology). We should keep aware of the status of this as it is preferred we stay in line with SOA.

The TSC approved the  Security and Privacy Ontology Project:

excerpt from e-mail sent on 3/30/2010: (from Lynn Lasko of HL7) · Security and Privacy Ontology Project for Security Work Group [WG] of Foundation and Technology Steering Division [FTSD] (TSC Issue # 1478 – Status=Closed; Project Insight ID= 646). This project will develop a domain ontology encompassing the healthcare IT security and privacy domains providing a single, formal vocabulary embodying the concepts in each domain as well as concepts shared between the two. The concepts identified and defined in this ontology will be primarily drawn from those concepts contained in the Security and Composite Privacy DAMs. The concepts in this ontology will be extended in order to bridge to standard ontologies in associated domains such as enterprise architecture, clinical care and biomedicine. (Rob) We will need specific use case to clearly cover our spectrum of use, phrases, concepts (to which BFO will not be necessary as an ontology)

    1. Security and Privacy DAM Harmonized Security and Privacy DAM Consolidated Peer Review Comments
  1. (5 min) Other Business

Action Items

Back to Security Main Page