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