Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Nairobi · Economy & commerce

Insurance.
Explore policies, coverage and claims context.

Start with the published policy sample, then review the documented relationships between coverage, residents and claims.

Public sample available

Published domain facts

Structural Certification Checks, Nairobi (4 N/A — later-stage tables still populating)
11 PASS / 0 FAIL
Policy, Coverage & Claims Context
Connected
Kenyan Coverage Context
Public + Private

Overview

Domain scope

Start with the published policy sample, then review the documented relationships between coverage, residents and claims.

Read the published guide →

Known limits

The documented rebuild checks await generation. Concurrent employer policies remain a deferred gap; the direct Employment coverage link is unconfirmed. Unsupported extension checks report N/A. Claims and premiums support analysis, not actuarial pricing or real underwriting.

Review the source limits →
Full scope reference 3 documented sections
Published domain scope.

Published domain scope.

Trace policies, coverage, premiums and claims for synthetic residents. Concurrent protections retain their separate policy and coverage references.

  • Compare policy coverage types
  • Inspect start years and policy status
  • Check which claim relationships are documented
Structural Certification Checks, Nairobi (4 N/A — later-stage tables still populating)
11 PASS / 0 FAIL
Policy, Coverage & Claims Context
Connected
Kenyan Coverage Context
Public + Private
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

One citizen. Multiple protections. One connected life. FCTE tracks every synthetic citizen's insurance relationships as concurrent, real coverage — a government SHA policy and an employer's private plan, active at the same time, on the same person — because that's how real Kenyan formal employment actually works.

Nairobi City Twin™ · 1940–2026

What Insurance actually models — and where it stops.

What Insurance actually models — and where it stops.

Inspect the published definitions and release context.

Read the published detail

Every capability below is backed by release evidence or certification; the physical design is intentionally generalized.

Insurer and payer context represented as public semantic entities.

Policy — plan tier, copay type/value, deductible, coverage limit, monthly premium, acquisition type, linked to its issuing company.

Coverage — per-citizen enrollment, now modeled so distinct active policy relationships can coexist while duplicate same-policy enrollment is prevented.

Claims context captures amount/outcome/cause and optional care linkage; physical fields and adjudication design are controlled.

Accident and premium-payment context are represented longitudinally; physical relationship fields remain controlled.

Coverage and claim timing is checked against the synthetic resident lifecycle so analytically impossible post-lifecycle records are not treated as valid.

Synthetic by design: FCTE insurance records are analytically representative coverage and claims data. They are not real policyholder records, real claims history, or a substitute for any insurer's or regulator's own data. The public data model claims only the capabilities described here; physical internal methods remain controlled.

Healthcare models the clinical encounter. Employment determines whether employer-provided cover exists. Insurance models the coverage relationship itself — the policy, the enrollment, and what happens when a claim is filed.

DomainCore QuestionKey Objects
InsuranceWhat coverage protects this citizen, and against what?Payer, policy, coverage, claim and premium context
HealthcareWhat clinical care did the citizen receive?Care encounter and diagnosis context
EmploymentDoes this citizen have employer-provided cover at all?Contract and employer context
BusinessIs the insurer itself a registered enterprise?Registered-enterprise context

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

Policy referenceCoverage typeStart yearStatus
POL-11891Health2022Active
POL-44002Asset2020Renewed

Showing 2 of 2 sample rows and 4 of 4 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 4 visible fields

Policy reference

The reference used to identify the policy associated with this record.

Original field: PolicyId
Example: POL-11891

Coverage type

The category or type assigned to the coverage in the source record.

Original field: CoverageType
Example: Health

Start year

The calendar year in which the recorded coverage began.

Original field: StartYear
Example: 2022

Status

The state recorded for the in this extract.

Original field: Status
Example: Active

Complete published field dictionary · 4 fields
PolicyIdPolicy reference
The reference used to identify the policy associated with this record.Example: POL-11891
CoverageTypeCoverage type
The category or type assigned to the coverage in the source record.Example: Health
StartYearStart year
The calendar year in which the recorded coverage began.Example: 2022
StatusStatus
The state recorded for the in this extract.Example: Active
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
From a company to a citizen's claim history.

From a company to a citizen's claim history.

