Transparency alternatives to DocEngage
Other Medical practice software vendors we measure, sorted by how much they publish that DocEngage does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 87 that differ from DocEngage on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DocEngage has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and DocEngage does not” is the one that closes them.
| Vendor | Score | Publishes, and DocEngage does not | DocEngage publishes, and they do not | |
|---|---|---|---|---|
| Nookalnookal.com | 78/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | nothing | Compare |
| Teleclinicteleclinic.com | 43/100 | 3 Data location stated, No third-party tracking before consent, Named privacy contact | 1 Certifications named | Compare |
| Semblesemble.io | 39/100 | 3 Subprocessor list, Status page with history, Named privacy contact | 1 Public pricing | Compare |
| Doctenadoctena.com | 35/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 1 Public pricing | Compare |
| Clinikocliniko.com | 43/100 | 2 Data location stated, Status page with history | nothing | Compare |
| Clinicmasterclinicmaster.com | 30/100 | 2 Data processing agreement, Data location stated | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Heidi Healthheidihealth.com | 30/100 | 2 Status page with history, security.txt (RFC 9116) | 1 Certifications named | Compare |
| NextGennextgen.com | 30/100 | 2 Data location stated, Named privacy contact | 1 Public pricing | Compare |
| Function 365function365.co.uk | 26/100 | 2 Data location stated, Named privacy contact | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| tomedotomedo.de | 26/100 | 2 Data location stated, Named privacy contact | 2 Public pricing, Certifications named | Compare |
| Doctolibdoctolib.de | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 2 Public pricing, Certifications named | Compare |
| Duriaduria.de | 22/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 2 Public pricing, Certifications named | 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.