FDA-cleared profile

FractureDetect (FX)

Imagen Technologies, Inc. · X-ray/Radiography · FDA-cleared (510(k))

Authorized purpose: Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.

Clinical role
Computer-assisted detection and diagnosis software assisting clinicians reviewing adult musculoskeletal radiographs; if it detects a fracture, its output overlay adds a “Fracture: DETECTED” annotation and bounding boxes, and clinicians can toggle the overlay within their PACS viewer.
Images and patients
X-ray/Radiography · MSK
Key limitation
Keep in mind: Adults only, limited to listed study types and views, with no patient contact.

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: Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.
  • Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: MSK Input: Commonly acquired adult radiographs received through a generic DICOM node or PACS.
  • Who uses it?Intended users: Clinicians.
  • What does the software produce?Output: A toggleable DICOM overlay reading Fracture: DETECTED with bounding boxes or Fracture: NOT DETECTED without boxes.
  • What is its most important limitation?Key limitation: Adults only, limited to listed study types and views, with no patient contact.

Clinical takeaway. Clinical role: Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.

Evidence takeaway. Evidence from the reviewed source record: Standalone study of 11,970 cases reported sensitivity 0.951, specificity 0.893, and AUC 0.982; an MRMC study used 24 readers and 175 cases.

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
Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.
  • Exact FDA submission
  • Checked 2026-09-15

Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.

Workflow role
Computer-assisted detection and diagnosis software assisting clinicians reviewing adult musculoskeletal radiographs; if it detects a fracture, its output overlay adds a “Fracture: DETECTED” annotation and bounding boxes, and clinicians can toggle the overlay within their PACS viewer.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "FractureDetect (FX) is a computer-assisted detection and diagnosis (CAD) software device to assist clinicians in detecting fractures during the review of radiographs of the musculoskeletal system. FX is indicated for adults only." … "If any fracture is detected by FX, the output overlay is composed to include the text annotation “Fracture: DETECTED” and to include one or more bounding boxes surrounding any fracture site(s).". Read from the exact FDA decision document on 2026-11-14.

Required input
Commonly acquired adult radiographs received through a generic DICOM node or PACS.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet input scope.

Output and clinician action
A toggleable DICOM overlay reading Fracture: DETECTED with bounding boxes or Fracture: NOT DETECTED without boxes.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet output scope.

Care setting
Adult
  • Exact FDA submission
  • Checked 2026-09-01

Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.

Intended users
Clinicians.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet intended-user statement.

Limitations
Adults only, limited to listed study types and views, with no patient contact.
  • Exact FDA submission
  • Checked 2026-09-15

Exact FDA limitation boundary.

Evidence summary
Standalone study of 11,970 cases reported sensitivity 0.951, specificity 0.893, and AUC 0.982; an MRMC study used 24 readers and 175 cases.
  • Exact FDA submission
  • Checked 2026-09-15

Submission-reported performance result.

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
Standalone study of 11,970 cases reported sensitivity 0.951, specificity 0.893, and AUC 0.982; an MRMC study used 24 readers and 175 cases.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

Submission-reported performance result.

