Use the exact cleared version and supported image inputs. Segmentation and implant-planning outputs require dentist or surgeon confirmation and do not replace clinical examination or surgical judgment.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
Output and human actionThree-dimensional models, measurements, implant or canal planning views, surgical-guide inputs, and reports for professional review.
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
NemoScan supports dental implantology by segmenting and transferring anatomy from CT or cone-beam CT images for implant and surgical planning.
Use the exact cleared version and supported image inputs. Segmentation and implant-planning outputs require dentist or surgeon confirmation and do not replace clinical examination or surgical judgment.
K192571 reports dental image segmentation, planning, visualization, and software validation for implantology. The public FDA summary does not establish a universal clinical-outcome or diagnostic-performance metric, and later NemoScan family material must not be assumed to describe this version.
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
K192571 reports dental image segmentation, planning, visualization, and software validation for implantology. The public FDA summary does not establish a universal clinical-outcome or diagnostic-performance metric, and later NemoScan family material must not be assumed to describe this version.
Sensitivity is not the primary endpoint for this system, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-03
Specificity is not the primary endpoint for this system, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K192571 FDA performance package for NemoScan
DesignManufacturer dental image segmentation, visualization, implant-planning, and software validation
PopulationDental CT or CBCT implant-planning workflows
Scopeexact submission
Tested versionNemoScan
IndependenceSponsor or vendor study
K192571
Manufacturer evidence submitted for FDA clearance or approval; local clinical, technical, and workflow acceptance remains necessary.
2 unlinked candidate evidence records are retained for source review and excluded from this evidence display.
Safety and lifecycle
Postmarket record
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 K192571 by exact submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-03
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 dental CT, cone-beam CT, panoramic, cephalometric, or intraoral radiographic data.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Three-dimensional models, measurements, implant or canal planning views, surgical-guide inputs, 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: Three-dimensional models, measurements, implant or canal planning views, surgical-guide inputs, 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.
Software Nemotec, S.L. hosts its RINA ISO/IEC 27001:2022 certificate (first issue 2023-03-31, revision 2025-04-01, stated expiry 2026-03-30; no renewal copy located as of 2026-10-27) covering information security management for the design, development, manufacture, installation, training, technical support and distribution of planning software for dental applications.
Product family
Checked 2026-10-27
Certificate PDF read on the owning domain (nemotec.com). The hosted certificate states an expiry date of 2026-03-30 and no renewal copy was located; validity is subject to periodic RINA audits. Scope is planning software for dental applications, which covers NemoScan.
Only qualified dentists, dental radiologists, oral and maxillofacial surgeons, and trained dental imaging staff should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
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: Use the exact cleared version and supported image inputs. Segmentation and implant-planning outputs require dentist or surgeon confirmation and do not replace clinical examination or surgical judgment.
DICOM import and export to dental workstations, PACS, laboratory, or guide-manufacturing workflows; validate patient identity, orientation, voxel geometry, measurements, and export.
exact submission · checked 2026-09-03
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally. The capability is derived from the exact FDA workflow and still requires local acceptance testing.
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. Use the exact cleared version and supported image inputs. Segmentation and implant-planning outputs require dentist or surgeon confirmation and do not replace clinical examination or surgical judgment.
exact submission · checked 2026-09-03
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-03
No exact-product price was found in the reviewed public material; vendor productivity claims are scenario inputs, not guaranteed local savings.
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: Use the exact cleared version and supported image inputs. Segmentation and implant-planning outputs require dentist or surgeon confirmation and do not replace clinical examination or surgical judgment.
exact submission · checked 2026-09-03
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. The capability is derived from the exact FDA workflow and still requires local acceptance testing.
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-04Last searched
25Fields reviewed
10Source classes checked
2Awaiting review PubMed leads
0Awaiting review trial leads
0Unreviewed FDA recall leads
Recovered from the prior exact-submission extraction and normalized under the current provenance rules. Exact FDA decision materials were reviewed for identity, indication, users, workflow, limitations, and submitted performance. Current vendor material is labeled product-family context where it does not establish the exact release. PubMed and ClinicalTrials.gov results are retained as candidate evidence with version applicability pending; CMS reimbursement context and exact-identifier openFDA postmarket results were also checked. Pricing, final security architecture, contracted services, enabled options, and local interoperability remain organization-specific evidence. Automated exact-name discovery found 2 PubMed and 0 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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-03 - 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.
Authorized purpose: Displays and supports interpretation of digital/digitized dental media, including CBCT and other 2D/3D X-ray images; its Panoramic Curve Proposal generates a proposed dental-arch curve for patients aged 12 years and older with permanent dentition that a clinician can review and adjust.
Authorized purpose: Relu Creator manages, transfers, displays, enhances, and analyzes dental and craniomaxillofacial image information and provides design input for dental solutions within the labeled workflow.
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.