OHDSI Home | Forums | Wiki | Github

HADES development announcements

Capr v2.0.7 has been released. Move CirceR to remotes section to pass HADES weekly checks. Pausing efforts to submit to CRAN due to this change.

ResultModelManager v0.5.0 has been released.
This includes a new utility class for exporting results in a validated way as well as some changes to the result model specification support (removing the use of the “emptyIsNa” field).

Please see the change log for a full list of changes.

CohortDiagnostics version 3.2.4 . This is a hotfix to
support newer versions of OhdsiShinyModules which have a minor API change.

Please check the release notes for details of changes.

SqlRender 1.16.0 has been released. This includes various minor bugfixes and updates.

SqlRender 1.16.1 has been released. Most important change is a bugfix and a workaround for issues caused by 1.16.0.

DataQualityDashboard 2.4.1 has been released. The release contains some minor updates to documentation; improvements to remote DB tests; and a patch to address a dependency issue.

2 Likes

SelfControlledCaseSeries 5.0.0 has been released. This major release is focused on adjusting for temporal trends. Some important innovations:

  1. Better diagnostic for temporal stability.
  2. Option to automatically restrict study time to when the drug was on the market (i.e. the time it was observed in the database).
  3. Ability to define multiple study periods. The main use case is excluding the time of the COVID-19 pandemic, when most clinical events show temporal instability.

DeepPatientLevelPrediction 2.0.1 has been released. This is mostly a bug fix release and improvements to the documentation based on feedback from the HADES hackathon.

DataQualityDashboard v2.5.0 has been released. This release contains a new function contributed by @Jared - thanks very much Jared for your work on this and for helping to get this merged in at the HADES Hackathon :partying_face:

The new function, writeDBResultsToJson, can be used to export DQD results from a database table into a JSON file. Multiple folks have requested this feature so I’m super happy that Jared took the initiative to add it in!

This release also contains some bugfixes including fixing some queries that were broken for users who store their vocab in a separate schema from the CDM, and allowing DQD to run even if the CDM_SOURCE table has multiple rows (previously it was throwing an error).

CohortExplorer 0.1.0 got released a few weeks ago. This version is also in cran CRAN - Package CohortExplorer

New functionality that adds a ‘Feature Cohort’ domain based on instantiated cohorts. Useful for case adjudication. Use case example: look for 1 symptom cohort of dyspnea vs every concept for dyspnea while adjudicating a pneumonia cohort.

ResultModelManager v0.5.2 has been released.
This hotfix is to allow support for PooledConnectionHandlers to allow configurable DBI connection parameters allowing driver specification.

Please see the change log for a full list of changes.

DatabaseConnector 6.3.0 has been released. This contains minor improvements and bugfixes, and finally runs unit tests on all supported database platforms.

1 Like

FeatureExtraction 3.3.2 has been released. It is a bugfix release.

Andromeda 0.6.4 has been released on github and should be on CRAN soon. This is a patch release.

DatabaseConnector 6.3.1 has been released. This contains two minor bugfixes.

DeepPatientLevelPrediction 2.0.2 has been released. This is mostly a bugfix with some refactoring.

DatabaseConnector 6.3.2 has been released. This fixes a small bug introduced in 6.3.1 causing an error when inserting tables while Andromeda was not installed.

SelfControlledCaseSeries 5.1.0 has been released. This update includes various improvements when running large number analyses (e.g. when performing risk discovery).

1 Like

CohortMethod 5.2.0 has been released. This release focus on generalizability, by comparing the population after all adjustments (e.g. PS matching) to the population before all adjustments, and report any characteristics that have changed.

The choice of population to consider for generalizability is now driven by your analysis choices. For example, if you use PS matching, (implying ATT), generalizability will be computed for the target (treated) population.

EmpiricalCalibration 3.1.2 has been released. This includes 2 minor bugfixes handling edge cases.

t