The Neu Platform is intended to quantify the kinematics of movement disorder symptoms, including tremor in adults (45 years and older) with mild to moderate Parkinson's disease.
Device Story
Neu Platform captures digital motor and patient-reported data for Parkinson's disease management. Input: accelerometer data from commercial off-the-shelf (COTS) smartphones during patient-performed motor tasks. Operation: software application collects sensor data, which is transmitted to a cloud-based backend; clinician dashboard displays quantified tremor kinematics for review. Used in home and clinic settings; operated by patients for data entry and clinicians for monitoring. Output: quantified tremor measurements. Benefit: enables remote tracking of symptom severity to assist clinical decision-making. Does not provide diagnosis or treatment recommendations.
Clinical Evidence
Bench testing only. No clinical or animal studies included. Performance validated by comparing device tremor measurements to the MDS-UPDRS-III clinical standard. Results showed correlation of 0.92 (p<0.01) for rest tremor and 0.85 (p=0.002) for postural tremor, demonstrating equivalence to the predicate device.
Technological Characteristics
Stand-alone software application utilizing COTS smartphone accelerometers. Connectivity via cellular or wireless network to cloud-based central database. Data encrypted via TLS-1.2+ and AES-256. Software developed per IEC 62304; risk management per ISO 14971. Cybersecurity controls include MFA and threat mitigation per FDA guidance.
Indications for Use
Indicated for adults (45 years and older) with mild to moderate Parkinson's disease to quantify kinematics of movement disorder symptoms, including tremor.
Regulatory Classification
Identification
A tremor transducer is a device used to measure the degree of tremor caused by certain diseases.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
April 25, 2025
Neuhealth Digital Ltd.
% Dave Yungvirt
CEO
Third Party Review Group, LLC
25 Independence Boulevard
Warren, New Jersey 07059
Re: K250153
Trade/Device Name: Neu Platform
Regulation Number: 21 CFR 882.1950
Regulation Name: Tremor transducer
Regulatory Class: Class II
Product Code: GYD
Dated: March 5, 2025
Received: March 6, 2025
Dear Dave Yungvirt:
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 (the 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 available 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.
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device"
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K250153 - Dave Yungvirt
Page 2
(https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-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 Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 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-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/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-devices/device-advice-comprehensive-regulatory-assistance/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).
{2}
K250153 - Dave Yungvirt
Page 3
Sincerely,
Jay R. Gupta -S
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
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Indications for Use
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
Submission Number (if known)
K250153
Device Name
Neu Platform
Indications for Use (Describe)
The Neu Platform is intended to quantify the kinematics of movement disorder symptoms, including tremor in adults (45 years and older) with mild to moderate Parkinson's disease.
Type of Use (Select one or both, as applicable)
☑ 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.”
{4}
neu health
Neu Platform
510(k) Summary
# Traditional 510(k) Summary
## Summary of Safety and Effectiveness
This summary of 510(k) safety and effectiveness information is being submitted in accordance with the requirement of 21 CFR 807.92.
Submitter Information:
Name: Neuhealth Digital Ltd.
Address: 10 Fitzroy Square, London, W1T 5HP, United Kingdom
Establishment Registration Number: 3032027298
Owner/Operator Number: 10091292
Phone: +44 330 0430 939
Contact: Giovanni Maggi, Senior Manager of Quality and Regulatory
E-mail: giovanni.maggi@neu.health
Date of Summary: 14-Jan-2025
## Device Information:
Below summarises the Device Classification information regarding the Neu Platform.
| Device Proprietary Name | Neu Platform |
| --- | --- |
| Common Name: | Tremor Transducer |
| Trade Name: | Neu Platform |
| Product Code(s): | GYD |
Primary Product Code
| Regulation Number (21 CFR) | Device | Product Class | Product Code | Classification Panel |
| --- | --- | --- | --- | --- |
| 882.1950 | Tremor Transducer | Class II | GYD | Neurology |
Substantial Equivalence
| Manufacturer | Trade Name | Regulation & Product Code | 510(k) Number |
| --- | --- | --- | --- |
| H2O Therapeutics | Parky App | 882.1950
GYD, NXQ, ISD | K220820 |
## Submission Description
This traditional 510(k) presents a new medical device for the measurement of tremor for patients with Parkinson's Disease. Well-established methods have been used to evaluate the change and the date to be reviewed is provided in a summary in this submission.
## Device Description
### General Description
The Neu Platform is a platform designed to capture digital motor and patient-reported data in patients with mild to moderate Parkinson's Disease. The platform has two key components:
{5}
neu health
Neu Platform
510(k) Summary
- A smartphone application for the remote capture of symptoms - Patients utilise the smartphone application to perform the motor tremor measurement activities. The app is also used for the patient to self-reported data, including onboarding information and subjective symptom information,
- A dashboard for the clinical team to view the captured data - The clinician dashboard presents the data to clinical staff responsible for managing the patient's condition for review.
The Platform is comprised of a patient app, supporting backend infrastructure, and a clinician web-based dashboard. The Neu Platform is related to the components of the platform specifically for data capture from patients with Parkinson's disease. The smartphone application and clinical dashboard have been developed and validated with extensive input from patients and clinicians.
Figure 1 provides a high level schematic of the system, components and operation.

Figure 1: High Level Overview of the Neu Platform
# Intended/ Indications for Use
The Neu Platform is intended to quantify the kinematics of movement disorder symptoms, including tremor in adults (45 years and older) with mild to moderate Parkinson's disease.
# Comparison with the Predicate and Previously Cleared Device
The proposed device is substantially equivalent to the predicate, K220820, the Parky App and a comparison of the key characteristics is summarised in Table 1. The devices are similar in terms of indications for use, technological characteristics and performance data and therefore there are no new or different questions and effectiveness.
| Characteristic | Subject Device Neu Platform | Predicate Device Parky App – K220820 | Equivalence Comparison |
| --- | --- | --- | --- |
| Intended Use | To measure the degree of tremor caused by certain diseases. | To measure the degree of tremor caused by certain diseases. | Same as the predicate |
| Indications for Use | The Neu Platform is intended to quantify the kinematics of movement disorder symptoms, including tremor in | The Parky App is intended to quantify kinematics of movement disorder symptoms including | Similar to the predicate; both the Subject and Predicate device measure tremor. The subject device |
| | adults and their children. | adults and their children. | the patient's condition. |
{6}
Page: 3
| Characteristic | Subject Device Neu Platform | Predicate Device Parky App – K220820 | Equivalence Comparison |
| --- | --- | --- | --- |
| | adults (45 years and older) with mild to moderate Parkinson’s disease. | tremor and dyskinesia, in adults (45 years of age or older) with mild to moderate Parkinson’s disease. | does not measure dyskinesia. |
| Rx vs OTC | Rx | Rx | Same as the predicate |
| Patient Population | 45+ with mild to moderate Parkinson’s disease. | 45+ with mild to moderate Parkinson’s disease. | Same as the predicate |
| Use Environment | Home and clinic. | Home and clinic. | Same as the predicate |
| Measurement method | Accelerometer in commercial off the shelf digital device. | Accelerometer in commercial off the shelf digital device. | Same as the predicate |
| Functionality | Measurement of tremor using accelerometer within digital device; recording of medication, report symptoms and questionnaires. | Measurement of tremor using accelerometer within digital device; recording of medication, report symptoms and questionnaires. | Same as the predicate |
| Software | Software validation conducted as per FDA Guidance ‘Content of premarket submissions for Device Software Functions’, issued May 11, 2005. | Software validation conducted as per FDA Guidance ‘Content of premarket submissions for Device Software Functions’, issued May 11, 2005. | Same as the predicate |
| Hardware/Software | Mobile Phone with internet access. Min OS – iOS 14.1; Android 7. | Apple watch Mobile Phone with internet access. | Similar to the predicate – both devices use off the shelf mobile software and hardware and transmit that using internet. |
| Cybersecurity | Cybersecurity threat analysis and mitigation has been conducted according to “Content of Premarket Submissions for Management of Cybersecurity in Medical Devices”. | Cybersecurity threat analysis and mitigation has been conducted according to “Content of Premarket Submissions for Management of Cybersecurity in Medical Devices”. | Same as the predicate |
| Cybersecurity Encryption & authentication | Data encrypted TLS-1.2+ and AES-256. Patient and clinician secure access with MFA. | Not specified. | All data is encrypted in transit and at rest throughout the system |
| Outputs and features | Measure and quantify degree of tremor. | Measure and quantify degree of tremor. | Same as the predicate |
{7}
Page: 4
| Characteristic | Subject Device Neu Platform | Predicate Device Parky App – K220820 | Equivalence Comparison |
| --- | --- | --- | --- |
| Diagnosis or treatment recommendations | No | No | Same as the predicate |
| Data transmission | Cellular or wireless network. | Cellular or wireless network. | Same as the predicate |
| Off-the-Shelf Software | Utilizes Apple and Android OS and accelerometer to measure and quantify tremor related to Parkinson’s Disease. | Utilizes Apple’s MM4PD API and Apple Watch’s accelerometer to measure and quantify dyskinesia and tremor related to Parkinson’s Disease. | Similar to the predicate; both devices use the accelerometers in mobile devices to perform the measurement |
| Performance data | Device measurements highly correlated to measurements of tremor severity. Correlation of 0.92 (p<0.01) and 0.85 (p=0.002) between the tremor measurement and the clinical standard for the rest and postural tremor measurements respectively. | Device Measurements highly correlated to clinical evaluations of tremor severity (Rank Correlation Coefficient=0.80) and mapped to expert ratings of dyskinesia presence (P<0.001) during in-clinic tasks. Device captured symptom changes in response to treatment that matched the clinician’s expectations in 94% of evaluated subjects. | Similar to the predicate |
| Patient Interface | Stand-alone software running on general purpose commercial off-the-shelf mobile smartphones. Display of tremor activity, medication information and other information. | Stand-alone software running on general purpose commercial off-the-shelf mobile smartphones. Display of tremor activity, medication information and other information. | Same as the predicate |
| Healthcare Professional interface | Data stored in remote central database (i.e., Cloud). Information accessed by clinician via web portal. | Data stored in remote central database (i.e., Cloud). Information accessed by clinician via web portal. | Same as the predicate |
Table 1: Comparison of characteristics between the Subject Device and the Predicate Device.
## Technological Characteristics
### Intended Use
The subject device and the predicate device both measure the kinematics of movement disorders, specifically tremor for patients with mild to moderate Parkinson’s Disease. Both devices capture the measurements through the accelerometers in commercial digital personal devices.
{8}
neu health
Neu Platform
510(k) Summary
The Neu Platform does not currently detect dyskinesia, so this symptom measurement is removed. However, this can still be assessed clinically by the 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.
Neither the Subject device nor the Predicate device provide diagnosis or contain results that provide any diagnostics or treatment recommendations.
## Principle of operation and technology used
The Subject and Predicate Devices use a mobile device such as smartphone/watch and its sensors (e.g., accelerometer, touchscreen) to administer, measure and collect various tasks and data from a patient, storing the data remotely and present that information to the patient or healthcare professional for review and tracking.
The Subject and Predicate devices are stand-alone software applications that use off-the-shelf general-purpose devices such as mobile phones or tablets to collect data and display information.
The Subject device offers similar measurement and assessment of symptoms as the Predicate device which are then displayed for the patient and sent to a clinician for review. All data is stored in central database and available for access on demand.
The Subject device and the Predicate device both offer similar feature of allowing the patient to frequently perform tasks, report symptoms or respond to questionnaires.
## Software and Cybersecurity
The subject device used the same FDA Guidance and International Standards for software development process (IEC 62304) software documentation (Content of Premarket Submissions for Device Software Functions), Risk Management process (IEC 14971), cybersecurity (Content of Premarket Submissions for Management of Cybersecurity in Medical Devices).
## Summary of Performance Data
The performance data demonstrates that the Neu Health tremor measurements are in agreement with clinically meaningful differences in tremor severity and therefore is substantially equivalent in performance with the predicate device. Both devices display significant correlation with the accepted clinical standard (MDS-UPDRS).
Bench testing validated our devices tremor measurements by comparing the results of our tremor measurements, obtained in a controlled setting, to the same clinical standard as the predicate device (tremor severity as defined by the UPDRS-III assessment). In our bench testing, we observed a correlation of 0.92 (p<0.01) and 0.85 (p=0.002) between the tremor measurement and the clinical standard for the rest and postural tremor measurements respectively. These strong correlations demonstrate that our device is capable of detecting changes in tremor at the equivalent, or greater, level of accuracy as the predicate device (r=0.72).
This supports that the Neu Platform is an effective tool for assessing tremor in patients with mild to moderate Parkinson's Disease. The performance is deemed substantially equivalent to those presented by the predicate device.
## Summary of Animal & Clinical Studies
Substantial equivalence is based on an assessment of non-clinical performance data and no animal or clinical performance data is included.
## Conclusion
Based on the information presented in this Traditional 510(k) submission, the Neu Platform, is substantially equivalent to the predicate device (Parky App) in terms of safety, performance, functionality, and indications for use and is as safe and effective for its intended use.
Page: 5
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
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.