Authorized purpose: Assist hospital networks and appropriately trained medical specialists in triaging adults aged 22 years and older by flagging suspected aortic dissection or aortic intramural hematoma on chest or chest-abdomen CTA.
Clinical role
Notification-only parallel triage and worklist prioritization; the device flags cases for earlier review without marking a location or replacing clinical assessment.
Images and patients
CT/CTA · Chest, abdomen, and thoracoabdominal aorta
Key limitation
Keep in mind: The output is for worklist prioritization or triage, not standalone clinical decision-making. It is not intended to rule out acute aortic syndrome or preclude clinical assessment of CTA cases, and it does not provide lesion marking or location-specific guidance.
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: Assist hospital networks and appropriately trained medical specialists in triaging adults aged 22 years and older by flagging suspected aortic dissection or aortic intramural hematoma on chest or chest-abdomen CTA.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest, abdomen, and thoracoabdominal aorta Input: DICOM chest or chest-abdomen CTA studies from adults aged 22 years and older; the FDA validation set included 380 CTA studies with 156 positive and 224 negative cases.
Who uses it?Intended users: Hospital networks and appropriately trained medical specialists
What does the software produce?Output: Case-level passive notification or flag to a PACS/workstation indicating suspected aortic dissection or aortic intramural hematoma; the device does not mark, highlight, or direct attention to a specific image location.
What is its most important limitation?Key limitation: The output is for worklist prioritization or triage, not standalone clinical decision-making. It is not intended to rule out acute aortic syndrome or preclude clinical assessment of CTA cases, and it does not provide lesion marking or location-specific guidance.
Clinical takeaway. Clinical role: Assist hospital networks and appropriately trained medical specialists in triaging adults aged 22 years and older by flagging suspected aortic dissection or aortic intramural hematoma on chest or chest-abdomen CTA.
Evidence takeaway. Evidence from the reviewed source record: FDA K240291 reports a retrospective, blinded, multisite validation of 380 consecutively collected US CTA studies, including 156 positives and 224 negatives, independent of model development and analytical validation. Three US board-certified radiologists established ground truth by majority agreement. Sensitivity was 0.929 (95% CI 0.878-0.960) and specificity was 0.915 (95% CI 0.871-0.945). The secondary system-processing endpoint was 37.86 seconds per study (95% CI 35.22-40.50).
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
Assist hospital networks and appropriately trained medical specialists in triaging adults aged 22 years and older by flagging suspected aortic dissection or aortic intramural hematoma on chest or chest-abdomen CTA.
Notification-only parallel triage and worklist prioritization; the device flags cases for earlier review without marking a location or replacing clinical assessment.
DICOM chest or chest-abdomen CTA studies from adults aged 22 years and older; the FDA validation set included 380 CTA studies with 156 positive and 224 negative cases.
Case-level passive notification or flag to a PACS/workstation indicating suspected aortic dissection or aortic intramural hematoma; the device does not mark, highlight, or direct attention to a specific image location.
The output is for worklist prioritization or triage, not standalone clinical decision-making. It is not intended to rule out acute aortic syndrome or preclude clinical assessment of CTA cases, and it does not provide lesion marking or location-specific guidance.
FDA K240291 reports a retrospective, blinded, multisite validation of 380 consecutively collected US CTA studies, including 156 positives and 224 negatives, independent of model development and analytical validation. Three US board-certified radiologists established ground truth by majority agreement. Sensitivity was 0.929 (95% CI 0.878-0.960) and specificity was 0.915 (95% CI 0.871-0.945). The secondary system-processing endpoint was 37.86 seconds per study (95% CI 35.22-40.50).
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 K240291 reports a retrospective, blinded, multisite validation of 380 consecutively collected US CTA studies, including 156 positives and 224 negatives, independent of model development and analytical validation. Three US board-certified radiologists established ground truth by majority agreement. Sensitivity was 0.929 (95% CI 0.878-0.960) and specificity was 0.915 (95% CI 0.871-0.945). The secondary system-processing endpoint was 37.86 seconds per study (95% CI 35.22-40.50).
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
EFAI CARDIOSUITE CTA ACUTE AORTIC SYNDROME ASSESSMENT SYSTEM regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K240291
Samplen=380
IndependenceIndependence not established
K240291
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
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 K240291. 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: DICOM chest or chest-abdomen CTA studies from adults aged 22 years and older; the FDA validation set included 380 CTA studies with 156 positive and 224 negative cases.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The packet describes DICOM input and passive output to a PACS/RIS workstation for worklist prioritization or triage. Specific interface versions, current deployment, and local compatibility are not established.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision document was reviewed on 2026-11-14 and does not state where the subject device's software runs or how it is hosted. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-11-14 ·
Returned objects
Source context, not route validation: Case-level passive notification or flag to a PACS/workstation indicating suspected aortic dissection or aortic intramural hematoma; the device does not mark, highlight, or direct attention to a specific image location.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Case-level passive notification or flag to a PACS/workstation indicating suspected aortic dissection or aortic intramural hematoma; the device does not mark, highlight, or direct attention to a specific image location.
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 packet describes DICOM input and passive output to a PACS/RIS workstation for worklist prioritization or triage. Specific interface versions, current deployment, and local compatibility are not established.
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.
ACR AI Central provides an exact-submission model card for EFAI CARDIOSUITE CTA ACUTE AORTIC SYNDROME ASSESSMENT SYSTEM; FDA labeling remains controlling for clinical use, limitations, and performance.
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
24Fields 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 K240291 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.
Deployment: Not publicly available - checked 2026-11-14 - Exact FDA submission
The exact FDA decision document was reviewed on 2026-11-14 and does not state where the subject device's software runs or how it is hosted. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor.
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-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.