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