Designing common data models that support RWE across indications



Designing Common Data Models that Support RWE Across Indications

Published on 04/12/2025

Designing Common Data Models that Support RWE Across Indications

In the rapidly evolving landscape of healthcare data, designing common data models that support real-world evidence (RWE) across indications is critical for effective regulatory submissions and health outcomes research. This tutorial provides a step-by-step guide for regulatory, biostatistics, HEOR, and data standards professionals in pharma and medtech to navigate the complexities of data standards such as CDISC, SDTM, ADaM, and HL7/FHIR. Establishing a clear framework is essential for ensuring compliance and optimizing the utilization of RWE in regulatory settings.

Understanding the Importance of Data Standards in RWE

Data standards play a pivotal role in harmonizing the collection, management, and reporting of healthcare information. With the

growing emphasis on RWE in regulatory decision-making, understanding relevant data standards is paramount. This section covers the basics of RWE, the integral role of data standards, and the specific standards mentioned.

What is Real-World Evidence?

Real-World Evidence refers to the clinical evidence derived from the analysis of real-world data (RWD)—data collected outside of traditional clinical trials. It encompasses information relating to patient health status and the delivery of healthcare. Regulatory bodies, particularly the US Food and Drug Administration (FDA), are increasingly recognizing RWE for its potential to inform treatment paradigms, approve new indications, and support post-marketing surveillance.

Core Data Standards for RWE

  • CDISC (Clinical Data Interchange Standards Consortium): This organization develops data standards that streamline the collection and sharing of health research data.
  • SDTM (Study Data Tabulation Model): A standardized format for submitting clinical trial data to regulatory authorities.
  • ADaM (Analysis Data Model): Provides a standard structure for datasets used in the preparation of statistical analyses.
  • HL7/FHIR (Fast Healthcare Interoperability Resources): A standard for exchanging healthcare information electronically.
See also  Governance for data sharing agreements between hospitals and app vendors

CDISC Compliance: Establishing Frameworks for Data Submission

Compliance with CDISC standards is essential for ensuring that the data submissions are credible and can be easily interpreted by regulatory authorities. Key to establishing compliance are comprehensive training, proper tool usage, and systematic processes.

Steps to Achieve CDISC Compliance

  1. Training and Education: Ensure that all relevant team members are well-versed in CDISC standards and their implications for data management and regulatory submissions. Numerous resources, including webinars and workshops, are available through both CDISC and external organizations.
  2. Tool Utilization: Make use of available tools designed to facilitate compliance with CDISC standards. This can include statistical software that supports SDTM compliance, as well as document management systems that maintain proper version control.
  3. Standard Operating Procedures (SOPs): Develop SOPs that establish a structured approach to data handling, including SDTM mapping, data validation, and final submission processes. This can help ensure consistency across different studies.

Implementing SDTM Mapping for Clinical Trials

The mapping of clinical trial data to SDTM is a fundamental aspect of regulatory submission that directly influences the assessment of the data by review authorities. Identifying the appropriate mappings reduces analysis time and allows for streamlining and clarity.

Key Steps in SDTM Mapping

  1. Data Review and Collection: Begin by thoroughly reviewing the clinical datasets generated from clinical trials. Collect observations and measurements according to pre-defined variables.
  2. Identify Mapping Requirements: Establish which SDTM domains correspond to the data collected. This is critical in ensuring the right relationships between data elements are captured.
  3. Execution of Mapping Procedures: Leverage software solutions designed for SDTM mapping to facilitate the transformation of raw data into compliant SDTM datasets. Tools such as Pinnacle 21 can assist in verifying compliance.
  4. Quality Assurance: Implement quality control processes to check the accuracy of the data transformation and ensure that the final SDTM datasets maintain the integrity of the original data.
See also  HL7 FHIR as a bridge between EHR data and RWE analytic datasets

Creating ADaM Datasets for Efficient Analysis

The development of ADaM datasets is crucial for effective data analysis. These datasets are tailored for specific analytic needs and must comply with specific statistical methodologies to guarantee clarity and rigor.

Steps for Developing ADaM Datasets

  1. Understanding Analysis Needs: Collaborate with biostatistics and clinical teams to understand the analytical requirements. This helps in formulating the necessary elements of the datasets.
  2. Define Dataset Structure: Establish the dataset structure, including the necessary variables and derived measures required for the planned statistical analysis. ADaM provides a clear framework for this.
  3. Data Derivation: Carefully derive new variables as required and ensure they are documented comprehensively. It’s vital to maintain a record of changes and methodologies used.
  4. Compliance Checks: Execute regular compliance checks against ADaM standards to verify adherence. Utilizing tools that check ADaM compliance during the development phase can significantly reduce oversight issues.

Integrating FHIR for Modern Data Standards

The integration of the HL7 FHIR standard represents a shift towards interoperability in healthcare data exchange. One of the key advantages of FHIR is its ability to facilitate real-time data access and integration across multiple platforms.

Implementing FHIR Integration: Key Considerations

  1. Stakeholder Engagement: Engage with stakeholders to assure that their data needs are accurately captured. This is crucial for ensuring willingness to incorporate FHIR methodologies into practice.
  2. System Readiness: Evaluate current data systems to determine their compatibility with FHIR standards. Local systems may require upgrades or changes to accommodate FHIR resources.
  3. Building FHIR Resources: Create FHIR resources pertinent to your models. This could include Patient, Observation, and Medication resources that align with your RWE initiatives.
  4. Testing and Validation: Implement testing procedures for the FHIR integration. Ensuring multiple stakeholders can easily interact and use the standardized format is critical for efficient data exchange.

Conclusion: Establishing a Framework for Next-Generation RWE Models

As the demand for RWE grows, the importance of reliable, standardized data cannot be overstated. By building strong data models using established standards such as CDISC, SDTM, ADaM, and HL7/FHIR, regulatory professionals can ensure compliant submissions and optimize the use of data for informed decisions. The path to effective real-world evidence generation and utilization requires not just adherence to standards but a proactive approach towards integrating and evolving alongside regulatory expectations and technological advancements.

See also  Converting messy RWD into CDISC SDTM and ADaM formats for regulators

For further reading on FDA’s expectations regarding data standards and real-world evidence, consult the FDA’s guidance document on the subject. Those involved in RWE and data standard development should remain current on both FDA updates and international regulatory guidelines to ensure ongoing compliance and relevance in a global market.