DecisioQ System Architecture Decision Concepts Decision List API Guide Client Kit Developer Center Decision Studio Quick Start Playground End-to-End Examples

AUTO-INS-011 End-to-End Example

Determine Claim Intake Priority ranks new claims by urgency, severity, customer impact, coverage clarity, fraud risk, and estimated loss exposure.

Automotive Auto Insurance Claims Intake & Triage TOPSIS
IdentityIssue bearer token
Decision CatalogDiscover decision knowledge
MappingTranslate business data
Decision ServiceExecute request
Decision ServiceRank claims
ExplanationExplain the result

Overview

AUTO-INS-011, Determine Claim Intake Priority, ranks new auto-insurance claims by urgency, severity, customer impact, handling risk, and financial exposure.

Decision ID
AUTO-INS-011
Decision Name
Determine Claim Intake Priority
Description
Rank new claims by urgency, severity, customer impact, and handling risk.
Industry
Automotive
Sector
Auto Insurance (AUTO-INS)
Category
Claims Intake & Triage (AUTO-INS-CLAIMS-INTAKE-TRIAGE)
Decision Preparation Model
auto-insurance-determine-claim-intake-priorit-auto-ins-011 version 1.0.0
Default Profile
balanced
Default Scenario
standard
Algorithm
TOPSIS
Weight Strategy
Expert (Manual) (API value Expert)
Catalog
DKR-AUTO-RUNTIME-001, version 13.9.3
The deterministic Decision Service evaluates and ranks the claims. The Explanation of Decision Result is explanatory only and must not select, rerank, recalculate, or override the deterministic result.

Understanding This Decision

Determine Claim Intake Priority helps claims intake teams decide which newly reported claims should be reviewed first by balancing claim severity, customer impact, coverage clarity, fraud risk, and estimated loss exposure.

Business question

Which new claim should receive the highest intake priority under the selected operating context?

Expected outcome

A ranked list of candidate claims with a recommended highest-priority claim and criterion-level score evidence.

Typical users

Claims intake teams, claims operations managers, triage supervisors, customer care leaders, and integration teams building claims workflow automation.

Decision boundary

Use this decision to prioritize supplied claim cases. It does not replace coverage review, fraud investigation, legal review, adjuster judgment, or privacy controls for sensitive claim data.

Criteria

Use exact criterionId keys. Display names can change; canonical IDs drive validation, mapping, weighting, and execution.

Criterion IDNameDescriptionDirectionWeightUnitData TypeValidationRequired
claim_severity_scoreClaim Severity ScoreOverall severity of the reported loss.minimize25ScoreNumberscore_0_to_100true
customer_impact_scoreCustomer Impact ScoreHardship, mobility impact, complaint sensitivity, or service urgency.maximize20ScoreNumberscore_0_to_100true
coverage_clarity_scoreCoverage Clarity ScoreHow clearly policy, endorsements, dates, and loss facts support coverage determination.maximize20ScoreNumberscore_0_to_100true
fraud_risk_scoreFraud Risk ScoreLikelihood that suspicious indicators require special investigation.minimize20ScoreNumberscore_0_to_100true
estimated_loss_amountEstimated Loss AmountEstimated total indemnity exposure before final adjudication.minimize15CurrencyCurrencynon_negative_currencytrue

Data Preparation Guide

Loading criterion-specific integration guidance...

Constraint Processing

This decision currently has no catalog-defined hard constraints. All validated candidates proceed to criteria-based ranking.

Verified Catalog ConstraintStatusEffect
None returned by Decision Catalog for AUTO-INS-011No hard constraints definedCandidate eligibility is determined by request validation; all validated candidates are ranked by criteria.
Eligible and Excluded Candidates
{
  "constraintSummary": {
    "definedConstraintCount": 0,
    "activeConstraintCount": 0,
    "eligibleOptionCount": 3,
    "excludedOptionCount": 0,
    "eligibleOptions": [
      "CLAIM-011-01",
      "CLAIM-011-02",
      "CLAIM-011-03"
    ],
    "excludedOptions": []
  }
}
Constraint Handling Pattern
const constraints = decisionDetail.constraints || [];
if (constraints.length === 0) {
  // No catalog-defined hard constraints.
  // Submit all validated candidates for criteria-based ranking.
}

