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

Difference between revisions of "September 7th, 2010 Security Conference Call"

From HL7Wiki
Jump to navigation Jump to search
Line 24: Line 24:
 
No update today, but this ballot is now open.  Please sign up to vote.
 
No update today, but this ballot is now open.  Please sign up to vote.
 
====Security & Privacy Ontology Project====
 
====Security & Privacy Ontology Project====
 +
#LOINC to RBAC discussion:
 +
#*This discussion related to examining the LOINC objects to determine which map to HL7 permission catalog and how they would map to SNOMED CT.
 +
#*The purpose is to determine how we will use the ontology to link a different ontology (a bridge ontologies—which we may use or SNOMED CT directly)
 +
#*Question: Is this a new ontology vs. an update to the current ontology? 
 +
#**Yes, we wouldn’t’ necessary put these items in the RBAC catalog directly — instead we should be able to map these terms to the various linkages, e.g., to SNOMED-CT.
 +
#*The premise is that the relationship to SNOMED-CT has been harmonized to LOINC.  Mike will check with the VA terminologies to confirm this assumption.
 +
 +
 +
 +
 +
 
Tony has posted the [http://gforge.hl7.org/gf/download/docmanfileversion/5828/7511/Ontologies.zip first draft] of the Security-Privacy Ontology expressed in OWL 2 and suitable for viewing with the Protégé 4.1 OWL Editor.
 
Tony has posted the [http://gforge.hl7.org/gf/download/docmanfileversion/5828/7511/Ontologies.zip first draft] of the Security-Privacy Ontology expressed in OWL 2 and suitable for viewing with the Protégé 4.1 OWL Editor.
 
*In addition, for those who are not using Protégé, there is a [http://gforge.hl7.org/gf/download/docmanfileversion/5829/7512/HL7SecurityandPrivacyOntologyUpdate.doc Word document] with screen shots and other information.
 
*In addition, for those who are not using Protégé, there is a [http://gforge.hl7.org/gf/download/docmanfileversion/5829/7512/HL7SecurityandPrivacyOntologyUpdate.doc Word document] with screen shots and other information.

Revision as of 15:53, 13 September 2010

Security Working Group Meeting

Back to Security Main Page

Attendees

Agenda

  1. (05 min) Roll Call, Accept Minutes August 31st Security Work Group, Call for additional agenda items & Accept Agenda
  2. (05 min) Pat Pyette - PASS Audit Update
  3. (05 min) John Moehrke - John’s updates regarding the Risk Assessment
  4. (50 min) Security and Privacy Ontology project

Minutes

1. Action Items

  • Tony: Request administrative privileges to update GForge.
    • Mike to approve once request has been submitted

2. Resolutions - none

3. Updates/Discussion

PASS Audit Update

No update today, but this ballot is now open. Please sign up to vote.

Security & Privacy Ontology Project

  1. LOINC to RBAC discussion:
    • This discussion related to examining the LOINC objects to determine which map to HL7 permission catalog and how they would map to SNOMED CT.
    • The purpose is to determine how we will use the ontology to link a different ontology (a bridge ontologies—which we may use or SNOMED CT directly)
    • Question: Is this a new ontology vs. an update to the current ontology?
      • Yes, we wouldn’t’ necessary put these items in the RBAC catalog directly — instead we should be able to map these terms to the various linkages, e.g., to SNOMED-CT.
    • The premise is that the relationship to SNOMED-CT has been harmonized to LOINC. Mike will check with the VA terminologies to confirm this assumption.



Tony has posted the first draft of the Security-Privacy Ontology expressed in OWL 2 and suitable for viewing with the Protégé 4.1 OWL Editor.

  • In addition, for those who are not using Protégé, there is a Word document with screen shots and other information.
    • Corresponding wiki entries will be made after Tony Weida obtains proper wiki access.
    • Tony will pass along files to Serafina and Suzanne until he is able to post on GForge.
    • Tony will make a request to join the HL7 Security GForge space. Mike can then approve the addition.

Back to Security Main Page