FDA-cleared profile

Relu Creator

Relu BV · CBCT · FDA-cleared (510(k))

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.

Clinical role
Dental and craniomaxillofacial image management, transfer, enhancement, analysis, and design-input support.
Images and patients
CBCT · Dental/Maxillofacial
Key limitation
Keep in mind: Exact image source, anatomy, design workflow, output use, and compatible software limits are submission- and release-specific. Relu Creator manages, transfers, displays, enhances, and analyzes dental and craniomaxillofacial image information and provides design input for dental solutions within the labeled workflow.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: Relu Creator manages, transfers, displays, enhances, and analyzes dental and craniomaxillofacial image information and provides design input for dental solutions within the labeled workflow.
  • Which images or clinical context are in scope?Modality: CBCT Anatomy or clinical context: Dental/Maxillofacial Input: Supported dental, maxillary, mandibular, airway, or other labeled image information and associated DICOM data.
  • Who uses it?Intended users: Qualified dental, oral and maxillofacial, radiology, and other trained healthcare professionals.
  • What does the software produce?Output: Enhanced, displayed, transferred, or analyzed dental and craniomaxillofacial image information for professional review.
  • What is its most important limitation?Key limitation: Exact image source, anatomy, design workflow, output use, and compatible software limits are submission- and release-specific. Relu Creator manages, transfers, displays, enhances, and analyzes dental and craniomaxillofacial image information and provides design input for dental solutions within the labeled workflow.

Clinical takeaway. Clinical role: Relu Creator manages, transfers, displays, enhances, and analyzes dental and craniomaxillofacial image information and provides design input for dental solutions within the labeled workflow.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports, without study design, data size or numeric results, that the device passed testing for appropriate verification and validation and, based on performance testing and software validation testing, was shown to be appropriate for its indications for use. 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
Relu Creator manages, transfers, displays, enhances, and analyzes dental and craniomaxillofacial image information and provides design input for dental solutions within the labeled workflow.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Dental and craniomaxillofacial image management, transfer, enhancement, analysis, and design-input support.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported dental, maxillary, mandibular, airway, or other labeled image information and associated DICOM data.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Enhanced, displayed, transferred, or analyzed dental and craniomaxillofacial image information for professional review.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Dental and craniomaxillofacial imaging or design workflows covered by the exact submission labeling.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Qualified dental, oral and maxillofacial, radiology, and other trained healthcare professionals.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
Exact image source, anatomy, design workflow, output use, and compatible software limits are submission- and release-specific. Relu Creator manages, transfers, displays, enhances, and analyzes dental and craniomaxillofacial image information and provides design input for dental solutions within the labeled workflow.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports, without study design, data size or numeric results, that the device passed testing for appropriate verification and validation and, based on performance testing and software validation testing, was shown to be appropriate for its indications for use. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The Subject Device has passed testing for appropriate verification and validation and performed per its intended use." … "Based on the performance testing and software validation testing, the Subject Device, Relu Creator, has been shown to be appropriate for its indications for use". Read from the exact FDA decision document on 2026-11-14.

Evidence

Performance evidence

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, without study design, data size or numeric results, that the device passed testing for appropriate verification and validation and, based on performance testing and software validation testing, was shown to be appropriate for its indications for use. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The Subject Device has passed testing for appropriate verification and validation and performed per its intended use." … "Based on the performance testing and software validation testing, the Subject Device, Relu Creator, has been shown to be appropriate for its indications for use". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No exact submission and version-linked sensitivity endpoint is published in this dossier; do not substitute a product-family or candidate-study value.

Reported specificity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No exact submission and version-linked specificity endpoint is published in this dossier; do not substitute a product-family or candidate-study value.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

FDA submission-specific verification and validation evidence for K233925

  • DesignRegulatory verification, validation, and labeling evidence reviewed for exact FDA submission K233925.
  • PopulationThe labeled population and test materials for exact submission K233925; a general clinical study population is not established here.
  • Scopeexact submission
  • Tested versionRelu Creator (K233925)
  • IndependenceSponsor or vendor study

K233925

FDA regulatory evidence is submission-specific but is not independent clinical performance evidence.

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
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: Supported dental, maxillary, mandibular, airway, or other labeled image information and associated DICOM data.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-04 · FDA decision summary for K233925 - Relu Creator

  2. Routing

    Source context, not route validation: The exact FDA package describes Relu Creator providing outputs in STL, DICOM, PLY, and OBJ formats and storing and providing images within the system or across computer systems at different locations. Interface versions and local compatibility require confirmation.

    Scope: Exact FDA submission. Packet wording: "The subject device provides outputs in several formats (STL, DICOM, PLY, OBJ) that are commonly for dental and craniomaxillofacial treatment planning applications." … "It stores and provides these images within the system or across computer systems at different locations.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-11-14 · FDA decision summary for K233925 - Relu Creator

  3. AI processing

    Unresolved route: Not established for the exact route.

    Scope: Exact FDA submission. Exact deployment topology, hosting, network boundaries, update mechanism, and local operational requirements are not established for this submission.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-04 ·

  4. Returned objects

    Source context, not route validation: Enhanced, displayed, transferred, or analyzed dental and craniomaxillofacial image information for professional review.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-04 · FDA decision summary for K233925 - Relu Creator

  5. Viewer/worklist/report

    Unresolved route: Enhanced, displayed, transferred, or analyzed dental and craniomaxillofacial image information 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.

    Field checked 2026-09-04 · FDA decision summary for K233925 - Relu Creator

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Integration
The exact FDA package describes Relu Creator providing outputs in STL, DICOM, PLY, and OBJ formats and storing and providing images within the system or across computer systems at different locations. Interface versions and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The subject device provides outputs in several formats (STL, DICOM, PLY, OBJ) that are commonly for dental and craniomaxillofacial treatment planning applications." … "It stores and provides these images within the system or across computer systems at different locations.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Workflow role