const summary = response.constraintSummary;
const excluded = response.decisionResult?.excludedOptions || [];

Excluded candidates do not participate in ranking because hard constraints are evaluated before scoring. For AUTO-INS-011, no candidates are excluded by catalog-defined constraints because Decision Catalog currently defines none for this decision.

Decision Preparation Model

The published Decision Preparation Model validates and transforms illustrative Business Data into the canonical criteria required by AUTO-INS-011 before Decision Service applies ranking.

Profile ID
auto-insurance-determine-claim-intake-priorit-auto-ins-011
Version
1.0.0
Options Path
$.claims
Option ID Path
$.optionId
Display Name Path
$.name
Client Business Data PathTransformationCanonical Criterion IDUnitValidation
option.assessment.claimSeverityScoredirect valueclaim_severity_scoreScoreInput Contract
option.assessment.customerImpactScoredirect valuecustomer_impact_scoreScoreInput Contract
option.assessment.coverageClarityScoredirect valuecoverage_clarity_scoreScoreInput Contract
option.risk.fraudRiskScoredirect valuefraud_risk_scoreScoreInput Contract
option.financial.estimatedLossAmountdirect valueestimated_loss_amountCurrencyInput Contract
Illustrative Business Data
{
  "requestContext": {
    "sourceSystem": "automotive-profile-factory",
    "correlationId": "factory-auto-ins-011"
  },
  "claims": [
    {
      "optionId": "CLAIM-011-01",
      "name": "Determine Claim Intake Priority Option 1",
      "assessment": {
        "claimSeverityScore": 46.0,
        "customerImpactScore": 50.0,
        "coverageClarityScore": 64.0
      },
      "risk": {
        "fraudRiskScore": 30.0
      },
      "financial": {
        "estimatedLossAmount": 50000.0
      }
    },
    {
      "optionId": "CLAIM-011-02",
      "name": "Determine Claim Intake Priority Option 2",
      "assessment": {
        "claimSeverityScore": 43.0,
        "customerImpactScore": 75.0,
        "coverageClarityScore": 59.0
      },
      "risk": {
        "fraudRiskScore": 51.0
      },
      "financial": {
        "estimatedLossAmount": 42500.0
      }
    }
  ]
}
Prepared Option Values
{
  "optionId": "CLAIM-011-01",
  "name": "Determine Claim Intake Priority Option 1",
  "values": {
    "claim_severity_score": 46.0,
    "customer_impact_score": 50.0,
    "coverage_clarity_score": 64.0,
    "fraud_risk_score": 30.0,
    "estimated_loss_amount": 50000.0
  }
}
This example illustrates the published request structure. Adapt it to your organization and validate it against the Input Contract.

Profiles and Scenarios

This example selects a Profile for evaluation emphasis and a Scenario for operating context. Discover both from the selected Decision Catalog definition.

Profile IDNamePurpose
balancedBalancedPreserves the default criterion priorities for this insurance decision.
cost_controlCost ControlEmphasizes financial leakage, claim cost, reserves, and expense control.
risk_averseRisk AverseEmphasizes coverage, liability, fraud exposure, severity, and compliance risk.
customer_focusedCustomer FocusedEmphasizes service speed, customer impact, and experience quality.
Scenario IDNameUse When
standardStandard Claim HandlingOrdinary claim volume and complete claim information.
catastrophe_eventCatastrophe EventHigh-volume event conditions require faster triage and severity prioritization.
coverage_uncertaintyCoverage UncertaintyPolicy, liability, or eligibility information is incomplete.
customer_escalationCustomer EscalationComplaint risk, hardship, or service-level commitments are elevated.

Prepared Input

The active Decision Service Prepared Criteria Mode contract accepts decisionId, profileId, scenarioId, algorithm, weightStrategy, runSensitivity, requestContext, and options.

