K252109 · RaySearch Laboratories AB (PUBL) · MUJ · Dec 22, 2025 · Radiology
Device Facts
Record ID
K252109
Device Name
RayStation (2024A SP3)
Applicant
RaySearch Laboratories AB (PUBL)
Product Code
MUJ · Radiology
Decision Date
Dec 22, 2025
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.5050
Device Class
Class 2
Attributes
Software as a Medical Device, Therapeutic
Indications for Use
RayStation is a software system for radiation therapy and medical oncology. Based on user input, RayStation proposes treatment plans. After a proposed treatment plan is reviewed and approved by authorized intended users, RayStation may also be used to administer treatments. The system functionality can be configured based on user needs.
Device Story
RayStation is a standalone software medical device for radiation therapy and medical oncology treatment planning and delivery management. It processes patient medical images (CT, PET, MR), disease data, and treatment unit parameters to generate optimized radiation treatment plans, including beam arrangements, energies, and fluence patterns. The system comprises three main applications: RayStation (planning), RayPhysics (commissioning), and RayTreat (delivery management). RayTreat assigns approved plans to fractions, sends them to treatment delivery devices, and records treatment data. Used in clinical settings by authorized personnel (physicians, physicists, therapists). It does not perform real-time delivery monitoring. The device aids clinical decision-making by providing tools for manual or semi-automatic plan generation and evaluation, aiming to deliver safe and effective radiation dose distributions.
Clinical Evidence
No clinical trials were required. Evidence consists of bench testing, including software verification and validation (unit, interoperability, system-level, cybersecurity, and regression testing). Performance was verified using machine simulators (IBA, TomoTherapy TDCS Radixact, CyberKnife).
Technological Characteristics
Standalone software medical device. Operates on standard office PCs running Windows 10 Professional or higher/Windows Server 2012 R2 or higher. Uses three Microsoft SQL databases for data storage. Supports DICOM for network transfer. Complies with IEC 61217, IEC 62083, IEC 62304, IEC 62366-1, ISO 14971, and IEC 81001-5-1. Features include patient/beam modeling, dose calculation algorithms, and plan parameter optimization.
Indications for Use
Indicated for persons prescribed external beam radiation therapy or chemotherapy treatment.
Regulatory Classification
Identification
A medical charged-particle radiation therapy system is a device that produces by acceleration high energy charged particles (e.g., electrons and protons) intended for use in radiation therapy. This generic type of device may include signal analysis and display equipment, patient and equipment supports, treatment planning computer programs, component parts, and accessories.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
December 22, 2025
RaySearch Laboratories AB (publ)
Olympiada Lachana
QA/RA Specialist
Eugeniavägen 18C
Stockholm, 11368
Sweden
Re: K252109
Trade/Device Name: RayStation (2024A SP3)
Regulation Number: 21 CFR 892.5050
Regulation Name: Medical charged-particle radiation therapy system
Regulatory Class: Class II
Product Code: MUJ
Dated: July 4, 2025
Received: July 7, 2025
Dear Olympiada Lachana:
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.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K252109 - Olympiada Lachana
Page 2
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" (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-
{2}
K252109 - Olympiada Lachana
Page 3
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).
Sincerely,

