Sourced from the CFDE-CC Documentation Wiki
Association between a subject and a Human Phenotype Ontology term
For subjects with phenotype metadata, this table will have one row for each phenotype associated with each such subject, along with an association_type
field distinguishing "phenotype present" from "phenotype specifically ruled out."
All fields are required: this table can be empty (header-row only), but any non-header rows must leave no fields blank.
Some examples:
Field | Field Description | Required? | Field Value Type | Extra Info |
---|---|---|---|---|
subject_id_namespace | Identifier namespace for this subject [part 1 of 4-component composite primary key] | Required | string | This will be the value of id_namespace in the row in subject.tsv corresponding to the subject referenced in this row. If your program has not registered multiple CFDE identifier namespaces, this will be exactly the same value for all rows. |
subject_local_id | The ID of this subject [part 2 of 4-component composite primary key] | Required | string | This will be the value of local_id in the row in subject.tsv corresponding to the subject referenced in this row. |
association_type | An indicator distinguishing "phenotype present" from "phenotype ruled out" [part 3 of 4-component composite primary key] | Required | one of cfde_phenotype_association_type:0 (meaning "phenotype ruled out")orcfde_phenotype_association_type:1 (meaning "phenotype observed") | |
phenotype | A valid Human Phenotype Ontology term [part 4 of 4-component composite primary key] | Required | string | Human Phenotype Ontology lookup Examples: HP:0000349 , HP:0012425 |