Prepared Criteria Mode JSON
{
  "decisionId": "AUTO-INS-011",
  "profileId": "balanced",
  "scenarioId": "standard",
  "algorithm": "TOPSIS",
  "weightStrategy": "Expert",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "auto-ins-011-demo-001"
  },
  "options": [
    {
      "optionId": "CLAIM-011-01",
      "name": "Claim CASE-001",
      "values": {
        "claim_severity_score": 83,
        "customer_impact_score": 83,
        "coverage_clarity_score": 83,
        "fraud_risk_score": 78,
        "estimated_loss_amount": 62500
      }
    },
    {
      "optionId": "CLAIM-011-02",
      "name": "Claim CASE-002",
      "values": {
        "claim_severity_score": 75,
        "customer_impact_score": 75,
        "coverage_clarity_score": 75,
        "fraud_risk_score": 70,
        "estimated_loss_amount": 107500
      }
    }
  ]
}

Execute

cURL
curl -X POST "https://dde.vinquery.com/api/v1/decide" \
  -H "Authorization: Bearer ${DECISIOQ_TOKEN}" \
  -H "Content-Type: application/json" \
  -H "X-Correlation-Id: auto-ins-011-demo-001" \
  --data @auto-ins-011-execute.json

Decision Service retrieves authoritative criteria, profiles, scenarios, and validation metadata from Decision Catalog, composes the engine-ready request, and executes the deterministic ranking.

Interpret the Result

Every successful response includes the deterministic decisionResult and a top-level explanation object. Use decisionResult.winner and decisionResult.ranking as the ranking; the explanation adds context but does not change it. Scores are useful within the same run, not across unrelated decisions or catalog versions.

Successful Response Shape
{
  "service": "decisioq",
  "version": "7.6.3",
  "requestId": "0HNE...",
  "operation": "Decide",
  "success": true,
  "timestampUtc": "2026-07-19T00:00:00Z",
  "requestContext": {
    "correlationId": "auto-ins-011-demo-001",
    "decision": {
      "id": "AUTO-INS-011",
      "name": "Prioritize Insurance Claims",
      "catalogVersion": "13.9.3"
    }
  },
  "configurationUsed": {
    "weightStrategy": { "value": "Expert", "source": "ExplicitRequest" },
    "rankingAlgorithm": { "value": "TOPSIS", "source": "ExplicitRequest" },
    "profile": { "value": "balanced", "source": "ExplicitRequest" },
    "scenario": { "value": "standard", "source": "ExplicitRequest" },
    "sensitivity": { "value": false, "source": "PlatformDefault" }
  },
  "decisionResult": {
    "winner": "CLAIM-011-01",
    "confidence": 72.4,
    "ranking": [
      {
        "optionId": "CLAIM-011-01",
        "score": 0.8421,
        "breakdown": {
          "claim_severity_score": 0.15,
          "customer_impact_score": 0.20
        },
        "normalizationBreakdown": {}
      }
    ],
    "excludedOptions": []
  },
  "explanation": {
      "summary": "The selected claim has the strongest overall priority.",
      "whyRecommended": "It combined high customer impact and clear coverage with manageable loss exposure.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard claim-handling scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
  },
  "constraintSummary": {
    "definedConstraintCount": 0,
    "activeConstraintCount": 0,
    "eligibleOptionCount": 3,
    "excludedOptionCount": 0,
    "eligibleOptions": [
    "CLAIM-011-01",
    "CLAIM-011-02",
    "CLAIM-011-03"
    ],
    "excludedOptions": []
  },
  "warnings": []
}
WinnerThe selected claim option ID in decisionResult.winner.
WarningsNon-fatal issues to review before relying on the recommendation.
Operational MetadataKeep request IDs, correlation IDs, selected profile, selected scenario, and catalog version for support.

Sensitivity Analysis

Use "runSensitivity": true when the client needs evidence about recommendation stability. DecisioQ varies criterion weights by controlled factors while keeping submitted options and values fixed.

Sensitivity Result Shape
{
  "runSensitivity": true,
  "sensitivityResult": {
    "stableWinner": true,
    "winner": "CLAIM-011-01",
    "mostSensitiveCriterion": "claim_severity_score",
    "confidence": 95,
    "criterionImpacts": {
      "claim_severity_score": 0.1842
    },
    "winnerChangeCounts": {
      "claim_severity_score": 0
    }
  }
}
Sensitivity Analysis does not replace the deterministic decision result. It provides evidence about how stable that result is under permitted changes.

Explanation of Decision Result

Every successful response includes a provider-neutral top-level explanation object. The Explanation Service receives the finalized deterministic result and a controlled evidence package; the object adds context but does not change the ranking.

