Integrations

Day 1 Feedback: Heidi Remote – Serious Real‑World Usability Issues
Day 1 Feedback: Heidi Remote – Serious Real‑World Usability Issues We started using the new Heidi Remote today with two clinicians. Our first question after day one is simple: Was this product tested in real‑world clinical environments before release? User 1 Experience 4 failed attempts using the remote today No syncing occurred at all The only data captured was the session start time No notes, no transcript, no audio Approximately 2 hours of clinical data lost One session reported incorrectly as “too short”, despite being ~20 minutes A major usability issue: The start/stop button does not respond to a normal or firm press It appears to require a very light, precise “micro‑press” to work Long or firm presses do nothing It took us ~1.5 hours to even work out how to successfully start or stop a recording This is not intuitive, not discoverable, and completely impractical in a real clinical setting. User 2 Experience Better overall outcome Used the remote across 10 sessions However: 2 sessions failed to load or work 1 session incorrectly flagged as “too short” Another failed due to a Bluetooth connection interruption This raises a major concern: We were under the impression that the remote did not require continuous Bluetooth connection to function. If Bluetooth dropouts can invalidate sessions entirely, this needs to be made explicit. Critical Design Flaw: No Recovery or Re‑Sync Option The most serious issue we’ve identified: If a session fails to sync, there is: No ability to retry syncing No way to force upload/download No way to reconnect the remote and retrieve data No way to assign or reattach the session to a new appointment Once it fails, the data appears to be permanently lost. For a clinical product, this is unacceptable. Temporary connection issues should never result in irreversible loss of clinical records. Summary Right now, Heidi Remote: Feels unfinished Is not resilient to real‑world conditions Lacks basic usability safeguards Introduces risk of irretrievable data loss This was day one. Multiple failures, lost data, and significant clinician time wasted. At its current state, this product is not ready for routine clinical use. We strongly recommend: Immediate review of button interaction design Clear documentation on Bluetooth dependency Robust retry / re‑sync / recovery options Real‑world clinician testing before further rollout We want this product to succeed — but right now, it is creating risk rather than reducing workload.
2
Load More