Healthcare Billing Automation: Extract Data From EOBs & Medical Bills

Explanation of Benefits (EOBs)Medical billsSuperbillsItemized statements

The problem

Billing teams manually re-key claim numbers, billed/allowed/paid amounts, and procedure codes from EOBs and provider bills into billing or patient-accounting systems. Reconciling payer adjustments by hand is slow, and it gets harder to keep accurate at volume.

How Dokyumi solves it

Define a schema for the EOB or medical-bill fields you need — claim number, provider, service date, billed/allowed/paid amounts, patient responsibility, and procedure codes — then select it on the shared extraction endpoint. A successful request returns structured data with confidence and validation details; resolve review results before downstream use.

Because you define the schema, you can limit which fields appear in structured output. The full uploaded source and OCR data still follow Dokyumi’s documented security and retention process; review /security and /privacy before sending sensitive data.

For handling of protected health information, see our security page — Dokyumi uses a HIPAA-aware architecture, and a BAA is available on the Enterprise plan.

Example schema and result

A real schema shape for healthcare billing documents, and the JSON you get back from one extraction.

Example schema definition

{
  "slug": "eob-parser",
  "name": "EOB Parser",
  "description": "Extracts claim and billing data from Explanation of Benefits statements",
  "ocr_mode": "standard",
  "fields": [
    {
      "key": "claim_number",
      "type": "string",
      "required": true
    },
    {
      "key": "provider_name",
      "type": "string",
      "required": true
    },
    {
      "key": "service_date",
      "type": "date",
      "required": true
    },
    {
      "key": "billed_amount",
      "type": "currency",
      "required": true
    },
    {
      "key": "allowed_amount",
      "type": "currency",
      "required": false
    },
    {
      "key": "paid_amount",
      "type": "currency",
      "required": false
    },
    {
      "key": "patient_responsibility",
      "type": "currency",
      "required": false
    },
    {
      "key": "cpt_codes",
      "type": "array",
      "required": false
    }
  ]
}

Result — POST /api/v1/extract

{
  "id": "91ebdb7e-efc3-43c1-b8fd-19b929d3c3d4",
  "status": "completed",
  "request_id": "861aec32-4511-4850-b254-b17dfc89594a",
  "schema": "eob-parser",
  "data": {
    "claim_number": "CLM-2026-771234",
    "provider_name": "Lakeside Family Medicine",
    "service_date": "2026-05-08",
    "billed_amount": 480,
    "allowed_amount": 310,
    "paid_amount": 248,
    "patient_responsibility": 62,
    "cpt_codes": [
      "99214",
      "90471"
    ]
  },
  "confidence": {
    "claim_number": 0.99,
    "billed_amount": 0.98,
    "cpt_codes": 0.93
  },
  "validation": {
    "valid": true,
    "errors": [],
    "low_confidence_fields": []
  },
  "meta": {
    "processing_time_ms": 1340,
    "page_count": 2,
    "credits_used": 1,
    "ocr_cached": false,
    "model": "anthropic/claude-sonnet-4"
  }
}

How it works

Define the fields you need

Claim number, amounts, procedure codes — only what your billing workflow actually uses.

Call the shared endpoint

Send the file with your schema slug.

Submit EOBs and medical bills

PDF or scanned image, one API call.

Review, then reconcile

Inspect confidence and validation details before mapping structured data into your billing or patient-accounting system.

Healthcare Billing FAQ

Is Dokyumi HIPAA-compliant?+

Dokyumi is built with a HIPAA-aware architecture: encryption in transit and at rest, access controls, and schemas designed to help you minimize what you collect. A Business Associate Agreement (BAA) is available on the Enterprise plan — contact hello@dokyumi.com before sending PHI. See /security for details.

Can I limit which patient fields get captured?+

You design the schema, so omitted fields are not requested in the structured extraction output. The uploaded source file and OCR data may still be stored under the current retention process; review /security and /privacy and confirm requirements before sending PHI.

Does Dokyumi integrate with my EHR or billing system?+

Not with a native pre-built connector today. Direct API extractions return JSON in the response, and upload-site submissions can use a configured webhook for your integration.

Can it read handwritten superbills?+

OCR accuracy on handwriting is limited compared to typed or printed documents; typed EOBs and itemized statements extract most reliably.

What happens with a low-confidence field, like a hard-to-read procedure code?+

A successful response can return review status. Inspect both validation errors and low-confidence fields, then route the affected result for manual review instead of trusting it blindly.

Stop re-keying explanation of benefits (eobs) by hand.

25 free credits every month — one credit covers a document up to 5 pages, with no credit card or AWS account required.