Lora D. Weidner, Ph.D.
Assistant Director
Radiation Therapy Team
DHT8C: Division of Radiological
Imaging and Radiation Therapy Devices
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
RayStation
Page 8 of 37
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K252109 | ? |
| Please provide the device trade name(s). | | ? |
| RayStation (2024A SP3) | | |
| Please provide your Indications for Use below. | | ? |
| RayStation is a software system for radiation therapy and medical oncology. Based on user input, RayStation proposes treatment plans. After a proposed treatment plan is reviewed and approved by authorized intended users, RayStation may also be used to administer treatments.
The system functionality can be configured based on user needs. | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (Part 21 CFR 801 Subpart D)
☐ Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
{4}
RaySearch Laboratories
# K252109 510(K) SUMMARY (21 CFR § 807.92)
## I. Contact Details
Applicant
RaySearch Laboratories AB (publ)
Eugeniavägen 18C Stockholm 113 68 Sweden
+46 8 510 53000
Contact
Ms. Olympiada Lachana
quality@raysearchlabs.com
Preparation Date
7 August, 2025
## II. Device
Device Trade Name
| Device Name | Software Version number |
| --- | --- |
| RayStation | 2024A SP3 |
Common Name
Medical charged-particle radiation therapy system
Classification Name
System, Planning, Radiation Therapy Treatment
Regulation Number
892.5050
Product Code(s)
MUJ
Page 1 of 10
{5}
RaySearch Laboratories
## III. Legally Marketed Predicate Device
Predicate # K240398
Predicate Trade Name RayStation 2024A SP3
Product Code MUJ
Reference Device used: RayStation 11B, K220141.
Use of reference device: The RayTreat application was previously cleared with RayStation 11B, K220141. Since then, some RayTreat functions have been changed compared with RayStation 11B and therefore the use of RayStation 11B as a reference device is essential to compare and describe the changes.
## IV. Device Description Summary
Explanation of how the device functions
RayStation is a software system for radiation therapy and medical oncology. Based on user input, RayStation proposes treatment plans. After a proposed treatment plan is reviewed and approved by authorized intended users, RayStation may also be used to administer treatments.
The system functionality can be configured based on user needs.
RayStation consists of multiple applications:
- The main RayStation application is used for treatment planning.
- The RayPhysics application is used for commissioning of treatment machines to make them available for treatment planning and used for commissioning of imaging systems.
- The RayTreat application is used for sending plans to treatment delivery devices for treatment and receiving records of performed treatments.
The device to be marketed, RayStation 2024A SP3, adds the RayTreat application compared with last cleared version, the predicate RayStation 2024A SP3 (without RayTreat), K240398.
The RayTreat application was previously cleared with RayStation 11B, K220141. Since then some RayTreat functions have been changed:
- RayTreat is now session focused
- Usability improvements
- Bug fixes
Page 2 of 10
{6}
RaySearch Laboratories
# Device design information
The RayStation applications are built on a software platform, containing the radiotherapy domain model and providing GUI, optimization, dose calculation and storage services. The platform uses three Microsoft SQL databases for persistent storage of the patient, machine and clinic settings data.
As a treatment planning system, RayStation aims to be an extensive software toolbox for generating and evaluating various types of radiotherapy treatment plans. RayStation supports a wide variety of radiotherapy treatment techniques and features an extensive range of tools for manual or semi-automatic treatment planning.
The RayStation applications are divided into modules, which are activated through licensing.
# The RayTreat application
RayTreat manages treatment delivery. An approved plan can be assigned to fractions in a treatment course and sent to the treatment delivery device. Treatment records from the treatment delivery device are recorded and sent to RayCarePACS.
Note that all real-time monitoring of actual delivery is handled by treatment delivery device software, not by RayStation.
Scientific concepts that form the basis for the device and significant performance characteristics:
RayStation is a stand-alone software medical device intended for radiation therapy. Input to the device is patient, disease and treatment unit information, output from the device is one or more treatment plans. The treatment plans include treatment unit parameter settings for optimal beam arrangements, energies, field sizes, and ultimately fluence patterns to produce as safe and effective radiation dose distribution as the predicate.
The scientific concepts of a treatment planning system are patient and beam modeling, and algorithms for dose calculation and plan parameter optimization.
The patient model is a computerized representation of the patient tissue and densities, identifying the target regions and particular organs at risk. The model is based on medical images of the patient and must have the desired level of accuracy. Likewise, the beam modeling is a computerized representation of the treatment unit, defined by fluence type, energy distribution, machine specific geometry, and beam modifiers such as MLC, flattening filters, wedges etc. The algorithms for dose calculation and plan parameter optimization must take into account all geometries and materials that affect irradiation transport through the treatment unit and the patient. The optimization algorithm iterates treatment plan parameters until the desired treatment plan and dose distribution have been obtained. Also here, all steps must be done to the desired level of accuracy.
Significant physical characteristics of the device, material used, and physical properties:
The device is a standalone software medical device. It has no physical properties or materials. The device design information can be found in the subsection above "Device design information".
Page 3 of 10
{7}
RaySearch Laboratories
# V. Intended Use/Indications for Use
RayStation is a software system for radiation therapy and medical oncology. Based on user input, RayStation proposes treatment plans. After a proposed treatment plan is reviewed and approved by authorized intended users, RayStation may also be used to administer treatments.
The system functionality can be configured based on user needs.
# Indications for Use Comparison
The indications for use are the same as for the predicate device.
# VI. Technological Comparison
Comparing RayStation 2024A SP3 with RayTreat with the previously cleared RayStation 2024A SP3 without RayTreat, both devices are treatment planning systems. Based on user input, both RayStation versions propose treatment plans. After a proposed treatment plan is reviewed and approved by authorized intended users, both RayStation versions may also be used to administer treatments.
General functions comparison table
| Item | Compared to RayStation 2024A SP3 | Comment |
| --- | --- | --- |
| Hardware platform | Substantially Equivalent | RayStation 2024A SP3 (with RayTreat) and RayStation 2024A SP3 all use standard office PCs as hardware platform. |
| Operating system | Substantially Equivalent | RayStation 2024A SP3 (with RayTreat) and RayStation 2024A SP3 all use Windows 10 Professional (or higher) and Windows Server 2012 R2 (or higher). See RayStation 2024A System Environment Guidelines for details. |
| Target population | Substantially Equivalent | RayStation 2024A SP3 (with RayTreat) and RayStation 2024A SP3 are intended for the same target population and anatomical sites; persons that have been prescribed an external beam radiation therapy or chemotherapy treatment. |
| Anatomical sites | Substantially Equivalent | |
| Human factors | Substantially Equivalent | In terms of human factors, the systems are considered equivalent. There are minor changes only. The user interfaces use the same framework with the same controls and views. |
| Standards met | Substantially Equivalent | RayStation 2024A SP3 (with RayTreat) and RayStation 2024A SP3 all comply with the IEC 61217, IEC 62083, IEC 62304, IEC 62366-1 and ISO 14971. |
| Image types | Substantially Equivalent | RayStation 2024A SP3 (with RayTreat) and RayStation 2024A SP3 all support CT, PET and MR images for identifying patient organs and contouring. |
| Reporting aspects | Substantially Equivalent | When evaluating and approving treatment plans, all necessary data is presented to the user and available in print in all systems. |
Page 4 of 10
{8}
RaySearch Laboratories
| Item | Compared to RayStation 2024A SP3 | Comment |
| --- | --- | --- |
| Image storing | Substantially Equivalent | None of the systems are intended for long term storage of images or other patient data. |
| Network / remote connections and capabilities | Substantially Equivalent | All systems are capable of network transfer of patient data using the DICOM protocol RayStation 2024A SP3 (with RayTreat) and RayStation 2024A SP3 are designed for desktop use and for remote access using standard virtualization techniques. Remote connection to the system is verified in detail and equivalent to local connection. |
| Cybersecurity | Substantially Equivalent | No architectural changes or major new functions that affect cyber security. |
The above listed changes in the general functions do not raise different questions of safety or effectiveness.
The changes in the device to be marketed are the following:
I. The RayTreat application is added in the device to be marketed, compared with the predicate device, RayStation 2024A SP3. However, the RayTreat application was previously cleared with the reference device RayStation version 11B, K220141.
II. The device to be marketed also contains a validation for Hyperscan plans with Boron Carbide energy selector plates. This change is an additional validation and results in no changes in the technological characteristics of the device compared to the predicate device, RayStation 2024A SP3.
The principle of operation of the device to be marketed is the same as that of the existing predicate device. Verification and validation demonstrate that the device to be marketed is as safe and effective as the predicate. RaySearch therefore believes that the device to be marketed is substantially equivalent to the predicate device.
The RayTreat application contains some new and modified functions which are compared to the RayTreat application in the reference device RayStation 11B and presented in the table below.
| Changed RayTreat function in RayStation 2024A SP3 (with RayTreat) compared to reference device, RayStation 11B | Description of the RayTreat function changes | Evaluation of change compared to RayStation 11B, K220141 |
| --- | --- | --- |
| Bug fixes, not recall associated. | Bugs have been resolved related to stuck sessions, evaluation licenses, continuation sessions, nominal progress, import of treatment records, changing patient/room name, updates of beam sets, approval of alternative plans. Also bug fixes related to the communication with Radixact® have been resolved. | Substantially Equivalent. The function change does not raise different questions of safety or effectiveness. |
| Bug fix related to recall RES 90498/FSN 99333. | Recall bug has been resolved related to treatment course information not being synced with RayCare. | Substantially Equivalent. The function change does not raise different questions of safety or effectiveness. |
Page 5 of 10
{9}
RaySearch Laboratories
| Changed RayTreat function in RayStation 2024A SP3 (with RayTreat) compared to reference device, RayStation 11B | Description of the RayTreat function changes | Evaluation of change compared to RayStation 11B, K220141 |
| --- | --- | --- |
| RayTreat is now session focused. | Treatment course information is no longer displayed in RayTreat results workspace, it is displayed in RayCare. | Substantially Equivalent. The function change does not raise different questions of safety or effectiveness. |
| Usability improvements. | Usability improvements in: • Room and activity status • Scheduling workspace • Preparation workspace • Results workspace | Substantially Equivalent. The function change does not raise different questions of safety or effectiveness. |
# VII. Non-Clinical and/or Clinical Tests Summary
Software verification and validation testing were conducted, and documentation was provided as recommended by FDA's Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices". The software for this device was considered as a "Major" level of concern, since a failure or latent flaw in the software could directly result in serious injury or death to the patient.
Cybersecurity and Interoperability requirements were assessed per FDA guidance's "Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions (Sept 2023)" as for the predicate. The cybersecurity analysis showed that the cybersecurity risks are mitigated, and the residual risk is acceptable. The devices are secure for use in their intended environment and methods are in place for ensuring security throughout the total product lifecycle.
Compliance with device-specific recognized consensus standards, along with general and collateral safety and performance standards for medical devices listed below, ensures that basic safety and essential performance requirements are met.
Standards applied:
| Standard No. | Standard Title | Recognition no. |
| --- | --- | --- |
| IEC 61217 | Radiotherapy equipment - Coordinates movements and scales | 12-267 |
| IEC 62304 | Medical device software - Software life cycle processes | 13-79 |
| IEC 62366-1 | Medical devices - Part 1: Application of usability engineering to medical devices | 5-129 |
| ISO 14971 | Medical devices - Application of risk management to medical devices | 5-125 |
| IEC 62083 | Medical electrical equipment - Requirements for the safety of radiotherapy treatment planning systems | 12-217 |
| IEC 81001-5-1 | Health software and health IT systems safety effectiveness and security - Part 5-1: Security - Activities in the product life cycle | 13-122 |
Page 6 of 10
{10}
RaySearch Laboratories
According to the FDA's "General Principles of Software Validation", software verification provides evidence that design outputs meet specified requirements for each development phase. Software validation confirms that software specifications meet user needs and intended uses, ensuring consistent fulfillment of requirements.
Below is an overview of the verification and validation activities used to demonstrate substantial equivalence. The specific validation activities for selected significant functions are presented in the table below.
- Unit Testing: This involves testing individual software requirements to ensure that small sections of the code function as intended in isolation. It helps identify and fix bugs at an early stage.
- Interoperability Testing: This type of testing ensures that software and hardware components can exchange information and use the information that has been exchanged effectively. It verifies that the software and the treatment machine can work together seamlessly.
- System Level Testing: This testing evaluates the entire software system to ensure it meets the specified requirements to validate the overall behaviour of the system.
- Cybersecurity Testing: This testing assesses the software's ability to protect against cyber threats and vulnerabilities. It includes penetration testing to ensure the software is secure and resilient against attacks.
- Regression Testing: This testing ensures that changes to the software do not introduce new bugs or negatively impact existing functionality. It involves re-running previously conducted tests to verify that the software still performs as expected after changes.
In the below table, an overview of the verification and validation activities is presented for the changes in the device to be marketed, RayStation 2024A SP3 (with RayTreat).
| Changed RayStation function in RayStation 2024A SP3 (with RayTreat) compared to predicate device, RayStation 2024A SP3. | Verification and validation data used to demonstrate substantial equivalence | Substantially equivalent? |
| --- | --- | --- |
| Addition of RayTreat application | System level verification and validation and unit tests. Purpose of testing: To verify that RayTreat performs as intended and as in reference device RayStation 11B. No new, unmitigated hazards have been added compared to predicate device RayStation 2024A SP3. For the verification of changes to RayTreat since the last cleared device with RayTreat, RayStation 11B, refer to the following table. | Yes. The successful validation of this function change demonstrates that the device is as safe and effective as the predicate device. |
Page 7 of 10
{11}
RaySearch Laboratories
In the below table, an overview of the verification and validation activities is presented for changed RayTreat functions compared to the reference device RayStation 11B.
| Changed RayTreat function in RayStation 2024A SP3 (with RayTreat) compared to reference device, RayStation 11B. | Verification and validation data used to demonstrate substantial equivalence | Substantially equivalent? |
| --- | --- | --- |
| RayTreat is now session focused | System level verification and validation. Purpose of testing: Perform a main flow and verify that the treatment delivery is successful using: • IBA machine simulator • TomoTherapy TDCS Radixact simulator • CyberKnife simulator Pass criteria: The session (treatment or QA plan) has been completed, and the treatment record has been received in RayCare. | Yes. The successful validation of this function change demonstrates that the device is as safe and effective as the predicate device. |
| Usability improvements | System level verification and validation. Purpose of testing: • Verify that the Patient card, task list, beam set note and appointment comments details. Pass criterion: The new comment is visible in RayTreat, and the status of the changed appointment is updated. • Verify that Send session to driver although QA has not been performed. | Yes. The successful validation of this function change demonstrates that the device is as safe and effective as the predicate device. |
{12}
RaySearch Laboratories
| Changed RayTreat function in RayStation 2024A SP3 (with RayTreat) compared to reference device, RayStation 11B. | Verification and validation data used to demonstrate substantial equivalence | Substantially equivalent? |
| --- | --- | --- |
| | Pass criteria: In RayTreat, the icon indicating that the session has warnings that need to be overridden shall appear again. It shall not be possible to open the session.
• Verify the setting and changing of setup instructions and machine model from RayCare.
Pass criterion: The setup instructions used during delivery match what is seen viewing the delivered sessions.
• Verify that the treatment delivery is successful using:
• IBA machine simulator
• TomoTherapy TDCS Radixact simulator
• CyberKnife simulator
Pass criteria: The session (treatment or QA plan) has been completed and the treatment record has been received in RayCare. | |
The data obtained from the verification show that system tests, use error tests, unit and subsystem tests are acceptable, and the validations have been completed successfully. The reviews of design, code and labeling met the acceptance criteria.
From the successful verification and validation activities, the conclusion can be drawn that RayStation 2024A SP3 with RayTreat has met specifications and is as safe, as effective and perform as well as the legally marketed predicate devices.
## VIII. Animal Testing
No animal testing was required to demonstrate substantial equivalence.
## IX. Clinical Testing
No Clinical trials were required to demonstrate substantial equivalence.
Page 9 of 10
{13}
RaySearch Laboratories
# X. Conclusion
The changes between the predicate and device to be marketed do not raise any new or different questions of safety or effectiveness.
In the Technological Comparison section above, the added RayTreat application in RayStation 2024A SP3 is compared to the predicate device, RayStation 2024A SP3 in a General functions comparison table. The changes to RayTreat since the last cleared RayStation version with RayTreat, 11B have been compared in a Changed RayTreat function Table of section VI. All compared items are evaluated as substantially equivalent and do not raise different questions of safety of effectiveness.
The non-clinical data support the safety of the device as compared to the predicate and the software verification and validation demonstrate that the RayStation 2024A SP3 device with RayTreat should perform as intended in the specified use conditions, and the performance testing demonstrates that the RayStation 2024A SP3 device with RayTreat performs as well as the predicate device, RayStation 2024A SP3 that is currently marketed for the same intended use.
Therefore, all the changes are substantially equivalent to the predicate device RayStation 2024A SP3 cleared under K240398.
Page 10 of 10
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.