Transparency alternatives to Aidoc
Other Medical imaging and radiology vendors we measure, sorted by how much we found at them and not at Aidoc. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Aidoc on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Aidoc has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Aidoc” is the one that closes them.
| Vendor | Score | Found there, not found at Aidoc | Found at Aidoc, not found there | |
|---|---|---|---|---|
| RamSoftramsoft.comSee also Transparency alternatives to RamSoft | 30/100 | 3 Data processing agreement, Certifications named, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Merativemerative.comSee also Transparency alternatives to Merative | 17/100 | 2 Certifications named, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Novaradnovarad.netSee also Transparency alternatives to Novarad | 17/100 | 2 Certifications named, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Viz.aiviz.aiSee also Transparency alternatives to Viz.ai | 17/100 | 2 Certifications named, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Sectrasectra.comSee also Transparency alternatives to Sectra | 30/100 | 1 Named privacy contact | nothing | Compare |
| Gleamergleamer.aiSee also Transparency alternatives to Gleamer | 26/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| HeartFlowheartflow.comSee also Transparency alternatives to HeartFlow | 26/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Jacobianjacobian.comSee also Transparency alternatives to Jacobian | 26/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Qure.aiqure.aiSee also Transparency alternatives to Qure.ai | 26/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Wellbeing Techwellbeingtech.coSee also Transparency alternatives to Wellbeing Tech | 22/100 | 1 No third-party tracking before consent | 1 Data location stated | Compare |
| Milvuemilvue.comSee also Transparency alternatives to Milvue | 17/100 | 1 Named privacy contact | 1 Data location stated | Compare |
| Agfa HealthCareagfahealthcare.comSee also Transparency alternatives to Agfa HealthCare | 13/100 | 1 Certifications named | 2 Data location stated, security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.