HOME
DOCUMENTATION
1) Upload patient data
2) Upload visit data
3) Upload diagnosis data
4) Upload diagnosis descr.
5) Group diagnoses
6) Define diagnoses pairs
7) Define comorbidity analysis parameters
8) Start comorbidity analysis
Ⓒ 2018,
GNU AFFERO v3
Integrative Biomedical Informatics Group, GRIB
Comorbidity4web: interactive comorbidity analysis on the web
Comorbidity4web is a Web-based java tool aimed at enabling the analyses of disease comorbidity in an interactive manner, by means of Web visualizations (
example of comorbidity analysis result
). Comorbidity analysis can be executed:
on-line
: by means of the Comorbidity4web, from this web page;
locally on your workstation
: by means of
Comorbidity4j, the Java library that powers Comorbidity4web
. To download Comorbidity4j Java library and obtain instructions for local execution of comorbidity analyses, access the
Comorbidity4j documentation
. Comorbidity analyses executed by Comorbidity4j expects the same input data and produce the same set of interactive Web visualizations generated by Comorbidity4web, but data are processed and results are stored locally to the user workstation. In this way it si possible to enforce a greater data privacy or to exploit more powerful workstations.
Start comorbidity analysis!
How Comorbidity4web works?
Comorbidity4web supports the identification and analysis of significant co-occurrences of diagnoses over large datasets of patient data, using as input patient demographic information (birth-date together with, optionally gender and secondary patient features like education level, ethnicity, etc.) and the history of diagnoses of a set of patients over time. everal statistical measures to identify relevant pairs of co-occurring diagnoses are computed over the patients' data provided as by the user, and a variety of interactive graphical representations are provided to visualize and analyze the results.
The web interface of Comorbidity4web constitutes the gateway to set-up, execute and access the results of comorbidity analyses performed by this tool.
In particular, from this Web interface Comorbidity4web users can:
interactively upload and validate all the clinical data needed to execute the comorbidity analysis
. Input data should be provided by the user by means of a set of tabular datasets (i.e. CSV, TSV - UTF-8-encoded text files) presented in more details below in this page;
fine tune different parameters to customize the analysis of comorbidities
, like strategies to group and pair diagnoses occurring in the input data or approaches to filter the results of the analysis;
execute the analysis and explore the results
. To this purpose a set of interactive Web-based visualization are generated on the flight. The results of comorbidity analysis can be also downloaded as a zip file including these data in CSV format and as standalone Web visualizations.
Browse the
Comorbidity4j documentation
for more info.
What input data are required to execute a comorbidity analysis by Comorbidity4web?
On the column on the left side the different steps to set-up an analysis of comorbidities are listed. They include:
Steps 1 to 4
: uploading and validation of user’s input data, provided by means of a set of tabular datasets (i.e. CSV, TSV - UTF-8-encoded text files)
Steps 5 to 7
: customization of parameters of the comorbidity analysis
It is possible to
download an example dataset
generated by
Synthea
to inspect the input tabular files that Comorbidity4web expects as input to execute a comorbidity analysis and try the tool. In particular, considering the steps 1 to 3, the following three tabular datasets (i.e. CSV, TSV - UTF-8-encoded text files) are required in order to execute a comorbidity analysis:
Patient data
(step 1): a tabular dataset (
download example file
) where each row represents a single patient by specifying, in different columns, the
patient_id
,
patient_birth_date
and, optionally, the
patient_gender
and
other patient variables or facets
required to stratify patients.
Visit data
(step 2): a tabular dataset (
download example file
) where each row characterizes a single visit of a patient by specifying, in different columns, the
patient_id
, the
visit_id
and the
visit_date
.
Diagnosis data
(step 3): a tabular dataset (
download example file
) where each row describes the association of a diagnosis (by a diagnosis code - i.e. ICD9, SNOMED-CT, CUI or any other diagnosis identifier) to a specific patient in a particular visit. These three parameters are provided by specifying, in different columns, the
patient_id
, the
visit_id
and the
diagnosis_code
.
The
Diagnosis description
tabular dataset (step 4,
download example file
) is an optional data input, used to provide a free-text description to the diagnosis codes.
When each tabular dataset is uploaded, the user will be asked to interactively define the semantics of each column of the tables, the formats of dates and other parameters of interest to correctly interpret user’s input data. Different column separators and text delimiters are supported.
More details and examples of these tabular dataset are provided interactively while loading data.