On-prem CPU / GPU
Full throughput on commodity servers — encoder models run in milliseconds on CPU, faster still with a single GPU.
Open-source insurance NER
Your Data. Your Model. Your Hardware.
OpenCover is a family of eight trained encoder models built for insurance. They read dec pages, FNOL notices, ACORD forms, adjuster notes and medical reports, extract 28+ entity types, and de-identify PII and PHI without a single record leaving your network. Apache-2.0, hosted on Hugging Face.
$ pip install git+https://github.com/flowx-ai/openner
from openner import analyze result = analyze(document, profile="glba-hipaa") print(result.entities) # POLICY_NUMBER, CLAIM_NUMBER, PERIL, VIN … safe = result.deidentify() # strips PII + all 18 HIPAA identifiers on-device
Small encoders mean no GPU cluster, no vendor API, no data-processing addendum. Deploy at the point of intake.
Full throughput on commodity servers — encoder models run in milliseconds on CPU, faster still with a single GPU.
Ship the weights on physical media and run with zero outbound connectivity — built for regulated core networks.
Embed as a library in Guidewire-, Duck Creek- or homegrown-core pipelines, right where FNOLs and dec pages arrive.
Quantized ONNX builds run in-browser via WASM — redact a document before it ever reaches your server.
A one-command self-hosted service exposes every model behind REST and gRPC for your internal platform teams.
Insurance is the rare industry that handles financial NPI and health PHI in the same claim file. OpenCover treats both as first-class.
All eight models are trained and shipping — compact encoders with ONNX/edge exports and built-in VIN check-digit and ICD/CPT validation. Download from Hugging Face once, fine-tune freely, compose as needed. For scanned or photographed forms, the cross-industry FlowX DocFormNER model is an early preview (see the FAQ).
Policy numbers, coverages, limits, deductibles, premiums and effective dates from declarations pages.
Claim number, loss date, cause, reserve and status from FNOL notices and running claim files.
Tags perils and cause-of-loss — fire, flood, wind, theft, collision — from free-text loss descriptions.
Roles every party in the file: policyholder, claimant, adjuster, broker, beneficiary, carrier.
Insured objects and their identifiers: VIN, make/model/year, property addresses, equipment serials.
Reference codes wherever they hide: NAIC, NCCI class, ICD/CPT, CAT event, NAICS/SIC.
The dual-regulation de-identifier: GLBA financial PII plus all 18 HIPAA Safe Harbor identifiers.
Clinical branch for bodily-injury and health claims — reuses proven clinical NER weights.
Teams compose the models into working products. Three we ship as reference implementations:
Turns a phone transcript, email or photo FNOL into a structured, ACORD-mapped claim in seconds — every PII field flagged before it hits the queue. Runs on-prem.
Reads adjuster notes and medical reports, scores severity, and routes fast-track versus SIU/fraud review — with a full audit trail for Fair Claims Practices.
Ingests broker slips, loss runs and SOVs; extracts risk entities and codes into a clean submission summary — no data ever leaving the carrier.
On-device processing doesn't exempt you from regulation — it just makes compliance tractable. OpenCover maps to the frameworks your legal team will ask about.
We benchmarked our small on-device models head-to-head against the latest cost-effective frontier LLMs — same documents, same entity types.
Frontier LLMs win at open-ended reasoning — not structured, convention-bound extraction. Small fine-tuned encoders win there, and keep dual-regulated data on-prem.
An open-source, privacy-first family of eight trained encoder NER models for insurance — PolicyDetect, ClaimExtract, AssetDetect, PerilClassify, PartyResolve, CodeMap, InsurRedact and MedClaimNER — covering P&C, life, claims and underwriting. They extract 28+ entity types with VIN check-digit and ICD/CPT validation, and de-identify GLBA + HIPAA data with signed audit reports, all on your own hardware. ONNX/edge exports included. Apache-2.0 licensed, models hosted on Hugging Face.
Extraction and redaction are token-classification problems, and small encoders are excellent at them: deterministic spans, millisecond CPU inference, no hallucinated fields, and models small enough to run inside a claims system or even a browser. Use an LLM downstream if you want; OpenCover keeps the sensitive first pass local and cheap.
Insurance sits at the intersection of two regulatory regimes: policy and payment data is financial NPI under GLBA, while bodily-injury and health claims carry PHI under HIPAA. A single claim file often contains both. InsurRedact handles them in one pass so you don't have to stitch a banking redactor onto a healthcare one.
No. Inference runs entirely in your process on your hardware. There are no cloud APIs, no telemetry and no phone-home. The only network activity is the one-time model download from Hugging Face — and in air-gapped mode you skip even that by importing the weights on physical media.
Yes — that's the point of shipping small models under Apache-2.0. Fine-tune on your carrier-specific forms, endorsements and note-taking conventions with standard Hugging Face tooling, entirely inside your network. Your data never leaves; your improved weights are yours.
As an early preview, the cross-industry FlowX DocFormNER model (a LayoutLMv3 encoder that reads text, 2D layout and the page image together, published at huggingface.co/flowxai/docformner) now reads scanned and photographed insurance documents such as ACORD forms and FNOL/claims packets, entirely on-prem — though it is trained on synthetically rendered forms and still needs evaluation on your real OCR'd scans before production use.
Everything — code, weights, training recipes — is Apache-2.0. An honest caveat: public insurance-text NER corpora are scarce, so training relies heavily on synthetic generation of ACORD forms, FNOL notices and dec pages, plus reuse of clinical de-identification corpora (i2b2/n2c2) for the medical-claims branch. We publish the generation pipelines so you can inspect and extend them.
Apache-2.0 · An open-source model family — not affiliated with any carrier or regulator.