K253764 · Disior, Ltd. · OSN · Feb 26, 2026 · Orthopedic
Device Facts
Record ID
K253764
Device Name
ENOS Software Guided External Fixation System
Applicant
Disior, Ltd.
Product Code
OSN · Orthopedic
Decision Date
Feb 26, 2026
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 888.3030
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The ENOS Software Guided External Fixation System application is used with the Paragon 28 Monkey Rings™ External Fixation System for the treatment of traumatic or reconstructive deformities within the indications for use of the Monkey Rings External Fixation System. It is used to generate a prescription of strut adjustments to provide to the patient.
Device Story
Cloud-based software assisting orthopedic surgeons in planning patient-specific deformity corrections for the Monkey Rings Circular External Fixation System. Surgeon inputs anatomical alignment values, hardware configuration parameters, and treatment objectives; software algorithm processes these inputs alongside mechanical hardware characteristics to calculate required strut lengths. Output is a patient-specific strut adjustment schedule (prescription) provided to the patient for manual hardware adjustment. Used in clinical settings by orthopedic surgeons to visualize bone position and determine necessary mechanical corrections. Benefits include precise, patient-specific deformity correction planning.
Clinical Evidence
No clinical data. Substantial equivalence supported by software verification and validation (unit, integration, and system levels) and non-clinical bench testing using mathematically randomized input sets covering various anatomical sites and hardware configurations.
Technological Characteristics
Cloud-based medical device software. Operates via algorithmic processing of manual surgeon inputs (anatomical alignment, hardware parameters) to compute mechanical strut adjustments. Designed for use with Monkey Rings Circular External Fixation System. Software verification conducted per FDA guidance.
Indications for Use
Indicated for patients requiring treatment of traumatic or reconstructive deformities using the Paragon 28 Monkey Rings External Fixation System.
Regulatory Classification
Identification
Single/multiple component metallic bone fixation appliances and accessories are devices intended to be implanted consisting of one or more metallic components and their metallic fasteners. The devices contain a plate, a nail/plate combination, or a blade/plate combination that are made of alloys, such as cobalt-chromium-molybdenum, stainless steel, and titanium, that are intended to be held in position with fasteners, such as screws and nails, or bolts, nuts, and washers. These devices are used for fixation of fractures of the proximal or distal end of long bones, such as intracapsular, intertrochanteric, intercervical, supracondylar, or condylar fractures of the femur; for fusion of a joint; or for surgical procedures that involve cutting a bone. The devices may be implanted or attached through the skin so that a pulling force (traction) may be applied to the skeletal system.
Predicate Devices
SixFix™ Hexapod Fixator and Deformity Analysis and Correction Software (DACS) (K190069)
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
February 26, 2026
Disior, Ltd.
% Edward Wells-Spicer
Senior Regulatory Affairs Specialist
Paragon 28, Inc.
14445 Grasslands Dr.
Englewood, Colorado 80112
Re: K253764
Trade/Device Name: ENOS Software Guided External Fixation System
Regulation Number: 21 CFR 888.3030
Regulation Name: Single/Multiple Component Metallic Bone Fixation Appliances And Accessories
Regulatory Class: Class II
Product Code: OSN
Dated: November 25, 2025
Received: November 25, 2025
Dear Edward Wells-Spicer:
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}
K253764 - Edward Wells-Spicer
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 13484 clause 8.3 (Nonconforming product), and ISO 13485 clause 8.5 (Corrective and 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 21 CFR 820.70) and document changes and approvals in the Medical Device File (21 CFR 820.181).
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 the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-
{2}
K253764 - Edward Wells-Spicer
Page 3
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,
Shumaya Ali -S
Shumaya Ali, M.P.H.
Assistant Director
DHT6C: Division of Restorative,
Repair, and Trauma Devices
OHT6: Office of Orthopedic Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
Page 1 of 1
| 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. | K253764 | ? |
| Please provide the device trade name(s). | | ? |
| ENOS Software Guided External Fixation System | | |
| Please provide your Indications for Use below. | | ? |
| The ENOS Software Guided External Fixation System application is used with the Paragon 28 Monkey Rings™ External Fixation System for the treatment of traumatic or reconstructive deformities within the indications for use of the Monkey Rings External Fixation System. It is used to generate a prescription of strut adjustments to provide to the patient. | | |
| 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
Manufacturer: Disior Ltd
HTC Helsinki, Building Pinta, Tammasaarenkatu 3
Helsinki Uusimaa, FL, 00180, Finland
Contact: Aarno Jussila
Director of Smart 28 - Quality
Phone: +358 40 673 4939
Email: aarno.jussila@zimmerbiomet.com
Prepared By: Edward Wells-Spicer
Senior Regulatory Affairs Specialist
Paragon 28, Inc.
14445 Grasslands Dr.,
Englewood, CO, 80112
Phone: 720-994-5481
Date Prepared: February 25, 2025
Device Trade Name: ENOS Software Guided External Fixation System
Device Class and Common Name: Class II, Software for diagnosis/treatment
Classification: 888.3030 - Single/multiple component metallic bone fixation appliances and accessories
Product Codes: OSN
Indications for Use: The ENOS Software Guided External Fixation System application is used with the Paragon 28 Monkey Rings™ External Fixation System for the treatment of traumatic or reconstructive deformities within the indications for use of the Monkey Rings External Fixation System. It is used to generate a prescription of strut adjustments to provide to the patient.
Device Description: The ENOS Software Guided External Fixation System (also known as Smart Monkey Rings) is a cloud-based medical device software system that assists orthopedic surgeons in planning patient-specific deformity corrections for use with the Monkey Rings Circular External Fixation System. The surgeon enters anatomical alignment values, hardware configuration parameters, and treatment objectives, and the software's algorithm processes these inputs together with the mechanical characteristics of the Monkey Rings hardware to generate a patient-specific strut adjustment schedule.
Traditional 510(k) - K253764
{5}
Traditional 510(k) - K253764
Page 2 of 3
Primary Predicate: SixFix™ Hexapod Fixator and Deformity Analysis and Correction Software (DACS) (K190069)
Additional Predicate: Orthohub External Fixator Software (K140550)
Substantial Equivalence:
The subject device and the primary predicate device have similar intended uses. Both the ENOS Software Guided External Fixation System and the Sixfix Hexapod primary predicate are intended to be used for traumatic (subject device) and post-traumatic injuries (primary predicate device). The subject device and the secondary predicate device are both intended for the treatment of traumatic or reconstructive deformities. The subject device and secondary predicate device have identical intended uses, except for the secondary predicate specifying reconstructive tibia deformities while the subject device is intended for reconstructive deformities within the Monkey Rings External Fixation System (K212895). The subject device, primary predicate device and the secondary predicate device generate a prescription of strut adjustments.
The subject device and primary predicate have manual input methods to assist the surgeon calculating the lengths of the struts connecting the rings to manipulate the bone fragments. Also, for the subject and primary predicate, the software receives inputs from the physician and allows the physician to visualize the moving bone position. The subject and primary predicate program computes the strut lengths necessary to implement adjustments required by the surgeon. The output of the subject device is a prescription of strut adjustments, which is identical to the primary and secondary predicates.
A difference between the subject device and secondary predicate is the use of a web-based software run in the cloud for the subject device and the use of a macintosh computer for the secondary predicate. Additionally, the secondary predicate utilizes x-rays in addition to manual surgeon input for calculations of recommended adjustments while the subject device is manual input only.
The differences between the subject device and predicates do not introduce new issues of safety and effectiveness.
Performance Testing:
All necessary testing has been performed on the ENOS Software Guided External Fixation System to assure substantial equivalence to its predicate and demonstrate the subject device performs as intended.
Software Verification and Validation
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 to determine substantial equivalence to the predicate device.
Non-Clinical Bench Testing
Beyond Formal Verification Testing, incremental testing of software inputs against expected frame data was also performed. Given the number of anatomical sides, sites, ring combinations, and ring sizes possible, a mathematically randomized set of inputs over defined limits was selected to be used to validate that the software was developed to satisfy its intended purpose.
{6}
Conclusions:
Clinical data are not needed to support the safety and effectiveness of the subject device.
The subject device possesses similar intended uses, technological characteristics, and principles of operation as the primary predicate and secondary predicate devices. The subject device does not raise new issues of safety or effectiveness. The subject device is substantially equivalent to the legally marketed predicate devices.
Traditional 510(k) - K253764
Page 3 of 3
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.