K213519 · Rune Labs, Inc. · GYD · Jun 10, 2022 · Neurology
Device Facts
Record ID
K213519
Device Name
Rune Labs Tremor Transducer System
Applicant
Rune Labs, Inc.
Product Code
GYD · Neurology
Decision Date
Jun 10, 2022
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 882.1950
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K213519 · Jun 10, 2022
Rune Labs Tremor Transducer System
Rune Labs, Inc.
Longitudinal patient study (all-day living data); Longitudinal control study (elderly non-PD subjects); Published clinical literature (Powers et al., 2021)
The device algorithm (MM4PD) was validated using real-world data from patients with Parkinson's disease and elderly controls to demonstrate correlation between smartwatch-derived movement metrics and clinical ratings of tremor and dyskinesia.
Parkinson's disease; Tremor; Dyskinesia; Longitudinal monitoring; Real-world data
Clinical Evidence
Study Design
Population
Comparator
Key Endpoints
Powers et al. (2021) Longitudinal Patient and Control Studies; Longitudinal observational study using all-day living data; Follow-up/Duration: >59,000 hours of all-day data
Adults with Parkinson's disease and elderly controls without Parkinson's; Sample Size: 343 participants with PD; 171 elderly controls
Not applicable for this study
Correlation between smartwatch-derived tremor/dyskinesia percentages and clinical MDS-UPDRS ratings
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Tremor
Motor Fluctuations Monitor for Parkinson's Disease (MM4PD) toolkit
—
Spearman's rank correlation coefficient of 0.72
Pilot study: N=69; Longitudinal patient study design set: first 143 subjects; Longitudinal control study: N=236
>1 (MDS-certified experts)
Longitudinal patient study hold-out set: n=43
>1 (MDS-certified experts)
Dyskinesia
Motor Fluctuations Monitor for Parkinson's Disease (MM4PD) toolkit
—
P < 0.027 (Wilcoxon rank sum test)
Pilot study: N=10; Longitudinal patient study design set: first 143 subjects; Longitudinal control study: N=171
3 (MDS-certified experts)
Longitudinal patient study hold-out set
3 (MDS-certified experts)
Indications for Use
The Rune Labs Kinematic System is intended to quantify kinematics of movement disorder symptoms including tremor and dyskinesia, in adults (45 years of age or older) with mild to moderate Parkinson's disease.
Device Story
System collects wrist movement data via Apple Watch accelerometers and gyroscopes; utilizes Apple's Motor Fluctuations Monitor for Parkinson's Disease (MM4PD) toolkit to calculate probability scores for tremor and dyskinesia. Data processed on-watch and uploaded to Rune Labs Cloud Platform via cellular/wireless network. Clinicians access cloud-based visualizations to monitor patient symptoms over time. Output assists clinicians in assessing movement disorder fluctuations; enables continuous monitoring compared to traditional episodic reporting. Benefits include improved longitudinal symptom tracking for Parkinson's management.
Clinical Evidence
Clinical validation based on Powers et al. (2021) study. Tremor validation: Spearman's rank correlation (ρ=0.72) between daily tremor percentage and MDS-UPDRS tremor constancy score (n=95 design set, n=43 hold-out). Dyskinesia validation: Wilcoxon rank sum test showed significant differences (p<0.001 design set; p=0.027 hold-out) between patients with/without chorea. False-positive rates: 0.25% for tremor in elderly controls; 2.0% median for dyskinesia in elderly controls. Bench testing confirmed correlation (r=0.98) with Vicon motion capture system.
Technological Characteristics
Software-only system interfacing with Apple Watch (accelerometers/gyroscopes). Data transmission via cellular/wireless network to cloud platform. Web-based clinician interface. Algorithm: MM4PD toolkit for tremor/dyskinesia classification. No specific materials or sterilization required as it is a software-only device.
Indications for Use
Indicated for adults aged 45+ with mild to moderate Parkinson's disease to quantify tremor and dyskinesia symptoms.
Regulatory Classification
Identification
A tremor transducer is a device used to measure the degree of tremor caused by certain diseases.
{0}------------------------------------------------
June 10, 2022
Image /page/0/Picture/1 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left, there is a seal with an abstract design. To the right of the seal, there is the FDA logo in blue, with the words "U.S. FOOD & DRUG" stacked on top of "ADMINISTRATION". The logo is simple and professional, and it is easily recognizable.
Rune Labs, Inc. % Courtney Lane CEO/Principal Consultant Anacapa Clinical Research Inc. 2421 Sunset Dr. Ventura, CA 93001
#### Re: K213519
Trade/Device Name: Rune Labs Kinematics System Regulation Number: 21 CFR 882.1950 Regulation Name: Tremor Transducer Regulatory Class: Class II Product Code: GYD Dated: May 11, 2022 Received: May 13, 2022
#### Dear Courtney Lane:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part
{1}------------------------------------------------
801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
for Jay Gupta Assistant Director DHT5A: Division of Neurosurgical, Neurointerventional and Neurodiagnostic Devices OHT5: Office of Neurological and Physical Medicine Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K213519
Device Name Rune Labs Kinematic System
Indications for Use (Describe)
The Rune Labs Kinematic System is intended to quantify kinematics of movement disorder symptoms including tremor and dyskinesia, in adults (45 years of age or older) with mild to moderate Parkinson's disease.
| Type of Use (Select one or both, as applicable) |
|-------------------------------------------------|
|-------------------------------------------------|
X Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
#### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
Image /page/3/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube made of lines, followed by the text "rune labs" in a simple, sans-serif font. The logo is in black and white.
# 510(k) Summary
# Contact Details
Applicant Name: Rune Labs Inc. Applicant Address: 649 Irving Street, San Francisco, CA 94122, United States Applicant Contact Telephone: 360-606-2929 Applicant Contact: Mr. Brian Pepin Applicant Contact Email: brian@runelabs.io
Correspondent Name: Anacapa Clinical Research Inc. Correspondent Address: 2421 Sunset Dr.. Ventura. CA. 93001. United States Correspondent Contact Telephone: 805-856-8141 Correspondent Contact: Dr. Courtney Lane Correspondent Contact Email: courtney@runelabs.io
# Device Name
Device Trade Name: Rune Labs Kinematics System Common Name: Tremor transducer Classification Name: Transducer, Tremor Regulation Number: 882.1950 Product Code: GYD
# Legally Marketed Predicate Devices
Predicate # K140086 Predicate Trade Name: Personal Kinetigraph (PKG) System Product Code: GYD
# Device Description Summary
The Rune Labs Kinematic System collects derived tremor and dyskinesia probability scores using processes running on the Apple Watch, and then processes and uploads this data to Rune's cloud platform where it is available for display for clinicians.
The Rune Labs Kinematic System uses software that runs on the Apple Watch to measure patient wrist movements. These movements are used to determine how likely dyskinesias or tremors are to have occurred. The times with symptoms are then sent to the Rune Labs Cloud Platform using the Apple Watch's internet connection, which is then displayed for clinician use.
The Apple Watch contains accelerometers and gyroscopes which provide measurements of wrist movement. The Motor Fluctuations Monitor for Parkinson's Disease (MM4PD) is a toolkit developed by Apple for the Apple Watch that assesses the likely presence of tremor and
{4}------------------------------------------------
Image /page/4/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube or a stylized representation of interconnected nodes, placed to the left of the text "rune labs". The text is in lowercase and appears to be in a sans-serif font.
dyskinesia as a function of time. Specifically, every minute, the Apple Watch calculates what percentage of the time that tremor and dyskinesia were likely to occur. The movement disorder data that is output from the Apple's MM4PD toolkit have been validated in a clinical study (Powers et al., 20211).
The Rune Labs Kinematic System is software that receives, stores, and transfers the Apple Watch MM4PD classification data to the Rune Labs Cloud Platform where it is available for visualization by clinicians. The device consists of custom software that runs on the users' smart watch and web browsers.
# Intended Use/Indications for Use
The Rune Labs Kinematic System is intended to quantify kinematics of movement disorder symptoms including tremor and dyskinesia, in adults (45 years of age or older) with mild to moderate Parkinson's disease.
# Indications for Use Comparison
The predicate indication for use statement is as follows:
"The Personal Kinetigraph (PKG) System is intended to quantify kinematics of movement disorder symptoms in conditions such as Parkinson's disease, including tremor, bradykinesia and dyskinesia. It includes a medication reminder, an event marker and is intended to monitor activity associated with movement during sleep. The device is indicated for use in individuals 46 to 83 years of age."
Rune Labs does not currently detect bradykinesia so this symptom measurement is removed. However, bradykinesia can still be assessed clinicians and/or reported by the patient so this change does not constitute a change in the type or level of risk compared to the predicate device.
Medication reminders, event markers, sleep movement, and activity measurements are not included with the Rune Labs Kinematic System. However, this functionality is readily provided by commercially available off-the-shelf software. Therefore, this change does not constitute a significant change in type or level of risk compared to the predicate device.
The algorithm used in the Rune Labs Kinematic System was validated in a clinical study¹ on adults with Parkinson's disease with an age range of 71.4 vrs [±8.9 standard deviation]. The lower cutoff therefore represents three standard deviations from the mean for patients in the validation study, and the upper cutoff is likely limited by the life expectancy of the user. Parkinson's disease typically affects only adults aged 60 or older, and their life expectancy is
<sup>1</sup> Powers R, Etezadi-Amoli M, Arnold EM, Kianian S, Mance I, Gibiansky M, Trietsch D, Alvarado AS, Kretlow JD, Herrington TM, Brillman S, Huang N, Lin PT, Pham HA, Ullal AV. Smartwatch inertial sensors continuously monitor real-world motor fluctuations in Parkinson's disease. Sci Transl Med. 2021 Feb 3;13(579):eabd7865. doi: 10.1126/scitranslmed.abd7865. PMID: 33536284.
This document is the sole property of Rune Labs and cannot be reproduced without written consent.
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube or a stylized representation of interconnected nodes, followed by the text "rune labs" in a simple, sans-serif font. The geometric shape is composed of lines that create a sense of depth and connectivity, while the text is clean and modern.
estimated to be 83.3 years?. Therefore, this change does not constitute a significant change in type or level of risk compared to the predicate device.
The environment of use for the PKG System and Rune Labs System are similar, but the Rune Labs device can be used continuously whereas the PKG Watch must be mailed back to the company for data analysis after several days' use. Continuous monitoring is likely to improve the ability for physician's to monitor their patients over time so this change does not constitute a significant change in type or level of risk compared to the predicate device.
# Technological Comparison
The key operating principle of the system and the predicate is the recording and analysis of the patient's wrist movement to provide a report to the clinician regarding the presence or absence of movement disorders systems.
#### Comparison of Outputs and Features
The Rune Lab device outputs are the percentage of the time that tremor and dyskinesia were likely to occur while the PKG device outputs are an estimate of when tremor is present, a percent time that tremor is present (PTT), and an estimate of dyskinesia scores every two minutes over 10 days. The PKG device also provides information about bradykinesia (see above).
While the technological details of the tremor and dyskinesia detection algorithms are not the same as the predicates, this difference does not raise new types of safety or effectiveness questions because the algorithms used were both correlated with accepted scientific methods, such as the UPDRS III.
#### Comparison of Data Transmission
There is a difference between the Rune Kinematic System and the predicate device with respect to the mechanism of data transmission. Rune Labs uploads data from the Apple Watch to the Rune Labs Cloud Platform using either a cellular or wireless network. The predicate device requires the device to be mailed back to the manufacturer for processing, and then a report is emailed to the clinician.
We have noted that a newer device by the same manufacturer has been cleared by the FDA and is deemed substantially equivalent to the predicate device (K161717³), which uses wireless communication to upload the patient data via the internet. This device can be considered a reference device for the Rune Kinematics and serves to demonstrate that the type of communication protocols used do not impact the safety and effectiveness of the device, provided that controls are in place that the data is preserved across the the various communication methods, which we have shown in our verification testing.
<sup>2</sup> https://www.mayoclinic.org/diseases-conditions/parkinsons-disease/syc-20376055
<sup>3</sup> https://www.accessdata.fda.gov/cdrh_docs/pdf16/K161717.pdf
This document is the sole property of Rune Labs and cannot be reproduced without written consent.
{6}------------------------------------------------
Image /page/6/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube made of lines, followed by the text "rune labs" in a sans-serif font. The cube is positioned to the left of the text, and both elements are in a dark color, likely black or a dark gray, against a white background.
#### Comparison of System Design
The Rune Labs device is a software-only device that interfaces with a toolkit provided by a consumer electronics device manufacturer (Apple) whereas the predicate device is a hardware and software system. However, the Apple Watch is used as the hardware component for other medical devices, such as the Apple electrocardiograph device (DEN180044) and photoplethysmograph device (DEN180042), which can be considered reference devices. Rune Labs will monitor and evaluate toolkit and Apple Watch releases to ensure that software or hardware changes released by the manufacturer do not affect the device performance. Therefore this difference will not impact the safety or effectiveness of the device.
#### Summary of Technical Comparison
Overall, the differences in the usability and design of the Rune Labs Kinematics System, which allows for longer use and direct upload of data, do not affect the safety and effectiveness of the device as compared to the predicate device.
#### Non-Clinical and/or Clinical Tests Summary
Software testing established that the system meets the software requirements and user needs for the intended uses.
Apple's MM4PD has been clinically validated as described in Powers et al. (2021)1, and the validation is summarized below. Table 1 shows baseline demographics for patients used in the validation studies.
{7}------------------------------------------------
Image /page/7/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube made of lines, followed by the text "rune labs" in a simple, sans-serif font. The logo is in black and white.
| | Pilot study<br>PD patients in-clinic + 1<br>week live-on | Longitudinal patient study<br>PD patients long-term live-on | Longitudinal control<br>study<br>Elderly controls |
|-------------------------------------------------|----------------------------------------------------------|-------------------------------------------------------------|---------------------------------------------------|
| Age [± Standard<br>Dev] | 68.1 yrs [±9.0] | 71.4 yrs [±8.9] | 74.7 yrs [±5.4] |
| Years with PD [±<br>Standard Dev] | 6.5 yrs [±5.6] | 10.3 yrs [±6.5] | n/a |
| Gender | 36 Female, 82 Male | 69 Female, 156 Male | 85 Female, 85 Male, 1<br>unknown |
| Most Affected Side | 62 Right / 39 Left / 17<br>unspecified | 105 Right / 120 Left | n/a |
| History of Tremor | - | 166/225 Participants | n/a |
| History of<br>Dyskinesia<br>(History of Chorea) | - | 94/225 Participants<br>(66/94 with dyskinesia) | n/a |
| History of Freezing<br>Gait | - | 85/225 Participants | n/a |
| History of Slow<br>Gait | - | 172/225 Participants | n/a |
| | | *self-reported history | |
#### Table 1: Subject demographics for the Powers et al. (2021) study1
#### 1.1. Measured Watch displacements compared to motion measurements
The measured watch movement was correlated with the measurements taken from a commercially available motion tracking system (Vicon; see Figure 1). A healthy control subject simulated tremor movements with varying amplitudes while wearing the Apple Watch in seated and standing positions. The Pearson correlation coefficient between displacement measured by the motion capture system and the watch estimate was 0.98 in a control subject with a mean signed error of -0.04 ± 0.17 cm.
{8}------------------------------------------------
Image /page/8/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube or a stylized representation of interconnected nodes, followed by the text "rune labs" in a simple, sans-serif font. The logo and text are both in black and white.
Image /page/8/Figure/1 description: The figure is a scatter plot comparing smartwatch estimates to motion capture reference values, both measured in centimeters. Data points are categorized by number and activity (sit or stand), with different colors representing each category. The plot shows a generally positive correlation between the two measurement methods, as indicated by the dashed line, but there is some scatter around the line, especially at higher values.
Fiqure 1: Apple Watch estimate of motion as a function of measurements from a commercially available motion capture system (Vicon). From Powers et al., 2021, Figure 3A.
#### 1.2. Tremor Validation
The tremor detection algorithm was developed using data collected from the following data sets:
1. Pilot study: N=69 subjects in the pilot study, with tremor reported during a stationary task (mainly sitting tasks such as cognitive distraction or hands-in-lap but also during standing periods)
2. Longitudinal patient study: subiects in the longitudinal patient study design set (first 143 subjects enrolled) with tremor reported during a stationary task
3. Longitudinal control study: All day living data from additional subjects without Parkinson's (N=236 subjects, >59,000 hours of data)
The mean daily tremor detection rate for all subjects from the longitudinal patient study was compared to the clinician's overall tremor rating, which takes both constancy of tremor and severity into account. Design set patients were used to determine the tremor detection algorithm, and a hold-out set was used to ensure that these cutoffs were well correlated in additional subjects. The daily tremor percentage was calculated as the total detected tremor time divided by the total time period the watch was worn. Watch wear time excluded periods where the subject was likely asleep or where the watch was not being worn as indicated by a lack of device movement. This percentage was then averaged across all the days the subject was in the study. Six subjects were excluded because they had insufficient data for analysis. The Spearman's rank correlation coefficient between the daily tremor percentage and the clinicians' tremor constancy score was calculated.
All-day tremor estimates from the longitudinal patient study, as quantified by an individual's mean percentage of time with tremor detected per day, correlated with their MDS-UPDRS
{9}------------------------------------------------
Image /page/9/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube made of lines, followed by the text "rune labs" in a simple, sans-serif font. The logo and text are both in black and white.
tremor constancy score assessed during a brief, in-clinic visit at the start of the study, with a Spearman's rank correlation coefficient of 0.72 in the design set (n = 95) and in the hold-out set (n = 43) (Figure 2).
Image /page/9/Figure/2 description: The image shows two box plots comparing the mean daily tremor (%) to the MDS-UPDRS tremor constancy. Both plots are labeled as a longitudinal patient study with \( \rho = 0.72 \). The left plot shows the number of patients with MDS-UPDRS tremor constancy of 0, 1, 2, 3, and 4 are 36, 18, 17, 11, and 13, respectively. The right plot shows the number of patients with MDS-UPDRS tremor constancy of 0, 1, 2, 3, and 4 are 19, 6, 4, 7, and 7, respectively.
#### Figure 2: Mean daily tremor percentage compared to MDS-UPDRS tremor constancy score from the longitudinal study for the design set (left; n = 95) and hold-out set (right; n = 43). Rank correlation coefficient for the design set is 0.72; for the hold-out set rank correlation coefficient is also 0.72. From Powers et al., 2021, Figure 3D and E.
False positives occurred 0.25% of the time when evaluated in 171 elderly, non-PD longitudinal control subjects using over 43,300 hours of all-day data. False positives were also rare during targeted activities in young, healthy controls, such as manual teeth brushing (8%) and playing a musical instrument (2%; see Table S2 in Powers et al., 2021).
- 1.3. Dyskinesia Validation
The dyskinesia detection algorithm was designed using data collected from the following data sets:
1. Pilot study: N=10 subjects from the pilot study, divided evenly between subjects observed to have choreiform dyskinesia reqularly affecting the wrist on which the watch was worn and subjects with no history of any dyskinetic symptoms (one week of all-day data for each subject)
2. Longitudinal patient study: N=97 subjects from the longitudinal patient study design set (first 143 subjects enrolled), consisting of 22 subjects with choreiform dyskinesia and 75 with no history of choreiform dyskinesia (>25,000 hours of all-day data)
This document is the sole property of Rune Labs and cannot be reproduced without written consent.
{10}------------------------------------------------
Image /page/10/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube or a series of interconnected lines, followed by the text "rune labs" in a simple, sans-serif font. The logo and text are both in black and white.
3. Longitudinal control study: N=171 subjects without Parkinson's from the Longitudinal Control study (>59,000 hours of all-day data)
The dyskinesia algorithm was designed and validated across 343 participants with PD (61 with dyskinesia) and 171 elderly, non-PD controls. The choreiform movement score (CMS) was calculated from sensor data in the pilot study and compared to dyskinesia ratings from three MDS-certified experts during multiple MDS-UPDRS assessments. The CMS was used to classify data into 1 minute segments where dyskinesia was likely or not.
CMS showed significant differences (P < 0.001) for all pairwise comparisons using a Wilcoxon rank sum test across three groups: (i) 65 subjects with confirmed absence of in-session dyskinesia by all three raters (89 tasks), (ii) 69 subjects with discordant dyskinesia ratings (109 tasks), and (iii) 19 subjects with confirmed dyskinesia across all three raters (22 tasks, Figure 3).
Image /page/10/Figure/4 description: This image is a boxplot comparing CMS values across three conditions: DK absent, raters disagree, and DK present. The CMS values for the DK absent condition have a sample size of approximately 89, while the raters disagree condition has a sample size of approximately 109, and the DK present condition has a sample size of 22. Statistical significance (p < 0.001) is indicated by asterisks (***) between the DK absent and raters disagree conditions, as well as between the raters disagree and DK present conditions, and below the DK absent condition.
Figure 3: Chorea movement scores computed during in-clinic cognitive distraction tasks for the pilot study differentiated between the presence of dyskinesia (DK) as based on expert ratings (p < 0.001 for all pairwise comparisons, using Wilcoxon rank sum test).
This document is the sole property of Rune Labs and cannot be reproduced without written consent.
{11}------------------------------------------------
Image /page/11/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube constructed from lines, positioned to the left of the text "rune labs". The text is in a simple, sans-serif font and is horizontally aligned with the geometric shape.
Image /page/11/Figure/1 description: The image contains two box plots comparing dyskinesia detection percentages between 'No DK' and 'Chorea' groups. The left plot shows a significant difference (***) with 'No DK' having n=125 and 'Chorea' having n=32, with a 51% increase noted. The right plot also shows a difference (*) between 'No DK' (n=47) and 'Chorea' (n=10), though the percentage increase is not specified.
Fiqure 4: Mean daily dyskinesia percentage compared to dyskinesia ratings from the longitudinal study for the design set (left) and hold-out set (right). The amount of dyskinesia detected in patients significantly differed between subjects with and without chorea in both the design set (p<0.001 using Wilcoxon rank sum test) and hold-out set (p=0.027 using a Wilcoxon rank sum test). From Powers et al., 2021, Figure 4D and E.
The amount of dyskinesia detected by MM4PD significantly differed between subjects with PD with known chorea and those without, in both cross-validation and hold-out datasets. In the cross-validation design set (Figure 4, left), dyskinesia was detected for an average of 10.7 ± 9.9% (mean ± standard deviation) of the day in 32 subjects with chorea. In contrast, dyskinesia was detected for 2.7 ± 2.2% of the day in 125 patients with PD with no known dyskinesia (p < 0.001, Wilcoxon rank sum test). In a hold-out dataset from the longitudinal patient study, the percentage of time dyskinesias were detected for the chorea group (5.9 ± 5.3%) significantly differed from subjects with no reported dyskinesias (2.0 ± 2.2%) (P = 0.027, Wilcoxon rank sum test; Figure 4, right).
Dyskinesia false-positive rates were low across common activities like walking (1%). In all-day data from elderly, non-PD controls in the longitudinal control study, the median false-positive rate was 2.0% (Powers et al, 2022, Table S2). However, specific activities that mimic choreiform movements, such as playing the piano, had high false-positive rates (Powers et al, 2022, Table S2).
- 1.4. Clinical Validation Summary
Overall, the outputs of the MM4PD algorithm provide detection of tremor and dyskinesia
{12}------------------------------------------------
Image /page/12/Picture/0 description: The image shows the logo for Rune Labs. The logo consists of a geometric shape resembling a cube made of lines, followed by the text "rune labs" in lowercase letters. The geometric shape is on the left, and the text is on the right.
symptoms in Parkinson's disease patients that are well correlated with clinical ratings of tremor constancy and dyskinesia presence.
# Conclusions
While the Rune Labs Kinematics System Indications for Use are not identical to the Indications for Use of the predicate device, the minor differences do not alter the intended effects or impact safety or effectiveness, as they are achieved using the same mechanisms of action and the same types of data. Moreover, the minor differences in the Indications for Use of the Rune Labs Kinematic System does not change the type of risk or increase the level of risk as compared to the predicate device. The Rune Labs Kinematic System therefore is considered substantially equivalent to its predicate device.
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.