Findings
TOMs are underutilized in clinical trials for neurodegenerative disorders.
Challenges include relevance of measured targets, standardization of parameters, costs, and patient compliance.
Lack of validation studies for TOMs' clinical meaningfulness and issues with proprietary platform integration.

Recommendations
Validate TOMs output to ensure clinical meaningfulness.
Standardize clinically relevant measures and procedures.
Establish a single platform for data integration from various proprietary platforms.
Assist in regulatory approvals to facilitate wider use of TOMs.
Enhance the ecological validity of TOMs by using them in natural settings.

Regulatory Considerations
Overcome regulatory roadblocks for wider use of TOMs.
Assist manufacturers in obtaining regulatory approvals for TOMs.
Address integration issues with proprietary platforms from different manufacturers.

Findings
Successful PT implementation requires iterative planning across six stages to adapt to changing study goals and patient needs.
Early engagement with patients, caregivers, sites, and regulatory bodies is critical to align PT goals with stakeholder priorities.
Identifying technical, operational, and compliance risks early on is essential for smooth implementation and scalability.
Rapid, small-scale tests of technologies can help address unknowns, refine user experience, and mitigate technical risks before full-scale pilots.
Scaling PT across geographies and populations requires addressing regional variations in infrastructure, regulations, and cultural acceptance.

Recommendations
Start with a clear, organization-wide PT strategy to align with clinical trial goals and define success metrics.
Involve patients, sites, and regulatory authorities early to gather insights and ensure alignment with their needs and priorities.
Test technologies in controlled environments to validate functionality, usability, and integration before pilot studies.
Use technology pilots to collect data on feasibility, usability, and implementation challenges to inform broader rollouts.
Leverage learnings from pilots to develop a scalable strategy that addresses technical, regulatory, and cultural barriers.

Regulatory Considerations
Determine whether the technology is classified as a medical device and ensure compliance with relevant regulations (e.g., FDA, EMA, MDR).
Address data protection regulations, such as GDPR, by implementing robust privacy measures and secure data storage practices.
Account for region-specific regulatory requirements and infrastructure challenges during scaling.
Proactively consult regulatory agencies during pilots to align on technology use, endpoints, and data validity.

Findings
D-PPAC (daily tool) and C-PPAC (weekly tool) are hybrid tools combining subjective patient inputs with objective activity monitor outputs, offering comprehensive insights into PA levels.
Psychometric validation indicates reliability, with high internal consistency and construct validity, though test-retest reliability is limited to specific trials.
Both tools are sensitive to changes in physical activity, but interpretation is limited in patients with very severe COPD or significant comorbidities.
Minimal important difference (MID) thresholds were identified for domains and total scores, though their clinical meaningfulness remains under investigation.
The tools' interchangeability within trials is limited due to differing score ranges and measurement approaches.

Recommendations
Apply D-PPAC in trials where daily monitoring of physical activity is a primary endpoint.
Use C-PPAC in trials requiring supportive outcome data or when minimizing patient burden is critical.
Train investigators and patients thoroughly to ensure high compliance with both tools.
Further refine the total score derivation methodology to enhance interpretability and clinical relevance.
Expand validation efforts to include patients with broader comorbidity profiles and greater PA limitations.

Regulatory Considerations
Restrict the tools' use to the validated activity monitors (Actigraph G3TX and Dynaport MoveMonitor) until further assessments are conducted.
MID thresholds should be used with caution, considering their limited precision and potential variability across different populations.
The use of these PRO tools in regulatory submissions must align with EMA's guidance for COPD, ensuring endpoints align with study objectives.

Findings
The integration of mobile devices into interventional research, specifically RCTs, is evolving slowly.
There is a lack of standardization in mobile outcome assessments, making it difficult to compare results across studies.
Current definitions for conventionally measured outcomes do not adequately reflect the novelty of mobile outcome assessments.

Recommendations
Emphasize validating the clinical meaningfulness of mobile outcome assessments.
Develop new mobile outcome assessments for future clinical research.
Use CTTI's recommendations and tools for selecting appropriate mobile outcomes as trial endpoints.

Regulatory Considerations
Standardization is necessary to facilitate the acceptance and use of mobile outcomes in regulatory interventional research.
Validation of mobile outcomes is crucial for their use in regulatory decision-making.
The development of new categories or modification of current definitions may be needed to accommodate novel measures using mobile devices.

Findings
Challenges related to data safety, quality, privacy, and regulatory requirements in smart sensor technologies.
Bias in standard RCTs due to exclusion of participants with language or motor barriers.
Need for ICT systems to detect smooth transitions in cognitive abilities and everyday functions.

Recommendations
Develop ICT-based procedures that capture relevant clinical features validly.
Ensure data fidelity and robustness in ICT systems.
Incorporate user needs into ICT solutions.
Address data safety and privacy concerns.
Develop international policies for access, security, and privacy in ICT solutions.

Regulatory Considerations
Need for international efforts to address gaps in policies around access, security, and privacy.
Current laws do not cover health information on mobile apps or the Internet.
Lack of regulation could undermine the credibility of RWE results.

