Integration · systems
What an Australian insurer actually runs, and how intactly attaches to each. Where a connector does not exist, the generic pattern that replaces it is named rather than glossed over.
Stated plainly, because a connector catalogue that implies everything is built is the fastest way to lose a technical evaluation.
| Status | Means |
|---|---|
| Pattern | A documented integration approach using the system's standard interfaces. No pre-built adapter ships today; the work is configuration plus mapping. |
| Generic | Handled by the file, API or bus patterns rather than anything system-specific. Most systems land here and that is fine. |
| Planned | On the roadmap, sequenced behind a design partner who actually uses it. We do not build adapters speculatively. |
The system of record. intactly reads from it and never writes a decision back to it.
Messaging plugin or event fabric emits claim and activity events. Read via the Cloud API. Handler view can be embedded as a page fragment under the same SSO session.
Source for the policy schedule, product code, period of insurance, sums insured and endorsements that the coverage engine assesses against.
Common in AU life and personal injury. Read via its integration services; map absence and disability case states to the canonical event vocabulary.
Extract or API-based read of claim and policy data.
Standard API or extract integration.
Used across Australian workers compensation and self-insurance. Extract-based integration is the usual route.
Case events published to a bus; obligations returned as a work queue.
Platform events out, obligations back as records or an embedded component.
Nightly extract to SFTP or object storage. Obligation clocks run in days, so a nightly cadence loses very little. This is a first-class option, not a fallback.
Personal injury in Australia means reporting into a scheme regulator as well as handling the claim. These are the interfaces that make a national book genuinely harder here than in a single-regulator market.
| Scheme | Jurisdiction | Relevance | Status |
|---|---|---|---|
| SIRA | NSW | Workers compensation and CTP data standards, and the source of the guidelines the NSW rules encode. Reissued 30 June and 1 July 2026. | Pattern |
| icare | NSW | Nominal Insurer scheme data exchange, for agents on the panel. | Pattern |
| WorkSafe Victoria | VIC | Agent reporting and claim data exchange. | Pattern |
| TAC | VIC | Transport accident claims. | Pattern |
| WorkCover Queensland | QLD | Claims data and decision reporting. | Pattern |
| MAIC | QLD | CTP scheme data. | Pattern |
| ReturnToWork SA | SA | Claims determination reporting. | Pattern |
| WorkCover WA / ICWA | WA | Workers compensation under the 2023 Act, and CTP. | Pattern |
| Comcare | Federal | Commonwealth employees. | Planned |
Casefile reads the file as it exists. Document access is usually the longest approval in the whole programme, so start it in week one rather than at phase five.
Graph API with a scoped application permission, restricted to the claims document library.
Widely used by Australian government and scheme agents.
Standard content API integration.
Records management in scheme and government environments.
Where legal files sit alongside claim files.
S3 or Azure Blob with pre-signed, time-limited, per-document URLs. Simplest to secure and easiest to audit.
A monitored claims mailbox. Attachments are traversed to depth - email into PDF into embedded image.
Read claims from a curated layer; write obligations and findings back as tables for your own reporting.
Delta table exchange in both directions.
Common in AU insurers on the Microsoft stack.
The best transport for the event flow. Ordering per claim matters; ordering across claims does not.
Scheduled extract orchestration.
Where a managed pipeline already exists, reuse it rather than building a second one.
| Capability | Support | Notes |
|---|---|---|
| SAML 2.0 | Pattern | Entra ID, Okta, Ping, ADFS. |
| OIDC / OAuth 2.0 | Pattern | Preferred for new deployments. |
| SCIM 2.0 | Pattern | Automated provisioning and, more importantly, automated de-provisioning. |
| Role mapping | Pattern | Maps to the roles the rule console already models: author, peer reviewer, verifier, publisher, reader. |
| Break-glass | Pattern | Separate, logged, time-limited. Never shared credentials. |
Relevant because several obligations discharge on communication, not on internal action. A progress update that was made but never recorded appears as a breach.
Interaction records supply claim.progress.updated and customer.enquiry.received.
Contact trace records to the same events.
Case activity as evidence of contact.
Send confirmations are the cleanest evidence that a notice was actually issued.
Enrich supplies context that only exists in this market. All sourced onshore.
| Source | Used for | Status |
|---|---|---|
| ICA catastrophe declarations | Whether a claim sits inside a declared Insurance Catastrophe or Significant Event, which changes the applicable Code timeframes. | Pattern |
| Bureau of Meteorology | Event verification for storm, flood, hail and cyclone claims. | Pattern |
| Geoscape / G-NAF | Address resolution and property matching. | Pattern |
| ABN Lookup & ASIC registers | Entity verification for suppliers, repairers and employers. | Pattern |
| Vehicle valuation | Market value for total-loss assessment. Redbook, Glass's. | Pattern |
| Police event numbers | Verification, per state format. | Planned |
| Medicare / PBS | Treatment history in personal injury and life claims. Consent-gated, and never used as an integrity signal without it. | Planned |
| Insurance Fraud Bureau of Australia | Industry data sharing for organised patterns. | Planned |
| Destination | What intactly contributes |
|---|---|
| Code Governance Committee | Significant breach identification and the 10-business-day reporting clock under GI Code para 181, with the underlying evidence. |
| AFCA | Per-claim compliance reports for member responses, with the instrument text and the full event timeline. |
| APRA | CPS 230 material service provider pack, CPS 234 control evidence, and the operational risk position for claims handling as a critical operation. |
| ASIC | Claims handling evidence, and the APP 1 automated decision-making disclosure. |
| Scheme regulators | Statutory timeframe compliance by jurisdiction, which is what remediation plans are written against. |
| Your data warehouse | Obligation, finding and report tables so this feeds your own board reporting rather than becoming another silo. |
It is almost certainly still fine. Every system on this page reduces to one of three questions:
If the answer to the first is yes, there is a viable integration. The other two can follow later. Bring the system name to a briefing and we will tell you which pattern applies rather than promising an adapter.