Inspect the published definitions and release context.

Read the published detail

Representative semantic rows for the Nairobi insurance model. Synthetic examples; not policyholder records and not the internal data structures.

Explore Coverage Data →

Public entity familyRepresentsDisclosure boundary
Payer & product contextInsurer/payer and policy-product contextPhysical company/policy fields are controlled
Coverage relationshipResident protection and acquisition contextPhysical uniqueness constraints and keys are controlled
Premium contextPremium-payment history and status contextExact payment fields and duplicate rules are controlled
Claims contextClaim amount/outcome/cause and care contextAdjudication fields and design are controlled
Coverage TypeProduct ContextAcquisitionStatus
Public health coverNational/basic health coveragePublicActive
Employer health coverEmployer/private top-upEmployerActive
Individual private coverPrivate health protectionPersonalRepresentative

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
Resident coverage relationshiprelease integrity checked
Businessinsurer/payer enterprise context where available; physical linkage and reconciliation are controlled
Demographicscoverage and claim activity is bounded by the resident lifecycle
HealthKenya's clinical claims link Claim to a supplied visit (Core relationship, added only when Visit exists)
EmploymentEmployment context (employer-sponsored coverage is represented conceptually; internal linkage is not asserted publicly)
Full relationship reference 1 documented sections
Known and possible relationships.

Known and possible relationships.

Inspect the published definitions and release context.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or contextRelationship and published scope
Resident coverage relationshiprelease integrity checked
Businessinsurer/payer enterprise context where available; physical linkage and reconciliation are controlled
Demographicscoverage and claim activity is bounded by the resident lifecycle
HealthKenya's clinical claims link Claim to a supplied visit (Core relationship, added only when Visit exists)
EmploymentEmployment context (employer-sponsored coverage is represented conceptually; internal linkage is not asserted publicly)

Domain guide

Insurance · archived guide edition

Striped Donkey V5.89 - 7 September 2026

Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.

Published scope and limits

The documented rebuild checks await generation. Concurrent employer policies remain a deferred gap; the direct Employment coverage link is unconfirmed. Unsupported extension checks report N/A. Claims and premiums support analysis, not actuarial pricing or real underwriting.

Read the source limits →
Accessible HTML reference 2 documented sections
One citizen. Multiple protections. One connected life.

One citizen. Multiple protections. One connected life.

Inspect the published definitions and release context.

Read the published detail

The single most important fact about this domain: a real citizen can hold more than one active insurance policy at the same time — and until 2026-08-01, FCTE's own data structure forbade it.

The model supports a public-coverage relationship alongside distinct private or employer coverage where the city context calls for it.

Different active policies can coexist for one synthetic resident while duplicate enrollment in the same policy is treated as invalid. The physical constraint design is controlled.

The release now permits concurrent distinct-policy coverage for one synthetic resident while still preventing duplicate enrollment in the same policy. Exact uniqueness constraints and migration mechanics are intentionally withheld.

Two genuinely different insurance systems, not one template twice.

Two genuinely different insurance systems, not one template twice.

Inspect the published definitions and release context.

Read the published detail

Kenya's model emphasizes health-insurance and claims context, while Nigeria's model emphasizes a broader general-insurance market. The distinction is part of the public semantic architecture, not merely a naming change; internal data structures differences remain private.

Real payers span five tiers by establishment date: NHIF (1966), SHA (2023-10-23, replacing NHIF), Linda Mama (2013), long-established private insurers Jubilee (1937), Britam (1965), APA (1979), CIC (1978), plus international entrants Cigna (2000), Allianz Care (2010), Bupa Global (2012), and the M-TIBA mobile health wallet (2016).

NHIF (1966), SHA (2023-10-23), Linda Mama (2013), Jubilee (1937), AAR (1984), Britam (1965), APA (1979), CIC (1978), Madison (1988), Heritage (1976), Resolution Health (2002), Cigna (2000), Allianz Care (2010), Bupa Global (2012), M-TIBA (2016).

Kenya’s public and private coverage can overlap in real life, providing evidence for representing concurrent distinct-policy protection in the synthetic model.

Open Insurance Evidence Catalogue →

