2016-05-16 - OBSERVABLE Meeting
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:
Attendees
Rob Hausam
Former user (Deleted)
Michael Osborne (Unlicensed)
Daniel Karlsson
Former user (Deleted)
Apologies
Farzaneh Ashrafi
Scott Campbell
Jim Campbell
Objectives
LOINC cooperation issue resolution
Recommendation for role grouping
Addressing "protein-as-proxy-for-sequence-variation" issue
Discussion items
Item | Description | Owner | Notes | Action |
|
|---|---|---|---|---|---|
1 | Welcome & apologies | Daniel Karlsson |
| Check GotoMeeting number before next session |
|
2 | Conflicts of interest | Daniel Karlsson | None stated |
|
|
3 | Previous minutes & action items | Daniel Karlsson |
|
|
|
5 | LOINC - SNOMED CT cooperation | Suzanne Santamaria Farzaneh Ashrafi Daniel Karlsson |
|
| |
4 | Daniel Karlsson | Daniel Karlsson Ask Jim Case to consider the alternatives. The group leans TOWARDS alternative 3 |
| ||
5 | Daniel Karlsson Scott Campbell Jim Campbell |
|
| ||
6 | Wellington meeting | Daniel Karlsson | Possibility to have an Observables meeting in Wellington in October | Daniel Karlsson Request full-day meeting in Wellington |
|
6 | AOB | Daniel Karlsson |
|
|
|
Meeting Files
Previous Meetings
Comments
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".
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.
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.