{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-045","code":"wm-act-045-insurance-claim-handling","url":"https://ver.cy/models/wm-act-045-insurance-claim-handling/","name":"Insurance Claim Handling","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"aggregate","plane":"","domain":["ACT.INS"],"industry":["Cross-industry"],"navPath":"NAV.ACT.INS","tags":["insurance","claim","handling","act.ins"],"facets":{}},"whatItIs":"Owns handling-case identity and lineage, mandate, assignment, intake, acknowledgement, triage, authoritative claim and policy bindings, evidence requests and use, investigation activity, assessment assertions, decision and offer records, settlement and financial handoffs, status communications, review and dispute links, fraud and recovery referrals, closure, reopening, quality, provenance, access, retention and interoperability. Insurance Claim, Policy, Loss, Party, Evidence, Fraud, Complaint, Legal, Payment, Reserve, Communication, Audit and Record masters remain external.","purpose":"Represent one governed insurance-claim-handling case that coordinates notification, investigation, coverage and amount assessment, reasoned decision, settlement handoffs, communications, review and closure without becoming the insurance claim or the systems it coordinates.","scope":{"in":["Handling-case identity, authority, intake, acknowledgement, guidance, triage, assignments, claim and policy bindings","Evidence requests and use, investigation, coverage, liability, causation, benefit and amount assessments, fraud indicators and controlled referral","Reasoned decisions, offers, settlements, payment and recovery handoffs, communications, reviews, closure, reopening, provenance, privacy, retention and interoperability"],"out":["Independent insurance claim, policy, coverage, loss, party, asset, damage, injury, evidence, expert, fraud, complaint, legal case, payment, reserve, communication, audit or record master lifecycles","Treating notification as acceptance, policy existence as coverage, investigation as proof, reserve as offer, decision as payment, suspicion as fraud or closure as erased rights","Providing legal or medical judgment, executing payments, operating insurer systems, determining universally applicable deadlines or autonomously deciding or settling claims"],"boundaries":[{"neighbor":"WM-ECO-036 Insurance Claim candidate composer","distinction":"The claim master owns the claim identifier and substantive policy-loss-demand assertions. This aggregate owns one handling process, its work, decisions and handoffs. The ledger relation is candidate, not approved."},{"neighbor":"WM-ECO-003 Insurance Policy and Coverage","distinction":"The policy master owns contract, insured risk, coverage terms and policy lifecycle. The handling case records source-qualified interpretations and decision-time snapshots without rewriting the contract."},{"neighbor":"Evidence, Expert, Damage, Injury and Loss Event","distinction":"External masters own source observations and subject facts. This case records requests, custody references, validation, use and resulting assessments."},{"neighbor":"Fraud Case, Complaint, Ombudsman, Arbitration and Court Case","distinction":"This process may create a controlled referral or bind an external review outcome; it does not decide fraud or absorb independent redress and adjudication lifecycles."},{"neighbor":"Reserve, Payment, Accounting, Reinsurance, Subrogation and Salvage","distinction":"This model owns estimates, approval and handoff assertions needed to explain handling. External financial and recovery masters own booking, execution, clearing, rights and proceeds."}]},"distinguishingFeatures":["Models the insurer's handling work on a claim, not the claim, policy or loss event.","Keeps coverage, liability, benefit, reserve, offer, settlement and payment as separate decisions.","Routes suspected fraud to a separate case instead of deciding it inside handling.","Records reasons for decisions and review routes for claimants."],"structure":{"bundles":[{"id":"handling-case-identity-boundary-and-authority","name":"Handling case identity, boundary and authority","description":"Groups governed context for handling case identity, boundary and authority.","layers":[{"id":"case-profile-identity-lineage-and-jurisdiction","name":"Case profile, identity, lineage and jurisdiction","description":"Groups claim-handling context for case profile, identity, lineage and jurisdiction.","findings":[{"id":"handling-case-type-scope-insurance-line-jurisdiction-and-boundary","name":"Handling case type, scope, insurance line, jurisdiction and boundary","description":"Records handling case type, scope, insurance line, jurisdiction and boundary as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish handling case type, scope, insurance line, jurisdiction and boundary?","id":"handling-case-type-scope-insurance-line-jurisdiction-and-boundary-q01","kind":"classification"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support handling case type, scope, insurance line, jurisdiction and boundary?","id":"handling-case-type-scope-insurance-line-jurisdiction-and-boundary-q02","kind":"temporal"},{"text":"How may handling case type, scope, insurance line, jurisdiction and boundary be validated, challenged, corrected, related, retained or disposed without losing history?","id":"handling-case-type-scope-insurance-line-jurisdiction-and-boundary-q03","kind":"lifecycle"}]},{"id":"case-identifier-source-version-predecessor-successor-and-lineage","name":"Case identifier, source, version, predecessor, successor and lineage","description":"Records case identifier, source, version, predecessor, successor and lineage as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish case identifier, source, version, predecessor, successor and lineage?","id":"case-identifier-source-version-predecessor-successor-and-lineage-q01","kind":"identity"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support case identifier, source, version, predecessor, successor and lineage?","id":"case-identifier-source-version-predecessor-successor-and-lineage-q02","kind":"composition"},{"text":"How may case identifier, source, version, predecessor, successor and lineage be validated, challenged, corrected, related, retained or disposed without losing history?","id":"case-identifier-source-version-predecessor-successor-and-lineage-q03","kind":"event"}]}]},{"id":"mandate-participants-delegation-conflicts-and-outsourcing","name":"Mandate, participants, delegation, conflicts and outsourcing","description":"Groups claim-handling context for mandate, participants, delegation, conflicts and outsourcing.","findings":[{"id":"insurer-handler-adjuster-expert-claimant-representative-role-and-authority","name":"Insurer, handler, adjuster, expert, claimant, representative, role and authority","description":"Records insurer, handler, adjuster, expert, claimant, representative, role and authority as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish insurer, handler, adjuster, expert, claimant, representative, role and authority?","id":"insurer-handler-adjuster-expert-claimant-representative-role-and-authority-q01","kind":"authority"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support insurer, handler, adjuster, expert, claimant, representative, role and authority?","id":"insurer-handler-adjuster-expert-claimant-representative-role-and-authority-q02","kind":"evidence"},{"text":"How may insurer, handler, adjuster, expert, claimant, representative, role and authority be validated, challenged, corrected, related, retained or disposed without losing history?","id":"insurer-handler-adjuster-expert-claimant-representative-role-and-authority-q03","kind":"retention"}]},{"id":"delegation-assignment-outsourcing-conflict-competence-capacity-and-oversight","name":"Delegation, assignment, outsourcing, conflict, competence, capacity and oversight","description":"Records delegation, assignment, outsourcing, conflict, competence, capacity and oversight as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish delegation, assignment, outsourcing, conflict, competence, capacity and oversight?","id":"delegation-assignment-outsourcing-conflict-competence-capacity-and-oversight-q01","kind":"ownership"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support delegation, assignment, outsourcing, conflict, competence, capacity and oversight?","id":"delegation-assignment-outsourcing-conflict-competence-capacity-and-oversight-q02","kind":"interoperability"},{"text":"How may delegation, assignment, outsourcing, conflict, competence, capacity and oversight be validated, challenged, corrected, related, retained or disposed without losing history?","id":"delegation-assignment-outsourcing-conflict-competence-capacity-and-oversight-q03","kind":"security"}]}]}]},{"id":"notification-intake-triage-and-coverage-framing","name":"Notification, intake, triage and coverage framing","description":"Groups governed context for notification, intake, triage and coverage framing.","layers":[{"id":"notification-receipt-acknowledgement-guidance-and-routing","name":"Notification receipt, acknowledgement, guidance and routing","description":"Groups claim-handling context for notification receipt, acknowledgement, guidance and routing.","findings":[{"id":"notification-channel-received-time-submitter-loss-reference-and-duplicate-check","name":"Notification channel, received time, submitter, loss reference and duplicate check","description":"Records notification channel, received time, submitter, loss reference and duplicate check as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish notification channel, received time, submitter, loss reference and duplicate check?","id":"notification-channel-received-time-submitter-loss-reference-and-duplicate-check-q01","kind":"event"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support notification channel, received time, submitter, loss reference and duplicate check?","id":"notification-channel-received-time-submitter-loss-reference-and-duplicate-check-q02","kind":"quality"},{"text":"How may notification channel, received time, submitter, loss reference and duplicate check be validated, challenged, corrected, related, retained or disposed without losing history?","id":"notification-channel-received-time-submitter-loss-reference-and-duplicate-check-q03","kind":"validation"}]},{"id":"acknowledgement-guidance-required-information-language-accessibility-and-routing","name":"Acknowledgement, guidance, required information, language, accessibility and routing","description":"Records acknowledgement, guidance, required information, language, accessibility and routing as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish acknowledgement, guidance, required information, language, accessibility and routing?","id":"acknowledgement-guidance-required-information-language-accessibility-and-routing-q01","kind":"process"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support acknowledgement, guidance, required information, language, accessibility and routing?","id":"acknowledgement-guidance-required-information-language-accessibility-and-routing-q02","kind":"state"},{"text":"How may acknowledgement, guidance, required information, language, accessibility and routing be validated, challenged, corrected, related, retained or disposed without losing history?","id":"acknowledgement-guidance-required-information-language-accessibility-and-routing-q03","kind":"privacy"}]}]},{"id":"claim-policy-coverage-party-and-priority-binding","name":"Claim, policy, coverage, party and priority binding","description":"Groups claim-handling context for claim, policy, coverage, party and priority binding.","findings":[{"id":"claim-policy-insured-claimant-beneficiary-loss-exposure-and-coverage-reference","name":"Claim, policy, insured, claimant, beneficiary, loss, exposure and coverage reference","description":"Records claim, policy, insured, claimant, beneficiary, loss, exposure and coverage reference as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish claim, policy, insured, claimant, beneficiary, loss, exposure and coverage reference?","id":"claim-policy-insured-claimant-beneficiary-loss-exposure-and-coverage-reference-q01","kind":"relationship"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support claim, policy, insured, claimant, beneficiary, loss, exposure and coverage reference?","id":"claim-policy-insured-claimant-beneficiary-loss-exposure-and-coverage-reference-q02","kind":"measurement"},{"text":"How may claim, policy, insured, claimant, beneficiary, loss, exposure and coverage reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"claim-policy-insured-claimant-beneficiary-loss-exposure-and-coverage-reference-q03","kind":"access"}]},{"id":"completeness-admissibility-triage-severity-vulnerability-catastrophe-and-service-target","name":"Completeness, admissibility, triage, severity, vulnerability, catastrophe and service target","description":"Records completeness, admissibility, triage, severity, vulnerability, catastrophe and service target as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish completeness, admissibility, triage, severity, vulnerability, catastrophe and service target?","id":"completeness-admissibility-triage-severity-vulnerability-catastrophe-and-service-target-q01","kind":"requirement"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support completeness, admissibility, triage, severity, vulnerability, catastrophe and service target?","id":"completeness-admissibility-triage-severity-vulnerability-catastrophe-and-service-target-q02","kind":"lifecycle"},{"text":"How may completeness, admissibility, triage, severity, vulnerability, catastrophe and service target be validated, challenged, corrected, related, retained or disposed without losing history?","id":"completeness-admissibility-triage-severity-vulnerability-catastrophe-and-service-target-q03","kind":"exception"}]}]}]},{"id":"evidence-investigation-and-assessment","name":"Evidence, investigation and assessment","description":"Groups governed context for evidence, investigation and assessment.","layers":[{"id":"evidence-requests-receipt-custody-quality-and-expert-input","name":"Evidence requests, receipt, custody, quality and expert input","description":"Groups claim-handling context for evidence requests, receipt, custody, quality and expert input.","findings":[{"id":"information-request-purpose-scope-deadline-burden-response-and-escalation","name":"Information request, purpose, scope, deadline, burden, response and escalation","description":"Records information request, purpose, scope, deadline, burden, response and escalation as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish information request, purpose, scope, deadline, burden, response and escalation?","id":"information-request-purpose-scope-deadline-burden-response-and-escalation-q01","kind":"process"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support information request, purpose, scope, deadline, burden, response and escalation?","id":"information-request-purpose-scope-deadline-burden-response-and-escalation-q02","kind":"event"},{"text":"How may information request, purpose, scope, deadline, burden, response and escalation be validated, challenged, corrected, related, retained or disposed without losing history?","id":"information-request-purpose-scope-deadline-burden-response-and-escalation-q03","kind":"identity"}]},{"id":"evidence-source-receipt-custody-integrity-quality-challenge-and-expert-opinion","name":"Evidence source, receipt, custody, integrity, quality, challenge and expert opinion","description":"Records evidence source, receipt, custody, integrity, quality, challenge and expert opinion as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish evidence source, receipt, custody, integrity, quality, challenge and expert opinion?","id":"evidence-source-receipt-custody-integrity-quality-challenge-and-expert-opinion-q01","kind":"evidence"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support evidence source, receipt, custody, integrity, quality, challenge and expert opinion?","id":"evidence-source-receipt-custody-integrity-quality-challenge-and-expert-opinion-q02","kind":"retention"},{"text":"How may evidence source, receipt, custody, integrity, quality, challenge and expert opinion be validated, challenged, corrected, related, retained or disposed without losing history?","id":"evidence-source-receipt-custody-integrity-quality-challenge-and-expert-opinion-q03","kind":"authority"}]}]},{"id":"coverage-liability-causation-damage-benefit-and-fraud-assessment","name":"Coverage, liability, causation, damage, benefit and fraud assessment","description":"Groups claim-handling context for coverage, liability, causation, damage, benefit and fraud assessment.","findings":[{"id":"policy-term-in-force-coverage-exclusion-condition-limit-deductible-and-coordination-analysis","name":"Policy term, in-force, coverage, exclusion, condition, limit, deductible and coordination analysis","description":"Records policy term, in-force, coverage, exclusion, condition, limit, deductible and coordination analysis as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish policy term, in-force, coverage, exclusion, condition, limit, deductible and coordination analysis?","id":"policy-term-in-force-coverage-exclusion-condition-limit-deductible-and-coordination-analysis-q01","kind":"decision"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support policy term, in-force, coverage, exclusion, condition, limit, deductible and coordination analysis?","id":"policy-term-in-force-coverage-exclusion-condition-limit-deductible-and-coordination-analysis-q02","kind":"security"},{"text":"How may policy term, in-force, coverage, exclusion, condition, limit, deductible and coordination analysis be validated, challenged, corrected, related, retained or disposed without losing history?","id":"policy-term-in-force-coverage-exclusion-condition-limit-deductible-and-coordination-analysis-q03","kind":"relationship"}]},{"id":"liability-causation-damage-benefit-adjustment-estimate-uncertainty-and-fraud-indicator","name":"Liability, causation, damage, benefit, adjustment, estimate, uncertainty and fraud indicator","description":"Records liability, causation, damage, benefit, adjustment, estimate, uncertainty and fraud indicator as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish liability, causation, damage, benefit, adjustment, estimate, uncertainty and fraud indicator?","id":"liability-causation-damage-benefit-adjustment-estimate-uncertainty-and-fraud-indicator-q01","kind":"measurement"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support liability, causation, damage, benefit, adjustment, estimate, uncertainty and fraud indicator?","id":"liability-causation-damage-benefit-adjustment-estimate-uncertainty-and-fraud-indicator-q02","kind":"validation"},{"text":"How may liability, causation, damage, benefit, adjustment, estimate, uncertainty and fraud indicator be validated, challenged, corrected, related, retained or disposed without losing history?","id":"liability-causation-damage-benefit-adjustment-estimate-uncertainty-and-fraud-indicator-q03","kind":"provenance"}]}]}]},{"id":"decisions-settlement-and-financial-handoffs","name":"Decisions, settlement and financial handoffs","description":"Groups governed context for decisions, settlement and financial handoffs.","layers":[{"id":"reserves-authority-limits-and-reasoned-decisions","name":"Reserves, authority limits and reasoned decisions","description":"Groups claim-handling context for reserves, authority limits and reasoned decisions.","findings":[{"id":"estimate-reserve-external-reference-authority-limit-review-and-change-rationale","name":"Estimate, reserve external reference, authority limit, review and change rationale","description":"Records estimate, reserve external reference, authority limit, review and change rationale as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish estimate, reserve external reference, authority limit, review and change rationale?","id":"estimate-reserve-external-reference-authority-limit-review-and-change-rationale-q01","kind":"provenance"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support estimate, reserve external reference, authority limit, review and change rationale?","id":"estimate-reserve-external-reference-authority-limit-review-and-change-rationale-q02","kind":"privacy"},{"text":"How may estimate, reserve external reference, authority limit, review and change rationale be validated, challenged, corrected, related, retained or disposed without losing history?","id":"estimate-reserve-external-reference-authority-limit-review-and-change-rationale-q03","kind":"process"}]},{"id":"coverage-liability-benefit-item-adjudication-acceptance-partial-denial-and-reason","name":"Coverage, liability, benefit, item adjudication, acceptance, partial denial and reason","description":"Records coverage, liability, benefit, item adjudication, acceptance, partial denial and reason as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish coverage, liability, benefit, item adjudication, acceptance, partial denial and reason?","id":"coverage-liability-benefit-item-adjudication-acceptance-partial-denial-and-reason-q01","kind":"decision"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support coverage, liability, benefit, item adjudication, acceptance, partial denial and reason?","id":"coverage-liability-benefit-item-adjudication-acceptance-partial-denial-and-reason-q02","kind":"access"},{"text":"How may coverage, liability, benefit, item adjudication, acceptance, partial denial and reason be validated, challenged, corrected, related, retained or disposed without losing history?","id":"coverage-liability-benefit-item-adjudication-acceptance-partial-denial-and-reason-q03","kind":"decision"}]}]},{"id":"offers-negotiation-settlement-payment-and-recovery-instructions","name":"Offers, negotiation, settlement, payment and recovery instructions","description":"Groups claim-handling context for offers, negotiation, settlement, payment and recovery instructions.","findings":[{"id":"reasoned-offer-counteroffer-negotiation-acceptance-release-and-settlement-terms","name":"Reasoned offer, counteroffer, negotiation, acceptance, release and settlement terms","description":"Records reasoned offer, counteroffer, negotiation, acceptance, release and settlement terms as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish reasoned offer, counteroffer, negotiation, acceptance, release and settlement terms?","id":"reasoned-offer-counteroffer-negotiation-acceptance-release-and-settlement-terms-q01","kind":"lifecycle"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support reasoned offer, counteroffer, negotiation, acceptance, release and settlement terms?","id":"reasoned-offer-counteroffer-negotiation-acceptance-release-and-settlement-terms-q02","kind":"exception"},{"text":"How may reasoned offer, counteroffer, negotiation, acceptance, release and settlement terms be validated, challenged, corrected, related, retained or disposed without losing history?","id":"reasoned-offer-counteroffer-negotiation-acceptance-release-and-settlement-terms-q03","kind":"temporal"}]},{"id":"payment-instruction-payee-allocation-currency-tax-interest-offset-and-clearing-reference","name":"Payment instruction, payee, allocation, currency, tax, interest, offset and clearing reference","description":"Records payment instruction, payee, allocation, currency, tax, interest, offset and clearing reference as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish payment instruction, payee, allocation, currency, tax, interest, offset and clearing reference?","id":"payment-instruction-payee-allocation-currency-tax-interest-offset-and-clearing-reference-q01","kind":"relationship"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support payment instruction, payee, allocation, currency, tax, interest, offset and clearing reference?","id":"payment-instruction-payee-allocation-currency-tax-interest-offset-and-clearing-reference-q02","kind":"identity"},{"text":"How may payment instruction, payee, allocation, currency, tax, interest, offset and clearing reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"payment-instruction-payee-allocation-currency-tax-interest-offset-and-clearing-reference-q03","kind":"composition"}]}]}]},{"id":"communications-disputes-fraud-and-recoveries","name":"Communications, disputes, fraud and recoveries","description":"Groups governed context for communications, disputes, fraud and recoveries.","layers":[{"id":"status-communications-deadlines-complaints-and-reviews","name":"Status communications, deadlines, complaints and reviews","description":"Groups claim-handling context for status communications, deadlines, complaints and reviews.","findings":[{"id":"status-update-request-response-reason-language-channel-delivery-and-deadline","name":"Status update, request, response, reason, language, channel, delivery and deadline","description":"Records status update, request, response, reason, language, channel, delivery and deadline as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish status update, request, response, reason, language, channel, delivery and deadline?","id":"status-update-request-response-reason-language-channel-delivery-and-deadline-q01","kind":"temporal"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support status update, request, response, reason, language, channel, delivery and deadline?","id":"status-update-request-response-reason-language-channel-delivery-and-deadline-q02","kind":"authority"},{"text":"How may status update, request, response, reason, language, channel, delivery and deadline be validated, challenged, corrected, related, retained or disposed without losing history?","id":"status-update-request-response-reason-language-channel-delivery-and-deadline-q03","kind":"evidence"}]},{"id":"internal-review-complaint-ombudsman-arbitration-litigation-appeal-and-remedy-reference","name":"Internal review, complaint, ombudsman, arbitration, litigation, appeal and remedy reference","description":"Records internal review, complaint, ombudsman, arbitration, litigation, appeal and remedy reference as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish internal review, complaint, ombudsman, arbitration, litigation, appeal and remedy reference?","id":"internal-review-complaint-ombudsman-arbitration-litigation-appeal-and-remedy-reference-q01","kind":"relationship"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support internal review, complaint, ombudsman, arbitration, litigation, appeal and remedy reference?","id":"internal-review-complaint-ombudsman-arbitration-litigation-appeal-and-remedy-reference-q02","kind":"relationship"},{"text":"How may internal review, complaint, ombudsman, arbitration, litigation, appeal and remedy reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"internal-review-complaint-ombudsman-arbitration-litigation-appeal-and-remedy-reference-q03","kind":"interoperability"}]}]},{"id":"fraud-referral-subrogation-salvage-and-third-party-recovery","name":"Fraud referral, subrogation, salvage and third-party recovery","description":"Groups claim-handling context for fraud referral, subrogation, salvage and third-party recovery.","findings":[{"id":"fraud-indicator-referral-authority-restriction-outcome-reference-and-non-prejudice","name":"Fraud indicator, referral, authority, restriction, outcome reference and non-prejudice","description":"Records fraud indicator, referral, authority, restriction, outcome reference and non-prejudice as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish fraud indicator, referral, authority, restriction, outcome reference and non-prejudice?","id":"fraud-indicator-referral-authority-restriction-outcome-reference-and-non-prejudice-q01","kind":"security"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support fraud indicator, referral, authority, restriction, outcome reference and non-prejudice?","id":"fraud-indicator-referral-authority-restriction-outcome-reference-and-non-prejudice-q02","kind":"provenance"},{"text":"How may fraud indicator, referral, authority, restriction, outcome reference and non-prejudice be validated, challenged, corrected, related, retained or disposed without losing history?","id":"fraud-indicator-referral-authority-restriction-outcome-reference-and-non-prejudice-q03","kind":"quality"}]},{"id":"subrogation-salvage-contribution-reinsurance-recovery-right-handoff-and-proceeds-reference","name":"Subrogation, salvage, contribution, reinsurance, recovery right, handoff and proceeds reference","description":"Records subrogation, salvage, contribution, reinsurance, recovery right, handoff and proceeds reference as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish subrogation, salvage, contribution, reinsurance, recovery right, handoff and proceeds reference?","id":"subrogation-salvage-contribution-reinsurance-recovery-right-handoff-and-proceeds-reference-q01","kind":"relationship"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support subrogation, salvage, contribution, reinsurance, recovery right, handoff and proceeds reference?","id":"subrogation-salvage-contribution-reinsurance-recovery-right-handoff-and-proceeds-reference-q02","kind":"process"},{"text":"How may subrogation, salvage, contribution, reinsurance, recovery right, handoff and proceeds reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"subrogation-salvage-contribution-reinsurance-recovery-right-handoff-and-proceeds-reference-q03","kind":"state"}]}]}]},{"id":"lifecycle-quality-provenance-retention-interoperability-and-agents","name":"Lifecycle, quality, provenance, retention, interoperability and agents","description":"Groups governed context for lifecycle, quality, provenance, retention, interoperability and agents.","layers":[{"id":"lifecycle-events-reopening-quality-and-fairness-observation","name":"Lifecycle events, reopening, quality and fairness observation","description":"Groups claim-handling context for lifecycle events, reopening, quality and fairness observation.","findings":[{"id":"notified-registered-triaged-investigating-decided-settled-closed-reopened-and-corrected-event","name":"Notified, registered, triaged, investigating, decided, settled, closed, reopened and corrected event","description":"Records notified, registered, triaged, investigating, decided, settled, closed, reopened and corrected event as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish notified, registered, triaged, investigating, decided, settled, closed, reopened and corrected event?","id":"notified-registered-triaged-investigating-decided-settled-closed-reopened-and-corrected-event-q01","kind":"event"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support notified, registered, triaged, investigating, decided, settled, closed, reopened and corrected event?","id":"notified-registered-triaged-investigating-decided-settled-closed-reopened-and-corrected-event-q02","kind":"decision"},{"text":"How may notified, registered, triaged, investigating, decided, settled, closed, reopened and corrected event be validated, challenged, corrected, related, retained or disposed without losing history?","id":"notified-registered-triaged-investigating-decided-settled-closed-reopened-and-corrected-event-q03","kind":"measurement"}]},{"id":"timeliness-fairness-consistency-explanation-burden-complaint-and-outcome-observation","name":"Timeliness, fairness, consistency, explanation, burden, complaint and outcome observation","description":"Records timeliness, fairness, consistency, explanation, burden, complaint and outcome observation as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish timeliness, fairness, consistency, explanation, burden, complaint and outcome observation?","id":"timeliness-fairness-consistency-explanation-burden-complaint-and-outcome-observation-q01","kind":"quality"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support timeliness, fairness, consistency, explanation, burden, complaint and outcome observation?","id":"timeliness-fairness-consistency-explanation-burden-complaint-and-outcome-observation-q02","kind":"temporal"},{"text":"How may timeliness, fairness, consistency, explanation, burden, complaint and outcome observation be validated, challenged, corrected, related, retained or disposed without losing history?","id":"timeliness-fairness-consistency-explanation-burden-complaint-and-outcome-observation-q03","kind":"lifecycle"}]}]},{"id":"provenance-privacy-retention-projection-and-safe-agent-operations","name":"Provenance, privacy, retention, projection and safe agent operations","description":"Groups claim-handling context for provenance, privacy, retention, projection and safe agent operations.","findings":[{"id":"actor-tool-source-method-derivation-event-time-knowledge-time-access-and-audit-reference","name":"Actor, tool, source, method, derivation, event time, knowledge time, access and audit reference","description":"Records actor, tool, source, method, derivation, event time, knowledge time, access and audit reference as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish actor, tool, source, method, derivation, event time, knowledge time, access and audit reference?","id":"actor-tool-source-method-derivation-event-time-knowledge-time-access-and-audit-reference-q01","kind":"provenance"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support actor, tool, source, method, derivation, event time, knowledge time, access and audit reference?","id":"actor-tool-source-method-derivation-event-time-knowledge-time-access-and-audit-reference-q02","kind":"composition"},{"text":"How may actor, tool, source, method, derivation, event time, knowledge time, access and audit reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"actor-tool-source-method-derivation-event-time-knowledge-time-access-and-audit-reference-q03","kind":"event"}]},{"id":"retention-hold-redaction-mapping-loss-idempotency-dry-run-post-check-and-contestability","name":"Retention, hold, redaction, mapping loss, idempotency, dry-run, post-check and contestability","description":"Records retention, hold, redaction, mapping loss, idempotency, dry-run, post-check and contestability as source-qualified claim-handling context while preserving external master ownership and separating request, assessment, decision, instruction and execution.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish retention, hold, redaction, mapping loss, idempotency, dry-run, post-check and contestability?","id":"retention-hold-redaction-mapping-loss-idempotency-dry-run-post-check-and-contestability-q01","kind":"retention"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support retention, hold, redaction, mapping loss, idempotency, dry-run, post-check and contestability?","id":"retention-hold-redaction-mapping-loss-idempotency-dry-run-post-check-and-contestability-q02","kind":"evidence"},{"text":"How may retention, hold, redaction, mapping loss, idempotency, dry-run, post-check and contestability be validated, challenged, corrected, related, retained or disposed without losing history?","id":"retention-hold-redaction-mapping-loss-idempotency-dry-run-post-check-and-contestability-q03","kind":"retention"}]}]}]}]},"agentConduct":{"may":["Acknowledge and triage incoming notifications.","Request missing documents and track replies.","Prepare a coverage assessment draft citing policy terms.","Send status updates to claimants."],"mustNot":["Accept or deny coverage without an authorised handler.","Accuse a claimant of fraud or flag them publicly.","Request medical or personal data beyond what the claim needs.","Delay acknowledgement or decisions past regulatory deadlines.","Issue payments directly."],"requiresHuman":["Coverage and liability decisions.","Fraud referrals.","Settlement offers and complaint handling."]},"ethics":{"considerations":["Claimants are often in distress after a loss; delays and unclear reasons cause harm.","Health and injury data are sensitive and must be minimal and protected.","Automated fraud scoring can discriminate and wrongly deny valid claims."],"affectedParties":["Claimants and beneficiaries","Injured third parties","Claims handlers and experts"]},"owners":{"steward":"Dimension owner and insurance-claim-handling mandate","roles":[{"name":"Claim handling owner","responsibilities":["Own case scope, mandate, service and lifecycle."]},{"name":"Claim handler or adjuster","responsibilities":["Own assigned intake, investigation, assessment and communications within authority."]},{"name":"Coverage and legal reviewer","responsibilities":["Own policy interpretation and reasoned exception review."]},{"name":"Medical, engineering or valuation expert","responsibilities":["Own source-qualified expert observations without deciding the claim outside delegation."]},{"name":"Settlement authority","responsibilities":["Own decision and settlement approvals within recorded limits."]},{"name":"Fraud referral steward","responsibilities":["Own restricted indicator review and independent referral."]},{"name":"Complaint and dispute reviewer","responsibilities":["Own impartial review, escalation and redress handoffs."]},{"name":"Privacy, records and assurance steward","responsibilities":["Own protected views, holds, retention, disclosure and auditability."]}],"masterSystems":[]},"relations":[{"target":"WM-ECO-036 Insurance Claim","type":"composes","note":"Candidate composition preserving claim identity and handling-case separation; no approved edge exists."},{"target":"WM-ECO-003 Insurance Policy and policy, coverage, loss, party, asset, injury and damage models","type":"references","note":"Bind authoritative contract and subject facts while their masters retain identity and lifecycle."},{"target":"Evidence, Expert, Fraud Case, Complaint, Ombudsman, Arbitration, Court Case, Communication, Audit and Record models","type":"references","note":"Bind investigation evidence, referrals, redress and accountable communication without lifecycle cascade."},{"target":"Reserve, Payment, Accounting Entry, Reinsurance, Subrogation, Salvage and Recovery models","type":"references","note":"Issue bounded instructions and record receipts while external financial and rights masters own execution and proceeds."},{"target":"IAIS ICP, NAIC claim-conduct models, FCA ICOBS, EU motor and distribution directives, HL7 FHIR and ACORD P&C","type":"aligned","note":"Project version-pinned conduct, regulatory and exchange views with declared jurisdiction, maturity and information loss."},{"target":"WM-ECO-036 Insurance Claim candidate composer","type":"neighbor","note":"The claim master owns the claim identifier and substantive policy-loss-demand assertions. This aggregate owns one handling process, its work, decisions and handoffs. The ledger relation is candidate, not approved."},{"target":"WM-ECO-003 Insurance Policy and Coverage","type":"neighbor","note":"The policy master owns contract, insured risk, coverage terms and policy lifecycle. The handling case records source-qualified interpretations and decision-time snapshots without rewriting the contract."},{"target":"Evidence, Expert, Damage, Injury and Loss Event","type":"neighbor","note":"External masters own source observations and subject facts. This case records requests, custody references, validation, use and resulting assessments."},{"target":"Fraud Case, Complaint, Ombudsman, Arbitration and Court Case","type":"neighbor","note":"This process may create a controlled referral or bind an external review outcome; it does not decide fraud or absorb independent redress and adjudication lifecycles."},{"target":"Reserve, Payment, Accounting, Reinsurance, Subrogation and Salvage","type":"neighbor","note":"This model owns estimates, approval and handoff assertions needed to explain handling. External financial and recovery masters own booking, execution, clearing, rights and proceeds."},{"target":"WM-ECO-036","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system handling-case identifier qualified by insurer, source and profile.","Governed globally resolvable handling-case IRI.","Dimension UUID when neither preceding identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A handling case has a claim number, a policy reference, a claimant, a loss date and a handler.","It is confused with the claim, the policy, the loss event or a fraud case."]},"capabilities":{"applicability":"required","items":["Register handling case: Governed operation to register handling case with attributable evidence and no hidden master-system mutation.","Acknowledge and triage notification: Governed operation to acknowledge and triage notification with attributable evidence and no hidden master-system mutation.","Bind claim, policy, loss and parties: Governed operation to bind claim, policy, loss and parties with attributable evidence and no hidden master-system mutation.","Plan and conduct investigation: Governed operation to plan and conduct investigation with attributable evidence and no hidden master-system mutation.","Assess coverage, liability and benefit: Governed operation to assess coverage, liability and benefit with attributable evidence and no hidden master-system mutation.","Refer suspected fraud: Governed operation to refer suspected fraud with attributable evidence and no hidden master-system mutation.","Issue reasoned decision or offer: Governed operation to issue reasoned decision or offer with attributable evidence and no hidden master-system mutation.","Settle and initiate financial handoffs: Governed operation to settle and initiate financial handoffs with attributable evidence and no hidden master-system mutation.","Review, dispute, reopen or correct: Governed operation to review, dispute, reopen or correct with attributable evidence and no hidden master-system mutation.","Close, project, retain and audit: Governed operation to close, project, retain and audit with attributable evidence and no hidden master-system mutation."]},"hazards":{"applicability":"required","items":["Wrongful denial leaving people without support.","Data leaks of health or financial information.","Missed regulatory deadlines leading to penalties."]},"interfaces":{"applicability":"required","items":["ACORD data standards.","ISO 20022 for settlement payments."]},"context":{"applicability":"required","items":["Deadlines, reasonableness, settlement duties, disclosure, interest, limitation and appeal rights depend on jurisdiction and policy class.","NAIC models are United States model texts rather than automatically applicable state law; FCA and EU sources are regional profiles.","Health claim exchanges and patient-facing projections vary by trading-partner agreement, jurisdiction and FHIR implementation guide."]}},"sources":[{"title":"Insurance Core Principles and Common Framework for the Supervision of Internationally Active Insurance Groups","url":"https://www.iaisweb.org/uploads/2024/12/IAIS-ICPs-and-ComFrame-adopted-in-December-2024.pdf","note":"International Association of Insurance Supervisors"},{"title":"Unfair Claims Settlement Practices Act","url":"https://content.naic.org/sites/default/files/model-law-900.pdf","note":"National Association of Insurance Commissioners"},{"title":"Unfair Property/Casualty Claims Settlement Practices Model Regulation","url":"https://content.naic.org/sites/default/files/model-law-902.pdf","note":"National Association of Insurance Commissioners"},{"title":"Market Conduct Record Retention and Production Model Regulation","url":"https://content.naic.org/sites/default/files/model-law-910.pdf","note":"National Association of Insurance Commissioners"},{"title":"ICOBS 8 Claims handling","url":"https://handbook.fca.org.uk/handbook/icobs8","note":"Financial Conduct Authority"},{"title":"Guidelines on Complaints-Handling by Insurance Undertakings","url":"https://www.eiopa.europa.eu/publications/guidelines-complaints-handling-insurance-undertakings_en","note":"European Insurance and Occupational Pensions Authority"},{"title":"Directive 2009/103/EC relating to insurance against civil liability in respect of the use of motor vehicles","url":"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32009L0103","note":"European Union"},{"title":"Directive (EU) 2016/97 on insurance distribution","url":"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016L0097","note":"European Union"},{"title":"Enterprise Act 2016, Part 5: Late Payment of Insurance Claims","url":"https://www.legislation.gov.uk/ukpga/2016/12/notes/division/6/index.htm","note":"United Kingdom Legislation"},{"title":"FHIR R5 Claim","url":"https://hl7.org/fhir/R5/claim.html","note":"Health Level Seven International"},{"title":"FHIR R5 ClaimResponse","url":"https://hl7.org/fhir/R5/claimresponse.html","note":"Health Level Seven International"},{"title":"FHIR R5 ExplanationOfBenefit","url":"https://hl7.org/fhir/R5/explanationofbenefit.html","note":"Health Level Seven International"},{"title":"ACORD Property and Casualty Data Standards","url":"https://www-dev.acord.org/standards-architecture/acord-data-standards/Property_Casualty_Data_Standards","note":"Association for Cooperative Operations Research and Development"},{"title":"Regulation (EU) 2016/679 General Data Protection Regulation","url":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","note":"European Union"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/info/rfc3339/","note":"Internet Engineering Task Force"}],"openQuestions":["Approve or reject the WM-ECO-036 composition and define claim-to-handling-case cardinality, reopening and multi-insurer coordination semantics.","Create line-of-business profiles with specialized evidence, benefit, authority, reserve, settlement and recovery rules.","Create jurisdiction profiles for deadlines, reasoned decisions, interest, limitation, privacy, complaints, redress, retention and catastrophe duties.","Test full licensed ACORD mappings and selected FHIR implementation guides without treating either as universal semantics.","Obtain supplemental Claude or Grok review and resolve any material challenge before canonical promotion.","Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.","WM-ECO-036 COMPOSE WM-ACT-045 is a candidate relation, not an approved edge.","Life, health, disability, workers compensation, property, motor, liability, travel, cyber, marine, reinsurance and catastrophe handling require separate profiles.","ACORD evidence is limited to public overview material and HL7 FHIR R5 financial resources are Trial Use; no full ACORD or universal FHIR conformance is claimed."],"resources":{"spec":"/models/wm-act-045-insurance-claim-handling/spec.yaml","agents":"/models/wm-act-045-insurance-claim-handling/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-045"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-act-045-insurance-claim-handling/spec.yaml","ver-cy/world-models/card-supplements/wm-act-045-insurance-claim-handling.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T08:54:37Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}