DimensionKenya (Nairobi)
Core ModelHealth-insurance claims-TPA
Companies15 payers, 5 tiers
Product CatalogPlan tier + copay + deductible
Claim LinkageVisit (clinical)
Motor/Accident LineNot a primary payer line
Beneficiary ModelingNot applicable at this layer
Fraud DetectionFraud-analysis consistency represented as a public analytical rule

Evidence & limits

Scope and known limits

The documented rebuild checks await generation. Concurrent employer policies remain a deferred gap; the direct Employment coverage link is unconfirmed. Unsupported extension checks report N/A. Claims and premiums support analysis, not actuarial pricing or real underwriting.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

The documented rebuild checks await generation. Concurrent employer policies remain a deferred gap; the direct Employment coverage link is unconfirmed. Unsupported extension checks report N/A. Claims and premiums support analysis, not actuarial pricing or real underwriting.

Read the published detail

Two concurrent employer-provided policies for the same citizen (e.g. from concurrent formal employment at two employers) is a real, disclosed gap — deliberately deferred rather than silently forbidden by an overly broad rule. This is a known and disclosed limitation, not a hidden one.

Employer-sponsored coverage is represented conceptually. This page does not claim a confirmed, verified direct read from Employment's Contract rows into Coverage — that specific cross-domain link has not been confirmed in the data model.

Synthetic citizens and coverage records are not real people and carry no real personally identifiable information. This page makes no claims about compliance frameworks for handling real policyholder data.

Beneficiary and accident-line checks are city-extension checks that are not active in the Nairobi release. They correctly report N/A when the corresponding extension or prerequisite context is absent; N/A is a scoped result, not a hidden certification failure.

Kenya’s fraud-analysis context includes additional claim consistency checks; exact fields and logic are controlled.

Claim amounts, approval rates and premium figures are analytically representative, not sourced from any real insurer's or regulator's actual claims experience. They should not be used for actuarial pricing or real underwriting decisions.

Coverage, Claim, Premium Payment, claim line items and the fraud-workflow queue are all part of the same generation pass and have not yet been (re)run on Nairobi in the current rebuild cycle — those checks report N/A rather than a false PASS or a hidden failure until they run.

View All Insurance Limitations →

Does synthetic coverage resemble real insurance relationships?

Does synthetic coverage resemble real insurance relationships?

Inspect the published definitions and release context.

Read the published detail

Insurance certification evaluates release-level structural, temporal and lifecycle consistency across payer, policy, coverage and claims context. Public results show the outcome and current data-availability state; physical constraints, deployment history and recovery mechanics are intentionally withheld.

Open Insurance Realism Report →

N/A is used deliberately when prerequisite data doesn't exist — never to hide a failure. Coverage and Claims are now live in Nairobi (11 of 15 checks applicable, all passing); the remaining 4 N/A checks depend on later-stage tables (Premium Payments, claim line items, fraud-workflow queue) that are still populating as part of the same generation pass. This page reports the current release state rather than substituting a last-known-good result.

Explore Every Insurance Check →

  • Payer context — PASS, 15 companies
  • Policy catalogue — PASS, 28 policies
  • Coverage relationship integrity — PASS, 0 orphaned rows
  • Claim value integrity — PASS, 0 violations
  • Premium value & uniqueness — N/A, insurance. PremiumPayment still populating
  • Coverage chronology — PASS, 0 violations across policy and claim lifecycle
  • Fraud-analysis consistency — PASS, 0 inconsistent rows
  • Resident-lifecycle boundary — PASS in the documented release state

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Published access and recorded examples 1 documented sections
Recorded example.

Recorded example.

Published release reference · These recorded checks are not a current rerun.

Explore the supplied synthetic example and its source references.

Read the published detail

28 real Policy rows exist today, naming real Kenyan insurers and products — "NHIF Basic Inpatient Cover," "Britam Afya Imara Basic" among them.

confirmed in the published source: Coverage, Claim, PremiumPayment and AccidentClaim all have 0 rows. The product catalog is real; no citizen-level enrollment, coverage or claim activity has been generated yet.

Employment or scheme enrollment → Policy selection → active Coverage → filed Claim is the designed model — shown as scope, not as a live result.

Risk becomes coverage. One citizen. Multiple protections. One connected life.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™