FDA-cleared profile

FEops HEARTguideTM, FEops HEARTguideTM ALPACA

FEops nv · CT/CTA · FDA-cleared (510(k))

Authorized purpose: Enable visualization and measurement of heart and vessel structures for preprocedural planning and sizing of structural-heart interventions, including LAAO and TAVI; qualified clinicians use the results with clinical history, symptoms, other evaluations, and professional judgment, and the results do not replace implant-device instructions for final device selection or placement.

Clinical role
AI-assisted and human-supervised cardiovascular segmentation, visualization, annotation, and measurement for preprocedural planning and sizing of transcatheter structural-heart interventions; clinicians review and adapt segmentation as needed.
Images and patients
CT/CTA · Heart and cardiovascular vessels, including the left atrium, left atrial appendage, aortic root/ascending aorta, and left ventricle
Key limitation
Keep in mind: The results are for preprocedural planning and sizing and do not replace implant-device instructions for final LAAO or TAVI selection and placement. The subject device lacks the predicate's post-intervention evaluation and coronary-calcification/diagnostic functions. Segmentation is followed by human supervision and quality checking, and the TAVI perimeter-based annulus diameter is not automatically calculated; manual action is required. The service-based cloud workflow's current data flow and security configuration are not established.

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: Enable visualization and measurement of heart and vessel structures for preprocedural planning and sizing of structural-heart interventions, including LAAO and TAVI; qualified clinicians use the results with clinical history, symptoms, other evaluations, and professional judgment, and the results do not replace implant-device instructions for final device selection or placement.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Heart and cardiovascular vessels, including the left atrium, left atrial appendage, aortic root/ascending aorta, and left ventricle Input: CT data in DICOM format of the heart and vessels for patients undergoing preprocedural planning for structural-heart interventions, including LAAO and TAVI; the exact acquisition protocol is not specified in the FDA packet.
  • Who uses it?Intended users: Qualified clinicians, including cardiologists, radiologists, and clinical specialists
  • What does the software produce?Output: Cardiovascular segmentations, 2D review and MPR, interactive 3D visualizations, landmarks, measurements and annotations, PDF reports, and DICOM MPR visualizations. LAAO output includes mean landing-zone diameter measurements; TAVI output includes a perimeter-based aortic-annulus diameter that requires a manual measurement action. The application can also display output from FEops HEARTguide Simulation Application K214066.
  • What is its most important limitation?Key limitation: The results are for preprocedural planning and sizing and do not replace implant-device instructions for final LAAO or TAVI selection and placement. The subject device lacks the predicate's post-intervention evaluation and coronary-calcification/diagnostic functions. Segmentation is followed by human supervision and quality checking, and the TAVI perimeter-based annulus diameter is not automatically calculated; manual action is required. The service-based cloud workflow's current data flow and security configuration are not established.

Clinical takeaway. Clinical role: Enable visualization and measurement of heart and vessel structures for preprocedural planning and sizing of structural-heart interventions, including LAAO and TAVI; qualified clinicians use the results with clinical history, symptoms, other evaluations, and professional judgment, and the results do not replace implant-device instructions for final device selection or placement.

Evidence takeaway. Evidence from the reviewed source record: FDA K223855 reports separate retrospective 35-case studies for LAAO and TAVI with no training-data overlap. For LAAO, semi-automatic landing-zone diameter mean difference was 1.4% +/- 4.6% with limits of agreement -7.7% to 10.4% and confidence limits within the prespecified +/-18% goal; semi-automatic LAA-region Dice was 0.98 +/- 0.01. For TAVI, semi-automatic annulus diameter mean difference was 0.5% +/- 1.9% with limits of agreement -3.2% to 4.2% and confidence limits within the prespecified +/-10% goal; semi-automatic aortic-root Dice was 0.97 +/- 0.01. Fully automatic LAAO and TAVI segmentation Dice values were also reported separately, 0.93 +/- 0.04 and 0.96 +/- 0.01 respectively.

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
Enable visualization and measurement of heart and vessel structures for preprocedural planning and sizing of structural-heart interventions, including LAAO and TAVI; qualified clinicians use the results with clinical history, symptoms, other evaluations, and professional judgment, and the results do not replace implant-device instructions for final device selection or placement.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
AI-assisted and human-supervised cardiovascular segmentation, visualization, annotation, and measurement for preprocedural planning and sizing of transcatheter structural-heart interventions; clinicians review and adapt segmentation as needed.
  • Exact FDA submission
  • Checked 2026-09-08
