Transparency alternatives to Duria
Other Medical practice software vendors we measure, sorted by how much we found at them and not at Duria. This is a comparison of disclosure, not of features or fitness.
12 shown of 85 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 “Found there, not found at Duria” is the one that closes them.
| Vendor | Score | Found there, not found at Duria | Found at Duria, not found there | |
|---|---|---|---|---|
| Nookalnookal.comSee also Transparency alternatives to Nookal | 78/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Heidi Healthheidihealth.comSee also Transparency alternatives to Heidi Health | 52/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 1 No third-party tracking before consent | Compare |
| Clinikocliniko.comSee also Transparency alternatives to Cliniko | 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 |
| Semblesemble.ioSee also Transparency alternatives to Semble | 39/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Clinicmasterclinicmaster.comSee also Transparency alternatives to Clinicmaster | 39/100 | 3 Data processing agreement, Data location stated, Certifications named | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Doctenadoctena.comSee also Transparency alternatives to Doctena | 35/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Teleclinicteleclinic.comSee also Transparency alternatives to Teleclinic | 35/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| NextGennextgen.comSee also Transparency alternatives to NextGen | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| ChiroTouchchirotouch.comSee also Transparency alternatives to ChiroTouch | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Function 365function365.co.ukSee also Transparency alternatives to Function 365 | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Mira Healthmirahealth.careSee also Transparency alternatives to Mira Health | 26/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| SimplePracticesimplepractice.comSee also Transparency alternatives to SimplePractice | 26/100 | 2 Status page with history, Public pricing | 2 No third-party tracking before consent, 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.