There are pills and a minor balloon dilation. The point is I would not be threated without it. Now I can go with my girlfriend for a dinner. That would be a huge stress before that.
Nothing he stated suggests this. Not giving a nod to how difficult it is doesn't mean people don't care. Unfortunately it is still true, we all have to advocate for our own care and pay attention to ourselves. The fact that this negatively affects the people who need the most care and attention is a harrowing part of humanity we often gloss over.
A boxing referee says "Protect yourself at all times."
They do this not because it isn't their job to protect fighters from illegal blows, but because the consequences of illegal blows are sometimes unfixable.
An encouragement for patients to co-own their own care isn't a removal of a physician's responsibility.
It's an acknowledgement that (1) physicians are human, fallible, and not omniscient, (2) most health systems have imperfect information sync'ing across multiple parties, and (3) no one is going to care more about you than you (although others might be much more informed and capable).
Self-advocacy isn't a requirement for good care -- it's due diligence and personal responsibility for a plan with serious consequences.
If a doc misses a diagnosis and a patient didn't spend any effort themselves, is that solely the doctor's fault?
PS to parent's insinuation: 20 years in the industry and 15 years of managed cancer in immediate family, but what do I know?
My question is, since you understand this very well, how successful
are patients (that manage the effort) at both acquiring scientifically accurate knowledge
and improving their health meaningfully?
And maybe share some tips like good knowledge databases?
I've seen patients (both family and non) meaningfully improve their health outcomes with statistically-significant frequency primarily via 4 methods.
1. Take ownership of their own medical records, learn them, and bring them to appointments. The most common failure in the current US medical system is incomplete/missing record transfer because of disconnected systems. Physicians will almost always attempt to confirm critical details, but that doesn't help if the patient says "I don't know."
2. Learn basic medical system-level knowledge relevant to a case. E.g. college 1xx freshman-level. No need to become an expert, but if a patient is dealing with kidney issues... it's pretty important to learn the basics about what kidneys are and do.
3. Ask about alternatives. "If we didn't go with that plan, what would be your next two recommended plans, and why aren't they first?" Having that alternative context is especially helpful when visiting specialists / other parties, as the patient can more fully describe the thinking behind their treatment plan. Also when researching online, the context helps avoid obvious pitfalls. (And yes, sometimes the reason will be "Because your insurance wouldn't cover X", which is also useful to know)
4. Use second options to measure uncertainty about the primary plan (e.g. everyone agrees vs it's debatable), but don't treatment-shop. The useful piece of information is opening a discussion about specific alternatives, while also listening to reasons against them.
Peer reviewed studies are surprisingly accessible (e.g. PubMed et al.), but they're also functionally useless without basic medical knowledge and details about a specific case.
Finally, for potentially lethal and/or lengthy conditions, I'm a firm believer that any empowerment improves outcomes simply by making the patient feel more involved and in control of their care.
Almost every "that could have been avoided" case I know was a willfully-ignorant and/or disinterested patient.
Using Grep or regex is textual refactoring. If you want to rename every reference to a type Foo, how do you is that without touching any variables named foo, or any classes named FooBar
The answer is use tools that have semantic info to rename things.
Another poster mentioned using symbols and references, another way to refactor code programmatically is to make use of code mods. Code mods are very powerful and this is a use case where I find LLMs to shine as the various syntax and language ASTs are hard to remember (even if you do understand what you're doing).
Problem is that NVIDIA literally makes the only sane graphics/compute APIs. And part of it is to make the API accessible, not needlessly overengineered. Either the other vendors start to step up their game, or they'll continue to lose.
I'm having a hard time taking an API seriously that uses atomic types rather than atomic functions. But at least it seems to be better than Vulkan/OpenGL/DirectX.
reply