What we learned building healthcare integrations for the past year
Over the past year, the team built healthcare integrations with EHRs and payor portals lacking real APIs, leading to challenges in reliability and scalability. They shifted from AI-driven browser agents to more deterministic methods using Playwright and build-time AI for script generation. The focus is now on maintainable, engineer-controlled automation with selective AI assistance for edge cases.
- ▪Integrating with healthcare systems was difficult due to fragmented data, missing APIs, and limited FHIR functionality.
- ▪The team moved from runtime AI agents to using Playwright with build-time AI, leveraging Claude Code to generate and debug scripts.
- ▪Direct network request integrations were faster and more reliable but sometimes blocked by bot detection systems.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3908239) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Michael Kronovet Posted on May 1 What we learned building healthcare integrations for the past year #api #backend #discuss #softwareengineering Over the past year we’ve been building integrations with EHRs and payor portals that don’t expose real APIs. It’s been a pain in the ass. Thought it’d be helpful to share what we’ve learned and also hear from others what’s worked well or hasn’t worked for them.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