Required input
CT data in DICOM format of the heart and vessels for patients undergoing preprocedural planning for structural-heart interventions, including LAAO and TAVI; the exact acquisition protocol is not specified in the FDA packet.
  • Exact FDA submission
  • Checked 2026-09-08
Output and clinician action
Cardiovascular segmentations, 2D review and MPR, interactive 3D visualizations, landmarks, measurements and annotations, PDF reports, and DICOM MPR visualizations. LAAO output includes mean landing-zone diameter measurements; TAVI output includes a perimeter-based aortic-annulus diameter that requires a manual measurement action. The application can also display output from FEops HEARTguide Simulation Application K214066.
  • Exact FDA submission
  • Checked 2026-09-08
Care setting
Preprocedural structural-heart intervention workflow; the FDA packet does not specify a facility type
  • Exact FDA submission
  • Checked 2026-09-08
Intended users
Qualified clinicians, including cardiologists, radiologists, and clinical specialists
  • Exact FDA submission
  • Checked 2026-09-08
Limitations
The results are for preprocedural planning and sizing and do not replace implant-device instructions for final LAAO or TAVI selection and placement. The subject device lacks the predicate's post-intervention evaluation and coronary-calcification/diagnostic functions. Segmentation is followed by human supervision and quality checking, and the TAVI perimeter-based annulus diameter is not automatically calculated; manual action is required. The service-based cloud workflow's current data flow and security configuration are not established.
  • Exact FDA submission
  • Checked 2026-09-08
Evidence summary
FDA K223855 reports separate retrospective 35-case studies for LAAO and TAVI with no training-data overlap. For LAAO, semi-automatic landing-zone diameter mean difference was 1.4% +/- 4.6% with limits of agreement -7.7% to 10.4% and confidence limits within the prespecified +/-18% goal; semi-automatic LAA-region Dice was 0.98 +/- 0.01. For TAVI, semi-automatic annulus diameter mean difference was 0.5% +/- 1.9% with limits of agreement -3.2% to 4.2% and confidence limits within the prespecified +/-10% goal; semi-automatic aortic-root Dice was 0.97 +/- 0.01. Fully automatic LAAO and TAVI segmentation Dice values were also reported separately, 0.93 +/- 0.04 and 0.96 +/- 0.01 respectively.
  • Exact FDA submission
  • Checked 2026-09-08

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
FDA K223855 reports separate retrospective 35-case studies for LAAO and TAVI with no training-data overlap. For LAAO, semi-automatic landing-zone diameter mean difference was 1.4% +/- 4.6% with limits of agreement -7.7% to 10.4% and confidence limits within the prespecified +/-18% goal; semi-automatic LAA-region Dice was 0.98 +/- 0.01. For TAVI, semi-automatic annulus diameter mean difference was 0.5% +/- 1.9% with limits of agreement -3.2% to 4.2% and confidence limits within the prespecified +/-10% goal; semi-automatic aortic-root Dice was 0.97 +/- 0.01. Fully automatic LAAO and TAVI segmentation Dice values were also reported separately, 0.93 +/- 0.04 and 0.96 +/- 0.01 respectively.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

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

FEops HEARTguideTM, FEops HEARTguideTM ALPACA regulatory performance study summary

  • DesignStand-Alone Performance
  • PopulationPopulation described in the exact-submission ACR model card
  • Scopeexact submission
  • Tested versionExact product version not reported; regulatory study summarized for FDA submission K223855
  • Samplen=35
  • IndependenceIndependence not established

