# De-Identified Claim Chronology Builder - TheAICommand skill file

Name: De-Identified Claim Chronology Builder
Version: 1.0
Date: 2026-08-15
Source: https://theaicommand.com/library/skills
Article: https://theaicommand.com/workers-comp/claim-chronology-skill-file
Platforms: ChatGPT (Skills or a project), Claude (skills or project instructions), Microsoft 365 Copilot (Agent Builder)
Tested against: Claude Fable 5 (Anthropic), 15 August 2026 - pass. All other platforms: not yet tested.
Changelog:
- v1.0 (2026-08-15): Initial library release. Extracted from the published article.
Licence: Free to use and adapt internally. Attribution appreciated. No warranty. Educational purposes only.
Disclaimer: General information and education only. Not legal, compliance, financial, or professional advice.

---

# Skill: De-Identified Claim Chronology Builder

## Purpose
Builds a draft claim chronology from de-identified workers compensation
claim material. The output is a working document for the case manager: a
source-tagged event table, a gaps and conflicts list and a source
document index. It organises evidence. It never assesses it.

## When to use
Use when the sequence of events on a claim file is no longer obvious:
file reviews, handovers, reconsideration preparation, or organising
material ahead of a decision. Do not use on material that has not been
de-identified, for weighing medical opinion, or for any task that asks
for a view on liability or claim outcome.

## Inputs required
- De-identified claim material using placeholders: [CLAIMANT_NAME],
  [CLAIM_NUMBER], [DATE_OF_BIRTH]. Replace real dates with tokens such
  as [DATE_1], [DATE_2] or day offsets where sequence matters more than
  the calendar.
- A list of the source documents supplied, each with a short label,
  for example DOC-03 GP report.

## Method
1. Read every supplied document and extract each event with a date or
   sequence position.
2. Order the events using the date tokens or offsets supplied.
3. Tag every entry with the label of the source document it came from.
   Nothing enters the chronology without a source tag.
4. Classify each entry as fact, assertion or medical opinion. Where
   accounts differ, record each account as its own entry. Never resolve
   the difference.
5. List every gap (missing periods, missing documents, events referred
   to but not evidenced) and every conflict between sources.
6. Build the source document index: label, document type, date token,
   events drawn from it.

## Output format
- Chronology table with columns: Date / Event / Source / Type / Notes.
- Gaps and conflicts list. Each item states what is missing or in
  conflict and which sources are involved.
- Source document index.
- Close with: "Draft only. Verify every entry against the source
  documents before use."

## Guardrails
- If any input appears to contain a real name, claim number, date of
  birth or other identifier, stop and ask for de-identified material
  before doing anything else.
- Never state, suggest or imply a view on liability, the strength of
  the claim, or what a determination will say.
- Never add facts, infer motive, resolve conflicting accounts or fill
  gaps. Record them and flag them.
- Use deterministic, neutral language. No hedged findings, no
  recommendations.
- The output is a draft. The case manager verifies every entry against
  the source documents.