<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20120330//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd">
<!--<?xml-stylesheet type="text/xsl" href="article.xsl"?>-->
<article article-type="discussion" dtd-version="1.2" xml:lang="en" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<front>
<journal-meta>
<journal-id journal-id-type="issn">2694-1473</journal-id>
<journal-title-group>
<journal-title>Journal of the Society for Clinical Data Management</journal-title>
</journal-title-group>
<issn pub-type="epub">2694-1473</issn>
<publisher>
<publisher-name>Society for Clinical Data Management</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.47912/jscdm.230</article-id>
<article-categories>
<subj-group>
<subject>Opinion paper</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Feasibility Assessment of Using CDISC Data Standards for in <italic>vivo</italic> and <italic>in silico</italic> Medical Device Trials</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Aydin</surname>
<given-names>Bur&#231;</given-names>
</name>
<xref ref-type="aff" rid="aff-1">1</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Kiely</surname>
<given-names>&#201;anna</given-names>
</name>
<xref ref-type="aff" rid="aff-2">2</xref>
</contrib>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Ohmann</surname>
<given-names>Christian</given-names>
</name>
<email>christianohmann@outlook.de</email>
<xref ref-type="aff" rid="aff-1">1</xref>
</contrib>
</contrib-group>
<aff id="aff-1"><label>1</label>European Clinical Research Infrastructure Network (ECRIN), Paris, France</aff>
<aff id="aff-2"><label>2</label>ClinBuild Clinical Data Services Limited, Cork, Ireland</aff>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2023-09-13">
<day>13</day>
<month>09</month>
<year>2023</year>
</pub-date>
<pub-date pub-type="collection">
<year>2023</year>
</pub-date>
<volume>3</volume>
<issue>3</issue>
<elocation-id>3</elocation-id>
<history>
<date date-type="received" iso-8601-date="2022-10-20">
<day>20</day>
<month>10</month>
<year>2022</year>
</date>
<date date-type="accepted" iso-8601-date="2023-08-04">
<day>04</day>
<month>08</month>
<year>2023</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright: &#x00A9; 2023 The Author(s)</copyright-statement>
<copyright-year>2023</copyright-year>
<license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/">
<license-p>SCDM publishes JSCDM content in an open access manner under a Attribution-Non-Commercial-ShareAlike (CC BY-NC-SA) license. This license lets others remix, adapt, and build upon the work non-commercially, as long as they credit SCDM and the author and license their new creations under the identical terms. See <uri xlink:href="https://creativecommons.org/licenses/by-nc-sa/4.0/">https://creativecommons.org/licenses/by-nc-sa/4.0/</uri>.</license-p>
</license>
</permissions>
<self-uri xlink:href="https://www.jscdm.org/articles/10.47912/jscdm.230/"/>
<abstract>
<p>This paper discusses the current applicable regulatory framework and feasibility of using CDISC data standards for <italic>in vivo</italic> and <italic>in silico</italic> (ie, research conducted by means of computer modeling and simulation) medical device clinical trials with an objective of adequately structuring clinical data generated through <italic>in vivo</italic> and <italic>in silico</italic> medical device trials using CDISC standards. The covered topics are global regulatory data requirements, guidance documents, application examples of CDISC standards for medical device trials, specific data conformity and verification/validation steps expected to be required for <italic>in silico</italic> device trials, and mapping scenarios of physics-based or physiological modeling data generated by <italic>in silico</italic> studies within the CDISC standards. A practical project approach is presented to address the opportunities, challenges, and multidisciplinary solutions for complementary <italic>in vivo</italic> and <italic>in silico</italic> clinical development of transcatheter aortic valve replacement devices with use of CDISC data standards. Continous discussion within the regulatory and CDISC standards frameworks, supported by computer modeling outputs and reuse of available clinical data generated by <italic>in vivo</italic> trials, is needed for successful use of CDISC standards in interdependent <italic>in vivo</italic> and <italic>in silico</italic> medical device trials.</p>
</abstract>
<kwd-group>
<kwd>Medical device</kwd>
<kwd>clinical trial</kwd>
<kwd>CDISC</kwd>
<kwd>in silico</kwd>
<kwd>transcatheter aortic valve replacement</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec>
<title>Introduction</title>
<p>It is the reliable and standardized clinical data behind a medicinal product that makes the evaluation and approval of a medicine or a medical device possible by the regulatory authorities. This regulatory procedure is a cornerstone to ensure the clinical safety and efficacy of medicinal products ultimately marketed for use by the medical community and by patients. Regulatory approval requirements primarily define which data elements should be collected and how they should be presented and analyzed. Within the context of this paper, the definition of <italic>in silico</italic> clinical trial is taken from the Avicenna Alliance as &#8220;<italic>the use of individualised computer simulation in the development or regulatory evaluation of a medicinal product, medical device, or medical intervention</italic>&#8221;.<sup><xref ref-type="bibr" rid="B1">1</xref></sup></p>
</sec>
<sec>
<title>Regulatory data requirements for medical device clinical trials</title>
<sec>
<title>In vivo medical device trials</title>
<p>Medical device clinical trials in European Union (EU) are currently regulated by Regulation 2017/745 (also known as the &#8216;EU Medical Devices Regulation&#8217; [EU MDR]) and are termed as &#8216;clinical investigations&#8217; (ie, any systematic investigation involving one or more human subjects, undertaken to assess the safety or performance of a device). In EU MDR, &#8216;clinical data&#8217; means information concerning safety or performance that is generated from the use of a device. Intracardiac devices are classified as Class III medical devices and their review demands (with certain exceptions) performing clinical investigations.<sup><xref ref-type="bibr" rid="B2">2</xref></sup> EU MDR provides the requirements for medical device clinical investigations under Annex XV Clinical Investigations, which are generally like the ones required by EU regulations for pharmaceutical randomized clinical trials. While EU MDR is the overarching European regulation for medical device clinical trials, regulatory overview of medical devices is managed by accredited notified bodies on a member state level with the scientific opinion sought from the European Medicines Agency (EMA) in case (a) medicines are used in combination with a medical device, (b) medical devices contain an ancillary medicinal substance, (c) a medical device is a companion diagnostic test, (d) medical devices are made of substances that are systemically absorbed, or (e) a medical device is categorized as a high-risk medical device.<sup><xref ref-type="bibr" rid="B3">3</xref></sup></p>
<p>Currently, there is no Europe-wide mandate for any clinical data standard to be applied for the regulatory overview of a pharmaceutical or a medical device. European initiatives, however, exist at EMA and Heads of Medicines Agencies (HMA) levels to promote the use of standards to facilitate interoperability of data and possible adoption of relevant Clinical Data Interchange Standards Consortium (CDISC) standards for collecting raw data in clinical studies.<sup><xref ref-type="bibr" rid="B4">4</xref>,<xref ref-type="bibr" rid="B5">5</xref></sup></p>
<p>The medical device data requirements of the United States Food and Drug Administration (FDA) are managed by the Center for Devices and Radiological Health (CDRH). CDRH encourages manufacturers to use data and terminology standards in pre-market submissions and post-market reports for medical devices yet does not require the use of specific clinical data standards. Medical device clinical trial data are accepted by the CDRH in any format, including CDISC standards.<sup><xref ref-type="bibr" rid="B6">6</xref></sup> However, CDRH is expected to adopt an approach in the future for data standardization in medical device clinical trial data submissions and early adoption of clinical data standards by medical device developers could support process optimization, successful data submission, and timely regulatory review.<sup><xref ref-type="bibr" rid="B7">7</xref>,<xref ref-type="bibr" rid="B8">8</xref>,<xref ref-type="bibr" rid="B9">9</xref>,<xref ref-type="bibr" rid="B10">10</xref>,<xref ref-type="bibr" rid="B11">11</xref></sup> Of note on this possible change in the FDA policy for medical device clinical trial data submissions, the FDA Center for Drug Evaluation and Research (CDER) and Center for Biologics Evaluation and Research (CBER) already require pharmaceutical clinical trials data to be presented in CDISC standards, along with controlled terminologies.<sup><xref ref-type="bibr" rid="B12">12</xref></sup></p>
</sec>
<sec>
<title>In silico medical device trials</title>
<p>While 75 EU-funded research projects concerning <italic>in silico</italic> trials are ongoing in Europe, there is not yet a European framework or strategy for implementing <italic>in silico</italic> medical device trials.<sup><xref ref-type="bibr" rid="B13">13</xref></sup> In fact, a few of these projects are expected to support the European framework for <italic>in silico</italic> trials.<sup><xref ref-type="bibr" rid="B14">14</xref>,<xref ref-type="bibr" rid="B15">15</xref></sup> This paper itself is a similarly targeted assessment of the current and evolving framework.</p>
<p>The FDA has recently published draft guidance for the assessment of the credibility of <italic>in silico</italic> approach in medical device regulatory submissions.<sup><xref ref-type="bibr" rid="B16">16</xref></sup> While this guidance does not directly address any clinical data standard, it does provide an important framework for credibility assessment of different <italic>in silico</italic> clinical trial approaches, from defining the question of interest to generating the adequacy assessment and reporting, following the document &#8216;Assessing Credibility of Computational Modeling through Verification and Validation: Application to Medical Devices&#8217;, prepared by the American Society of Mechanical Engineers.<sup><xref ref-type="bibr" rid="B17">17</xref></sup> The FDA presents different evidence categories for <italic>in silico</italic> clinical data generation; two categories are relevant for medical device trials: Category 5 &#8211; Evidence generated using <italic>in vivo</italic> conditions to support the current context of use (for individual-level data and for comparison between model predictions and a clinical dataset) and Category 8 &#8211; Population-based evidence (no comparison is made on a patient-level basis). Relevance of each of these clinical evidence categories is considered within the verification and validation needs.<sup><xref ref-type="bibr" rid="B16">16</xref></sup>A reporting guidance document by the FDA is also available for reporting modeling studies in medical device submissions.<sup><xref ref-type="bibr" rid="B18">18</xref></sup></p>
<p>As a section summary, data standards are not currently mandated for medical device clinical trial submissions in the EU or the United States yet regulators might be expected to adopt or to broaden the scope of clinical data standards. Inclusion of <italic>in silico</italic> medical device trials data into regulatory submission files also raises issues of data conformity and verification/validation with the corresponding <italic>in vivo</italic> medical device trials data. Use of clinical data standards for medical device trials has been presented by medical device developers in recent literature.<sup><xref ref-type="bibr" rid="B7">7</xref>,<xref ref-type="bibr" rid="B8">8</xref>,<xref ref-type="bibr" rid="B9">9</xref>,<xref ref-type="bibr" rid="B10">10</xref>,<xref ref-type="bibr" rid="B11">11</xref></sup> Interestingly, the FDA itself is currently partnered with the private sector to produce the first simulated human heart, the &#8216;Living Heart&#8217;. Objectives of this project include <italic>in silico</italic> testing of new medical devices.<sup><xref ref-type="bibr" rid="B19">19</xref></sup> While other data standards could also be employed for medical device trials, CDISC standards represent the most advanced set availablefrom a regulatory point of view. The next section valuates the potential use of CDISC standards for the management of <italic>in vivo</italic> and <italic>in silico</italic> medical device trials data.</p>
</sec>
</sec>
<sec>
<title>CDISC standards and medical device trials</title>
<p>CDISC is a standards development organization that manages data standards and controlled terminology for clinical research data management. These standards make standardized clinical data collection, organization, analysis, and review possible.<sup><xref ref-type="bibr" rid="B20">20</xref></sup> CDISC standards also include a tabulation standard for animal studies (Standard for Exchange of Nonclinical Data, [SEND]), study planning, data exchange, and descriptive dataset metadata (Define-XML). CDISC standards employ different domains for clinical trial data, such as medical history, adverse events, laboratory test results, and medical device properties. Domains are further grouped into classes, with most belonging to the following three: General Observation Classes of Interventions (Concomitant Medication and Exposure), Events (Adverse Events and Medical History) and Findings (Laboratory and Questionnaires). Domains and classes have associated variables, controlled terminologies, and business rules.<sup><xref ref-type="bibr" rid="B20">20</xref></sup> The structured model can support clinical researchers in becoming proficient with the standard. CDISC has implementation guides already in place for the SDTM and ADaM standards, for use in medical device clinical trials. This guidance covers seven medical device-related domains (for device identification, fixed and variable device properties, device tracking, and device-subject exposure), and complements other foundational CDISC standards.<sup><xref ref-type="bibr" rid="B21">21</xref></sup></p>
<p>Since 17 December 2016, the FDA, CDER, and CBER require pharmaceutical submission data and metadata to be structured using CDISC standards, namely Study Data Tabulation Model (SDTM), Analysis Data Model (ADaM), SEND, and Define-XML.<sup><xref ref-type="bibr" rid="B22">22</xref></sup> The Japanese Pharmaceuticals and Medical Devices Agency requires CDISC standards for both pharmaceutical and medical devices submissions.<sup><xref ref-type="bibr" rid="B23">23</xref></sup> The Chinese National Medical Products Administration has made a recommendation to report data in CDISC standards.<sup><xref ref-type="bibr" rid="B24">24</xref></sup> While CDISC standards are mostly used by the pharmaceutical industry for regulatory submission purposes and have only been partially implemented in the academic world, CDISC now collaborates with Research Electronic Data Capture (REDCap) and OpenClinica initiatives to promote the adoption and use of CDISC and Clinical Data Acquisition Standards Harmonization (CDASH) standards in academic clinical research as well.<sup><xref ref-type="bibr" rid="B25">25</xref>,<xref ref-type="bibr" rid="B26">26</xref></sup> An academic research community has also expressed interest in using CDISC standards for investigator-led clinical research without a regulatory mandate.<sup><xref ref-type="bibr" rid="B27">27</xref></sup></p>
<p>The FDA has published guidance for industry on specifics of standardized study data and controlled terminologies for pharmaceutical submissions.<sup><xref ref-type="bibr" rid="B12">12</xref>,<xref ref-type="bibr" rid="B28">28</xref></sup> There are two major needs that are fulfilled by these technical requirements: (1) To facilitate and expedite the regulatory review process of the clinical data (using a study data standardization plan, data standards, and controlled terminologies); and (2) to conduct comparative analyses across studies. An additional benefit of data sharing and reuse is facilitated by applying the same data standards across different research groups.<sup><xref ref-type="bibr" rid="B29">29</xref>,<xref ref-type="bibr" rid="B30">30</xref></sup> For simulation and modeling purposes, data sharing is more than an ethical imperative: validation and improvement of the models require patient- and/or population-level clinical data over time from the studies within the therapeutic area, and any shared clinical data should be made interoperable to serve the purpose.<sup><xref ref-type="bibr" rid="B1">1</xref>,<xref ref-type="bibr" rid="B31">31</xref></sup> It is reasonable to expect that these regulatory and data sharing benefits would similarly apply to clinical data generated within medical device trials if clinical data standards are adopted for regulatory submission and data sharing procedures.</p>
<sec>
<title>Limitations of CDISC Standards</title>
<p>While comprehensive, CDISC standards have some general and device-related limitations. As an example, the FDA states that ADaM structures do not support simultaneous analysis of multiple dependent variables or correlation analysis across several response variables. Conversion of legacy study data (data in a non-standardized format) to SDTM and ADaM formats could also raise traceability issues and may require extensive work on the data to conform to regulatory standards, depending on the complexity and available documentation of the source data.<sup><xref ref-type="bibr" rid="B22">22</xref></sup> Prospective application of CDISC standards is therefore a more appropriate procedure. As CDISC standards are not binding for medical device manufacturers, clear implementation of the standards has not been possible so far. Example implementation strategies and associated problems to be considered in advance have been shared in the literature.<sup><xref ref-type="bibr" rid="B7">7</xref>,<xref ref-type="bibr" rid="B8">8</xref>,<xref ref-type="bibr" rid="B9">9</xref>,<xref ref-type="bibr" rid="B10">10</xref>,<xref ref-type="bibr" rid="B11">11</xref></sup> Finally, CDISC standards do not address specific data management requirements for <italic>in silico</italic> trials; these specific aspects are further elaborated below.</p>
</sec>
<sec>
<title>Considerations for physics-based or physiological modeling data</title>
<p>CDISC standards have been developed for real-world clinical data, meaning that they help organize biologically or operationally obtained data. In <italic>in silico</italic> trials, however, data will be generated solely through simulation and modeling. While clinical components of these data could be managed using CDISC standards (assuming that data will be generated as one record per subject per parameter per timepoint), the physics-based or physiological data generated within a medical device simulation model could require a different structure and/or standard. An FDA guidance document provides a general outline for the reporting requirements of computational medical device modeling studies, without naming particular data submission requirements.<sup><xref ref-type="bibr" rid="B18">18</xref></sup> If new medical device standards were to be developed to support the modeling and submission of underlying physics-based or physiological data to regulatory bodies, a cross-functional team including CDISC experts could support on this task. The data could be mapped to CDISC SDTM and ADaM domains and datasets, and have additional metadata described in the Define-XML as needed. This approach could also help to map relatedness and causality links between medical device physics-based or physiological data and clinical events, findings, and interventions datasets.</p>
</sec>
</sec>
<sec>
<title>Implementation issues and scenarios</title>
<p>From a technical perspective, implementing CDISC standards for the clinical data of a medical device trial should take the same approach and involve the same considerations whether the trial is <italic>in vivo</italic> or <italic>in silico</italic>. The key decision point is the anticipated purpose of conducting an <italic>in silico</italic> device trial: If the purpose is to validate the <italic>in silico</italic> trial model for supporting the regulatory submission of a new device, the reviewers will require a twin set of identical <italic>in vivo</italic> and <italic>in silico</italic> trials for validation purposes, depending on the novelty and the associated risks of a the new medical device. This assumption demands an <italic>in silico</italic> trial generating patient-level data and the same CDISC standards and considerations should apply for the <italic>in vivo</italic> as well as the <italic>in silico</italic> trial. The regulators will also require the same data approach from the Case Report Form (CRF) variables and format up to the analysis results and metadata to verify model validation and conduct patient-level comparative analyses. It will be ideal, therefore, to prospectively implement the <italic>in silico</italic> trial strategy into an actual and <italic>in vivo</italic> clinical development program of a medical device.</p>
<p>If the purpose of the <italic>in silico</italic> approach is to supplement the assumptions and findings of an <italic>in vivo</italic> trial (eg, extrapolation for patient populations with different baseline characteristics), an approach should be taken for generating population-level model and data. An <italic>in silico</italic> trial with population-level findings would be of limited use for regulatory purposes as the cross-comparison of <italic>in silico</italic> and <italic>in vivo</italic> clinical data would be restricted to the level of aggregated data.</p>
<p><italic>In silico</italic> trials are expected to be accompanied by additional animal, human and/or cadaver studies within a regulatory submission package of a medical device (whether for model validation purposes or for parameters that could not be addressed by the <italic>in silico</italic> trial, or both).<sup><xref ref-type="bibr" rid="B32">32</xref></sup> As discussed above, CDISC standards (along with Controlled Terminologies) provide an interoperable and harmonized data framework for all of these study types. The FDA study data technical conformance guide provides a folder structure to organize clinical and non-clinical datasets from multiple studies within the same submission package.<sup><xref ref-type="bibr" rid="B28">28</xref>,<xref ref-type="bibr" rid="B33">33</xref></sup> Care should be taken to harmonize any custom term or domain created by the sponsor (if required) across the submission dossier.</p>
<p>Another potential challenge in <italic>in silico</italic> medical device trials would involve traceability and causality links with the underlying physics model.<sup><xref ref-type="bibr" rid="B34">34</xref></sup> For example, how would an <italic>in silico</italic> transcatheter aortic valve implantation (TAVI) medical device trial simulate the adverse event of procedural bleeding in a single patient? Would the adverse event have causal (ie, mathematical) connection to the underlying physics data or would it appear solely stochastically through statistical probability analysis? In any case, the <italic>in silico</italic> trial should clearly define individual elements of engineering and modeling outcomes and their relation to the clinical outcomes. CDISC standards (SDTM, ADaM, and Define-XML) could be employed to identify and map the metadata of these outcomes, just as they are used to identify the clinical ones. The Define-XML specification document provides methodology and examples, including use of supplemental files, for linking computational methods, algorithms, and code to a clinical variable.<sup><xref ref-type="bibr" rid="B35">35</xref></sup></p>
<p>Full technical details of successful implementation of CDISC standards for TAVI medical device trials is beyond the scope of this paper and readers are advised to consult the references of previous publications.<sup><xref ref-type="bibr" rid="B7">7</xref>,<xref ref-type="bibr" rid="B8">8</xref>,<xref ref-type="bibr" rid="B9">9</xref>,<xref ref-type="bibr" rid="B10">10</xref>,<xref ref-type="bibr" rid="B11">11</xref></sup> Of special interest for TAVI trials, the Edwards Lifesciences group reported their successful implementation of CDISC standards for their TAVI trials and their involvement with the CDISC authors to work on CDISC implementation and the development of user guides<sup><xref ref-type="bibr" rid="B9">9</xref></sup> The last, but highly crucial, step would include direct and trial-/device-specific discussions with the regulators for the data requirements. The FDA emphasizes this point and advises that the discussions should be initiated at an early development phase.<sup><xref ref-type="bibr" rid="B28">28</xref></sup> EU authorities similarly offer expert panel consultation for all class III devices, and prior to the clinical investigation, the manufacturer may consult an expert panel with the aim of reviewing the manufacturer&#8217;s intended clinical development strategy and proposals for clinical investigation.<sup><xref ref-type="bibr" rid="B2">2</xref>,<xref ref-type="bibr" rid="B3">3</xref></sup></p>
</sec>
<sec>
<title>Discussion</title>
<p>This paper assessed the feasibility of using CDISC data standards for <italic>in vivo</italic> and <italic>in silico</italic> medical device trials from a regulatory requirements and data management perspective. TAVI medical device trials were taken as a use case for practical implications. For regulatory evaluation and approval procedures, clinical data submission requirements should be considered to be the same for <italic>in vivo</italic> and <italic>in silico</italic> medical device clinical trials for data validation, traceability, and interoperability purposes. These trials should be expected to be complementary to each other, possibly along with supplemental non-clinical or observational data, within the same submission package. While there are no binding regulatory frameworks in the United States and EU for clinical data submission of medical device clinical trials, the available FDA framework of CDISC standards and controlled terminologies for pharmaceuticals offers a viable and feasible option. CDISC standards and additional controlled terminologies should be considered as the most advanced clinical and non-clinical data tools from a regulatory and clinical development perspective for practical adoption into the data management structure of medical device trials. Use of CDISC standards for medical device clinical development could facilitate and expedite the regulatory review process, cross-study comparative analyses, clinical data sharing and use, and model validation and improvement. While this reasoning for CDISC standards is supported by available guidance documents and successful real-world TAVI medical device approval cases made available in the literature, adoption of CDISC standards for medical device trials is still an active research area and requires prospective consideration and built-in investment in a clinical data management program, ideally starting from the CRF development stage. Plans for providing standardized clinical data should be discussed with regulators at an early stage of a medical device clinical development program.</p>
<p>When compared to <italic>in vivo</italic> medical device trials, an <italic>in silico</italic> approach comes with specific opportunities and challenges for implementing CDISC standards. If validation of an <italic>in silico</italic> trial model is desired with the use of patient-level data along with <italic>in vivo</italic> clinical studies of a medical device, <italic>in vivo</italic> and <italic>in silico</italic> clinical development activities and elements, including data format and standards, should be prospectively harmonized within the same development program before any data collection begins. This approach should avoid traceability and interoperability problems. If the purpose of an <italic>in silico</italic> trial model is limited to supplementing an <italic>in vivo</italic> medical device trial, a population-level data generation model could be built. In this case, the statistical analysis plan and structure of datasets generated by the <italic>in silico</italic> approach require careful consideration to provide reliable supplementary outcomes while conforming with regulatory statistical principles. In both cases, an early discussion with regulators should again help medical device developers to design and implement an optimal <italic>in silico</italic> model within the clinical development activities of a medical device.</p>
<p>A unique challenge for <italic>in silico</italic> medical device trials will be the formatting and mapping of physics-based or physiological data generated by a medical device computational model. As medical device modeling studies mature, new data structures and standards could be required to present datasets of computational outputs linked with medical device trials to support regulatory submissions. CDISC metadata standards could be used for mapping model-generated data to CDISC, SDTM, and ADaM domains. Addressing this challenge will require the multidisciplinary work of subject matter experts in computational modeling, clinical research, and data management. CDISC community and research activities are ongoing for mitigation. Specifically, an ongoing European project called &#8216;In-Silico testing and validation of Cardiovascular IMplantable devices (SIMCor)&#8217; is aiming to establish a computational platform for <italic>in silico</italic> development, validation, and regulatory approval of cardiovascular implantable devices.<sup><xref ref-type="bibr" rid="B36">36</xref></sup> One of the project&#8217;s objectives to mitigate the challenges stated above is to contact medical device manufacturers that are sponsoring TAVI clinical trials for which the possibility of anonymized patient-level data sharing was announced on clinical trial registries, and to request the reuse of trial metadata and anonymized patient-level data. If made available, the trial metadata will be used to build up template CRFs, SDTM, ADaM, and Define-XML files for pilot implementation of mapping between computational model-generated data and clinical outcomes, while anonymized patient-level data will be used to support computational model development, verification, and validation.<sup><xref ref-type="bibr" rid="B37">37</xref></sup> Additionally, the SIMCor project involves scientific and regulatory advisory boards to facilitate the formation of the desired multidisciplinary forum for advancement of <italic>in silico</italic> medical device trials methodology.</p>
<p>This feasibility assessment concludes that CDISC standards are an ideal foundation to start addressing harmonized clinical data management of <italic>in vivo</italic> and <italic>in silico</italic> medical device trials for regulatory approval procedures. This ssessment is limited to the scope of a single-use case of TAVI medical device trials;similar steps should be taken for different types of medical devices for which clinical trials for regulatory approval are required and an <italic>in silico</italic> clinical trial approach could provide added benefit. For specific disease areas, CDISC Therapeutic Area User Guides can support <italic>in silico</italic> medical device trials design and evaluation teams with disease-specific examples and guidance for CDISC standards implementation.<sup><xref ref-type="bibr" rid="B38">38</xref></sup> While the learnings from <italic>in vivo</italic> medical device trials using CDISC standards are relevant for <italic>in silico</italic> trials, continous regulatory discussion, multidisciplinary teamwork, and reuse of available trial metadata and clinical data are needed to overcome specific challenges and to successfully implement CDISC standards for complementary <italic>in vivo</italic> and <italic>in silico</italic> medical device trials.</p>
</sec>
</body>
<back>
<ack>
<title>Acknowledgements</title>
<p>The authors wish to thank Steve Canham (ECRIN) for his input.</p>
</ack>
<sec>
<title>Funding Information</title>
<p>This paper was prepared within the &#8216;In-Silico testing and validation of Cardiovascular IMplantable devices (SIMCor)&#8217; project activities. This project received funding from the European Union&#8217;s Horizon 2020 research and innovation programme under grant agreement No 101017578.</p>
</sec>
<sec>
<title>Competing Interests</title>
<p>BA is currently an employee of Aixial Group on behalf of Sanofi. This paper is not related in any way with BA&#8217;s current role or employer. &#201;K is an authorized CDISC Instructor and has performed consultancy work for CDISC. CO has no competing interests to declare.</p>
</sec>
<sec>
<title>Author Contributions</title>
<p>BA provided the first and the updated version of the manuscript. &#201;K and CO reviewed the manuscripts and gave feedback to BA. &#201;K provided input as CDISC specialist and CO as a previous head of a clinical trial unit. BA, &#201;K and CO have been involved in the SIMCor project.</p>
</sec>
<ref-list>
<ref id="B1"><mixed-citation publication-type="journal"><label>1.&#160;</label><string-name><surname>Viceconti</surname> <given-names>M</given-names></string-name>, <string-name><surname>Henney</surname> <given-names>A</given-names></string-name>, <string-name><surname>Morley-Fletcher</surname> <given-names>E</given-names></string-name>. <article-title>in silico Clinical Trials: How Computer Simulation Will Transform the Biomedical Industry</article-title>. <month>January</month> <year>2016</year>. DOI: <pub-id pub-id-type="doi">10.18203/2349-3259.ijct20161408</pub-id></mixed-citation></ref>
<ref id="B2"><mixed-citation publication-type="journal"><label>2.&#160;</label><collab>European Parliament and European Council</collab>. <article-title>Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, amending Directive 2001/83/EC, Regulation (EC) No 178/2002 and Regulation (EC) No 1223/2009 and repealing Council Directives 90/385/EEC and 93/42/EEC</article-title>. <source>Official Journal of the European Union</source> <year>2017</year>, 5.5.2017; L 117/1.</mixed-citation></ref>
<ref id="B3"><mixed-citation publication-type="webpage"><label>3.&#160;</label><collab>European Medicines Agency</collab>. <article-title>Human regulatory &#8211; medical devices</article-title>. Accessed February 21, 2022. <uri>https://www.ema.europa.eu/en/human-regulatory/overview/medical-devices</uri></mixed-citation></ref>
<ref id="B4"><mixed-citation publication-type="webpage"><label>4.&#160;</label><collab>Heads of Medicines Agencies and European Medicines Agency</collab>. <article-title>HMA-EMA Joint Big Data Taskforce &#8211; summary report</article-title>. <month>February</month> <day>13</day>, <year>2019</year>. EMA/105321/2019. Accessed February 22, 2022. <uri>https://www.ema.europa.eu/en/documents/minutes/hma/ema-joint-task-force-big-data-summary-report_en.pdf</uri></mixed-citation></ref>
<ref id="B5"><mixed-citation publication-type="webpage"><label>5.&#160;</label><collab>Heads of Medicines Agencies and European Medicines Agency</collab>. <article-title>European Medicines Regulatory Network Data Standardisation Strategy</article-title>. <month>December</month> <day>16</day>, <year>2021</year>. EMA/447502/2021. Accessed February 22, 2022. <uri>https://www.ema.europa.eu/en/documents/other/european-medicines-regulatory-network-data-standardisation-strategy_en.pdf</uri></mixed-citation></ref>
<ref id="B6"><mixed-citation publication-type="webpage"><label>6.&#160;</label><collab>Food and Drug Administration</collab>. <article-title>Data Standards and Terminology Standards for Information Submitted to CDRH</article-title>. Accessed June 3, 2022. <uri>https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/data-standards-and-terminology-standards-information-submitted-cdrh</uri></mixed-citation></ref>
<ref id="B7"><mixed-citation publication-type="webpage"><label>7.&#160;</label><string-name><surname>Smoak</surname> <given-names>C</given-names></string-name>. <article-title>CDISC Standards for Medical Devices: Historical Perspective and Current Status</article-title>. <source>PharmaSUG</source> <year>2020</year>, Paper MD-020. Accessed February 22, 2022. <uri>https://www.pharmasug.org/proceedings/2020/MD/PharmaSUG-2020-MD-020.pdf</uri></mixed-citation></ref>
<ref id="B8"><mixed-citation publication-type="webpage"><label>8.&#160;</label><string-name><surname>Hall</surname> <given-names>P</given-names></string-name>. <article-title>Successful US Submission of Medical Device Clinical Trial using CDISC</article-title>. <source>PharmaSUG</source> <year>2020</year>, Paper MD-041. Accessed February 22, 2022. <uri>https://www.pharmasug.org/proceedings/2020/MD/PharmaSUG-2020-MD-041.pdf</uri></mixed-citation></ref>
<ref id="B9"><mixed-citation publication-type="webpage"><label>9.&#160;</label><string-name><surname>Hall</surname> <given-names>P</given-names></string-name>, <string-name><surname>Karunasundera</surname> <given-names>T</given-names></string-name>, <string-name><surname>Maharjan</surname> <given-names>S</given-names></string-name>, <string-name><surname>Vegesna</surname> <given-names>V</given-names></string-name>. <article-title>Multiple Successful Submissions of Medical Device Clinical Trial in the US and China using CDISC</article-title>. <source>PharmaSUG</source> <year>2021</year>, Paper MD-044. Accessed February 22, 2022. <uri>https://www.pharmasug.org/proceedings/2021/MD/PharmaSUG-2021-MD-044.pdf</uri></mixed-citation></ref>
<ref id="B10"><mixed-citation publication-type="webpage"><label>10.&#160;</label><string-name><surname>Smoak</surname> <given-names>C</given-names></string-name>. <article-title>A Critique of Implementing the Submission Data Tabulation Model (SDTM) for Drugs and Medical Devices</article-title>. <source>PharmaSUG</source> <year>2017</year>, Paper DS25. Accessed February 22, 2022. <uri>https://www.pharmasug.org/proceedings/2017/DS/PharmaSUG-2017-DS25.pdf</uri></mixed-citation></ref>
<ref id="B11"><mixed-citation publication-type="webpage"><label>11.&#160;</label><string-name><surname>Teli</surname> <given-names>R</given-names></string-name>, <string-name><surname>Sacco</surname> <given-names>A</given-names></string-name>. <article-title>Medical Device SDTM: A Real Case</article-title>. <source>PHUSE EU Connect</source> <year>2019</year>, Paper PP05. Accessed February 21, 2022. <uri>https://phuse.s3.eu-central-1.amazonaws.com/Archive/2019/Connect/EU/Amsterdam/PAP_PP05.pdf</uri></mixed-citation></ref>
<ref id="B12"><mixed-citation publication-type="webpage"><label>12.&#160;</label><collab>Food and Drug Administration</collab>. <article-title>Providing Regulatory Submissions In Electronic Format &#8211; Standardized Study Data Guidance for Industry</article-title>. <month>June</month> <year>2021</year>, revision 2. Accessed August 22 2023. <uri>https://collections.nlm.nih.gov/catalog/nlm:nlmuid-9918350982006676-pdf</uri></mixed-citation></ref>
<ref id="B13"><mixed-citation publication-type="webpage"><label>13.&#160;</label><collab>European Commission</collab>. <article-title>The Community Research and Development Information Service, (CORDIS). Search conducted with the keyword &#8216;in silico trial&#8217;</article-title>, accessed February 21, 2022. <uri>https://cordis.europa.eu/search/en</uri></mixed-citation></ref>
<ref id="B14"><mixed-citation publication-type="webpage"><label>14.&#160;</label><collab>European Commission</collab>. <article-title>The Community Research and Development Information Service (CORDIS). In Silico World: Lowering barriers to ubiquitous adoption of In Silico Trials</article-title>. Accessed February 21, 2022. <uri>https://cordis.europa.eu/project/id/101016503</uri></mixed-citation></ref>
<ref id="B15"><mixed-citation publication-type="webpage"><label>15.&#160;</label><collab>European Commission</collab>. <article-title>The Community Research and Development Information Service (CORDIS). A European standardization framework for data integration and data-driven in silico models for personalized medicine</article-title>. Accessed February 21, 2022. <uri>https://cordis.europa.eu/project/id/825843</uri></mixed-citation></ref>
<ref id="B16"><mixed-citation publication-type="webpage"><label>16.&#160;</label><collab>Food and Drug Administration</collab>. <article-title>Assessing the Credibility of Computational Modeling and Simulation in Medical Device Submissions &#8211; Draft Guidance for Industry and Food and Drug Administration Staff</article-title>. <month>December</month> <year>2021</year>. Accessed August 22, 2023. <uri>https://www.fda.gov/regulatory-information/search-fda-guidance-documents/assessing-credibility-computational-modeling-and-simulation-medical-device-submissions</uri></mixed-citation></ref>
<ref id="B17"><mixed-citation publication-type="journal"><label>17.&#160;</label><collab>American Society of Mechanical Engineers</collab>. <article-title>Assessing Credibility of Computational Modeling through Verification and Validation: Application to Medical Devices</article-title>. <year>2018</year>, V&amp;V 40.</mixed-citation></ref>
<ref id="B18"><mixed-citation publication-type="journal"><label>18.&#160;</label><collab>Food and Drug Administration</collab>. <article-title>Reporting of Computational Modeling Studies in Medical Device Submissions Guidance for Industry and Food and Drug Administration Staff</article-title>. <month>September</month> <year>2016</year>.</mixed-citation></ref>
<ref id="B19"><mixed-citation publication-type="webpage"><label>19.&#160;</label><article-title>Dassault Syst&#232;mes and the FDA Extend Collaboration to Inform Cardiovascular Device Review Process and Accelerate Access to New Treatments</article-title>. Accessed February 21, 2022. <uri>https://www.3ds.com/newsroom/press-releases/dassault-systemes-and-fda-extend-collaboration-inform-cardiovascular-device-review-process-and-accelerate-access-new-treatments</uri></mixed-citation></ref>
<ref id="B20"><mixed-citation publication-type="webpage"><label>20.&#160;</label><collab>Clinical Data Interchange Standards Consortium</collab>. <article-title>CDISC Standards</article-title>. Accessed August 22, 2023. <uri>https://www.cdisc.org/standards</uri></mixed-citation></ref>
<ref id="B21"><mixed-citation publication-type="webpage"><label>21.&#160;</label><collab>Clinical Data Interchange Standards Consortium</collab>. <article-title>Medical Devices</article-title>. Accessed February 21, 2022. <uri>https://www.cdisc.org/standards/foundational/medical-devices</uri></mixed-citation></ref>
<ref id="B22"><mixed-citation publication-type="webpage"><label>22.&#160;</label><collab>Food and Drug Administration</collab>. <article-title>Data Standards Catalog v8.0 (02-15-2022) &#8211; Supported and Required Standards</article-title>. Accessed February 23, 2022. <uri>https://www.fda.gov/media/156273/download</uri></mixed-citation></ref>
<ref id="B23"><mixed-citation publication-type="webpage"><label>23.&#160;</label><collab>The Japanese Pharmaceuticals and Medical Devices Agency</collab>. <article-title>Revision of Technical Conformance Guide on Electronic Study Data Submissions</article-title>. <month>January</month> <year>2019</year>, Notification No. 0124001. Accessed August 22, 2023. <uri>https://www.pmda.go.jp/files/000229468.pdf</uri></mixed-citation></ref>
<ref id="B24"><mixed-citation publication-type="journal"><label>24.&#160;</label><collab>The Chinese National Medical Products Administration</collab>. <article-title>Guideline on the Submission of Clinical Trial Data</article-title>. <month>July</month> <year>2020</year>.</mixed-citation></ref>
<ref id="B25"><mixed-citation publication-type="webpage"><label>25.&#160;</label><collab>Clinical Data Interchange Standards Consortium</collab>. <article-title>CDISC and REDCap Work Together to Foster More Meaningful Clinical Research for Academics</article-title>. Accessed February 23, 2022. <uri>https://www.cdisc.org/news/cdisc-and-redcap-work-together-foster-more-meaningful-clinical-research-academics</uri></mixed-citation></ref>
<ref id="B26"><mixed-citation publication-type="webpage"><label>26.&#160;</label><collab>Clinical Data Interchange Standards Consortium</collab>. <article-title>CDISC and OpenClinica Collaborate to Drive Academic Clinical Research Forward</article-title>. Accessed February 23, 2022. <uri>https://www.cdisc.org/news/cdisc-and-openclinica-collaborate-drive-academic-clinical-research-forward</uri></mixed-citation></ref>
<ref id="B27"><mixed-citation publication-type="journal"><label>27.&#160;</label><string-name><surname>Takahara</surname> <given-names>S</given-names></string-name>, <string-name><surname>Saito</surname> <given-names>TI</given-names></string-name>, <string-name><surname>Imai</surname> <given-names>Y</given-names></string-name>, <string-name><surname>Kawakami</surname> <given-names>T</given-names></string-name>, <string-name><surname>Murayama</surname> <given-names>T</given-names></string-name>. <article-title>A use-case analysis of Clinical Data Interchange Standards Consortium/Study Data Tabulation Model in academia in an investigator-initiated clinical trial</article-title>. <source>Nagoya J Med Sci</source>. <year>2022</year>; <volume>84</volume>(<issue>1</issue>): <fpage>120</fpage>&#8211;<lpage>132</lpage>. DOI: <pub-id pub-id-type="doi">10.18999/nagjms.84.1.120</pub-id></mixed-citation></ref>
<ref id="B28"><mixed-citation publication-type="webpage"><label>28.&#160;</label><collab>Food and Drug Administration</collab>. <article-title>Study Data Technical Conformance Guide &#8211; Technical Specifications Document</article-title>. <month>March</month> <year>2022</year>, Version 4.9. Accessed August 22, 2023. <uri>https://www.fda.gov/media/153632/download</uri></mixed-citation></ref>
<ref id="B29"><mixed-citation publication-type="journal"><label>29.&#160;</label><string-name><surname>Kush</surname> <given-names>RD</given-names></string-name>, <string-name><surname>Warzel</surname> <given-names>D</given-names></string-name>, <string-name><surname>Kush</surname> <given-names>MA</given-names></string-name>, et al. <article-title>FAIR data sharing: The roles of common data elements and harmonization</article-title>. <source>J Biomed Inform</source>. <year>2020</year>; <volume>107</volume>: <elocation-id>103421</elocation-id>. DOI: <pub-id pub-id-type="doi">10.1016/j.jbi.2020.103421</pub-id></mixed-citation></ref>
<ref id="B30"><mixed-citation publication-type="journal"><label>30.&#160;</label><string-name><surname>Ohmann</surname> <given-names>C</given-names></string-name>, <string-name><surname>Banzi</surname> <given-names>R</given-names></string-name>, <string-name><surname>Canham</surname> <given-names>S</given-names></string-name>, et al. <article-title>Sharing and reuse of individual participant data from clinical trials: principles and recommendations</article-title>. <source>BMJ Open</source>. <year>2017</year>; <volume>7</volume>(<issue>12</issue>): <elocation-id>e018647</elocation-id>. DOI: <pub-id pub-id-type="doi">10.1136/bmjopen-2017-018647</pub-id></mixed-citation></ref>
<ref id="B31"><mixed-citation publication-type="journal"><label>31.&#160;</label><string-name><surname>Romero</surname> <given-names>K</given-names></string-name>, <string-name><surname>Ito</surname> <given-names>K</given-names></string-name>, <string-name><surname>Rogers</surname> <given-names>JA</given-names></string-name>, et al. <article-title>The future is now: model-based clinical trial design for Alzheimer&#8217;s disease</article-title>. <source>Clin Pharmacol Ther</source>. <year>2015</year>; <volume>97</volume>(<issue>3</issue>): <fpage>210</fpage>&#8211;<lpage>214</lpage>. DOI: <pub-id pub-id-type="doi">10.1002/cpt.16</pub-id></mixed-citation></ref>
<ref id="B32"><mixed-citation publication-type="journal"><label>32.&#160;</label><string-name><surname>Faris</surname> <given-names>O</given-names></string-name>, <string-name><surname>Shuren</surname> <given-names>J</given-names></string-name>. <article-title>An FDA Viewpoint on Unique Considerations for Medical-Device Clinical Trials</article-title>. <source>N Engl J Med</source>. <year>2017</year>; <volume>376</volume>(<issue>14</issue>): <fpage>1350</fpage>&#8211;<lpage>1357</lpage>. DOI: <pub-id pub-id-type="doi">10.1056/NEJMra1512592</pub-id></mixed-citation></ref>
<ref id="B33"><mixed-citation publication-type="webpage"><label>33.&#160;</label><collab>Food and Drug Administration</collab>. <article-title>Providing Regulatory Submissions in Electronic Format &#8212; Certain Human Pharmaceutical Product Applications and Related Submissions Using the eCTD Specifications Guidance for Industry</article-title>. <month>February</month> <year>2020</year>. Accessed August 22, 2023. <uri>https://www.fda.gov/regulatory-information/search-fda-guidance-documents/providing-regulatory-submissions-electronic-format-certain-human-pharmaceutical-product-applications</uri></mixed-citation></ref>
<ref id="B34"><mixed-citation publication-type="journal"><label>34.&#160;</label><string-name><surname>Bodner</surname> <given-names>J</given-names></string-name>, <string-name><surname>Kaul</surname> <given-names>V</given-names></string-name>. <article-title>A Framework for In Silico Clinical Trials For Medical Devices Using Concepts From Model Verification, Validation, And Uncertainty Quantification (VVUQ)</article-title>. <source>ASME VVS</source> <year>2021</year>, VVS2021-65094. DOI: <pub-id pub-id-type="doi">10.1115/VVS2021-65094</pub-id></mixed-citation></ref>
<ref id="B35"><mixed-citation publication-type="webpage"><label>35.&#160;</label><collab>Clinical Data Interchange Standards Consortium</collab>. <article-title>Define-XML</article-title>. Accessed February 23, 2022. <uri>https://www.cdisc.org/standards/data-exchange/define-xml</uri></mixed-citation></ref>
<ref id="B36"><mixed-citation publication-type="webpage"><label>36.&#160;</label><collab>European Commission</collab>. <article-title>The Community Research and Development Information Service (CORDIS). In Silico testing and validation of Cardiovascular Implantable devices</article-title>. Accessed February 21, 2022. <uri>https://cordis.europa.eu/project/id/101017578</uri></mixed-citation></ref>
<ref id="B37"><mixed-citation publication-type="journal"><label>37.&#160;</label><string-name><surname>Aydin</surname> <given-names>B</given-names></string-name>, <string-name><surname>Ohmann</surname> <given-names>C</given-names></string-name>. <article-title>SIMCOR Deliverable 10.1: In-silico trial impact assessment framework</article-title>. <source>Zenodo</source>. <month>December</month>, <year>2021</year>. DOI: <pub-id pub-id-type="doi">10.5281/zenodo.6353628</pub-id></mixed-citation></ref>
<ref id="B38"><mixed-citation publication-type="webpage"><label>38.&#160;</label><collab>Clinical Data Interchange Standards Consortium</collab>. <article-title>Therapeutic Areas</article-title>. Accessed February 23, 2022. <uri>https://www.cdisc.org/standards/therapeutic-areas</uri></mixed-citation></ref>
</ref-list>
</back>
</article>