Explanation Shape
{
  "explanation": {
      "summary": "The selected claim has the strongest overall priority.",
      "whyRecommended": "It combined high customer impact and clear coverage with manageable loss exposure.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard claim-handling scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
  }
}

The Explanation of Decision Result must not receive raw private claim files or unrestricted notes. It explains the already-finalized result; it does not select, rerank, recalculate, or override it.

Tracing and Logs

Use request identifiers to connect client, Identity, Decision Catalog, and Decision Service activity. Authentication and identity-security activity belongs in IdentityAuditEvents. Catalog, mapping, decision execution, sensitivity, and explanation operations belong in decisioq_log.

X-Request-Id
Optional client-supplied request ID. If omitted, Decision Service or Decision Catalog generates one.
X-Correlation-Id
Optional client workflow ID propagated from Decision Service to Decision Catalog.
requestContext.correlationId
Payload value echoed by Decision Service and used for execution logging.
DecisionId
Recorded for decision-specific operations. General catalog and identity operations may not have a decision ID.
ServiceNameOperationRequestIdCorrelationIdDecisionIdStatusTimestamp
IdentityToken issuedidentity requestoptionalSuccessUTC
Decision CatalogDecisionCatalog.DecisionDefinitionDecision Service propagated requestauto-ins-011-demo-001AUTO-INS-011SuccessUTC
Decision ServiceDecideDecision Service requestauto-ins-011-demo-001AUTO-INS-011SuccessUTC
Never log API Consumer secrets, bearer tokens, raw authorization headers, or sensitive claim details.

Code Examples

These examples authenticate, retrieve AUTO-INS-011 metadata, validate profile and scenario selections, execute the decision, pass a correlation ID, and print the deterministic result.

Environment variables
DECISIOQ_CLIENT_ID
DECISIOQ_CLIENT_SECRET

Optional:
DECISIOQ_IDENTITY_URL=https://identity.vinquery.com/connect/token
DECISIOQ_DKS_URL=https://dks.vinquery.com
DECISIOQ_DDE_URL=https://dde.vinquery.com

Troubleshooting

SymptomLikely CauseHTTP Status or ErrorCorrective ActionWhere to Investigate
Token rejectedInvalid credentials or access code401 or 400Request a new server-side token; do not expose credentials in browser JavaScript.IdentityAuditEvents
Unknown decision IDDecision is absent from the active Decision Catalog404Verify AUTO-INS-011 in /decisioncatalog/decisions/AUTO-INS-011.Decision Catalog logs
Invalid profile or scenarioRequest value is not listed in decision metadata400Use one of the profile or scenario IDs returned by Decision Catalog.Decision Service validation logs
Missing criterionOption values omit a required canonical criterion400 validation errorSend all five required AUTO-INS-011 criteria for every claim.Decision Service validation response
Out-of-range valueScore outside 0-100 or negative currency value400 validation errorApply score_0_to_100 and non_negative_currency before submit.Client validation, Decision Service validation
Service unavailableDecision Catalog, Decision Service, or Identity unavailable5xx or non-JSON upstream errorCheck health endpoints and server logs.Hosting/IIS logs and DecisioQ logs
Explanation unavailableExplanation provider disabled or failed silentlySuccess with a top-level explanation objectUse deterministic decisionResult; inspect the returned explanation object for available context and warnings.Decision Service application logs
Download link failsStatic asset missing from website404Verify the file exists under examples/auto-ins-011.Website static files

Production Checklist

Security

Keep API Consumer credentials server-side, use HTTPS, cache JWTs, renew before expiration, never log secrets, and ensure the API Consumer is linked to a DecisioQ account for usage accounting.

Knowledge and Versioning

Retrieve Decision Catalog metadata, preserve decision preparation model version 1.0.0, and monitor catalog version changes.

Execution Reliability

Use timeouts, cancellation tokens, structured error handling, and avoid unsafe automatic retries unless idempotency is established.

Observability

Propagate X-Correlation-Id, retain requestId, and distinguish Decision Catalog failures from Decision Service failures.

Explanation Safety

Persist deterministic results separately and isolate explanation failure from ranking success.

Testing

Use contract tests, validation tests, sensitivity tests, and privacy-safe claim samples.