CDMS is a Microsoft Windows based software application designed to record and manage physics data acquired during acceptance testing, commissioning and calibration of radiation therapy treatment devices. In addition, CDMS uses the same physics data to allow users to perform MU calculations based on treatment field parameters that are either imported from the treatment planning system or entered manually. CDMS is also used to manage linac calibration using standard protocols.
Device Story
CDMS is a Windows-based software for radiation therapy quality assurance; manages physics data from commissioning, acceptance testing, and calibration of linear accelerators. Inputs include technical specifications, measured physics data from water phantoms, and treatment field parameters imported via DICOM RT or manual entry. Operates by comparing measured data against peer-reviewed/manufacturer values; performs MU calculations using Khan (classical) algorithm. Used by medical physicists in clinical settings to verify treatment plan quality and manage linac calibration per AAPM TG-51/TG-40 protocols. Outputs include calculated dose/MU values and calibration reports in Word, Excel, or PDF formats. Facilitates regulatory compliance and audit readiness through structured data storage.
Clinical Evidence
No clinical data; bench testing only. Validation included importing measured physics data, performing monitor unit/dose calculations, and executing linear accelerator calibration per TG-51, with side-by-side comparisons to predicate performance.
Technological Characteristics
Windows-based software; minimum Pentium II processor. Uses Khan (classical) dose calculation algorithm. Supports DICOM RT data import. Exports to Word, Excel, or PDF. Three-level password-protected user security. Manages data for linear accelerators with multi-modality energies, photon/electron particles, field blocking, linear wedges, and MLCs (52, 80, 120 leaf).
Indications for Use
Indicated for use by medical physicists to record/manage radiation therapy device physics data, perform monitor unit (MU) calculations for treatment plans, and manage linear accelerator (linac) calibration using standard protocols.
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}------------------------------------------------
X082606
5-2
## 510(k) Summary
This summary is submitted in compliance with 21 CFR 807.92
NOV 1 0 2008
| (a) (1) Submitted by: | D3 Radiation Planning<br>5750 Centre Avenue, Suite 500<br>Pittsburgh, PA 15206 |
|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Trade name of the company: | D3 |
| Contact Persons: | Nabil Adnani, Ph.D, DABR<br>412-365-0743 |
| Date of preparation: | 26 August - 2008 |
| (2) Trade name of device: | CDMS |
| Common name: | Commissioning Data Management System |
| Classification name: | (Accessory to) Radionuclide radiation<br>therapy, §892.5750; X-ray radiation therapy<br>system, §892.5900; and Medical charged-<br>particle radiation therapy system,<br>§892.5050. |
| (3) Identification of predicate<br>Marketed device: | K010464 RadCalc V4.0. |
#### (4) Device Description:
CDMS is a software program designed to record radiation beam data acquired during the commissioning, acceptance testing and calibration of a radiation therapy treatment device.
IMSure.
K031975
A CDMS session would look like this:
- 1. A new treatment machine is installed. The commissioning physicist enters its technical specification in CDMS.
- 2. A third party FDA approved water phantom is used to measure the physics characteristics of each beam generated by the machine.
{1}------------------------------------------------
- 3. Measured physics data is imported to CDMS.
- 4. Measured data in CDMS is compared to peer reviewed/published or manufacturer provided measured values.
- Treatment plans generated by a radiation therapy treatment 5. planning system imported to CDMS via DICOM RT.
- 6. Imported treatment fields parameters are used in conjunction with CDMS stored measured physics data to calculate dose and/or monitor units.
- 7. The difference between planned and CDMS calculations is used as a measure of the quality of the treatment plan (QA).
The above workflow is only given as an example to illustrate how the application is used. Other steps may be added to the workflow or may be left out, for example performing a query of the measured physics data based on beam type, energy and field geometry and saving calibration parameters for use on a monthly QA basis.
#### Intended Use: (5)
CDMS is a Microsoft Windows based software application designed to record and manage physics data acquired during acceptance testing, commissioning and calibration of radiation therapy treatment devices. In addition, CDMS uses the same physics data to allow users to perform MU calculations based on treatment field parameters that are either imported from the treatment planning system or entered manually. CDMS is also used to manage linac calibration using standard protocols.
#### (6) Technological Comparison:
The intended use of CDMS is the same as the predicate devices with a few additions that do not affect the safety and effectiveness of the device.
{2}------------------------------------------------
:
| System Component | LifeLine Sofware, Inc.<br>RadCalc, Model V.4.0 | D3 Advanced Planning Service<br>CDMS |
|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| K number | K010464 | This filing |
| Application (use) | Utilized for the determination of<br>monitor units or dose. Serves to<br>validate those monitor units computed<br>by the primary radiation therapy<br>planning system. Primary means of<br>calculating monitor units in situations<br>where the physician does not order the<br>use of a radiation therapy treatment<br>plan. | Independent dose and monitor unit<br>calculations for imported treatment<br>plans from a radiation therapy<br>treatment planning system. Performs<br>monitor unit calculations for simple<br>plan geometries based on a physician<br>prescribed dose. It also records and<br>manages measured beam data during<br>acceptance testing, commissioning and<br>calibration of radiation therapy devices. |
| Platform | Minimum Pentium II processor, MFS<br>network enabled | Minimum Pentium II processor |
| Operating System | Any MS Windows | Windows 2000, XP, VISTA |
| MU Calculation Dose<br>Algorithm | Khan (Classical) | Khan (Classical) |
| Algorithm - map<br>verification | Single Source model | Not Available |
| Algorithm - IMRT<br>dose Calculation | Single Source model, Clarkson<br>scatter algorithm based on<br>University of Chicago method | Not Available |
| Patient Geometry<br>Specification | Two dimensional, graphical user<br>interface based | Two dimensional, graphical user<br>interface based |
| Machines supported | Commercially available Linear<br>Accelerators with multi-modality<br>energies and both photon and electron<br>particles, including field blocking and<br>linear wedge applicators for photon<br>fluence modulation, and with 52, 80,<br>120 leaf Multi-leaf collimators | Commercially available Linear<br>Accelerators with multi-modality<br>energies and both photon and electron<br>particles, including field blocking and<br>linear wedge applicators for photon<br>fluence modulation, and with 52, 80,<br>120 leaf Multi-leaf collimators |
| Calculation Point for IMRT<br>QA | Fixed, Iso-centric | Not Available |
| Calculation point for MU<br>calculations | Off axis and depth specified calculation<br>points using measured physical data. | Off axis and depth specified calculation<br>points using measured physical data. |
| Physics data | Measured, tabular database stored,<br>multiple linear accelerators allowed. | Measured, tabular database stored,<br>multiple linear accelerators allowed. |
| Import data | RTP link, DICOM RT for IMRT QA<br>and MU Calculations | DICOM RT for independent MU<br>Calculations |
| | | Network location for measured data. |
| Calibration methods | Iso-centric or fixed Calibration<br>Distance | Iso-centric or fixed Calibration<br>Distance. |
| Export Data | RTP link, DICOM RT, paper<br>documentation | Paper or electronic in the form of word,<br>excel or PDF document. |
| User security | Two levels of user, password enabled | Three levels of users, password enabled |
| System Component | Standard Imaging, Inc.<br>IMSure | D3 Advanced Planning Service<br>CDMS |
| K number | K031975 | This filing |
| Application (use) | Independent dose and fiuence map<br>verification software for Intensity<br>Modulated Radiation Therapy based on<br>Linear accelerator plans containing<br>multi-leaf collimator leaf sequence data<br>and fluence maps from primary IMRT<br>treatment planning systems.<br>Independent dose computation software<br>for standard, simple geometry radiation<br>therapy treatment<br>planning and verification of monitor<br>units based on Linear Accelerator<br>parameters and physician prescribed<br>dose information. | Independent dose and monitor unit<br>calculations for imported treatment<br>plans from a radiation therapy<br>treatment planning system. Performs<br>monitor unit calculations for simple<br>plan geometries based on a physician<br>prescribed dose. It also records and<br>manages measured beam data during<br>acceptance testing, commissioning and<br>calibration of radiation therapy devices. |
| Platform | Minimum Pentium III processor, MFS<br>network enabled | Minimum Pentium II processor |
| Operating System | Windows 2000, XP | Windows 2000, XP, VISTA |
| MU Calculation Dose<br>Algorithm | Khan (Classical) | Khan (Classical) |
| Algorithm - map<br>verification | Single Source model | Not Available |
| Algorithm - IMRT<br>dose Calculation | Single Source model, Clarkson scatter<br>algorithm based on University of<br>Chicago method | Not Available |
| Patient Geometry<br>Specification | Two dimensional, graphical user<br>interface based | Two dimensional, graphical user<br>interface based |
| Machines supported | Commercially available Linear<br>Accelerators with multi-modality<br>energies and both photon and electron<br>particles, including field blocking and<br>linear wedge applicators for photon<br>fluence modulation, and with 52, 80,<br>120 leaf Multi-leaf collimcators | Commercially available Linear<br>Accelerators with multi-modality<br>energies and both photon and electron<br>particles, including field blocking and<br>linear wedge applicators for photon<br>fluence modulation, and with 52,80 and<br>120 leaf<br>Multi-leaf collimators |
| Calculation Point for IMRT<br>QA | Off-Axis calculation points<br>incorporating modeled head scatter<br>information and measured fluence<br>perturbations | Not Available |
| Calculation point for MU<br>calculations | Off axis and depth specified calculation<br>points using measured physical data. | Off axis and depth specified calculation<br>points using measured physical data. |
| Physics data | Measured, tabular database stored,<br>multiple linear accelerators allowed. | Measured, tabular database stored,<br>multiple linear accelerators allowed. |
| Import data | RTP link, DICOM RT for IMRT QA<br>and MU Calculations | DICOM RT for independent MU<br>Calculations<br>Network location for measured data. |
| Calibration methods | Iso-centric or fixed Calibration<br>Distance | Iso-centric or fixed Calibration<br>Distance. |
| Export Data | RTP link, DICOM RT, paper<br>documentation | Paper or electronic in the form of word,<br>excel or PDF document. |
| User security | Three levels of user, password enabled | Three levels of user, password enabled |
{3}------------------------------------------------
{4}------------------------------------------------
CDMS differs from the predicate devices by allowing for the management linear accelerators calibration according to American Association of Physicists in Medicine (AAPM) Task Group 51. This feature is equivalent to using an excel sheet to perform the required calibration and save the necessary parameters for future use on monthly basis following AAPM Task Group 40 recommendations. It is therefore not seen to be a threat to patient safety and effectiveness. In fact, it is seen as an enhancement because it will allow for proper storage of calibration parameters as well as better management of calibration reports in format that is easily accessible to external auditors, state and federal regulators.
### (7) Non-Clinical tests:
The non-clinical tests involved using CDMS to import measured physics data, to perform numerous monitor unit/dose calculations and to calibrate a linear accelerator according to TG-51. Side by side comparison tables are shown in the supporting Validation & Verification documentation
#### Clinical tests: (8)
Due to the fact that the system is a software application that is not directly involved with patient treatment delivery, no clinical tests were performed.
#### Conclusion: (9)
According to the intended use, technological characteristics and non-clinical testing, CDMS is substantially equivalent to IMSure and RadCalc, Model V4.0 (the predicate devices). The documentation presented in this submission supports the claim of substantial equivalence.
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a circular seal with the text "DEPARTMENT OF HEALTH & HUMAN SERVICES USA" arranged around the perimeter. Inside the circle is a stylized graphic of three wavy lines, which is the department's symbol.
### DEPARTMENT OF HEALTH & HUMAN SERVICES
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850
### NOV 1 0 2008
Nabil Adnani, Ph.D., DABR Senior Medical Physicist D3 Radiation Planning 5750 Centre Avenue, Suite 500 PITTSBURGH PA 15206
Re: K082606
Trade/Device Name: CDMS Regulation Number: 21 CFR 892.5050 Regulation Name: Medical charged-particle radiation therapy system Regulatory Class: II Product Code: MUJ Dated: August 29, 2008 Received: September 8, 2008
Dear Dr. Adnani:
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.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to such 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.
{6}------------------------------------------------
### Page 2
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); 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.
This letter will allow you to begin marketing your device as described in your Section 510(k) premarket notification. The FDA finding of substantial equivalence of your device to a legally marketed predicate device results in a classification for your device and thus, permits your device to proceed to the market.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Office of Compliance at one of the following numbers, based on the regulation number at the top of this letter:
| 21 CFR 876.xxx | (Gastroenterology/Renal/Urology) | 240-276-0115 |
|----------------|----------------------------------|--------------|
| 21 CFR 884.xxx | (Obstetrics/Gynecology) | 240-276-0115 |
| 21 CFR 894.xxx | (Radiology) | 240-276-0120 |
| Other | | 240-276-0100 |
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807.97). For questions regarding postmarket surveillance, please contact CDRH's Office of Surveillance and Biometrics' (OSB's) Division of Postmarket Surveillance at 240-276-3474. For questions regarding the reporting of device adverse events (Medical Device Reporting (MDR)), please contact the Division of Surveillance Systems at 240-276-3464. You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638-2041 or (240) 276-3150 or at its Internet address http://www.fda.gov/odrh/industry/support/index.html.
Sincerely yours.
hoque Mr. Khang
Joyce M. Whang, Ph.D. Acting Director, Division of Reproductive, Abdominal, and Radiological Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{7}------------------------------------------------
### Indications for Use
510(k) Number (if known):
K082606
Device Name: CDMS
Indications For Use:
CDMS is a Microsoft Windows based software application designed to record and manage physics data acquired during acceptance testing, commissioning and calibration of radiation therapy treatment devices. In addition, CDMS uses the same physics data to allow users to perform MU calculations based on treatment field parameters that are either imported from the treatment planning system or entered manually. CDMS is also used to manage linac calibration using standard protocols.
Prescription Use YES (Part 21 CFR 801 Subpart D)
AND/OR
Over-The-Counter Use (21 CFR 807 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of OPRH, Office of Device Evaluation (ODE)
Hubert Humer
Page 1 of 1
(Division Sign-Off)
Division of Reproductive, Abdominal and
Radiological Devices
510(k) Number K082606
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.