Healthcare is fragmented, and care teams do much of the work of holding it together. They track down records, re-enter information in various systems, and follow up so patients can get care.
Today we’re sharing improvements to ChatGPT to help move care forward. 🧵
@oshauly These kinds of outside records are absolutely part of the proposal. This is what I often call the "junk drawer" -- all kinds of critical stuff in there and it often doesn't make it out through standardized apis.
AI agents can now reliably review a patient's chart -- but agentic access needs data + workflows beyond USCDI FHIR APIs. Under current rules, a practice can spend months navigating EHR partner fees, IP terms, and app registration. There's a better way... https://t.co/IlhgHpgLpU
I asked Fable 5.2 to make its SVG color choices more friendly to deuteranopes. (I'm color deficient.) We're $25 and 30min into a detailed Python simulation of human vision...
"Maybe model intelligence improvement outstrips my feature appetite such that it's fine" -- for small scale hobby projects, this is exactly how I'm experiencing things
I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.
On the theme of appetite for software being much larger than historical supply... Sometimes I wake up in the middle of the night and can just tell that I won't be able to fall back asleep. At times like these I reach for a podcast (played through headphones), but fumbling with my phone and selecting it and hitting play and adjusting the volume are all little unnecessary movements (and light!) that can disturb my wife. Last night I had Claude build a replacement for the default Android screensaver -- it only activates when my phone is plugged in on its charging stand at night, and when it is active it notices if I turn on my Bluetooth headphones and automatically selects the next unplayed episode of my mindless-content-for-when-I-can't-sleep podcast and plays it after setting the volume to a quiet default. The phone screen, while still black, turns into an interface I can tap once to toggle pause/play, and horizontally drag to adjust volume within a constrained range (0-20% level). This setup supports zero-touch default case, and any manual parts are "wide targets" that I can actuate silently -- and with my eyes closed. I built the whole thing using Claude code on my phone, remoted in to my desktop on the home Wi-Fi which can connect back to my phone over ADB to install, test, and run software on the phone. 15min project!
@NKairinos80602 Yes. (I mean, If the provider is accessing via a user-agent, then the question falls squarely on the relationship and contractual agreements between the provider and the agent they employ.)
ONC finalized the first part of its HTI-5 rule, scaling back its proposed EHR deregulation (still waiting to see what lands re: AI Agents + Info blocking). See article for what was cut or deferred, and how it compares to our SMART Health IT comment letter. https://t.co/07BELPP2Gz
@NKairinos80602 "Can a provider use any agent of their choice to interact with the EHR's UI?" (Today of course, the most common "user agents" -- the technical term for web browsers! -- are fairly dumb but getting smarter fast.)
@NKairinos80602 "Can a provider use any agent of their choice to interact with the EHR's UI?" (Today of course, the most common "user agents" -- the technical term for web browsers! -- are fairly dumb but getting smarter fast.)
@NKairinos80602 The patient and their agent would have the same access to, say, portal capabilities, yes -- but I think the hard questions are in the provider facing space.