K261641 · AI Planning Logic, Inc. · QIH · Aug 18, 2026 · Radiology
Device Facts
Record ID
K261641
Device Name
Lower Limb AI (LLAI)
Applicant
AI Planning Logic, Inc.
Product Code
QIH · Radiology
Decision Date
Aug 18, 2026
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K261641 · Aug 18, 2026
Lower Limb AI (LLAI)
AI Planning Logic, Inc.
Retrospective de-identified clinical CT image sets from multiple acquisition sites
Retrospective clinical CT image datasets were used to validate the performance of the AI segmentation, landmark localization, and angle measurement algorithms.
Retrospective clinical data; CT imaging; Performance validation; Real-world clinical records
The AI Planning Logic (AIPL) Lower Limb AI (LLAI) is software intended for use by orthopedic healthcare professionals in the preoperative planning of knee osteotomy procedures. The device processes CT images of the lower limb to provide: • Automated segmentation and 3D reconstruction of bony anatomy • Quantitative measurement of lower limb alignment, including mechanical and anatomical axis angles • Visualization of anatomical structures and surgical planning outcomes in a virtual 3D environment The software is intended to be used as an adjunctive tool to support clinical judgment and is not intended to provide diagnostic information or to replace the surgeon's decision-making process.
Device Story
LLAI is a cloud-based SaMD for orthopedic preoperative planning. It ingests DICOM CT images of the lower limb; performs automated bone segmentation (pelvis, femur, tibia, ankle) using locked deep-learning models; identifies anatomical landmarks; generates 3D anatomical reconstructions; and computes quantitative alignment measurements via deterministic mathematical algorithms. The device is accessed by orthopedic surgeons via a secure web interface. Outputs include segmented bone models, anatomical landmarks, and alignment measurements, which are presented for clinician review and confirmation. The device serves as an adjunctive tool to support clinical judgment; it does not provide diagnostic information or replace surgeon decision-making. By providing repeatable, automated 3D visualization and alignment data, the device assists in surgical planning for knee osteotomies.
Clinical Evidence
Bench testing only. Retrospective, non-interventional validation using 170 internal (327 image sets) and 63 independent external (116 image sets) patients. Segmentation performance: Dice 0.9916–0.9965, HD95 < 1 mm. Landmark localization: mean radial error 3.611–4.213 mm. Angle measurement and STL representation met prespecified acceptance criteria. No clinical outcome data provided.
Technological Characteristics
Cloud-hosted software; GPU-accelerated inference. Uses convolutional neural network (CNN) for segmentation and deterministic geometric algorithms for alignment measurements. Inputs: DICOM CT data. Outputs: 3D STL models and quantitative measurements. Secure web interface access. No patient-contacting components.
Indications for Use
Indicated for orthopedic healthcare professionals performing preoperative planning for knee osteotomy procedures using lower limb CT images.
Regulatory Classification
Identification
A medical image management and processing system is a device that provides one or more capabilities relating to the review and digital processing of medical images for the purposes of interpretation by a trained practitioner of disease detection, diagnosis, or patient management. The software components may provide advanced or complex image processing functions for image manipulation, enhancement, or quantification that are intended for use in the interpretation and analysis of medical images. Advanced image manipulation functions may include image segmentation, multimodality image registration, or 3D visualization. Complex quantitative functions may include semi-automated measurements or time-series measurements.
Special Controls
*Classification.* Class II (special controls; voluntary standards—Digital Imaging and Communications in Medicine (DICOM) Std., Joint Photographic Experts Group (JPEG) Std., Society of Motion Picture and Television Engineers (SMPTE) Test Pattern).
{0}
**FDA** U.S. FOOD & DRUG
ADMINISTRATION
August 18, 2026
AI Planning Logic, Inc.
% Jennifer Palinchik
Owner & CEO
Sagemar Medical, LLC
30628 Detroit Rd.
#254
Westlake, Ohio 44145
Re: K261641
Trade/Device Name: Lower Limb AI (LLAI)
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: QIH
Dated: August 10, 2026
Received: August 10, 2026
Dear Jennifer Palinchik:
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}
K261641 - Jennifer Palinchik
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 Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
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 Management System Regulation (QMSR) (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
{2}
K261641 - Jennifer Palinchik
Page 3
the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Jessica Lamb, PhD
Assistant Director
Imaging Software Team
DHT8B: Division of Radiological Imaging
Devices and Electronic Products
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
| 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. | K261641 | ? |
| Please provide the device trade name(s). | | ? |
| Lower Limb AI (LLAI) | | |
| Please provide your Indications for Use below. | | ? |
| The AI Planning Logic (AIPL) Lower Limb AI (LLAI) is software intended for use by orthopedic healthcare professionals in the preoperative planning of knee osteotomy procedures. The device processes CT images of the lower limb to provide: • Automated segmentation and 3D reconstruction of bony anatomy • Quantitative measurement of lower limb alignment, including mechanical and anatomical axis angles • Visualization of anatomical structures and surgical planning outcomes in a virtual 3D environment The software is intended to be used as an adjunctive tool to support clinical judgment and is not intended to provide diagnostic information or to replace the surgeon's decision-making process. | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (21 CFR 801 Subpart D) ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
{4}
[LOGO]
K261641
## 510(k) Summary - Lower Limb AI (LLAI)
This 510(k) Summary is being submitted in accordance with the requirements of 21 CFR 807.92
**510(k) SUBMITTER:**
AI Planning Logic, Inc.
1617 Ronne Drive
Santa Rosa, CA 95404
Primary Contact:
Philippe Ballaire, CEO
**Alternate Contact:**
Taman Upadhaya, PhD, CTO
**Official Correspondent:**
Jennifer Palinchik, Regulatory Consultant
(440) 935-3282
| **Device Trade Name:** | Lower Limb AI (LLAI) |
| --- | --- |
| **Common Name:** | Automated Radiological Image Processing Software |
| **Device Classification Name:** | Medical Image Management and Processing System |
| **Regulation Number:** | 21 CFR 892.2050 |
| **Regulatory Class:** | Class II |
| **Product Code:** | QIH |
| **Review Panel:** | Radiology |
| **Primary Predicate:** | SMART Bun-Yo-Matic CT (K240642) |
| **Reference Predicate:** | PeekMed Web (K252856) |
**Device Description:**
Lower Limb AI (LLAI) is a cloud-based Software as a Medical Device that processes lower-limb CT imaging to support orthopedic preoperative planning. The device receives DICOM CT data, performs automated bone segmentation using locked deep-learning models, identifies anatomical landmarks, generates three-dimensional anatomical reconstructions, and computes quantitative alignment measurements using deterministic mathematical algorithms. Outputs are presented to the clinician for review, confirmation, and use in surgical planning.
The scientific basis for the device includes convolutional neural network image segmentation using deep learning-based segmentation algorithm, geometric modeling of bone surfaces, and established orthopedic alignment principles. Mechanical and anatomical measurements are derived from three-dimensional landmarks, vectors, planes, and joint-center calculations. The software provides automated pelvis, femur, tibia, and ankle-region segmentation; hip, knee, and ankle landmark localization; deterministic angle calculation; STL-based visualization; and repeatable outputs.
LLAI is a software-only device with no patient-contacting components and is accessed through a secure web interface. Significant performance characteristics include:
- Automated segmentation of pelvis, femur, tibia, and ankle regions
- Anatomical landmark localization for hip, knee, and ankle regions
- Deterministic angle computation using landmarks, vectors, planes, and joint-center calculations for mechanical axis and related alignment parameters
Page 1 of 8
{5}
Planning Logic
### 510(k) Summary - Lower Limb AI (LLAI)
- STL-based anatomical visualization for preoperative assessment
- Repeatable algorithmic outputs generated by locked software models and deterministic measurement calculations
- Cloud-hosted processing with GPU-accelerated inference
- Integrated cybersecurity controls for secure system access and data handling
LLAI is designed to segment native lower-limb bony anatomy from CT image data and to identify anatomical landmarks on the resulting bony structures. The device does not segment orthopedic implants as device outputs. Implant-specific subgroup performance was not established as a separate validation endpoint, and performance claims are limited to the evaluated input conditions.
For purposes of the device description and performance characterization, reconstruction parameters refer to CT acquisition and reconstruction characteristics that may influence image appearance and spatial sampling, including slice thickness, through-plane spacing, pixel spacing, reconstruction diameter or field of view, tube voltage, scanner manufacturer/model, and reconstruction kernel where available.
The system is accessed through a secure web interface and does not modify, store, or transmit data beyond the functions required for image processing and clinician review. All measurements and visualizations generated by the device are advisory and are intended to assist, not replace, clinical judgment.
#### **Indications for Use:**
The AI Planning Logic (AIPL) Lower Limb AI (LLAI) is software intended for use by orthopedic healthcare professionals in the preoperative planning of knee osteotomy procedures. The device processes CT images of the lower limb to provide:
- Automated segmentation and 3D reconstruction of bony anatomy
- Quantitative measurement of lower limb alignment, including mechanical and anatomical axis angles
- Visualization of anatomical structures and surgical planning outcomes in a virtual 3D environment
The software is intended to be used as an adjunctive tool to support clinical judgment and is not intended to provide diagnostic information or to replace the surgeon's decision-making process.
#### **Technological Characteristics:**
LLAI uses deep-learning segmentation, deterministic geometric algorithms for angle measurement, and a cloud-hosted inference pipeline. The technological characteristics are similar to the predicate devices, which also use automated segmentation, 3D reconstruction, and measurement tools. Differences do not raise new questions of safety or effectiveness.
#### **Performance Testing – Machine Learning Validation Summary**
Performance testing was conducted to support the substantial equivalence determination for Lower Limb AI (LLAI) and to characterize the performance of the device's machine learning-derived outputs. Testing evaluated segmentation performance, landmark localization, angle measurement, STL representation fidelity, workflow operation, and performance across available imaging conditions and evaluated subgroups. The clinical performance evaluation was retrospective and non-interventional and used de-
Page 2 of 8
{6}
Planimologic
## 510(k) Summary - Lower Limb AI (LLAI)
identified lower-limb CT image sets. The evaluation assessed device performance and workflow function; patient outcomes, complication rates, and therapeutic benefit were outside the scope of the evaluation. Training Dataset
Separate segmentation-model training datasets were maintained for the pelvis, knee, and ankle anatomical regions. The pelvis model training dataset included 593 unique patients and 1,280 CT image volumes. The knee model training dataset included 625 unique patients and 1,280 CT image volumes. The ankle model training dataset included 667 unique patients and 1,280 CT image volumes.
A patient could contribute more than one CT volume; therefore, unique-patient counts and CT image-volume counts are reported separately and should not be aggregated across anatomical datasets.
Training images were acquired using CT scanners from multiple manufacturers, including GE, Siemens, Toshiba, and Philips, with smaller contributions from other manufacturers were recorded. The predominant tube voltage was 120 kVp, accounting for approximately 90.70% of the combined training image volumes.
Training-data through-plane spacing and slice-thickness characteristics varied by anatomical model. For the pelvis dataset, through-plane spacing ranged from 0.1 to 10.0 mm and slice thickness ranged from 0.5 to 10.0 mm. For the knee dataset, through-plane spacing ranged from 0.1 to 5.0 mm and slice thickness ranged from 0.5 to 5.0 mm. For the ankle dataset, through-plane spacing ranged from 0.1 to 5.0 mm and slice thickness ranged from 0.3 to 5.0 mm.
Although maximum spacing and slice-thickness values varied by dataset, most training volumes used thinner image spacing. At least 98.2% of training volumes had through-plane spacing of 2.5 mm or less, and at least 99.2% had through-plane spacing of 3.0 mm or less. At least 98.4% of training volumes had slice thickness of 2.5 mm or less, and at least 99.4% had slice thickness of 3.0 mm or less.
Available training metadata indicated approximate age ranges of 11–71 years for the pelvis and knee datasets and 11–75 years for the ankle dataset. Recorded sex/gender information was available at the image-volume-record level. Male-associated image-volume records represented approximately 65% of the pelvis dataset, 65% of the knee dataset, and 68% of the ankle dataset. Female-associated image-volume records represented approximately 33%, 33%, and 30%, respectively. Small proportions were recorded as other, unknown, or anonymized. These distributions do not represent deduplicated unique-patient demographic distributions.
Race and ethnicity were not included in the supplied de-identified training metadata. The Dataset Characterization Report provides the available training-data distributions for tube voltage, pixel spacing, through-plane spacing, reconstruction diameter, scanner manufacturer and model, contributing institutions, collection period, and other available imaging characteristics. Missing or unknown metadata are identified within the applicable tables. The Supplementary Material Supporting Validation Report is identified as the authoritative source for the training dataset patient and CT image-volume counts.
### Validation Dataset
The clinical performance validation dataset included both internal validation and independent external validation cohorts.
| Validation cohort | Unique patients | Complete image sets |
| --- | --- | --- |
| Internal validation | 170 | 327 |
| Independent external validation | 63 | 116 |
Page 3 of 8
{7}
Planimologic
# 510(k) Summary - Lower Limb AI (LLAI)
## Demographic Characteristics
Available demographic information included age and recorded sex/gender at the image-set-record level. Because deduplicated patient-level demographic data were not available for all records, patients contributing multiple image sets may be represented more than once in demographic summaries.
| Cohort | Age information | Recorded sex/gender | Race and ethnicity |
| --- | --- | --- | --- |
| Internal validation | Available for 320 of 327 image sets; approximately 17–69 years | Male 230; female 91; other 3; unknown 3 | Not included in supplied de-identified metadata |
| Independent external validation | Available for 101 of 116 image sets; approximately 9–71 years | Male 64; female 45; other 3; unknown 4 | Not included in supplied de-identified metadata |
Race and ethnicity were not included in the supplied de-identified training or validation metadata. The datasets were assembled from retrospective imaging records across multiple acquisition sites, and available metadata were limited to the fields provided by the source datasets, including age, recorded sex/gender, acquisition characteristics, scanner information, and selected imaging parameters. Because race and ethnicity were unavailable, they were not used for subgroup analysis, and no conclusions are made regarding performance across racial or ethnic groups.
## Clinical Subgroups, Confounders, and Edge Cases
Subgroup analyses were performed according to output type. Segmentation performance was evaluated across tube-voltage and BMI categories. Landmark-localization and angle-measurement performance were evaluated across age, recorded sex/gender, and scanner-manufacturer categories. STL representation performance was evaluated in aggregate because overall accuracy was consistently high and no subgroup-specific performance signal was identified.
No clinically significant subgroup-specific performance patterns were identified among the evaluated subgroups. Several subgroup categories included limited case numbers, and BMI information was unavailable for a substantial proportion of datasets. Accordingly, the subgroup analyses support performance characterization for the evaluated data but do not establish equivalent performance across all patient populations or acquisition conditions.
Reviewed edge cases included incomplete or zoomed anatomy, ankle-tip holes, unusual or distorted anatomy, and connected femur or tibia. Cases outside intended input conditions were excluded from applicable quantitative landmark and angle analyses and were separately reviewed for potential safety impact.
## Implants and Reconstruction Parameters
LLAI does not segment orthopedic implants as device outputs. The segmentation and landmark-localization algorithms are intended to identify native bony anatomy for lower-limb preoperative planning. Implant-specific subgroup performance was not established as a separate validation endpoint. As a result, performance claims are limited to the evaluated input conditions, and the 510(k) Summary and labeling do not claim validated robustness across implants.
Page 4 of 8
{8}
Planimologic
# 510(k) Summary - Lower Limb AI (LLAI)
For the device description and performance discussion, “reconstruction parameters” refer to CT acquisition and reconstruction characteristics that may influence image appearance and spatial sampling, including slice thickness, through-plane spacing, pixel spacing, reconstruction diameter or field of view, tube voltage, scanner manufacturer/model, and reconstruction kernel where available. Performance claims are limited to the patient populations, acquisition conditions, reconstruction characteristics, and input-quality characteristics represented in the training and validation datasets.
# Imaging Equipment and Acquisition Characteristics
Validation datasets were collected from multiple clinical acquisition sites and included CT scanners from multiple manufacturers. Internal-validation image sets were acquired using scanners from GE Medical Systems, Siemens, Toshiba, Philips, and Canon Medical Systems. Independent external-validation image sets were acquired using recorded scanner models from GE Medical Systems, Philips, Siemens Healthineers, Siemens, and Toshiba.
Most validation image sets were acquired at 120 kVp. Across the internal and independent external cohorts, excluding two internal image sets with missing or invalid tube-voltage metadata, 400 of 441 image sets, or 90.70%, were acquired at 120 kVp.
For internal validation, both through-plane spacing and slice thickness ranged from 0.3 to 2.5 mm. For independent external validation, both ranged from 0.4 to 2.5 mm. Available metadata also characterized pixel spacing, reconstruction diameter, scanner manufacturers and models, acquisition sites, and other imaging characteristics.
# Reference Standard and Truthing Process
Segmentation reference masks were generated through manual annotation in ITK-SNAP. Trained annotators edited and refined the masks to remove irrelevant anatomical structures and establish anatomically appropriate segmentation boundaries. Expert clinicians reviewed the resulting masks for anatomical correctness and clinical validity but did not directly edit them. Any discrepancies identified during clinical review were returned to the trained annotators for correction and subsequent re-review before acceptance.
Qualified clinical experts established fixed reference-standard landmark coordinates using 3D CAD software tools. Joint angles were calculated from those landmarks using independently verified angle-computation software. Reference-standard data were locked before comparison with AI outputs.
Independent external validation used triangulated comparison among AI Core outputs, a separate expert orthopedic surgeon assessment, and the 3D CAD software tools derived reference standard. When disagreement exceeded protocol-defined tolerance, additional expert review, consensus, or adjudication was required before final disposition.
# Independence of Test Data from Training Data
The production software and model versions were frozen, and validation datasets were locked before validation testing. No patient, CT image volume, CT series, reconstructed volume, derived image, segmentation mask, landmark annotation, or other data from the 116-case independent external validation dataset were used for model training, model selection, checkpoint selection, hyperparameter tuning, operating-threshold selection, acceptance-criterion development, or adaptation of the released models.
Page 5 of 8
{9}
Planimologic
## 510(k) Summary - Lower Limb AI (LLAI)
De-identified patient identifiers, image-set identifiers, site records, and controlled dataset inventories were reviewed to maintain separation between development data and independent external test data. No retraining or model modification was performed in response to validation results.
### Performance Testing Results
LLAI met the prespecified acceptance criteria for the evaluated outputs.
| Output | Test method | Acceptance criteria / evaluation framework | Results |
| --- | --- | --- | --- |
| Segmentation | Comparison with expert-verified reference masks using Dice, Intersection over Union, HD95, precision, and recall | Dice ≥ 0.95; IoU ≥ 0.90; HD95 ≤ 3.5 mm; precision ≥ 0.90; recall ≥ 0.90 | All endpoints passed. Mean Dice values ranged from approximately 0.9916 to 0.9965 across anatomical regions and validation cohorts. Mean HD95 values were below 1 mm. |
| Landmark localization | Three-dimensional radial distance between AI-generated, reference-standard, and expert landmarks | Overall mean radial error ≤ 7 mm; standard deviation ≤ 5 mm; deviations clinically reviewed; no unresolved safety concern | All landmark-localization comparisons passed. Mean radial error values ranged from approximately 3.611 mm to 4.213 mm across reported comparison groups. |
| Angle measurement | Mean absolute error, signed bias, standard deviation, interquartile range, confidence intervals, Bland–Altman analysis, expert-comparator agreement, outlier review, and residual-risk assessment | Protocol-defined agreement framework; deterministic computation verified; deviations clinically reviewed; no unresolved safety concern | Angle validation passed. Greater variability was observed for geometrically sensitive measurements, and users are instructed to review and, where necessary, correct underlying landmarks before relying on derived measurements. |
| STL representation | Hausdorff distance, average surface distance, volume ratio, mesh-integrity review, and clinical-acceptability review | HD ≤ 2.5 mm; ASD ≤ 0.5 mm; volume ratio ≥ 0.95; valid mesh; clinically acceptable | STL representation met prespecified acceptance criteria, supporting high-fidelity surface reconstruction relative to reference representations. |
The validation evidence demonstrates that LLAI performs as intended for the evaluated lower-limb CT imaging conditions and met the prespecified acceptance criteria for segmentation, landmark localization, angle-measurement evaluation, and STL representation. The results support the device's performance for its intended use while recognizing limitations in available validation metadata and evaluated subgroups, including unavailable race/ethnicity data, incomplete BMI data, and lack of implant-specific subgroup validation.
### Substantial Equivalence:
Page 6 of 8
{10}
Planning Logic
## 510(k) Summary - Lower Limb AI (LLAI)
The Indications for Use of the subject device and the predicate devices are similar. Differences do not constitute a different intended use because all devices are intended to provide 3D models, measurements, and pre-surgical planning information generated from CT input for orthopedic healthcare professionals.
The subject and predicate devices have similar technological characteristics. Differences in output format and user interface do not introduce new questions of safety or effectiveness.
Performance testing demonstrates that the subject device performs as intended and meets its predefined acceptance criteria. Prospective clinical outcome data were not required to support the substantial equivalence determination.
| Category | Subject Device (LLAI) | Primary Predicate (K240642 – SMART Bun-Yo-Matic CT) | Reference Predicate (K252856 – PeekMed Web) |
| --- | --- | --- | --- |
| Manufacturer | AI Planning Logic, Inc. | Disior Ltd | PeekMed |
| Trade Name | Lower Limb AI (LLAI) | SMART Bun-Yo-Matic CT | PeekMed Web |
| Input | CT imaging (DICOM) of the lower limb | CT imaging (DICOM) | CT imaging (DICOM) |
| Image Processing | Automated segmentation of bone structures; anatomical landmark detection; 3D reconstruction; quantitative alignment measurements | Automated segmentation of bone structures; 3D reconstruction; case report generation | Automated segmentation, 3D reconstruction, and orthopedic planning tools |
| Output | Segmented bone models, anatomical landmarks, 3D reconstructions, quantitative alignment measurements for pre-operative planning | 3D model of patient anatomy; surgical instrument parameters; case report | 3D models, measurements, and planning tools for orthopedic assessment |
| Measuring & Planning | Deterministic geometric algorithms for angle and alignment measurement; supports orthopedic pre-operative planning | Performs measurements for presurgical planning | Performs measurements and planning for orthopedic procedures |
| User Interface | Web-based graphical user interface accessed through a standard browser | Standalone application-based GUI | Web-based GUI |
| Technological Characteristics | Deep-learning segmentation ; cloud-hosted inference pipeline; deterministic measurement algorithms | Automated segmentation and measurement algorithms; workstation-based processing | Automated segmentation and measurement algorithms; cloud-enabled workflow |
| Performance Testing | Validation testing evaluated internal and independent external CT image sets. LLAI met prespecified acceptance criteria for segmentation, landmark localization, angle- | Predicate meets acceptance criteria of 95% model conformance within 1.0 mm and 2° SD | Predicate demonstrates acceptable segmentation and |
Page 7 of 8
{11}
Planning Logic
# **510(k) Summary - Lower Limb AI (LLAI)**
| | measurement evaluation, STL representation, and workflow performance under the evaluated imaging conditions. Mean Dice values ranged from approximately 0.9916 to 0.9965, and mean HD95 values were below 1 mm. Performance claims are limited to conditions represented in the validation datasets, and implant-specific subgroup performance was not established. | for angular measurements | measurement accuracy |
| --- | --- | --- | --- |
# **Safety and Clinical Interpretation:**
No clinically unsafe systematic output or unresolved device-related safety concern was identified during validation. The evaluations were retrospective and non-interventional and were not designed to demonstrate improved patient outcomes or reduced complication rates. Device outputs remain advisory and must be reviewed by qualified users before use in planning.
# **Conclusion:**
LLAI has the same intended use and similar technological characteristics as the predicate devices. Differences in technological characteristics do not raise new questions of safety or effectiveness. Under the evaluated conditions, performance testing demonstrated that LLAI performs as intended and meets its predefined acceptance criteria. Based on the intended use, technological characteristics, and performance testing, LLAI is substantially equivalent to the predicate and reference devices.
Page 8 of 8
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.