Large trials and studies generate many analysis results in the form of tables, figures, and written reports. Historically, a typical workflow for producing analysis results involves the end user generating the display in a static format such as RTF or PDF from the Analysis Data Model (ADaM) dataset (see Figure 1). The Analysis Results Metadata (ARM) for Define-XML (available at https://www.cdisc.org/standards/foundational/define-xml/) is then created retrospectively to provide high-level documentation about metadata relating to the analysis displays and results. However, there is no formal model or structure to describe analysis results and associated metadata, leaving a gap in standardization. The current process is expensive and time-consuming, lacks automation and traceability, and leads to unnecessary variation in analysis results reporting.
Figure 1. Example of Current Workflow
The goal for the future state of analysis results is that they are machine-readable, easily navigable, and highly reusable. The aim in creating the ARS was to provide a logical model that fully described analysis results and associated metadata to support
- automated generation of machine-readable results data;
- improved navigation and reusability of analysis and results data;
- storage, access, processing, and reproducibility of results data; and
- traceability to the study protocol, statistical analysis plan (SAP), and to the input ADaM dataset.
The ARS Model has several possible implementations, including leveraging analysis results metadata to aid in automation as well as representing analysis results as data in a dataset structure. The creation of an ARS technical specification could be used to support automation, traceability, and the creation of data displays. An analysis results dataset could support reuse and reproducibility of results data. Figure 2 is an example of how the ARS Model could be used in a modernized workflow that shifts the focus from retrospective reporting to prospective planning.
Figure 2: Example of Potential Future Workflow
First, an end user could use the ARS Model to guide the generation of a technical specification prior to generating a display, rather than after the display has been created. This approach allows for better planning and standardization of the analysis process, resulting in more consistent and traceable reporting. The technical specification could include metadata about the statistical methods, data sources, and displays to be generated. This technical specification could then be used to generate an analysis results dataset containing the results data needed to generate the display. The analysis results dataset could be designed to support reuse and reproducibility of the results data, enabling more efficient and effective analysis reporting.
Finally, the machine-readable analysis results dataset serves as the "single source of truth" capturing the analysis results metadata and results data in a standardized format. This dataset can then be used to generate displays for multiple reporting purposes, such as traditional analysis reporting for the clinical study report (CSR), in-text tables for the CSR, safety reporting, meta-analyses, dynamic applications, ClinicalTrials.gov, publications, and presentations. This streamlined approach ensures consistency and accuracy in the generation of displays across various deliverables, making it more efficient and reliable for reporting and communication of analysis results.
Overall, this new workflow allows end users to generate analysis results metadata prospectively, with greater standardization, consistency, and traceability of analysis results reporting, which in turn enables better decision making and regulatory submissions. Shifting the focus from retrospective reporting to prospective planning helps to address many of the current limitations of analysis results reporting and supports the development of more efficient and effective analysis standards.
Use of LinkML for the Development of the ARS Logical Model
Many of the same metadata components are needed both to create a prospective technical specification of analyses to be performed and to give context to reported results. Therefore, a single logical model has been developed, which includes the components needed to specify analyses, represent contextualized results, and indicate how the results are displayed.
LinkML is an open-source schema development language and framework for generating machine-readable models and downstream artifacts, including JSON-Schema, ShEx, RDF, OWL, GraphQL, and SQL DDL.
The logical model acts as a blueprint or a set of rules describing how things should be organized and structured. For the ARS, it is being used to create a model that describes how analysis results data should be organized and structured. LinkML allows the creation of a standardized and consistent approach to describing analysis results data, enabling greater interoperability and collaboration across different stakeholders. Additionally, it enables the conversion of analysis definitions and associated results data into various machine-readable formats (e.g., JSON, YAML, OWL, XML).
Further, LinkML is a flexible and extensible tool; the model can be easily modified as needed to incorporate new data elements or requirements. By creating a machine-readable model, analysis results data can be more easily understood, shared, and reused by both humans and machines. LinkML also supports the development of validation rules that can be used to ensure the integrity and quality of the data, which is essential in the highly regulated pharmaceutical industry.