Skip to main content

Key Concepts

Understanding the XY Platform starts with Workflows—the central orchestration layer that brings together all other components to achieve end-to-end automation outcomes.

Workflow​

The primary building block of the XY Platform. A Workflow is a sequence of connected steps that automates an end-to-end business process. Workflows orchestrate the four main ingredient types to accomplish complex healthcare operations.

Workflows can operate in three modes:

  • Co-pilot: Attended mode with human oversight at each step
  • Supervised: Automated execution with HitL checkpoints for exceptions
  • Fully Automated: Unattended execution with minimal human intervention

Examples: Invoice processing, claims submission, patient intake, denial management.

Workflow Ingredients​

Workflows are composed of four primary ingredient types that work together:

Agents​

Task-focused, AI-enhanced services that can reason, make decisions, and perform specialized work within workflows. Agents combine domain expertise with AI capabilities to handle complex healthcare operations.

Key characteristics:

  • Configurable for specific healthcare tasks
  • Can reference policies, templates, and knowledge bases
  • Handle both structured and unstructured data
  • Make intelligent decisions within defined parameters

Examples: Claims Management, Data Entry & Transcription, Scheduling, Missing Information Remediation.

Integrations​

Connections that allow workflows to interact with external systems and services. Integrations enable workflows to pull data from, push data to, and synchronize with your existing healthcare infrastructure.

System categories:

  • EHR/Practice Management: DrChrono, eClinicalWorks, Elation
  • Billing: CollaborateMD and other revenue cycle systems
  • Patient Engagement & Communications: Spruce and other communication platforms
  • Collaboration: Slack, Microsoft Teams
  • Productivity: Gmail, Outlook
  • Storage: Google Drive, OneDrive

Files​

Documents, images, and other file assets that workflows can consume as inputs or produce as outputs. Files are processed, analyzed, and transformed by Agents within workflows.

File capabilities:

  • OCR and text extraction from scanned documents
  • Document classification and routing
  • Template-based document generation
  • Secure storage and retrieval
  • Version control and audit trails

Common file types: PDFs, images, Word documents, Excel spreadsheets, HL7 messages, X12 EDI files.

Browser Tasks​

Automated browser interactions initially recorded by the Browser Agent and then executed repeatedly within workflows. Browser Tasks bridge the gap when APIs are unavailable or limited.

Process flow:

  1. Record: Browser Agent captures real user interactions in web portals
  2. Parameterize: Convert recordings into configurable, reusable tasks
  3. Execute: Browser Agent performs the tasks automatically within workflows
  4. Adapt: AI reasoning handles edge cases and unexpected scenarios

Use cases: Portal logins, data entry into web forms, status checks, file downloads/uploads.

Supporting Concepts​

Data​

Information that flows through workflows—retrieved from integrations, extracted from files, generated by agents, or collected from browser tasks. Data is stored securely in the XY Platform backend for use across workflows and future reference.

Data types:

  • Retrieved: Patient demographics, insurance eligibility, claim statuses
  • Processed: Extracted invoice line items, classified documents, validated forms
  • Generated: Reports, summaries, structured outputs, notifications

HitL (Human-in-the-Loop)​

Checkpoints within workflows where human judgment, review, or approval is required. HitL ensures quality and compliance while maintaining automation efficiency.

HitL features:

  • Review queues with clear context and decision options
  • Escalation rules and timeout handling
  • Audit trails of all human decisions
  • Automatic workflow resumption after review

When HitL is used: Low confidence predictions, policy exceptions, high-value transactions, compliance requirements.

Browser Agent​

The specialized component that enables Browser Tasks within workflows. The Browser Agent handles the complete lifecycle from initial recording to production execution.

Core capabilities:

  • Records real browser work with DOM and visual understanding
  • Parameterizes recordings for reuse across different data sets
  • Executes browser tasks reliably with intelligent error handling
  • Adapts to UI changes and unexpected scenarios using AI reasoning

How They Work Together​

A typical workflow combines these ingredients in orchestrated steps:

Example: Claims Processing Workflow

  1. Integration retrieves pending claims from EHR
  2. Agent validates claim data against payer requirements
  3. File processing extracts supporting documentation
  4. Browser Task submits claims through a billing portal
  5. HitL checkpoint for claims flagged with potential issues
  6. Integration updates claim status back in EHR
  7. Data storage maintains audit trail and analytics

This orchestrated approach enables complex healthcare operations to run reliably with appropriate human oversight, system integration, and intelligent decision-making.

Licensing note: Agents are licensed separately; workflows can use any Agents your organization has licensed. See Pricing/Terms for details.