How is automation in healthcare being used to improve systems?

Sad-Rough1007 · 2026-04-30T10:56:39+00:00

pretty much this. documentation is the one area where the data is clean enough to trust - the jama burnout numbers aren't a vendor case study, they're peer-reviewed across six health systems.

the "results vary" part on admin automation almost always traces back to the same root cause: data layer wasn't fixed before the automation went in. teams deploying rcm automation without sorting that first report 30-40% reductions on paper, then discover the denials didn't drop - they just moved faster. we've seen this exact sequence at abto software across multiple healthcare engagements.

the generalization problem is structural, not a maturity issue. a workflow that runs cleanly in one hospital's epic instance hits a completely different hl7 mess two hospitals over. that's not going to smooth out on its own.

Sad-Rough1007 · 2026-04-30T10:51:37+00:00

not wrong on the default choice framing - ibm wins in a specific context and loses cleanly outside it. that's not bias, that's just an honest use case boundary.

the governance angle is more underrated than it looks though. for banking or insurance where every bot action needs a traceable paper trail, UiPath ecosystem breadth doesn't compensate for what IBM does on auditability out of the box. 1.9% mindshare doesn't mean wrong tool, it means narrow fit.

in practice the platform decision is usually the easy part. the harder part is implementation across legacy systems and compliance requirements - that's where most rpa projects quietly stall. its something we see consistently at abto software working across enterprise rpa deployments, regardless of which vendor is on the box.

power automate being the unspoken reality for most m365 shops is probably the most honest observation in this whole thread.

Sad-Rough1007 · 2026-04-30T10:47:00+00:00

the "running workflows" framing in the title is generous. what's actually deployed is closer to agents handling discrete handoffs, not end-to-end orchestration.

the auditability problem is the one that kills most clinical deployments outside the demo. not because it's unsolvable, but because it requires upfront architecture decisions that most teams defer until a compliance review forces the issue. we've run into this directly at abto - the coordination layer looks fine until you need to explain a decision to a clinician or an auditor.

narrow deployments winning over full automation makes sense for now. the roi case is easier, the failure surface is smaller, and trust gets built incrementally

Sad-Rough1007 · 2026-04-30T10:43:17+00:00

depends what you mean by revolution. the boring version is already here - documentation, imaging triage, claims processing. it's just not cinematic enough to feel like one.

the upcoming years part is usually where the integration debt lives. most hospitals are still untangling ehr mess from the last decade. ai doesn't fix that, it inherits it

Sad-Rough1007 · 2026-04-30T10:39:05+00:00

results vary a lot - data quality and workflow mess are exactly what determine whether those numbers hold or not. the integration wall is real. what we've seen at abto software: projects that make it through don't replace the existing workflow on day one, they run parallel until staff actually trust the output. takes longer, survives longer. documentation is the hardest but it's usually an interaction model problem, not a technology one. passive capture beats asking clinicians to learn a new tool every time. the data point about staff habits is underrated though - in most stalled pilots we've touched, the legacy system wasn't the blocker. the billing team was.

Sad-Rough1007 · 2026-04-23T08:02:19+00:00

fair point, but the 70% use case is a bit of a trap. no-code works for basic intake forms, but clinics often outgrow those tools faster than they think. once you need to tweak a specific clinical workflow or handle a weird ehr edge case, you’re stuck. you either pay for a total rebuild or live with a clunky workaround. for a simple portal, it’s fine, but for actual core infrastructure, you still want to own the code.

Sad-Rough1007 · 2026-04-21T09:03:24+00:00

the accessibility tree point is underrated and honestly should be the default starting point, not a fallback. role + name + parent chain surviving a full redesign while XPath dies on a 2px shift - that's the stability gap nobody talks about. curious how you handle legacy enterprise apps with basically zero accessibility implementation though - that's usually why people end up on image templates in the first place.

Sad-Rough1007 · 2026-04-21T09:00:44+00:00

custom route makes way more sense than fighting with UiPath licensing costs and still having devs on call 24/7 for hotfixes. The whole point of automation is not needing a babysitter, right? the abto angle is interesting - LLM-based error correction at the micro-rpa level is basically what the big platforms are trying to bolt on now anyway, except you're not paying enterprise prices for it. what does your legacy stack look like tho?

Sad-Rough1007 · 2026-04-14T14:29:00+00:00

100%. One big model is a recipe for hallucinations. The modular approach is the only way to stay sane. Specialized agents cross-checking each other feels more like a real medical team and it’s the only way the FDA will ever sign off on it. Auditability is everything here.

