Deduplication Hash
Objective
Capture and validate the deduplication hash element within the Incident Identity & Workflow layer.
UAIF requirement
The incident record should implement the canonical deduplication_hash field using the defined UAIF data type, validation constraints, and conditional rules.
Business impact
Supports stable incident identity, deduplication, workflow tracking and an auditable reporting record.
Validation approach
Validate deduplication_hash for required in the Core profile, pattern conformance. Then review semantic consistency against the source incident evidence and the selected conformance profile.
Expected evidence
Retain the source record or analyst input for deduplication_hash, schema-validation output, transformation history, selected profile, schema version and reviewer rationale where judgement is involved.
Mapping and source
UAIF Schema Specification; UAIF Technical Specification; JSON pointer /properties/deduplication_hash.
Implementation guidance
Populate deduplication_hash from an identified source or documented analyst decision. Enforce the schema constraints at record creation and update, preserve the original value and provenance, and surface validation failures without silently coercing data.
Assessment considerations
Sample records across normal, boundary and invalid conditions. Confirm that deduplication_hash is populated only when applicable, conditional rules are enforced, provenance is retained and downstream systems do not change its meaning or precision.
Canonical schema definition
| JSON property | deduplication_hash |
|---|---|
| Required in core profile | Yes |
| Type | "string" |
| pattern | ^[a-fA-F0-9]{64}$ |
Source: UAIF Schema Specification and UAIF Core JSON Schema.