K223855

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 K223855. 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-08
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: CT data in DICOM format of the heart and vessels for patients undergoing preprocedural planning for structural-heart interventions, including LAAO and TAVI; the exact acquisition protocol is not specified in the FDA packet.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K223855: FEops HEARTguideTM, FEops HEARTguideTM ALPACA

  2. Routing

    Source context, not route validation: The FDA packet describes a service-based cloud workflow, CT DICOM input, a web application, PDF reports, interactive 3D, and DICOM MPR outputs; the customer provides input data and FEops prepares and returns the anatomical analysis. Specific current PACS, RIS, EHR, interfaces, versions, hosting region, and local deployment are not established.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K223855: FEops HEARTguideTM, FEops HEARTguideTM ALPACA

  3. AI processing

    Source context, not route validation: The exact FDA package describes FEops HEARTguide ALPACA as a cloud-based device used in a service-based model in which FEops prepares the anatomical analysis and delivers results to clinicians through its web application. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "Cloud-based Yes No, 3mensio is a Different, while the traditional software subject device is cloud-" … "The software is used in a service-based business model: the customer (clinician) provides the necessary input data, FEops prepares the anatomical analysis, and delivers the results to the customer.". 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 K223855: FEops HEARTguideTM, FEops HEARTguideTM ALPACA

  4. Returned objects

    Source context, not route validation: Cardiovascular segmentations, 2D review and MPR, interactive 3D visualizations, landmarks, measurements and annotations, PDF reports, and DICOM MPR visualizations. LAAO output includes mean landing-zone diameter measurements; TAVI output includes a perimeter-based aortic-annulus diameter that requires a manual measurement action. The application can also display output from FEops HEARTguide Simulation Application K214066.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K223855: FEops HEARTguideTM, FEops HEARTguideTM ALPACA

  5. Viewer/worklist/report

    Unresolved route: Cardiovascular segmentations, 2D review and MPR, interactive 3D visualizations, landmarks, measurements and annotations, PDF reports, and DICOM MPR visualizations. LAAO output includes mean landing-zone diameter measurements; TAVI output includes a perimeter-based aortic-annulus diameter that requires a manual measurement action. The application can also display output from FEops HEARTguide Simulation Application K214066.

    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.

    Field checked 2026-09-08 · FDA K223855: FEops HEARTguideTM, FEops HEARTguideTM ALPACA

  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 FEops HEARTguide ALPACA as a cloud-based device used in a service-based model in which FEops prepares the anatomical analysis and delivers results to clinicians through its web application. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Cloud-based Yes No, 3mensio is a Different, while the traditional software subject device is cloud-" … "The software is used in a service-based business model: the customer (clinician) provides the necessary input data, FEops prepares the anatomical analysis, and delivers the results to the customer.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The FDA packet describes a service-based cloud workflow, CT DICOM input, a web application, PDF reports, interactive 3D, and DICOM MPR outputs; the customer provides input data and FEops prepares and returns the anatomical analysis. Specific current PACS, RIS, EHR, interfaces, versions, hosting region, and local deployment are not established.
  • Exact FDA submission
  • Checked 2026-09-08

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.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for FEops HEARTguideTM, FEops HEARTguideTM ALPACA; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
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
K223855
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Heart and cardiovascular vessels, including the left atrium, left atrial appendage, aortic root/ascending aorta, and left ventricle
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2023-06-06
  • 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
22Fields reviewed
9Source 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, 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 K223855 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.

7 sources - 3 history items

Source ledger

  1. FDA K223855: FEops HEARTguideTM, FEops HEARTguideTM ALPACA

    U.S. Food and Drug Administration - Published 2023-06-06 - Accessed 2026-09-08

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. FEops HEARTguideTM, FEops HEARTguideTM ALPACA model card (K223855)

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

    Scope: intendedUsers, output, 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 K223855

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

    Scope: postmarketSafety

Research history

  1. K223855 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 K252029

AI-CVD

HeartLung Corporation

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.

Modality
CT/CTA
Anatomy
Chest, abdomen, heart, lungs, liver, aorta, pulmonary artery, bone, muscle, and fat
Decision
2025-12-19
FDA-cleared K252217

CT VScore+

Canon Medical Informatics, Inc.

Authorized purpose: CT VScore+ evaluates calcified coronary lesions on ECG-gated, non-contrast cardiac CT in patients aged 30 years or older, automatically generating coronary calcium scores and highlighted calcium segmentation for qualified clinical review.

Modality
CT/CTA
Anatomy
Heart/Cardiovascular
Decision
2025-11-28
FDA-cleared K251027

cvi42 Coronary Plaque Software Application

Circle Cardiovascular Imaging, Inc.

Authorized purpose: cvi42 Coronary Plaque supports qualified professionals with viewing, post-processing, and qualitative and quantitative evaluation of adult cardiac CT DICOM images to assess the presence and extent of coronary plaques and stenoses in CCTA for CAD or suspected CAD.

Modality
CT/CTA
Anatomy
Heart/Cardiovascular
Decision
2025-10-27

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