OpenAdaptHow do you stop re-keying claims into your claims system?
Take claims in as data: your claims system's API or import, an intake portal, or an electronic feed. If claims still arrive as PDFs, faxes or email, OpenAdapt can read the document (tested on synthetic documents), make the screen entry, and check each save against the claims system's own data.
Updated 2026-10-18
The options, in order
| Option | Good when | Watch out for |
|---|---|---|
| Your claims system's API or bulk import | Claims already arrive as files or forms | Mapping each source's fields once |
| An intake portal or electronic feed | You can ask claimants or providers to submit online | Not everyone will |
| Screen entry by a program, with a read-back | The system has no usable import for this claim type | It needs a read-only way to confirm the save |
| The same program, filled from the claim document | Claims arrive as PDFs, fax images or email | Unclear fields are held back for a person, who also checks the first runs |
If you enter through the screen
In our openIMIS test, a program learned from a demonstration entered 6 synthetic claims: 5 were saved and read back by our test setup, 15 of 15 fields matching, and the one with a mistyped insured number stopped before saving. We found no published study of how long insurer staff take per claim, so time your own.
- Confirm each save through a read-only database role, a report or an API.
- Make sure a mismatch, such as no member found, stops before saving.
- Know the limits: a number that belongs to another member can look normal on screen; only a record check or a person catches it.
For agencies re-keying into carrier portals
Agencies often key one submission into several carrier portals; in Ivans' 2026 survey of 702 independent agents, 74% named re-keying as their top workflow pain. The options are comparative raters, carrier downloads (IVANS in the US, CSIO in Canada), and carrier APIs where offered. Where staff still key into the portal, OpenAdapt could make the entry, then open the saved submission again in a fresh browser session and compare every field with what it entered; that check is set up with each workflow. Some portal terms forbid letting anyone else use your login, so we read each portal's terms with you.
Where OpenAdapt fits
For carriers, MGAs and TPAs entering claims into their own system: see claims intake and Insurance. For brokers keying into carrier portals: Insurance. API or screen automation?
Sources
- OpenAdapt on openIMIS 25.10 (open-source insurance system), local test copy, 12 Oct 2026. A program learned from one demonstration entered 6 synthetic health-facility claims in one batch, with 0 AI model calls. 5 were saved; our test setup read each back through SQL and the openIMIS API, and 15 of 15 fields matched the claim document. On the 6th, the insured number had two digits swapped: openIMIS found no member, the screen no longer matched the demonstration, and the program stopped before saving (no claim was written). The engine labels the 5 saved runs "Finished, not checked", because this program has no record check of its own yet.
- Ivans, 2026 Carrier-Agency Connection Report: an online survey of 702 independent agents, April to May 2026, run by a vendor of agency-carrier connectivity software. 74% name re-keying as their No. 1 workflow pain point.
See it on your process
Bring one task your team types every day. We'll tell you whether it fits, and what a test on your own system would cover.