Reported sensitivity
95% (95% CI: 94%, 96%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model sensitivity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

Reported specificity
89.3% (95% CI: 88.6%, 89.8%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model specificity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

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

FractureDetect (FX) regulatory performance study summary

  • DesignStand-alone performance and reader study (ACR AI Central category)
  • PopulationAdult
  • Scopeexact submission
  • Tested versionExact product version not reported; regulatory study summarized for FDA submission K193417
  • Samplen=11970
  • IndependenceIndependence not established

K193417

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

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
The exact-identifier FDA recall query returned no native recall record for K193417. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-09
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

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: Commonly acquired adult radiographs received through a generic DICOM node or PACS.

    Scope: Exact FDA submission. FDA packet input scope.

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

    Field checked 2026-09-15 · FDA K193417: FractureDetect (FX)

  2. Routing

    Source context, not route validation: The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.

    Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

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

    Field checked 2026-09-01 · FractureDetect (FX) model card (K193417)

  3. AI processing

    Source context, not route validation: The exact FDA package describes the FractureDetect (FX) platform as secure local processing and delivery of DICOM images. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "The table below compares the key technological feature of the subject devices to the predicate device (OsteoDetect, DEN180005)." … "Platform Secure local processing and Secure local processing and delivery of DICOM images delivery of DICOM images". 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.

    Field checked 2026-11-14 · FDA K193417: FractureDetect (FX)

  4. Returned objects

    Source context, not route validation: A toggleable DICOM overlay reading Fracture: DETECTED with bounding boxes or Fracture: NOT DETECTED without boxes.

    Scope: Exact FDA submission. FDA packet output scope.

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

    Field checked 2026-09-15 · FDA K193417: FractureDetect (FX)

  5. Viewer/worklist/report

    Unresolved route: A toggleable DICOM overlay reading Fracture: DETECTED with bounding boxes or Fracture: NOT DETECTED without boxes.

    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.

    Field checked 2026-09-15 · FDA K193417: FractureDetect (FX)

  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

Deployment
The exact FDA package describes the FractureDetect (FX) platform as secure local processing and delivery of DICOM images. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The table below compares the key technological feature of the subject devices to the predicate device (OsteoDetect, DEN180005)." … "Platform Secure local processing and Secure local processing and delivery of DICOM images delivery of DICOM images". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-09-01

Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

Security
Imagen's security policy (effective 2024-04-02) states HIPAA, HITRUST CSF and SOC 2 Type II compliance, encryption in transit and at rest, least-privilege access, multi-factor authentication, audit trails and incident response. Vendor statement; no report or certificate was read.
  • Vendor-wide
  • Checked 2026-10-26

Vendor statement, not an attestation. Identity bridge: the policy is on imagen.ai, whose AI software page lists this product by name, and the FDA letter for this entry names Imagen Technologies, Inc. (New York). The policy is company-wide; exact-release scope is not established. A 2023 HITRUST release names the Care Delivery Services platform, not the devices, and is not applied.

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

Result destination

PACS is explicitly referenced as a result destination.

exact submission · checked 2026-09-01

Confirm supported products, versions, routing behavior, and display requirements during local evaluation.

Supported acquisition environment

Scanner manufacturers: All

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for FractureDetect (FX); FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-09
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
K193417
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
X-ray/Radiography
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

FDA radiograph scope.

Anatomy
MSK
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet lists multiple adult musculoskeletal regions and views.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-07-30
  • 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
27Fields 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 K193417 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
  • 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.

8 sources - 3 history items

Source ledger

  1. FDA K193417: FractureDetect (FX)

    U.S. Food and Drug Administration - Published 2020-07-30 - Accessed 2026-09-09

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary, deployment

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. FractureDetect (FX) model card (K193417)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  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. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K193417

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

    Scope: postmarketSafety

  8. Imagen Security Policy

    Imagen Technologies - Published 2024-04-02 - Accessed 2026-10-26

    Scope: security

Research history

  1. K193417 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 K242171

TechCare Trauma

Milvue

Authorized purpose: Aids clinicians and radiologists reviewing 2D X-ray radiographs by detecting, localizing, and characterizing fractures across the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib examinations, and by detecting elbow joint effusion on lateral elbow or forearm views in children/adolescents and adults; results are not standalone clinical decisions.

Modality
X-ray/Radiography
Anatomy
MSK
Decision
2025-01-17
FDA-cleared K240845

Rayvolve

AZmed SAS

Authorized purpose: Assists radiologists and emergency physicians in detecting fractures on DICOM musculoskeletal radiographs for adults and children aged 2 years or older, limited to the FDA-listed anatomic areas and standard views (ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot); it is an aided-diagnosis device and does not operate autonomously.

Modality
X-ray/Radiography
Anatomy
MSK
Decision
2024-07-17
FDA-cleared K251408

OsteoSight™ Hip (v1)

Naitive Technologies Ltd

Authorized purpose: Opportunistically analyzes standard AP hip or pelvis radiographs in patients aged 50 years and older and issues a report when the estimated femoral-neck BMD is below a preset threshold to prompt clinical bone-health assessment; absence of a report does not rule out low BMD.

Modality
X-ray/Radiography
Anatomy
MSK
Decision
2025-09-02
FDA-cleared K252953

Velmeni for Dentists (V4D) Endo-Perio

Velmeni, Inc.

Authorized purpose: Concurrent-read CADe to assist dentists in detecting specified tooth and jaw anatomy, bone-level landmarks, and root-canal-treated teeth in digital radiographs of permanent teeth in patients 15 years or older.

Modality
X-ray/Radiography
Anatomy
Permanent teeth and jaw/maxillofacial anatomy, including enamel, dentine, pulp, root, mental foramen, inferior alveolar canal, maxillary sinus, cementoenamel junction, crestal bone, and root-canal-treated teeth
Decision
2026-05-11

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