CT-based preoperative planning for hip surgery, including interactive implant-geometry overlay and generation of a surgeon-reviewable planning report.
Clinical role
Interactive CT-based implant overlay and preoperative hip-surgery planning.
Images and patients
CT/CTA · Hip
Key limitation
The qualified professional remains responsible for the surgical plan and must verify implant data and patient-specific decisions.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Imaging and anatomyCT/CTA · Hip
Workflow roleInteractive CT-based implant overlay and preoperative hip-surgery planning.
Required inputPre-dimensioned patient CT studies imported from PACS or conventional media.
Output and human actionA customizable digital plan using an integrated hip-implant geometry database and a printable PDF report.
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
CT-based preoperative planning for hip surgery, including interactive implant-geometry overlay and generation of a surgeon-reviewable planning report.
The exact FDA document reports validation of image processing accuracy on 60 images (from 60 patients) in the US, comparing automatically generated femur and hemipelvis 3D models to manual segmentation by US radiologists (average Dice for image segmentation: hemipelvis 0.95, femur 0.97; all acceptance criteria met), and of implant sizing on 133 images (from 133 patients) in Australia against orthopaedic surgeons (stems 94% and cups 98% within 2 sizes). Substantial equivalence was not based on clinical performance data. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "performed on 60 images acquired (from 60 patients) in the US to validate accuracy of image processing by comparing automatically generated 3D models of the femur and hemipelvis to the 3D models generated via manual segmentation by a panel of US radiologists." … "All acceptance criteria were met, as shown in the table below.". 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 validation of image processing accuracy on 60 images (from 60 patients) in the US, comparing automatically generated femur and hemipelvis 3D models to manual segmentation by US radiologists (average Dice for image segmentation: hemipelvis 0.95, femur 0.97; all acceptance criteria met), and of implant sizing on 133 images (from 133 patients) in Australia against orthopaedic surgeons (stems 94% and cups 98% within 2 sizes). Substantial equivalence was not based on clinical performance data. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "performed on 60 images acquired (from 60 patients) in the US to validate accuracy of image processing by comparing automatically generated 3D models of the femur and hemipelvis to the 3D models generated via manual segmentation by a panel of US radiologists." … "All acceptance criteria were met, as shown in the table below.". Read from the exact FDA decision document on 2026-11-14.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
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 K213272. 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: Pre-dimensioned patient CT studies imported from PACS or conventional media.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The cleared application imports imaging from PACS or conventional media and can export the finalized plan as a PDF report.
Scope: Exact FDA submission.
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 Formus Hip as accessed from the Chrome internet browser launched from a standalone PC or workstation with internet access, with Windows with a Chrome browser as its operating system. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Computer Personal computer or workstation Personal computer or workstation Operating System Windows with a Chrome browser Windows or OS X" … "Device Availability Can be accessed from the Chrome It can be set to start from a workstation internet browser launched from a or standalone for planning procedures. standalone PC or workstation with internet access.". 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.
Unresolved route: A customizable digital plan using an integrated hip-implant geometry database and a printable PDF report.
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.
The exact FDA package describes Formus Hip as accessed from the Chrome internet browser launched from a standalone PC or workstation with internet access, with Windows with a Chrome browser as its operating system. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Computer Personal computer or workstation Personal computer or workstation Operating System Windows with a Chrome browser Windows or OS X" … "Device Availability Can be accessed from the Chrome It can be set to start from a workstation internet browser launched from a or standalone for planning procedures. standalone PC or workstation with internet access.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Formus describes the current Hip family as cloud-based, AI-automated three-dimensional preoperative planning for primary total hip arthroplasty from patient CT.
product family · checked 2026-09-08
Confirm exact-release availability, interfaces, hosting, security, support, and commercial terms during procurement.
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-08Last searched
16Fields reviewed
9Source classes checked
0Awaiting review PubMed leads
0Awaiting review trial leads
0Unreviewed FDA recall leads
Recovered from the prior exact-submission extraction and normalized under the current provenance rules. Exact FDA scope controls clinical claims. ACR and official vendor material provide bounded catalog or product-family context. Candidate literature metadata remains a discovery queue until full-text identity, endpoint, population, and version review is completed. Automated exact-name discovery found 0 PubMed and 0 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, vendor product page, 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 verified - checked 2026-09-08 - Exact FDA submission
No public price or quote for the exact K213272 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-08 - 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-08 - 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-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Enhanced Boundary for PCCT is a deep-learning CT processing function for improved soft-tissue delineation in routine head examinations with or without contrast.
Authorized purpose: Fibresolve analyzes lung CT in patients with pulmonary symptoms to provide an adjunct diagnostic-subtype classification for suspected interstitial lung disease and support referral to a multidisciplinary discussion.
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.