Input or output interoperability
DICOM is explicitly referenced in the described input, output, or workflow.
exact submission · checked 2026-09-01The model card does not establish every supported DICOM object, transfer method, or local interface.
FDA-cleared profile
FractureDetect (FX)
Imagen Technologies, Inc.
Authorized purpose: Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.
Evidence status: each field states its source quality, applicability, and review date. Research pending, information not established, and vendor documentation pending remain distinct outcomes.
Product overview
Start with the essentials
Authorized purpose: Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.
Overview status: Source-reviewed overview
- 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.
Clinical details
What this tool is for
Start with the authorized purpose, then verify how it fits your service line and reading workflow.
- Exact purpose
- Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
- Intended users
- Clinicians.
FDA packet intended-user statement.
- Care setting and population
- Adult
Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.
- Workflow role
- Detection, localization, or diagnostic support
Conservative normalization of explicit wording in an exact-submission source.
- Required input
- Commonly acquired adult radiographs received through a generic DICOM node or PACS.
FDA packet input scope.
- Output and human action
- A toggleable DICOM overlay reading Fracture: DETECTED with bounding boxes or Fracture: NOT DETECTED without boxes.
FDA packet output scope.
- Limitations
- Adults only, limited to listed study types and views, with no patient contact.
Exact FDA limitation boundary.
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.
Implementation
Questions for IT, informatics, and operations
Use these fields to structure a vendor demo, security review, and implementation estimate.
- 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.
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
- Deployment and data flow
- On-premise
Deployment category preserved from the prior exact-submission review; hosting region, data flow, and current commercial configuration still require vendor confirmation.
- Security and privacy
- Vendor documentation pending
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
- Training and support
- Vendor documentation pending
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
- Monitoring and change control
- Vendor documentation pending
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Result destination
PACS is explicitly referenced as a result destination.
exact submission · checked 2026-09-01Confirm supported products, versions, routing behavior, and display requirements during local evaluation.
Supported acquisition environment
Scanner manufacturers: All
exact submission · checked 2026-09-01Confirm 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-09Evidence
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.
Submission-reported performance result.
- Reported sensitivity
- 95% (95% CI: 94%, 96%)
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%)
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.
Costs and setup
Budget and ongoing governance
These are common procurement questions; unknown values remain visible until a source supports them.
- Pricing and total cost
- Vendor documentation pending
No public price or quote for the exact K193417 configuration was established in this review.
- Reimbursement and coding
- Not established in reviewed sources
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
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.
Buyer worksheet
Open questions to take to the vendor
- Verify security and privacy controls: Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
- Verify training: Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
- Verify pricing and total cost: No public price or quote for the exact K193417 configuration was established in this review.
- Verify reimbursement and coding relevance: No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
- Verify local validation and lifecycle monitoring: Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
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
Sources & history
How this profile was documented
Open the ledger for source dates, scope, and research-record updates.
View source ledger and history
Source ledger
-
FDA K193417: FractureDetect (FX)
Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary
-
Artificial Intelligence-Enabled Medical Devices
Scope: regulatoryIdentity, modalityContext
-
FractureDetect (FX) model card (K193417)
Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities
-
PubMed biomedical literature index
Scope: evidenceDiscovery
-
ClinicalTrials.gov study registry
Scope: evidenceDiscovery, studyStatus
-
openFDA Device Recall API
Scope: recallDiscovery, nativeSubmissionMatching
-
openFDA exact recall query for K193417
Scope: postmarketSafety
Research history
-
K193417 FDA decision
Regulatory record
510(k)
-
Source-review record updated
Research record
fda record reviewed
-
Reader overview source-reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
Related tools to compare
FDA-cleared K242171
TechCare Trauma
Milvue
Aids clinicians and radiologists reviewing 2D X-ray radiographs by detecting, localizing, and characterizing fractures across the FDA-listed appendicular, hip/pelvis, clavicle,...
- Modality
- X-ray/Radiography
- Anatomy
- MSK
- Decision
- 2025-01-17
FDA-cleared K240845
Rayvolve
AZmed SAS
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...
- Modality
- X-ray/Radiography
- Anatomy
- MSK
- Decision
- 2024-07-17
FDA-cleared K251408
OsteoSight™ Hip (v1)
Naitive Technologies Ltd
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...
- Modality
- X-ray/Radiography
- Anatomy
- MSK
- Decision
- 2025-09-02
FDA-cleared K252953
Velmeni for Dentists (V4D) Endo-Perio
Velmeni, Inc.
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...
- 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