Findings
Concerns about data accuracy, particularly variability in measurements across different age groups and devices.
Issues with data provenance, as raw data from wearables are often transformed and filtered before storage, making comprehensive analysis difficult.
Regulatory challenges due to lack of specific FDA guidance for clinical trials using wearables and mobile devices.

Recommendations
Improve data accuracy through standardized approaches and expert recommendations.
Enhance data provenance by developing methods to trace data lineage and ensure transparency in data processing.
Develop specific FDA guidance for the use of wearables and mobile devices in clinical trials.
Implement robust security measures to protect data integrity and privacy.
Follow the ePRO Consortium's recommendations for device suitability in clinical trials.

Regulatory Considerations
The need for FDA guidance specific to clinical trials using mHealth technologies.
Sponsors' responsibility to validate the reliability of mHealth technology in capturing and transmitting data.
Security vulnerabilities in devices, necessitating adherence to privacy standards and robust security protocols.

Findings
Researchers face challenges in scientific methodology, regulatory, legal, and operational aspects.
Many consumer-grade devices lack scientific evidence for their health claims.
There are significant challenges in data management, infrastructure, analysis, and security.
Lack of mobile technology data standards and transparency in data processing algorithms.
The need for a shared understanding of methodologies and terminology.

Recommendations
Develop industry-wide standards for data and terminology.
Foster dialogue between biopharmaceutical industry and device manufacturers for methodological development.
Ensure a patient-centric approach in clinical trials using wearable devices.
Conduct well-powered studies with clear medical problem statements.
Implement rigorous analytical and clinical validation processes.

Regulatory Considerations
Separate marketing approval paths for drugs and devices in the US.
Most wearable devices are classified as Class II devices requiring 510(k) clearance.
Compliance with HIPAA for data obtained via medical devices.
Need for device performance validation in specific populations relevant to device label claims.
Differences in US and EU regulations regarding data protection and consent requirements.

Findings
Traditional endpoints like HbA1c are insufficient to assess hypoglycemia's impact on quality of life and daily function for diabetes patients.
CGM offers continuous, objective glucose monitoring, enabling the detection of glycemic variability and hypoglycemic episodes in real-time.
Stakeholders, including regulators, industry, and patients, emphasize the need for CGM-derived endpoints to complement traditional biomarkers.
Challenges include standardizing hypoglycemia definitions, creating shared databases for CGM data, and addressing technical limitations at lower glucose levels.
Patient-reported outcomes (PROs) combined with CGM data can provide a comprehensive view of treatment effects but require further validation.

Recommendations
Establish consensus definitions of hypoglycemia and standardized metrics for CGM-based endpoints, such as percent reduction in hypoglycemia duration or frequency.
Create shared CGM databases to facilitate data analysis and validation of novel endpoints across clinical trials.
Conduct CGM-based studies to correlate hypoglycemia metrics with meaningful patient outcomes, including wellness, disease burden, and functional impacts.
Integrate CGM endpoints into regulatory submissions alongside traditional measures like HbA1c to demonstrate comprehensive treatment effects.
Collaborate with stakeholders to address technical challenges, such as CGM accuracy at lower glucose levels, and explore their application in pediatric populations in the future.

Regulatory Considerations
Validate CGM-derived endpoints to align with regulatory requirements, demonstrating their predictive value for severe hypoglycemia and other meaningful outcomes.
Engage regulators early to ensure CGM metrics complement existing endpoints like HbA1c and address unmet needs in diabetes trials.
Address technical limitations, such as CGM calibration and data accuracy at low glucose levels, to meet evidentiary standards for clinical trial endpoints.
Develop and document statistical methodologies for analyzing CGM-derived endpoints, including handling missing data and variability.
Include patient-reported outcomes and quality-of-life measures to contextualize CGM data in regulatory submissions.

Findings
Current PD endpoints, such as UPDRS and PDQ scales, rely on subjective assessments and may not fully capture disease fluctuations or treatment effects.
Accelerometer technology offers objective and continuous data, addressing limitations of traditional endpoints.
The proposed endpoint focuses on "bothersome tremor," validated through observational studies and patient input.
Collaboration among stakeholders, including regulators and technology manufacturers, is crucial for endpoint development and standardization.
Developing a basket of endpoints, including accelerometer-derived measures, can provide a more comprehensive picture of PD burden and treatment impact.

Recommendations
Define the context of use (COU) for accelerometer-derived endpoints, focusing on patient-centered measures like "number of episodes and total duration of bothersome tremor."
Validate accelerometer data through real-world and controlled studies, correlating it with existing PD measures and clinical outcomes.
Collaborate with technology manufacturers to optimize accelerometer placement, signal detection, and patient usability.
Engage with regulators early to align novel endpoints with evidentiary and regulatory requirements.
Establish frameworks for data sharing and standardization to facilitate endpoint development and adoption.

Regulatory Considerations
Validate endpoints to ensure alignment with existing PD measures and regulatory standards for clinical trials.
Incorporate patient feedback during endpoint development to support meaningful and relevant measures.
Address intellectual property (IP) concerns by redefining IP as the execution of algorithms rather than the algorithms themselves.
Align trial design with regulatory requirements, ensuring endpoints can reliably measure treatment impact on PD symptoms.
Engage regulators early to obtain feedback and confirm endpoint readiness for regulatory submission.

