0.1.0 🌈 Release

Added

• {func}~ehrdata.move_to_obs and {func}~ehrdata.move_to_x are new helpers for conveniently moving variables from central 2D arrays to the .obs field, and vice versa. (#199) @eroell
• {func}~ehrdata.dt.physionet2019 as another out-of-the-box, conveniently available dataset with 40'000 ICU stays from the Physionet 2019 challenge. (#204) @eroell
• time_precision parameter ("date" or "datetime") to {func}~ehrdata.io.omop.setup_variables and {func}~ehrdata.io.omop.setup_interval_variables for finer temporal granularity control. (#210) @eroell

Fixed

• {func}~ehrdata.io.read_h5ad fixed issues when backed=True. (#199) @eroell
• {func}~ehrdata.io.read_h5ad fixed bug when .X is None and harmonize_missing_features is True. (#206) @eroell
• {func}~ehrdata.io.omop.setup_obs with observation_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_blobs now takes n_cat_var and n_categories arguments to generate categorical (integer encoded) time series data (#207) @sueoglu
• If enrich_var_with_feature_info=True in {func}~ehrdata.io.omop.setup_variables and {func}~ehrdata.io.omop.setup_interval_variables, data_table_concept_ids not included within the concept table are now mapped from their respective alternate concept_id included in the concept_relationship table to retrieve the available feature information. (#205) @KilianDahm
• {func}~ehrdata.io.omop.setup_variables and {func}~ehrdata.io.omop.setup_interval_variables with use of "person" now checks birth_datetime for meaningful behaviour and error messages. (#210) @eroell
• {func}~ehrdata.integrations.vitessce.gen_default_config provides convenience to generate a config directly from an EHRData object, and should be used instead of the previous ehrdata.integrations.vitessce.gen_config. (#211) @eroell