TWIN:Phenotype
From Schemalet Wiki
Contents |
Generic phenotype datamodel
Story
The database should be able to handle phenotype measurements taken over different time points. Also it is necessary to group individual measurements together under specific measurement and classification frameworks. (ref: Litton et.al. Twin Res. 2003 Oct;6(5):383-90)
Class diagram
Description
Observation is phenotypic observation done by a specific method, which is documented under an observation framework (E.g. here GenomEUtwin specifications). Classification is inferred or classified conclusion of measurement(s) (here blood pressure). Ontology is name space (E.g. EUTwin) for used vocabulary (i.e. High blood pressure, low blood pressure) and Classification method provides information on classification spesification. Time_accuracy is needed because it is not always possible to know the time exactly (e.g. in some cases exact time cannot be given and date and month must be coded using agreed convention).
Usage
Current database implementation is based on the conceptual model. Classification methods and observation frameworks are not used. Data are also not stored as name value pairs.
Phenotype v 2.0
Description
Same model as above but the Classification is considered to be a special case of observation which is based on (or inferred from) multiple observations. Terms or names of observations are defined in specific ontology ( defined in Otology_term, which has term name and name space. See e.g. FuGE). Value class is expanded to include subtypes (this is copied from PaGE-OM)
All observations can be linked to a framework. The observation framework is conceptually same as classification method (in prev. model) and thus the relationship has been moved to super class. Classification can have hierarchies.
Usage
Not used
