You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Study Data Tabulation Model (SDTM) developed by the Clinical
27
-
Data Interchange Standards Consortium's (CDISC) [@cdisc] is a standardised format
28
-
designed for data storage and provides a coherent framework for harmonising data
29
-
from multiple clinical trials into a common format. The Infectious Diseases Data
30
-
Observatory (IDDO), a group that has championed open-access scientific resources
31
-
in the context of poverty related infectious diseases, has developed a repository
32
-
to collate data from clinical trials for infectious diseases using SDTM as the common format.
33
-
Under STDM, data from trials are stored across several domains in a long format
34
-
linked by unique participant or study identification key. Generating analysis
35
-
ready datasets (‘analysis datasets’) requires several complex transformations of
36
-
the SDTM across different domains, which necessitates further time and resource
37
-
for the end-users.
38
-
39
-
The `iddoverse` package provides a reproducible suite of functions which allows
40
-
users to transform datasets from SDTM to analysis datasets, whilst also providing
41
-
options to customise these outputs for a range of use cases. The `iddoverse` package
42
-
is intended for epidemiologists, statisticians and data scientists with a diverse range of
43
-
programming ability, but with some familiarity with R software. Advanced knowledge
44
-
of the SDTM ontology which removes hurdles for data requesters, especially
45
-
those in Low- and Middle- Income Countries, where
46
-
SDTM training and expertise is harder to access.
47
-
48
-
The iddoverse package provides a user-friendly, replicable framework for generating
49
-
analysis datasets using IDDO’s SDTM format, whilst still allowing
50
-
analysts to modify the output. Consequently, the time spent on data manipulation
51
-
will be reduced, expediting the research, whilst also ensuring reproducibility and
52
-
increasing the accessibility of the SDTM format.
53
-
54
-
# Statement of need
55
-
56
-
Clinical studies are key elements in global scientific
57
-
research, especially for infectious diseases which disproportionately affect
58
-
communities in low- and middle-income countries (LMICs) [@iddo]. However, often
59
-
the data from these studies are analysed just once or twice.
60
-
IDDO exists to promote the reuse of
61
-
individual participant data by
62
-
curating submitted data from various sources in-house, to produce freely
63
-
available harmonised datasets, enabling scientists to answer new research
64
-
questions from existing data. In order to store the data in a centralised
65
-
database, IDDO uses the Clinical
66
-
Data Interchange Standards Consortium's (CDISC) [@cdisc] international data
67
-
standard, SDTM, where data is split into a
68
-
series of subsets called domains, each corresponding to a specific type of data.
69
-
Most domains are stored in a long data format, typically multiple rows per
70
-
participant, per day, which is burdensome to analyse and often requires
71
-
significant data manipulation to transform into a format which can then be
72
-
analysed. This also mandates a working knowledge of the SDTM format and
73
-
nomenclature, as well as, the IDDO implementation of SDTM, since IDDO has adjusted
74
-
elements of the standard in order to curate highly heterogeneous legacy data
75
-
[@iddo_KKSS]. Consequently, this creates a skill and knowledge based barrier to
76
-
accessing the data in the IDDO repository, particularly for researchers in LMICs.
77
-
78
-
Organisations and individuals have
79
-
created tools to support the transformation of SDTM to analysis datasets, such
80
-
as the pharmaverse [@pharmaverse] R [@r_core] packages, however, these do not
81
-
work for non-standard implementation of SDTM, thus, are of limited use to
82
-
requesters of the data IDDO stores. Moreover, these tools are designed for an
83
-
audience accustomed to the CDISC standards, whereas, the researchers using
84
-
the IDDO repository often are not familiar with SDTM. Other tools to generate analysis
85
-
datasets are private or subscription based business models which are not feasible
86
-
in resource limited settings. This warrants an
87
-
alternative, open source solution to solve this gap, we propose the `iddoverse` R package, a
88
-
disease agnostic transformation tool aimed at researchers using the IDDO
89
-
repository and designed to be understandable by a wide range of people
90
-
regardless of their data standard knowledge or programming ability. This will
91
-
broaden the user audience of the data IDDO holds, increasing the accessibility
92
-
of data and accelerate research by minimising the data transformation time [@patel].
93
-
94
-
# IDDO Data Lifecycle
95
-
96
-
IDDO hosts a data repository spanning multiple infectious
97
-
diseases, driven by data sharing. Investigators of clinical studies are encouraged to share their data
98
-
through a secured portal for the purpose of a specific study group aimed at
99
-
answering a particular research question of public health importance. After the data are uploaded
100
-
to the IDDO portal, the data are standardised to the
101
-
IDDO-SDTM format through a bespoke curation process. The standardised data is then
102
-
placed securely in the repository and is available as an open-access resource to
103
-
the research community. Access to the data is managed by a data access committee, which remains independent to IDDO.
104
-
Once the application is approved, the
105
-
IDDO-SDTM data are transferred securely to the data requesters. Users could then
106
-
utilise the functions in the `iddoverse` to generate analysis datasets to support their research.
107
-
108
-
# Using the iddoverse package
109
-
110
-
The package transforms
111
-
IDDO-SDTM domains from long to wider data formats, taking events, findings or tests which were
112
-
listed individually by rows per participant, and pivots them into columns, which is more typical for
113
-
analysis. This is performed on one domain at a time through the `prepare_domain()` function.
114
-
`prepare_domain()` takes a SDTM domain with often
115
-
up to 3 columns for the results and a variety of over 20 timing
116
-
variables, amalgamates the data so that there is one 'best choice' result and
117
-
timing variable, then pivot the rows by the best choice time variable, the
118
-
study id and participant number (`USUBJID`). The different events/findings/tests
119
-
then become columns and the dataset is populated with the associated result.
120
-
These best choices follow a hierarchical
121
-
list of variables, so for a given row, if the first
122
-
variable in the hierarchy list is not present, the second will be used unless that is
123
-
also empty, and so on. Customisation options include which variables to subset the output on,
124
-
whether to add a column for the method
125
-
or location of a test, changing the timing variables used or the hierarchy order
126
-
and what should happen to rows in the event that they are not uniquely separable
127
-
in the pivot process.
128
-
129
-
Additionally, the package contains functions to create
130
-
standardised analysis datasets, such as `create_participant_table()`. These use the
131
-
`prepare_domain()` function multiple times to extract specific variables from the
132
-
domains they reside in. The choice of which variables to include are based on subject
133
-
matter expertise. The purpose of
134
-
these tables is to provide most of the key information for an analysis, such as
135
-
the information typically presented in Table 1 of clinical trials.
136
-
A key limitation is that these functions cannot address every needs of the
137
-
researchers and neither it would be possible to attempt to make an all-encompassing
138
-
solution due to the large variability in the dataset within and across the diseseses.
139
-
However, these standardised tables do provide useful key information with minimal
140
-
user input, ideal for those who are not an experienced R or programming users.
141
-
142
-
`iddoverse` also contains functions to check and summarise the IDDO-SDTM
143
-
data for the user, this supports
144
-
with exploratory data analysis and can inform the choice of parameter options
145
-
within `prepare_domain`. Additionally, some utility and support functions exist
146
-
to derive or convert certain variables. Synthetic data have been
147
-
packaged within `iddoverse` to provide IDDO-SDTM examples for documentation
148
-
and can be used to gain familiarity or test the user's code whilst
149
-
awaiting the data access to be granted.
150
-
151
-
In conclusion, the `iddoverse` R package provides users of the IDDO data
152
-
repository a variety of functions and example datasets to assist their research
153
-
by speeding up data pre-processing. The package also increases the accessibility of the
154
-
repository and will allow more people to confidently use the IDDO-SDTM data, whilst minimising
155
-
duplicated effort of researchers having to code solutions to manipulate the data. Creating a range of
156
-
standardised analysis datasets from custom-SDTM implementation is shown to be possible and
157
-
`iddoverse` provides a framework for other organisations whom to do not use SDTM
158
-
for pharmaceutical regulatory submission.
26
+
Study Data Tabulation Model (SDTM) developed by the Clinical Data Interchange Standards Consortium's (CDISC) [@cdisc] is a standardised format designed for data storage and provides a coherent framework for harmonising data from multiple clinical trials into a common format. The Infectious Diseases Data Observatory (IDDO), a group that has championed open-access scientific resources in the context of poverty related infectious diseases, has developed a repository to collate data from clinical trials for infectious diseases using SDTM as the common format. Under STDM, data from trials are stored across several domains in a long format linked by unique participant or study identification key. Generating analysis ready datasets (‘analysis datasets’) requires several complex transformations of the SDTM across different domains, which necessitates further time and resource for the end-users.
27
+
28
+
The `iddoverse` package provides a reproducible suite of functions which allows users to transform datasets from SDTM to analysis datasets, whilst also providing options to customise these outputs for a range of use cases. The `iddoverse` package is intended for epidemiologists, statisticians and data scientists with a diverse range of programming ability, but with some familiarity with R software. Advanced knowledge of the SDTM ontology which removes hurdles for data requesters, especially those in Low- and Middle- Income Countries, where SDTM training and expertise is harder to access.
29
+
30
+
The iddoverse package provides a user-friendly, replicable framework for generating analysis datasets using IDDO’s SDTM format, whilst still allowing analysts to modify the output. Consequently, the time spent on data manipulation will be reduced, expediting the research, whilst also ensuring reproducibility and increasing the accessibility of the SDTM format.
31
+
32
+
# Statement of need
33
+
34
+
Clinical studies are key elements in global scientific research, especially for infectious diseases which disproportionately affect communities in low- and middle-income countries (LMICs) [@iddo]. However, often the data from these studies are analysed just once or twice. IDDO exists to promote the reuse of individual participant data by curating submitted data from various sources in-house, to produce freely available harmonised datasets, enabling scientists to answer new research questions from existing data. In order to store the data in a centralised database, IDDO uses the Clinical Data Interchange Standards Consortium's (CDISC) [@cdisc] international data standard, SDTM, where data is split into a series of subsets called domains, each corresponding to a specific type of data. Most domains are stored in a long data format, typically multiple rows per participant, per day, which is burdensome to analyse and often requires significant data manipulation to transform into a format which can then be analysed. This also mandates a working knowledge of the SDTM format and nomenclature, as well as, the IDDO implementation of SDTM, since IDDO has adjusted elements of the standard in order to curate highly heterogeneous legacy data [@iddo_KKSS]. Consequently, this creates a skill and knowledge based barrier to accessing the data in the IDDO repository, particularly for researchers in LMICs.
35
+
36
+
Organisations and individuals have created tools to support the transformation of SDTM to analysis datasets, such as the pharmaverse [@pharmaverse] R [@r_core] packages, however, these do not work for non-standard implementation of SDTM, thus, are of limited use to requesters of the data IDDO stores. Moreover, these tools are designed for an audience accustomed to the CDISC standards, whereas, the researchers using the IDDO repository often are not familiar with SDTM. Other tools to generate analysis datasets are private or subscription based business models which are not feasible in resource limited settings. This warrants an alternative, open source solution to solve this gap, we propose the `iddoverse` R package, a disease agnostic transformation tool aimed at researchers using the IDDO repository and designed to be understandable by a wide range of people regardless of their data standard knowledge or programming ability. This will broaden the user audience of the data IDDO holds, increasing the accessibility of data and accelerate research by minimising the data transformation time [@patel].
37
+
38
+
# IDDO Data Lifecycle
39
+
40
+
IDDO hosts a data repository spanning multiple infectious diseases, driven by data sharing. Investigators of clinical studies are encouraged to share their data through a secured portal for the purpose of a specific study group aimed at answering a particular research question of public health importance. After the data are uploaded to the IDDO portal, the data are standardised to the IDDO-SDTM format through a bespoke curation process. The standardised data is then placed securely in the repository and is available as an open-access resource to the research community. Access to the data is managed by a data access committee, which remains independent to IDDO. Once the application is approved, the IDDO-SDTM data are transferred securely to the data requesters. Users could then utilise the functions in the `iddoverse` to generate analysis datasets to support their research.
41
+
42
+
# Using the iddoverse package
43
+
44
+
The package transforms IDDO-SDTM domains from long to wider data formats, taking events, findings or tests which were listed individually by rows per participant, and pivots them into columns, which is more typical for analysis. This is performed on one domain at a time through the `prepare_domain()` function. `prepare_domain()` takes a SDTM domain with often up to 3 columns for the results and a variety of over 20 timing variables, amalgamates the data so that there is one 'best choice' result and timing variable, then pivot the rows by the best choice time variable, the study id and participant number (`USUBJID`). The different events/findings/tests then become columns and the dataset is populated with the associated result. These best choices follow a hierarchical list of variables, so for a given row, if the first variable in the hierarchy list is not present, the second will be used unless that is also empty, and so on. Customisation options include which variables to subset the output on, whether to add a column for the method or location of a test, changing the timing variables used or the hierarchy order and what should happen to rows in the event that they are not uniquely separable in the pivot process.
45
+
46
+
Additionally, the package contains functions to create standardised analysis datasets, such as `create_participant_table()`. These use the `prepare_domain()` function multiple times to extract specific variables from the domains they reside in. The choice of which variables to include are based on subject matter expertise. The purpose of these tables is to provide most of the key information for an analysis, such as the information typically presented in Table 1 of clinical trials. A key limitation is that these functions cannot address every needs of the researchers and neither it would be possible to attempt to make an all-encompassing solution due to the large variability in the dataset within and across the diseases. However, these standardised tables do provide useful key information with minimal user input, ideal for those who are not an experienced R or programming users.
47
+
48
+

49
+
50
+
`iddoverse` also contains functions to check and summarise the IDDO-SDTM data for the user, this supports with exploratory data analysis and can inform the choice of parameter options within `prepare_domain`. Additionally, some utility and support functions exist to derive or convert certain variables. Synthetic data have been packaged within `iddoverse` to provide IDDO-SDTM examples for documentation and can be used to gain familiarity or test the user's code whilst awaiting the data access to be granted.
51
+
52
+
In conclusion, the `iddoverse` R package provides users of the IDDO data repository a variety of functions and example datasets to assist their research by speeding up data pre-processing. The package also increases the accessibility of the repository and will allow more people to confidently use the IDDO-SDTM data, whilst minimising duplicated effort of researchers having to code solutions to manipulate the data. Creating a range of standardised analysis datasets from custom-SDTM implementation is shown to be possible and `iddoverse` provides a framework for other organisations whom to do not use SDTM for pharmaceutical regulatory submission.
159
53
160
54
# Acknowledgements
161
55
162
-
This research was supported by the Wellcome Trust [222410/Z/21/Z].
56
+
This research was supported by the Wellcome Trust [222410/Z/21/Z].
0 commit comments