Sensitivity
86.1 percent
- EndpointAcute-infarct triage sensitivity at operating point 0.091176
- PopulationThin-slice non-contrast brain CT cohort
- Tested versionAnnalise Enterprise submitted in K253818; build not stated
FDA-cleared profile
Harrison-AI Medical Pty, Ltd. · CT/CTA · FDA-cleared (510(k))
Authorized purpose: Annalise Enterprise prioritizes and notifies trained CT clinicians of suspected acute infarct on non-contrast brain CT for adults; it is a study-level, non-localizing worklist aid and never downgrades an existing priority.
Overview status: Source-reviewed overview
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
Clinical takeaway. Clinical role: Annalise Enterprise prioritizes and notifies trained CT clinicians of suspected acute infarct on non-contrast brain CT for adults; it is a study-level, non-localizing worklist aid and never downgrades an existing priority.
Evidence takeaway. Evidence from the reviewed source record: A retrospective study used consecutive cases from five U.S. hospital networks, with separate thin- and thick-slice cohorts and expert reference standards.
Evidence context not reviewed for this FDA record.
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.
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.
86.1 percent
91.4 percent
K253818
Reference standard used two expert readers with third-reader adjudication; advanced imaging was available. Metrics above are thin-slice only.
Safety and lifecycle
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
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.
Price not public here; enter your quote
Not verified: Pricing information is recorded but not verified against a resolving source.
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.
Source context, not route validation: Non-contrast axial brain CT with brain reconstruction kernel, slice thickness up to 5 mm, and up to 1,000 images.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Field checked 2026-09-05 · FDA 510(k) K253818: Annalise Enterprise
Source context, not route validation: FDA labeling describes integration with PACS, RIS, or an order system for worklist notification.
Scope: Exact FDA submission. Named platform examples do not establish a local compatibility commitment.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-05 · FDA 510(k) K253818: Annalise Enterprise
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. Current hosting model was not established in the reviewed material.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-05 ·
Source context, not route validation: Study-level notification for suspected acute infarct; no localizing output and no output that excludes infarct.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Field checked 2026-09-05 · FDA 510(k) K253818: Annalise Enterprise
Unresolved route: Study-level notification for suspected acute infarct; no localizing output and no output that excludes infarct.
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-05 · FDA 510(k) K253818: Annalise Enterprise
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
No tests below have been performed or accepted.
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
Named platform examples do not establish a local compatibility commitment.
Vendor statements. Entity bridge: the Harrison.ai privacy notice names 'Harrison-AI Medical Pty Ltd ABN 92 635 645 260' as a group entity, bridging the FDA applicant. The Harrison.ai Trust Centre rendered no readable content on 2026-10-26, so no certification claims were applied. Exact-release scope is not established.
Harrison.ai describes a broader CT-brain suite and an acute-infarct triage clearance announcement.
product family · checked 2026-09-05Broader suite finding counts and workflows are not assumed for this exact acute-infarct configuration.
Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
No stored PubMed or ClinicalTrials candidates. Native-submission recall candidate snapshot was zero. 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, acr ai central product, fda decision material, vendor product page, literature index, trial registry, fda device recall, pubmed, clinical trials, openfda device recall
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.
No scoped public price or procurement award was reviewed.
Bounded web search on 2026-10-26 (query: "Annalise Enterprise CT reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. Harrison.ai's NTAP announcement concerns Annalise Obstructive Hydrocephalus, not this entry. This records what was found, not that none exists.
Current hosting model was not established in the reviewed material.
Current training/support commitments were not established.
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
8 sources - 3 history items
Scope: identity, clinicalUse, modality, anatomy, input, output, limitations, integration, evidenceSummary, evidenceMetrics
Scope: regulatoryIdentity, modalityContext
Scope: intendedUsers, careSetting, output, reportedSensitivity, reportedSpecificity, evidenceSummary, anatomy, evidenceStudies
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: productFamilyWorkflow, implementationCapabilities
Scope: security
Regulatory record
510(k)
Research record
human reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
Aidoc Medical, Ltd.
Authorized purpose: Adult contrast-enhanced brain CT triage for suspected brain aneurysm findings at least 3.0 mm.
Methinks Software S.L.
Authorized purpose: Methinks CTA Stroke analyzes acute-setting brain CT angiography in adults over 21 with suspected stroke for suspected large-vessel occlusion in the terminal ICA, MCA-M1, or MCA-M2 and sends PACS and/or specialist notifications in parallel to standard care; previews are informational and not diagnostic.
iSchemaView
Authorized purpose: Rapid CTA 360 analyzes adult head CTA DICOM images to flag suspected large- and medium-vessel occlusion in specified intracranial and vertebral segments and notify trained clinicians for workflow triage; notifications are informational and not diagnostic.
Methinks Software S.L.
Authorized purpose: Methinks NCCT Stroke analyzes adult non-contrast head CT to flag suspected intracranial hemorrhage and suspected large-vessel occlusion of the ICA, MCA-M1, or MCA-M2 for parallel workflow triage via PACS and/or notifications; previews are informational, not diagnostic, and a negative notification does not rule out LVO or replace CTA/standard care.
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 destinationPermission 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.
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