FDA-cleared profile

qER

Qure.ai Technologies · CT/CTA · FDA-cleared (510(k))

qER is a radiological computer aided triage and notification software indicated for use in the analysis of non-contrast head CT images. The device is intended to assist hospital networks and trained medical specialists in workflow triage by flagging the following suspected positive findings of pathologies in head CT images: intracranial hemorrhage, mass effect, midline shift and cranial fracture. qER uses an artificial intelligence algorithm to analyze images on a Stand-Alone Performance cloud-based application in parallel to the ongoing standard of care image interpretation.

Clinical role
Parallel-workflow triage that automatically processes incoming head CT scans and places a priority flag on the user's worklist for suspected intracranial hemorrhage, mass effect, midline shift or cranial fracture, so users can prioritize scans.
Images and patients
CT/CTA · Brain
Key limitation
Exclusion criteria: Scans with artifacts and missing field of view

Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial 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

  • Imaging and anatomyCT/CTA · Brain
  • Workflow roleParallel-workflow triage that automatically processes incoming head CT scans and places a priority flag on the user's worklist for suspected intracranial hemorrhage, mass effect, midline shift or cranial fracture, so users can prioritize scans.
  • Required inputNon-contrast adult head CT scan DICOM files, which the device processes as incoming CT scans when deployed with a PACS or CT scanner.
  • Output and human actionIntracranial hemorrhage, midline shift, mass effect or cranial fractures

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
qER is a radiological computer aided triage and notification software indicated for use in the analysis of non-contrast head CT images. The device is intended to assist hospital networks and trained medical specialists in workflow triage by flagging the following suspected positive findings of pathologies in head CT images: intracranial hemorrhage, mass effect, midline shift and cranial fracture. qER uses an artificial intelligence algorithm to analyze images on a Stand-Alone Performance cloud-based application in parallel to the ongoing standard of care image interpretation.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Parallel-workflow triage that automatically processes incoming head CT scans and places a priority flag on the user's worklist for suspected intracranial hemorrhage, mass effect, midline shift or cranial fracture, so users can prioritize scans.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The qER device is intended for use in parallel to the standard of care workflow. With the addition of the subject device to the workflow, the user is able to prioritize scans based on a suspected critical abnormality detected and flagged by qER." … "Once deployed in conjunction with a PACS or CT scanner, the device automatically processes incoming CT scans and produces triage results that appear on the user’s worklist as a priority flag.". Read from the exact FDA decision document on 2026-11-14.

Required input
Non-contrast adult head CT scan DICOM files, which the device processes as incoming CT scans when deployed with a PACS or CT scanner.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "qER accepts non-contrast adult head CT scan DICOM files as input and provides a priority flag indicating critical scans." … "Once deployed in conjunction with a PACS or CT scanner, the device automatically processes incoming CT scans". Read from the exact FDA decision document on 2026-11-14.

Output and clinician action
Intracranial hemorrhage, midline shift, mass effect or cranial fractures
  • Exact FDA submission
  • Checked 2026-09-01

Clinical output reported in the exact-submission ACR model card.

Care setting
Adult
  • Exact FDA submission
  • Checked 2026-09-01

Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.

Intended users
trained medical specialists
  • Exact FDA submission
  • Checked 2026-09-01

Intended-user text reported in the exact-submission ACR model card.

Limitations
Exclusion criteria: Scans with artifacts and missing field of view
  • Exact FDA submission
  • Checked 2026-09-01

Limitations and supported-acquisition details reported in the exact-submission ACR model card.

Evidence summary
Study type: Stand-Alone Performance. Cases: 1320. Reference standard: Interpretation by Reviewing Clinician. Reported sensitivity: ICH: 96.98%, Skull Fracture: 96.77%, Mass Effect: 96.39%, Midline Shift: 97.34%. Reported specificity: ICH: 93.92%, Skull Fracture: 92.72%, Mass Effect: 96.00%, Midline Shift: 95.36%
  • Exact FDA submission
  • Checked 2026-09-01

Structured study metadata from the exact-submission ACR model card; this is not an independent evidence synthesis.

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
Study type: Stand-Alone Performance. Cases: 1320. Reference standard: Interpretation by Reviewing Clinician. Reported sensitivity: ICH: 96.98%, Skull Fracture: 96.77%, Mass Effect: 96.39%, Midline Shift: 97.34%. Reported specificity: ICH: 93.92%, Skull Fracture: 92.72%, Mass Effect: 96.00%, Midline Shift: 95.36%
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Structured study metadata from the exact-submission ACR model card; this is not an independent evidence synthesis.

Reported sensitivity
ICH: 96.98%, Skull Fracture: 96.77%, Mass Effect: 96.39%, Midline Shift: 97.34%
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model sensitivity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

