This can still be done programmatically without any kind of confirmation from aws-cli, bringing this back to, an API can (and probably should be able to) take certain destructive operations that someone’s blocked from doing in a UI, such as in your example.
My s3 buckets are backed up with Nakivo (and immutable for 7 days) just in case, and that’s just to protect me from myself and my s3 provider either failing or deciding they don’t want to do business with me anymore for some arbitrary reason. I’m not even turning an LLM loose on it.
it was doing the same to me in 26.2 , to the point where I’d pause and reveal any passwords it just generated then copy and paste them into a note before proceeding.
Not sure if it’s fixed in 26.4 because I don’t trust their updates anymore every one just makes the phone worse or deploys some new oppressive age app or identity verification scheme to lick another nation-states jackboots.
1) in the event you find yourself partially or totally disabled but the records don’t really make a good case for it and your provider has a dismissive attitude about filling out additional documentation to substantiate what they failed to in your records.
You’re not necessarily going to get approved for FMLA, STD, LTD, SS etc based on a diagnosis or test results alone. They will nitpick over say, heart failure, as if that’s magically and spontaneously going to go away. If you’re telling your provider that you’re limited by things like oh I don’t know, “I’m only awake for 2-4 hours before I need to sleep again” or “some days I just can’t do it and sleep 20 hours” but it’s not in your chart… expect denials and clarifications and a huge burden on you to prove why it’s limiting.
2) continuity of care, so you don’t end up explaining everything from the top to a specialist or having them run all these tests and procedures from square one — when there’s months long backlogs , and we already did all this and you need treatment - but - there wasn’t much to work with in your referring chart.
You might not appreciate the “intrusion” if you’re healthy and just worried about your privacy.
If/When things go south and you find yourself fighting these entities for a year or two or three while they nitpick and delay and deny and drag their feet , you’ll be glad an “AI” kept up meticulous records because this is phenomenally stressful and an endless burden on you when they don’t.
So, their AI slop can vomit out all this extra info on why insurance companies should pay them or why your condition is in fact disabling, and now their AI slop can comb through it looking for all that. Because they will try to avoid paying or approving any kind of leave or benefits if it’s not there
And god forbid you hand them a form where they’re being asked to explain themselves. 50/50 on them being eager to help out or rolling their eyes and saying something really nasty about the imposition. And then even when they do that, they almost never file a copy in your chart so your chart STILL doesn’t substantiate your claims. I’m all for an “ai” doing the progress notes in a case where the facility or provider can’t be fucked to do so.
Happily that’s not true of my current provider, who just, does that anyway (?) But I’ve been around enough to know they’re an exception. Even when providers are on your side and mean well, and want to bend over backwards to help you in any way they can — and I want to just acknowledge that’s the situation I’m in today — honestly , sometimes they just forget some of the details when they do their notes.
That’s why some places make the provider do it in real time while they’re talking to you, so they didn’t forget something relevant thirty minutes later. The other side of the coin here may be that some providers find that distracting or off putting to be typing away like a stenographer while they’re examining you…
I think it would be fair to say this can all be tedious and a burden for both patients and providers. There’s just a world of difference between a provider who wants to do this to provide excellency in care, and a provider who wants to do this because they resent it and think it’s beneath them.
not sure if this confirms the impression you have there... I wasn't like this until a couple of headless VPS'es (on Arm8) got through the upgrade from 18.x -> 20.x -> 22.x and then crashed out over -> 24.x for a still unknown reason. now I'm just afraid .. or I should say reluctant ..to repeat that whole fiasco.
Sometimes swearing a little or grumbling “HEY. I typed what I typed” at it helps a little.
I don’t even know how many times in 20-30+ years I’ve checked some box in system or program preferences begging it to knock that off.
This is the real reason I already loathe and avoid the emdash (nitpicking over a personal stylistic preference I won’t relent on even if I’m wrong) but I can’t be the only one this happens to.
Getting piled on and called “AI” really doesn’t ease my distaste for it, but .. do people.. not write enough to understand that it brute forces its way into human copy as well?
and yes. phone posting on HN. will insert them. to my dismay.
The other one that ticks me off endlessly but I’ve finally said to hell with it and just let it go?
Turning " into “.
(Writer. Not a very good one and I’m not here to steer anyone to that drivel. But at least I’m a human one.)
But I actually did appreciate the one time he handed me a Cisco config that was 90% perfect and took me all of 5 minutes to fix. Sometimes the three of us make a hell of a team.
My s3 buckets are backed up with Nakivo (and immutable for 7 days) just in case, and that’s just to protect me from myself and my s3 provider either failing or deciding they don’t want to do business with me anymore for some arbitrary reason. I’m not even turning an LLM loose on it.