Transparency alternatives to opta data
Other Home health and care agencies vendors we measure, sorted by how much we found at them and not at opta data. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from opta data on at least one criterion we measured for both. Public transparency score, not a product or security rating.
opta data 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 opta data” is the one that closes them.
| Vendor | Score | Found there, not found at opta data | Found at opta data, not found there | |
|---|---|---|---|---|
| AlayaCarealayacare.comSee also Transparency alternatives to AlayaCare | 17/100 | 3 Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| CareVoyantcarevoyant.comSee also Transparency alternatives to CareVoyant | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Generationshomecaresoftware.comSee also Transparency alternatives to Generations | 22/100 | 2 Data location stated, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| MatrixCarematrixcare.comSee also Transparency alternatives to MatrixCare | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Trella Healthtrellahealth.comSee also Transparency alternatives to Trella Health | 18/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Brittcobrittco.comSee also Transparency alternatives to Brittco | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Rosemarkrosemarksystem.comSee also Transparency alternatives to Rosemark | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| CareSmartz360caresmartz360.comSee also Transparency alternatives to CareSmartz360 | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| HHAeXchangehhaexchange.comSee also Transparency alternatives to HHAeXchange | 13/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| MEDIFOX DANmedifoxdan.deSee also Transparency alternatives to MEDIFOX DAN | 13/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| mynevamyneva.euSee also Transparency alternatives to myneva | 13/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Netsmartntst.comSee also Transparency alternatives to Netsmart | 13/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | 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.