Findings
Software changes must be assessed for potential impacts on the safety and effectiveness of the device, even if they are routine updates.
A risk-based assessment is required to determine whether changes introduce new risks, modify existing risks, or necessitate new risk controls.
Cybersecurity updates, routine maintenance changes, and minor clarifications may not require a new 510(k) if they do not affect performance specifications or safety.
Substantial modifications, such as adding new algorithms, introducing new functionalities, or modifying clinical performance, generally require a new 510(k).
Manufacturers must document all changes, even those not requiring a new 510(k), in compliance with QS regulations.

Recommendations
Use the provided flowchart and guiding principles to evaluate whether software changes exceed the regulatory threshold for submission of a new 510(k).
Conduct a risk-based assessment for all changes, focusing on new or modified risks and the adequacy of existing risk controls.
Verify and validate changes to ensure they meet device specifications and do not introduce unintended consequences.
Submit a new 510(k) for changes that significantly affect clinical functionality, performance specifications, or introduce new risks that are not mitigated.
Maintain detailed documentation of all decisions regarding software changes, including rationale for whether submission of a new 510(k) was required.

Regulatory Considerations
Submission of a new 510(k) is required for changes that could significantly impact the safety or effectiveness of a device or constitute a major modification to its intended use.
Cybersecurity updates generally do not require a new 510(k) if they solely strengthen security without affecting device performance.
Manufacturers must evaluate cumulative changes and submit a new 510(k) if the combined impact exceeds the regulatory threshold.
Device software changes involving substantial algorithm modifications or system architecture updates are likely to require a new 510(k).
Changes that address compliance during a recall or correction must be evaluated under FDA's guidance for recalls and device enhancements.

Findings
Interoperable medical devices require design considerations for safe information exchange and use, including standards for data format, transmission, and synchronization.
Risk management should address hazards associated with unintended access, corrupted data, and misuse of interfaces.
Verification and validation should include real-world testing to demonstrate safe operation in specified interoperable scenarios and with representative devices or systems.
Clear labeling is critical to minimize risks and guide users in safely connecting and using the device, particularly in systems with multiple components.
Using recognized consensus standards can support device safety and effectiveness but is voluntary; manufacturers can also implement proprietary designs with openly available interface specifications.

Recommendations
Include the purpose of electronic interfaces in device design and premarket submissions, specifying supported device types, data exchange methods, and use cases.
Identify anticipated users (e.g., clinicians, IT professionals, patients) and address their needs in device design, instructions, and labeling.
Conduct a thorough risk analysis to identify hazards related to interoperability, and implement risk controls for safe and effective device use.
Perform verification and validation testing to confirm device performance under normal and abnormal conditions, including interactions with other devices or systems.
Develop labeling that provides detailed instructions, interface specifications, limitations, and warnings for safe device use and integration.

Regulatory Considerations
Premarket submissions for interoperable medical devices must include:
Detailed device descriptions, including the purpose and functionality of electronic interfaces.
Results of risk analyses, verification, and validation testing.
Labeling that supports safe connection and use in interoperable systems.
Devices incorporating standards-based interfaces should include documentation of conformance to those standards.
Manufacturers should specify the intended use and limitations of electronic interfaces to guide users and mitigate risks.
For complex systems involving multiple devices, a systems-based approach should be used to manage shared risks.
Documentation requirements vary based on device risk level and intended use, with detailed test reports required for high-risk systems and summaries acceptable for low-risk cases.

Findings
Clearly defining the Context of Use (CoU) is essential for regulatory assessment and qualification success.
Qualification requires robust diagnostic and prognostic performance, including sensitivity, specificity, and predictive values.
Statistical analysis plans (SAPs) must be pre-specified and justify the inclusion of exploratory and confirmatory data sets.
Clinical utility should be demonstrated by showing the methodology’s impact on diagnostic thinking, patient management, and outcomes.
Validation of the analytical platform for its intended Context of Use is critical to ensure reliability and robustness.

Recommendations
Define the Context of Use (CoU) with clarity, specifying how the novel methodology will be applied and its purpose in drug development.
Validate the analytical platform and demonstrate its robustness for the intended application.
Ensure statistical planning aligns with regulatory expectations, with pre-specified analysis plans and justification for exploratory and confirmatory approaches.
Establish clinical utility by detailing the methodology’s impact on patient management and clinical outcomes.
Address limitations to the standard of truth with appropriate surrogate standards, where necessary, ensuring they are well-justified.

Regulatory Considerations
Follow ICH guidelines, including ICH E16 (genomic biomarkers), ICH E18 (sampling and data management), and ICH E9 (statistical principles for clinical trials), for data structure and validation.
Use reflection papers on pharmacogenomic samples and data handling for guidance on sample storage, transport, and testing.
Ensure compliance with regulatory requirements for analytical and performance validation, as specified in EMA guidance documents.
Leverage cross-validation methods, especially in rare disease scenarios, with pre-specified methodologies.