United Orthopedic Knee Patient Specific Instrumentation
Enhatch, Inc. • Orthopedic • 12/20/2023
Device Purpose
The United Orthopedic Knee Patient Specific Instrumentation system aims to enhance total knee arthroplasty by providing pre-operative surgical planning and customized surgical guides derived from patient-specific imaging. Its methodology integrates deep learning algorithms for segmenting CT and X-ray images and an optimization algorithm for determining implant size and position, facilitating the creation of precise, single-use instrumentation.
Summary
The United Orthopedic Knee Patient Specific Instrumentation is an orthopedic instrument system designed to assist surgeons in the positioning of compatible total knee arthroplasty (TKA) systems. It comprises surgical planning software (Intelligent Surgery Knee CT Segmentation Engine/Knee X-ray Segmentation Engine, and Implant Recognition Engine), patient-specific surgical guides, and anatomical models. The system is intended to preoperatively plan the surgical placement of United Orthopedics Knee implants using patient radiological images (CT or X-ray) and 3D bone reconstructions, and is indicated for patients without severe bone deformities (e.g., HKA greater than 15° or deformities due to prior fracture) for use with the U2 Total Knee System. The instruments, including guides and models, are single-use only. The system's methodology relies on deep learning algorithms within its segmentation engines to process DICOM medical images, extracting femur and tibia data to generate 3D models for treatment planning and surgical guide design. The Implant Recognition Engine uses an optimization algorithm to assist in selecting implant size and position by identifying anatomical landmarks and articular surface topographies, guiding the design of patient-specific surgical instruments. This process is managed by Enhatch technicians who interface with the software to produce outputs for surgeons. Non-clinical performance testing, including segmentation accuracy, model verification, software system testing, guide wear, and full system verification using cadaver specimens, demonstrated satisfactory performance and accuracy in line with its intended use.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the accuracy of the deep learning segmentation engine compare between CT and X-ray modalities, particularly in patients with borderline bone deformities close to the exclusion criteria (HKA ~15°)?; What is the typical turnaround time from image acquisition to the availability of the surgical plan and patient-specific guides, and how might this impact urgent or time-sensitive cases?; Given that Enhatch technicians interface with the software, what quality control measures are in place to ensure consistency and accuracy in the preoperative plans provided to surgeons?; How does the optimization algorithm for implant sizing and positioning account for soft tissue considerations or patient-specific ligamentous balancing, if at all?; What were the quantitative accuracy results (e.g., mean error in degrees and millimeters for resection angles and levels) from the cadaveric system verification and validation tests compared to the preoperative plan?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Post-§524B but no clear network capability detected
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of ML-BOM detected in AI-generated device summary.
• SBOM not mentioned in AI-generated device summary. Under §524B (effective Oct 2023), cyber devices must provide a SBOM.
• Cybersecurity risk assessment not referenced in AI-generated device summary. FDA cybersecurity guidance (2023) expects this for cyber devices.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• Not detected in AI-generated device summary: SBOM, SaaSBOM, HBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly