In this article, I will introduce IRIS FHIR Agents, a multi-agent clinical AI platform built on InterSystems IRIS for Health.
IRIS FHIR Agents demonstrates how InterSystems IRIS for Health can serve as the data, interoperability, analytics, and vector-search foundation for a multi-agent clinical AI application. The platform combines conversational triage, specialist consultation, medication safety, live vital-sign monitoring, FHIR server exploration, and a no-code Agent Builder, all working directly on top of a live FHIR R4 server.
What is IRIS FHIR Agents?
IRIS FHIR Agents is a multi-agent healthcare AI application where specialized LangChain-powered agents work together to solve different clinical tasks.
Every request first passes through a routing agent that determines which specialist should handle it. Depending on the conversation, the platform can:
perform patient triage
analyze medical conditions
detect medication interactions and allergy conflicts
recommend specialist referrals
monitor live patient vitals
retrieve clinical guidelines using InterSystems IRIS Vector Search
query live FHIR resources
create structured FHIR resources
deploy custom clinical agents without writing code
Although users interact with a single chat interface, several AI agents may collaborate behind the scenes.Â
Platform Architecture
The application is built around five major components:
Triage Chat
Analytics Dashboard
Live Vitals Monitor
FHIR Server Agent
Agent Builder
At the center of the application is a routing agent that decides which specialist should answer each request.Â
InterSystems IRIS provides the foundation for the entire application, combining FHIR interoperability, Embedded Python, SQL analytics, and Vector Search within a single platform.
Clinical AI Features
Multi-Agent Orchestration
Instead of asking one LLM to perform every task, I divided responsibilities across multiple specialized agents.
The platform currently includes:
Triage Agent
Specialist Agent
Pharmacy Agent
FHIR Server Agent
Each conversation begins with an LLM router that automatically dispatches requests to the appropriate agent. Users never need to select an agent manually.
Retrieval-Augmented Generation with IRIS Vector Search
To improve the quality of clinical recommendations, I integrated InterSystems IRIS Vector Search.Â
The platform stores 50 clinical guidelines as vector embeddings and retrieves the most relevant passages using VECTOR_COSINE similarity search before generating a response. This allows recommendations to be grounded in trusted medical guidance instead of relying solely on the language model.
Native FHIR Integration
Every agent works directly with a live InterSystems IRIS FHIR server.
The platform retrieves information such as:
Patients
Conditions
Medications
Allergies
Observations
Agents can also create structured FHIR resources, including:
Observation
ServiceRequest
MedicationRequest
This means the AI doesn't simply generate textâit can produce structured clinical data using standard FHIR resources.
Walking Through the Application
Triage Chat
The Triage Chat is the primary interface for interacting with the platform.
A clinician or patient simply describes symptoms in natural language. Behind the scenes, the routing agent selects the appropriate specialist, retrieves the patient's clinical context from the FHIR server, and generates a response grounded in relevant guidelines.
The interface also displays:
Patients can be selected from a searchable list loaded directly from the FHIR server, and conversations support both voice input and multiple languages.
Analytics Dashboard
The Analytics Dashboard provides a real-time overview of clinical data stored in IRIS together with an audit trail of AI-generated activity.
It includes:
Because the dashboard reads directly from the FHIR server, every action performed by the agents immediately becomes visible.
Live Vitals Monitor
Live Vitals Monitor demonstrates how AI agents can react automatically to live clinical events. Patient vital signs are streamed every two seconds using Server-Sent Events. Each reading is immediately written to IRIS as a FHIR Observation. Whenever a critical threshold is detected, the platform automatically launches a triage assessment.
The AI assessment appears in real time together with its urgency level and the guideline references used during reasoning.
FHIR Server Agent
FHIR Server Agent combines two complementary interfaces. The first is a conversational assistant that lets me query live FHIR data in natural language. The second is a visual Capability Explorer that reads the server's CapabilityStatement and displays:
supported resources
interactions
search parameters
resource categories
server capabilities
Because everything is loaded dynamically, the interface always reflects the actual configuration of the connected FHIR server.
Agent Builder
I also wanted to make it easy to extend the platform without modifying the application itself. The Agent Builder provides a no-code interface for creating new clinical agents.
Users can:
The project includes templates for Oncology, Cardiology, Geriatrics, Pediatrics, and Nutrition, but new specialties can be added without changing the application code.
Why InterSystems IRIS for Health?
This project brings together several InterSystems technologies that naturally complement AI applications. InterSystems IRIS for Health provides:
native FHIR R4 interoperability
Embedded Python
SQL analytics
Vector Search
structured healthcare data storage
real-time FHIR read and write operations
Using these capabilities together means the application can retrieve patient data, perform semantic search over clinical guidelines, generate AI recommendations, and store structured clinical resources within the same platform.
Key Takeaways
Building IRIS FHIR Agents allowed me to explore how multiple AI agents can collaborate on top of live healthcare data instead of acting as isolated chatbots.
Using InterSystems IRIS for Health, I was able to combine FHIR interoperability, Vector Search, Embedded Python, analytics, and AI into a single platform that can retrieve patient data, ground recommendations in clinical guidelines, monitor live patient events, and create structured FHIR resources.
While this project is a demonstration, it illustrates how InterSystems IRIS can provide the foundation for multi-agent healthcare applications that move beyond conversation and interact directly with real clinical workflows.Â
Frequently Asked Questions
What is IRIS FHIR Agents?
IRIS FHIR Agents is a multi-agent clinical AI platform built on InterSystems IRIS for Health. It combines patient triage, specialist consultation, medication safety, live vital-sign monitoring, FHIR server exploration, and a no-code Agent Builder. All agents work directly with a live FHIR R4 server and can retrieve or create structured clinical data.
How does the multi-agent architecture work?
Instead of relying on a single AI assistant, the platform uses multiple specialized agents. Every user request is first analyzed by a routing agent, which automatically selects the most appropriate specialist agentâsuch as the Triage Agent, Specialist Agent, Pharmacy Agent, or a custom agent created through the Agent Builder.
How is InterSystems IRIS Vector Search used?
The platform stores clinical guidelines as vector embeddings in InterSystems IRIS and retrieves the most relevant passages using semantic similarity (VECTOR_COSINE). These guidelines are then included in the AI prompt, allowing the agents to generate responses grounded in trusted medical guidance rather than relying solely on the language model.
Does the application work with live FHIR data?
Yes. The application connects directly to a live InterSystems IRIS FHIR R4 server. The agents can retrieve patient information, conditions, medications, allergies, observations, and other FHIR resources in real time.
Can the AI agents write data back to the FHIR server?
Yes. In addition to reading clinical data, the agents can create structured FHIR resources such as Observation, ServiceRequest, and MedicationRequest. This allows AI-generated recommendations and clinical events to become part of the patient's structured healthcare record.