logoalt Hacker News

Advancing computer-use agents for healthcare teams

23 points • by gmays • today at 6:26 PM • 15 comments • view on HN

Comments

dumbmrblah • today at 9:12 PM

Speaking of the physician who extensively uses Opus and Sol (through the appropriate HIPAA channels) I do worry about overutilization of resources. Both tools regularly recommend expensive testing that may not be clinically indicated. This consumes a finite pool of resources (we keep getting more patients, but we're not getting more MRI machines)

The underlying issue is that these models tend to shotgun orders because, at their core, they want more data. More data isn't always better for the patient: it generates incidentalomas, follow-up imaging, and downstream workups etc that carry their own risks and costs.

I do like the agent triaging in basket messages, though. That's pretty clever. Where it breaks down is when things get super specialized. This works well for primary care, etc. Maybe not in your ultra/hyper specialized setting.

➕ show 1 reply
w10-1 • today at 8:27 PM

> Healthcare is fragmented, and teams often need to move information between systems manually before a patient can get care

This actually is the main issue, but the cause is partly EPIC and partly the federated nature of health care, where each practice (even within a health system) can have different procedure for qualifying and submitting referrals.

But their use-case of AI fielding emails or listening and summarizing is a different issue: providers are being forced on pain of losing their jobs to cut the time they take with patients.

I can see how AI could relieve pressure in both cases, but that would fix nothing. If it's easier to complete referrals, referrals will become more complex, because that's how they manage their workload. If providers can be force into 20-minute visits, they'll be forced into 10-minute visits via triage.

When AI is deployed to improve quality and not efficiency, it can only make things worse.

When it's deployed for quality, it can actually help - injecting an additional test for a low-traffic diagnosis, walking generalists through complex diagnosis algorithms, etc.

➕ show 1 reply
User1988_m • today at 7:58 PM

The problem isn't so much that the AI summarizes, but that the summary doesn't cite the source. The correct approach would be for the phrase in the draft to link to the original document; for example, mentioning that it's a note from a specific date, or that the image is from a particular source, so the doctor can quickly verify what really matters.

le-mark • today at 8:03 PM

> lower back pain

Lol in 20 years no Dr ever has taken my back pain seriously. This ai is already delivering better care!

➕ show 1 reply
ActionHank • today at 7:58 PM

Best part is that we are a hair away from some middleman reselling this to hospitals to offload liability and selling access to health insurance orgs.

OAI and ANT really are leading the charge to pull us into the worst timeline.

➕ show 1 reply
sandworm101 • today at 7:31 PM

>> A patient messages their clinician about lower back pain. A computer-use agent reviews the patient’s visit notes, physical therapy records, and prior imaging in the EHR. It drafts an MRI order, an encounter note, and a reply to the patient for the clinician to review. The agent then uses the same records to prepare a prior authorization request in the insurer’s portal for an authorization specialist to review.

Um... can I please have the clinician review my file? Having the AI review my file and present a summary to the clinician/doctor means no human has looked at my actual history, only summaries provided by the AI. This is exactly how things get missed. It is exactly why doctors look at charts no matter what they are told verbally about a patient. Relying on AI to do all the chart reading is asking for trouble.

➕ show 3 replies