<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<!DOCTYPE GmsArticle SYSTEM "http://www.egms.de/dtd/2.0.34/GmsArticle.dtd">
<GmsArticle xmlns:xlink="http://www.w3.org/1999/xlink">
  <MetaData>
    <Identifier>26dkou400</Identifier>
    <IdentifierDoi>10.3205/26dkou400</IdentifierDoi>
    <IdentifierUrn>urn:nbn:de:0183-26dkou4001</IdentifierUrn>
    <ArticleType>Meeting Abstract</ArticleType>
    <TitleGroup>
      <Title language="en">How simulation-based planning and smart wearable data help understand the role of peak loads during fracture healing</Title>
    </TitleGroup>
    <CreatorList>
      <Creator>
        <PersonNames>
          <Lastname>Arnegger</Lastname>
          <LastnameHeading>Arnegger</LastnameHeading>
          <Firstname>Andreas</Firstname>
          <Initials>A</Initials>
        </PersonNames>
        <Address>
          <Affiliation>OSORA medical GmbH, Ulm, Deutschland</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="yes">author</Creatorrole>
      </Creator>
      <Creator>
        <PersonNames>
          <Lastname>Niemeyer</Lastname>
          <LastnameHeading>Niemeyer</LastnameHeading>
          <Firstname>Frank</Firstname>
          <Initials>F</Initials>
        </PersonNames>
        <Address>
          <Affiliation>OSORA medical GmbH, Ulm, Deutschland</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="no">author</Creatorrole>
      </Creator>
      <Creator>
        <PersonNames>
          <Lastname>Popov</Lastname>
          <LastnameHeading>Popov</LastnameHeading>
          <Firstname>Ilya</Firstname>
          <Initials>I</Initials>
        </PersonNames>
        <Address>
          <Affiliation>ComeBack Mobility Inc., San Antonio, USA</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="no">author</Creatorrole>
      </Creator>
      <Creator>
        <PersonNames>
          <Lastname>Protsenko</Lastname>
          <LastnameHeading>Protsenko</LastnameHeading>
          <Firstname>Vsevolod</Firstname>
          <Initials>V</Initials>
        </PersonNames>
        <Address>
          <Affiliation>ComeBack Mobility Inc., San Antonio, USA</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="no">author</Creatorrole>
      </Creator>
      <Creator>
        <PersonNames>
          <Lastname>Bilyi</Lastname>
          <LastnameHeading>Bilyi</LastnameHeading>
          <Firstname>Vladyslav</Firstname>
          <Initials>V</Initials>
        </PersonNames>
        <Address>
          <Affiliation>ComeBack Mobility Inc., San Antonio, USA</Affiliation>
        </Address>
        <Creatorrole corresponding="no" presenting="no">author</Creatorrole>
      </Creator>
    </CreatorList>
    <PublisherList>
      <Publisher>
        <Corporation>
          <Corporatename>German Medical Science GMS Publishing House</Corporatename>
        </Corporation>
        <Address>D&#252;sseldorf</Address>
      </Publisher>
    </PublisherList>
    <SubjectGroup>
      <SubjectheadingDDB>610</SubjectheadingDDB>
    </SubjectGroup>
    <DatePublishedList>
     <DatePublished>20261020</DatePublished>
    </DatePublishedList>
    <Language>engl</Language>
    <License license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/">
      <AltText language="en">This is an Open Access article distributed under the terms of the Creative Commons Attribution 4.0 License.</AltText>
      <AltText language="de">Dieser Artikel ist ein Open-Access-Artikel und steht unter den Lizenzbedingungen der Creative Commons Attribution 4.0 License (Namensnennung).</AltText>
    </License>
    <SourceGroup>
      <Meeting>
        <MeetingId>M0659</MeetingId>
        <MeetingSequence>400</MeetingSequence>
        <MeetingCorporation>Deutsche Gesellschaft f&#252;r Orthop&#228;die und Unfallchirurgie</MeetingCorporation>
        <MeetingCorporation>Deutsche Gesellschaft f&#252;r Orthop&#228;die und Orthop&#228;dische Chirurgie</MeetingCorporation>
        <MeetingCorporation>Deutsche Gesellschaft f&#252;r Unfallchirurgie</MeetingCorporation>
        <MeetingCorporation>Berufsverband f&#252;r Orthop&#228;die und Unfallchirurgie</MeetingCorporation>
        <MeetingName></MeetingName>
        <MeetingTitle>Deutscher Kongress f&#252;r Orthop&#228;die und Unfallchirurgie (DKOU 2026)</MeetingTitle>
        <MeetingSession>Grundlagenforschung &#124; Trauma und Inflammation 1</MeetingSession>
        <MeetingCity>Berlin</MeetingCity>
        <MeetingDate>
          <DateFrom>20261020</DateFrom>
          <DateTo>20261023</DateTo>
        </MeetingDate>
      </Meeting>
    </SourceGroup>
    <ArticleNo>DKOU26&#95;Abs&#95;2289</ArticleNo>
  </MetaData>
  <OrigData>
    <TextBlock name="Text" linked="yes">
      <MainHeadline>Text</MainHeadline><Pgraph><Mark1>Objectives and questions: </Mark1>Bone fracture healing is strongly influenced by mechanical loading, yet clinicians rarely know what patients actually do during rehabilitation &#91;1&#93;. We present a case study that combines mechanobiological fracture-healing simulation (OSORA) with continuous weight-bearing monitoring using smart crutches (Comeback Mobility). Using a data-driven patient-specific digital twin of bone healing can be useful for educating patients on the expected healing progress and ultimately help reducing the rate of complications &#91;2&#93;.</Pgraph><Pgraph><Mark1>Material and methods: </Mark1>A surgically treated tibia fracture was reconstructed from clinical imaging (post-OP CT), metadata and observed healing outcome, which was subsequently simulated using OSORA&#8217;s mechanobiological model &#91;3&#93;. For outcome evaluation tissue differentiation, interfragmentary movement (IFM) and consolidation over time were computed. First, the attending surgeon&#8217;s recommended ideal weight-bearing build-up was used to simulate the base scenario with 100&#37; patient compliance presumed. Second, the clinically observed case with loadings recorded by sensor-equipped Smart Crutch Tips&#8482; during daily activities was set up.</Pgraph><Pgraph><Mark1>Results: </Mark1>Simulation results show that the patient frequently exceeded the recommended peak loads of the planned weight-bearing corridor, in particular during the first four to five weeks. Particularly on day 7, the patient applied up to 80&#37; of full weight-bearing load, resulting in high implant stress beyond the fatigue strength in the screws as well as the nail in proximity to the fracture location. Continued overloading can lead to failure of the bone-implant-construct and thus requires monitoring. In silico comparison suggests that strict adherence to the prescribed loading corridor would have led to slightly faster bony consolidation than the actual loading pattern. Episodes of elevated peak load were associated with correspondingly increased IFM and thus locally increased mechanical stimulus. However, the effect on the overall outcome is limited, with a slight delay in bone healing of two days.</Pgraph><Pgraph><Mark1>Discussion and conclusions: </Mark1>A limitation of the methodical approach is, that real weight-bearing is imposed without regard of the healing progress, and thus individual pain thresholds might hinder an actual patient from applying this level of load bearing. This case highlights how combining wearable-derived loading data with predictive simulation can make hidden aspects of rehabilitation visible and clinically actionable. For clinicians, the workflow supports holistic planning from osteosynthesis choice to weight-bearing progression and potential revision. For patients, quantified feedback on both average and peak load can improve understanding and compliance. Next steps include streamlined data integration, enabling near-real-time computation and validation in larger prospective cohorts.</Pgraph></TextBlock>
    <Media>
      <Tables>
        <NoOfTables>0</NoOfTables>
      </Tables>
      <Figures>
        <NoOfPictures>0</NoOfPictures>
      </Figures>
      <InlineFigures>
        <NoOfPictures>0</NoOfPictures>
      </InlineFigures>
      <Attachments>
        <NoOfAttachments>0</NoOfAttachments>
      </Attachments>
    </Media>
  </OrigData>
</GmsArticle>