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