Core claims systems integration
Ishqkala + Origami Risk
Subrogation detection for Origami Risk claims administration, built for TPAs, pools and self-insureds.
Overview
Origami Risk runs claims administration and RMIS for self-insured entities, public entity pools, TPAs and carriers. Ishqkala reads claims, notes and attachments through the Origami REST API with a role-scoped API user, scores each claim for third-party recovery, and returns findings to the domain your administrators designate, such as a note, a task or a configured subrogation field. For historical sweeps, a scheduled Origami export over SFTP feeds the Closed-Claim Sweeper.
Use cases
- Find recoveries against at-fault drivers in a public entity pool's fleet physical damage claims.
- Spot third-party actions in self-insured workers' compensation claims, such as a negligent driver or a defective machine.
- Give a TPA a per-client Recovery Opportunity Manifest from claims administered in Origami.
- Flag property claims where a vendor's or contractor's work caused the loss.
Architecture & data flow
How data moves between Origami Risk and Ishqkala.
01
Authenticate
Ishqkala exchanges API user credentials for a short-lived token (30 minutes by default) and renews it at expiry.
02
Discover fields
DataDictionary calls map your configured claim fields, custom fields included, so configuration changes do not break ingestion.
03
Incremental pull
Query calls return claims changed since the last run, with their notes and attachments.
04
NLP and scoring
Notes and documents are read for liability signals, then scored on recoverable dollars, win probability and days to SOL.
05
Write-back
Findings post to the designated domain through the API, or arrive as a daily file for Origami's import tools.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Claim | Read | Claim number, claimant, status, date of loss, coverage line, location and total incurred. |
| Claim notes | Read / write | Examiner notes parsed for liability language; Ishqkala posts a finding note with cited text where your API role permits creates. |
| Attachments | Read | Police reports, incident reports, contractor invoices and photos linked to the claim. |
| Financial transactions | Read | Paid and incurred by category, used to estimate net recoverable dollars. |
| Location and entity hierarchy | Read | Client, member or location levels, so TPAs and pools see opportunities by client or member entity. |
| Task or subrogation field | Write | A review task or a configured subrogation indicator, set on the domain your administrator designates. |
Security & data governance
Controls on this connection.
- Dedicated Origami API user with a role limited to the domains Ishqkala reads and the one domain it writes.
- API tokens held in memory and renewed at expiry; API user credentials stored in an encrypted secrets vault.
- Client and member data partitioned per tenant, so one TPA client never sees another's opportunities.
- AES-256 at rest, TLS 1.3 in transit, US-only hosting and zero model training on claim files.
- HIPAA BAA available for workers' compensation and liability files containing medical records.
Setup timeline
From kickoff to first findings.
Week 1
API user and scope
Your administrator creates the API user and role, and confirms the environment URL (staging first, then production).
Week 2
Field mapping
DataDictionary review to map coverage lines, claim types, custom fields and hierarchy levels.
Weeks 3 to 4
Baseline and review
Closed-claim baseline from an SFTP export; examiners review a sample of findings.
Week 5
Go-live
Incremental API pulls and write-back enabled in production.
FAQ
Origami Risk integration FAQ
No formal partnership is implied. Ishqkala connects through the published Origami REST API using an API user your administrators create, scope and can disable at any time.
Yes. Ishqkala reads the DataDictionary for each domain before it ingests, so renamed or added fields are picked up at the next run instead of failing silently.
Yes. Opportunities, manifests and reports are partitioned by the client or member level in your hierarchy, which suits TPAs and pools reporting recoveries to each client.
Ishqkala delivers findings as a daily file your team imports with Origami's tools, or examiners work findings in Ishqkala and record decisions in Origami.
More core claims systems
Find the millions hiding in your closed claim files before the Statute of Limitations expires.
We'll scan a batch of 500 closed claims for free and deliver an itemized recovery manifest within 5 business days.