Authorized purpose: Vent Creativity Knee v1.0 (Hermes) assists healthcare professionals in transferring CT imaging into bone segmentation and preoperative orthopedic planning outputs, including proximal tibial and distal or posterior femoral cut-plane planning and diagnostic physical replicas.
Clinical role
Segments knee bones, identifies landmarks, creates 3D representations, and provides initial cut-plane planning views for clinician review.
Images and patients
CT/CTA · Knee/femur/tibia/fibula/patella
Key limitation
Keep in mind: The FDA material states that the output does not provide an individual implant fit and supplies initial cut planes; expert judgment remains required, and physical replicas are for diagnostic orthopedic use within the labeled workflow.
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: Vent Creativity Knee v1.0 (Hermes) assists healthcare professionals in transferring CT imaging into bone segmentation and preoperative orthopedic planning outputs, including proximal tibial and distal or posterior femoral cut-plane planning and diagnostic physical replicas.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Knee/femur/tibia/fibula/patella Input: De-identified DICOM CT scans containing Hounsfield data, with user or system-selected point clouds and landmarks.
Who uses it?Intended users: Orthopedic surgeons and other trained healthcare professionals involved in knee surgical planning.
What does the software produce?Output: Bone models, point clouds, meshes, landmarks, and initial proximal tibial and distal or posterior femoral cut planes for planning and diagnostic physical-replica workflows.
What is its most important limitation?Key limitation: The FDA material states that the output does not provide an individual implant fit and supplies initial cut planes; expert judgment remains required, and physical replicas are for diagnostic orthopedic use within the labeled workflow.
Clinical takeaway. Clinical role: Vent Creativity Knee v1.0 (Hermes) assists healthcare professionals in transferring CT imaging into bone segmentation and preoperative orthopedic planning outputs, including proximal tibial and distal or posterior femoral cut-plane planning and diagnostic physical replicas.
Evidence takeaway. Evidence from the reviewed source record: K241961 FDA material describes a convolutional-neural-network segmentation workflow trained on CT scans from 120 de-identified arthritic patients and verification against predicate segmentation and cut-plane outputs; no clinical outcome performance is established.
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
Vent Creativity Knee v1.0 (Hermes) assists healthcare professionals in transferring CT imaging into bone segmentation and preoperative orthopedic planning outputs, including proximal tibial and distal or posterior femoral cut-plane planning and diagnostic physical replicas.
Bone models, point clouds, meshes, landmarks, and initial proximal tibial and distal or posterior femoral cut planes for planning and diagnostic physical-replica workflows.
The FDA material states that the output does not provide an individual implant fit and supplies initial cut planes; expert judgment remains required, and physical replicas are for diagnostic orthopedic use within the labeled workflow.
K241961 FDA material describes a convolutional-neural-network segmentation workflow trained on CT scans from 120 de-identified arthritic patients and verification against predicate segmentation and cut-plane outputs; no clinical outcome performance is established.
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
K241961 FDA material describes a convolutional-neural-network segmentation workflow trained on CT scans from 120 de-identified arthritic patients and verification against predicate segmentation and cut-plane outputs; no clinical outcome performance is established.
Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, and source if later verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, and source if later verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K241961 FDA evidence package for Vent Creativity Knee v1.0 (Hermes)
DesignFDA 510(k) software verification and validation of knee-bone segmentation and cut-plane planning functions.
PopulationDe-identified arthritic knee CT scans and the supported femur, tibia, fibula, and patella segmentation workflow.
Scopeexact submission
Tested versionVent Creativity Knee v1.0 (Hermes) configuration described in K241961
Samplen=120
IndependenceSponsor or vendor study
K241961
The FDA summary identifies 120 training cases but does not provide a clinical outcome study; implant fit is outside the stated output.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K241961 by exact native submission identifier. This does not exclude product-family, later-version, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
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: De-identified DICOM CT scans containing Hounsfield data, with user or system-selected point clouds and landmarks.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA material describes upload of de-identified DICOM CT to a cloud workflow, processing through an internal server, and a custom OHIF-based interface for reviewing outputs.
Scope: Exact FDA submission. This is the interface boundary described in the exact FDA decision material; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The FDA material describes a cloud-based Python workflow using an encrypted Google Cloud Platform folder and an internal server; current hosting, access, retention, security qualification, and site configuration remain unverified.
Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA decision material; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Bone models, point clouds, meshes, landmarks, and initial proximal tibial and distal or posterior femoral cut planes for planning and diagnostic physical-replica workflows.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Bone models, point clouds, meshes, landmarks, and initial proximal tibial and distal or posterior femoral cut planes for planning and diagnostic physical-replica workflows.
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 FDA material describes a cloud-based Python workflow using an encrypted Google Cloud Platform folder and an internal server; current hosting, access, retention, security qualification, and site configuration remain unverified.
Exact FDA submission
Checked 2026-09-04
This is the release-level boundary described in the exact FDA decision material; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
The FDA material describes upload of de-identified DICOM CT to a cloud workflow, processing through an internal server, and a custom OHIF-based interface for reviewing outputs.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA decision material; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Only Orthopedic surgeons and other trained healthcare professionals involved in knee surgical planning should operate or interpret the product; local onboarding must cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K241961 by exact hardware, software, model, algorithm version, patient population, anatomy, protocol, operator, input quality, output edits or overrides, failed studies, repeat acquisition or rework, downstream impact, downtime, incidents, recalls, and updates. Track these product-specific limits: The FDA material states that the output does not provide an individual implant fit and supplies initial cut planes; expert judgment remains required, and physical replicas are for diagnostic orthopedic use within the labeled workflow.
Exact FDA submission
Checked 2026-09-04
Buyer-facing monitoring guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
The FDA material describes a cloud-based Python workflow using an encrypted Google Cloud Platform folder and an internal server; current hosting, access, retention, security qualification, and site configuration remain unverified.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA material describes upload of de-identified DICOM CT to a cloud workflow, processing through an internal server, and a custom OHIF-based interface for reviewing outputs.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. The FDA material states that the output does not provide an individual implant fit and supplies initial cut planes; expert judgment remains required, and physical replicas are for diagnostic orthopedic use within the labeled workflow.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.
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.
Human reviewedStatus
2026-09-04Last searched
32Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The discovery snapshot contains no PubMed or ClinicalTrials.gov candidates for K241961; 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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 list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
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
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 materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Authorized purpose: Auto-Seg and Spine Auto-Seg accept spine and pelvis CT images and provide three-dimensional segmentation and labels to support spine-surgery planning and assessment by spine surgeons.
Authorized purpose: Acorn 3D Software and Acorn 3DP Model process CT, synthetic CT, and CT angiography for segmentation, visualization, measurement, treatment planning, and three-dimensional printing, including adult and pediatric spine trajectory planning.
Modality
CT/CTA
Anatomy
Spine; craniomaxillofacial; musculoskeletal anatomy; and patient-specific printed models
Authorized purpose: AI-CVD provides automated quantitative CT-derived anatomical and density measurements for clinician review, including calcium scores, cardiac and vascular measurements, lung and liver density, bone mineral density, and muscle/fat composition; it is opportunistic decision support, not diagnostic interpretation or risk prediction.
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.