Skip to main content

​
Agent Collaborative Workflows

Because agents are services, they can collaborate by sharing memory and delegating tasks.

​
Example Collaboration Workflow

1

Primary Agent Interaction

A primary agent handles the clinician conversation and gathers clinical information.
2

Task Delegation

The primary agent hands off billing code suggestions to a specialized background agent.
3

Shared Memory Access

Both agents access a shared core memory, ensuring that the billing agent knows what procedures were discussed earlier.
4

Result Integration

The background agent’s recommendations are integrated back into the primary conversation flow.
Collaboration is managed via tool calls and memory updates rather than direct message passing, reducing complexity and improving reliability.
Clinia’s Agents as a Service model empowers organizations to build modular, reusable agents that can scale across applications. Combined with stateful memory and flexible tool integration, it lays the foundation for a robust agentic platform tailored for healthcare.
Traditionally, building an agent meant embedding it directly into an application. Clinia takes a different approach: agents are services. You define an agent once and then interact with it through a REST API. This service model simplifies deployment, promotes reusability and centralizes state management.

​
Defining Agents as Services

An agent service is identified by an agent_id and exposes a simple endpoint: 
POST /agents/{agent_id}/messages
Your application sends user messages to this endpoint, and the agent returns responses. The underlying agent may call tools, update its memory or collaborate with other agents—all of this happens behind the service boundary.

​
Benefits of the Service Model as a Service

Single Point of Deployment

You define the agent once on Clinia’s platform and then use it across multiple applications (e.g., an EHR interface, a clinician chat app or a scheduling bot). Consistent behaviour is guaranteed because all calls go through the same service.

Shared Core Memory

Multiple agents can share the same core memory, enabling collaboration. A background agent that updates billing codes can access the same clinical context as the primary agent that communicates with clinicians.

Template-driven Setup

Clinia supports templates for common agent types (e.g., general practice assistant, scheduling assistant). Templates provide predefined persona memories and tool configurations, speeding up development while allowing customization.
Shared memory also allows agents to coordinate through long‑term knowledge rather than ad‑hoc message passing.

​
Agent Types

Clinia recognizes several classes of agents, each optimized for different workloads:
  • Background Agents
  • Low-latency Agents
  • Workflow Agents

​
Background Agents

  • 🔄 Run in the background and perform tasks asynchronously
  • 📋 Handle tasks such as filling out forms or generating summaries
  • 🤝 Share memory with primary agents but operate independently
Perfect for automated workflows that don’t require direct user interaction.
These categories are not mutually exclusive; you can combine their characteristics to suit your use case. The common thread is that all agents are service endpoints with persistent state, tool orchestration and configurable personas.
⌘I