Authorized purpose: SMART PCFD uses algorithms to support orthopedic diagnosis and surgical planning for progressive collapsing foot deformity from weight-bearing CT, including three-dimensional models, measurements, fixation devices, and osteotomy planning.
Clinical role
Medical-image processing, measurement, quantification, visualization, and reporting support.
Images and patients
CT/CTA · Foot and ankle
Key limitation
Keep in mind: Outputs supplement accepted interpretation or planning methods and require review against source images; supported modality, anatomy, protocol, patient population, and version limits apply.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: SMART PCFD uses algorithms to support orthopedic diagnosis and surgical planning for progressive collapsing foot deformity from weight-bearing CT, including three-dimensional models, measurements, fixation devices, and osteotomy planning.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Foot and ankle Input: Supported DICOM images, study metadata, and release-specific user inputs.
Who uses it?Intended users: Qualified imaging professionals and physicians trained for the represented anatomy and workflow.
What does the software produce?Output: Measurements, segmentations, visualizations, calculations, models, and reports for professional review.
What is its most important limitation?Key limitation: Outputs supplement accepted interpretation or planning methods and require review against source images; supported modality, anatomy, protocol, patient population, and version limits apply.
Clinical takeaway. Clinical role: SMART PCFD uses algorithms to support orthopedic diagnosis and surgical planning for progressive collapsing foot deformity from weight-bearing CT, including three-dimensional models, measurements, fixation devices, and osteotomy planning.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification and validation at the unit, integration, and system levels and non-clinical bench testing of the Surgical Planning Component, with outputs evaluated by qualified truthers and estimated correction ±1 degree for angular and ±1.0 mm for distance measurements. Its machine learning outputs are the same as the predicate SMART Bun-Yo-Matic CT (K240642) and no new validations were conducted; clinical data are stated as not needed. Results are as reported in the FDA submission, not independent validation.
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
SMART PCFD uses algorithms to support orthopedic diagnosis and surgical planning for progressive collapsing foot deformity from weight-bearing CT, including three-dimensional models, measurements, fixation devices, and osteotomy planning.
Outputs supplement accepted interpretation or planning methods and require review against source images; supported modality, anatomy, protocol, patient population, and version limits apply.
The exact FDA document reports software verification and validation at the unit, integration, and system levels and non-clinical bench testing of the Surgical Planning Component, with outputs evaluated by qualified truthers and estimated correction ±1 degree for angular and ±1.0 mm for distance measurements. Its machine learning outputs are the same as the predicate SMART Bun-Yo-Matic CT (K240642) and no new validations were conducted; clinical data are stated as not needed. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Software verification and validation were carried out based on the “Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices”, at the unit, integration, and system levels" … "Non-Clinical Bench Testing Performance testing was conducted to evaluate the Surgical Planning Component of the device.". Read from the exact FDA decision document on 2026-11-14.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
Evidence summary
The exact FDA document reports software verification and validation at the unit, integration, and system levels and non-clinical bench testing of the Surgical Planning Component, with outputs evaluated by qualified truthers and estimated correction ±1 degree for angular and ±1.0 mm for distance measurements. Its machine learning outputs are the same as the predicate SMART Bun-Yo-Matic CT (K240642) and no new validations were conducted; clinical data are stated as not needed. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Software verification and validation were carried out based on the “Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices”, at the unit, integration, and system levels" … "Non-Clinical Bench Testing Performance testing was conducted to evaluate the Surgical Planning Component of the device.". Read from the exact FDA decision document on 2026-11-14.
Values reported in the exact-submission materials. Consult the linked source for endpoint, threshold, population, and confidence interval before comparison.
Values reported in the exact-submission materials. Consult the linked source for endpoint, threshold, population, and confidence interval before comparison.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K250023 FDA evidence package for SMART PCFD
DesignFDA software substantial-equivalence decision with WBCT reconstruction, measurement, planning, usability, and workflow verification
PopulationAdult progressive collapsing foot deformity cases represented by weight-bearing CT for orthopedic professional review and surgical planning
Scopeexact submission
Tested versionSMART PCFD configuration described in K250023
IndependenceSponsor or vendor study
K250023
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K250023 by exact native submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, or surgical service line and verify payer, site-of-service, and coding assumptions independently.
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: Supported DICOM images, study metadata, and release-specific user inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The public exact-submission material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, and downtime locally.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The public exact-submission material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Measurements, segmentations, visualizations, calculations, models, and reports for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Measurements, segmentations, visualizations, calculations, models, and reports for professional review.
Scope: Exact FDA submission.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
Only qualified imaging professionals and physicians trained for the represented anatomy and workflow should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, and downtime contract locally.
product family · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally. Current vendor material is product-family context; confirm exact release, enabled options, deployment, and local compatibility.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Outputs supplement accepted interpretation or planning methods and require review against source images; supported modality, anatomy, protocol, patient population, and version limits apply.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.
Monitor by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: Outputs supplement accepted interpretation or planning methods and require review against source images; supported modality, anatomy, protocol, patient population, and version limits apply.
product family · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. Current vendor material is product-family context; confirm exact release, enabled options, deployment, and local compatibility.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-20Last searched
27Fields reviewed
13Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, fda decision material, vendor product page, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
Pricing model: Not yet reviewed
Setup and integration fees: Not yet reviewed
Recurring fees: Not yet reviewed
Minimum commitment: Not yet reviewed
Contract duration: Not yet reviewed
Renewal terms: Not yet reviewed
Cancellation terms: Not yet reviewed
Support and service terms: Not yet reviewed
Trial or pilot terms: Not yet reviewed
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The public exact-submission material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The public exact-submission material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, and downtime locally.
Data hosting location: Not yet reviewed
Data retention: Not yet reviewed
Documented data use: Not yet reviewed
Hardware requirements: Not yet reviewed
Network requirements: Not yet reviewed
Identity and access: Not yet reviewed
Security: Not verified - checked 2026-09-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Authorized purpose: Auto-Seg and Spine Auto-Seg accept spine and pelvis CT images and provide three-dimensional segmentation and labels to support spine-surgery planning and assessment by spine surgeons.
Authorized purpose: Acorn 3D Software and Acorn 3DP Model process CT, synthetic CT, and CT angiography for segmentation, visualization, measurement, treatment planning, and three-dimensional printing, including adult and pediatric spine trajectory planning.
Modality
CT/CTA
Anatomy
Spine; craniomaxillofacial; musculoskeletal anatomy; and patient-specific printed models
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.