Architecture

Workflow engine meets decision memory

Citron is designed around first-class workflows, recommendations, operator decisions, and outcome tracking rather than isolated copilot surfaces.

Workflow Engine

Workflow definitions encode queue semantics, owners, service expectations, trigger sources, and target outcomes for ASC authorization, coding review, denials, appeals, charge capture, and follow-up work.

Decision Memory

Every recommendation is paired with an explicit human decision. Accepted, escalated, and rejected actions become structured memory for how the operation actually runs.

Outcome Tracking

Citron ties work to what happened next: revenue recovered, denial prevented, turnaround improved, or task rerouted. The point is operational learning, not just suggestion volume.

Operational Intelligence

Existing detectors and copilots become producers in a broader system. The platform can compare queue aging, bottlenecks, recovery pipeline, and workflow health in one place.

Producers

Coding QA, denials, AR, seeded workflow signals, and payer intelligence.

Operating Layer

Task, recommendation, decision, outcome, workflow state, and queue orchestration.

Product Surfaces

Operations Command Center, manager dashboard, workflow engine, and interactive demo.