Evaluation packet
deepcOS
deepc · Radiology
Prepared November 22, 2026 from the public listing on CIFoundry. It shows what the public record says and what to ask the vendor. It is not a recommendation or an endorsement.
1. What the public record shows
- Regulatory status
- CE marked platform; hosts FDA-cleared third-party tools
- Published evidence
- Not on record
- Named health-system users
- Not on record
- Integrations
- Not on record
- Data inputs
- Not on record
- HIPAA BAA
- Not on record
- SOC 2 / HITRUST
- Not on record
- Deployment model
- Not on record
- Website
- https://deepc.ai
Integrations, data inputs, BAA, SOC 2, HITRUST and deployment model are reported by the vendor and not checked by us. Confirm them in writing.
2. Evaluation checklist for your role
Each question shows what the public record says: on record (with its source), reported by the maker, or not on record. It is a list of things to check, not a score.
For every reviewer
IT & security
Your ticks and notes stay in this browser. Nothing is sent to us.
3. Gaps to raise with the vendor
Based on what is missing or worth confirming in this tool’s public record.
- No published study is linked. Ask for peer-reviewed validation done outside the developer’s own sites, and for results on patients and equipment like yours.
- We found no public reports naming health systems that use it. Ask for reference sites similar to yours and contact them yourself.
- Will the vendor sign a HIPAA Business Associate Agreement?
- Does the vendor have a current SOC 2 Type II report or HITRUST certification you can review?
- Where is data stored and processed (cloud region, on-premises), and which subcontractors, including any large-language-model provider, touch patient data?
- How does it integrate with your EHR or imaging system, and where do results appear for the clinician?
- Is your data used to train the vendor’s models, and can it be deleted when the contract ends?
4. Questions for this kind of tool
From our Radiology AI guide.
Change tool type:
Urgent-finding triage and notification
Use this section if the tool screens studies for urgent findings, such as stroke, brain bleed or pulmonary embolism, and moves them up the worklist or alerts the care team.
Questions to ask
- What are sensitivity and specificity on our scanner models and protocols?
- How many false alerts per day should we expect at our volume?
- Does it actually change read order and time to treatment, and can you show data from a site like ours?
- Who receives mobile alerts (stroke team, ED), and is that part of the cleared use?
Test it locally
- Measure time from scan to read and to treatment before and after go-live, and audit every missed case in the first months.
Red flags
- No scanner or protocol breakdown
- Turnaround claims without before-and-after data
Detection and characterization aids
Use this section if the tool marks possible findings or rates how suspicious they are, for example lung nodules, fractures or lesions on screening mammograms.
Questions to ask
- What did the FDA test set include: number of cases, sites, scanner vendors? Which earlier device did the clearance rely on?
- How does it perform by age, sex, breast density or body habitus, as relevant?
- What failure modes are known? An algorithm with a blind spot misses the same kind of case on every study, not just once.
- How do you guard against radiologists over-trusting the marks, or under-reading studies with no marks?
Test it locally
- Run it silently on several hundred recent studies with known outcomes, per scanner model, before switching it on.
Red flags
- No subgroup data
- Results only in a separate viewer
- No monitoring dashboard
Measurement and quantification
Use this section if the tool measures structures or lesions, for example organ volumes, brain atrophy, lesion size or change over time.
Questions to ask
- How do measurements compare with your radiologists, and how repeatable are they on the same patient?
- Are results consistent across scanner models and software upgrades, so follow-up comparisons are valid?
- Can radiologists correct a measurement, and is the correction kept?
Test it locally
- Re-check measurements after any scanner or protocol change.
Image reconstruction and acquisition
Use this section if the tool changes how images are made, for example deep-learning reconstruction, noise reduction, lower-dose CT or faster MRI.
Questions to ask
- Could it remove or create detail, such as small lesions, and how was that tested?
- Which scanners and sequences is it cleared for?
- What dose or scan-time reduction have similar sites achieved while keeping diagnostic quality?
Test it locally
- Have radiologists compare standard and AI-processed images side by side on cases with known subtle findings.
Report drafting
Use this section if the tool drafts findings or impressions for the radiologist to edit and sign.
Questions to ask
- Is it FDA-cleared for this use, or positioned as a non-device writing aid? What does its intended use say?
- How often does a draft contain a finding not in the images, or miss one that is?
- Does it keep your follow-up recommendation standards and structured templates?
- Which large-language-model provider is used, and where are images and reports processed?
Red flags
- No measured error rate
- Drafts that can be signed without review
5. Questions for every tool
The 12 questions that apply to every tool
Fit and evidence
- Intended use. Does the stated use match the patients, setting, user and decision you plan to use it for?
- Evidence level. From weakest to strongest: vendor-internal test, retrospective external validation, prospective "silent" run, prospective live study, randomized trial, proven change in outcomes. Ask which level the claims rest on and look for peer-reviewed external validation.
- Population and equipment. Ask for results by age, sex, race and ethnicity, language and payer, and, where relevant, skin type and body habitus. Ask for results on your scanner or device vendors, EHR and protocols.
- Local validation. Before go-live, run the tool on your own recent cases and compare it to ground truth. Agree in the contract on what counts as passing.
Workflow and people
- Workflow cost. Count clicks, alerts per clinician per shift, minutes added per case, and who acts on the output. A strong tool that nobody acts on has no value.
- Integration. Native EHR or PACS integration or a separate window? Single sign-on? Where do results land?
- Human oversight. Who has the final say, how are disagreements with the tool handled, and how do you guard against over-reliance? Train users on known failure modes, not just features. Explanations matter most for risk scores and decision support.
After go-live
- Monitoring. Who checks for drift, how often, and what triggers a pause? Re-check after vendor updates, scanner or EHR changes, and shifts in your patient population. Agree in advance on the results that would retire the tool.
- Model updates. Version control, advance notice of changes, and the right to stay on a version you validated.
Data, liability and money
- Data rights and security. BAA, where data is stored and processed, encryption, retention, SOC 2 or HITRUST, whether your data trains the vendor's models, the list of subcontractors that touch patient data (including any large-language-model provider), and whether data can be deleted.
- Liability and patient notice. Who is liable when AI-assisted care goes wrong is still unsettled, and responsibility currently stays with the clinicians and organizations using the tool. Ask your malpractice carrier, and cover indemnification, audit rights and incident reporting in the contract. Joint Commission and CHAI guidance says patients should be told when AI directly affects their care, with consent where relevant.
- Money and exit. Pricing model, any real payment pathway, the return you will measure, termination for performance failure, data return, and no auto-renewal without a performance review.
6. Notes and decision
Problem we want to solve and how we will measure it
Vendor answers and follow-ups
Local test plan and what counts as passing
Decision, owner and next step