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