Use case
Use case3 min readBy The Data Workers Team

Value-based care data, run by agents

Contract performance depends on payer files, attribution lists and claims that arrive in different formats every month. Here is how Data Workers runs it instead.

Key takeaways

  • •The problem today. Contract performance depends on payer files, attribution lists and claims that arrive in different formats every month.
  • •What changes. Agents land and map every payer file, reconcile attribution and keep contract metrics governed.
  • •What stays with your people. Settlement inputs: they move shared savings.
  • •The result. Contract performance is visible monthly, not at settlement.

The problem today

Contract performance depends on payer files, attribution lists and claims that arrive in different formats every month.

What changes with Data Workers

Agents land and map every payer file, reconcile attribution and keep contract metrics governed.

The workflow: Data Ingestion agent (get_connector_status) → Schema Evolution agent (detect_schema_change) → Quality Monitoring agent (run_quality_check) → Data Context & Catalog agent (define_business_rule).
Fig. 1:The workflow: Data Ingestion agent (get_connector_status) → Schema Evolution agent (detect_schema_change) → Quality Monitoring agent (run_quality_check) → Data Context & Catalog agent (define_business_rule).

The workflow, step by step

  1. 1.The Data Ingestion agent calls get_connector_status and lands payer files.
  2. 2.The Schema Evolution agent calls detect_schema_change and maps payer layouts.
  3. 3.The Quality Monitoring agent calls run_quality_check and reconciles attribution.
  4. 4.The Data Context & Catalog agent calls define_business_rule and governs contract metrics.

The impact metrics we move

  • •Payer file mapped: from about a week to ~1 h
  • •Attribution reconciled: from about a week to 2 h
  • •Contract scorecard: from about a month to 1 day
Time to complete, current practice (black) vs. with Data Workers (green). Illustrative.
Fig. 2:Time to complete, current practice (black) vs. with Data Workers (green). Illustrative.

What goes on autopilot

  • •Payer files are mapped on arrival, so no month is lost to layout changes.
  • •Contract metrics are governed, so negotiations start from one number.

Where your people stay in charge

Settlement inputs always go to a named approver, because they move shared savings. Everything starts at L1, observing only, and autonomy rises only on evidence.

The pilot

  • •Scope. Two payer contracts at L2.
  • •First week. Agents run at L1, observing only, and show the fixes they would have made, with receipts.
  • •By week two. The routine work above runs on its own; anything sensitive stays with a named approver.
  • •At day 30. We review the impact metrics against your baseline:
  • •Payer file mapped: from about a week to ~1 h
  • •Attribution reconciled: from about a week to 2 h
  • •Contract scorecard: from about a month to 1 day
  • •Cost. Start with a pilot ($7,500 one-time, credited in full against the first year). Scale is from $1,000 a month and Enterprise from $3,000 a month, billed annually, with unlimited seats, no usage meter and no markup on model spend. See pricing.