> For the complete documentation index, see [llms.txt](https://fieldworker.gitbook.io/fieldworker-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fieldworker.gitbook.io/fieldworker-docs/product-guides/ai-agents.md).

# AI agents

## The CareOps™ AI Agent Suite

Welcome to the CareOps™ AI Agent Suite. This product marks our evolution from a traditional "system of record" into an interconnected ecosystem of independent, specialized digital teammates. The CareOps™ Suite is engineered with a modular, plug-and-play architecture. Agencies can deploy these autonomous agents individually to solve targeted operational bottlenecks or run them in tandem as a unified, end-to-end intelligence workforce. By automating administrative overhead, this suite protects agency revenue, eliminates employee burnout, and redirects valuable human hours back to direct client care.

### Core Architecture: Standalone Simplicity, Tandem Power

Unlike rigid, all-or-nothing software packages, the CareOps™ Suite treats every agent as an independent operator.

* The Standalone Option: An agency can deploy a single agent (such as the Ingestion Agent) to address one specific operational friction point without changing the rest of their tech stack and workflows.
* The Tandem Option: When deployed together, the agents establish an automated data loop. One agent’s output automatically becomes the context and trigger for the next, scaling your operational capacity without adding administrative staff.

### The CareOps™ Agent Roster

```
   ┌─────────────────────────────────────────────────────────┐
   │                THE CAREOPS™ AGENT ROSTER                │
   └─────────────────────────────────────────────────────────┘
                               │
         ┌─────────────────────┼─────────────────────┐
         ▼                     ▼                     ▼
 ┌───────────────┐     ┌───────────────┐     ┌───────────────┐
 │ Agent 1:      │     │ Agent 2:      │     │ Agent 3:      │
 │ Ingestion &   │     │ Ambient Care  │     │ Pre-Claim     │
 │ Onboarding    │     │ Documentation │     │ Compliance    │
 └───────────────┘     └───────────────┘     └───────────────┘
         │                     │                     │
         └─────────────────────┼─────────────────────┘
                               ▼
                       ┌───────────────┐
                       │ Agent 4:      │
                       │ Trend & Care  │
                       │ Forecaster    │
                       └───────────────┘
```

#### Agent 1: The Plan Ingestion & Onboarding Specialist

* Role: Instantly provisions complete digital workspaces from dense state documentation.
* How it works: The [agent](/fieldworker-docs/fundamentals/pages/ingestion-and-onboarding-agent.md) reads uploaded NJ DDD care plans (ICP/NJISP) and Service Delivery Records (SDR). It executes an automated, 13-step parsing and validation pipeline to build out the client workspace.

<figure><img src="/files/TTCUhfQjDO1Yql4mO4xP" alt=""><figcaption></figcaption></figure>

* Core Intelligence: It uses an intelligent, non-destructive merge logic to layer new authorization details on top of existing profiles without risking data loss or creating duplicate entries. It matches individuals by their unique DDD ID, cross-references insurance data to pre-vetted billing networks, and auto-creates required shift tasks linked directly to state-approved outcomes.

#### Agent 2: The Ambient Care Documentation Assistant

* Role: Relieves frontline Direct Support Professionals (DSPs) of typing shift notes.
* How it works: This voice-first agent securely captures natural spoken summaries from caregivers at the end of a shift.
* Core Intelligence: The agent filters out filler words, translates spoken summaries into clear English narrative strings, and automatically structures the notes. It maps the caregiver’s observations directly to the Individualized Service Plan (ISP) outcomes established by Agent 1.

#### Agent 3: The Pre-Claim Compliance Guard

* Role: Acts as a defensive shield against billing rejections and retroactive audit clawbacks.
* How it works: Running silently in the background, this agent audits daily documentation logs across multiple operational sections before billing files are sent to the clearinghouse.
* Core Intelligence: It continuously cross-references daily care notes, EVV (Electronic Visit Verification) data, scheduled shift hours, and state Medicaid parameters. If a caregiver mentions a specific behavioral intervention in their note but the corresponding behavioral form remains uncompleted, the agent flags the gap for review before submission.

#### Agent 4: The Trend & Care Forecaster

* Role: Identifies subtle shifts in patient well-being to enable proactive care coordination.
* How it works: This analytical module scans longitudinal shift notes, health data, and incident logs over multi-week windows.
* Core Intelligence: Rather than waiting for a crisis, smaller, fine-tuned models detect micro-trends—such as a gradual reduction in mobility, a sudden shift in sleep patterns, or a slow increase in targeted behaviors—and flag them for case managers to trigger early care interventions.

### Benefits

#### For the Agency: Operational Scale & Revenue Defense

* Eliminate Billing Slip-Ups: By cross-checking procedure codes against claims-supported insurance data right at onboarding, the suite prevents formatting and data entry errors from reaching the clearinghouse.
* Bulletproof Audit Readiness: Every action taken by an agent triggers an unalterable transaction record. Your system maintains a continuous, software-generated proof-of-origin for all workspaces and compliance decisions.
* Institutional Memory Protection: Staff turnover won't break your workflow. The suite standardizes data processing, ensuring client records remain clean and consistent regardless of team transitions.

#### For the Employee: Frictionless Workflows & Burnout Relief

* No Software Overhead: Frontline caregivers and intake coordinators are care experts, not data operators. The suite hides complex tasks—such as full-text database lookups for medication verifications—behind a clean, one-click interface.
* Instant Shift Clarity: Caregivers no longer have to dig through lengthy state files. The suite translates dense documentation into clear, outcome-focused tasks right inside their shift log layouts.
* Mission Realignment: By shifting administrative burdens away from humans, your workforce can refocus its energy on what matters most: human connection and high-quality care.

### Compliance Guardrails & Governance

The CareOps™ Suite operates under a strict [Human-in-the-Loop](/fieldworker-docs/fundamentals/concepts/human-in-the-loop.md) architecture. In the healthcare and social services sectors, autonomous decision-making presents unacceptable regulatory and operational risks.

Therefore, our agents do not execute clinical or billing changes entirely on their own. Instead, they function as high-powered assistants that compile data, detect discrepancies, and present structured recommendations or drafts. A human coordinator, administrator, or clinician must explicitly review, modify, and sign off on any agent-generated output, ensuring full compliance with state accountability mandates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fieldworker.gitbook.io/fieldworker-docs/product-guides/ai-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
