Authorized purpose: EFAI RTSuite CT HN-Segmentation System automatically delineates head-and-neck organs at risk on adult non-contrast CT images to support radiation-treatment workflows; initial contours are transferred to a DICOM-compliant treatment-planning system for professional review and editing.
Clinical role
Radiotherapy contouring, treatment planning, adaptation, or treatment-session support under professional review.
Images and patients
Radiotherapy Planning Imaging · Head and neck organs at risk
Key limitation
Keep in mind: Initial head-and-neck organ-at-risk contours require professional review and editing; the labeled system is not a decision-making or lesion-detection system.
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 RTSuite CT HN-Segmentation System automatically delineates head-and-neck organs at risk on adult non-contrast CT images to support radiation-treatment workflows; initial contours are transferred to a DICOM-compliant treatment-planning system for professional review and editing.
Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: Head and neck organs at risk Input: Supported CT or MR images, structures, prescriptions, plans, registrations, and treatment-session data.
Who uses it?Intended users: Qualified radiation oncologists, medical physicists, dosimetrists, and radiation therapists.
What does the software produce?Output: Contours, treatment plans, adapted plans, dose or evaluation results, or session information requiring review and approval.
What is its most important limitation?Key limitation: Initial head-and-neck organ-at-risk contours require professional review and editing; the labeled system is not a decision-making or lesion-detection system.
Clinical takeaway. Clinical role: EFAI RTSuite CT HN-Segmentation System automatically delineates head-and-neck organs at risk on adult non-contrast CT images to support radiation-treatment workflows; initial contours are transferred to a DICOM-compliant treatment-planning system for professional review and editing.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification and validation testing and a non-inferiority standalone performance test comparing the mean Dice coefficient of automatically generated head and neck OAR contours with that of the predicate device; it states the device was non-inferior to the predicate by at least a non-inferiority limit of 0.1 Dice, described as the largest clinically acceptable difference based on previous studies. No measured Dice values or test dataset size are given. 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 RTSuite CT HN-Segmentation System automatically delineates head-and-neck organs at risk on adult non-contrast CT images to support radiation-treatment workflows; initial contours are transferred to a DICOM-compliant treatment-planning system for professional review and editing.
Initial head-and-neck organ-at-risk contours require professional review and editing; the labeled system is not a decision-making or lesion-detection system.
The exact FDA document reports software verification and validation testing and a non-inferiority standalone performance test comparing the mean Dice coefficient of automatically generated head and neck OAR contours with that of the predicate device; it states the device was non-inferior to the predicate by at least a non-inferiority limit of 0.1 Dice, described as the largest clinically acceptable difference based on previous studies. No measured Dice values or test dataset size are given. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Performance of the EFAI HNSeg v1.0 has been evaluated and verified in accordance with software specifications and applicable performance standards through software verification and validation testing." … "To establish the contour performance of EFAI HNSeg, a non-inferiority standalone performance test was performed. This non-inferiority test compared the mean Dice coefficient of the automatically generated head and neck OAR contours for EFAI HNSeg against that of the predicate device". 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 software verification and validation testing and a non-inferiority standalone performance test comparing the mean Dice coefficient of automatically generated head and neck OAR contours with that of the predicate device; it states the device was non-inferior to the predicate by at least a non-inferiority limit of 0.1 Dice, described as the largest clinically acceptable difference based on previous studies. No measured Dice values or test dataset size are given. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Performance of the EFAI HNSeg v1.0 has been evaluated and verified in accordance with software specifications and applicable performance standards through software verification and validation testing." … "To establish the contour performance of EFAI HNSeg, a non-inferiority standalone performance test was performed. This non-inferiority test compared the mean Dice coefficient of the automatically generated head and neck OAR contours for EFAI HNSeg against that of the predicate device". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint for this device or software function. 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 for this device or software function. 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.
K220264 FDA evidence package for EFAI RTSuite CT HN-Segmentation System
DesignFDA 510(k) substantial-equivalence decision evidence and product verification described in the exact submission.
PopulationHead and neck organs at risk
Scopeexact submission
Tested versionEFAI RTSuite CT HN-Segmentation System configuration described in K220264
IndependenceSponsor or vendor study
K220264
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
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 K220264 by exact native submission identifier. This does not exclude product-family, later, 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 radiation-oncology material. Evaluate net planning or delivery value within the radiotherapy service line.
No separate named-product payment identified in reviewed public material
Centers for Medicare & Medicaid Services · United States
This is not a product-specific reimbursement determination. Build a local total-cost and value model 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: Supported CT or MR images, structures, prescriptions, plans, registrations, and treatment-session data.
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 CT input and DICOM or RTSTRUCT organ-at-risk output to a DICOM-compliant treatment-planning system; verify exact local compatibility.
Scope: Exact FDA submission. This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, and archive 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 exact FDA package describes a specialized server on a local network for the EFAI HN-Segmentation release; verify current topology, service responsibility, and site configuration locally.
Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Contours, treatment plans, adapted plans, dose or evaluation results, or session information requiring 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, treatment plans, adapted plans, dose or evaluation results, or session information requiring 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 a specialized server on a local network for the EFAI HN-Segmentation release; verify current topology, service responsibility, and site configuration locally.
Exact FDA submission
Checked 2026-09-04
This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, and site configuration remain separate evidence.
The exact FDA package describes DICOM CT input and DICOM or RTSTRUCT organ-at-risk output to a DICOM-compliant treatment-planning system; verify exact local compatibility.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, and archive behavior still require acceptance testing.
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.
Only qualified radiation oncologists, medical physicists, dosimetrists, and radiation therapists should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K220264 by exact hardware, software, model, and 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: Initial head-and-neck organ-at-risk contours require professional review and editing; the labeled system is not a decision-making or lesion-detection system.
Exact FDA submission
Checked 2026-09-04
Monitoring guidance is buyer-facing implementation guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
The exact FDA package describes a specialized server on a local network for the EFAI HN-Segmentation release; verify current topology, service responsibility, and site configuration locally.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
The exact FDA package describes DICOM CT input and DICOM or RTSTRUCT organ-at-risk output to a DICOM-compliant treatment-planning system; verify exact local compatibility.
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. Initial head-and-neck organ-at-risk contours require professional review and editing; the labeled system is not a decision-making or lesion-detection system.
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.
Monitor K220264 by exact hardware, software, model, and 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: Initial head-and-neck organ-at-risk contours require professional review and editing; the labeled system is not a decision-making or lesion-detection system.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. radiotherapy planning or image-processing software limits remain submission-specific.
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-20Last searched
27Fields reviewed
12Source 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, 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 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.
Authorized purpose: AccuContour 4.0 uses deep-learning contours to support segmentation of organs at risk on CT images for radiation-treatment planning, evaluation, and adaptation; qualified professionals review and may edit the contours.
Modality
Radiotherapy Planning Imaging
Anatomy
Head and neck, thorax, abdomen, and pelvis organs at risk
Authorized purpose: Contour ProtégéAI+ automatically creates contours on CT and T2 MR DICOM images as an accessory to MIM software for quantitative analysis, adaptive therapy, transfer, and archive; users must review and edit contours, and the device is not intended to detect or contour lesions.
Modality
Radiotherapy Planning Imaging
Anatomy
CT anatomical regions; prostate, seminal vesicles, and urethra on T2 MR
Authorized purpose: DeepContour uses deep-learning CT processing to generate editable organ contours and RTSTRUCT objects for selected adult radiation-treatment planning workflows, with quantitative statistics, registration, and three-dimensional visualization; it does not contour tumors.
Authorized purpose: Contour ProtegeAI assists trained medical professionals with automated processing of CT and MR images, creates machine-learning contours for quantitative analysis, adaptive therapy, transfer to radiation-treatment planning systems, and archiving, segments structures across CT locations, and segments the prostate, seminal vesicles, and urethra on T2-weighted MR images.
Modality
Radiotherapy Planning Imaging
Anatomy
CT anatomic locations and the prostate, seminal vesicles, and urethra on T2-weighted MR
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.