PolicyBlockchain Data Standard

The record format the PolicyBlockchain network uses for insurance data: parties, policies, coverages, forms, claims, billing, regulatory reporting, reinsurance and capital, plus an experimental model for underwriting reputation and track record.

It is our own model, written as JSON Schema 2020-12. It is compatible with the formats the industry already uses, so carrier, MGA and agency data maps in and out by identifier.

• Open licence. Apache-2.0 for the whole standard: schemas, code sets, examples, tooling and documentation.
• Free tooling. A validator and conformance checker anyone can run, and free converters planned for common formats.
• Compatibility mappings. Existing data maps in by identifier, without republishing anyone's proprietary content.
• Conformance. A clear Core, Line and Full test, and a “PolicyBlockchain Compatible” mark defined by passing it.
• A path to neutral governance. An open comment process, a steering group, and a stated plan to move the standard to a neutral foundation.

1. Our own names. Plain camelCase fields owned by the standard.
2. Identifiers, not content. External codes travel as qualified values, e.g. { "system": "ncci.class", "code": "8810" }. Forms are cited by number and edition.
3. Transactions are the record. A policy term, a claim and a loss run are projections of append-only transactions, with both business time and recorded time.
4. One party key. Parties are keyed by their InsureBio identity; insured, carrier, wholesaler and claimant are roles.
5. Money is exact. Integer minor units plus an ISO 4217 currency.
6. Premium is typed charges. Each charge says who ultimately receives it, so a payment splits cleanly.
7. No personal data on chain. Events carry hashes or tokens; personal fields move only under a data access grant.
8. Corrections are new records. Nothing is edited in place or deleted.

Every line follows one pattern, { lineCode, exposures[], coverages[], ratingBasis[] }, and has an end-to-end example from submission to loss run.

An excess and surplus lines overlay applies to any line: placement, home state, diligent search, licensed broker, affidavit, stamping and tax allocation.

Events are named domain.object.action (for example claim.reserve.changed) across policy, claim, billing, trust, reinsurance, capital, regulatory, identity and ledger domains. Each has a payload schema and a version. Payloads carry no personal data.

A proposal: original, plainly worded coverage forms published under Apache-2.0, each with a stable id and edition, with every clause individually addressable. Coverages can cite them directly. State form-filing rules still apply, so a carrier files an Open Coverage Form before using it.

An experimental, open model for underwriting reputation: seasons, listed programs and books (rows), seats, free-entry contests of skill scored on chain data, forecasts, and verified books of business. A seat is never an underwriting decision, and contests never take an entry fee.

Licensed under Apache-2.0. Third-party form numbers and codes appear only as identifiers, for compatibility. The standard does not reproduce third-party form wording, element dictionaries, class descriptions or code lists.

The validator will be published with the schemas, runnable with npx or Docker.

Questions, objections and proposals go to the community forum, in the Developers category. Changes to the standard follow a public request-for-comment process there.

Forum: community.policyblockchain.com, Developers category.