Authorized purpose: Measures minimum joint-space width and assesses sclerosis, joint-space narrowing, osteophytes, and radiographic knee osteoarthritis using OARSI and Kellgren-Lawrence criteria.
Clinical role
Fully automated software that measures minimum joint space width on CR or DX images and gives an OARSI/KL-based output to aid medical professionals, without interpreting results; not to be solely relied upon to make or confirm a diagnosis.
Images and patients
X-ray/Radiography · Knee
Key limitation
Keep in mind: Not a substitute for full evaluation or sole basis for diagnosis; trained professionals are required and packet Linux/Docker compatibility is not current deployment assurance.
Clinical detailsPurpose, 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: Measures minimum joint-space width and assesses sclerosis, joint-space narrowing, osteophytes, and radiographic knee osteoarthritis using OARSI and Kellgren-Lawrence criteria.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Knee Input: AP/PA and lateral digital knee radiographs.
Who uses it?Intended users: Trained radiologists, orthopedics, physicians, and medical technicians.
What does the software produce?Output: Visual overlays and a table with JSW, OARSI, and Kellgren-Lawrence results plus text findings and impression; PACS/DICOM review is supported.
What is its most important limitation?Key limitation: Not a substitute for full evaluation or sole basis for diagnosis; trained professionals are required and packet Linux/Docker compatibility is not current deployment assurance.
Clinical takeaway. Clinical role: Measures minimum joint-space width and assesses sclerosis, joint-space narrowing, osteophytes, and radiographic knee osteoarthritis using OARSI and Kellgren-Lawrence criteria.
Evidence takeaway. Evidence from the reviewed source record: OAI dataset with physician ground truth reported task-specific sensitivity and specificity pairs for Kellgren-Lawrence, joint-space narrowing, osteophytosis, and sclerosis; no one generic metric applies.
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
Measures minimum joint-space width and assesses sclerosis, joint-space narrowing, osteophytes, and radiographic knee osteoarthritis using OARSI and Kellgren-Lawrence criteria.
Exact FDA submission
Checked 2026-09-15
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Fully automated software that measures minimum joint space width on CR or DX images and gives an OARSI/KL-based output to aid medical professionals, without interpreting results; not to be solely relied upon to make or confirm a diagnosis.
Exact FDA submission
Checked 2026-11-14
Packet wording: "RBknee is a radiological fully automated image processing software device of either computed (CR) or directly digital (DX) images intended to aid medical professionals in the measurement of minimum joint space width;" … "RBknee is not interpreting any results but makes an objective measurement and providing an output based on a well established scale (OARSI/KL).". Read from the exact FDA decision document on 2026-11-14.
Patients whose standing, fixed-flexion knee radiographs are assessed for radiographic knee osteoarthritis (OA); the FDA document does not specify a facility type.
Exact FDA submission
Checked 2026-11-14
Packet wording: "the presence or absence of radiographic knee OA based on Kellgren-Lawrence grading of standing, fixed-flexion radiographs of the knee." … "information on the presence or absence of radiographic knee osteoarthritis (OA) based on the Kellgren-Lawrence (KL) score.". Read from the exact FDA decision document on 2026-11-14.
Not a substitute for full evaluation or sole basis for diagnosis; trained professionals are required and packet Linux/Docker compatibility is not current deployment assurance.
OAI dataset with physician ground truth reported task-specific sensitivity and specificity pairs for Kellgren-Lawrence, joint-space narrowing, osteophytosis, and sclerosis; no one generic metric applies.
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
OAI dataset with physician ground truth reported task-specific sensitivity and specificity pairs for Kellgren-Lawrence, joint-space narrowing, osteophytosis, and sclerosis; no one generic metric applies.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Rbknee regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K203696
Samplen=1403
IndependenceIndependence not established
K203696
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K203696. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: AP/PA and lateral digital knee radiographs.
Scope: Exact FDA submission. FDA packet input scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes RBknee taking digital AP/PA radiographs as input, being able to be integrated to a PACS, and providing outputs that can be reviewed in a DICOM viewer. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "RBknee can be integrated to a PACS and the outputs of RBknee can be reviewed in a DICOM viewer." … "In brief, RBknee takes digital radiographs (AP/PA) as input and as output provides:". 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.
Source context, not route validation: The exact FDA package describes RBknee as operating in a Linux environment and deployable to be compatible with any operating system supporting the third-party software Docker. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "RBknee operates in a Linux environment and can be deployed to be compatible with any operating system supporting the third-party software Docker.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Visual overlays and a table with JSW, OARSI, and Kellgren-Lawrence results plus text findings and impression; PACS/DICOM review is supported.
Scope: Exact FDA submission. FDA packet output scope.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Visual overlays and a table with JSW, OARSI, and Kellgren-Lawrence results plus text findings and impression; PACS/DICOM review is supported.
Scope: Exact FDA submission. FDA packet output scope.
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.
The exact FDA package describes RBknee as operating in a Linux environment and deployable to be compatible with any operating system supporting the third-party software Docker. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "RBknee operates in a Linux environment and can be deployed to be compatible with any operating system supporting the third-party software Docker.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes RBknee taking digital AP/PA radiographs as input, being able to be integrated to a PACS, and providing outputs that can be reviewed in a DICOM viewer. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "RBknee can be integrated to a PACS and the outputs of RBknee can be reviewed in a DICOM viewer." … "In brief, RBknee takes digital radiographs (AP/PA) as input and as output provides:". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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.
Exact FDA record reviewedStatus
2026-09-20Last searched
25Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 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, fda device recall, literature index, trial registry, fda decision summary packet, 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 verified - checked 2026-09-09 - Exact FDA submission
No public price or quote for the exact K203696 configuration 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 publicly available - checked 2026-09-09 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
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 verified - checked 2026-09-09 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: View and quantify bone age from 2D posteroanterior left-hand radiographs to aid pediatric radiologists assessing patients aged 2-18 years.
Authorized purpose: Analyzes two-dimensional bitewing and periapical radiographs of permanent teeth in patients aged 15 and older to identify and localize caries, calculus, periapical radiolucency, root canal filling deficiency, discrepancy at an existing restoration margin, and bone loss; also supports alveolar bone-level measurement and restoration/dental-anatomy segmentation as an adjunct to dentist review.
Authorized purpose: Provides automated concurrent-read detection and segmentation of caries on bitewing radiographs in patients 18 and older, adding information for the dentist while requiring complete dentist review and judgment.
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.