Terminology & Glossary

Core Platform Concepts

Agent — Configurable, AI-enhanced service that performs work; may invoke tools, files, and models.
Workflow — Ordered steps combining Agents, tools, integrations, and model calls.
Tool — A callable function/integration used by Agents (API, DB, search, file IO).
Integration — A connection to a third-party system (EHR, billing, engagement, collaboration, storage, productivity).
Files — Source documents (PDF, DOCX, images) and outputs (CSV/JSON/PDF) used by Agents.
HitL (Human-in-the-Loop) — Review/approval path for exceptions; resumes after fix.
Browser Agent — UI automation that records user actions and replays them robustly with intelligent web interaction.
Browser Task — Automated browser interactions recorded by the Browser Agent and executed repeatedly within workflows.
Step — A single action or decision point within a workflow (agent step, integration step, decision step, human step).
Instance — An active, running copy of a workflow processing real data; created from templates when triggered.
Template — Pre-built, reusable workflow pattern for common tasks that can be used as-is or customized.
Queue — Review interface for managing items requiring human review, approval, or intervention in HitL workflows.
Workspace — Organization-level container for users, workflows, agents, integrations, and files in the XY Platform.
Integration Instance — A specific authenticated connection to an external system; multiple instances of the same integration type can exist.
Capability — A specific operation that an integration can perform (read, write, configure); can be enabled or disabled per instance.
Orchestrator — The workflow execution engine that manages step dependencies, retries, and data flow through workflows.
DAG (Directed Acyclic Graph) — The underlying structure of workflows showing step dependencies and execution order.

Execution Modes

Co-pilot — Attended execution mode with human oversight at each step; manual initiation with full visibility.
Supervised — Automated execution with HitL checkpoints for exceptions; balances automation with human judgment.
Fully Automated (Autopilot) — Unattended execution from start to finish; triggered by schedules, events, or API calls.
Attended — Execution mode where a human is present to monitor and intervene if needed.
Unattended — Execution mode that runs automatically without human presence.
Headless — Browser execution mode without a visible user interface, used for automated workflows.

Browser Agent & Automation

Record — The process of capturing real user interactions in web portals using the Browser Agent.
Parameterize — Converting recorded browser interactions into configurable, reusable tasks with variable inputs.
Selector — Element identification method used by the Browser Agent to locate and interact with page elements.
XY-ID — Unique identifier assigned to DOM elements by the Browser Agent for reliable element targeting.
DOM (Document Object Model) — The structured representation of a web page that the Browser Agent uses to understand page structure.
Selector Robustness — The ability of selectors to reliably find elements even when page structure changes.
Page Capture — Screenshot or document capture of a web page for review, documentation, or processing.

Data & Variables

Variable — Named storage for data that flows through workflows; can be simple values, objects, or arrays.
Memory Variable — Persistent state storage that maintains data across workflow steps and iterations.
Workflow Field Variable — Input variables passed to a workflow when it starts execution.
Variable Substitution — Using {{variable_name}} syntax to reference stored values in workflow steps.
Data Flow — The movement of information through workflow steps via inputs, variables, transformations, and outputs.
Transformation — Modifying data as it flows through workflows (extract, format, validate).

Workflow Execution

Idempotency — Property allowing workflows to be safely re-run without duplicating work or causing problems.
Retry — Automatic attempt to recover from temporary failures by re-executing a failed step.
Fallback — Alternative processing path taken when the primary path fails.
Error Handling — Built-in mechanisms for managing failures including retries, fallbacks, notifications, and logging.
Dead Letter Queue — Special queue for items that fail all retry attempts and require investigation.
Breakpoint — Debugging pause point in workflow execution for manual verification or data inspection.
Test Mode — Execution environment for testing workflows with sample data before production deployment.
Sample Data — Test data used to validate workflow behavior in test mode.
Synthetic Data — Artificially generated test data for workflow testing and development.

AI & Agents

Confidence Score — AI-provided measure of certainty for agent outputs; low-confidence items route to human review.
Agent Communication Protocol (ACP) — Standardized data exchange format ensuring consistent input/output structure across all agents.
AI Assistant — Chat interface that provides intelligent help with page analysis, workflow optimization, and automation guidance.
XY Assistant — XY's built-in AI assistant accessible via the Browser Agent, web app, or API.
Pattern Recognition — AI capability to identify trends in denials, errors, or inefficiencies from historical data.
Adaptive Learning — Agent capability to improve accuracy over time by learning from corrections and feedback.

Healthcare Terminology

EHR (Electronic Health Record) — Digital version of a patient's medical history maintained by healthcare providers.
PM (Practice Management) — Software system for managing day-to-day operations of a medical practice.
RCM (Revenue Cycle Management) — The financial process of managing claims, payments, and revenue from patient registration to final payment.
EOB (Explanation of Benefits) — Statement from insurance explaining what was paid, denied, or requires patient payment.
ERA (Electronic Remittance Advice) — Electronic version of EOB sent by payers to providers.
EDI (Electronic Data Interchange) — Standard format for electronic exchange of healthcare data.
837 — EDI transaction set for healthcare claims (837P for professional, 837I for institutional).
ICD-10 — International classification system for diagnosis codes used in healthcare claims.
CPT (Current Procedural Terminology) — Standardized medical code set for procedures and services.
HCPCS (Healthcare Common Procedure Coding System) — Code set for medical procedures, supplies, and services.
NPI (National Provider Identifier) — Unique 10-digit identifier for healthcare providers.
Clearinghouse — Service that validates, formats, and routes healthcare claims between providers and payers.
Denial — Claim rejection by a payer requiring correction, appeal, or write-off.
Appeal — Process of challenging a claim denial to seek payment.
PHI (Protected Health Information) — Individually identifiable health information protected under HIPAA.
HIPAA (Health Insurance Portability and Accountability Act) — Federal law protecting patient health information privacy and security.

