Alternatives to Nookal
Other Medical practice software vendors we measure, sorted by how much they publish that Nookal does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Nookal on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nookal has 3 gaps in what we could measure: No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Nookal does not” is the one that closes them.
| Vendor | Score | Publishes, and Nookal does not | Nookal publishes, and they do not | |
|---|---|---|---|---|
| Duriaduria.de | 22/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | Compare |
| Heidi Healthheidihealth.com | 43/100 | 1 security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | Compare |
| Doctenadoctena.com | 35/100 | 1 security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Doctolibdoctolib.de | 22/100 | 1 security.txt (RFC 9116) | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | Compare |
| CGMcgm.com | 17/100 | 1 security.txt (RFC 9116) | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | Compare |
| DAMPSOFTdampsoft.de | 17/100 | 1 security.txt (RFC 9116) | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | Compare |
| medatixxmedatixx.de | 17/100 | 1 security.txt (RFC 9116) | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | Compare |
| Arzt Direktarzt-direkt.de | 13/100 | 1 No third-party tracking before consent | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | Compare |
| Dr. Flexdr-flex.de | 13/100 | 1 No third-party tracking before consent | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | Compare |
| jamedajameda.de | 4/100 | 1 security.txt (RFC 9116) | 9 Data processing agreement, Subprocessor list, Data location stated, +6 | Compare |
| Clinikocliniko.com | 43/100 | nothing we found there and not here | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | Compare |
| NextGennextgen.com | 30/100 | nothing we found there and not here | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 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.