Transparency alternatives to Function 365
Other Medical practice software vendors we measure, sorted by how much we found at them and not at Function 365. 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 “Found there, not found at Function 365” is the one that closes them.
| Vendor | Score | Found there, not found at Function 365 | Found at Function 365, not found there | |
|---|---|---|---|---|
| Nookalnookal.comSee also Transparency alternatives to Nookal | 78/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | nothing | Compare |
| Heidi Healthheidihealth.comSee also Transparency alternatives to Heidi Health | 52/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | 2 Data location stated, Named privacy contact | Compare |
| Semblesemble.ioSee also Transparency alternatives to Semble | 39/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 2 Data location stated, Public pricing | Compare |
| Clinikocliniko.comSee also Transparency alternatives to Cliniko | 43/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Clinicmasterclinicmaster.comSee also Transparency alternatives to Clinicmaster | 39/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 2 Public pricing, Named privacy contact | Compare |
| Mira Healthmirahealth.careSee also Transparency alternatives to Mira Health | 39/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Public pricing, Named privacy contact | Compare |
| Doctenadoctena.comSee also Transparency alternatives to Doctena | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Doctolibdoctolib.deSee also Transparency alternatives to Doctolib | 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.deSee also Transparency alternatives to Duria | 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.deSee also Transparency alternatives to samedi | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| CGMcgm.comSee also Transparency alternatives to CGM | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| NextGennextgen.comSee also Transparency alternatives to NextGen | 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.