Security & Compliance

Keystore — Secure storage system for API keys, credentials, and authentication tokens.
Encryption — Process of encoding data to protect it from unauthorized access.
At Rest — Data encryption for stored data in databases and file systems.
In Transit — Data encryption for data being transmitted over networks.
SSO (Single Sign-On) — Authentication method allowing users to access multiple systems with one set of credentials.
MFA (Multi-Factor Authentication) — Security method requiring multiple verification factors for access.
SAML (Security Assertion Markup Language) — XML-based standard for exchanging authentication and authorization data.
OAuth — Authorization protocol for secure API access without sharing passwords.
RBAC (Role-Based Access Control) — Access control method where permissions are assigned based on user roles.
Least Privilege — Security principle of granting users minimum necessary permissions.
Separation of Duties — Security principle preventing conflicts of interest through appropriate role separation.
Break-glass — Emergency access procedure for urgent situations requiring elevated permissions.
Data Retention — Policy defining how long data is stored before automatic deletion.
PHI Detection — Automated identification of protected health information for compliance handling.
Audit Trail — Complete log of all user actions, system events, and data changes for compliance and security.
SOC 2 — Security compliance standard for service organizations handling customer data.
Compliance — Adherence to regulatory requirements such as HIPAA, SOC 2, and other healthcare regulations.

Integrations & APIs

API Key — Unique identifier for authenticating API requests to external systems.
Token — Authentication credential used for API access, often with expiration and refresh capabilities.
Credential — Authentication information (username, password, API key, token) for system access.
Rotation — Process of periodically updating credentials for security purposes.
Expiration — Time limit after which credentials become invalid and must be renewed.
Webhook — HTTP callback mechanism for real-time event notifications from external systems.
Rate Limiting — API restriction on number of requests per time period to prevent abuse.
Connection Pooling — Resource optimization technique for managing multiple API connections efficiently.
Sync Frequency — How often XY checks for new or updated data from integrated systems (real-time, hourly, daily).
Batch Processing — Processing multiple items together in a single operation for efficiency.

Files & Documents

OCR (Optical Character Recognition) — Technology that extracts text from scanned documents, images, and PDFs.
Document Classification — Automated categorization of documents by type (invoice, claim, referral, etc.).
Document Routing — Automated direction of documents to appropriate workflows or queues based on classification.
Template-based Generation — Creating documents using predefined templates with variable substitution.
Version Control — Tracking and managing different versions of files and documents.

Notifications & Communication

WebSocket — Real-time bidirectional communication protocol for live status updates.
Polling — Periodic checking for updates by repeatedly querying a system.
Toast Notification — Temporary alert message displayed in the user interface.
Badge — Visual indicator (usually a number) showing count of pending items or notifications.
Modal — Dialog window that requires user interaction before continuing.
Digest — Batched summary of notifications delivered at scheduled intervals.
Escalation — Automatic increase in notification priority or routing to supervisors when items remain unaddressed.
Alert Fatigue — Problem of too many notifications reducing user attention and response effectiveness.
Deep-linking — Direct navigation to specific pages or content from notifications.
Context-aware — Notifications that provide situation-specific information and actionable next steps.

User Management

User Role — Access level assigned to users (Viewer, Editor, Admin) determining permissions.
Viewer — Read-only role that can see workflows and data but cannot make changes.
Editor — Role that can create and modify workflows, agents, and integrations.
Admin — Administrative role with full access including user management and system configuration.
Session — Active user login period with defined timeout and access permissions.
Timeout — Automatic session expiration after period of inactivity for security.

Development & Deployment

YAML — Human-readable data format used for workflow configuration under the hood.
DirectFlow — XY's workflow execution engine that converts Python-like syntax to YAML steps.
Staging — Test environment for validating workflows before production deployment.
Production — Live environment where workflows process real business data.
UAT (User Acceptance Testing) — Final testing phase where end users validate workflows meet requirements.
Version Control — System for tracking workflow versions, comparing changes, and rolling back if needed.
Rollback — Reverting to a previous workflow version if issues are discovered.
Deploy — Publishing a workflow to production for live use.

Monitoring & Analytics

Logging — Recording of all workflow actions, decisions, and system events for debugging and audit purposes.
Performance Metric — Measurable indicator of workflow efficiency, accuracy, or throughput.
Throughput — Rate at which workflows process items (items per hour/day).
Accuracy Rate — Percentage of correct outputs or decisions made by agents.
Latency — Time delay between action initiation and completion.
Bottleneck — Performance constraint that limits overall workflow speed or capacity.
Processing Trend — Pattern showing how workflow performance changes over time.
Error Pattern — Recurring failure types that indicate systematic issues requiring attention.

Agent Types

Data Entry & Transcription Agent — Extracts data from files, emails, and faxes, then populates systems.
Claims Management Agent — Assembles, optimizes, and submits claims with fewer denials.
Scheduling Coordinator — Manages appointments, reduces no-shows, and optimizes schedules.
Knowledge Base Agent — Enables teams to search and chat with organizational knowledge and files.
Payment Posting Agent — Determines, executes, and tracks vendor payments across systems.
Patient 360 Agent — Builds and updates unified patient profiles from multiple data sources.
Patient Cost Estimator — Combines procedure, insurance, and pricing data to generate cost estimates.
Missing Information Agent — Ensures accurate and complete data through cross-system reconciliation.