The intended use of the p.d software is to aid radiation therapy professionals in the design, construction, and testing of radiotherapy beam modifying devices. The software is intended to interface with most major treatment planning systems and design devices that are compatible with most major radiotherapy linear accelerators and particle therapy delivery systems. And while the primary intent is for the software to design and measure devices that are manufactured by .decimal, this does not exclude, in some cases, the software being used with devices that are constructed on-site or by other vendors (with explicit permission from .decimal).
Device Story
p.d 5.1 is a software application for radiation therapy professionals to design, manufacture, and perform quality assurance (QA) on beam shaping and compensating filters. Inputs include DICOM files from Treatment Planning Systems (TPS) and user-supplied data. The software converts TPS compensator files into .decimal manufacturing formats; designs beam shaping/compensating filters; and performs QA testing on physical treatment devices using scanned images (e.g., CT). Designed devices are transferred back to the TPS for final dose verification before clinical use. Used in clinical settings by radiation therapy professionals. Benefits include improved accuracy in creating patient-specific beam modifying devices and streamlined QA workflows. Output facilitates the fabrication of custom radiotherapy hardware.
Clinical Evidence
No clinical data. Bench testing only. Software verification and validation conducted per FDA guidance. Validation included comparing results to known predicate devices and performing QA measurements on devices of known quality. Conformance to ISO 14971, IEC 62083, IEC 61217, IEC 62304, and IEC 62366 standards.
Technological Characteristics
Software application for radiotherapy device design and QA. Features include DICOM-based file conversion, beam shaping/compensating filter design, and image-based QA tools. Algorithms are similar to DRR generation and semi-automatic image contouring found in major TPS. Conforms to ISO 14971, IEC 62083, IEC 61217, IEC 62304, and IEC 62366. Software level of concern: Major.
Indications for Use
Indicated for radiation therapy professionals to assist in the design, manufacturing, and quality assurance testing of radiation therapy devices for cancer patients.
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}------------------------------------------------
Image /page/0/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo is a circular seal with the words "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" around the perimeter. Inside the circle is an abstract symbol that resembles a stylized caduceus, which is a traditional symbol of medicine.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
August 7, 2015
.decimal, LLC % Kevin Erhart, Ph.D. Senior Engineer 121 Central Park Place SANFORD FL 32771
Re: K151369 Trade/Device Name: p.d 5.1 Regulation Number: 21 CFR 892.5050 Regulation Name: Medical charged-particle radiation therapy system Regulatory Class: II Product Code: MUJ Dated: May 15, 2015 Received: May 21, 2015
Dear Dr. Erhart:
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. 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 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
{1}------------------------------------------------
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Industry and Consumer Education at its toll-free number (800) 638 2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/Resourcesfor You/Industry/default.htm. 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
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours.
Michael D'Hara
For
Robert Ochs, Ph.D. Acting Director Division of Radiological Health Office of In Vitro Diagnostics and Radiological Health Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
#### Indications for Use
K151369
Device Name p.d 5.1
#### Indications for Use (Describe)
The p.d software is used by radiation therapy professionals to assist in the design, manufacturing, and quality assurance testing of various radiation therapy devices used for cancer patients. The p.d software performs three distinct, primary functions which each are described below.
I) The p.d software takes a design of a compensating filter from a Treatment Planning System and converts the Treatment Planning System compensator filter file format. This file can then be electronically submitted to .decimal through the software, so that we can manufacture the device.
2) The p.d software can design a beam shaping and compensating filters based on Treatment Planning System and other user supplied data. The device designs for compensating filters will be transferred back into the Treatment Planning System for final dose verification before devices are ordered and used for patient treatment.
3) The p.d software can perform quality assurance testing of the physical characteristics of treatment devices using data from various types of scanned images, including computed tomography images.
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)
PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON A SEPARATE PAGE IF NEEDED.
#### FOR FDA USE ONLY
Concurrence of Center for Devices and Radiological Health (CDRH) (Signature)
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 Decimal. The word "decimal" is written in a sans-serif font, with the ".d" in blue and the rest of the word in gray. The tagline "The benchmark for custom radiation therapy" is written in a smaller font below the logo.
Section 5 510(k) Summary
#### Section 807.87 (h) A 510(k) Summary as described in Section 807.92
# Premarket Notification [510(k)] Summary as required by 21 CFR 807.92
#### Date summary was prepared:
May 15, 2015
#### Submitter's Name:
.decimal, LLC 121 Central Park PL Sanford, Florida 32771
#### Contact Person:
Kevin Erhart Senior Engineer Phone: 407-330-3300 407-322-7546 Fax: Email:kerhart@dotdecimal.com
# Device Name:
p.d 5.1
# Classification Name and Code:
Class II, MUJ, 21 CFR 892.5050 Medical charged-particle radiation therapy systems
# Device Description:
The .decimal p.d device is a software application that will enable users of various radiation treatment planning systems (TPS) to design, measure, and order beam shaping and modulating devices used in the delivery of various types of radiotherapy, including photon, electron, and particle therapy. The input from the treatment planning systems to the p.d product is generally received in DICOM file format. but other vendor specific or generic file formats are also utilized. p.d will also provide a simplified radiation dose calculator for the purpose of improving its ability to accurately create/modify patientspecific radiation beam modifying devices without the need for iteration with other treatment planning systems. However, all modulating devices will have final dose verification performed in a commissioned Treatment Planning System before devices are used for patient treatment. Additionally, the p.d software contains tools for analyzing
{4}------------------------------------------------
scanned image data that aids users in performing quality assurance measurement and testing of radiotherapy devices.
# Predicate Device(s):
K083672 - p.d software (version 5.0) - .decimal, LLC (Primary Predicate Device) K141283 - Eclipse Treatment Planning System - Varian Medical Systems, Inc. (Reference Predicate Device)
# Intended Use:
The intended use of the p.d software is to aid radiation therapy professionals in the design, construction, and testing of radiotherapy beam modifying devices. The software is intended to interface with most major treatment planning systems and design devices that are compatible with most major radiotherapy linear accelerators and particle therapy delivery systems. And while the primary intent is for the software to design and measure devices that are manufactured by .decimal, this does not exclude, in some cases, the software being used with devices that are constructed on-site or by other vendors (with explicit permission from .decimal).
# Indications for Use:
The p.d software is used by radiation therapy professionals to assist in the design, manufacturing, and quality assurance testing of various radiation therapy devices used for cancer patients. The p.d software performs three distinct, primary functions which each are described below.
- 1) The p.d software takes a design of a compensating filter from a Treatment Planning System and converts the Treatment Planning System compensator filter files into a .decimal file format. This file can then be electronically submitted to .decimal through the software, so that we can manufacture the device.
- 2) The p.d software can design a beam shaping and compensating filters based on Treatment Planning System and other user supplied data. The device designs for compensating filters will be transferred back into the Treatment Planning System for final dose verification before devices are ordered and used for patient treatment.
- 3) The p.d software can perform quality assurance testing of the physical characteristics of treatment devices using data from various types of scanned images, including computed tomography images.
# Summary of Technological Characteristics:
The device features of p.d are similar to the predicate device p.d (K083672) as both are software applications that design and order the same types of radiotherapy beam modifying devices, using nearly identical algorithms and processes. The new version however incorporates additional quality assurance measurement tools that are
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image shows the logo for ".decimal" in a simple, modern design. The word "decimal" is written in a sans-serif font, with the "." in blue and the rest of the word in gray. Below the logo is the tagline "The benchmark for custom radiation therapy" in a smaller font.
substantially equivalent to functionality found in most all major treatment planning systems (TPS), including the Eclipse TPS from Varian Medical Systems (K141283), which is used here as the predicate device for comparison of this functionality of our p.d software. It should be noted that the p.d device contains are very small subset of the functionality present in the Eclipse TPS, so specifically, the quality assurance measurements performed in p.d use algorithms that are similar to those used to build Digitally Reconstructed Radiographs (DRRs), which is a tool present in the Eclipse TPS. In addition, the semi-automatic image contouring tools of Eclipse utilize similar image processing and recognition techniques as those employed within p.d.
#### Summary of Non-Clinical Testing:
Clinical testing was not performed as part of the development of this product. Clinical testing is not advantageous in demonstrating substantial equivalence or safety and effectiveness of the device since testing can be performed such that no human subjects are exposed to risk.
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 or operator. Clinically oriented validation tests were written and executed by .decimal personnel and hospital-based testing partners. Validation tests included comparing results to those of known predicate devices as well as performing quality assurance measurements on devices of known quality. In addition this device was evaluated and conforms to ISO 14971, IEC 62083, IEC 61217, IEC 62304 and IEC 62366 standards. These tests show that the p.d software performed equivalently to the predicate device when appropriate and that the software is deemed safe and effective for clinical use.
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.