Authorized purpose: The OFIX MIS App assists healthcare professionals in viewing, storing, and measuring images and planning orthopedic surgeries, including measurements for placement of surgical implants.
Clinical role
Medical-image measurement and orthopedic or surgical planning support.
Images and patients
Radiological images; modality varies or is not specified in FDA list · Patient-specific orthopedic surgical anatomy and implant-placement landmarks
Key limitation
Keep in mind: Clinical judgment and experience remain required; planning outputs are not a substitute for source-image review, examination, or final patient-management decisions.
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: The OFIX MIS App assists healthcare professionals in viewing, storing, and measuring images and planning orthopedic surgeries, including measurements for placement of surgical implants.
Which images or clinical context are in scope?Modality: Radiological images; modality varies or is not specified in FDA list Anatomy or clinical context: Patient-specific orthopedic surgical anatomy and implant-placement landmarks Input: Patient medical images and user measurements or planning inputs within the exact labeled scope.
Who uses it?Intended users: Trained healthcare professionals responsible for orthopedic, surgical, or image-planning decisions.
What does the software produce?Output: Measurements, implant-placement planning views, or multidimensional image displays for professional review.
What is its most important limitation?Key limitation: Clinical judgment and experience remain required; planning outputs are not a substitute for source-image review, examination, or final patient-management decisions.
Clinical takeaway. Clinical role: The OFIX MIS App assists healthcare professionals in viewing, storing, and measuring images and planning orthopedic surgeries, including measurements for placement of surgical implants.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports non-clinical testing only: software verification and validation testing, which demonstrated that the App meets the required specifications, and usability testing in which the App demonstrated accuracy and usability with bench top and simulated use testing. Results are as reported in the FDA submission, not independent validation.
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
The OFIX MIS App assists healthcare professionals in viewing, storing, and measuring images and planning orthopedic surgeries, including measurements for placement of surgical implants.
Clinical judgment and experience remain required; planning outputs are not a substitute for source-image review, examination, or final patient-management decisions.
The exact FDA document reports non-clinical testing only: software verification and validation testing, which demonstrated that the App meets the required specifications, and usability testing in which the App demonstrated accuracy and usability with bench top and simulated use testing. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-Clinical Test Conducted for Determination of Substantial Equivalence" … "Software verification and validation testing were conducted and documentation was provided". Read from the exact FDA decision document on 2026-11-14.
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
The exact FDA document reports non-clinical testing only: software verification and validation testing, which demonstrated that the App meets the required specifications, and usability testing in which the App demonstrated accuracy and usability with bench top and simulated use testing. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-Clinical Test Conducted for Determination of Substantial Equivalence" … "Software verification and validation testing were conducted and documentation was provided". Read from the exact FDA decision document on 2026-11-14.
No exact-submission and version-linked sensitivity endpoint is promoted; candidate or product-family values were not substituted.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact-submission and version-linked specificity endpoint is promoted; candidate or product-family values were not substituted.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
FDA submission-specific verification and validation evidence for K230252
DesignFDA 510(k) regulatory decision material and submission-specific verification or validation evidence for K230252; this is regulatory evidence, not an independent clinical effectiveness study.
PopulationThe labeled population, anatomy, images, and test materials described in the exact FDA decision material for K230252; a broader clinical population is not established here.
Scopeexact submission
Tested versionOFIX MIS App (K230252)
IndependenceSponsor or vendor study
K230252
The exact FDA material is submission-specific and should not be generalized to other versions, enabled options, sites, protocols, or clinical outcomes.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
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: Patient medical images and user measurements or planning inputs within the exact labeled scope.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. Exact FDA evidence does not establish the complete local interface, identity, routing, display, report, fallback, or interoperability behavior for this submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. Exact deployment topology, hosting, network boundaries, PHI flow, retention, update mechanism, and local operational requirements are not established for this submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Measurements, implant-placement planning views, or multidimensional image displays for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Measurements, implant-placement planning views, or multidimensional image displays for professional review.
Scope: Exact FDA submission.
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.
Current vendor material is product-family context for K230252 only; exact release, enabled options, deployment, security, interoperability, pricing, and local workflow require confirmation.
product family · checked 2026-09-04
Vendor material is not exact-release evidence unless that linkage is separately proven.
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
31Fields reviewed
13Source 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, vendor product page, implementation documentation, reimbursement policy, peer reviewed literature, clinical trial registry, fda device recall, literature index, trial registry, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public exact-release price, license fee, subscription, contract, or implementation cost 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 applicable - checked 2026-09-04 - Not applicable
CMS coverage-index context was checked, but no product-specific coverage or reimbursement determination is inferred.
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
Exact deployment topology, hosting, network boundaries, PHI flow, retention, update mechanism, and local operational requirements are not established for this submission.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
Exact FDA evidence does not establish the complete local interface, identity, routing, display, report, fallback, or interoperability behavior for this submission.
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 publicly available - checked 2026-09-04 - Exact FDA submission
Public sources reviewed here do not establish the complete exact-release security posture, including identity, audit, encryption, retention, remote access, vulnerability management, backup, or incident response.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-10-27 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-10-27 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: ADAS 3D supports visualization and analysis of MR and CT images of the heart for individual patients with cardiovascular disease, including patients with myocardial scar from ischemic or non-ischemic heart disease. Qualified professionals may use it for cardiac calculation, quantification, visualization, pre-planning, and electrophysiology procedures; produced data support clinical decision-making and must not be used as irrefutable medical advice or for radiotherapy planning, dose calculation, or treatment delivery.
Modality
Radiological images; modality varies or is not specified in FDA list
Authorized purpose: Cercare Neurosuite with Capillary Function and Oncology Virtual Expert processes CT or MR information to provide perfusion, tissue-blood-volume, diffusion, labeling, and quantification support for adult brain glioma workflows.
Modality
Radiological images; modality varies or is not specified in FDA list
Synapse PACS 7.6.0 provides medical-image management and processing, including measurements, regional segmentation, clinical calculations, structured reports, comparison, fusion, and volume rendering to aid reading, interpretation, reporting, and treatment planning.
Modality
Radiological images; modality varies or is not specified in FDA list
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.