Transparency alternatives to Clinicmaster
Other Medical practice software vendors we measure, sorted by how much we found at them and not at Clinicmaster. This is a comparison of disclosure, not of features or fitness.
12 shown of 88 that differ from Clinicmaster on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Clinicmaster has 8 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Clinicmaster” is the one that closes them.
| Vendor | Score | Found there, not found at Clinicmaster | Found at Clinicmaster, not found there | |
|---|---|---|---|---|
| Nookalnookal.comSee also Transparency alternatives to Nookal | 78/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | nothing | Compare |
| Heidi Healthheidihealth.comSee also Transparency alternatives to Heidi Health | 52/100 | 4 Status page with history, Public pricing, security.txt (RFC 9116), +1 | 2 Data location stated, Certifications named | Compare |
| Semblesemble.ioSee also Transparency alternatives to Semble | 39/100 | 3 Subprocessor list, Status page with history, Named privacy contact | 2 Data processing agreement, Data location stated | Compare |
| Clinikocliniko.comSee also Transparency alternatives to Cliniko | 43/100 | 2 Status page with history, Public pricing | 1 Data processing agreement | Compare |
| Mira Healthmirahealth.careSee also Transparency alternatives to Mira Health | 39/100 | 2 Subprocessor list, Notice before subprocessors change | 2 Data processing agreement, HTTPS enforced with HSTS | Compare |
| Doctenadoctena.comSee also Transparency alternatives to Doctena | 35/100 | 2 security.txt (RFC 9116), Named privacy contact | 1 Data processing agreement | Compare |
| Teleclinicteleclinic.comSee also Transparency alternatives to Teleclinic | 35/100 | 2 Public pricing, Named privacy contact | 2 Data processing agreement, Certifications named | Compare |
| Eye Cloud Proeyecloudpro.comSee also Transparency alternatives to Eye Cloud Pro | 32/100 | 2 Public pricing, security.txt (RFC 9116) | 2 Data processing agreement, HTTPS enforced with HSTS | Compare |
| ChiroTouchchirotouch.comSee also Transparency alternatives to ChiroTouch | 26/100 | 2 Public pricing, Named privacy contact | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | Compare |
| Function 365function365.co.ukSee also Transparency alternatives to Function 365 | 26/100 | 2 Public pricing, Named privacy contact | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | Compare |
| SimplePracticesimplepractice.comSee also Transparency alternatives to SimplePractice | 26/100 | 2 Status page with history, Public pricing | 3 Data processing agreement, Data location stated, Certifications named | Compare |
| 4D EMR4d-emr.comSee also Transparency alternatives to 4D EMR | 22/100 | 2 Public pricing, Named privacy contact | 3 Data processing agreement, Data location stated, 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.