Transparency alternatives to Telemis
Other Medical imaging and radiology vendors we measure, sorted by how much we found at them and not at Telemis. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from Telemis on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Telemis has 12 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Telemis” is the one that closes them.
| Vendor | Score | Found there, not found at Telemis | Found at Telemis, not found there | |
|---|---|---|---|---|
| RamSoftramsoft.comSee also Transparency alternatives to RamSoft | 33/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Sectrasectra.comSee also Transparency alternatives to Sectra | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Aidocaidoc.comSee also Transparency alternatives to Aidoc | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Biotronics3Dbiotronics3d.comSee also Transparency alternatives to Biotronics3D | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Gleamergleamer.aiSee also Transparency alternatives to Gleamer | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| HeartFlowheartflow.comSee also Transparency alternatives to HeartFlow | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Jacobianjacobian.comSee also Transparency alternatives to Jacobian | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Qure.aiqure.aiSee also Transparency alternatives to Qure.ai | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Merativemerative.comSee also Transparency alternatives to Merative | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Novaradnovarad.netSee also Transparency alternatives to Novarad | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Viz.aiviz.aiSee also Transparency alternatives to Viz.ai | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| ScImagescimage.comSee also Transparency alternatives to ScImage | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | 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.