Alternatives to Duria
Other Medical practice software vendors we measure, sorted by how much they publish that Duria does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Duria on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Duria has 9 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, Notice before subprocessors change, Named privacy contact. The column “publishes and Duria does not” is the one that closes them.
| Vendor | Score | Publishes, and Duria does not | Duria publishes, and they do not | |
|---|---|---|---|---|
| Nookalnookal.com | 78/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Clinikocliniko.com | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Heidi Healthheidihealth.com | 43/100 | 3 Data location stated, Status page with history, Public pricing | 1 No third-party tracking before consent | Compare |
| Doctenadoctena.com | 35/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 No third-party tracking before consent | Compare |
| NextGennextgen.com | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Tebratebra.com | 30/100 | 3 Data location stated, Status page with history, Public pricing | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| SimplePracticesimplepractice.com | 26/100 | 2 Status page with history, Public pricing | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| tomedotomedo.de | 26/100 | 2 Data location stated, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| DrChronodrchrono.com | 17/100 | 2 Status page with history, Public pricing | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Doctolibdoctolib.de | 22/100 | 1 Status page with history | 1 No third-party tracking before consent | Compare |
| eClinicalWorkseclinicalworks.com | 22/100 | 1 Data location stated | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| CGMcgm.com | 17/100 | 1 Certifications named | 1 No third-party tracking before consent | 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.