LingOral is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include prosthetic devices (Veneer, Crown, Bridge, In/Onlay) and orthodontic devices (Clear Aligner). To use LingOral, users must have the necessary education and domain knowledge in orthodontic or prosthodontic practice and receive dedicated training in the use of the software.
Device Story
LingOral is a dental design software used by dentists and oral/maxillofacial specialists in clinical settings. It ingests patient 3D mesh data and DICOM images from compatible scanners. The software provides tools for virtual 3D model creation, alignment, measurement, and analysis (e.g., tooth segmentation, Bolton analysis, IPR). It enables orthodontic treatment simulation and the design of clear aligners. The software outputs 3D data for treatment devices, which are then used by the clinician to guide patient care. By facilitating precise virtual planning and device design, the system assists clinicians in creating customized orthodontic appliances. The software operates on standard PC hardware (Windows/macOS/Linux) and requires a discrete GPU for 3D rendering.
Clinical Evidence
No clinical data. Bench testing only. Verification and validation performed per FDA software and cybersecurity guidance documents.
Indicated for dental professionals to assist in treatment planning and design of prosthetic (Veneer, Crown, Bridge, In/Onlay) and orthodontic (Clear Aligner) devices using patient 3D mesh data. Requires users to have orthodontic or prosthodontic domain knowledge and dedicated software training.
Regulatory Classification
Identification
An orthodontic plastic bracket is a plastic device intended to be bonded to a tooth to apply pressure to a tooth from a flexible orthodontic wire to alter its position.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
May 8, 2026
Hangzhou ChohoTech Co., Ltd.
% Ariel Xiang
Official Correspondent
Shanghai SUNGO Management Consulting Co., Ltd.
14th Floor, Dongfang Bldg., 1500# Century Ave.
Shanghai,
CHINA
Re: K260419
Trade/Device Name: LingOral Dental Design System
Regulation Number: 21 CFR 872.5470
Regulation Name: Orthodontic Plastic Bracket
Regulatory Class: Class II
Product Code: PNN, NOF
Dated: February 9, 2026
Received: February 9, 2026
Dear Ariel Xiang:
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}
K260419 - Ariel Xiang
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}
K260419 - Ariel Xiang
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,
MICHAEL E. ADJODHA -
S
Michael E. Adjodha, MChE, RAC, CQIA
Assistant Director
DHT1B: Division of Dental and ENT Devices
OHT1: Office of Ophthalmic, Anesthesia, Respiratory, ENT, and Dental Devices
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. | K260419 | ? |
| Please provide the device trade name(s). | | ? |
| LingOral Dental Design System | | |
| Please provide your Indications for Use below. | | ? |
| LingOral is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include prosthetic devices (Veneer, Crown, Bridge, In/Onlay) and orthodontic devices (Clear Aligner). To use LingOral, users must have the necessary education and domain knowledge in orthodontic or prosthodontic practice and receive dedicated training in the use of the software. | | |
| 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}
510(k) Summary - K260419
1. 510(k) Summary
The summary of 510(k) safety and effectiveness information is being submitted in accordance with the requirements of 21 CFR Part 807.92.
2. Date:2025/11/21
3. Administrative Information
| Applicant | Hangzhou ChohoTech Co., Ltd. |
| --- | --- |
| Address | Room 405, F4, Building 5, No. 188, LianChuang Street, Yuhang District, Hangzhou, Zhejiang, China |
| Contact Person | Cui Jianqiao |
| Email | cjianqiao@chohotech.com |
4. Device Information
| Trade/Proprietary Name | LingOral |
| --- | --- |
| Common Name | LingOral Dental Design System |
| Device | 21 CFR 872.5470 |
| Regulation Number | Orthodontic Plastic Bracket (Software) |
| Class | 2 |
| Product Code | PNN |
5. Predicate device
Device Name:RAYDENT SW,
510(k) Number: K233625
RAY Co., Ltd.
6. Device Description
LingOral is a software that provides tools to simulate treatment plans based on patient images generated by compatible scanners and design treatment devices based on appropriate three-dimensional images. It allows dental offices to acquire patient data in conjunction with software on compatible imaging equipment and utilize the acquired images to create treatment plans and devices for skilled dentists and oral and maxillofacial specialists.
{5}
7. Indication for use
LingOral is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include prosthetic devices (Veneer, Crown, Bridge, In/Onlay) and orthodontic devices (Clear Aligner).
To use LingOral, users must have the necessary education and domain knowledge in orthodontic or prosthodontic practice and receive dedicated training in the use of the software.
8. Product Comparison Table
| Parameter | Proposed Device | Predicate Device | Remark |
| --- | --- | --- | --- |
| Manufacturer | Hangzhou ChohoTech Co., Ltd. | RAY Co., Ltd. | - |
| Device name | LingOral | RAYDENT SW | - |
| 510(K) Number | / | K233625 | - |
| Common Name | LingOral Dental Design System | Orthodontic Software | - |
| Classification Product Code | PNN | PNN, NOF | SE |
| Indications for use | LingOral is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include prosthetic devices (Veneer, Crown, Bridge, In/Onlay) and orthodontic devices (Clear Aligner). To use LingOral, users must have the necessary education and domain knowledge in orthodontic or prosthodontic practice and receive dedicated training in the use of the software. | RAYDENT SW is a software designed to assist dental professionals in planning patient treatment and designing treatment devices. The software performs simulations based on patient images, allowing reference to treatment plans, and is used as a tool to design treatment devices based on 3D mesh data. Treatment devices include prosthetic devices (Veneer, Crown, Bridge, In/Onlay) and orthodontic devices (Clear Aligner). To use RAYDENT SW, users must have the necessary | SE |
{6}
| | | education and domain knowledge in orthodontic or prosthodontic practice and receive dedicated training in the use of the software. | |
| --- | --- | --- | --- |
| Minimum Hardware/Software Requirements | CPU: Multi-core x86- 64 processor (e.g., Intel® Core™ i7 or equivalent/higher) Memory: ≥ 16 GB RAM (32 GB recommended) Storage: ≥ 512 GB SSD for case data and temporary files GPU: Discrete GPU supporting CUDA (e.g., NVIDIA RTX series, ≥ 6 GB VRAM) Display: Resolution ≥ 1920×1080 with 3D rendering capability Network: Stable internet connection, latency ≤ 100 ms, IPv4/IPv6 supported Operating systems: Windows 10 or later; macOS 10.15 or later; Linux (mainstream distributions such as Ubuntu 20.04+ or later) 64-bit Google Chrome desktop application supported | CPU: Intel Core i5 RAM: 16GB GPU: NVIDIA GeForce RTX 2060 6GB Storage: 1TB SSD Resolution: 1920 x 1080 LAN: 1Gbps Ethernet OS: Windows 10 x64 or Windows 11 x64 | Similar |
| Support Images | DICOM, 2D and 3D images (PLY, OBJ, STL) | DICOM, 2D and 3D images (PLY, OBJ, STL) | SE |
| Supported anatomic areas | Maxilla, Mandible | Maxilla, Mandible | SE |
{7}
| Functionality | - Acquisition of oral topography image data - Creation of virtual 3D virtual dental models - Alignment of 3D virtual dental models - Measurement of 3D virtual dental models - Analysis of 3D virtual dental models - Orthodontic treatment simulation - Virtual orthodontic appliance design - Exporting of 3D virtual model, analysis and treatment case data | - Acquisition of oral topography image data - Creation of virtual 3D virtual dental models - Alignment of 3D virtual dental models - Measurement of 3D virtual dental models - Analysis of 3D virtual dental models - Orthodontic treatment simulation - Virtual orthodontic appliance design - Exporting of 3D virtual model, analysis and treatment case data - Prosthesis design | SE, Proposed Device Except for lacking the Prosthesis design functionality, all other features align with those of the Predicate Device. |
| --- | --- | --- | --- |
| Analysis Features | - Define occlusion - Tooth segmentation - Measure length and angle in the frontal and lateral direction - Define the tooth and set the tooth axis - Tooth width measurements - Bolton analysis - IPR | - Define occlusion - Tooth segmentation - Measure length and angle in the frontal and lateral direction - Define the tooth and set the tooth axis - Tooth width measurements - Bolton analysis - IPR | SE |
| Artificial Intelligence and Machine Learning (AI/ML)-Enabled Medical Devices | YES | YES | SE |
| Prosthesis design | NO | Crown | Proposed Device have no Prosthesis design function, which have no impact on safety and efficacy. |
| | | Pontic | |
| | | Bridge | |
| | | Veneer | |
| | | Inlay/Onlay | |
| | | Temporary Denture | |
| | | eModel | |
The function of Proposed Device is less than Predicate Device, Minimum Hardware/ Software Requirements between Proposed Device and Predicate Device is a little different, Verification has confirmed that these minor variations do not affect the product's safety and efficacy.
{8}
5 / 5
# 9. Performance Testing
Software, hardware, and integration verification and validation testing was performed in accordance with the FDA Guidance Document "Guidance for the Content of Premarket Submissions for Device Software Functions" and "Guidance for the Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions".
The validation suite includes validation of implemented mitigations related to device hazards identified in the risk management procedures.
All test results have been reviewed and approved, showing the LingOral Dental Design System to be substantially equivalent to the predicate devices.
The documentation level of LingOral Dental Design System corresponds to basic documentation level based on the intended use, design, and risk of device software functionality.
# 10. Clinical Testing
Clinical testing is not a requirement and has not been performed.
# 11. Conclusions
In accordance with the Federal Food, Drug and Cosmetic Act, 21 CFR Part 807 and based on the information provided in this premarket notification. Hangzhou ChohoTech Co., Ltd. concludes that the LingOral Dental Design System is substantially equivalent to the predicate device as described herein.
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.