CombineOverlappingPeriods
CombineOverlappingPeriods
Bases: Node
CombineOverlappingPeriods takes overlapping and consecutive time periods the source table and combines them into a single time period with a single start and end date on a per patient level. For example, if a patient has two visits with the same start and end date, they will be combined into one visit. If a patient has two visits with overlapping dates, they will be combined into one visit with the earliest start date and the latest end date. If a patient has two visits with consecutive dates, they will be combined into one visit with the earliest start date and the latest end date. This is useful for creating a single time period for a patient, e.g. admission discharge periods, vaccination periods, etc. It is also useful for creating a single time period for a patient when there are multiple visits with the same start and end date, or overlapping dates.
Source code in phenex/derived_tables/combine_overlapping_periods.py
11 12 13 14 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 | |
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
execution_metadata
property
Retrieve the full execution metadata row for this node from the local DuckDB database.
Returns:
| Type | Description |
|---|---|
|
pandas.Series: A series containing NODE_NAME, LAST_HASH, NODE_PARAMS, and LAST_EXECUTED for this node, or None if the node has never been executed. |
reverse_dependency_graph
property
clear_cache(con=None, recursive=False)
Clear the cached state for this node, forcing re-execution on the next call to execute().
This method removes the node's hash from the node states table and optionally drops the materialized table from the database. After calling this method, the node will be treated as if it has never been executed before.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
con
|
Optional[object]
|
Database connector. If provided, will also drop the materialized table from the database. |
None
|
recursive
|
bool
|
If True, also clear the cache for all child nodes recursively. Defaults to False. |
False
|
Example
Source code in phenex/node.py
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
332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 | |
to_dict()
Return a dictionary representation of the Node. The dictionary must contain all dependencies of the Node such that if anything in self.to_dict() changes, the Node must be recomputed.
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 |