Reported specificity
ICH: 93.92%, Skull Fracture: 92.72%, Mass Effect: 96.00%, Midline Shift: 95.36%
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model specificity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

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

qER regulatory performance study summary

  • DesignStand-Alone Performance
  • PopulationAdult
  • Scopeexact submission
  • Tested version1.0
  • Samplen=1320
  • IndependenceIndependence not established

K200921

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 K200921. 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: Non-contrast adult head CT scan DICOM files, which the device processes as incoming CT scans when deployed with a PACS or CT scanner.

    Scope: Exact FDA submission. Packet wording: "qER accepts non-contrast adult head CT scan DICOM files as input and provides a priority flag indicating critical scans." … "Once deployed in conjunction with a PACS or CT scanner, the device automatically processes incoming CT scans". Read from the exact FDA decision document on 2026-11-14.

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

    Field checked 2026-11-14 · FDA K200921: qER

  2. Routing

    Source context, not route validation: The exact FDA package describes qER accepting non-contrast adult head CT DICOM files as input, a configurable gateway interfacing with client systems such as the PACS and worklist, notifications sent to the worklist, and non-diagnostic preview images returned to the PACS. Interface versions and local compatibility require confirmation.

    Scope: Exact FDA submission. Packet wording: "qER accepts non-contrast adult head CT scan DICOM files as input and provides a priority flag indicating critical scans." … "a configurable gateway as an interface with the client systems such as the PACS and worklist". 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.

    Field checked 2026-11-14 · FDA K200921: qER

  3. AI processing

    Source context, not route validation: Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-01 · qER model card (K200921)

  4. Returned objects

    Source context, not route validation: Intracranial hemorrhage, midline shift, mass effect or cranial fractures

    Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.

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

    Field checked 2026-09-01 · qER model card (K200921)

  5. Viewer/worklist/report

    Unresolved route: Intracranial hemorrhage, midline shift, mass effect or cranial fractures

    Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.

    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-01 · qER model card (K200921)

  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
Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-09-01

Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.

Integration
The exact FDA package describes qER accepting non-contrast adult head CT DICOM files as input, a configurable gateway interfacing with client systems such as the PACS and worklist, notifications sent to the worklist, and non-diagnostic preview images returned to the PACS. Interface versions and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "qER accepts non-contrast adult head CT scan DICOM files as input and provides a priority flag indicating critical scans." … "a configurable gateway as an interface with the client systems such as the PACS and worklist". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Security
Qure.ai's documentation FAQ says data is sent over HTTPS (TLS 1.2 or higher), stored encrypted at rest with AES-256-GCM, backed up with restore tests twice a year, and that Qure maintains an ISO 27001 certification with periodic surveillance audits. It also says hospitals anonymize PHI before sending data. The certificate itself was not read and no date or scope is given.
  • Vendor-wide
  • Checked 2026-10-25

Vendor-wide statement, not an independent attestation. It does not establish certificate or report scope for this exact release, expiry, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.

Monitoring
Qure.ai's vulnerability disclosure programme states that it covers all Qure.ai commercial products, including cloud-hosted products and Qure.ai-operated infrastructure, and commits to handling every report promptly and transparently with an acknowledgement and tracking reference within 2 business days.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement, not an attestation. The page names Qure.ai generally and does not scope these commitments to any specific product release; exact-release scope is not established. The programme is an intake and response-handling commitment; it makes no uptime, drift or continuous-monitoring claims.

Deployment model

Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.

exact submission · checked 2026-09-01

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for qER; 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
K200921
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Brain
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-06-17
  • 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-08Last searched
25Fields reviewed
10Source classes checked
20Awaiting review PubMed leads
2Awaiting review trial leads
0Unreviewed FDA recall leads

Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA scope controls clinical claims. ACR and official vendor material provide bounded catalog or product-family context. Candidate literature metadata remains a discovery queue until full-text identity, endpoint, population, and version review is completed. Automated exact-name discovery found 20 PubMed and 2 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.

Candidate leads remain unpublished until a human confirms the exact product and tested version.

Source classes: fda ai list, fda decision summary, acr ai central product, vendor documentation, 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 K200921 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
  • 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.

9 sources - 2 history items

Source ledger

  1. FDA K200921: qER

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

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

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. qER model card (K200921)

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

    Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, deployment, 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 K200921

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

    Scope: postmarketSafety

  8. Qure.ai Documentation: Security and Privacy FAQ

    Qure.Ai Technologies - Accessed 2026-10-25

    Scope: security

  9. Qure.ai Vulnerability Disclosure Programme

    Qure.ai - Accessed 2026-10-27

    Scope: security, monitoring

Research history

  1. K200921 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

Alternatives

Related tools to compare

FDA-cleared K251590

Methinks CTA Stroke

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-08-20
FDA-cleared K251151

Rapid CTA 360

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-07-16
FDA-cleared K250685

Methinks NCCT Stroke

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-06-16

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