139 karma · joined November 3, 2020
Email: cfu288 at meremedical.co
Resident doctor and ex-software engineer - Always looking to connect with other people
cfu288.com
Are these palliative care doctors and nurses engaging with the patient and your family? One thing they do is ask about code status (full code vs DNR/DNI) and clarify what the wishes of the patient are, help out with legacy planning, make sure everyone is aware of all the possible outcomes (not just death but reduction in QOL), and provide emotional support. Note that this job is not limited to a palliative team, but most patients and families don’t think about these things until it’s too late. CPR can have a pretty poor outcome in many elderly patients and can do more harm then good, so they may just want to make sure you have all the right information. It’s becoming the standard to engage in these talks sooner, not necessarily because they anticipate a poor recovery on this admission but you never know about the next one.
Just FYI and to tie this back to the original article, the physicians taking care of your father have no say in organ donation, it’s a conflict of interest for obvious reasons.
You’ll get something like “sepsis criteria triggered by wbc 13, cr 1.5, hr 101, rr 22.” And that’s it - usually in the middle of a night on a new patient I just got a page for. Can’t open documentation to see the patients med history. It’s ridiculous. I’m not using Epic but I am using a major EMR.
To be fair I’ve written almost exactly what you mentioned out of sheer frustration once or twice but it’s not ideal
Remember - the 80 hour a week limit is not a max limit. It is the max hours per week AVERAGED OVER 4 weeks. You can easily work 100 hours this week if you do 60 the next.
There’s just an assumption that these client databases don’t need mature tools and migration strategies as “it’s just a web client, you can always just re-sync with a server”. Few client db felt mature enough to warrant building my entire app on as they’re not the easiet to migrate off of.
I also tried LokiJS which is mentioned in the OP. I even forked (renamed it SylvieJS lol) it to rewrite it in TS and update some of the adapters. I ultimately moved away from it as well. I found an in memory db will struggle past a few hundred mbs which I hit pretty quickly.
No matter what db you use, you’re realistically using indexed db behind the hood. What surprised me was that a query to indexed db can be slower than a network call. Like what.
For me: Got CS degree in undergrad, worked as a SWE full time for for 2 years, did OSS and some consulting work in med school (0-20hrs/week). Now my work is primarily clinical as a resident ~65 hrs/week, with just 5-10hrs/week on programming.
It might be a prompting skill issue on my end though. Maybe if I cared a bit more I could make provide a tool to the LLM to calculate contrast between two colors and provide it as a tool?
https://www.healthit.gov/sites/default/files/2018modelprivac...
---
The concept of creating a standard viral privacy policy that dictates how your data must be access/stored/secured is super intriguing. I'm imagining a future where this is combined with FHIR - you can link individual FHIR resources to a privacy policy/license, maybe sign the resources so they can't be easily modified. Downstream apps would need to respect the policies before using the data.
I do wonder who would actually push for this though - I care, privacy focused patients would care, but getting adoption might be tough?
Today the incentive no longer exists. Instead theres a penalty in the form of reduced Medicare/medicaid reimbursement for practices that don’t comply.
I am currently on my 4th year rotations and I find them to be some of the most educational, important, and interesting ones. YMMV of course