RESUMEN
A central tenet of reproducible research is that scientific results are published along with the underlying data and software code necessary to reproduce and verify the findings. A host of tools and software have been released that facilitate such work-flows and scientific journals have increasingly demanded that code and primary data be made available with publications. There has been little practical advice on implementing reproducible research work-flows for large 'omics' or systems biology data sets used by teams of analysts working in collaboration. In such instances it is important to ensure all analysts use the same version of a data set for their analyses. Yet, instantiating relational databases and standard operating procedures can be unwieldy, with high "startup" costs and poor adherence to procedures when they deviate substantially from an analyst's usual work-flow. Ideally a reproducible research work-flow should fit naturally into an individual's existing work-flow, with minimal disruption. Here, we provide an overview of how we have leveraged popular open source tools, including Bioconductor, Rmarkdown, git version control, R, and specifically R's package system combined with a new tool DataPackageR, to implement a lightweight reproducible research work-flow for preprocessing large data sets, suitable for sharing among small-to-medium sized teams of computational scientists. Our primary contribution is the DataPackageR tool, which decouples time-consuming data processing from data analysis while leaving a traceable record of how raw data is processed into analysis-ready data sets. The software ensures packaged data objects are properly documented and performs checksum verification of these along with basic package version management, and importantly, leaves a record of data processing code in the form of package vignettes. Our group has implemented this work-flow to manage, analyze and report on pre-clinical immunological trial data from multi-center, multi-assay studies for the past three years.
RESUMEN
BACKGROUND: The valuable clinical data, specimens, and assay results collected during a primary clinical trial or observational study can enable researchers to answer additional, pressing questions with relatively small investments in new measurements. However, management of such follow-on, "ancillary" studies is complex. It requires coordinating across institutions, sites, repositories, and approval boards, as well as distributing, integrating, and analyzing diverse data types. General-purpose software systems that simplify the management of ancillary studies have not yet been explored in the research literature. METHODS: We have identified requirements for ancillary study management primarily as part of our ongoing work with a number of large research consortia. These organizations include the Center for HIV/AIDS Vaccine Immunology (CHAVI), the Immune Tolerance Network (ITN), the HIV Vaccine Trials Network (HVTN), the U.S. Military HIV Research Program (MHRP), and the Network for Pancreatic Organ Donors with Diabetes (nPOD). We also consulted with researchers at a range of other disease research organizations regarding their workflows and data management strategies. Lastly, to enhance breadth, we reviewed process documents for ancillary study management from other organizations. RESULTS: By exploring characteristics of ancillary studies, we identify differentiating requirements and scenarios for ancillary study management systems (ASMSs). Distinguishing characteristics of ancillary studies may include the collection of additional measurements (particularly new analyses of existing specimens); the initiation of studies by investigators unaffiliated with the original study; cross-protocol data pooling and analysis; pre-existing participant consent; and pre-existing data context and provenance. For an ASMS to address these characteristics, it would need to address both operational requirements (e.g., allocating existing specimens) and data management requirements (e.g., securely distributing and integrating primary and ancillary data). CONCLUSIONS: The scenarios and requirements we describe can help guide the development of systems that make conducting ancillary studies easier, less expensive, and less error-prone. Given the relatively consistent characteristics and challenges of ancillary study management, general-purpose ASMSs are likely to be useful to a wide range of organizations. Using the requirements identified in this paper, we are currently developing an open-source, general-purpose ASMS based on LabKey Server (http://www.labkey.org) in collaboration with CHAVI, the ITN and nPOD.
Asunto(s)
Investigación Biomédica/métodos , Programas Informáticos , HumanosRESUMEN
Attenuated poxviruses have been developed for use as candidate vaccine vectors. ALVAC, a strain of the Avipoxvirus canarypox, has been extensively evaluated as a vector for vaccines against the human immunodeficiency virus type 1 (HIV-1). This report presents the safety and reactogenicity data derived from 11 multicenter, randomized controlled trials of ALVAC-HIV vaccines conducted by the HIV Vaccine Trials Network (HVTN) and its predecessor, the AIDS Vaccine Evaluation Group (AVEG). Five different ALVAC vaccine constructs were tested among 1497 volunteers. Reactogenicity was similar for different ALVAC constructs. Local reactions of any grade to ALVAC vaccines were common. However, fewer than 2% of vaccinees had severe local responses, and less than 1% experienced severe local pain or tenderness. Systemic responses were mild and transient. As combination vaccine regimens are in common use, we also evaluated side effects of ALVAC vectors given in combination with a recombinant subunit protein. No significant differences were noted in the reactogenicity of ALVAC given with or without a recombinant envelope subunit vaccine. Black, non-Hispanic and male recipients of ALVAC-HIV reported less pain following vaccination than White, non-Hispanics and females, respectively. ALVAC-HIV vaccines are well tolerated at tested doses. The reactogenicity profiles are comparable to those reported for existing vaccines licensed for use among adults. Reactogenicity does not appear to be related to the number or type of inserted genes, and did not vary between different ALVAC constructs.