What a privacy nightmare - eviltoast
  • sp3ctr4l@lemmy.zip
    link
    fedilink
    English
    arrow-up
    15
    ·
    3 days ago

    Yep, was gonna post this.

    Good luck, this hospital’s IT department, good fucking luck.

      • sp3ctr4l@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 hours ago

        … Can you expand on what you mean by that?

        Are you saying just… firewall all the Echoes, lock them out of any ability to access the actual internet?

        So they never phone home?

        I mean… yeah I guess that could work, if you took the time to manually do custom firmware updates on them in some way that only involves your local (hospital) intranet… and overrides the default proprietary firmware and basically flashes it with some custom system that doesn’t rely on AWS connections to work… if… that even exists…

        Their hospital oriented implementation… was… reliant on a constant AWS connection to actually process voice recordings, transform them into text or some other digital format, then send that back to the hospital, “securely.”

        https://www.hipaajournal.com/amazon-ends-support-for-third-party-hipaa-eligible-alexa-skills/

        Apparently they actually lost HIPAA compliance back in 22.

        If they are literally just a being used as an intercomm system… why would you even use Echoes?

        There are tons of other, actually HIPAA compliant, hospital oriented, digital intercomm software systems and manufacturers.

        Seriously, please explain to me how ‘802.11x’, a term that means ‘all wifi standards’, somehow solves the problem of Echoes being non HIPAA compliant, requiring constant access to Amazon servers to actually process the raw audio…

        Please elaborate.