Page tree

Date

2016-05-16 20.00 UTC

GoToMeeting Details

https://global.gotomeeting.com/join/201313901

I get an error starting the meeting! Will start a join.me session in a sec!

USE THIS INSTEAD:

https://join.me/473-077-130

Objectives

  • LOINC cooperation issue resolution
  • Recommendation for role grouping
  • Addressing "protein-as-proxy-for-sequence-variation" issue

Discussion items

ItemDescriptionOwnerNotesAction 
1Welcome & apologiesDaniel Karlsson
  • Remember recording!
  • Check GotoMeeting number before next session
 
2Conflicts of interestDaniel KarlssonNone stated  
3Previous minutes & action itemsDaniel Karlsson   
5

LOINC - SNOMED CT cooperation

Suzanne Santamaria

Farzaneh Ashrafi

Daniel Karlsson

 
  •  
 
4Recommendation for role groupingDaniel Karlsson
  •  

  • Daniel Karlsson Ask Jim Case to consider the alternatives. The group leans TOWARDS alternative 3

 

5Protein as a proxy for sequence variation

Daniel Karlsson

Scott Campbell

James R. Campbell

 
  •  
 
6Wellington meetingDaniel KarlssonPossibility to have an Observables meeting in Wellington in October  
6AOBDaniel Karlsson 

 

 

Meeting Files

No files shared here yet.


 

3 Comments

  1. One of the above items on the agenda is about the different ways that the COMPONENT attribute is role grouped in Procedures and Observables. There was some discussion about the idea of creating two different COMPONENT roles, one for use with Observables and the other for use with Procedures. Although the TOWARD attribute by itself continues to seem rather confusing because it is "overloaded," I wonder what the group would think about addressing this issue by adding three different sub-roles, such as TOWARD COMPONENT, TOWARD DISPOSITION, and TOWARD REALIZATION. TOWARD COMPONENT could be used with Observables, while "plain" COMPONENT could be used with Procedures.

  2. I'll just throw this out there... Perhaps since we are trying to describe the "Feature of an entity", we should call the attribute "feature component". 

  3. Since the context of use is implied in the hierarchy they are used with, what is the advantage of creating two attributes? Each addition of a new attribute makes consistent modeling more difficult to obtain.