Phenotype
A phenotype is a description of the state of a person at a specific time.
In Phenex, phenotypes are implemented using the Phenotype class. The Phenotype class is designed so that there is clear separation between the "what" from the "how". The "what" is expressed in the Phenotype init function: what codelists to use, what time range to include, constraints relative to other Phenotype's, visit detail information to include, etc. The "what" is meant to mirror how we normally talk about real-world data studies.
The translation of this description in actual executable code (the "how") is handled via the Phenotype.execute()
method. The execute method returns a PhenotypeTable - the realization of the defined Phenotype in a particular database. See execute()
for details.
All Phenotype's in Phenex derive from the Phenotype class.
To subclass
- Define the parameters required to compute the Phenotype in the
__init__()
interface. - Within
__init__()
, defineself.children
- a list of Phenotype's which must be executed before the current Phenotype, allowing Phenotype's to be chained and executed recursively. - Define
self._execute()
. Theself._execute()
method is reponsible for interpreting the input parameters to the Phenotype and returning the appropriate PhenotypeTable. - Define tests in
phenex.test.phenotypes
! We demand a high level of test coverage for our code. High test coverage gives us confidence that our answers are correct and makes it easier to make changes to the code later on.
Source code in phenex/phenotypes/phenotype.py
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 |
|
namespaced_table
property
A PhenotypeTable has generic column names 'person_id', 'boolean', 'event_date', and 'value'. The namespaced_table appends the phenotype name to all of these columns. This is useful when joining multiple phenotype tables together.
Returns:
Name | Type | Description |
---|---|---|
table |
Table
|
The namespaced table for the current phenotype. |
_execute(tables)
Executes the phenotype processing logic.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
tables
|
Dict[str, Table]
|
A dictionary where the keys are table names and the values are Table objects. |
required |
Raises:
Type | Description |
---|---|
NotImplementedError
|
This method should be implemented by subclasses. |
Source code in phenex/phenotypes/phenotype.py
execute(tables)
Executes the phenotype computation for the current object and its children. This method recursively iterates over the children of the current object and calls their execute method if their table attribute is None.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
tables
|
Dict[str, PhenexTable]
|
A dictionary mapping table names to PhenexTable objects. See phenex.mappers.DomainsDictionary.get_mapped_tables(). |
required |
Returns:
Name | Type | Description |
---|---|---|
table |
PhenotypeTable
|
The resulting phenotype table containing the required columns. The PhenotypeTable will contain the columns: PERSON_ID, EVENT_DATE, VALUE. DATE is determined by the return_date parameter. VALUE is different for each phenotype. For example, AgePhenotype will return the age in the VALUE column. A MeasurementPhenotype will return the observed value for the measurement. See the specific phenotype of interest to understand more. |