Unified request, queue, review workspace, approval, discard, and regeneration flow for every Operix AI surface.
RedactionQueued jobsReview workspaceROI
Workflow
How This Flow Lands In The Product
1
Request draft
Staff trigger an AI action from a specific screen such as Smart Insights, Appointments, Patients, Consultations, Pharmacy, or Billing.
2
Build minimum context
Operix extracts only the smallest structured context needed for the capability.
3
Redact before egress
PHI is replaced with deterministic placeholders before outbound provider calls.
4
Queue and persist
Provider calls run in the queue and persist into ai_runs with prompt version, model, usage, latency, and safety flags.
5
Review and decide
Staff can approve, discard, copy, or regenerate the draft; stale drafts are flagged when the source changed.
Details
Product Surface
AI is now a coherent product layer instead of scattered buttons.
Dashboard summary cards and clinic scorecard backlog signals
Smart Insights daily, weekly, and executive briefs
AI Run Log Review console
AI Settings control plane
Module-level request actions with freshness, redaction, and review state badges
Source summary versus draft preview, reviewer comments, feedback tags, reviewer disposition and rubric metadata, exportable drafts, and regenerate lineage in the run log
Optional handoff into communications or clipboard workflows without auto-send or auto-write
Run log brings pending review, stale, failed, and approved drafts into one console.AI settings exposes provider health, capability matrix, retention, and usage.
Details
Capabilities In v1
The current release deliberately favors high-utility drafts over open-ended chat.