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