惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

量子位
F
Fortinet All Blogs
小众软件
小众软件
人人都是产品经理
人人都是产品经理
The Cloudflare Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Microsoft Azure Blog
Microsoft Azure Blog
J
Java Code Geeks
有赞技术团队
有赞技术团队
D
DataBreaches.Net
Hugging Face - Blog
Hugging Face - Blog
V
Visual Studio Blog
A
About on SuperTechFans
I
InfoQ
The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
雷峰网
雷峰网
H
Hackread – Cybersecurity News, Data Breaches, AI and More
罗磊的独立博客
C
Check Point Blog
大猫的无限游戏
大猫的无限游戏
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
酷 壳 – CoolShell
酷 壳 – CoolShell
MyScale Blog
MyScale Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
From Pixels to Prescriptions: Building an Autonomous Heal...
Beck_Moulton · 2026-05-23 · via DEV Community

Beck_Moulton

We’ve all been there: you get your blood test results back, see a scary red arrow next to "Alanine Aminotransferase," and immediately spiral into a WebMD rabbit hole. But what if your AI didn't just explain the results, but actually did something about it?

In the world of AI Agents, we are moving past simple chatbots and into the era of Agentic Workflows. Today, we are building a production-grade healthcare agent using LangGraph, Playwright, and OpenAI Functions. This agent doesn't just talk; it analyzes lab reports, identifies anomalies, and autonomously navigates a booking portal to secure an appointment with the right specialist.

By leveraging autonomous healthcare agents and browser automation, we can bridge the gap between diagnostic data and clinical action. If you're interested in how these patterns scale to enterprise levels, I highly recommend checking out the advanced architectural guides over at WellAlly Tech Blog, which served as a major inspiration for this build.


The Architecture: State Machines are the Secret Sauce

Unlike linear chains, healthcare workflows are loopy and conditional. If a lab report is clear, the agent should stop. If an anomaly is found, it needs to search for a doctor. This is why LangGraph is the perfect tool—it allows us to define the agent logic as a state machine.

Agentic Flow Diagram

graph TD
    A[Start: Receive Lab Report] --> B{Analyze Report}
    B -- No Anomalies --> C[Notify User: All Clear]
    B -- Abnormal Indicators Found --> D[Search Specialist Database]
    D --> E[Check Availability]
    E -- Found Slot --> F[Execute Booking via Playwright]
    E -- No Slot --> G[Retry/Backoff]
    F --> H[Confirm Appointment to User]
    C --> I[End]
    H --> I

Enter fullscreen mode Exit fullscreen mode


Prerequisites

To follow this advanced tutorial, you'll need:

  • LangGraph: For the stateful orchestration.
  • OpenAI GPT-4o: For reasoning and function calling.
  • Playwright: To automate the browser for the booking process.
  • Python 3.10+

Step 1: Defining the Agent State

In LangGraph, the "State" is a shared memory that every node in your graph can read from and write to.

from typing import TypedDict, List, Annotated
from langgraph.graph import StateGraph, END

class AgentState(TypedDict):
    report_text: str
    anomalies: List[str]
    specialist_type: str
    appointment_status: str
    requires_action: bool

Enter fullscreen mode Exit fullscreen mode


Step 2: The Analysis Node (OpenAI Functions)

We use OpenAI's function calling to extract structured data from raw medical text. We want the LLM to decide if the patient needs to see a doctor.

import openai

def analyze_report_node(state: AgentState):
    # System prompt to identify medical anomalies
    prompt = f"Analyze this lab report: {state['report_text']}. Identify abnormalities."

    # In a real scenario, use structured output/Pydantic
    response = openai.chat.completions.create(
        model="gpt-4o",
        messages=[{"role": "user", "content": prompt}],
        functions=[{
            "name": "report_findings",
            "parameters": {
                "type": "object",
                "properties": {
                    "anomalies": {"type": "array", "items": {"type": "string"}},
                    "specialist": {"type": "string"}
                }
            }
        }]
    )

    # Update state
    findings = response.choices[0].message.function_call.arguments
    return {
        "anomalies": findings['anomalies'],
        "specialist_type": findings['specialist'],
        "requires_action": len(findings['anomalies']) > 0
    }

Enter fullscreen mode Exit fullscreen mode


Step 3: The Action Node (Playwright Browser Automation)

When an API isn't available for a legacy hospital portal, we use Playwright. This node simulates a human clicking through a booking system.

from playwright.sync_api import sync_playwright

def book_appointment_node(state: AgentState):
    if not state["requires_action"]:
        return {"appointment_status": "No appointment needed."}

    with sync_playwright() as p:
        browser = p.chromium.launch(headless=True)
        page = browser.new_page()
        page.goto("https://hospital-portal.example.com/booking")

        # Select department based on specialist_type extracted by LLM
        page.select_option("#dept-select", label=state["specialist_type"])
        page.click("#find-first-available")

        # Finalize booking
        page.click("button:has-text('Confirm')")
        booking_ref = page.inner_text("#confirmation-id")

        browser.close()
        return {"appointment_status": f"Booked! Ref: {booking_ref}"}

Enter fullscreen mode Exit fullscreen mode


Step 4: Wiring the Graph

Now, we connect the nodes. The conditional_edge is what makes this "Agentic."

workflow = StateGraph(AgentState)

# Add Nodes
workflow.add_node("analyzer", analyze_report_node)
workflow.add_node("booker", book_appointment_node)

# Set Entry Point
workflow.set_entry_point("analyzer")

# Logic: If anomalies found -> book, else -> END
workflow.add_conditional_edges(
    "analyzer",
    lambda x: "booker" if x["requires_action"] else END
)

workflow.add_edge("booker", END)

# Compile
app = workflow.compile()

Enter fullscreen mode Exit fullscreen mode


🚀 The "Official" Way: Ensuring Medical Safety

Building health-tech agents isn't just about cool code; it’s about reliability and safety. When moving from a hobby project to a production system, you need to consider HIPAA compliance, "Human-in-the-loop" (HITL) checkpoints, and prompt versioning.

For a deep dive into production-ready Agentic patterns and how to handle edge cases like "no available slots" or "multi-agent consensus" in medical AI, check out the comprehensive guides at WellAlly Tech Blog. They offer incredible insights into building robust AI systems that don't fail when lives (or schedules) are on the line.


Conclusion

We just built a system that:

  1. Understands complex medical data.
  2. Reasons about the necessity of medical intervention.
  3. Acts by navigating a real-world web interface.

This is the power of LangGraph combined with Playwright. We aren't just building "chatbots" anymore; we are building digital employees capable of handling end-to-end workflows.

What are you building with Agents? Drop a comment below or share your thoughts on the future of autonomous health-tech!