Added
- {func}
~ehrdata.move_to_obsand {func}~ehrdata.move_to_xare new helpers for conveniently moving variables from central 2D arrays to the.obsfield, and vice versa. (#199) @eroell - {func}
~ehrdata.dt.physionet2019as another out-of-the-box, conveniently available dataset with 40'000 ICU stays from the Physionet 2019 challenge. (#204) @eroell time_precisionparameter ("date"or"datetime") to {func}~ehrdata.io.omop.setup_variablesand {func}~ehrdata.io.omop.setup_interval_variablesfor finer temporal granularity control. (#210) @eroell
Fixed
- {func}
~ehrdata.io.read_h5adfixed issues whenbacked=True. (#199) @eroell - {func}
~ehrdata.io.read_h5adfixed bug when.XisNoneandharmonize_missing_featuresisTrue. (#206) @eroell - {func}
~ehrdata.io.omop.setup_obswithobservation_table="person_visit_occurrence"now supports multiple visits per patient, creating one row per visit with unique observation IDs, instead of failing with xarray conversion errors with non-unique indices. (#210) @eroell - OMOP time interval boundaries now use half-open intervals
[start, end)to prevent duplicate measurements at interval boundaries. (#210) @eroell
Maintenance
- Support Python3.14 (#194) @Zethson
- Address
FutureWarnings across multiple places (#200) @eroell - Enhanced tutorial structure (#208) @eroell
Modified
- Dataset generator function
ed.dt.ehrdata_blobsnow takesn_cat_varandn_categoriesarguments to generate categorical (integer encoded) time series data (#207) @sueoglu - If
enrich_var_with_feature_info=Truein {func}~ehrdata.io.omop.setup_variablesand {func}~ehrdata.io.omop.setup_interval_variables,data_table_concept_idsnot included within the concept table are now mapped from their respective alternateconcept_idincluded in the concept_relationship table to retrieve the available feature information. (#205) @KilianDahm - {func}
~ehrdata.io.omop.setup_variablesand {func}~ehrdata.io.omop.setup_interval_variableswith use of"person"now checksbirth_datetimefor meaningful behaviour and error messages. (#210) @eroell - {func}
~ehrdata.integrations.vitessce.gen_default_configprovides convenience to generate a config directly from anEHRDataobject, and should be used instead of the previousehrdata.integrations.vitessce.gen_config. (#211) @eroell