Authorized purpose: EFAI HCAPSeg assists trained radiation-oncology professionals with radiation-treatment planning by providing initial deep-learning contours of organs at risk on non-contrast CT images for transfer to a DICOM-compliant treatment-planning system.
Clinical role
Radiation-treatment planning, image registration, contouring, dose calculation, or plan review support under qualified professional control.
Images and patients
Radiotherapy Planning Imaging · Adult organs at risk on non-contrast CT during radiation-treatment planning
Key limitation
Keep in mind: Automated contours, plans, registrations, dose values, or other outputs require qualified review, editing, commissioning, and local validation before clinical use.
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: EFAI HCAPSeg assists trained radiation-oncology professionals with radiation-treatment planning by providing initial deep-learning contours of organs at risk on non-contrast CT images for transfer to a DICOM-compliant treatment-planning system.
Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: Adult organs at risk on non-contrast CT during radiation-treatment planning Input: Supported CT, MR, PET, or other DICOM image data, structures, prescriptions, and treatment-planning inputs within the exact submission.
Who uses it?Intended users: Radiation oncologists, medical physicists, dosimetrists, and other trained radiation-treatment professionals.
What does the software produce?Output: Contours, registered images, dose distributions, plans, measurements, or exported treatment-planning objects for professional review and approval.
What is its most important limitation?Key limitation: Automated contours, plans, registrations, dose values, or other outputs require qualified review, editing, commissioning, and local validation before clinical use.
Clinical takeaway. Clinical role: EFAI HCAPSeg assists trained radiation-oncology professionals with radiation-treatment planning by providing initial deep-learning contours of organs at risk on non-contrast CT images for transfer to a DICOM-compliant treatment-planning system.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports a standalone evaluation on 157 non-contrast U.S. CT cases independent of development training and internal testing, with ground truth from three board-certified radiation oncologists. Overall mean DSC was 0.83; non-inferiority tests against a comparison device met the primary endpoint, with mean DSC 0.80, 0.90, and 0.90 in Head & Neck, Chest, and Abdomen & Pelvis. OARs unique to the device, tested for superiority to a pre-specified value, had mean DSC 0.82. 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
EFAI HCAPSeg assists trained radiation-oncology professionals with radiation-treatment planning by providing initial deep-learning contours of organs at risk on non-contrast CT images for transfer to a DICOM-compliant treatment-planning system.
Automated contours, plans, registrations, dose values, or other outputs require qualified review, editing, commissioning, and local validation before clinical use.
The exact FDA document reports a standalone evaluation on 157 non-contrast U.S. CT cases independent of development training and internal testing, with ground truth from three board-certified radiation oncologists. Overall mean DSC was 0.83; non-inferiority tests against a comparison device met the primary endpoint, with mean DSC 0.80, 0.90, and 0.90 in Head & Neck, Chest, and Abdomen & Pelvis. OARs unique to the device, tested for superiority to a pre-specified value, had mean DSC 0.82. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The dataset used in this study comprised 157 non-contrast CT cases consecutively collected from the United States (U.S.), all meeting the established inclusion criteria. All data used during the standalone performance evaluation was acquired independently from product development training and internal testing." … "Each of the OAR contouring was generated by three board-certified radiation oncologists as the ground truth (GT).". 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 a standalone evaluation on 157 non-contrast U.S. CT cases independent of development training and internal testing, with ground truth from three board-certified radiation oncologists. Overall mean DSC was 0.83; non-inferiority tests against a comparison device met the primary endpoint, with mean DSC 0.80, 0.90, and 0.90 in Head & Neck, Chest, and Abdomen & Pelvis. OARs unique to the device, tested for superiority to a pre-specified value, had mean DSC 0.82. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "The dataset used in this study comprised 157 non-contrast CT cases consecutively collected from the United States (U.S.), all meeting the established inclusion criteria. All data used during the standalone performance evaluation was acquired independently from product development training and internal testing." … "Each of the OAR contouring was generated by three board-certified radiation oncologists as the ground truth (GT).". 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 K231928
DesignFDA 510(k) regulatory decision material and submission-specific verification or validation evidence for K231928; 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 K231928; a broader clinical population is not established here.
Scopeexact submission
Tested versionEFAI RTSUITE CT HCAP-Segmentation System (K231928)
IndependenceSponsor or vendor study
K231928
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: Supported CT, MR, PET, or other DICOM image data, structures, prescriptions, and treatment-planning inputs within the exact submission.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes DICOM-format CT image input and organ-at-risk contours output in DICOM format as RTSTRUCT, used with a DICOM-compliant treatment planning system to review and edit results. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "The device receives CT images in DICOM format as input and automatically generates the contours of OARs, which are stored in DICOM format and in RTSTRUCT modality." … "must be used in conjunction with a DICOM-compliant treatment planning system to review and edit results.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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 EFAI HCAPSeg as installed on a specialized server supporting deep learning processing, with a recommended deployment environment in a local network with an existing hospital-grade IT system. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The deployment environment is recommended to be in a local network with an existing hospital-grade IT system in place." … "EFAI HCAPSeg should be installed on a specialized server supporting deep learning processing.". 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.
Source context, not route validation: Contours, registered images, dose distributions, plans, measurements, or exported treatment-planning objects for professional review and approval.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Contours, registered images, dose distributions, plans, measurements, or exported treatment-planning objects for professional review and approval.
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 EFAI HCAPSeg as installed on a specialized server supporting deep learning processing, with a recommended deployment environment in a local network with an existing hospital-grade IT system. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The deployment environment is recommended to be in a local network with an existing hospital-grade IT system in place." … "EFAI HCAPSeg should be installed on a specialized server supporting deep learning processing.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes DICOM-format CT image input and organ-at-risk contours output in DICOM format as RTSTRUCT, used with a DICOM-compliant treatment planning system to review and edit results. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The device receives CT images in DICOM format as input and automatically generates the contours of OARs, which are stored in DICOM format and in RTSTRUCT modality." … "must be used in conjunction with a DICOM-compliant treatment planning system to review and edit results.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Ever Fortune.AI's investor information-security policy page states an implemented information security management system covering confidentiality, integrity, and availability, with security training and measurement targets; the page states the company has completed ISO 27001 certification and holds ISO/IEC 27701 PII-processor certification after independent third-party audit. The company's certification-milestones page lists ISO/IEC 27001:2022, ISO 22301:2019, ISO/IEC 27018:2019, and ISO/IEC 27017:2015.
Vendor-wide
Checked 2026-10-27
Vendor statement; certificates were not read. Applicant name variants (including uppercase and punctuation variants of Ever Fortune.AI Co., Ltd.) are bridged via the vendor's EFAI product naming and the owning domain everfortuneai.com.tw. Exact-release scope is not established.
Current vendor material is product-family context for K231928 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.
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
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: DeepBT Detector-Plus provides initial gross-tumor-volume contours on T1-weighted contrast-enhanced and optional T2-weighted MR images for radiation-treatment planning in adults with the labeled brain tumors.
Modality
Radiotherapy Planning Imaging
Anatomy
Brain tumors, including metastases, meningiomas, and acoustic neuromas
Authorized purpose: syngo.via RT Image Suite VC10 provides three-dimensional and four-dimensional multimodality visualization, registration, fusion, contouring, and planning support for radiation-treatment preparation.
Modality
Radiotherapy Planning Imaging
Anatomy
Brain, pelvis, thorax, abdomen, targets, organs at risk, and moving tumors or organs
Authorized purpose: The EMLA family delivers external-beam radiation therapy for adult and pediatric patients with benign, malignant, or metastatic disease. Authorized techniques vary by model: Synergy and Harmony include conventional and fractionated delivery; Infinity and Harmony Pro add SBRT/SABR; Versa HD and Evo also support SRS and specified functional disorders.
Authorized purpose: TAIMedImg DeepMets assists trained professionals by providing initial gross-tumor-volume contours on axial contrast-enhanced T1 brain MR images for radiation-treatment planning in adults with known brain metastases; the contours require thorough review and are not a replacement for manual contouring.
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.