Phenotype
Bases: Node
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, see documentation for Node.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
description
|
str
|
A plain text description of the phenotype. |
None
|
kwargs
|
For additional parameters, see Node. |
{}
|
Source code in phenex/phenotypes/phenotype.py
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 |
|
dependencies
property
Recursively collect all dependencies of a node (including dependencies of dependencies).
Returns:
Type | Description |
---|---|
Set[Node]
|
List[Node]: A list of Node objects on which this Node depends. |
dependency_graph
property
namespaced_table
property
A PhenotypeTable has generic column names 'person_id', 'boolean', 'event_date', and 'value'. The namespaced_table prepends 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. |
reverse_dependency_graph
property
execute(tables=None, con=None, overwrite=False, lazy_execution=False, n_threads=1)
Executes the Node computation for the current node and its dependencies. Supports lazy execution using hash-based change detection to avoid recomputing Node's that have already executed.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
tables
|
Dict[str, Table]
|
A dictionary mapping domains to Table objects. |
None
|
con
|
Optional[object]
|
Connection to database for materializing outputs. If provided, outputs from the node and all children nodes will be materialized (written) to the database using the connector. |
None
|
overwrite
|
bool
|
If True, will overwrite any existing tables found in the database while writing. If False, will throw an error when an existing table is found. Has no effect if con is not passed. |
False
|
lazy_execution
|
bool
|
If True, only re-executes if the node's definition has changed. Defaults to False. You should pass overwrite=True with lazy_execution as lazy_execution is intended precisely for iterative updates to a node definition. You must pass a connector (to cache results) for lazy_execution to work. |
False
|
n_threads
|
int
|
Max number of Node's to execute simultaneously when this node has multiple children. |
1
|
Returns:
Name | Type | Description |
---|---|---|
Table |
Table
|
The resulting table for this node. Also accessible through self.table after calling self.execute(). |
Source code in phenex/node.py
visualize_dependencies()
Create a text visualization of the dependency graph for this node and its dependencies.
Returns:
Name | Type | Description |
---|---|---|
str |
str
|
A text representation of the dependency graph |