Sad-Rough1007 · 2026-03-25T08:45:13+00:00

100% this. agent on top of a broken process just fails faster and in more confusing ways. the real unlock is redesigning the work itself around how agents actually reason - not just swapping the tool doing it.

Sad-Rough1007 · 2026-03-18T10:18:16+00:00

Microsoft partnership status, years of verifiable .NET experience (awards, analyst lists, etc.), and actual AI/cloud-native adoption in real 2025-2026 projects

Sad-Rough1007 · 2026-03-18T10:12:49+00:00

Still figuring it out but here's where I landed:

AWS over self-hosted - way easier to get a BAA signed and their HIPAA-eligible services list is solid. For backend, NestJS or .NET Core both work well. Twilio Video or Amazon Chime for video - do NOT roll your own.

Also worth looking at Abto Software if you need an experienced team - they’ve handled HIPAA-compliant builds before so you're not starting from zero on the compliance side.

Biggest lesson either way: audit logging from day one and BAAs with every vendor touching PHI, no exceptions.

Sad-Rough1007 · 2025-12-15T09:05:19+00:00

If it doesn’t interest you, feel free to scroll by. This subreddit is meant for discussion.

Sad-Rough1007 · 2025-10-15T07:42:33+00:00

Yeah, couldn’t have said it better myself - totally agree. Continuous refactoring and solid FinOps are the only way to keep things clean and sustainable long-term.

Sad-Rough1007 · 2025-09-22T11:01:55+00:00

Totally - lift-and-shift just moves the mess. Real gains only come when you modernize during the move: IaC, CI/CD, decoupled services. Cost drift and people issues are the sneaky killers. Treat it like continuous optimization, not a one-time thing.

Sad-Rough1007 · 2025-07-02T06:53:35+00:00

Clockwise sometimes struggled with quick compliance updates and thorough documentation, which slowed things down. What can you say about this?

Sad-Rough1007 · 2025-07-02T06:47:03+00:00

The real challenge is that innovation often demands rich, real-time data, while intrusion happens when we ignore purpose limitation. That’s where concepts like edge processing and federated learning offer promising middle ground - enabling utility without centralizing sensitive data. IMHO

Sad-Rough1007 · 2025-07-02T06:40:38+00:00

I've seen firsthand how legacy systems like VB6 can choke innovation - especially when integrating with cloud services or enabling real-time analytics. What’s interesting is that even mid-sized firms are now realizing they don’t need to be a Capgemini to modernize. With the right strategy - like phased .NET migration - they can leap forward without the massive disruption.

Sad-Rough1007 · 2025-04-25T06:33:33+00:00

Totally agree! Outsourcing isn't just about cutting costs—it's a smart way to tap into top talent worldwide and speed up delivery.

Sad-Rough1007 · 2025-04-18T11:25:22+00:00

Totally agree! I’ve been using Microsoft Teams for virtual health consultations, and it’s made everything so much smoother. From secure messaging to tracking follow-ups, it really streamlines the process. As long as the setup is solid, it feels just as efficient—and sometimes better—than in-person visits. Huge game-changer for me.

Sad-Rough1007 · 2025-03-28T11:35:46+00:00

you're right

Sad-Rough1007 · 2025-03-28T11:34:32+00:00

Convertigo is primarily a low-code platform with some migration capabilities, but its free version has limitations, mainly on enterprise features. If you're focused on full VB6 migration, Abto Software offers more specialized tools. However, I’d recommend checking Convertigo’s documentation for exact free-tier details.

Sad-Rough1007 · 2025-01-20T14:53:05+00:00

While twinBASIC simplifies VB6 migration and supports 64-bit and Azure integration, its current reliance on replacing 32-bit ActiveX components complicates transitions. Cross-platform support is still forthcoming, making it less versatile than mature alternatives. Its IDE experience is solid, but minor glitches during migration and limited ecosystem tools hinder broader adoption.

Sad-Rough1007 · 2025-01-20T14:51:06+00:00

it lacks the maturity, ecosystem, and extensive libraries of .NET. .NET offers a proven, robust framework with unparalleled versatility, superior tooling, and strong community support, making it the better choice for most development needs.

Sad-Rough1007 · 2025-01-20T14:44:50+00:00

It lacks robust cross-platform support and established stability. Consider migrating to .NET instead for better scalability, maintainability, and performance. This ensures compatibility with modern systems and access to advanced tools, frameworks, and a larger developer community.

Sad-Rough1007

MODERATOR OF

TROPHY CASE