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-011version1.0.0- Default Profile
balanced- Default Scenario
standard- Algorithm
TOPSIS- Weight Strategy
- Expert (Manual) (API value
Expert) - Catalog
DKR-AUTO-RUNTIME-001, version13.9.3
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 ID | Name | Description | Direction | Weight | Unit | Data Type | Validation | Required |
|---|---|---|---|---|---|---|---|---|
claim_severity_score | Claim Severity Score | Overall severity of the reported loss. | minimize | 25 | Score | Number | score_0_to_100 | true |
customer_impact_score | Customer Impact Score | Hardship, mobility impact, complaint sensitivity, or service urgency. | maximize | 20 | Score | Number | score_0_to_100 | true |
coverage_clarity_score | Coverage Clarity Score | How clearly policy, endorsements, dates, and loss facts support coverage determination. | maximize | 20 | Score | Number | score_0_to_100 | true |
fraud_risk_score | Fraud Risk Score | Likelihood that suspicious indicators require special investigation. | minimize | 20 | Score | Number | score_0_to_100 | true |
estimated_loss_amount | Estimated Loss Amount | Estimated total indemnity exposure before final adjudication. | minimize | 15 | Currency | Currency | non_negative_currency | true |
Data Preparation Guide
Constraint Processing
This decision currently has no catalog-defined hard constraints. All validated candidates proceed to criteria-based ranking.
| Verified Catalog Constraint | Status | Effect |
|---|---|---|
None returned by Decision Catalog for AUTO-INS-011 | No hard constraints defined | Candidate eligibility is determined by request validation; all validated candidates are ranked by criteria. |
{
"constraintSummary": {
"definedConstraintCount": 0,
"activeConstraintCount": 0,
"eligibleOptionCount": 3,
"excludedOptionCount": 0,
"eligibleOptions": [
"CLAIM-011-01",
"CLAIM-011-02",
"CLAIM-011-03"
],
"excludedOptions": []
}
}
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 Path | Transformation | Canonical Criterion ID | Unit | Validation |
|---|---|---|---|---|
option.assessment.claimSeverityScore | direct value | claim_severity_score | Score | Input Contract |
option.assessment.customerImpactScore | direct value | customer_impact_score | Score | Input Contract |
option.assessment.coverageClarityScore | direct value | coverage_clarity_score | Score | Input Contract |
option.risk.fraudRiskScore | direct value | fraud_risk_score | Score | Input Contract |
option.financial.estimatedLossAmount | direct value | estimated_loss_amount | Currency | Input Contract |
{
"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
}
}
]
}
{
"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
}
}
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 ID | Name | Purpose |
|---|---|---|
balanced | Balanced | Preserves the default criterion priorities for this insurance decision. |
cost_control | Cost Control | Emphasizes financial leakage, claim cost, reserves, and expense control. |
risk_averse | Risk Averse | Emphasizes coverage, liability, fraud exposure, severity, and compliance risk. |
customer_focused | Customer Focused | Emphasizes service speed, customer impact, and experience quality. |
| Scenario ID | Name | Use When |
|---|---|---|
standard | Standard Claim Handling | Ordinary claim volume and complete claim information. |
catastrophe_event | Catastrophe Event | High-volume event conditions require faster triage and severity prioritization. |
coverage_uncertainty | Coverage Uncertainty | Policy, liability, or eligibility information is incomplete. |
customer_escalation | Customer Escalation | Complaint 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.
{
"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 -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.
{
"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": []
}
decisionResult.winner.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.
{
"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
}
}
}
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": {
"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.
| ServiceName | Operation | RequestId | CorrelationId | DecisionId | Status | Timestamp |
|---|---|---|---|---|---|---|
| Identity | Token issued | identity request | optional | Success | UTC | |
| Decision Catalog | DecisionCatalog.DecisionDefinition | Decision Service propagated request | auto-ins-011-demo-001 | AUTO-INS-011 | Success | UTC |
| Decision Service | Decide | Decision Service request | auto-ins-011-demo-001 | AUTO-INS-011 | Success | UTC |
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.
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
| Symptom | Likely Cause | HTTP Status or Error | Corrective Action | Where to Investigate |
|---|---|---|---|---|
| Token rejected | Invalid credentials or access code | 401 or 400 | Request a new server-side token; do not expose credentials in browser JavaScript. | IdentityAuditEvents |
| Unknown decision ID | Decision is absent from the active Decision Catalog | 404 | Verify AUTO-INS-011 in /decisioncatalog/decisions/AUTO-INS-011. | Decision Catalog logs |
| Invalid profile or scenario | Request value is not listed in decision metadata | 400 | Use one of the profile or scenario IDs returned by Decision Catalog. | Decision Service validation logs |
| Missing criterion | Option values omit a required canonical criterion | 400 validation error | Send all five required AUTO-INS-011 criteria for every claim. | Decision Service validation response |
| Out-of-range value | Score outside 0-100 or negative currency value | 400 validation error | Apply score_0_to_100 and non_negative_currency before submit. | Client validation, Decision Service validation |
| Service unavailable | Decision Catalog, Decision Service, or Identity unavailable | 5xx or non-JSON upstream error | Check health endpoints and server logs. | Hosting/IIS logs and DecisioQ logs |
| Explanation unavailable | Explanation provider disabled or failed silently | Success with a top-level explanation object | Use deterministic decisionResult; inspect the returned explanation object for available context and warnings. | Decision Service application logs |
| Download link fails | Static asset missing from website | 404 | Verify 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.
