this post was submitted on 27 Jan 2024
239 points (97.6% liked)
Technology
59436 readers
3359 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I work in hospice making home visits, and yesterday was a bad day. Sucks when you're out making visits and missing notifications about change in patient conditions and death notifications. Before Teams they used a paging system that was glitchy, but everyone understood it was shit so there was an additional level of contact to ensure workers got relevant info when needed. Yesterday half the day went by before people realized the system was fucked.
Did we learn something about depending on bad infrastructure for essential comms?
Maybe backup systems for critical communications?
Nope, just going to keep rolling with perhaps the worst business chat client.
I'm going to guess they weren't the one that made the decision to only use Teams.
Certainly doesn't help that Microsoft continues to try and make Teams the only real thing that integrates properly with anything else in 365.
Embrace, Extend, Ex…
I feel like there is an opportunity for a local network solution to this that would be very resilient. It kind of surprises me that for medical communication you would ever want to rely primarily on an application that has to go out to the internet and back. Then again I guess companies that wish to make money probably can’t just, you know, sell a complete stand-alone product that just works. But if I were to build one for my networking class; what quality of life, or feature requirements would be preferred in a health care setting?
The hospital provides phones and has us use Teams for remote meetings and other communication. Official patient information is always recorded through Epic/Haiku. Since the majority of the staff is in the field, they'll use Teams to communicate throughout the day for staffing updates and to notify us of deaths - particularly helpful if you're me driving to the patients house and planning on giving them a massage lol.
My mind touched the void for a second reading this sentence.
Having to use shitty teams throughout the day for primary communication is already miserable enough, but the idea of people using it to report deaths in the same way I might report a dead port on a switch (knowing that somebody at some point absolutely 👍'd it) is some macabre shit.
I mean, it's hospice lol. I work with some of the most compassionate, respectful, and caring people I could ever hope to work with. We also tend to have a macabre sense of humor. 🥴
I don't doubt it. It's just a surreal thing to think about.
It's one of those industry things that are incomprehensible to outsiders. I work at a hospital, and my office is directly on the route between the ER and the morgue. I know how bad a day it's been by how many morgue carts roll by during a shift. Just one of those things.