Aidoc and Qure.ai describe different operating assumptions for clinical AI. Aidoc's aiOS is documented as an enterprise platform that runs and governs clinical AI across a health system, with one integration supporting multiple algorithms and care coordination tools [1]. Qure.ai's public materials describe modular products such as qXR for chest X-ray reporting, qER for head CT triage, and qCT for lung nodule quantification, each with its own workflow and regulatory documentation [7][9]. The comparison therefore turns on whether a buyer needs a systemwide platform layer or a focused imaging application that can be deployed on cloud or on-premise [7]. Neither vendor's public documentation supports a direct clinical superiority claim, and the sources do not provide head-to-head performance data.
Platform Architecture and Integration Boundaries
Aidoc's aiOS is described as a clinical AI platform designed to run and govern clinical AI across a health system, unifying data, workflows, and oversight at the point of care [1]. The vendor states that aiOS allows health systems to run multiple algorithms across a single scan and present AI insights in the context of the patient record, surfacing both suspected and incidental findings [1]. Aidoc also describes a selection layer that uses textual data, scan metadata, and pixel analysis to determine which scans proceed for AI processing [1]. This architecture implies a centralized deployment model where the platform, rather than individual algorithms, becomes the integration point for the enterprise.
Qure.ai's documentation presents a different boundary. The qXR product page describes deployment on cloud or on-premise and lists output specifications for GSPS overlays, PDF reports, DICOM encapsulated reports, structured reports, and secondary capture files [7][10]. The platform API documentation indicates that generated outputs are available as a response payload with URLs for file downloads [11]. This suggests an application-level integration where each product, such as qXR or qER, produces outputs that can be consumed by existing systems. The retrieved materials do not describe an equivalent enterprise platform layer for Qure.ai, though they do document a follow-up management platform called qTrack for lung nodule workflows [8].
Regulatory Scope and Intended Users
Aidoc's radiology materials state that the company provides access to one of the broadest ranges of FDA-cleared and CE/UKCA-marked algorithms in clinical AI [2]. The solutions page specifies 17 organic FDA-cleared algorithms and eight FDA-cleared partner algorithms for radiology [5]. Aidoc also lists algorithms across neuroscience, venous thromboembolism, aortic, cardiology, and chest, abdomen, breast, and bone categories [6]. These regulatory claims are vendor statements and do not independently establish clinical performance. The documentation does not provide a complete list of cleared indications for every algorithm, and some listed items are partner solutions rather than Aidoc's own cleared products [6].
Qure.ai's regulatory page provides more granular product-level detail. It states that qER is US FDA 510(k) cleared as a radiological computer aided triage and notification software intended to flag suspected intracranial hemorrhage, mass effect, midline shift, and cranial fracture in head CT images [9]. The page also states that qCT-quant is FDA cleared as an automated radiological image processing software for volumetric and diameter analysis of lung CT regions [9]. For qXR, the US page indicates that qXR-LN is FDA cleared for radiologists, pulmonologists, and emergency physicians reviewing adult chest imaging [8]. Qure.ai also documents CE certification under both EU MDD and EU MDR for several products, with Class IIa and Class IIb designations [9].
A Suggested Evaluation Workflow for a Multi-Hospital Radiology Group
A radiology group supporting three community hospitals and a teleradiology service could evaluate both vendors against a single chest X-ray and head CT workflow. For Qure.ai, the team would review the qXR API acceptance criteria to confirm that existing CR and DR systems meet the 1440 by 1440 minimum resolution and that patient age exclusions are acceptable [12]. They would then test the output specifications to verify that GSPS overlays and structured reports can be consumed by the existing PACS and reporting systems [10]. For Aidoc, the team would assess whether the aiOS platform's single-integration model can accommodate the group's existing EHR and PACS configurations across all three hospitals, and whether the governance analytics justify the platform-level deployment [1][4].
This suggested workflow is not a test protocol and does not imply that either vendor would pass or fail. It illustrates how the documented integration boundaries create different evaluation questions. A group with heterogeneous PACS instances may find Qure.ai's per-product deployment model easier to pilot, while a group seeking unified governance across multiple algorithms may find Aidoc's platform model more aligned. The sources do not provide enough information to determine which approach is more cost-effective or clinically appropriate for any specific organization.
Customer Settings and Workflow Assumptions
Aidoc's materials emphasize health system scale. The platform page cites live deployment across 150+ health systems and 1,600+ hospitals, with 230+ enterprise deployments and 60 million patients supported annually [1]. A case example describes Hartford HealthCare deploying 17 FDA-cleared algorithms plus care coordination and patient management tools across radiology, neurology, vascular, cardiology, and emergency care workflows [1]. Another example states that 12 use cases were deployed system-wide in three months, with urgent and incidental findings triaged in under five minutes, down from 20 [1]. These are vendor-reported figures and do not represent independent verification.
Qure.ai's materials describe a broader range of settings, including teleradiology and high-volume screening. The qXR page lists use cases for teleradiology and immigration screenings, active case finding for TB and lung cancer screening, and incidental finding detection for lung cancer and heart failure [7]. The page also cites 90+ countries and 3,100+ sites, with 10.7 million scans processed [7]. A case study describes a 40% turnaround time reduction by classifying 40% of normal X-rays with a 98.9% negative predictive value at Aarthi Scans in India [7]. These figures are vendor-reported and specific to the cited deployments. The documentation does not establish that these results generalize to other organizations.
Governance, Analytics, and Operational Oversight
Aidoc positions governance as a platform feature. The aiOS page states that the platform supports existing governance through validation, drift detection, override tracking, and analytics that fit into organizational and regulatory frameworks [1]. Aidoc Analytics is described as delivering real-time visibility into performance, adoption, and impact [1]. The vendor also states that aiOS scales AI enterprise-wide with one integration, reducing cognitive load and automating processes without raising costs [1]. These are vendor claims about platform capabilities, not independently validated outcomes. The documentation does not specify which governance metrics are available or how drift detection is implemented.
Qure.ai's documentation addresses governance primarily through quality systems and security certifications rather than a unified analytics layer. The regulatory page states that Qure.ai holds MDSAP certification for ISO 13485:2016 from TUV SUD, covering regulatory standards from the US FDA, Australian TGA, Brazilian ANVISA, Health Canada, and Japan's MHLW [9]. The page also states that Qure.ai is ISO 27001 certified and that cybersecurity audit reports are part of FDA submissions and CE technical files [9]. For workflow oversight, the US page describes qTrack as supporting radiology workflow coordination and longitudinal tracking across imaging and follow-up [8]. This is a narrower governance scope than Aidoc's platform-level analytics claims.
Documentation Depth and Technical Transparency
Qure.ai provides publicly accessible technical documentation that specifies input and output requirements. The qXR API documentation lists acceptance criteria including PA/AP view, minimum resolution of 1440 by 1440, patient age over six years, erect or supine position, modalities CR/DR/DX/RF, valid DICOM format, and chest body part [12]. The output specifications document describes GSPS overlays, PDF reports, DICOM encapsulated reports, structured reports, and secondary capture files [10]. This level of detail allows technical teams to evaluate integration requirements before procurement. The documentation does not include performance specifications or validation data.
Aidoc's public materials are less technically granular. The platform pages describe integration with EHR, PACS, scheduling, and reporting systems, and state that implementation takes two to three weeks with minimal IT effort [2][4]. The radiology page describes the Aidoc Widget as consolidating results from various algorithms, including strategic partner solutions, into a single interface [2]. However, the retrieved materials do not provide API-level input criteria or output file specifications comparable to Qure.ai's documentation. Buyers requiring detailed technical specifications may need to request additional documentation from Aidoc directly. This difference in public documentation depth does not indicate a difference in product capability.
Sources & references
- aiOS™ | End-To-End Clinical AI Platform | Aidoc · www.aidoc.com
- Radiology AI Imaging | Aidoc – Faster, Smarter Care · www.aidoc.com
- Radiology AI Imaging | Aidoc – Faster, Smarter Care · www.aidoc.com
- Enterprise Clinical AI Platform | Aidoc – Immediate Impact · www.aidoc.com
- AI-Powered Clinical Solutions | Aidoc · www.aidoc.com
- CT AI Algorithms | Aidoc · info.aidoc.com
- qXR AI enabled comprehensive Chest X-ray reporting tool · www.qure.ai
- AI Healthcare Solutions in USA - Qure.ai · www.qure.ai
- Qure AI | We ensure that our products are safe · www.qure.ai
- qXR · documentation.qure.ai
- Output Specifications · documentation.qure.ai
- qXR · documentation.qure.ai