Dental and craniomaxillofacial image management, transfer, enhancement, analysis, and design-input support.

exact submission · checked 2026-09-04

This is a submission-anchored intended-use summary, not a local acceptance result.

Input

Supported dental, maxillary, mandibular, airway, or other labeled image information and associated DICOM data.

exact submission · checked 2026-09-04

Exact supported inputs and protocol limits must be confirmed from the complete labeling.

Output

Enhanced, displayed, transferred, or analyzed dental and craniomaxillofacial image information for professional review.

exact submission · checked 2026-09-04

Output review, editing, and downstream use remain release- and site-specific.

Vendor family context

Current vendor material is product-family context for K233925 only; exact release, enabled options, deployment, and local interoperability require confirmation.

product family · checked 2026-09-04

Vendor material is not exact-release evidence unless that linkage is separately proven.

Site validation status

Exact local interfaces, deployment topology, security controls, downtime behavior, and support obligations remain unestablished.

exact submission · checked 2026-09-04

Obtain organization-specific implementation evidence before procurement or clinical use.

Sources & review details FDA 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.

FDA submission
K233925
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CBCT
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Dental/Maxillofacial
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2024-06-13
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
28Fields reviewed
14Source classes checked
2Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains 2 PubMed and 0 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 2 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, acr ai central product, vendor product page, implementation documentation, reimbursement policy, peer reviewed literature, clinical trial registry, 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 exact-release price, license fee, subscription, contract, or implementation cost was established in this review.

  • 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
  • Reimbursement: Not applicable - checked 2026-09-04 - Not applicable

    CMS index context was checked, but no product-specific coverage or reimbursement determination is inferred.

  • Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission

    Exact deployment topology, hosting, network boundaries, update mechanism, and local operational requirements are not established for this submission.

  • 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 publicly available - checked 2026-09-04 - Exact FDA submission

    Public sources reviewed here do not establish the complete exact-release security posture, including identity, audit, encryption, retention, remote access, vulnerability management, backup, or incident response.

  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-10-27 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

  • Monitoring: Not verified - checked 2026-10-27 - Exact FDA submission

    Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.

10 sources - 3 history items

Source ledger

  1. FDA decision summary for K233925 - Relu Creator

    U.S. Food and Drug Administration - Published 2024-06-13 - Accessed 2026-09-04

    Scope: regulatoryIdentity, productIdentity, indication, modality, anatomy, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. Relu Creator model card (K233925)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  7. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  8. Relu Creator family context

    Relu - Accessed 2026-09-04

    Scope: productFamilyContext, workflowRole, implementationCapabilities

  9. FDA-Approved AI Solutions in Dental Imaging: A Narrative Review of Applications, Evidence, and Outlook.

    U.S. National Library of Medicine - Accessed 2026-09-04

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  10. Comparative analysis of five AI platforms for mandibular canal segmentation on CBCT images.

    U.S. National Library of Medicine - Accessed 2026-09-04

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

Research history

  1. K233925 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K250755

DS Core Diagnosis

Dentsply Sirona Inc.

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.

Modality
CBCT
Anatomy
Dental/Maxillofacial
Decision
2025-08-12
FDA-cleared K251514

Overjet CBCT Assist

Overjet, Inc.

Authorized purpose: Dental and craniomaxillofacial CBCT segmentation, measurement and visualization support

Modality
CBCT
Anatomy
Dental/Maxillofacial
Decision
2025-12-05
FDA-cleared K232698

NemoScan

Software Nemotec S.L.

NemoScan supports dental CT or cone-beam CT visualization, segmentation, implant and surgical planning, instrument positioning, and guide planning from preoperative maxillofacial images.

Modality
CBCT
Anatomy
Dental/Maxillofacial
Decision
2024-01-18
FDA-cleared K231757

Ez3D-i /E3

Ewoosoft Co., Ltd

Authorized purpose: Ez3D-i/E3 provides dental and maxillofacial DICOM viewing, three-dimensional visualization, multiplanar reconstruction, two-dimensional analysis, implant simulation, canal tracing, and bone-density tools for trained radiologists and dentists.

Modality
CBCT
Anatomy
Dental/Maxillofacial
Decision
2023-07-14

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history