Trusted by teams turning documents into production data
Insurance
Summary of Benefits and Coverage (SBC) documents standardize how health plans present coverage details. While federally mandated, carrier implementations vary in layout and terminology. Sensible turns SBCs into structured JSON for plan comparison, benefits administration, and enrollment.
Validated JSON
Schema-enforced output; every field matches your contract
Source coordinates
Every value links back to page + bounding box for audit
Per-document pricing
Predictable cost. No token-volatility surprises
Trusted by teams turning documents into production data
Despite a standardized federal template, carriers vary in visual layout, table structure, and how they express cost-sharing details. Hybrid extraction handles the variation while enforcing consistent output.
01
Primary care, specialist visits, ER, hospitalization, prescriptions: SBCs list cost-sharing for dozens of categories. Each one is extracted with its copay, coinsurance, and any limits or conditions attached.
02
Every service row has separate in-network and out-of-network costs. Some carriers use columns; others use alternating rows. The extraction config captures both regardless of visual presentation.
03
Excluded services and coverage limitations appear as text blocks, not structured fields. LLM parsing identifies these sections and extracts the specific services and conditions mentioned.
Managed services
Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.
What's included
01Plan.Engineers review your samples and pick the right method
02Build.SenseML configs written from your samples
03Deploy.Same engine as self-serve, ready for production
04Adjust.We update configs when formats shift or new edge cases appear
05Integrate.Help with custom integration into your downstream systems
We configure every SBC extraction to your exact schema, not a fixed field list. The fields below are the ones benefits teams pull most often — tell us what your benefits-administration workflow needs and we map the rest.
01
Plan overview
Plan name, plan type (HMO/PPO/EPO/POS), coverage period, deductible (individual/family), out-of-pocket maximum, copay/coinsurance structure
02
Covered services
Service category, in-network cost sharing, out-of-network cost sharing, deductible applies (yes/no), prior authorization required, visit limits
03
Exclusions and limitations
Excluded services list, coverage limitations, prescription formulary tier structure, prior authorization requirements
config.json
SenseML
{ /* SenseML: Summary of Benefits and Coverage extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "plan_name", "description": "plan name, coverage name, health plan" },
{ "id": "annual_deductible", "description": "annual deductible, individual deductible, in-network deductible" },
{ "id": "out_of_pocket_max", "description": "out-of-pocket maximum, OOP max, out of pocket limit" },
{ "id": "pcp_copay", "description": "primary care visit cost, PCP copay, office visit copay" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible's healthcare template library includes SBC configurations for major carriers. The hybrid approach adapts to each carrier's visual layout while enforcing consistent output.
Group health plans (employer-sponsored), individual marketplace plans (ACA), Medicare Advantage, dental, vision
UnitedHealthcare, Anthem, Aetna, Cigna, Humana, BCBS affiliates, Kaiser, regional health plans
Answers about SBC parsing, plan comparison, and cost-sharing extraction.
Yes. Sensible outputs SBC data in a consistent schema. You can compare copays, deductibles, out-of-pocket maximums, and covered services across plans programmatically.
By default Sensible captures deductibles, copays, coinsurance, out-of-pocket maximums, and coverage percentages for both in-network and out-of-network services. The output is defined in configuration, so you can reshape it to match how your team stores or compares plan data.
Yes. Sensible reads the cost-sharing structure for each covered service category, including primary care visits, specialist visits, emergency room, hospitalization, and prescription drugs. Those categories are configuration. You can add any service line an SBC lists and shape the output to your schema.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
Start free
Free 14-day trial. No credit card required. Start extracting in minutes.